Contents

OSPF-TRAP-MIB· 1

About this MIB· 1

MIB file name· 1

Notifications· 1

ospfVirtIfStateChange· 1

ospfNbrStateChange· 2

ospfVirtNbrStateChange· 4

ospfIfConfigError 6

ospfVirtIfConfigError 7

ospfIfAuthFailure· 9

ospfVirtIfAuthFailure· 10

ospfIfRxBadPacket 12

ospfVirtIfRxBadPacket 13

ospfTxRetransmit 14

ospfVirtIfTxRetransmit 15

ospfOriginateLsa· 17

ospfMaxAgeLsa· 18

ospfLsdbOverflow· 20

ospfLsdbApproachingOverflow· 21

ospfIfStateChange· 22

ospfNssaTranslatorStatusChange· 23

ospfRestartStatusChange· 25

ospfNbrRestartHelperStatusChange· 26

ospfVirtNbrRestartHelperStatusChange· 27

 

 

OSPF-TRAP-MIB

About this MIB

Use this MIB to set, edit, and view OSPF protocol and notification information about network devices.

MIB file name

rfc4750-ospf-trap.mib

Notifications

ospfVirtIfStateChange

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.1	Virtual interface state changes.	Informational	Informational	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the state of a virtual interface changes. This issue occurs when one of the following conditions exists:

The state of a virtual interface changes from P2P to Down, or from Down to P2P.

The router ID of a virtual link neighbor changes.

System impact

If the state of a virtual interface changes from Down to P2P, it has no negative impact on services.

If the state of a virtual interface changes from P2P to Down, the virtual interface will be disconnected and OSPF route calculation will fail. Services might be interrupted.

Status control

ON

CLI: Use the snmp-agent trap enable ospf virtif-state-change command.

OFF

CLI: Use the undo snmp-agent trap enable ospf virtif-state-change command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.9.1.1 (ospfVirtIfAreaId)	ID of the area to which the virtual link belongs.	ospfVirtIfAreaId ospfVirtIfNeighbor	AreaID	IpAddress
1.3.6.1.2.1.14.9.1.2 (ospfVirtIfNeighbor)	Router ID of the virtual neighbor.	ospfVirtIfAreaId ospfVirtIfNeighbor	RouterID	IpAddress
1.3.6.1.2.1.14.9.1.7 (ospfVirtIfState)	Virtual interface state.	ospfVirtIfAreaId ospfVirtIfNeighbor	INTEGER	down (1), pointToPoint (4)

 

Recommended action

To resolve this issue:

1.Use the display ospf vlink command to view the state of the virtual interface.

  - If the state of the virtual interface changes from Down to P2P, no action is required.

  - If the state of the virtual interface changes from P2P to Down, proceed to step 2.

2.Use the display ospf spf-tree command to identify whether the flags of the SPF node corresponding to the neighbor router ID of the virtual interface include the S flag. The flag indicates that the neighbor is reachable.

  - If yes, check whether the virtual interface settings are configured correctly on both the local end and the remote end.

  - If no, check for the cause of the unreachability.

3.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

ospfNbrStateChange

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.2	Neighbor state changes.	Informational	Informational	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the state of a neighbor changes. This issue occurs when one of the following conditions exists:

The state of a neighbor changes from Attempt or any other state to 1-Way or Down, or from Down or any other state to 2-Way or Full.

The local and remote ends have different interface settings (such as the hello timer, dead timer, and authentication settings).

OSPF is restarted by the reset ospf process command.

The state of a neighbor in an NBMA or broadcast network changes from Full to another state or changes from another state to Full.

System impact

The process of OSPF neighbor establishment involves a series of neighbor state changes, including Down, Attempt, Init, 2-Way, ExStart, Exchange, Loading, and Full.

If the state of a neighbor progresses, it has no negative impact on services.

If the state of a neighbor regresses, services might be interrupted.

Status control

ON

CLI: Use the snmp-agent trap enable ospf neighbor-state-change command.

OFF

CLI: Use the undo snmp-agent trap enable ospf neighbor-state-change command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.10.1.1 (ospfNbrIpAddr)	IP address of the neighbor.	ospfNbrIpAddr ospfNbrAddressLessIndex	IpAddress	Standard MIB values.
1.3.6.1.2.1.14.10.1.2 (ospfNbrAddressLessIndex)	Set to 0 on an interface having an IP address, and set to the value of interface index in the Internet Standard MIB on an interface having no IP address.	ospfNbrIpAddr ospfNbrAddressLessIndex	InterfaceIndexOrZero	Integer32 (0..2147483647)
1.3.6.1.2.1.14.10.1.3 (ospfNbrRtrId)	Router ID of the neighbor.	ospfNbrIpAddr ospfNbrAddressLessIndex	RouterID	IpAddress
1.3.6.1.2.1.14.10.1.6 (ospfNbrState)	Neighbor state.	ospfNbrIpAddr ospfNbrAddressLessIndex	INTEGER	down (1), attempt (2), init (3), twoWay (4), exchangeStart (5), exchange (6), loading (7), full (8)
1.3.6.1.2.1.31.1.1.1.1 (ifName)	Interface name	ifIndex	DisplayString	OCTET STRING (0..255)

 

Recommended action

To resolve this issue:

1.Use the display ospf peer command to view the state of the neighbor. You can view the State field in the command output.

  - If the neighbor state is Full, no action is required.

  - If the neighbor state is not Full, proceed to step 2.

2.Use the display interface interface-type interface-number command to view the state of the neighbor-facing interface on the local end.

  - If the interface is up, proceed to step 3.

  - If the neighbor interface is down, check whether the shutdown command is executed on the interface.

If yes, execute the undo shutdown command on the interface, and then proceed to step 3.

If no, proceed to step 3.

