Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 06-HH3C-OSPF-MIB | 67.13 KB |
Contents
hh3cOspfIntraAreaRtrIdConflict
hh3cOspfPeerFlappingStatusChange
hh3cOspfSrPrefixSidConflictClear
HH3C-OSPF-MIB
About this MIB
Use this MIB to display OSPF information.
MIB file name
hh3c-ospf.mib
Notifications
hh3cOspfIntraAreaRtrIdConflict
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.161.0.1 |
Intra-area router ID conflict |
Informational |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when an intra-area router ID conflict is detected in a received router LSA.
The SNMP agent generates this notification only when it detects more than five intra-area router ID conflicts within two minutes. This can prevent the agent from generating too many hh3cOspfIntraAreaRtrIdConflict notifications within a short time.
This issue occurs when the local device and another device has the same router ID in an OSPF area.
System impact
Router LSA updates occur frequently, which results in route flapping.
Status control
ON
CLI: Use the snmp-agent trap enable ospf intra-area-router-id-conflict command.
OFF
CLI: Use the undo snmp-agent trap enable ospf intra-area-router-id-conflict command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.161.2.1 (hh3cOspfProcessIdForNotify) |
OSPF process ID. |
N/A |
Integer32 |
Integer32 (1..65535) |
|
1.3.6.1.4.1.25506.2.161.2.2 (hh3cOspfAreaIdForNotify) |
OSPF area ID. Each area has a unique ID. |
N/A |
IpAddress |
OCTET STRING(4) |
|
1.3.6.1.4.1.25506.2.161.2.3 (hh3cOspfIfName) |
Name of the packet incoming interface. |
N/A |
DisplayString |
OCTET STRING(1..255) |
|
1.3.6.1.4.1.25506.2.161.2.4 (hh3cOspfRouterID) |
Local router ID. |
N/A |
IpAddress |
OCTET STRING(4) |
|
1.3.6.1.4.1.25506.2.161.2.5 (hh3cOspfNbrIpAddr) |
Neighbor IP address. |
N/A |
IpAddress |
OCTET STRING(4) |
Recommended action
To resolve this issue:
1.Locate the neighbor device based on the 1.3.6.1.4.1.25506.2.161.2.5 (hh3cOspfNbrIpAddr) object in the notification.
2.Use the display ospf command to identify whether the neighbor device and the local device have the same router ID. If the two devices use the same router ID, change the router ID of the neighbor or local device, ensuring that no router ID conflicts will occur within the OSPF area.
3.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.
hh3cOspfDRIpAddressConflict
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.161.0.2 |
Intra-area DR IP address conflict |
Informational |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when an intra-area DR IP conflict is detected in a received network LSA.
The SNMP agent generates this notification only when it detects more than five intra-area DR IP conflicts within two minutes. This can prevent the agent from generating too many hh3cOspfDRIpAddressConflict notifications within a short time.
This issue occurs when one of the following conditions exist in an OSPF area:
The primary IP address of an interface on the local device is the same as the IP address of the DR.
The local device has an interface that acts as the DR and the primary IP address of an interface on another device is the same as the DR IP address.
System impact
This issue causes route flapping.
Status control
ON
CLI: Use the snmp-agent trap enable ospf dr-ip-address-conflict command.
OFF
CLI: Use the undo snmp-agent trap enable ospf dr-ip-address-conflict command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.161.2.1 (hh3cOspfProcessIdForNotify) |
OSPF process ID. |
N/A |
Integer32 |
Integer32 (1..65535) |
|
1.3.6.1.4.1.25506.2.161.2.2 (hh3cOspfAreaIdForNotify) |
OSPF area ID. Each area has a unique ID. |
N/A |
IpAddress |
OCTET STRING(4) |
|
1.3.6.1.4.1.25506.2.161.2.3 (hh3cOspfIfName) |
Name of the packet incoming interface. |
N/A |
DisplayString |
OCTET STRING(1..255) |
|
1.3.6.1.4.1.25506.2.161.2.4 (hh3cOspfRouterID) |
Local router ID. |
N/A |
IpAddress |
OCTET STRING(4) |
|
1.3.6.1.4.1.25506.2.161.2.5 (hh3cOspfNbrIpAddr) |
Conflicting IP address. |
N/A |
IpAddress |
OCTET STRING(4) |
|
1.3.6.1.4.1.25506.2.161.2.6 (hh3cOspfLsaAdvRtr) |
Router ID of the DR. |
N/A |
IpAddress |
OCTET STRING(4) |
|
1.3.6.1.4.1.25506.2.161.2.7 (hh3cOspfLsaLsid) |
Link state ID in the network LSA. |
N/A |
IpAddress |
OCTET STRING(4) |
Recommended action
To resolve this issue:
1.Locate the conflicting device based on the 1.3.6.1.4.1.25506.2.161.2.5 (hh3cOspfNbrIpAddr) and 1.3.6.1.4.1.25506.2.161.2.6 (hh3cOspfLsaAdvRtr) objects in the notification.
2.Use the display ospf command to check whether the device and the local device use the same IP address.
If the two devices use the same IP address, change the IP address for one of the devices, ensuring that no address conflicts will occur.
3.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.
hh3cOspfPeerFlappingStatusChange
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.161.0.3 |
Change in the state of OSPF neighbor flapping suppression. |
Informational |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when the state of OSPF neighbor flapping suppression changes.
This issue occurs when one of the following conditions exist:
OSPF neighbor flapping occurs frequently.
OSPF no longer flaps frequently.
System impact
Services might be affected if the interface recovers but OSPF is still under neighbor flapping suppression.
Status control
ON
CLI: Use the snmp-agent trap enable ospf peer-flapping-suppress-status-change command.
OFF
CLI: Use the undo snmp-agent trap enable ospf peer-flapping-suppress-status-change command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.161.2.1 (hh3cOspfProcessIdForNotify) |
OSPF process ID. |
N/A |
Integer32 |
Integer32 (1..65535) |
|
1.3.6.1.4.1.25506.2.161.2.2 (hh3cOspfAreaIdForNotify) |
OSPF area ID. Each area has a unique ID. |
N/A |
IpAddress |
OCTET STRING(4) |
|
1.3.6.1.4.1.25506.2.161.2.3 (hh3cOspfIfName) |
Interface name. |
N/A |
DisplayString |
OCTET STRING(1..255) |
|
1.3.6.1.4.1.25506.2.161.2.8 (hh3cOspfPeerFlappingStatus) |
Neighbor flapping suppression state. |
N/A |
INTEGER |
notSuppressed(1), holdDown(2), holdMaxCost(3) |
|
1.3.6.1.4.1.25506.2.161.2.9 (hh3cOspfPeerFlappingReason) |
Reason for the neighbor flapping suppression state change. |
N/A |
INTEGER |
resumed(1), configurationChanged(2), suppressed(3), exitHoldDownIntoHoldMaxCost(4) |
Recommended action
To resolve this issue:
1.Use the display interface interface-type interface-number command to identify whether the interface frequently goes down and up.
- If yes, no action is required.
- If no, check whether the remote interface frequently goes down and up. If no, proceed to step 2.
2.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.
hh3cOspfSrPrefixSidConflict
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.161.0.4 |
An OSPF SR prefix conflict or SID conflict occurs. |
Error |
Warning |
1.3.6.1.4.1.25506.2.161.0.5 (hh3cOspfSrPrefixSidConflictClear) |
ON |
Notification triggers
This notification is generated when a SR prefix conflict or SID configured for the loopback interface on the local device conflicts with that on another device.
This issue occurs when one of the following conditions exist:
Multiple devices advertise the same SR prefix in the network.
Multiple devices advertise the same SID in the network.
System impact
If an SR prefix conflict occurs, SR does not use the conflicting routes.
If an SID conflict occurs, the system selects one SID and ignores the same SID advertised by other devices.
Status control
ON
CLI: Use the snmp-agent trap enable ospf sr-prefix-sid-conflict command.
OFF
CLI: Use the undo snmp-agent trap enable ospf sr-prefix-sid-conflict command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.161.2.1 (hh3cOspfProcessIdForNotify) |
OSPF process ID. |
N/A |
Integer32 |
Integer32 (1..65535) |
|
1.3.6.1.4.1.25506.2.161.2.10 (hh3cOspfPrefixSid) |
Prefix SID. |
N/A |
Integer32 |
Integer32 (2048.. 1048575) |
|
1.3.6.1.4.1.25506.2.161.2.11 (hh3cOspfPrefixAddress) |
Prefix address. |
N/A |
IpAddress |
OCTET STRING(4) |
|
1.3.6.1.4.1.25506.2.161.2.12 (hh3cOspfPrefixMask) |
Prefix mask. |
N/A |
IpAddress |
OCTET STRING(4) |
|
1.3.6.1.4.1.25506.2.161.2.13 (hh3cOspfSrConflictType) |
Conflict type. |
N/A |
DisplayString |
PrefixConflict, SidConflict |
|
1.3.6.1.4.1.25506.2.161.2.14 (hh3cOspfSrConflictState) |
Conflict state. |
N/A |
DisplayString |
InConflict, ConflictResolved |
Recommended action
To resolve this issue:
1.Locate the advertisement source based on the prefix SID and prefix address, and then correct the address or SID configuration on the loopback interface of the source device.
2.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.
hh3cOspfSrPrefixSidConflictClear
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.161.0.5 |
An OSPF SR prefix conflict or SID conflict is cleared. |
Recovery |
Informational |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when the SR prefix or SID configured on the local Loopback interface no longer conflicts with that configured on any other device.
System impact
No negative impact on services.
Status control
ON
CLI: Use the snmp-agent trap enable ospf sr-prefix-sid-conflict-clear command.
OFF
CLI: Use the undo snmp-agent trap enable ospf sr-prefix-sid-conflict-clear command.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.161.2.1 (hh3cOspfProcessIdForNotify) |
OSPF process ID. |
N/A |
Integer32 |
Integer32 (1..65535) |
|
1.3.6.1.4.1.25506.2.161.2.10 (hh3cOspfPrefixSid) |
Prefix SID. |
N/A |
Integer32 |
Integer32 (2048.. 1048575) |
|
1.3.6.1.4.1.25506.2.161.2.11 (hh3cOspfPrefixAddress) |
Prefix address. |
N/A |
IpAddress |
OCTET STRING(4) |
|
1.3.6.1.4.1.25506.2.161.2.12 (hh3cOspfPrefixMask) |
Prefix mask. |
N/A |
IpAddress |
OCTET STRING(4) |
|
1.3.6.1.4.1.25506.2.161.2.13 (hh3cOspfSrConflictType) |
Conflict type. |
N/A |
DisplayString |
PrefixConflict, SidConflict |
|
1.3.6.1.4.1.25506.2.161.2.14 (hh3cOspfSrConflictState) |
Conflict state. |
N/A |
DisplayString |
InConflict, ConflictResolved |
Recommended action
No action is required.
