Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 06-HH3C-OSPFV3-MIB | 94.08 KB |
HH3C-OSPFv3-MIB
About this MIB
Use this MIB to display OSPFv3 information.
MIB file name
hh3c-ospfv3.mib
Notifications
hh3cOspfv3LastAuthKeyExpiry
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.239.0.1 |
The last active send key in the keychain used by OSPFv3 became inactive or no active key ID exists. |
Informational |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when the last active send key in the keychain used by OSPFv3 becomes inactive.
System impact
When no active send keys exist in the keychain used by OSPFv3, the neighbors cannot send OSPFv3 packets and will go down.
Status control
ON
CLI: Use the snmp-agent trap enable ospfv3 last-auth-key-expiry command.
OFF
CLI: Use the undo snmp-agent trap enable ospfv3 last-auth-key-expiry command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
OSPFv3 process ID. |
Integer32 |
Integer32 (1..65535) |
||
|
1.3.6.1.4.1.25506.2.239.2.2 (hh3cOspfv3AreaIdForNotify) |
OSPFv3 area ID. Each area has a unique ID. |
N/A |
IpAddress |
OCTET STRING(4) |
|
1.3.6.1.4.1.25506.2.239.2.3 (hh3cOspfv3IfName) |
Name of the packet incoming interface. |
N/A |
DisplayString |
OCTET STRING(1..255) |
|
1.3.6.1.4.1.25506.2.239.2.4 (hh3cOspfv3RouterID) |
Local router ID. |
N/A |
IpAddress |
OCTET STRING(4) |
Recommended action
To resolve this issue:
1. Use the display ospfv3 interface command to view the keychain enabled on the interface.
2. Use the display keychain command to identify whether the Default send key ID field is displayed. This field indicates whether a default send key exists and displays its status.
¡ If no default send keys exist, proceed to step 3.
¡ If the Default send key ID field displays an existing key ID and the status is Active, proceed to step 4.
¡ If the Default send key ID field displays an existing key ID and the status is Inactive, proceed to step 3.
¡ If the Default send key ID field displays None, proceed to step 3.
3. Use the display keychain command to view the Active send key ID field. This field displays the send key ID which is currently active.
¡ If the Active send key ID field displays the key ID which currently exists, proceed to step 4.
¡ If the Active send key ID field displays None, all send keys are inactive. Check whether the key configuration is complete and the system time is within the sending lifetime of the send key.
- If yes, proceed to step 4.
- If no, complete key configuration and update the send lifetime of the send key.
4. If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.
hh3cOspfv3IntraAreaRtrIdConflict
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.239.0.2 |
Intra-area router ID conflict. |
Informational |
Warning |
N/A |
ON |
Notification triggers
This notification is generated when an intra-area router ID conflict is detected in a received router LSA.
This issue occurs when the local device and a non-directly connected device has the same router ID in an OSPFv3 area.
System impact
Router LSA updates occur frequently, which results in route flapping.
Status control
ON
CLI: Use the snmp-agent trap enable ospfv3 intra-area-router-id-conflict command.
OFF
CLI: Use the undo snmp-agent trap enable ospfv3 intra-area-router-id-conflict command.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.239.2.1 (hh3cOspfv3ProcessIdForNotify) |
OSPFv3 process ID. |
N/A |
Integer32 |
Integer32 (1..65535) |
|
1.3.6.1.4.1.25506.2.239.2.2 (hh3cOspfv3AreaIdForNotify) |
OSPFv3 area ID. Each area has a unique ID. |
N/A |
IpAddress |
OCTET STRING(4) |
|
1.3.6.1.4.1.25506.2.239.2.3 (hh3cOspfv3IfName) |
Name of the packet outgoing interface. |
N/A |
DisplayString |
OCTET STRING(1..255) |
|
1.3.6.1.4.1.25506.2.239.2.4 (hh3cOspfv3RouterID) |
Local router ID. |
N/A |
IpAddress |
OCTET STRING(4) |
|
1.3.6.1.4.1.25506.2.239.2.5 (hh3cOspfv3NbrAddr) |
Neighbor IP address. |
N/A |
InetAddress |
OCTET STRING(0..255) |
Recommended action
To resolve this issue:
1. Obtain the OSPFv3 area ID reported in the notification.
2. Execute the display ospfv3 command on each device in the OSPFv3 area to check for the conflicting router ID. Change the router ID of the conflicting device or local device, ensuring that no router ID conflicts will occur within the OSPFv3 area.
3. If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.
