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 V200R013C00

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).
OSPFV3

OSPFV3

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.1 hwOspfv3VirtIfStateChange

Description

OSPFV3/2/VIFCHANGE:OID [oid] The status of the virtual interface has changed. (AreaId=[integer], NbrRouterId=[gauge], RouterId=[gauge], VIfState=[integer], ChgReason=[integer])

The status of the OSPFv3 virtual link interface changed. A possible cause is that the router ID of the neighbor on the virtual link changed after the virtual link was configured or the status of the physical interface of the virtual link changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.1 Major processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

AreaId

Indicates the ID of the OSPFv3 area. The value is a decimal integer.

NbrRouterId

Indicates the Router ID of the virtual neighbor. The value is a decimal integer.

RouterId

Indicates the Router ID of the local switch. The value is a decimal integer.

VIfState

Indicates the state of the virtual link interface.
  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2-Way
  • 5: Exstart
  • 6: Exchange
  • 7: Loading
  • 8: Full

ChgReason

Indicates the reason for change in the state of an OSPFv3 virtual interface.
  • 1: No Event
  • 2: Interface Up
  • 3: Wait Timer Expired
  • 4: Backup Seen Occurred
  • 5: Neighbor Change Event Occurred
  • 6: Loop Ind
  • 7: Unloop Ind
  • 8: Interface Down

Impact on the System

This trap message is generated when the status of a virtual interface changes. This trap may affect the neighbor status. If the interface goes Down, the neighbor relationship will be interrupted.

Possible Causes

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

2. The router ID of the neighbor on the virtual link changed.

Procedure

  1. Run the display ospfv3 vlink command to check whether the status of the virtual link interface is Up.

    • If so, it indicates that this trap message is informational only, and no action is required. Then, go to Step 5.

    • If not, go to Step 2.

  2. Run the display ipv6 interface and display ospfv3 interface commands to check whether the interface status is Up.

    • If so, go to Step 3.

    • If not, check the connection between physical interfaces. After the interface turns Up, check whether the alarm is cleared.
      • If so, go to Step 5.

      • If not, go to Step 3.

  3. Run the display current-configuration configuration ospfv3 command to check whether the ID of the neighbor on the virtual link changes.

    • If so, modify the configurations of the two ends to be the same. Then check whether the trap is cleared.
      • If so, go to Step 5.

      • If not, go to Step 4.

    • If not, go to Step 4.

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

Related Information

None

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.2 hwOspfv3NbrStateChange

Description

OSPFV3/2/NBRCHANGE:OID [oid] The status of the non-virtual neighbor has changed. (IfIndex=[integer], InstanceId=[integer], NbrRouterId=[gauge], RouterId=[gauge], NbrState=[integer], IfName=[octet], ChgReason=[integer])

The status of the OSPFv3 neighbor changed. A possible cause is that the status of the interface where the neighbor resided changed or the contents of the received Hello packets changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.2 Major processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

IfIndex

Indicates the index of the interface. The value is a decimal integer.

IfName

Indicates the name of the interface.

InstanceId

Indicates the ID of the OSPFv3 instance. The value is a decimal integer.

NbrRouterId

Indicates the Router ID of the neighbor. The value is a decimal integer.

RouterId

Indicates the Router ID of the local switch. The value is a decimal integer.

NbrState

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

ChgReason

Indicates the reason for change in the state of an OSPFv3 neighbor.
  • 1: No Event
  • 2: Received Hello Packet
  • 3: Start
  • 4: Received Two Way
  • 5: Negotiation Done
  • 6: ExchangeDone
  • 7: Received Bad LS Request
  • 8: Loading Done
  • 9: Established Adjacency
  • 10: Mismatch In Seq Number
  • 11: Received One Way
  • 12: NBR Killed
  • 13: Inactivity Timer Expired
  • 14: Link Down

Impact on the System

This trap is generated when the status of the neighbor (not a neighbor of a virtual link) changes. This trap indicates that the status of the neighbor changes. If the neighbor changes from a lower status to a higher status, this trap message is informational only, and no action is required. If the neighbor changes from a higher status to a lower status, services may be interrupted.

Possible Causes

  1. The status of the interface where the neighbor resided changed.
  2. The configured parameters (such as the Hello timer, dead timer, interface authentication, and network type) of the interfaces on the local end or remote end were modified.
  3. OSPF was restarted by using the reset ospfv3 command or the active/standby switchover was performed.
  4. The ping operation failed, which indicated that an error occurred during packet transmission.

