MFLP/4/MFLP_VSI_ALARM

Message

MFLP/4/MFLP_VSI_ALARM: Alarm only when loop existed in VSI. (VsiName=[vsiname], AlarmReason=[alarmreason], DetectMAC=[detectMAC], InterfaceName1=[AcName1], InterfaceName2=[AcName2], InterfaceName3=[AcName3])

Description

Only an alarm is sent when a loop occurs in a VSI.

Parameters

Parameter Name	Parameter Meaning
vsiname	VSI name
alarmreason	Causes for the alarm
detectMAC	MAC address that flaps
AcName1	Name of interface 1 on which MAC address flaps
AcName2	Name of interface 2 on which MAC address flaps
AcName3	Name of interface 3 on which MAC address flaps

Possible Causes

Cause 1: There is a loop which is not blocked. Cause 2: New block cannot take effect in VSI when the number of the blocked entries has reached the upper limit.

Procedure

Cause 1: There is a loop which is not blocked.

1. Run the display current-configuration command to check whether the loopback local command is configured on AC-side interfaces corresponding to the VSI.

If the loopback local command is configured on AC-side interfaces corresponding to the VSI, delete the command configuration and check whether the alarm is cleared. If the alarm persists, go to Step 2.
If the loopback local command is not configured on AC-side interfaces corresponding to the VSI, go to Step 2.

2. Run the display loop-detect eth-loop command to check whether Action is displayed as Alarm-only.

If Action is displayed as Alarm-only, go to Step 3.
If Action is not displayed as Alarm-only, go to Step 4.

3. For the VSI in the alarm, perform either of the following steps:

Run the shutdown command in the VSI and check whether the alarm is cleared. If the alarm persists, go to Step 4.
Run the loop-detect eth-loop command in the VSI view to change alarm-only to another parameter that allows the device to block an interface or a PW. For example, run the loop-detect eth-loop loop-times 3 detect-cycle 3 cycles 3 retry-times 1 block-time 10 command in the VSI view. 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: New block cannot take effect in VSI when the number of the blocked entries has reached the upper limit.

1. Run the display current-configuration command to check whether the loopback local command is configured on AC-side interfaces corresponding to the VSI.

If the loopback local command is configured on AC-side interfaces corresponding to the VSI, delete the command configuration and check whether the alarm is cleared. If the alarm persists, go to Step 2.
If the loopback local command is not configured on AC-side interfaces corresponding to the VSI, go to Step 2.

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