MFLP/5/MFLP_BD_LINKBLOCK_LOG

Message

MFLP/5/MFLP_BD_LINKBLOCK_LOG: The AC interfaces of the main interface have been blocked due to MAC-Flapping association. (BD=[bdid], ACInterfaceName=[ACName], MainInterfaceName=[MainIfName], BlockTime=[blockTime])

Description

A main interface's AC interfaces bound to BDs were all blocked due to MAC flapping association.

Parameters

Parameter Name	Parameter Meaning
bdid	Bridge domain ID
ACName	Name of the AC interface that triggers associated blocking
MainIfName	Name of the main interface that is blocked
blockTime	Blocking time

Possible Causes

The main interface is configed with MAC-Flapping association, and the AC interface in the main interface has circle.

Procedure

Cause: The main interface is configed with MAC-Flapping association, and the AC interface in the main interface has circle.

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

If the loopback local command is configured on AC-side interfaces corresponding to the BD, 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 BD, 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 BD in the alarm, perform either of the following steps:

Run the shutdown command in the BD and check whether the alarm is cleared. If the alarm persists, go to Step 4.
Run the loop-detect eth-loop command in the BD 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 BD 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.