Procedure

  1. Run the display ipv6 interface and display ospfv3 peer commands to check the status of the interface where the neighbor resides.

    • If the physical interface is Down, check the link and make the link Up, and then go to Step 2.

    • If the physical interface is Up, go to Step 2.

  2. Check whether packets are correctly forwarded and ping the IP address of the remote interface.

    • If the ping fails, go to Step 5.

    • If the ping succeeds, go to Step 3.

  3. Run the display ipv6 interface command to check whether the interface where the OSPFv3 neighbor resides 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.

  4. Run the display ospfv3 interface command to check whether the configurations of the two ends are correct.

    • If so, go to Step 6.

    • If not, go to Step 5.

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

Related Information

None

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.3 hwOspfv3VirtNbrStateChange

Description

OSPFV3/2/VNBRCHANGE:OID [oid] The status of the virtual neighbor has changed. (AreaId=[integer], VirtualNbrRouterId=[gauge], RouterId=[gauge], VNbrState=[integer], ChgReason=[integer])

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

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.3 Major processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

AreaId

Indicates the ID of the OSPFv3 area. The value is a decimal integer.

VirtualNbrRouterId

Indicates the Router ID of the virtual link neighbor. The value is a decimal integer.

RouterId

Indicates the Router ID of the local switch. The value is a decimal integer.

VNbrState

Indicates the state of the virtual link neighbor.
  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2-Way
  • 5: Exstart
  • 6: Exchange
  • 7: Loading
  • 8: Full

ChgReason

Indicates the reason for change in the state of virtual link neighbor.
  • 1: No Event
  • 2: Received Hello Packet
  • 3: Start
  • 4: Received Two Way
  • 5: Negotiation Done
  • 6: ExchangeDone
  • 7: Received Bad LS Request
  • 8: Loading Done
  • 9: Established Adjacency
  • 10: Mismatch In Seq Number
  • 11: Received One Way
  • 12: NBR Killed
  • 13: Inactivity Timer Expired
  • 14: Link Down

Impact on the System

This trap is generated when the status of the neighbor (a neighbor of a virtual link) changes. If the neighbor changes from a lower status to a higher status, this trap message is informational only, and no action is required. If the neighbor changes from a higher status to a lower status, services may be interrupted.

Possible Causes

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

2. The configured parameters (such as the Hello timer, dead timer, interface authentication, and network type) of the virtual link interface on the local end or remote end were modified.

3. OSPFv3 was restarted by using the reset ospfv3 command or the active/standby switchover was performed.

4. An error packet was received.

5. The overflow function was 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 packet transmission.

Procedure

  1. Run the display ospfv3 interface and display ipv6 interface brief commands to check whether the physical interface of the virtual link goes Down.

    • If the physical interface is Down, check the link and make the link Up, and then go to Step 2.

    • If the physical interface is Up, go to Step 2.

  2. Run the display ospfv3 peer command to check whether the OSPFv3 neighbor relationship is normal.

    • If the neighbor relationship is abnormal, check whether trap 1.3.6.1.4.1.2011.5.25.147.0.2 exists. If the trap exists, locate the fault 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 ospfv3 routing command to check whether the route to the neighbor on the virtual link exists.

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

    • If the route exists, go to Step 4.

  4. Run the display ospfv3 vlink and display current-configuration configuration ospfv3 commands to check whether the configurations of the two ends are correct.

    • If so, go to Step 6.

    • If not, go to Step 5.

  5. Adjust the parameters correctly according to the requirements of the networking, and 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

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.4 hwOspfv3IfConfigError

Description

OSPFV3/2/IFCFGERR:OID [oid] The configuration of the non-virtual interface is incorrect. (IfIndex=[integer], InstanceId=[integer], RouterId=[gauge], IfState=[integer], PacketSrcAdd=[octet], ErrorType=[integer], PacketType=[integer])

This trap is generated on a non-virtual-link interface when the local end refused to establish the adjacency relationship with the remote end. This trap indicated that the configurations of the interfaces on which the neighbor relationship is to be established were inconsistent. A possible cause is that the values of the Hello timer, dead timer, poll timer were not consistent on the two interfaces or the two interfaces were not in the same area.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.4 Major processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

IfIndex

Indicates the index of the interface. The value is a decimal integer.

InstanceId

