The status of an E-Trunk member changed. (ETrunkId=[ETrunkId], MemberType=[MemberType], MemberId=[MemberId], State=[State], StateReason=[StateReason])
The status of an E-Trunk member interface has changed.
| Trap Attribute | Description |
|---|---|
Alarm or Event |
Event |
Trap Severity |
Warning |
Mnemonic Code |
ETRUNK_MEMBER_STATUS_CHANGE |
Trap OID |
1.3.6.1.4.1.2011.5.25.178.2.2 |
MIB |
HUAWEI-E-TRUNK-MIB |
Alarm ID |
This is an event trap and does not involve alarm ID. |
Alarm Name |
This is an event trap and does not involve alarm name. |
Alarm Type |
This is an event trap and does not involve alarm type. |
Raise or Clear |
This is an event trap and does not involve alarm generation or clearance. |
Match trap |
- |
| Parameter | Description |
|---|---|
ETrunkId |
ID of the E-Trunk to which the member interface belongs. |
MemberType |
Member interface type. Currently, only the Eth-Trunk interface is supported. |
MemberId |
Member interface ID. |
State |
Member interface status. |
StateReason |
Reason for the member interface being in this state. |
| VB OID | VB Name | VB Index |
|---|---|---|
1.3.6.1.4.1.2011.5.25.178.1.2.1.4 |
hwETrunkMemberStatus |
hwETrunkMemberParentId hwETrunkMemberType hwETrunkMemberId |
1.3.6.1.4.1.2011.5.25.178.1.2.1.5 |
hwETrunkMemberStatusReason |
hwETrunkMemberParentId hwETrunkMemberType hwETrunkMemberId |
Cause 1: FORCE_BACKUP (The Eth-Trunk interface in the E-Trunk works in backup mode.)
Cause 2: FORCE_MASTER (The Eth-Trunk interface in the E-Trunk works in master mode.)
Cause 3: ETRUNK_INIT (The E-Trunk is undergoing initialization.)
Cause 4: ETRUNK_BACKUP (The E-Trunk works in backup mode.)
Cause 5: ETRUNK_MASTER (The E-Trunk works in master mode.)
Cause 6: PEER_MEMBER_DOWN (The peer Eth-Trunk interface goes Down.)
Cause 7: PEER_MEMBER_UP (The peer Eth-Trunk interface goes Up.)
1. Check whether the working mode of the local Eth-Trunk interface is changed.
2. Check whether the working mode change of the local Eth-Trunk interface is required. If the working mode change is not required, go to Step 3.
3. In the Eth-Trunk interface view, run the e-trunk mode { auto | force-master | force-backup } command to configure the correct working mode for the Eth-Trunk interface in the E-Trunk based on the networking. Check whether the alarm is cleared. If the alarm persists, go to Step 4.
4. Collect log information and configuration information, and then contact technical support personnel.
1. Check whether the working mode of the local Eth-Trunk interface is changed.
2. Check whether the working mode change of the local Eth-Trunk interface is required. If the working mode change is not required, go to Step 3.
3. In the Eth-Trunk interface view, run the e-trunk mode { auto | force-master | force-backup } command to configure the correct working mode for the Eth-Trunk interface in the E-Trunk based on the networking. Check whether the alarm is cleared. If the alarm persists, go to Step 4.
4. Collect log information and configuration information, and then contact technical support personnel.
See the troubleshooting steps in ETRUNK/4/ETRUNK_STATUS_CHANGE.
See the troubleshooting steps in ETRUNK/4/ETRUNK_STATUS_CHANGE.
See the troubleshooting steps in ETRUNK/4/ETRUNK_STATUS_CHANGE.
1. Check whether the peer interface is shut down.
2. Run the undo shutdown command in the interface view. Then, check whether the alarm is cleared. If the alarm persists, go to Step 3.
3. Check the physical link and repair it if faulty. If the alarm persists, go to Step 4.
4. Collect log information and configuration information, and then contact technical support personnel.
The alarm is informational only, and no action is required.