3.Use the ping command to identify whether the IP address of the remote interface is reachable.

  - If yes, proceed to step 4.

  - If no, proceed to step 6.

4.Use the display ospf interface command to view the state of the OSPF interface. You can view the State field in the command output.

  - If the neighbor-facing interface is down, proceed to step 6.

  - If the neighbor-facing interface is not down, proceed to step 5.

5.Use the display ospf interface verbose command to check whether the local and remote ends use the same interface settings, including the hello timer, dead timer, poll timer, OSPFv3 network type, and authentication settings.

  - If yes, proceed to step 6.

  - If no, use the following commands to modify inconsistent interface settings and make sure that the local and remote ends use the same interface settings.

ospf timer hello

ospf timer dead

ospf timer poll

ospf network-type

ospf authentication-mode

6.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

ospfVirtNbrStateChange

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.3	Virtual neighbor state changes.	Informational	Informational	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the state of a virtual neighbor changes. This issue occurs when one of the following conditions exists:

The state of a virtual neighbor regresses (for example, changing from Attempt or Full to 1-Way or Down) or progresses to the final state (for example, Full).

The state of the physical interface on which the virtual link is established changes.

The local and remote ends have different interface settings (such as the hello timer, dead timer, and authentication settings).

OSPF is restarted by the reset ospf process command.

System impact

If the state of a neighbor progresses, it has no negative impact on services.

If the state of a neighbor regresses, services might be interrupted.

Status control

ON

CLI: Use the snmp-agent trap enable ospf virtneighbor-state-change command.

OFF

CLI: Use the undo snmp-agent trap enable ospf virtneighbor-state-change command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.11.1.1 (ospfVirtNbrArea)	ID of the area to which the virtual neighbor belongs.	ospfVirtNbrArea ospfVirtNbrRtrId	AreaID	IpAddress
1.3.6.1.2.1.14.11.1.2 (ospfVirtNbrRtrId)	A 32-bit integer that uniquely identifies the neighboring router in the AS.	ospfVirtNbrArea ospfVirtNbrRtrId	RouterID	IpAddress
1.3.6.1.2.1.14.11.1.5 (ospfVirtNbrState)	Neighbor state.	ospfVirtNbrArea ospfVirtNbrRtrId	INTEGER	down (1), attempt (2), init (3), twoWay (4), exchangeStart (5), exchange (6), loading (7), full (8)

 

Recommended action

To resolve this issue:

1.Use the display ospf interface and display ip interface brief commands to view the state of the physical interface on which the virtual link is established.

  - If the physical state of the interface is down, check whether the interface has been shut down.

If yes, execute the undo shutdown command on the interface, and then proceed to step 2.

If no, proceed to step 2.

  - If the link layer protocol state of the interface is down, check whether the interface has been configured with an IP address.

If yes, proceed to step 2.

If no, use the ip address command to configure an IP address for the interface.

2.Use the display ospf peer command to view the state of the neighbor.

  - If the State field displays Full, proceed to step 3.

  - If the State field does not display Full, proceed to step 5.

3.Use the display ospf spf-tree command to whether the flags of the SPF node corresponding to the neighbor router ID of the virtual interface include the S flag. This flag indicates that the neighbor is reachable.

  - If yes, proceed to step 4.

  - If no, proceed to step 5.

4.Use the display ospf vlink and display current-configuration configuration ospf commands to identify whether the local and remote ends use the same settings, such as the hello timer, dead timer, and poll timer.

  - If yes, proceed to step 5.

  - If no, use the vlink-peer command to configure the same settings for both the local and remote ends, and then check whether the notification is cleared.

If yes, the troubleshooting is complete.

If no, proceed to step 5.

5.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

ospfIfConfigError

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.4	Interface configuration error.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated when an interface on a router receives a packet from another router with mismatched configuration. The optionMismatch event causes a notification only if it prevents an adjacency from establishing.

This issue occurs when one of the following conditions exists:

The local interface and the remote interface use different interface settings.

On a broadcast or NBMA network, the IP addresses of the local interface and the remote interface use different masks.

MTU check is enabled and the MTUs of the local interface and the remote interface are different.

A router ID conflict exists.

System impact

This issue typically has no impact on services as long as you reconfigure the local interface and the remote interface correctly.

Status control

ON

CLI: Use the snmp-agent trap enable ospf config-error command.

OFF

CLI: Use the undo snmp-agent trap enable ospf config-error command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.7.1.1 (ospfIfIpAddress)	IP address of the interface.	ospfIfIpAddress ospfAddressLessIf	IpAddress	Standard MIB values.
1.3.6.1.2.1.14.7.1.2 (ospfAddressLessIf)	Used to distinguish interface instances with addresses configured and those without addresses configured.	ospfIfIpAddress ospfAddressLessIf	InterfaceIndexOrZero	Integer32 (0..2147483647)
1.3.6.1.2.1.14.16.1.4 (ospfPacketSrc)	IP address that cannot be identified by a neighbor.	N/A	IpAddress	Standard MIB values.
1.3.6.1.2.1.14.16.1.2 (ospfConfigErrorType)	Configuration error type.	N/A	INTEGER	badVersion (1), areaMismatch (2), unknownNbmaNbr (3), unknownVirtualNbr (4), authTypeMismatch(5), authFailure (6), netMaskMismatch (7), helloIntervalMismatch (8), deadIntervalMismatch (9), optionMismatch (10), mtuMismatch (11), duplicateRouterId (12), noError (13)
1.3.6.1.2.1.14.16.1.3 (ospfPacketType)	OSPF packet type.	N/A	INTEGER	hello (1), dbDescript (2), lsReq (3), lsUpdate (4), lsAck (5), nullPacket (6)

 

Recommended action

To resolve this issue:

1.Use the display ospf interface interface-type interface-number command to identify whether the local OSPF interface and the remote OSPF interface use the same settings.

  - If yes, proceed to step 3.

  - If no, proceed to step 2.

