ETRUNK_1.3.6.1.4.1.2011.5.25.178.2.1 hwETrunkStatusChange
Description
ETRUNK/4/TRAP_STATUS:OID [oid] The status of an E-Trunk changed.(Index=[integer], State=[integer], Reason=[integer])
The status change of an E-Trunk was advertised to the NMS.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.178.2.1 | Warning | equipmentAlarm(5) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
Index |
Index of the E-Trunk |
State |
Status of the E-Trunk
|
Reason |
Cause for the E-Trunk in such a status |
Possible Causes
1.
The priority of the E-Trunk was changed.
2.
The packet-receiving timer at the local device expired.
3.
BFD detected the fault on the control link between PEs.
Procedure
- Run the display e-trunk etrunk-id command to check the cause for the master/backup status switchover
of the E-Trunk.
If the entry PRI(1) is displayed, indicating that the master/backup status is determined by the E-Trunk priority, go to Step 2.
If the entry TIMEOUT(2) is displayed, indicating that the local device becomes the master because it receives no protocol packets from the peer device within the timeout period, go to Step 3.
If the entry BFD_DOWN(3) is displayed, indicating that the local BFD detects the link-down event between the local device and the peer device, go to Step 4.
If the entry PEER_TIMEOUT(4) is displayed, indicating that the peer device becomes the master because it receives no protocol packets from the local device within the timeout period, go to Step 3.
If the entry PEER_BFD_DOWN(5) is displayed, indicating that the peer BFD detects the link-down event between the local device and the peer device, go to Step 4.
If the entry ALL_MEMBER_DOWN(6) is displayed, indicating that the two devices of an E-Trunk are Down, go to Step 4.
If the entry INIT(7) is displayed, indicating that the E-Trunk is being initialized, go to Step 5.
- Check whether the master/backup status of the E-Trunk is
switched over according to user's requirement.
If so, go to Step 14.
If not, go to Step 6.
- Check whether the IP addresses of the E-Trunk local device
and peer device are correctly configured.
If so, go to Step 7.
If not, go to Step 12.
- Check whether the E-Trunk interface is shut down.
If so, go to Step 8.
If not, go to Step 10.
- Check whether the E-Trunk is correctly initialized.
If so, go to Step 14.
If not, go to Step 13.
- Check whether the E-Trunk priority is changed according
to the entries displayed in Step 1.
If so, go to Step 9.
If not, go to Step 13.
- Check whether the route between E-Trunk devices is reachable.
If so, go to Step 13.
If not, go to Step 10.
- Run the undo shutdown command in the interface view
to check whether the trap is cleared.
If so, go to Step 14.
If not, go to Step 10.
- Check whether the E-Trunk priority is changed according
to a legal requirement.
If so, go to Step 14.
If not, go to Step 11.
- Check whether the physical links are repaired, and the
trap is cleared.
If so, go to Step 14.
If not, go to Step 13.
- Run the priority priority command
in the E-Trunk view to correctly configure the E-Trunk priority according
to the networking requirement, and then check whether the trap is
cleared.
If so, go to Step 14.
If not, go to Step 13.
- Run the peer-address peer-ip-address source-address source-ip-address command in the E-Trunk view
to correctly configure the IP addresses of the E-Trunk local device
and peer device, and then check whether the trap is cleared.
If so, go to Step 14.
If not, go to Step 13.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
Previous
