IFNET_1.3.6.1.4.1.2011.5.25.41.3.31 hwIfControlFlapSuppress

Trap Buffer Description

The state of interface changed from unsuppress to suppress. (InterfaceIndex=[InterfaceIndex], InterfaceExtIndex=[InterfaceExtIndex], InterfaceName=[InterfaceName], SuppressState=[SuppressState])

After the flapping control function is configured on an interface, the interface became suppressed.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Warning
Mnemonic Code	hwIfControlFlapAlarm
Trap OID	1.3.6.1.4.1.2011.5.25.41.3.31
MIB	HUAWEI-IF-EXT-MIB
Alarm ID	0x08522016
Alarm Name	hwIfControlFlapSuppress
Alarm Type	communicationsAlarm
Raise or Clear	Raise
Match trap	IFNET_1.3.6.1.4.1.2011.5.25.41.3.32 hwIfControlFlapResume

Trap Buffer Parameters

Parameter	Description
InterfaceIndex	Interface index
InterfaceExtIndex	Extended interface index
InterfaceName	Interface name
SuppressState	Interface suppression status: 0: The interface is not suppressed. 1: The interface is suppressed.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.2.1.31.1.1.1.1	ifName	ifIndex
1.3.6.1.4.1.2011.5.25.41.1.1.1.1.13	hwIFExtSuppressStatus	hwIFExtIndex

Impact on the System

After the interface is suppressed, the interface management module no longer reports interface Up or Down events to the routing protocol module before the interface recovers from suppression.

Possible Causes

The interface had the flapping control function configured. When the interface alternated between Up and Down frequently, the interface became suppressed. The number of the interface flapping times that triggers the suppression alarm depends on the control-flap command configuration.

Procedure

1. Check the physical link. Interface flapping usually results from a physical link fault or link instability during a short time.If the physical link works improperly, you need to check whether the hardware such as the network cable or optical module is disconnected or loosely connected and correctly connect the physical link and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 2.

If the alarm is generated on a physical interface, check whether the physical link of the interface works properly.
If the alarm is generated on a sub-interface, check whether the physical link of the main interface works properly.
If the alarm is generated on a trunk interface, check whether the physical links of the trunk member interfaces work properly.

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