2.Perform the following tasks to clear the notification:

Use the following commands to reconfigure the local or remote OSPFv3 interface, ensuring that the two interfaces use the same settings:

ospf timer hello

ospf timer dead

ospf timer poll

Identify whether the notification is cleared:

If yes, the troubleshooting is complete.

If no, proceed to step 3.

3.If the issue persists, collect alarm information and configuration data, and then contact H3C Support.

ospfVirtIfConfigError

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.5	Virtual interface configuration error.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated when an OSPF virtual interface on a router receives a packet from another router with mismatched configuration. The optionMismatch event causes a notification only if it prevents establishment of an adjacency.

This issue occurs when the interface settings on the ends of a virtual link are not the same.

System impact

This issue typically has no negative impact on services as long as the local interface and the remote interface use the same settings after configuration correction.

Status control

ON

CLI: Use the snmp-agent trap enable ospf virt-config-error command.

OFF

CLI: Use the undo snmp-agent trap enable ospf virt-config-error command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.9.1.1 (ospfVirtIfAreaId)	ID of the area to which the virtual link belongs.	ospfVirtIfAreaId ospfVirtIfNeighbor	AreaID	IpAddress
1.3.6.1.2.1.14.9.1.2 (ospfVirtIfNeighbor)	Router ID of the virtual neighbor.	ospfVirtIfAreaId ospfVirtIfNeighbor	RouterID	IpAddress
1.3.6.1.2.1.14.16.1.2 (ospfConfigErrorType)	Configuration error type.	N/A	INTEGER	badVersion (1), areaMismatch (2), unknownNbmaNbr (3), unknownVirtualNbr (4), authTypeMismatch(5), authFailure (6), netMaskMismatch (7), helloIntervalMismatch (8), deadIntervalMismatch (9), optionMismatch (10), mtuMismatch (11), duplicateRouterId (12), noError (13)
1.3.6.1.2.1.14.16.1.3 (ospfPacketType)	OSPF packet type.	N/A	INTEGER	hello (1), dbDescript (2), lsReq (3), lsUpdate (4), lsAck (5), nullPacket (6)

 

Recommended action

To resolve this issue:

1.Use the display ospf vlink and display current-configuration configuration ospf commands to identify whether the two ends of the virtual link use the same interface settings.

  - If yes, proceed to step 3.

  - If no, proceed to step 2.

2.Use the vlink-peer command to reconfigure an end of the virtual link, ensuring that the two ends of the virtual link use the same settings. Then, identify whether the notification is cleared:

  - If yes, the troubleshooting is complete.

  - If no, proceed to step 3.

3.If the issue persists, collect alarm information and configuration data, and then contact H3C Support.

ospfIfAuthFailure

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.6	Interface authentication failure.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated when OSPF interface authentication fails. This issue occurs if an OSPF interface on a router receives a packet from another router with mismatched authentication settings.

System impact

This issue typically has no negative impact on services as long as you reconfigure the same authentication settings for interfaces on both ends.

Status control

ON

CLI: Use the snmp-agent trap enable ospf authentication-failure command.

OFF

CLI: Use the undo snmp-agent trap enable ospf authentication-failure command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.7.1.1 (ospfIfIpAddress)	IP address of the interface.	ospfIfIpAddress ospfAddressLessIf	IpAddress	Standard MIB values.
1.3.6.1.2.1.14.7.1.2 (ospfAddressLessIf)	Used to distinguish interface instances with addresses configured and those without addresses configured.	ospfIfIpAddress ospfAddressLessIf	InterfaceIndexOrZero	Integer32 (0..2147483647)
1.3.6.1.2.1.14.16.1.4 (ospfPacketSrc)	IP address that cannot be identified by a neighbor instance.	N/A	IpAddress	Standard MIB values.
1.3.6.1.2.1.14.16.1.2 (ospfConfigErrorType)	Configuration error type.	N/A	INTEGER	badVersion (1), areaMismatch (2), unknownNbmaNbr (3), unknownVirtualNbr (4), authTypeMismatch(5), authFailure (6), netMaskMismatch (7), helloIntervalMismatch (8), deadIntervalMismatch (9), optionMismatch (10), mtuMismatch (11), duplicateRouterId (12), noError (13)
1.3.6.1.2.1.14.16.1.3 (ospfPacketType)	OSPF packet type.	N/A	INTEGER	hello (1), dbDescript (2), lsReq (3), lsUpdate (4), lsAck (5), nullPacket (6)

 

Recommended action

To resolve this issue:

1.Use the display current-configuration configuration ospf command to identify whether the local end and the remote end use the same area authentication settings.

2.Use the display current-configuration interface interface-type interface-number command to identify whether the local interface and the remote interface use the same interface authentication settings. The comparison result of interface-level authentication settings takes precedence over that of area-level authentication settings.

  - If yes, proceed to step 3.

  - If no, proceed to step 2.

3.Perform the following tasks to clear the notification:

Use the ospf authentication-mode command to reconfigure the interface authentication settings on the local or remote interface, ensuring that the two interfaces use the same settings.

Use the authentication-mode command to reconfigure the area authentication settings for the local or remote device, ensuring that the two devices use the same settings.

Identify whether the notification is cleared:

If yes, the troubleshooting is complete.

If no, proceed to step 3.

4.If the issue persists, collect alarm information and configuration data, and then contact H3C Support.

ospfVirtIfAuthFailure

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.7	Virtual interface authentication failure.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated when OSPF virtual interface authentication fails. This issue occurs when an OSPF virtual interface on a router receives a packet from another router with mismatched authentication settings.

System impact

This issue typically has no negative impact on services as long as you reconfigure the same authentication settings for virtual interfaces on both ends.

Status control

ON

