This notification is generated when the state of a virtual interface changes to Point-to-Point or changes from Point-to-Point to another state. To reduce unnecessary notifications caused by virtual interface up events, no virtual interface state change notification will be sent within 2 times the dead interval since the virtual interface state changes to a value other than DOWN.

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 OSPFV3 route calculation will fail. Services might be interrupted.

Status control

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

OFF

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

Object

OID (object name)

Description

Index

Type

Value range

1.3.6.1.2.1.191.1.1.1

(ospfv3RouterId)

Unique identifier of a router in an AS.

N/A

Ospfv3RouterIdTC

Unsigned32 (1..'FFFFFFFF'h)

1.3.6.1.2.1.191.1.8.1.9 (ospfv3VirtIfState)

Virtual interface state.

ospfv3VirtIfAreaId

ospfv3VirtIfNeighbor

INTEGER

down(1), pointToPoint(4)

Recommended action

To resolve this issue:

1.Use the display ospfv3 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 ospfv3 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. This 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.

ospfv3NbrStateChange

Basic information

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

Notification triggers

For DR and BDR, this notification is generated when the state of a neighbor changes to FULL or changes from FULL to another state. For DRother, this notification is sent when the state of a neighbor changes to 2-way or changes from 2-way to another state.

To reduce unnecessary notifications caused by interface up events, no neighbor state change notification will be sent within 2 times the dead interval since the interface state changes to a value other than DOWN.

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

OSPFv3 is restarted by the reset ospfv3 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 OSPFv3 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

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

OFF

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

Object

OID (object name)

Description

Index

Type

Value range

1.3.6.1.2.1.191.1.1.1

(ospfv3RouterId)

Unique identifier of a router in an AS.

N/A

Ospfv3RouterIdTC

Unsigned32 (1..'FFFFFFFF'h)

1.3.6.1.2.1.191.1.9.1.8 (ospfv3NbrState)

Neighbor state.

ospfv3NbrIfIndex

ospfv3NbrIfInstId

ospfv3NbrRtrId

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 ospfv3 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 IPv6 address of the remote interface is reachable.

- If yes, proceed to step 4.

- If no, proceed to step 6.

4.Use the display ospfv3 interface command to view the state of the OSPFv3 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 ospfv3 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.

ospfv3 timer hello

ospfv3 timer dead

ospfv3 timer poll

ospfv3 network-type

ospfv3 authentication-mode

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

ospfv3VirtNbrStateChange

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.191.0.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 to FULL or changes from FULL to another state. To reduce unnecessary notifications caused by virtual interface up events, no virtual neighbor state change notification will be sent within 2 times the dead interval since the virtual interface state changes to a value other than DOWN.

This issue occurs when one of the following conditions exists:

The state of a virtual neighbor regresses (for example, changing from 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).

OSPFv3 is restarted by the reset ospfv3 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

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

OFF

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

Object

OID (object name)

Description

Index

Type

Value range

1.3.6.1.2.1.191.1.1.1

(ospfv3RouterId)

Unique identifier of a router in an AS.

N/A

Ospfv3RouterIdTC

Unsigned32 (1..'FFFFFFFF'h)

1.3.6.1.2.1.191.1.11.1.8 (ospfv3VirtNbrState)

Virtual neighbor state.

ospfv3VirtNbrArea

ospfv3VirtNbrRtrId

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 ospfv3 interface and display ipv6 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 Up, proceed to step 2.

2.Use the display ospfv3 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 ospfv3 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. This flag indicates that the neighbor is reachable.

- If yes, proceed to step 4.

- If no, proceed to step 5.

4.Use the display ospfv3 vlink and display current-configuration configuration ospfv3 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.

ospfv3IfConfigError

Basic information

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

Notification triggers

This notification is generated when a non-virtual interface receives a packet from another router with mismatched configuration. This issue occurs when one of the following conditions exists:

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

The link layer protocol changes.

System impact

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

Status control

CLI: Use the snmp-agent trap enable ospfv3 if-cfg-error command.

OFF

CLI: Use the undo snmp-agent trap enable ospfv3 if-cfg-error command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.191.1.1.1 (ospfv3RouterId)	Unique identifier of a router in an AS.	N/A	Ospfv3RouterIdTC	Unsigned32 (1..'FFFFFFFF'h)
1.3.6.1.2.1.191.1.7.1.12 (ospfv3IfState)	Interface state.	ospfv3IfIndex ospfv3IfInstId	INTEGER	down(1), loopback(2), waiting(3), pointToPoint(4), designatedRouter(5), backupDesignatedRouter(6), otherDesignatedRouter(7), standby(8)
1.3.6.1.2.1.191.1.14.3 (ospfv3PacketSrc)	IPv6 packet that cannot be identified by a neighbor.	N/A	InetAddressIPv6	OCTET STRING (16)
1.3.6.1.2.1.191.1.14.1 (ospfv3ConfigErrorType)	OSPFv3 configuration error type.	N/A	INTEGER	badVersion(1), areaMismatch(2), unknownNbmaNbr(3), unknownVirtualNbr(4), helloIntervalMismatch(5), deadIntervalMismatch(6), optionMismatch(7), mtuMismatch(8), duplicateRouterId(9), noError(10)
1.3.6.1.2.1.191.1.14.2 (ospfv3PacketType)	OSPFv3 data packet type.	N/A	INTEGER	hello(1), dbDescript(2), lsReq(3), lsUpdate(4), lsAck(5), nullPacket(6)

Recommended action

1.Use the display ospfv3 interface interface-type interface-number command to identify whether the local OSPFv3 interface and the remote OSPFv3 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:

ospfv3 timer hello

ospfv3 timer dead

ospfv3 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.

ospfv3VirtIfConfigError

