Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 05-HH3C-OSPF-MIB | 118.46 KB |
HH3C-OSPF-MIB
About this MIB
Use this MIB to display OSPF information.
MIB file name
hh3c-ospf.mib
Root object
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cOspf(161)
Scalar objects
hh3cOspfProcessIdForNotify
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cOspfProcessIdForNotify (1.3.6.1.4.1.25506.2.161.2.1) |
accessible-for-notify |
Integer32 |
Integer32 (1..65535) |
As per the MIB. |
hh3cOspfAreaIdForNotify
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cOspfAreaIdForNotify (1.3.6.1.4.1.25506.2.161.2.2) |
accessible-for-notify |
IpAddress |
OCTET STRING (4) |
OSPF area ID. Each area has a unique ID. |
As per the MIB. |
hh3cOspfIfName
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cOspfIfName (1.3.6.1.4.1.25506.2.161.2.3) |
accessible-for-notify |
DisplayString |
OCTET STRING (1..255) |
OSPF interface name. |
As per the MIB. |
hh3cOspfRouterID
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cOspfRouterID (1.3.6.1.4.1.25506.2.161.2.4) |
accessible-for-notify |
IpAddress |
OCTET STRING (4) |
OSPF router ID. |
As per the MIB. |
hh3cOspfNbrIpAddr
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cOspfNbrIpAddr (1.3.6.1.4.1.25506.2.161.2.5) |
accessible-for-notify |
IpAddress |
OCTET STRING (4) |
OSPF neighbor IP address. |
As per the MIB. |
hh3cOspfLsaAdvRtr
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cOspfLsaAdvRtr (1.3.6.1.4.1.25506.2.161.2.6) |
accessible-for-notify |
IpAddress |
OCTET STRING (4) |
LSA advertisement source node. |
As per the MIB. |
hh3cOspfLsaLsid
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cOspfLsaLsid (1.3.6.1.4.1.25506.2.161.2.7) |
accessible-for-notify |
IpAddress |
OCTET STRING (4) |
Link state ID. |
As per the MIB. |
Tabular objects
hh3cOspfNetworkTable
About this table
This table displays OSPF network configuration information.
Support for operations
|
Create |
Edit/Modify |
Delete |
Read |
|
Not supported |
Not supported |
Not supported |
Supported |
Columns
The table indexes are hh3cOspfProcessId, hh3cOspfAreaId, and hh3cOspfNetworkIpAddr.
|
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
|
hh3cOspfProcessId (1.3.6.1.4.1.25506.2.161.1.1.1) |
not-accessible |
Integer32 |
Integer32(1..65535) |
OSPF process ID. |
As per the MIB. |
|
hh3cOspfAreaId (1.3.6.1.4.1.25506.2.161.1.1.2) |
not-accessible |
IpAddress |
OCTET STRING (4) |
Area ID, uniquely identifying an area. |
As per the MIB. |
|
hh3cOspfNetworkIpAddr (1.3.6.1.4.1.25506.2.161.1.1.3) |
not-accessible |
IpAddress |
OCTET STRING (4) |
Network address. |
As per the MIB. |
|
hh3cOspfNetworkIpMask (1.3.6.1.4.1.25506.2.161.1.1.4) |
read-only |
IpAddress |
OCTET STRING (4) |
Wildcard mask of the network address. |
As per the MIB. |
Notifications
hh3cOspfIntraAreaRtrIdConflict
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.161.0.1 |
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.
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.
Objects
|
OID (object name) |
Description |
Index nodes |
Type |
Value range |
|
OSPF process ID. |
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 |
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.
Objects
|
OID (object name) |
Description |
Index nodes |
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) |
|
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.