CLI: Use the snmp-agent trap enable ospf virt-authentication-failure command.

OFF

CLI: Use the undo snmp-agent trap enable ospf virt-authentication-failure command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.9.1.1 (ospfVirtIfAreaId)	ID of the area to which the virtual link belongs.	ospfVirtIfAreaId ospfVirtIfNeighbor	AreaID	IpAddress
1.3.6.1.2.1.14.9.1.2 (ospfVirtIfNeighbor)	Router ID of the virtual neighbor.	ospfVirtIfAreaId ospfVirtIfNeighbor	RouterID	IpAddress
1.3.6.1.2.1.14.16.1.2 (ospfConfigErrorType)	Configuration error type.	N/A	INTEGER	badVersion (1), areaMismatch (2), unknownNbmaNbr (3), unknownVirtualNbr (4), authTypeMismatch(5), authFailure (6), netMaskMismatch (7), helloIntervalMismatch (8), deadIntervalMismatch (9), optionMismatch (10), mtuMismatch (11), duplicateRouterId (12), noError (13)
1.3.6.1.2.1.14.16.1.3 (ospfPacketType)	OSPF packet type.	N/A	INTEGER	hello (1), dbDescript (2), lsReq (3), lsUpdate (4), lsAck (5), nullPacket (6)

 

Recommended action

To resolve this issue:

1.Use the display current-configuration configuration ospf command to identify whether the local end and the remote end use the same virtual link authentication settings and the same backbone area authentication settings. The comparison result of virtual link authentication settings takes precedence over that of backbone area authentication settings.

  - If yes, proceed to step 3.

  - If no, proceed to step 2.

2.Perform the following tasks to clear the notification:

Use the vlink-peer command to reconfigure the virtual link authentication settings for the local or remote device, ensuring that the two devices use the same settings.

Use the authentication-mode command to reconfigure the backbone area authentication settings for the local or remote device, ensuring that the two devices use the same settings.

Identify whether the notification is cleared:

If yes, the troubleshooting is complete.

If no, proceed to step 3.

3.If the issue persists, collect alarm information and configuration data, and then contact H3C Support.

ospfIfRxBadPacket

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.8	An interface receives an error packet.	Informational	Informational	N/A (N/A)	ON

 

Notification triggers

This notification is generated when an interface receives an OSPF packet that cannot be parsed. This issue occurs when one of the following conditions exists:

The length of the OSPF packet is incorrect.

The OSPF packet has content errors.

System impact

When a normal interface receives an OSPF packet that cannot be parsed, it discards the packet. If the packet is a hello packet, the neighbor that sends the packet might go down.

Status control

ON

CLI: Use the snmp-agent trap enable ospf bad-packet command.

OFF

CLI: Use the undo snmp-agent trap enable ospf bad-packet command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.7.1.1 (ospfIfIpAddress)	IP address of the interface.	ospfIfIpAddress ospfAddressLessIf	IpAddress	Standard MIB values.
1.3.6.1.2.1.14.7.1.2 (ospfAddressLessIf)	Used to distinguish interface instances with addresses configured and those without addresses configured.	ospfIfIpAddress ospfAddressLessIf	InterfaceIndexOrZero	Integer32 (0..2147483647)
1.3.6.1.2.1.14.16.1.4 (ospfPacketSrc)	IP address that cannot be identified by a neighbor.	N/A	IpAddress	Standard MIB values.
1.3.6.1.2.1.14.16.1.3 (ospfPacketType)	OSPF packet type.	N/A	INTEGER	hello (1), dbDescript (2), lsReq (3), lsUpdate (4), lsAck (5), nullPacket (6)

 

Recommended action

Collect alarm information and configuration data, and then contact H3C Support for help.

ospfVirtIfRxBadPacket

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.9	A virtual interface receives an error packet.	Informational	Informational	N/A (N/A)	ON

 

Notification triggers

This notification is generated when a virtual interface receives an OSPF packet that cannot be parsed. This issue occurs when one of the following conditions exists:

The length of the OSPF packet is incorrect.

The OSPF packet has content errors.

System impact

When a virtual interface receives an OSPF packet that cannot be parsed, it discards the packet. If the packet is a hello packet, the neighbor that sends the packet might go down.

Status control

ON

CLI: Use the snmp-agent trap enable ospf virt-bad-packet command.

OFF

CLI: Use the undo snmp-agent trap enable ospf virt-bad-packet command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.9.1.1 (ospfVirtIfAreaId)	ID of the area to which the virtual link belongs.	ospfVirtIfAreaId ospfVirtIfNeighbor	AreaID	IpAddress
1.3.6.1.2.1.14.9.1.2 (ospfVirtIfNeighbor)	Router ID of the virtual neighbor.	ospfVirtIfAreaId ospfVirtIfNeighbor	RouterID	IpAddress
1.3.6.1.2.1.14.16.1.3 (ospfPacketType)	OSPF packet type.	N/A	INTEGER	hello (1), dbDescript (2), lsReq (3), lsUpdate (4), lsAck (5), nullPacket (6)

 

Recommended action

Collect alarm information and configuration data, and then contact H3C Support for help.

ospfTxRetransmit

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.10	An interface retransmits an OSPF packet.	Informational	Informational	N/A (N/A)	ON

 

Notification triggers

This notification is generated when an interface retransmits an OSPF packet. All packets that might be retransmitted are associated with an LSDB entry, which is identified by the LS type, LS ID, and Router ID.

This issue occurs when one of the following conditions exists:

The neighbor considers packets from the local device illegal.

The neighbor is not reachable

System impact

This notification is generated typically due to heavy traffic load. Route synchronization and convergence might slow down.

Status control

ON

CLI: Use the snmp-agent trap enable ospf retransmit command.

OFF