Indicates the ID of the OSPFv3 instance. The value is a decimal integer.

RouterId

Indicates the Router ID of the local switch. The value is a decimal integer.

IfState

Indicates the status of an interface.
  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2-Way
  • 5: Exstart
  • 6: Exchange
  • 7: Loading
  • 8: Full

PacketSrcAdd

Indicates the address of the source node that sends the packet.

ErrorType

Indicates the type of the error.
  • 1: badVersion
  • 2: areaMismatch
  • 3: unknownNbmaNbr
  • 4: unknownVirtualNbr
  • 5: helloIntervalMismatch
  • 6: deadIntervalMismatch
  • 7: optionMismatch
  • 8: mtuMismatch
  • 9: duplicateRouterId
  • 10: noError

PacketType

Indicates the type of the packet.
  • 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 is generated when an interface receives a packet indicating parameters are incorrectly configured. Such configuration errors generally occur during the deployment test or cutover. You can rectify the fault by modifying the parameters on the two ends to be consistent, and services will not be affected.

Possible Causes

1. Parameters manually configured on the two interfaces were inconsistent.

2. The routing protocol on the link layer changed.

Procedure

  1. Run the display ospfv3 interface command to check whether the configurations of the two ends are consistent.

    • If so, go to Step 3.

    • If not, go to Step 2.

  2. Perform the following operations according to the networking:

    • If it is allowed to modify the configurations of the two ends to be consistent, go to Step 4.

    • If it is not allowed to modify the configurations of the two ends to be consistent, go to Step 3.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.5 hwOspfv3VirtIfConfigError

Description

OSPFV3/2/VIFCFGERR:OID [oid] The configuration of the virtual interface is incorrect. (AreaId=[integer], VirtualNbrRouterId=[gauge], RouterId=[gauge], VIfState=[integer], ErrorType=[integer], PacketType=[integer])

Configurations of the virtual link interface were incorrect. A possible cause is that the configurations of the parameters conflicted.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.5 Major processingErrorAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

AreaId

Indicates the ID of the OSPFv3 area. The value is a decimal integer.

VirtualNbrRouterId

Indicates the Router ID of the virtual neighbor. The value is a decimal integer.

RouterId

Indicates the Router ID of the local switch. The value is a decimal integer.

VIfState

Indicates the state of the virtual neighbor.
  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2-Way
  • 5: Exstart
  • 6: Exchange
  • 7: Loading
  • 8: Full

Errortype

Indicates the type of the error.
  • 1: badVersion
  • 2: areaMismatch
  • 3: unknownNbmaNbr
  • 4: unknownVirtualNbr
  • 5: helloIntervalMismatch
  • 6: deadIntervalMismatch
  • 7: optionMismatch
  • 8: mtuMismatch
  • 9: duplicateRouterId
  • 10: noError

Packettype

Indicates the type of the packet.
  • 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 is generated when the virtual link interface received a packet indicating parameters were incorrectly configured. Such configuration errors generally occur during the deployment test or cutover. You can modify the parameters on the two ends to be consistent to rectify the fault, and services will not be affected.

Possible Causes

The configurations of the interfaces on the two ends of the virtual link conflicted.

Procedure

  1. Run the display ospfv3 vlink and display current-configuration interface commands to check whether the configurations of the two interfaces are consistent.

    • If so, go to Step 3.

    • If not, go to Step 2.

  2. Perform the following operations according to the networking:

    • If it is allowed to modify the configurations of the two ends to be consistent, go to Step 4.

    • If it is not allowed to modify the configurations of the two ends to be consistent, go to Step 3.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.6 hwOspfv3IfRxBadPacket

Description

OSPFV3/3/IFRXBADPKT:OID [oid] Error packet was received on the non-virtual interface. (IfIndex=[integer], InstanceId=[integer], RouterId=[gauge], IfState=[integer], PacketSrcAdd=[octet], PacketType=[integer])

An OSPFv3 packet that cannot be parsed was received from a non-virtual-link interface. A possible cause is that the Huawei device was attacked or the interconnection between the Huawei device and non-Huawei device failed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.6 Minor processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

IfIndex

Indicates the index of the interface.

InstanceId

Indicates the ID of the OSPFv3 instance. The value is a decimal integer.

RouterId

Indicates the Router ID of the local switch. The value is a decimal integer.

IfState

Indicates the status of the non-virtual link interface.
  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2-Way
  • 5: Exstart
  • 6: Exchange
  • 7: Loading
  • 8: Full

