MFLP_1.3.6.1.4.1.2011.5.25.160.3.23 hwMflpBdPwBlock

Trap Buffer Description

The PW turned to block state. (BD=[bdid], VsiName=[vsiname], PeerIP=[peerip], PWID=[pwid], BlockTime=[blocktime], BlockReason=[blockreason], DetectMAC=[mac])

A PW is blocked.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Warning
Mnemonic Code	hwMflpBdPwBlock
Trap OID	1.3.6.1.4.1.2011.5.25.160.3.23
MIB	HUAWEI-MFLP-MIB
Alarm ID	0x00F10118
Alarm Name	hwMflpBdPwBlock
Alarm Type	communicationsAlarm
Raise or Clear	Raise
Match trap	MFLP_1.3.6.1.4.1.2011.5.25.160.3.24 hwMflpBdPwResume

Trap Buffer Parameters

Parameter	Description
bdid	Bridge domain ID
vsiname	VSI name
peerip	Peer IP address of the blocked PW
pwid	ID of the blocked PW
blocktime	Blocking time
blockreason	Reason for the blocking
mac	Detected MAC address

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.8	hwMflpBdCfgVsiName	hwMflpBdIndex
1.3.6.1.4.1.2011.5.25.160.1.3.1.9	hwMflpBdCfgIpAddr	hwMflpBdIndex
1.3.6.1.4.1.2011.5.25.160.1.3.1.10	hwMflpBdCfgPwId	hwMflpBdIndex
1.3.6.1.4.1.2011.5.25.160.1.3.1.2	hwMflpBdCfgBlockTime	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 on the PW in the BD cannot be forwarded.

Possible Causes

Cause 1: The PW has been blocked for BD loop, and the PW has already been permanently blocked.
Cause 2: The PW has been blocked for BD loop, and the loop has already been punished times times.

Procedure

Cause 1: The PW has been blocked for BD loop, and the PW has already been permanently blocked.
1. Run the display current-configuration command to check whether the loopback local command is configured on PW-side interfaces corresponding to the BD.
- If the loopback local command is configured on PW-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 PW-side interfaces corresponding to the BD, go to Step 2.
2. Log in to the device and run the reset loop-detect eth-loop vsi vsi-name { all | peer peer-ip-address pw-id pw-id } command to unblock the PW and check whether hwMflpPwResume is reported. If hwMflpPwResume is not reported, go to Step 3.

3. Collect alarm information and configuration information, and then contact technical support personnel.
Cause 2: The PW has been blocked for BD loop, and the loop has already been punished times times.
1. Run the display current-configuration command to check whether the loopback local command is configured on PW-side interfaces corresponding to the BD.
- If the loopback local command is configured on PW-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 PW-side interfaces corresponding to the BD, go to Step 2.
2. Check whether the PW recovers after the block-time specified in the loop-detect eth-loop command expires. If the PW does not recover, go to Step 3.

3. Collect alarm information and configuration information, and then contact technical support personnel.