OSPFV3_1.3.6.1.4.1.2011.5.25.147.0.8 hwOspfv3IfStateChange
Description
OSPFV3/2/IFCHANGE:OID [oid] The status of the non-virtual interface has changed. (IfIndex=[integer], InstanceId=[integer], RouterId=[gauge], IfState=[integer], IfName=[octet], ChgReason=[integer])
The status of the OSPFv3 non-virtual-link interface changed.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.147.0.8 | Major | processingErrorAlarm(4) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
IfIndex |
Indicates the index of the interface. The value is a decimal integer. |
InstanceId |
Indicates the ID of the OSPFv3 instance. The value is a decimal integer. |
RouterId |
Indicates the Router ID of the local router. The value is a decimal integer. |
IfState |
Indicates the status of the non-virtual neighbor.
|
IfName |
Indicates the name of the interface. |
ChgReason |
Indicates the reason for change in the state
of an OSPFv3 interface.
|
Impact on the System
This trap is generated when the status of a common interface changes. This trap may affect the neighbor status. If the interface goes Down, the neighbor relationship will be interrupted.
Possible Causes
1. The physical interface went Up or Down.
2. The OSPFv3 neighbor relationship was being established.
Procedure
- Run the display rm interface and display ipv6 interface brief commands to check whether
the interface is Down.
- If the physical interface is Down, check the link. Then check whether the trap is cleared.
If so, go to Step 4.
If not, go to Step 2.
If the physical interface is Up, go to Step 2.
- Run the display ospfv3 interface command to check whether the current interface is Up.
If so, go to Step 4.
If not, go to Step 3.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
Previous
