LDT/4/ALD_LOG_TRIGGERDOWN

Message

LDT/4/ALD_LOG_TRIGGERDOWN: The interface turned to trigger-down state, because of the loop detected on this interface. (Interface = [IfName], DomainType = [DomainType], DomainName = [DomainName],Trigger Source = [TrggerSourceifName]).

Description

An interface entered the trigger-down state because a loop was detected on this interface.

Parameters

Parameter Name	Parameter Meaning
IfName	Name of an interface
DomainType	Type of the domain
DomainName	Name of the domain
TrggerSourceifName	Name of the interface that triggers the loop

Possible Causes

Proactive loop detection was triggered when the interface went Up or was bound to a VSI.

After a loop was detected, the interface was blocked and entered the trigger-down state, and a log about this event was recorded.

Procedure

1. Run the display loop-detect trigger trigger-down all command to check whether there is an interface in the trigger-down state. If there is an interface in the trigger-down state, go to Step 2. If there is no interface in the trigger-down state, go to Step 4.

2. Check whether the interface connection has a loop. If the interface connection has a loop, go to Step 3. If the interface connection does not have a loop, go to Step 4.

3. Eliminate the loop, and run the shutdown and undo shutdown commands in sequence or run the reset loop-detect trigger trigger-down command on the blocked interface to release its blocking status. Either of the following two situations is available, depending on how proactive loop detection is triggered:

If proactive loop detection is triggered by the binding between the interface and a VSI, the interface is unblocked after it is unbound from the VSI. In this situation, check whether the loop alarm is cleared. If the loop alarm is cleared, the troubleshooting ends. If the loop alarm persists, go to Step 4.
If proactive loop detection is triggered by interface going Down physically, the interface is unblocked after it is unbound from the VSI, and a new round of loop detection starts. In this situation, check whether the loop alarm is cleared. If the loop alarm is cleared, the troubleshooting ends. If the loop alarm persists, go to Step 4.

4. Collect alarm, log, and configuration information, and contact technical support personnel.