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

E9000 Server V100R001 HMM Alarm Handling 19

This document describes E9000 server alarms in terms of the meaning, impact on the system, possible causes, and solutions.
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).
OSPFv3

OSPFv3

OSPFv3_1.3.6.1.2.1.191.0.2 ospfv3NbrStateChange

Description

The status of the non-virtual neighbor changes. (RouterId=[RouterId], NbrIfIndex=[NbrIfIndex], NbrIfInstId=[NbrIfInstId], NbrRtrId=[NbrRtrId], NbrState=[NbrState], SubReason=[SubReason], Reason=[NbrStateChangeReason])

The OSPFv3 neighbor status changes. The possible causes are that the status of the interface on the neighbor router changes and the contents of Hello packets change.

Attributes

Attributes

Description

Trap OID

1.3.6.1.2.1.191.0.2

Trap severity

Critical

Match trap

The clear-alarm trap is in the format of OSPFv3_1.3.6.1.2.1.191.0.2 ospfv3NbrStateChange. The fault trap and service restoration trap are in the same format except that the value of NbrState is different. The trap is a service restoration trap only when the value of 8: Full. Otherwise, it is a fault trap.

Parameters

Parameter

Description

RouterId

Indicates the router ID.

NbrIfIndex

Indicates the IP address of the neighbor.

NbrIfInstId

Indicates the interface index.

NbrRtrId

Indicates the router ID of the neighbor.

NbrState

Indicates the neighbor status.

  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2-Way
  • 5: ExStart
  • 6: Exchange
  • 7: Loading
  • 8: Full

SubReason

Indicates the detailed reason.

Reason

Indicates the reason why the neighbor status changes:

  • 1 (adjacencyHoldTimerExpired): The timer of the adjacent router timer times out.
  • 2 (physicalInterfaceChange): The status of the router physical interface on the router changes.
  • 3 (ospfProtocolReason): An OSPF protocol error occurs.
  • 4 (bfdSessionStateChange): The BFD session is closed.
  • 5 (configureChange): The OSPF configuration changes.
  • 6 (peerRouterReason): An alarm is generated because of the neighboring router.
  • 100 (alarmCleared): The alarm is cleared because services are restored or the neighbor is deleted.
Impact on the System

Whenever the non-virtual neighbor status changes, the trap will be sent. If the neighbor changes from a lower state to a higher state, this trap message is informational only and no action is required. If the neighbor changes from a higher state to a lower state, services may be interrupted.

Possible Causes

Cause 1: The status of the interface on the neighbor router changes.

Cause 2: Interface configurations on the local and remote devices are changed. The configurations include the Hello or Dead timer, interface authentication, and network type.

Cause 3: The reset ospfv3 command is used to restart the OSPF or perform a active/standby switchover.

Cause 4: A packet transmission error occurs and ping fails.

Procedure
  1. Run the display ipv6 interface and display ospfv3 peer commands to check the interface status of the neighbor router.
  • If the physical interface is Down, check whether the link is functioning properly. If the link is functioning properly, go to Step 2.
  • If the physical interface is Up, go to Step 2.
  1. Ping the peer IP address to check whether packets are forwarded correctly.

    • If the ping fails, go to Step 5.
    • If the ping succeeds, go to Step 3.

  2. Run the display ipv6 interface command on the neighbor device to check whether the OSPFv3 neighbor interface is in the Up state.

    • If the interface is in the Down state, go to Step 5.
    • If the interface is in the Up state, go to Step 4.

  3. Run the display ospfv3 interface command to check whether configurations on both ends are correct.

    • If they are correct, go to Step 6.
    • If they are incorrect, go to Step 5.

  4. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.
  5. End.

OSPFv3_1.3.6.1.2.1.191.0.4 ospfv3IfConfigError

Description

A packet is received on the non-virtual interface from a router whose configuration conflicts with the local configuration. (RouterId=[RouterId], IfIndex=[IfIndex], IfInstId=[IfInstId], IfState=[IfState], PacketSrc=[PacketSrc], ConfigErrorType=[ConfigErrorType], PacketType=[PacketType])

This alarm indicates that the configurations of interfaces used to establish a neighbor relationship are inconsistent. Possible causes are that the Hello, Dead, or Poll timer configurations on both ends were inconsistent or the interface configurations on both ends were not performed in the same area.

Attributes

Attributes

Description

Trap OID

1.3.6.1.2.1.191.0.4

Trap severity

Minor

Parameters

Parameter

Description

RouterId

Indicates the router ID.

IfnetIndex

Indicates the interface index.

NbrIfInstId

Indicates the ID of a neighbor interface.

NbrRtrId

Indicates the ID of a neighbor router.

NbrState

Indicates the neighbor status.

  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2-Way
  • 5: ExStart
  • 6: Exchange
  • 7: Loading
  • 8: Full

SubReason

Indicates detailed reasons.

Reason

Possible causes of the neighbor status change are as follows:

  • 1: adjacencyHoldTimerExpired. The value indicates that the timer of the neighbor switch modules times out.
  • 2: physicalInterfaceChange. The value indicates that the physical interface status of the switch modules changes.
  • 3: ospfProtocolReason. The value indicates that an OSPF protocol error occurs.
  • 4: bfdSessionStateChange. The value indicates that a BFD session is torn down.
  • 5: configureChange. The value indicates that OSPF configurations change.
  • 6: peerRouterReason. The value indicates that the neighbor switch modules does not function properly.
  • 100: alarmCleared. The value indicates that the service is restored or the neighbor switch modules is deleted and the alarm is cleared.
Impact on the System

This trap message is generated after an interface receives a message indicating that parameters are incorrectly configured. Such configuration errors generally occur during the deployment test or service cutover. You can adjust the parameters correctly to rectify the fault, and services will not be affected.