CLI: Use the undo snmp-agent trap enable ospf retransmit command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.7.1.1 (ospfIfIpAddress)	IP address of the interface.	ospfIfIpAddress ospfAddressLessIf	IpAddress	Standard MIB values.
1.3.6.1.2.1.14.7.1.2 (ospfAddressLessIf)	Used to distinguish interface instances with addresses configured and those without addresses configured.	ospfIfIpAddress ospfAddressLessIf	InterfaceIndexOrZero	Integer32 (0..2147483647)
1.3.6.1.2.1.14.10.1.3 (ospfNbrRtrId)	Router ID of the neighbor.	ospfNbrIpAddr ospfNbrAddressLessIndex	RouterID	IpAddress
1.3.6.1.2.1.14.16.1.3 (ospfPacketType)	OSPF packet type.	N/A	INTEGER	hello (1), dbDescript (2), lsReq (3), lsUpdate (4), lsAck (5), nullPacket (6)
1.3.6.1.2.1.14.4.1.2 (ospfLsdbType)	LSA type. Type-5 LSAs are not displayed.	ospfLsdbAreaId ospfLsdbType ospfLsdbLsid ospfLsdbRouterId	INTEGER	routerLink (1), networkLink (2), summaryLink (3), asSummaryLink (4), asExternalLink (5), multicastLink (6), nssaExternalLink (7), areaOpaqueLink (10)
1.3.6.1.2.1.14.4.1.3 (ospfLsdbLsid)	LS ID.	ospfLsdbAreaId ospfLsdbType ospfLsdbLsid ospfLsdbRouterId	IpAddress	Standard MIB values.
1.3.6.1.2.1.14.4.1.4 (ospfLsdbRouterId)	Router ID of the device that generates the LSA.	ospfLsdbAreaId ospfLsdbType ospfLsdbLsid ospfLsdbRouterId	RouterID	IpAddress

 

Recommended action

Collect alarm information and configuration data, and then contact H3C Support for help.

ospfVirtIfTxRetransmit

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.11	A virtual interface retransmits an OSPF packet.	Informational	Informational	N/A (N/A)	ON

 

Notification triggers

This notification is generated when a virtual interface retransmits an OSPF packet. All packets that might be retransmitted are associated with an LSDB entry, which is identified by the LS type, LS ID, and Router ID.

This issue occurs when the neighbor considers packets from the local device illegal.

System impact

This notification is generated typically due to heavy traffic load. Route synchronization and convergence might slow down.

Status control

ON

CLI: Use the snmp-agent trap enable ospf virt-retransmit command.

OFF

CLI: Use the undo snmp-agent trap enable ospf virt-retransmit command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.9.1.1 (ospfVirtIfAreaId)	ID of the area to which the virtual link belongs.	ospfVirtIfAreaId ospfVirtIfNeighbor	AreaID	IpAddress
1.3.6.1.2.1.14.9.1.2 (ospfVirtIfNeighbor)	Router ID of the virtual neighbor.	ospfVirtIfAreaId ospfVirtIfNeighbor	RouterID	IpAddress
1.3.6.1.2.1.14.16.1.3 (ospfPacketType)	OSPF packet type.	N/A	INTEGER	hello (1), dbDescript (2), lsReq (3), lsUpdate (4), lsAck (5), nullPacket (6)
1.3.6.1.2.1.14.4.1.2 (ospfLsdbType)	LSA type. Type-5 LSAs are not displayed.	ospfLsdbAreaId ospfLsdbType ospfLsdbLsid ospfLsdbRouterId	INTEGER	routerLink (1), networkLink (2), summaryLink (3), asSummaryLink (4), asExternalLink (5), multicastLink (6), nssaExternalLink (7), areaOpaqueLink (10)
1.3.6.1.2.1.14.4.1.3 (ospfLsdbLsid)	LS ID	ospfLsdbAreaId ospfLsdbType ospfLsdbLsid ospfLsdbRouterId	IpAddress	Standard MIB values.
1.3.6.1.2.1.14.4.1.4 (ospfLsdbRouterId)	Router ID of the device that generates the LSA.	ospfLsdbAreaId ospfLsdbType ospfLsdbLsid ospfLsdbRouterId	RouterID	IpAddress

 

Recommended action

To resolve this issue:

1.Use the display ospf vlink command on the remote device to view the state of the virtual link.

  - If the virtual interface state or neighbor state is Down, perform the recommended actions for the ospfVirtIfStateChange and ospfVirtNbrStateChange notifications.

  - If the neighbor state is Full, proceed to step 2.

2.Check whether the ospfVirtIfRxBadPacket notification is generated on the local and remote devices.

  - If yes, perform the recommended actions for the ospfVirtIfRxBadPacket notification.

  - If no, proceed to step 3.

3.If the issue persists, collect alarm information and configuration data, and then contact H3C Support.

ospfOriginateLsa

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.12	The local device generates a new LSA.	Informational	Informational	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the local device generates a new LSA. This notification is generated only when an LSA is originated because of a topology change. Flushing of aged LSAs and refreshes of LSAs will not trigger this notification.

This issue occurs when one of the following conditions exists:

An interface comes up or down.

The state of a neighbor changes.

A route redistributed by OSPF changes.

System impact

If the ospfNbrStateChange and ospfIfStateChange notifications are generated together with this notification, services might be affected.

Status control

ON

CLI: Use the snmp-agent trap enable ospf lsa-originate command.

OFF

