FIB_1.3.6.1.4.1.2011.5.25.227.2.1.13 hwWholeFwdResThresholdExceed

Trap Buffer Description

The whole device forwarding engine resources exceeded the threshold.(EntityPhysicalIndex=[EntiyPhysicalindex], EntPhysicalIndex=[EntPhysicalindex], EntPhysicalName=[EntPhysicalName], ReasonId=[ReasonId], ReasonDescription=[Reason])

The whole device forwarding engine resources exceeded the threshold.

In VS mode, this trap is supported only by the admin VS.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Warning
Mnemonic Code	hwWholeFwdResThresholdExceed
Trap OID	1.3.6.1.4.1.2011.5.25.227.2.1.13
MIB	HUAWEI-FWD-RES-TRAP-MIB
Alarm ID	0x00010002
Alarm Name	hwWholeFwdResThresholdExceed
Alarm Type	qualityOfServiceAlarm
Raise or Clear	Raise
Match trap	FIB_1.3.6.1.4.1.2011.5.25.227.2.1.14 hwWholeFwdResThresholdExceedResume

Trap Buffer Parameters

Parameter	Description
EntiyPhysicalindex	The index for this entry.
EntPhysicalindex	The index for this entry.
EntPhysicalName	The textual name of the entity.
ReasonId	The probable cause of trap.
Reason	The detailed cause of the trap.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.227.1.1	hwEntPhysicalindex	-
1.3.6.1.2.1.47.1.1.1.1.7	entPhysicalName	entPhysicalIndex
1.3.6.1.4.1.2011.5.25.227.1.3	hwFwdResLackReasonId	-

Impact on the System

Cause 15: The percentage of ND indexes exceeded the upper threshold supported by the forwarding engine.
Service may be unavailable.
Cause 16: The percentage of tunnel indexes exceeded the upper threshold supported by the forwarding engine.
Service may be unavailable.
Cause 17: The percentage of BFD indexes exceeded the upper threshold supported by the forwarding engine.
Service may be unavailable.
Cause 18: The percentage of VPLS LearnIDs exceeded the upper threshold supported by the forwarding engine.
Service may be unavailable.
Cause 19: The percentage of broadcast domain indexes exceeded the upper threshold supported by the forwarding engine.
Service may be unavailable.
Cause 20: The percentage of NS indexes exceeded the upper threshold supported by the forwarding engine.
Service may be unavailable.
Cause 21: The percentage of ring indexes exceeded the upper threshold supported by the forwarding engine.
Service may be unavailable.
Cause 34: The percentage of BFD sessions exceeded the upper threshold supported by the device.
Service may be unavailable.
Cause 98: The number of globaltoken1 forwarding engine resources exceeded the threshold.
Service may be unavailable.
Cause 100: The number of globaltoken2 forwarding engine resources exceeded the threshold.
Service may be unavailable.
Cause 103: The percentage of AT indexes exceeded the upper threshold supported by the forwarding engine.
Service may be unavailable.
Cause 205: The percentage of LDP over TE LSPs exceeded the upper threshold supported by the device.
Service may be unavailable.
Cause 400: The number of IGP peers exceeded the upper threshold supported by the device.
Service may be unavailable.
Cause 401: The number of BGP peers exceeded the upper threshold supported by the device.
Service may be unavailable.
Cause 402: The number of LDP peers exceeded the upper threshold supported by the device.
Service may be unavailable.
Cause 403: The number of PIM peers exceeded the upper threshold supported by the device.
Service may be unavailable.
Cause 551: The number of TBTP resource exceeded 85% of the specification of the forwarding engine resources(the whole is 4K).
Service may be unavailable.
Cause 552: The number of TBTP resource exceeded 85% of the specification of the forwarding engine resources(the whole is16K).
Service may be unavailable.
Cause 582: The number of user exceeded the specification of the forwarding engine resources.
Service may be unavailable.
Cause 583: The number of Lac user exceeded the specification of the forwarding engine resources.
Service may be unavailable.
Cause 587: The number of user on card0 exceeded 90% of the specification of the forwarding engine resources.
Service may be unavailable.
Cause 588: The number of user on card1 exceeded the 90% of the specification of the forwarding engine resources
Service may be unavailable.
Cause 589: The number of user on card0 exceeded the specification of the forwarding engine resources.
Service may be unavailable.
Cause 590: The number of user on card1 exceeded the specification of the forwarding engine resources.
Service may be unavailable.
Cause 701: The number of system IPv4 multicast forwarding group exceeded 95% of the forwarding engine resources.
Service may be unavailable.
Cause 702: The number of system IPv6 multicast forwarding group exceeded 95% of the forwarding engine resources.
Service may be unavailable.
Cause 772: The number of BIER TMGIDs exceeded 95% of the forwarding engine resource specification.
This alarm has no impact on the system. However, the hardware resource usage may reach 100% if the resources continue to be consumed.
Cause 928: The number of BIERv6 Traffic Management Group Indexes (TMGIDs) exceeded 95% of the forwarding engine resource specification.
This alarm has no impact on the system. However, the hardware resource usage may reach 100% if the resources continue to be consumed.

Possible Causes

