MFLP_1.3.6.1.4.1.2011.5.25.160.3.25 hwMflpBdAlarmOnly

Trap Buffer Description

Alarm only when loop existed in BD. (BD=[bdid], AlarmReason=[alarmreason], DetectMAC=[detectMAC], InterfaceName1=[AcName1], InterfaceName2=[AcName2], InterfaceName3=[AcName3])

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

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Warning
Mnemonic Code	MFLP_BD_ALARM
Trap OID	1.3.6.1.4.1.2011.5.25.160.3.25
MIB	HUAWEI-MFLP-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	-

Trap Buffer Parameters

Parameter	Description
bdid	Bridge domain ID.
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.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.160.1.3.1.1	hwMflpBdIndex	hwMflpBdIndex
1.3.6.1.4.1.2011.5.25.160.1.3.1.3	hwMflpBdCfgAcName	hwMflpBdIndex
1.3.6.1.4.1.2011.5.25.160.1.3.1.6	hwMflpBdCfgAcNameEx1	hwMflpBdIndex
1.3.6.1.4.1.2011.5.25.160.1.3.1.7	hwMflpBdCfgAcNameEx2	hwMflpBdIndex
1.3.6.1.4.1.2011.5.25.160.1.3.1.4	hwMflpBdCfgAlarmReason	hwMflpBdIndex
1.3.6.1.4.1.2011.5.25.160.1.3.1.5	hwMflpBdDetectMAC	hwMflpBdIndex

Impact on the System

Traffic is congested in the BD. If the loop is not eliminated in time, the network will break down.

Possible Causes

Cause 1: There is a loop which is not blocked. Cause 2: New block cannot take effect in BD 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 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.

Cause 2: New block cannot take effect in BD 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 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. Collect log information and configuration information, and then contact technical support personnel.