PacketSrcAdd

Indicates the address of the source node that sends the packet.

PacketType

Indicates the type of the packet.
  • 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 is generated when a common interface receives an errored packet that cannot be processed and then discards this packet. This may cause the neighbor to go Down.

Possible Causes

An errored packet was generated by the non-virtual-link interface on the remote end.

Procedure

  1. Collect alarm information and configuration information, and then contact technical support personnel.
  2. End.

Related Information

None

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.7 hwOspfv3VirtIfRxBadPacket

Description

OSPFV3/3/VIFRXBADPKT:OID [oid] Error packet was received on the virtual interface. (AreaId=[integer], VirtualNbrRouterId=[gauge], RouterId=[gauge], VIfState=[integer], PacketType=[integer])

An OSPFv3 packet that cannot be parsed was received from a virtual link interface. A possible cause is that the Huawei device was attacked or the interconnection between the Huawei device and non-Huawei device failed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.7 Minor processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

AreaId

Indicates the ID of the OSPFv3 area. The value is a decimal integer.

VirtualNbrRouterId

Indicates the Router ID of the virtual neighbor. The value is a decimal integer.

RouterId

Indicates the Router ID of the local switch. The value is a decimal integer.

VIfState

Indicates the status of a virtual link interface.
  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2-Way
  • 5: Exstart
  • 6: Exchange
  • 7: Loading
  • 8: Full

Packettype

Indicates the type of the packet.
  • 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 is generated when a virtual link interface receives a packet that cannot be parsed and then discards this packet. This may cause the neighbor to go Down.

Possible Causes

An errored packet was generated by the interface on the remote end of the virtual link.

Procedure

  1. Collect alarm information and configuration information, and then contact technical support personnel.
  2. End.

Related Information

None

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.8 hwOspfv3IfStateChange

Description

OSPFV3/2/IFCHANGE:OID [oid] The status of the non-virtual interface has changed. (IfIndex=[integer], InstanceId=[integer], RouterId=[gauge], IfState=[integer], IfName=[octet], ChgReason=[integer])

The status of the OSPFv3 non-virtual-link interface changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.8 Major processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

IfIndex

Indicates the index of the interface. The value is a decimal integer.

InstanceId

Indicates the ID of the OSPFv3 instance. The value is a decimal integer.

RouterId

Indicates the Router ID of the local switch. The value is a decimal integer.

IfState

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

IfName

Indicates the name of the interface.

ChgReason

Indicates the reason for change in the state of an OSPFv3 interface.
  • 1: No Event
  • 2: Interface Up
  • 3: Wait Timer Expired
  • 4: Backup Seen Occurred
  • 5: Neighbor Change Event Occurred
  • 6: Loop Ind
  • 7: Unloop Ind
  • 8: Interface Down

Impact on the System

This trap is generated when the status of a common interface changes. This trap may affect the neighbor status. If the interface goes Down, the neighbor relationship will be interrupted.

Possible Causes

1. The physical interface went Up or Down.

2. The OSPFv3 neighbor relationship was being established.

Procedure

  1. Run the display rm interface and display ipv6 interface brief commands to check whether the interface is Down.

    • If the physical interface is Down, check the link. Then check whether the trap is cleared.
      • If so, go to Step 4.

      • If not, go to Step 2.

    • If the physical interface is Up, go to Step 2.

  2. Run the display ospfv3 interface command to check whether the current interface is Up.

    • If so, go to Step 4.

    • If not, go to Step 3.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.9 hwOspfv3RestartStatusChange

Description

OSPFV3/3/RESTARTSTATUSCHANGE:OID [oid] The graceful restart status of the router has changed. (RouterId=[gauge], State=[integer], RestartInterval=[integer], RestartExitReason=[integer])

The GR status of the switch changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.9 Minor processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

RouterId

Indicates the Router-ID of the local node. The value is a decimal integer.

State

Indicates the restart status.
  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2-Way
  • 5: Exstart
  • 6: Exchange
  • 7: Loading
  • 8: Full

RestartInterval

Indicates the interval of GR.

RestartExitReason

Indicates the cause why the switch exits from the GR.
  • 1: None
  • 2: In progress
  • 3: Completed
  • 4: Time out
  • 5: Topology change

Impact on the System

This trap indicates that a switch enters the GR state or exists from the GR state. GR failure will affect the normal forwarding of routes.