Possible Causes

Cause 1: Interface configurations on both ends of the link were inconsistent.

Cause 2: The link protocol changed.

Procedure
  1. Use the display ospfv3 interface command to check whether the interface configurations on both ends of the link are consistent.
  • If they are consistent, go to Step 3.
  • If they are inconsistent, go to Step 2.
  1. Perform the following operations based on the networking condition:

    • If the configurations on both ends can be changed to be consistent, set the same Hello timer value, Dead timer value, and Poll timer value on both ends. Then check whether the alarm is cleared.
      • If the alarm is cleared, go to Step 4.
      • If the alarm persists, go to Step 3.
    • If the configurations on both ends of the link cannot be changed to be consistent, go to Step 3.

  2. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.
  3. End.

OSPFv3_1.3.6.1.2.1.191.0.6 ospfv3IfRxBadPacket

Description

An OSPFV3 packet that is received on a non-virtual interface cannot be parsed. (RouterId=[RouterId], IfIndex=[IfIndex], IfInstId=[IfInstId], IfState=[IfState], PacketSrc=[PacketSrc], PacketType=[PacketType])

An OSPFv3 packet that could not be parsed was received from a non-virtual interface. The possible cause is that the local device was attacked or the local device failed to connect to a non-Huawei device.

Attributes

Attributes

Description

Trap OID

1.3.6.1.2.1.191.0.6

Trap severity

Minor

Parameters

Parameter

Description

RouterId

Indicates the router ID.

IfIndex

Indicates the interface index.

IfInstId

Indicates the instance ID.

IfState

Indicates the interface status.

  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2–Way
  • 5: Exstart
  • 6: Exchange
  • 7: Loading
  • 8: Full

PacketSrc

Indicates the source IP address of packets.

PacketType

Indicates the packet type.

  • 1: Hello
  • 2: DD(Data base Description) packet
  • 3: LS Request
  • 4: LS Update
  • 5: LS Acknowledgement
  • 6: NULL packet
Impact on the System

This trap message is generated when a common interface receives a packet that cannot be parsed and discards this packet, which may change the neighbor status to Down.

Possible Causes

An incorrect packet was generated on the peer non-virtual interface.

Procedure
  1. Run the display ospfv3 error packet command in the diagnosis view to check the incorrect packet. This trap message indicates that the packet cannot be parsed. Save information about the incorrect packet.
  2. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.
  3. End.

OSPFv3_1.3.6.1.2.1.191.0.10 ospfv3IfStateChange

Description

The status of the non-virtual interface changes. (RouterId=[RouterId], IfIndex=[IfIndex], IfInstId=[IfInstId], IfState=[IfState])

An OSPFv3 packet that could not be parsed was received from a non-virtual interface. The possible cause is that the local device was attacked or the local device failed to connect to a non-Huawei device.

Attributes

Attributes

Description

Trap OID

1.3.6.1.2.1.191.0.10

Trap severity

Warning

Parameters

Parameter

Description

RouterId

Indicates the router ID.

IfIndex

Indicates the interface index.

IfInstId

Indicates the instance ID.

IfState

Indicates the interface status.

  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2–Way
  • 5: Exstart
  • 6: Exchange
  • 7: Loading
  • 8: Full
Impact on the System

This trap message is generated when the status of a common interface changes from a lower status to Full or from a higher status to a lower status. This trap message may affect the neighbor status. If the interface goes to a lower status such as Down, the neighbor relationship will be interrupted.

Possible Causes

Cause 1: The physical interface was in the Down state.

Cause 2: An OSPFv3 neighbor relationship was being established.

Procedure
  1. Run the display ospfv3 interface command to check whether the interface status is Up.
  • If the status is Up, go to step 3.
  • If the status is not Up, go to step 2.
  1. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.
  2. End.

OSPFv3_1.3.6.1.2.1.191.0.13 ospfv3NbrRestartHelperStatusChange

Description

The neighbor exits from the restart helper state. (RouterId=[RouterId], NbrIfIndex=[NbrIfIndex], NbrIfInstId=[NbrIfInstId], NbrRtrId=[NbrRtrId], NbrRestartHelperStatus=[NbrRestartHelperStatus], NbrRestartHelperAge=[NbrRestartHelperAge], NbrRestartHelperExitReason=[NbrRestartHelperExitReason])

The GR helper status of the OSPFv3 neighbor changed.

Attributes

Attributes

Description

Trap OID

1.3.6.1.2.1.191.0.13

Trap severity

Warning

Parameters

Parameter

Description

RouterId

Indicates the router ID.

NbrIfIndex

Indicates the index of the neighbor interface.

NbrIfInstId

Indicates the instance ID of the neighbor interface.

NbrRtrId

Indicates the neighbor router ID.

NbrRestartHelperStatus

Indicates the neighbor helper status.

NbrRestartHelperAge

Indicates the remaining time of a neighbor helper.

NbrRestartHelperExitReason

Indicates the reason why the neighbor device exits the Helper status.

  • 1: None
  • 2: In progress
  • 3: Completed
  • 4: Time out
  • 5: Topology change
Impact on the System

This trap message indicates whether the neighbor device is in the Helper state. If the GR process fails, the normal forwarding of routes is affected.

Possible Causes

Cause 1: The neighboring router in the helper state restarted.

Cause 2: The GR period expired.

Cause 3: The neighboring router received a Grace-LSA and exited from the helper state.

Procedure
  1. Perform the following operations as required:
  • If the trap message was caused by a manual active/standby switchover or OSPFv3 process restart by GR, go to step 4.
  • If the trap message was not caused by manual operations, go to step 3.
  1. Collect the alarm information, log information, and configuration information, and then contact Huawei technical support personnel.
  2. End.
Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 196168

Downloads: 1571

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