CLI: Use the undo snmp-agent trap enable ospf lsa-originate command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.4.1.1 (ospfLsdbAreaId)	ID of the area from which the LSA was received.	ospfLsdbAreaId ospfLsdbType ospfLsdbLsid ospfLsdbRouterId	AreaID	IpAddress
1.3.6.1.2.1.14.4.1.2 (ospfLsdbType)	LSA type. Type-5 LSAs are not displayed.	ospfLsdbAreaId ospfLsdbType ospfLsdbLsid ospfLsdbRouterId	INTEGER	routerLink (1), networkLink (2), summaryLink (3), asSummaryLink (4), asExternalLink (5), multicastLink (6), nssaExternalLink (7), areaOpaqueLink (10)
1.3.6.1.2.1.14.4.1.3 (ospfLsdbLsid)	LS ID.	ospfLsdbAreaId ospfLsdbType ospfLsdbLsid ospfLsdbRouterId	IpAddress	Standard MIB values.
1.3.6.1.2.1.14.4.1.4 (ospfLsdbRouterId)	Router ID of the device that generates the LSA.	ospfLsdbAreaId ospfLsdbType ospfLsdbLsid ospfLsdbRouterId	RouterID	IpAddress

 

Recommended action

To resolve this issue:

1.View the 1.3.6.1.2.1.14.4.1.2 (ospfLsdbType) object in the notification to identify the LSA type.

  - If the LSA is a Type-1 or Type-2 LSA, check whether the ospfNbrStateChange or ospfIfStateChange notification is generated.

If yes, perform the recommended actions for the corresponding notification.

If no, proceed to step 2.

  - If the LSA is a Type-3 or Type-7 LSA, proceed to step 2.

2.Use the display ip routing-table link-state-id command to identify whether the routing table has changed.

  - If yes, determine the cause of the change, or proceed to step 3.

  - If no, proceed to step 3.

3.If the issue persists, collect alarm information and configuration data, and then contact H3C Support.

ospfMaxAgeLsa

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.13	An LSA in the LSDB ages.	Informational	Informational	N/A (N/A)	ON

 

Notification triggers

This notification is generated when an LSA in the LSDB ages (becomes a MaxAge LSA). This issue occurs when one of the following conditions exists:

An interface comes up or down.

The state of a neighbor changes.

A route redistributed by OSPF changes.

System impact

This issue might affect route calculation. If the 1.3.6.1.2.1.14.4.1.3 (ospfLsdbLsid) object is in the service network segment, services will be affected.

Status control

ON

CLI: Use the snmp-agent trap enable ospf lsa-maxage command.

OFF

CLI: Use the undo snmp-agent trap enable ospf lsa-maxage command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.4.1.1 (ospfLsdbAreaId)	ID of the area from which the LSA was received.	ospfLsdbAreaId ospfLsdbType ospfLsdbLsid ospfLsdbRouterId	AreaID	IpAddress
1.3.6.1.2.1.14.4.1.2 (ospfLsdbType)	LSA type. Type-5 LSAs are not displayed.	ospfLsdbAreaId ospfLsdbType ospfLsdbLsid ospfLsdbRouterId	INTEGER	routerLink (1), networkLink (2), summaryLink (3), asSummaryLink (4), asExternalLink (5), multicastLink (6), nssaExternalLink (7), areaOpaqueLink (10)
1.3.6.1.2.1.14.4.1.3 (ospfLsdbLsid)	LS ID.	ospfLsdbAreaId ospfLsdbType ospfLsdbLsid ospfLsdbRouterId	IpAddress	Standard MIB values.
1.3.6.1.2.1.14.4.1.4 (ospfLsdbRouterId)	Router ID of the device that generates the LSA.	ospfLsdbAreaId ospfLsdbType ospfLsdbLsid ospfLsdbRouterId	RouterID	IpAddress

 

Recommended action

To resolve this issue:

1.View the 1.3.6.1.2.1.14.4.1.4 (ospfLsdbRouterId) object in the notification to identify whether the LSA is generated by the local device.

  - If yes, proceed to step 2.

  - If no, proceed to step 3.

2.View the 1.3.6.1.2.1.14.4.1.2 (ospfLsdbType) object in the notification to identify the LSA type.

  - If the LSA is a Type-1 or Type-2 LSA, check whether the ospfNbrStateChange or ospfIfStateChange notification is generated.

If yes, perform the recommended actions for the corresponding notification.

If no, proceed to step 3.

  - If the LSA is a Type-3 or Type-7 LSA, use the display ip routing-table link-state-id command to identify whether the routing table has changed.

If yes, determine the cause of the change, or proceed to step 3.

If no, proceed to step 3.

3.If the issue persists, collect alarm information and configuration data, and then contact H3C Support.

ospfLsdbOverflow

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.14	The number of LSAs in the LSDB of a device exceeds the upper limit.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the number of LSAs in the LSDB of a device exceeds the upper limit. This issue occurs when too many Type-5 and Type-7 LSAs exist in the LSDB.

System impact

This issue might cause network flapping if it affects route calculation.

Status control

ON

CLI: Use the snmp-agent trap enable ospf lsdb-overflow command.

OFF

CLI: Use the undo snmp-agent trap enable ospf lsdb-overflow command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.1.11 (ospfExtLsdbLimit)	Maximum number of non-default ASEs in the LSDB. A value of -1 indicates no limit.	N/A	Integer32	-1..'7FFFFFFF'h

 

Recommended action

To resolve this issue:

1.If the upper limit of external LSAs in the LSDB can be changed, use the lsdb-overflow-limit command to increase the value and make sure all OSPF devices use the same value throughout the network. If this notification is still generated after the new upper limit takes effect, proceed to step 2.

If the upper limit of external LSAs in the LSDB cannot be changed, proceed to step 2.

2.If the issue persists, collect alarm information and configuration data, and then contact H3C Support.

ospfLsdbApproachingOverflow

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.15	The number of LSAs in the LSDB of a device reaches 90% the upper limit.	Informational	Warning	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the number of LSAs in the LSDB of a device reaches 90% of the upper limit. This issue occurs when too many Type-5 and Type-7 LSAs exist in the LSDB.

System impact

This issue might cause network flapping if it affects route calculation.

Status control

ON