Possible Causes

1. OSPFv3 exited from GR.

2. The GR period exceeded the set value.

3. OSPFv3 GR is reset.

Procedure

  1. Run the display ospfv3 graceful-restart-information command to check the cause of becoming the GR and the current GR status.
  2. Perform the following operations as required:

    • If the active/standby switchover is performed manually or the OSPFv3 process is restarted in GR mode, go to Step 4.

    • If this trap is generated without any manual operation, go to Step 3.

    • If the reset ospfv3 graceful-restart command is executed, go to Step 4.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.10 hwOspfv3NbrRestartHelperStatusChange

Description

OSPFV3/3/NBRHELPERSTATUSCHNG:OID [oid] The helper status for the non-virtual neighbor has changed. (IfIndex=[integer], InstanceId=[integer], NbrRouterId=[gauge], RouterId=[gauge], State=[integer], HelperAge=[integer], HelperExitReason=[integer])

The GR helper status of the OSPFv3 neighbor changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.10 Minor processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

IfIndex

Indicates the index of the interface. The value is a decimal integer.

InstanceId

Indicates the ID of the OSPFv3 instance. The value is a decimal integer.

NbrRouterId

Indicates the Router ID of the neighbor. The value is a decimal integer.

RouterId

Indicates the Router ID of the local switch. The value is a decimal integer.

State

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

HelperAge

Indicates the remaining time of GR.

HelperExitReason

Indicates the cause why the switch exits from the GR helper status.
  • 1: None
  • 2: In progress
  • 3: Completed
  • 4: Time out
  • 5: Topology change

Impact on the System

This trap indicates a switch enters the GR helper state or exits from the GR helper state. GR failure will affect the normal forwarding of routes.

Possible Causes

1. The neighbor also restarts when it functions as a GR helper.

2. The grace timer expired.

3. The grace LSA was received.

Procedure

  1. Run the display ospfv3 graceful-restart-information command to check the reason that the local switch functions as the GR helper and check the current GR status.
  2. Perform the following operations as required:

    • If the active/standby switchover is performed manually or the OSPFv3 process is restarted in GR mode, go to Step 4.

    • If this trap is generated without any manual operation, go to Step 3.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.11 hwOspfv3VirtNbrRestartHelperStatusChange

Description

OSPFV3/3/VNBRHELPERSTATUSCHNG:OID [oid] The helper status for the virtual neighbor has changed. (AreaId=[integer], VirtualNbrRouterId=[gauge], RouterId=[gauge], State=[integer], HelperAge=[integer], HelperExitReason=[integer])

The GR helper status of the OSPFv3 neighbor on the virtual link changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.11 Minor processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

AreaId

Indicates the ID of the OSPFv3 area. The value is a decimal integer.

VirtualNbrRouterId

Indicates the Router ID of the virtual neighbor. The value is a decimal integer.

RouterId

Indicates the Router ID of the local switch. The value is a decimal integer.

State

Indicates the state of the virtual neighbor.
  • 1: Down
  • 2: Attempt
  • 3: Init
  • 4: 2-Way
  • 5: Exstart
  • 6: Exchange
  • 7: Loading
  • 8: Full

HelperAge

indicates the remaining time of GR.

HelperExitReason

Indicates the cause why the route exits from the GR helper.
  • 1: None
  • 2: In progress
  • 3: Completed
  • 4: Time out
  • 5: Topology change

Impact on the System

This trap indicates that the neighbor on the virtual link enters the helper state or exits from the helper state. GR failure will affect the normal forwarding of routes.

Possible Causes

1. The neighbor also restarts when it functions as a GR helper.

2. The grace timer expired.

3. The grace LSA was received.

Procedure

  1. Run the display ospfv3 graceful-restart-information command to check the reason that the local switch functions as the GR helper and check the current GR status.
  2. Perform the following operations as required:

    • If the active/standby switchover is performed manually or the OSPFv3 process is restarted in GR mode, go to Step 4.

    • If this trap is generated without any manual operation, go to Step 3.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.12 hwOspfv3NssaTranslatorStatusChange

Description

OSPFV3/3/NSSATRNSLTRSTSCHNG:OID [oid] The status of the NSSA translator has changed. (AreaId=[integer], RouterId=[gauge], State=[integer])

The translator role in the NSSA changed. A possible cause is that the status of the translator changed among Enabled, Elected, and Disabled.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.12 Minor processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

