No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
OSPF_1.3.6.1.4.1.2011.5.25.155.31.4 hwOspfv2IntraAreaDRIpAddressConflict

OSPF_1.3.6.1.4.1.2011.5.25.155.31.4 hwOspfv2IntraAreaDRIpAddressConflict

Description

OSPF/2/IPADDR_CONFLCT:OID [oid] IP addresses of DRs in an intra area conflict. (ProcessId=[integer], AreaId=[ipaddr], SelfIfnetIndex=[integer], NbrIpAddr=[ipaddr], RouterId=[ipaddr], IntierfaceIpAddress=[ipaddr], InterfaceName=[octet])

IP addresses of DRs in an intra area conflict.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.155.31.4 Major communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

ProcessId

Process ID

AreaId

Area ID

SelfIfnetIndex

Index of an interface

NbrIpAddr

IP address of a neighbor

RouterId

Local router ID

IntierfaceIpAddress

IP address of an interface

InterfaceName

Name of an interface

Impact on the System

The same IP address is configured for two indirectly connected router devices in the same area. Of which, one is selected as a DR to advertise network LSAs. As a result, route flapping occurs frequently.

Possible Causes

The same IP address was configured for two indirectly connected router devices in the same area. Of which, one was selected as a DR to advertise network LSAs.

Procedure

  1. Check whether the IP address displayed in this alarm conflicts with that of any interface in the same area.

    • If a conflict exists, go to Step 2.
    • If no conflict exists, go to Step 3.

  2. Change an IP address of a local interface to check whether the alarm is cleared.

    • If the alarm is cleared, go to Step 4.
    • If the alarm persists, go to Step 3.

  3. contact technical support personnel.
  4. End.

Related Information

None.

Translation
Download
Updated: 2019-08-12

Document ID: EDOC1100034065

Views: 144377

Downloads: 42

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next