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

S9300, S9300E, and S9300X V200R010C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
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.2.1.14.16.2.3 ospfVirtNbrStateChange

OSPF_1.3.6.1.2.1.14.16.2.3 ospfVirtNbrStateChange

Description

OSPF/3/NBBRCHG:OID [oid]: The status of the virtual neighbor changes. (VirtNbrArea=[area-id], VirtNbrRtrId=[neighbor-router-id], ProcessId=[process-id], RouterId=[router-id], VirtNbrState=[neighbor-state], InstanceName=[instance-name])

The status of the neighbor on the OSPF virtual link changed because the interface status of the virtual link changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.14.16.2.3 Minor environmentalAlarm (6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VirtNbrArea

Indicates the area ID.

VirtNbrRtrId

Indicates the router ID of the neighbor on the virtual link.

ProcessId

Indicates the process ID.

RouterId

Indicates the ID of the local switch.

VirtNbrState

Indicates the status of the neighbor.
  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2Way
  • 5: ExStart
  • 6: Exchange
  • 7: Loading
  • 8: Full

InstanceName

Indicates the instance name.

Impact on the System

This trap message will be generated when the status of the neighbor on the virtual link changes. If the status of the neighbor on the virtual link changes from Full to lower than Full, routes are incorrectly installed to the routing table, or some routes are wrongly deleted. This may affect services.

Possible Causes

1. The status of the physical interface of the virtual link changed.

2. The configured parameters (such as Hello timer, dead timer and interface authentication) of the interfaces that set up the neighbor relationship were inconsistent.

3. OSPF was restarted by using the reset ospf process command or the active/standby switchover was performed.

4. An error packet was received.

5. The overflow function is configured and the process entered the Overflow state.

6. Routes of the area configured with the virtual link were added or deleted.

7. The ping operation failed, which indicated that an error occurred during the transmission of the packet.

Procedure

  1. Run the display ospf interface and display ip interfacebrief commands to check whether the status of the interface used to establish the virtual link is normal.

    • If the physical interface is Down, check whether the link or interface is configured with the shutdown command.

    • If the protocol status of the interface is Down, check whether the interface is configured with an IP address.

    If the interface status is normal, go to Step 2.

  2. Run the display ospf peer command to check whether the OSPF neighbor relationship is normal.

    • If the neighbor relationship is abnormal, check whether trap 1.3.6.1.2.1.14.16.2.2 exists. If the trap exists, locate the problem according to the trap. If the trap does not exist, go to Step 6.

    • If the neighbor relationship is normal, go to Step 3.

  3. Run the display ospf routing router-id [ router-id ] command to check whether the switch object exists. router-id indicates the IP address of the neighbor on the virtual link.

    • If the route does not exist, go to Step 4.

    • If the route exists, go to Step 5.

  4. Configure the route to the neighbor of the virtual link. Then check whether the trap is cleared.

    • If so, go to Step 7.

    • If not, go to Step 5.

  5. Run the display ospf vlink and display current- configuration configuration ospf commands to check whether the configurations (including the Hello interval, Dead interval, and poll interval) on the two ends of the virtual link are consistent.

    • If the configurations are correct, check whether trap 1.3.6.1.2.1.14.16.2.14 exists.
      • If the trap exists, rectify the fault according to the related procedure of the trap.

      • If the trap does not exist, go to Step 6.

    • If not, run the following command to modify the configurations on the two ends to be consistent.

      vlink-peer router-id [ dead dead-interval | hello hello-interval | retransmit retransmit-interval | smart-discover | trans-delay trans-delay-interval | [ simple [ plain plain-text | [ cipher ] cipher-text ] | { md5 | hmac-md5 | hmac-sha256 } [ key-id { plain plain-text | [ cipher ] cipher-text } ] | authentication-null | keychain keychain-name ] ] *

      Then, check whether the trap is cleared.

      • If so, go to Step 7.

      • If not, go to Step 6.

  6. Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

None

Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000142054

Views: 190145

Downloads: 44

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