AreaId

Indicates the OSPFv3 area ID, which is a decimal integer.

RouterId

Indicates the router ID of the local device, which is a decimal integer.

State

Indicates the new status of the translator in the NSSA:
  • 1: enabled
  • 2: elected
  • 3: disabled

Impact on the System

ASE routes may flap for a short period in the following situations. The translator role of the NSSA ABR changes; Type 5 LSAs translated from Type 7 LSAs need to be flushed; or a new translator is translating Type 7 LSAs to Type 5 LSAs. In addition, the translator role changes without manual configuration mostly because the topology in the backbone area or the NSSA changes.

Possible Causes

1. The parameter translator-always in the nssa command was manually configured or canceled on an ABR in the NSSA.

2. A new router ID was configured on an ABR in the NSSA and took effect.

3. A new switch joined the NSSA or a switch exited from the NSSA.

4. The OSPFv3 protocol was restarted or the master/slave switchover was performed on a switch in the backbone area or the NSSA. This resulted in topology instability in the NSSA.

5. The nssa command was manually configured or the parameters in the nssa command were manually modified, which caused the topology of the backbone area or the NSSA changes. For example, configuring or canceling the parameter no-summary or no-import-route in the nssa command will lead to the reestablishment of neighbor relationships between the local switch and a switch in the backbone area, and between the local switch and a switch in the NSSA.

6. The role of the local switch changed to an ABR or changed from an ABR to another role.

7. The topology of the backbone area or the NSSA changed. As a result, the local switch cannot reach another ABR with a greater router ID or with the parameter translator-always from the backbone area or the NSSA.

Procedure

  1. If the nssa translator-always command is configured or canceled manually on the local switch, run the display ospfv3 area command to check whether the translator role of the local switch in the NSSA is correct.

    • If the nssa translator-always command is configured, run the display ospfv3 area command to check whether the status of the NSSA translator is always. If so, go to Step 8. If not, go to Step 7.

    • If the configuration of the nssa translator-always command is canceled, run the display ospfv3 area command to check the status of the NSSA translator. If the status is disabled, go to Step 2. If the status is elected, go to Step 8.

  2. A possible cause is that the nssa translator-always command is configured on an ABR in the NSSA. You can run the display ospfv3 lsdb routercommand to check whether the Router-LSA of a specific ABR in the NSSA carries the N bit. Alternatively, you can check whether the nssa translator-always is configured on other ABRs.

    • If the Router-LSA of a specific ABR carries the N bit or other ABRs are configured with the nssa translator-always command, go to Step 8.

    • If the Router-LSA of a specific ABR does not carry the N bit or other ABRs are not configured with the nssa translator-always command, go to Step 3.

  3. If a new router ID is configured on the local switch and already takes effect, after the topology in the area becomes stable, check whether the translator role of the local switch in the NSSA is correct.

    • If so, go to Step 8.

    • If not, go to Step 4.

  4. A possible cause is that a new router ID is configured on another ABR in the NSSA. In this case, check the configurations of other ABRs.

    • If the router ID of a specific ABR is changed, after the topology of the NSSA becomes stable, check whether the newly configured router ID is greater than the local router ID.
      • If so, go to Step 8.

      • If not, go to Step 5.

    • If the router ID of a specific ABR remains unchanged, go to Step 5.

  5. If a new switch joins the NSSA, do as follows as required:

    • If an ABR joins the NSSA, after the topology in the NSSA becomes stable, check whether the router ID of the ABR is greater than the local router ID.
      • If so, go to Step 8.

      • If not, go to Step 6.

    • If a non-ABR joins the NSSA, go to Step 6.

  6. Check whether the local switch and the neighboring switch have traps 1.3.6.1.2.1.14.16.2.1, 1.3.6.1.2.1.14.16.2.2, 1.3.6.1.2.1.14.16.2.3, and 1.3.6.1.2.1.14.16.2.16.

    • If the preceding traps are generated, refer to the related fault location procedure.
    • If the preceding traps are not generated, go to Step 7.

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

Related Information

None

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.13 hwOspfv3LastAuthKeyExpiry

Description

OSPFV3/2/LASTAUTHKEYEXPIRY:OID [oid] The last authentication key in keychain has expired. (RouterId=[gauge], IfName=[octet])

The last active key ID in the keychain expired.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.13 Major processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

RouterId

Local router ID with its value as a decimal integer