CLI: Use the snmp-agent trap enable ospf lsdb-approaching-overflow command.

OFF

CLI: Use the undo snmp-agent trap enable ospf lsdb-approaching-overflow command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.1.11 (ospfExtLsdbLimit)	Maximum number of non-default ASEs in the LSDB. A value of -1 indicates no limit.	N/A	Integer32	-1..'7FFFFFFF'h

 

Recommended action

To resolve this issue:

1.Use the display ospf lsdb brief command to identify whether the number of Type-5 and Type-7 LSAs reaches 90% the upper limit set by the lsdb-overflow-limit command.

  - If yes, proceed to step 2.

  - If no, proceed to step 3.

2.If the upper limit of external LSAs in the LSDB can be changed, use the lsdb-overflow-limit command to increase the value and make sure all OSPF devices use the same value throughout the network. If this notification is still generated after the new upper limit takes effect, proceed to step 3.

If the upper limit of external LSAs in the LSDB cannot be changed, proceed to step 3.

3.If the issue persists, collect alarm information and configuration data, and then contact H3C Support.

ospfIfStateChange

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.16	Interface state changes.	Informational	Informational	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the state of an OSPF interface regresses (for example, changing from DR to Down) or progresses to a terminal state (for example, Point-to-Point, DRother, DR, or Backup). This issue occurs when one of the following conditions exists:

The physical interface comes up or goes down.

The router priority for the interface changes and DR/BDR election is performed.

System impact

This issue might affect the state of neighbors. If the state of an OSPF interface regresses (for example, changing to Down), it will be disconnected from its neighbors.

Status control

ON

CLI: Use the snmp-agent trap enable ospf if-state-change command.

OFF

CLI: Use the undo snmp-agent trap enable ospf if-state-change command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.7.1.1 (ospfIfIpAddress)	IP address of the interface.	ospfIfIpAddress ospfAddressLessIf	IpAddress	Standard MIB values.
1.3.6.1.2.1.14.7.1.2 (ospfAddressLessIf)	Used to distinguish interface instances with addresses configured and those without addresses configured.	ospfIfIpAddress ospfAddressLessIf	InterfaceIndexOrZero	Integer32 (0..2147483647)
1.3.6.1.2.1.14.7.1.12 (ospfIfState)	Interface state.	ospfIfIpAddress ospfAddressLessIf	INTEGER	down (1), loopback (2), waiting (3), pointToPoint (4), designatedRouter (5), backupDesignatedRouter (6), otherDesignatedRouter (7)

 

Recommended action

To resolve this issue:

1.Use the display ospf interface command to view the interface state.

  - If the interface state is Down, proceed to step 2.

  - If the interface state is not Down, no action is required.

2.Use the display interface interface-type interface-number command to view the state of the interface.

  - If the interface is up, proceed to step 3.

  - If the interface is not up, check whether the interface has been shut down.

If yes, execute the undo shutdown command on the interface, and then proceed to step 3.

If no, proceed to step 3.

3.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

ospfNssaTranslatorStatusChange

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.17	A router's ability to translate OSPF type-7 LSAs into OSPF type-5 LSAs changes.	Informational	Informational	N/A (N/A)	ON

 

Notification triggers

This notification is generated when a router's ability to translate OSPF type-7 LSAs into OSPF type-5 LSAs changes. This issue occurs when one of the following conditions exists:

The translate-always keyword of the nssa command is configured or canceled on an NSSA ABR.

An NSSA ABR has been configured with a new router ID and the change is already in effect.

The device becomes an ABR or its role changes from ABR to another.

System impact

When the translator in an NSSA area changes, the former translator must flush the Type-5 LSAs translated from Type-7 LSAs and the new translator translates new OSPFv3 type-7 LSAs into OSPFv3 type-5 LSAs. This might cause temporary AES route flapping.

Status control

ON

CLI: Use the snmp-agent trap enable ospf nssatranslator-status-change command.

OFF

CLI: Use the undo snmp-agent trap enable ospf nssatranslator-status-change command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.2.1.1 (ospfAreaId)	Area ID, a 32-bit integer that uniquely identifies an area.	ospfAreaId	AreaID	IpAddress
1.3.6.1.2.1.14.2.1.12 (ospfAreaNssaTranslatorState)	Method for the NSSA ABR to become capable of translating Type-7 LSAs into Type-5 LSAs.	ospfAreaId	INTEGER	enabled (1), elected (2), disabled (3)

 

Recommended action

To resolve this issue:

1.If the nssa translate-always command is configured on the local device, use the display ospf command to identify whether the 7/5 translator state field displays Enabled.

  - If yes, no action is required.

  - If no, proceed to step 7.

If the nssa translate-always command is canceled on the local device, use the display ospf command to identify whether the 7/5 translator state field displays Disabled.

  - If the 7/5 translator state field displays Disabled, proceed to step 2.

  - If the 7/5 translator state field displays Elected, no action is required.

2.Use the display ospf lsdb router command to identify whether the Options field in the router LSA of an NSSA ABR contains the Nt bit.

  - If yes, no action is required.

  - If no, proceed to step 3.

3.If the local device has been configured with a new router ID and the change is already in effect, identify whether the NSSA translator role is correct after the network topology is stable.

  - If yes, no action is required.

  - If no, proceed to step 4.

4.Identify whether other NSSA ABRs have been configured with new router IDs. After the network topology is stable, identify whether one of the new router IDs is larger than the local router ID.

  - If yes, no action is required.

  - If no, proceed to step 5.

5.If a new NSSA ABR has been added in the area, identify whether the router ID of the new NSSA ABR is larger than the local router ID after the network topology is stable,.

  - If yes, no action is required.

  - If no, proceed to step 0.

If the new device is not an ABR, proceed to step 0.