Cause 15: The percentage of ND indexes exceeded the upper threshold supported by the forwarding engine.
Cause 16: The percentage of tunnel indexes exceeded the upper threshold supported by the forwarding engine.
Cause 17: The percentage of BFD indexes exceeded the upper threshold supported by the forwarding engine.
Cause 18: The percentage of VPLS LearnIDs exceeded the upper threshold supported by the forwarding engine.
Cause 19: The percentage of broadcast domain indexes exceeded the upper threshold supported by the forwarding engine.
Cause 20: The percentage of NS indexes exceeded the upper threshold supported by the forwarding engine.
Cause 21: The percentage of ring indexes exceeded the upper threshold supported by the forwarding engine.
Cause 34: The percentage of BFD sessions exceeded the upper threshold supported by the device.
Cause 98: The number of globaltoken1 forwarding engine resources exceeded the threshold.
Cause 100: The number of globaltoken2 forwarding engine resources exceeded the threshold.
Cause 103: The percentage of AT indexes exceeded the upper threshold supported by the forwarding engine.
Cause 205: The percentage of LDP over TE LSPs exceeded the upper threshold supported by the device.
Cause 400: The number of IGP peers exceeded the upper threshold supported by the device.
Cause 401: The number of BGP peers exceeded the upper threshold supported by the device.
Cause 402: The number of LDP peers exceeded the upper threshold supported by the device.
Cause 403: The number of PIM peers exceeded the upper threshold supported by the device.
Cause 551: The number of TBTP resource exceeded 85% of the specification of the forwarding engine resources(the whole is 4K).
Cause 552: The number of TBTP resource exceeded 85% of the specification of the forwarding engine resources(the whole is16K).
Cause 582: The number of user exceeded the specification of the forwarding engine resources.
Cause 583: The number of Lac user exceeded the specification of the forwarding engine resources.
Cause 587: The number of user on card0 exceeded 90% of the specification of the forwarding engine resources.
Cause 588: The number of user on card1 exceeded the 90% of the specification of the forwarding engine resources
Cause 589: The number of user on card0 exceeded the specification of the forwarding engine resources.
Cause 590: The number of user on card1 exceeded the specification of the forwarding engine resources.
Cause 701: The number of system IPv4 multicast forwarding group exceeded 95% of the forwarding engine resources.
Cause 702: The number of system IPv6 multicast forwarding group exceeded 95% of the forwarding engine resources.
Cause 772: The number of BIER TMGIDs exceeded 95% of the forwarding engine resource specification.
Cause 928: The number of BIERv6 Traffic Management Group Indexes (TMGIDs) exceeded 95% of the forwarding engine resource specification.

Procedure

Cause 15: The percentage of ND indexes exceeded the upper threshold supported by the forwarding engine.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 16: The percentage of tunnel indexes exceeded the upper threshold supported by the forwarding engine.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 17: The percentage of BFD indexes exceeded the upper threshold supported by the forwarding engine.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 18: The percentage of VPLS LearnIDs exceeded the upper threshold supported by the forwarding engine.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 19: The percentage of broadcast domain indexes exceeded the upper threshold supported by the forwarding engine.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 20: The percentage of NS indexes exceeded the upper threshold supported by the forwarding engine.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 21: The percentage of ring indexes exceeded the upper threshold supported by the forwarding engine.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 34: The percentage of BFD sessions exceeded the upper threshold supported by the device.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 98: The number of globaltoken1 forwarding engine resources exceeded the threshold.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 100: The number of globaltoken2 forwarding engine resources exceeded the threshold.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 103: The percentage of AT indexes exceeded the upper threshold supported by the forwarding engine.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 205: The percentage of LDP over TE LSPs exceeded the upper threshold supported by the device.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 400: The number of IGP peers exceeded the upper threshold supported by the device.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 401: The number of BGP peers exceeded the upper threshold supported by the device.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 402: The number of LDP peers exceeded the upper threshold supported by the device.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 403: The number of PIM peers exceeded the upper threshold supported by the device.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 551: The number of TBTP resource exceeded 85% of the specification of the forwarding engine resources(the whole is 4K).
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 552: The number of TBTP resource exceeded 85% of the specification of the forwarding engine resources(the whole is16K).
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 582: The number of user exceeded the specification of the forwarding engine resources.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 583: The number of Lac user exceeded the specification of the forwarding engine resources.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 587: The number of user on card0 exceeded 90% of the specification of the forwarding engine resources.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 588: The number of user on card1 exceeded the 90% of the specification of the forwarding engine resources
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 589: The number of user on card0 exceeded the specification of the forwarding engine resources.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 590: The number of user on card1 exceeded the specification of the forwarding engine resources.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 701: The number of system IPv4 multicast forwarding group exceeded 95% of the forwarding engine resources.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 702: The number of system IPv6 multicast forwarding group exceeded 95% of the forwarding engine resources.
Collect alarm information and configuration information, and then contact technical support personnel.
Cause 772: The number of BIER TMGIDs exceeded 95% of the forwarding engine resource specification.
This alarm has no impact on the system.
Cause 928: The number of BIERv6 Traffic Management Group Indexes (TMGIDs) exceeded 95% of the forwarding engine resource specification.
This alarm has no impact on the system.