Basic information

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

Notification triggers

This notification is generated when an OSPFv3 virtual interface on a router receives a packet from another router with mismatched configuration. 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 as long as the local interface and the remote interface use the same settings after configuration correction.

Status control

CLI: Use the snmp-agent trap enable ospfv3 virtif-cfg-error command.

OFF

CLI: Use the undo snmp-agent trap enable ospfv3 virtif-cfg-error command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.191.1.1.1 (ospfv3RouterId)	Unique identifier of a router in an AS.	N/A	Ospfv3RouterIdTC	Unsigned32 (1..'FFFFFFFF'h)
1.3.6.1.2.1.191.1.8.1.9 (ospfv3VirtIfState)	Virtual interface state.	ospfv3VirtIfAreaId ospfv3VirtIfNeighbor	INTEGER	down(1), pointToPoint(4)
1.3.6.1.2.1.191.1.14.1 (ospfv3ConfigErrorType)	OSPFv3 configuration error type.	N/A	INTEGER	badVersion(1), areaMismatch(2), unknownNbmaNbr(3), unknownVirtualNbr(4), helloIntervalMismatch(5), deadIntervalMismatch(6), optionMismatch(7), mtuMismatch(8), duplicateRouterId(9), noError(10)
1.3.6.1.2.1.191.1.14.2 (ospfv3PacketType)	OSPFv3 data packet type.	N/A	INTEGER	hello(1), dbDescript(2), lsReq(3), lsUpdate(4), lsAck(5), nullPacket(6)

Recommended action

1.Use the display ospfv3 vlink and display current-configuration configuration ospfv3 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.

ospfv3IfRxBadPacket

Basic information

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

Notification triggers

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

The length of the OSPFv3 packet is incorrect.

The OSPFv3 packet has content errors.

System impact

When a non-virtual interface receives an OSPFv3 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

CLI: Use the snmp-agent trap enable ospfv3 if-bad-pkt command.

OFF

CLI: Use the undo snmp-agent trap enable ospfv3 if-bad-pkt command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.191.1.1.1 (ospfv3RouterId)	Unique identifier of a router in an AS.	N/A	Ospfv3RouterIdTC	Unsigned32 (1..'FFFFFFFF'h)
1.3.6.1.2.1.191.1.7.1.12 (ospfv3IfState)	Interface state.	ospfv3IfIndex ospfv3IfInstId	INTEGER	down(1), loopback(2), waiting(3), pointToPoint(4), designatedRouter(5), backupDesignatedRouter(6), otherDesignatedRouter(7), standby(8)
1.3.6.1.2.1.191.1.14.3 (ospfv3PacketSrc)	IPv6 packet that cannot be identified by the neighbor.	N/A	InetAddressIPv6	OCTET STRING (16)
1.3.6.1.2.1.191.1.14.2 (ospfv3PacketType)	OSPFv3 data 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.

ospfv3VirtIfRxBadPacket

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.191.0.7	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 OSPFv3 packet that cannot be parsed. This issue occurs when one of the following conditions exists:

The length of the OSPFv3 packet is incorrect.

The OSPFv3 packet has content errors.

System impact

When a virtual interface receives an OSPFv3 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

CLI: Use the snmp-agent trap enable ospfv3 virtif-bad-pkt command.

OFF

CLI: Use the undo snmp-agent trap enable ospfv3 virtif-bad-pkt command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.191.1.1.1 (ospfv3RouterId)	Unique identifier of a router in an AS.	N/A	Ospfv3RouterIdTC	Unsigned32 (1..'FFFFFFFF'h)
1.3.6.1.2.1.191.1.8.1.9 (ospfv3VirtIfState)	Virtual interface state.	ospfv3VirtIfAreaId ospfv3VirtIfNeighbor	INTEGER	down(1), pointToPoint(4)
1.3.6.1.2.1.191.1.14.2 (ospfv3PacketType)	OSPFv3 data 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.

ospfv3IfStateChange

Basic information

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

Notification triggers

This notification is generated when the state of a non-virtual interface changes from DR to Down or changes to the Point-to-Point, DR, BDR, or DRother state. 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 OSPFv3 interface regresses (for example, changing to Down), it will be disconnected from its neighbors.

Status control

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

OFF

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

Object

OID (object name)

Description

Index

Type

Value range

1.3.6.1.2.1.191.1.1.1

(ospfv3RouterId)

Unique identifier of a router in an AS.

N/A

Ospfv3RouterIdTC

Unsigned32 (1..'FFFFFFFF'h)

1.3.6.1.2.1.191.1.7.1.12 (ospfv3IfState)

Interface state.

ospfv3IfIndex

ospfv3IfInstId

INTEGER

down(1), loopback(2), waiting(3), pointToPoint(4), designatedRouter(5), backupDesignatedRouter(6), otherDesignatedRouter(7), standby(8)

Recommended action

To resolve this issue:

1.Use the display ospfv3 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 in 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.

If no, proceed to step 3.

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

ospfv3NssaTranslatorStatusChange

Basic information

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

Notification triggers

This notification is generated when a router's ability to translate OSPFv3 type-7 LSAs into OSPFv3 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

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

OFF

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

Object

OID (object name)

Description

Index

Type

Value range

1.3.6.1.2.1.191.1.1.1

(ospfv3RouterId)

Unique identifier of a router in an AS.

N/A

Ospfv3RouterIdTC

Unsigned32 (1..'FFFFFFFF'h)

1.3.6.1.2.1.191.1.2.1.12 (ospfv3AreaNssaTranslatorState)

Method for the NSSA ABR to become capable of translating Type-7 LSAs into Type-5 LSAs.

ospfv3AreaId

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 ospfv3 command to identify whether the 7/5 translator state field displays Enabled.