IfName

Interface name

Impact on the System

The system may be attacked by invalid packets.

Possible Causes

The last active key ID in the keychain expired.

Procedure

  1. Run the display keychain keychain-name [ key-id key-id ] command to check the keychain configuration.

    • If the last active key ID in the keychain expired, go to Step 2.
    • If there are still active key IDs in the keychain, go to Step 3.

  2. Check the Timer Mode field in the keychain configuration.

    • If the value of the Timer Mode field is Periodic, the system automatically prolongs the active period of the key ID.
    • If the value of the Timer Mode field is Absolute, you need to run the keychain command to configure a new keychain.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.14 hwOspfv3AuthSequenceNumWrap

Description

OSPFV3/2/AUTHSEQUENCENUMWRAP:OID [oid] The cryptographic sequence number has wrapped. (RouterId=[gauge], IfName=[octet])

The higher order and lower order values of the 64-bit sequence number were misplaced.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.14 Major processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

RouterId

Local router ID with its value as a decimal integer

IfName

Interface name

Impact on the System

The device is open to potential attacks.

Possible Causes

The device has been running for a long time.

Procedure

  1. Run the display ospfv3 interface command to view the sequence number of the sent packet by checking Higher Order Sequence Number and Lower Order Sequence Number and run the display ospfv3 peer command to view the sequence number of the received packet by checking Received Higher Order Sequence Number and Received Lower Order Sequence Number. Then, check whether the sequence numbers of the sent and received packets are the same.
  2. Collect alarm information and configuration information, and then contact technical support personnel.
  3. End.

Related Information

None

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.15 hwOspfv3IntraAreaRouterIdConflictRecovered

Description

OSPFV3/2/ROUTERID_CONFLICT_RECOVER: OID [oid] Router IDs confliction is recovered. (ProcessId=[integer], AreaId=[integer], OldRouterId=[gauge], NewRouterId=[gauge])

The system automatically changed the router ID after detecting a router ID conflict in an OSPFv3 area.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.15 Major communicationsAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

ProcessId

Process ID

AreaId

Area ID

OldRouterId

Old router ID

NewRouterId

New router ID

Impact on the System

The alarm indicates that the router ID conflict has been resolved, and the system will not be affected.

Possible Causes

Two or more indirectly connected routers shared the same router ID within one OSPFv3 area. This router ID conflict caused frequent router LSA refreshment and route flapping. When detecting this conflict, the system automatically changed a router ID to resolve the problem.

Procedure

  • This alarm message is informational only, and no action is required.

Related Information

None

OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.16 hwOspfv3PeerFlappingSuppressStatusChange

Description

OSPFV3/2/NBRDAMP_SUPPRESS: OID [oid] The status of peer flapping suppress is changed.(ProcessId=[integer], RouterId=[integer], AreaId=[integer], ifName=[octet], SuppressStatus=[integer], SuppressReason=[integer])

The status of OSPFv3 neighbor relationship flapping suppression changed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.147.0.16 Major communicationsAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

ProcessId

Process ID

RouterId

Router ID

AreaId

Area ID

ifName

Interface name

SuppressStatus

Suppression status

SuppressReason

Suppression causes are as follows:

  • 1: The interval between two successive neighbor status changes from Full to a non-Full state was longer than the resume interval.
  • 2: A configuration was changed. For example, the OSPFv3 process was reset.
  • 3: An interface was forced to exit from OSPFv3 neighbor relationship flapping suppression using the reset ospfv3 suppress-flapping peer command.
  • 4: The OSPFv3 neighbor relationship flapped frequently.
  • 5: OSPFv3 neighbor relationship flapping suppression exited from Hold-down mode and began to work in Hold-max-cost mode.

Impact on the System

Services may be interrupted if OSPFv3 neighbor relationship flapping suppression persists on the interface.

Possible Causes

OSPFv3 neighbor relationship flapping suppression started, or the interface exited from the suppression.

Procedure

  1. Run the display interface command multiple times to check whether interface flapping frequently occurs.

    • If frequent interface flapping occurs, this trap message is informational only and no action is required.
    • If no frequent interface flapping occurs, go to Step 2.

  2. Run the reset ospfv3 process-id suppress-flapping peer [ interface-type interface-number ] [ notify-peer ] command to force the interface to exit from OSPFv3 neighbor relationship flapping suppression.
  3. End.

Related Information

None

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 3541

Downloads: 2

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