6.Check whether the ospfNbrStateChange or ospfIfStateChange notification is generated on the local and neighbor devices.

  - If yes, perform the recommended actions to clear the notification.

  - If no, proceed to step 7.

7.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

ospfRestartStatusChange

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.18	GR restarter state changes.	Informational	Informational	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the state of the GR restarter changes. This issue occurs when one of the following conditions exists:

The device stops GR.

The device starts GR.

System impact

If the state of the GR restarter changes due to a GR failure, this issue will affect services.

Status control

ON

CLI: Use the snmp-agent trap enable ospf grrestarter-status-change command.

OFF

CLI: Use the undo snmp-agent trap enable ospf grrestarter-status-change command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.1.21 (ospfRestartStatus)	GR restarter state.	N/A	INTEGER	notRestarting (1), plannedRestart (2), unplannedRestart (3)
1.3.6.1.2.1.14.1.19 (ospfRestartInterval)	Graceful restart timeout interval.	N/A	Integer32	1..1800
1.3.6.1.2.1.14.1.23 (ospfRestartExitReason)	Reason why the GR restarter exited.	N/A	INTEGER	none (1), inProgress (2), completed (3), timedOut (4), topologyChanged (5)

 

Recommended action

To resolve this issue:

1.If you are manually performing an active/standby switchover or restarting the OSPF process with GR, no action is required. Otherwise, proceed to step 2.

2.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

ospfNbrRestartHelperStatusChange

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.19	GR helper state changes.	Informational	Informational	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the GR helper state of a neighbor changes. This issue occurs when one of the following conditions exists:

The neighbor becomes the GR helper.

The neighbor stops being the GR helper.

System impact

If the GR helper state of a neighbor changes due to a GR failure, this issue will affect services.

Status control

ON

CLI: Use the snmp-agent trap enable ospf grhelper-status-change command.

OFF

CLI: Use the undo snmp-agent trap enable ospf grhelper-status-change command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.10.1.1 (ospfNbrIpAddr)	IP address of the neighbor.	ospfNbrIpAddr ospfNbrAddressLessIndex	IpAddress	Standard MIB values.
1.3.6.1.2.1.14.10.1.2 (ospfNbrAddressLessIndex)	Set to 0 on an interface having an IP address, and set to the value of interface index in the Internet Standard MIB on an interface having no IP address.	ospfNbrIpAddr ospfNbrAddressLessIndex	InterfaceIndexOrZero	Integer32 (0..2147483647)
1.3.6.1.2.1.14.10.1.3 (ospfNbrRtrId)	Router ID of the neighbor.	ospfNbrIpAddr ospfNbrAddressLessIndex	RouterID	IpAddress
1.3.6.1.2.1.14.10.1.12 (ospfNbrRestartHelperStatus)	GR helper state.	ospfNbrIpAddr ospfNbrAddressLessIndex	INTEGER	notHelping (1), helping (2)
1.3.6.1.2.1.14.10.1.13 (ospfNbrRestartHelperAge)	Remaining time of the GR interval when the router is acting as a GR helper for the neighbor.	ospfNbrIpAddr ospfNbrAddressLessIndex	Unsigned32	Standard MIB values.
1.3.6.1.2.1.14.10.1.14 (ospfNbrRestartHelperExitReason)	Reason why the GR helper exited.	ospfNbrIpAddr ospfNbrAddressLessIndex	INTEGER	none (1), inProgress (2), completed (3), timedOut (4), topologyChanged (5)

 

Recommended action

To resolve this issue:

1.If you are manually performing an active/standby switchover or restarting the OSPF process with GR, no action is required. Otherwise, proceed to step 2.

2.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

ospfVirtNbrRestartHelperStatusChange

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.14.16.2.20	The GR helper state of a virtual neighbor changes.	Informational	Informational	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the GR helper state of a virtual neighbor changes. This issue occurs when one of the following conditions exists:

The virtual neighbor becomes the GR helper.

The virtual neighbor stops being the GR helper.

System impact

If the GR helper state of a virtual neighbor changes due to a GR failure, this issue will affect services.

Status control

ON

CLI: Use the snmp-agent trap enable ospf virtgrhelper-status-change command.

OFF

CLI: Use the undo snmp-agent trap enable ospf virtgrhelper-status-change command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.14.1.1 (ospfRouterId)	Unique identifier of a router in an AS.	N/A	RouterID	IpAddress
1.3.6.1.2.1.14.11.1.1 (ospfVirtNbrArea)	ID of the area to which the virtual neighbor belongs.	ospfVirtNbrArea ospfVirtNbrRtrId	AreaID	IpAddress
1.3.6.1.2.1.14.11.1.2 (ospfVirtNbrRtrId)	A 32-bit integer that uniquely identifies the neighboring router in the AS.	ospfVirtNbrArea ospfVirtNbrRtrId	RouterID	IpAddress
1.3.6.1.2.1.14.11.1.9 (ospfVirtNbrRestartHelperStatus)	Whether the router is acting as a GR helper for the virtual neighbor.	ospfVirtNbrArea ospfVirtNbrRtrId	INTEGER	notHelping (1), helping (2)
1.3.6.1.2.1.14.11.1.10 (ospfVirtNbrRestartHelperAge)	Remaining time of the GR interval when the router is acting as a GR helper for the neighbor.	ospfVirtNbrArea ospfVirtNbrRtrId	Unsigned32	Standard MIB values.
1.3.6.1.2.1.14.11.1.11 (ospfVirtNbrRestartHelperExitReason)	Reason why the GR helper exited.	ospfVirtNbrArea ospfVirtNbrRtrId	INTEGER	none (1), inProgress (2), completed (3), timedOu t 4), topologyChanged (5)

 

Recommended action

To resolve this issue:

1.If you are manually performing an active/standby switchover or restarting the OSPF process with GR, no action is required. Otherwise, proceed to step 2.

2.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.