ETRUNK/4/ETRUNK_STATUS_CHANGE

Message

ETRUNK/4/ETRUNK_STATUS_CHANGE: The status of an E-Trunk changed.(ETrunkId=[ETrunkId], State=[State], StateReason=[StateReason])

Description

The E-Trunk status change was notified to the NMS.

Parameters

Parameter Name	Parameter Meaning
ETrunkId	E-Trunk ID
State	E-Trunk status
StateReason	Reason for the E-Trunk being in this status

Possible Causes

Cause 1: PRI (The master/backup status change is determined based on the priorities.)

Cause 2: TIMEOUT (The local device becomes the master if the timeout period expires before the device receives any packet from the peer.)

Cause 3: BFD_DOWN (The local BFD session detects that the link between the local device and the peer is Down.)

Cause 4: PEER_TIMEOUT (The peer becomes the master if the timeout period expires before the device receives any packet from the local device.)

Cause 5: INIT (The E-Trunk is undergoing initialization.)

Procedure

Cause 1: PRI

1. Check whether the E-Trunk master/backup status change is required. If it is not required, go to Step 2.

2. Run the display e-trunk etrunk-id command to check whether the E-Trunk priority is changed.

If the E-Trunk priority is changed, check whether the priority change is required. If the priority change is not required, go to Step 3.
If the E-Trunk priority is not changed, go to Step 4.

3. Run the priority priority command in the E-Trunk view to configure the E-Trunk priority based on the networking. Then, 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.

Cause 2: TIMEOUT

1. Check whether the IP addresses of the local and peer devices in the E-Trunk are configured correctly.

If the IP addresses of the local and peer devices in the E-Trunk are configured correctly, go to Step 2.
If the IP addresses of the local and peer devices in the E-Trunk are not configured correctly, go to Step 4.

2. Check whether the routes between the devices in the E-Trunk are reachable.

If the routes between the devices in the E-Trunk are reachable, go to Step 5.
If the routes between the devices in the E-Trunk are not reachable, go to Step 3.

3. Check the physical link and repair it if faulty. If the alarm persists, go to Step 5.

4. Run the peer-address source-address source-ip-address command in the E-Trunk view to correctly configure IP addresses for the local and peer devices in the E-Trunk. Then, check whether the alarm is cleared. If the alarm persists, go to Step 5.

5. Collect log information and configuration information, and then contact technical support personnel.

Cause 3: BFD_DOWN

1. Run the display bfd session command in the system view to check BFD session information.

If the BFD session is bound to the E-Trunk and is Down, see troubleshooting of BFD sessions.
If the BFD session is bound to the E-Trunk and is Up, go to Step 2.

2. Check whether the interface is shut down.

If the interface is shut down, go to Step 3.
If the interface is not shut down, go to Step 4.

3. Run the undo shutdown command in the interface view. Then, check whether the alarm is cleared. If the alarm persists, go to Step 4.

4. Check the physical link and repair it if faulty. If the alarm persists, go to Step 5.

5. Collect log information and configuration information, and then contact technical support personnel.

Cause 4: PEER_TIMEOUT

1. Check whether the IP addresses of the local and peer devices in the E-Trunk are configured correctly.

If the IP addresses of the local and peer devices in the E-Trunk are configured correctly, go to Step 2.
If the IP addresses of the local and peer devices in the E-Trunk are not configured correctly, go to Step 4.

2. Check whether the routes between the devices in the E-Trunk are reachable.

If the routes between the devices in the E-Trunk are reachable, go to Step 5.
If the routes between the devices in the E-Trunk are not reachable, go to Step 3.

3. Check the physical link and repair it if faulty. If the alarm persists, go to Step 5.

5. Collect log information and configuration information, and then contact technical support personnel.

Cause 5: INIT

1. Check whether the ongoing E-Trunk initialization is normal. If the ongoing E-Trunk initialization is not normal, go to Step 2.

2. Collect log information and configuration information, and then contact technical support personnel.