FIB_1.3.6.1.4.1.2011.5.25.227.2.1.1 hwWholeFwdResLack

Trap Buffer Description

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

If too many services are configured, alarms are generated when the specification of the whole device forwarding engine resources is exceeded.

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

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	SysfwdResourceOverload
Trap OID	1.3.6.1.4.1.2011.5.25.227.2.1.1
MIB	HUAWEI-FWD-RES-TRAP-MIB
Alarm ID	0x08710001
Alarm Name	SysfwdResourceOverload
Alarm Type	processingErrorAlarm
Raise or Clear	Raise
Match trap	FIB_1.3.6.1.4.1.2011.5.25.227.2.1.2 hwWholeFwdResLackResume

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 13: The number of forward tokens in the board space exceeded the specifications of the forwarding engine resources.
Cetain MPLS and VPLS service may be unavailable.
Cause 14: The number of FVRFs exceeded the specifications of the forwarding engine resources.
Certain VPN service may be unavailable.
Cause 15: The number of NDIndex exceeded the specifications of the forwarding engine resources.
Certain IPv6 service may be broken.
Cause 16: The number of Tunnel Index exceeded the specifications of the forwarding engine resources.
Certain service carried by tunnel may be broken.
Cause 17: The number of Bfd Index exceeded the specifications of the forwarding engine resources.
Certain BFD service may be broken.
Cause 18: The number of VPLS LearnId exceeded the specifications of the forwarding engine resources.
Certain VPLS service may be broken.
Cause 19: The number of broadcast domain Index exceeded the specifications of the forwarding engine resources.
Certain broadcast domain service may be broken.
Cause 20: The number of Ns Index exceeded the specifications of the forwarding engine resources.
Certain NetStream service may be broken.
Cause 21: The number of Ring Index exceeded the specifications of the forwarding engine resources.
Certain service carried by vlanIf may be broken.
Cause 22: The number of configured multicast replication services (for multicast and broadcast) exceeded the specification supported by the entire system.
Certain multicast replication services (multicast and broadcast) may be unavailable.
Cause 23: The number of downstream interfaces to which data (multicast, VLAN, and VPLS data) is replicated to exceeded the specification supported by the entire system.
Certain downstream interfaces to which data (multicast, VLAN, and VPLS data) is replicated to may be unavailable.
Cause 24: The number of TMGID exceeded the specification of the forwarding engine resources.
Certain multicast group cannot be established, and the multicast stream cannot be forwarded successfully.
Cause 25: The number of configured inter-board replication combinations was large and the number of configured multicast replication services (for multicast, VLAN, and VPLS) exceeded the specification supported by the entire system.
Certain multicast replication services(multicast,VLAN,and VPLS)may be unavailable.
Cause 26: The number of trill nhpIndex exceeded the specifications of the forwarding engine resources.
Cetain TRILL service may be unavailable.
Cause 29: The next hop resource usage for equal-cost routes has exceeded 90%.
Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.
Cause 31: The next hop resource usage has exceeded 90%.
Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.
Cause 34: The number of BFD sessions exceeded the specifications of the global bfd sessions.
Cannot establish more bfd session.
Cause 55: The number of Link Layer Encapsulation database exceeded the specification of the forwarding engine resources.
Service may be unavailable.
Cause 56: The number of Tunnel Encapsulation database exceeded the specification of the forwarding engine resources.
Service may be unavailable.
Cause 59: The number of Mac Multicast Index exceeded the specification of the forwarding engine resources.
Service may be unavailable.
Cause 60: The number of Virtual Ports exceeded the specification of the forwarding engine resources.
Service may be unavailable.
Cause 69: The number of Multicast Index exceeded the specification of the forwarding engine resources.
Service may be unavailable.
Cause 79: The number of global MAC Index exceeded the specification of the forwarding engine resources
Service may be unavailable.
Cause 93: The number of forward tokens in the system Global 1 space exceeded the specifications of the forwarding engine resources.
Cetain MPLS and VPLS service may be unavailable.
Cause 95: The number of forward tokens in the system Global 2 space exceeded the specifications of the forwarding engine resources.
Cetain MPLS and VPLS service may be unavailable.
Cause 103: The number of AT indexes exceeds the specifications of the forwarding engine resources.
Some IPv4 services are interrupted.
Cause 110: The number of global IP Index exceeded the specification of the forwarding engine resources
Service may be unavailable.
Cause 183: The number of L2VPN exceeds 90% of the specification of the resources.
The configuration of vlan service arrive 90% of the service spec. The service may not be affected. But if continue to add the service and arrive 100% of the service spec, certain configuration may not becom effective.
Cause 184: The number of Vlan exceeded the 90% of the resources
The configuration of vlan service arrive 90% of the service spec. The service may not be affected. But if continue to add the service and arrive 100% of the service spec, certain configuration may not becom effective.
Cause 185: The number of Bridge Domain exceeded the 90% of the resources
The configuration of BD service arrive 90% of the service spec. The service may not be affected. But if continue to add the service and arrive 100% of the service spec, certain configuration may not becom effective.
Cause 205: The number of LDP over TE lsps exceeded the specification supported by the entire system.
Some LDP over TE services may be unavaiable.
Cause 303: The number of system multicast forwarding group exceeded 95% of the forwarding engine resources.
The multicast forwarding group service arrive 95% of the service spec. The service may not be affected. But if continue to add the service and arrive 100% of the service spec, certain configuration may not becom effective.
Cause 324: The number of pbb evpn bmac exceeded the specification of the forwarding engine resources.
New bmac route are not avaliable.
Cause 404: The number of IGP peers exceeded the limit threshold supported by the device.
New bmac route are not avaliable.
Cause 405: The number of BGP peers exceeded the limit threshold supported by the device.
New bmac route are not avaliable.
Cause 406: The number of LDP peers exceeded the limit threshold supported by the device.
New bmac route are not avaliable.
Cause 407: The number of PIM peers exceeded the limit threshold supported by the device.
New bmac route are not avaliable.
Cause 408: The number of Multicast FRR exceeded the specification of the forwarding engine resources.
Certain multicast frr may be unavailable.
Cause 409: The number of Multicast FRR exceeded 95% of the specification of the forwarding engine resources
The multicast frr service arrive 95% of the service spec. The service may not be affected. But if continue to add the service and arrive 100% of the service spec, certain configuration may not becom effective.
Cause 410: The number of subscribed mac exceeded the specifications of the resources.
Impact subscribed mac.
Cause 549: The number of TBTP resource exceeded the specifications of the forwarding engine resources(the whole is 4K).
TBTP resource may not be enough.
Cause 550: The number of TBTP resource exceeded the specifications of the forwarding engine resources(the whole is 16K).
TBTP resource may not be enough.
Cause 605: No multicast forwarding table resource can be requested for Layer 2 multicast
Certain L2 multicast FIB entries cannot be delivered, resulting in interruption of some L2 multicast services or forwarding errors.
Cause 606: No multicast forwarding table resource can be requested for IPv6 Layer 2 multicast.
Certain IPv6 L2 multicast FIB entries cannot be delivered, resulting in interruption of some IPv6 L2 multicast services or forwarding errors.
Cause 611: The number of P2MP TE TMGID exceeded the specification of the forwarding engine resources.
Certain P2MP TE cannot be established, and the stream cannot be forwarded successfully.
Cause 612: The number of system P2MP TE TMGID exceeded 95% of the forwarding engine resources.
The P2MP TE service arrive 95% of the service spec. The service may not be affected. But if continue to add the service and arrive 100% of the service spec, certain configuration may not becom effective.
Cause 613: The number of MLDP TMGID exceeded the specification of the forwarding engine resources.
Certain MLDP cannot be established, and the stream cannot be forwarded successfully.
Cause 614: The number of system MLDP TMGID exceeded 95% of the forwarding engine resources.
The MLDP service arrive 95% of the service spec. The service may not be affected. But if continue to add the service and arrive 100% of the service spec, certain configuration may not becom effective.
Cause 615: The number of entries in the P2MP ELB select table exceeded the upper limit supported by the forwarding engine.
Some P2MP FRR functions fail.
Cause 616: The number of entries in the P2MP ELB select table exceeded 95% of the upper limit supported by the forwarding engine.
The number of FRR paths for P2MP TE or mLDP exceeded 95% of a specified upper limit. If more tunnels are configured and reach the upper limit, P2MP FRR fails in some scenarios.
Cause 704: No multicast forwarding table resource can be requested for IPv4 Layer 3 multicast.
Certain IPv4 multicast group cannot be established, and the multicast stream cannot be forwarded successfully.
Cause 705: No multicast forwarding table resource can be requested for IPv6 Layer 3 multicast.
Certain IPv6 multicast group cannot be established, and the multicast stream cannot be forwarded successfully.
Cause 706: The number of TBTP resource exceeded the specifications of the forwarding engine resources.
TBTP resource may not be enough.
Cause 769: The number of BIER tunnels exceeded the upper limit allowed by the device.
The loopback label cannot be obtained. As a result, traffic fails to be forwarded.
Cause 770: The number of BIER TMGIDs exceeded the specification of the forwarding engine resources.
TMGIDs cannot be allocated. As a result, traffic fails to be forwarded.
Cause 814: No multicast forwarding table resource can be requested for broadcast trunk load balancing services.
Some broadcast trunk load balancing services cannot be balanced.
Cause 815: No multicast forwarding table resource can be requested for VLAN-based IPv4 Layer 2 multicast routers' interfaces.
Multicast traffic of some VLAN-based IPv4 Layer 2 multicast groups cannot be properly forwarded.
Cause 816: No multicast forwarding table resource can be requested for VSI-based IPv4 Layer 2 multicast routers' interfaces.
Multicast traffic of some VSI-based IPv4 Layer 2 multicast groups cannot be properly forwarded.
Cause 817: No multicast forwarding table resource can be requested for BD-based IPv4 Layer 2 multicast routers' interfaces.
Multicast traffic of some BD-based IPv4 Layer 2 multicast groups cannot be properly forwarded.
Cause 818: No multicast forwarding table resource can be requested for IPv4 Layer 2 multicast PW redundancy protocol packets.
Some IPv4 Layer 2 multicast PW redundancy protocol packets cannot be properly forwarded.
Cause 819: No multicast forwarding table resource can be requested for the PIM FRR backup multicast group.
Some PIM FRR functions fail to take effect, and multicast groups' traffic cannot be fast switched through PIM FRR.
Cause 820: No multicast forwarding table resource can be requested for VLAN-based IPv6 Layer 2 multicast routers' interfaces.
Multicast traffic of some VLAN-based IPv6 Layer 2 multicast groups cannot be properly forwarded.
Cause 821: No multicast forwarding table resource can be requested for VSI-based IPv6 Layer 2 multicast routers' interfaces.
Multicast traffic of some VSI-based IPv6 Layer 2 multicast groups cannot be properly forwarded.
Cause 822: No multicast forwarding table resource can be requested for multicast groups in the broadcast domain when the outbound interface of IPv4 Layer 2 multicast protocol packets is a QinQ stacking/mapping interface.
When the outbound interface of IPv4 Layer 2 multicast protocol packets is a QinQ stacking/mapping interface, some IPv4 Layer 2 multicast protocol packets cannot be broadcast to QinQ stacking/mapping interfaces.
Cause 823: No multicast forwarding table resource can be requested for BRAS multicast protocol packet hardware replication.
Some BRAS multicast protocol packets cannot be properly forwarded.
Cause 824: No multicast forwarding table resource can be requested for multicast NAT.
Traffic of some multicast NAT multicast groups cannot be properly forwarded.
Cause 825: No multicast forwarding table resource can be requested for DSVPNs.
Some DSVPN traffic cannot be properly forwarded.
Cause 826: No broadcast forwarding table resource can be requested for BDs.
Broadcast traffic of some BD services cannot be properly forwarded.
Cause 827: No broadcast forwarding table resource can be requested for Layer 2 protocol hardware replication.
Some Layer 2 protocol hardware replication packets cannot be properly forwarded.
Cause 828: No broadcast forwarding table resource can be requested for VLANs.
Broadcast traffic of some VLAN services cannot be properly forwarded.
Cause 829: No broadcast forwarding table resource can be requested for L2VPNs.
Broadcast traffic of some L2VPN services cannot be properly forwarded.
Cause 830: No broadcast forwarding table resource can be requested for L2VPN APS.
Some L2VPN APS services cannot be normally forwarded.
Cause 927: The number of BIERv6 Traffic Management Group Indexes (TMGIDs) exceeded the specification of the forwarding engine resources.
TMGIDs cannot be allocated. As a result, traffic fails to be forwarded.

Possible Causes

Cause 13: The number of forward tokens in the board space exceeded the specifications of the forwarding engine resources.
Cause 14: The number of FVRFs exceeded the specifications of the forwarding engine resources.
Cause 15: The number of NDIndex exceeded the specifications of the forwarding engine resources.
Cause 16: The number of Tunnel Index exceeded the specifications of the forwarding engine resources.
Cause 17: The number of Bfd Index exceeded the specifications of the forwarding engine resources.
Cause 18: The number of VPLS LearnId exceeded the specifications of the forwarding engine resources.
Cause 19: The number of broadcast domain Index exceeded the specifications of the forwarding engine resources.
Cause 20: The number of Ns Index exceeded the specifications of the forwarding engine resources.
Cause 21: The number of Ring Index exceeded the specifications of the forwarding engine resources.
Cause 22: The number of configured multicast replication services (for multicast and broadcast) exceeded the specification supported by the entire system.
Cause 23: The number of downstream interfaces to which data (multicast, VLAN, and VPLS data) is replicated to exceeded the specification supported by the entire system.
Cause 24: The number of TMGID exceeded the specification of the forwarding engine resources.
Cause 25: The number of configured inter-board replication combinations was large and the number of configured multicast replication services (for multicast, VLAN, and VPLS) exceeded the specification supported by the entire system.
Cause 26: The number of trill nhpIndex exceeded the specifications of the forwarding engine resources.
Cause 29: The next hop resource usage for equal-cost routes has exceeded 90%.
Cause 31: The next hop resource usage has exceeded 90%.
Cause 34: The number of BFD sessions exceeded the specifications of the global bfd sessions.
Cause 55: The number of Link Layer Encapsulation database exceeded the specification of the forwarding engine resources.
Cause 56: The number of Tunnel Encapsulation database exceeded the specification of the forwarding engine resources.
Cause 59: The number of Mac Multicast Index exceeded the specification of the forwarding engine resources.
Cause 60: The number of Virtual Ports exceeded the specification of the forwarding engine resources.
Cause 69: The number of Multicast Index exceeded the specification of the forwarding engine resources.
Cause 79: The number of global MAC Index exceeded the specification of the forwarding engine resources
Cause 93: The number of forward tokens in the system Global 1 space exceeded the specifications of the forwarding engine resources.
Cause 95: The number of forward tokens in the system Global 2 space exceeded the specifications of the forwarding engine resources.
Cause 103: The number of AT indexes exceeds the specifications of the forwarding engine resources.
Cause 110: The number of global IP Index exceeded the specification of the forwarding engine resources
Cause 183: The number of L2VPN exceeds 90% of the specification of the resources.
Cause 184: The number of Vlan exceeded the 90% of the resources
Cause 185: The number of Bridge Domain exceeded the 90% of the resources
Cause 205: The number of LDP over TE lsps exceeded the specification supported by the entire system.
Cause 303: The number of system multicast forwarding group exceeded 95% of the forwarding engine resources.
Cause 324: The number of pbb evpn bmac exceeded the specification of the forwarding engine resources.
Cause 404: The number of IGP peers exceeded the limit threshold supported by the device.
Cause 405: The number of BGP peers exceeded the limit threshold supported by the device.
Cause 406: The number of LDP peers exceeded the limit threshold supported by the device.
Cause 407: The number of PIM peers exceeded the limit threshold supported by the device.
Cause 408: The number of Multicast FRR exceeded the specification of the forwarding engine resources.
Cause 409: The number of Multicast FRR exceeded 95% of the specification of the forwarding engine resources
Cause 410: The number of subscribed mac exceeded the specifications of the resources.
Cause 549: The number of TBTP resource exceeded the specifications of the forwarding engine resources(the whole is 4K).
Cause 550: The number of TBTP resource exceeded the specifications of the forwarding engine resources(the whole is 16K).
Cause 605: No multicast forwarding table resource can be requested for Layer 2 multicast
Cause 606: No multicast forwarding table resource can be requested for IPv6 Layer 2 multicast.
Cause 611: The number of P2MP TE TMGID exceeded the specification of the forwarding engine resources.
Cause 612: The number of system P2MP TE TMGID exceeded 95% of the forwarding engine resources.
Cause 613: The number of MLDP TMGID exceeded the specification of the forwarding engine resources.
Cause 614: The number of system MLDP TMGID exceeded 95% of the forwarding engine resources.
Cause 615: The number of entries in the P2MP ELB select table exceeded the upper limit supported by the forwarding engine.
Cause 616: The number of entries in the P2MP ELB select table exceeded 95% of the upper limit supported by the forwarding engine.
Cause 704: No multicast forwarding table resource can be requested for IPv4 Layer 3 multicast.
Cause 705: No multicast forwarding table resource can be requested for IPv6 Layer 3 multicast.
Cause 706: The number of TBTP resource exceeded the specifications of the forwarding engine resources.
Cause 769: The number of BIER tunnels exceeded the upper limit allowed by the device.
Cause 770: The number of BIER TMGIDs exceeded the specification of the forwarding engine resources.
Cause 814: No multicast forwarding table resource can be requested for broadcast trunk load balancing services.
Cause 815: No multicast forwarding table resource can be requested for VLAN-based IPv4 Layer 2 multicast routers' interfaces.
Cause 816: No multicast forwarding table resource can be requested for VSI-based IPv4 Layer 2 multicast routers' interfaces.
Cause 817: No multicast forwarding table resource can be requested for BD-based IPv4 Layer 2 multicast routers' interfaces.
Cause 818: No multicast forwarding table resource can be requested for IPv4 Layer 2 multicast PW redundancy protocol packets.
Cause 819: No multicast forwarding table resource can be requested for the PIM FRR backup multicast group.
Cause 820: No multicast forwarding table resource can be requested for VLAN-based IPv6 Layer 2 multicast routers' interfaces.
Cause 821: No multicast forwarding table resource can be requested for VSI-based IPv6 Layer 2 multicast routers' interfaces.
Cause 822: No multicast forwarding table resource can be requested for multicast groups in the broadcast domain when the outbound interface of IPv4 Layer 2 multicast protocol packets is a QinQ stacking/mapping interface.
Cause 823: No multicast forwarding table resource can be requested for BRAS multicast protocol packet hardware replication.
Cause 824: No multicast forwarding table resource can be requested for multicast NAT.
Cause 825: No multicast forwarding table resource can be requested for DSVPNs.
Cause 826: No broadcast forwarding table resource can be requested for BDs.
Cause 827: No broadcast forwarding table resource can be requested for Layer 2 protocol hardware replication.
Cause 828: No broadcast forwarding table resource can be requested for VLANs.
Cause 829: No broadcast forwarding table resource can be requested for L2VPNs.
Cause 830: No broadcast forwarding table resource can be requested for L2VPN APS.
Cause 927: The number of BIERv6 Traffic Management Group Indexes (TMGIDs) exceeded the specification of the forwarding engine resources.

Procedure

Cause 13: The number of forward tokens in the board space exceeded the specifications of the forwarding engine resources.
Please contact technical support personnel.
Cause 14: The number of FVRFs exceeded the specifications of the forwarding engine resources.
Please contact technical support personnel.
Cause 15: The number of NDIndex exceeded the specifications of the forwarding engine resources.
Please contact technical support personnel.
Cause 16: The number of Tunnel Index exceeded the specifications of the forwarding engine resources.
Please contact technical support personnel.
Cause 17: The number of Bfd Index exceeded the specifications of the forwarding engine resources.
Please contact technical support personnel.
Cause 18: The number of VPLS LearnId exceeded the specifications of the forwarding engine resources.
Please contact technical support personnel.
Cause 19: The number of broadcast domain Index exceeded the specifications of the forwarding engine resources.
Please contact technical support personnel.
Cause 20: The number of Ns Index exceeded the specifications of the forwarding engine resources.
Please contact technical support personnel.
Cause 21: The number of Ring Index exceeded the specifications of the forwarding engine resources.
Please contact technical support personnel.
Cause 22: The number of configured multicast replication services (for multicast and broadcast) exceeded the specification supported by the entire system.
Please contact technical support personnel.
Cause 23: The number of downstream interfaces to which data (multicast, VLAN, and VPLS data) is replicated to exceeded the specification supported by the entire system.
Please contact technical support personnel.
Cause 24: The number of TMGID exceeded the specification of the forwarding engine resources.
Please contact technical support personnel.
Cause 25: The number of configured inter-board replication combinations was large and the number of configured multicast replication services (for multicast, VLAN, and VPLS) exceeded the specification supported by the entire system.
Deleting some existing multicast replication service instances may not clear this alarm. Collect the alarm, log, and configuration information, and contact technical support personnel.
Cause 26: The number of trill nhpIndex exceeded the specifications of the forwarding engine resources.
Please contact technical support personnel.
Cause 29: The next hop resource usage for equal-cost routes has exceeded 90%.
Please contact technical support personnel.
Cause 31: The next hop resource usage has exceeded 90%.
Please contact technical support personnel.
Cause 34: The number of BFD sessions exceeded the specifications of the global bfd sessions.
Please contact technical support personnel.
Cause 55: The number of Link Layer Encapsulation database exceeded the specification of the forwarding engine resources.
Please contact technical support personnel.
Cause 56: The number of Tunnel Encapsulation database exceeded the specification of the forwarding engine resources.
Please contact technical support personnel.
Cause 59: The number of Mac Multicast Index exceeded the specification of the forwarding engine resources.
Please contact technical support personnel.
Cause 60: The number of Virtual Ports exceeded the specification of the forwarding engine resources.
Please contact technical support personnel.
Cause 69: The number of Multicast Index exceeded the specification of the forwarding engine resources.
Please contact technical support personnel.
Cause 79: The number of global MAC Index exceeded the specification of the forwarding engine resources
Please contact technical support personnel.
Cause 93: The number of forward tokens in the system Global 1 space exceeded the specifications of the forwarding engine resources.
Please contact technical support personnel.
Cause 95: The number of forward tokens in the system Global 2 space exceeded the specifications of the forwarding engine resources.
Please contact technical support personnel.
Cause 103: The number of AT indexes exceeds the specifications of the forwarding engine resources.
Please contact technical support personnel.
Cause 110: The number of global IP Index exceeded the specification of the forwarding engine resources
Please contact technical support personnel.
Cause 183: The number of L2VPN exceeds 90% of the specification of the resources.
Please contact technical support personnel.
Cause 184: The number of Vlan exceeded the 90% of the resources
Please contact technical support personnel.
Cause 185: The number of Bridge Domain exceeded the 90% of the resources
Please contact technical support personnel.
Cause 205: The number of LDP over TE lsps exceeded the specification supported by the entire system.
Please contact technical support personnel.
Cause 303: The number of system multicast forwarding group exceeded 95% of the forwarding engine resources.
Please contact technical support personnel.
Cause 324: The number of pbb evpn bmac exceeded the specification of the forwarding engine resources.
Please contact technical support personnel.
Cause 404: The number of IGP peers exceeded the limit threshold supported by the device.
Please contact technical support personnel.
Cause 405: The number of BGP peers exceeded the limit threshold supported by the device.
Please contact technical support personnel.
Cause 406: The number of LDP peers exceeded the limit threshold supported by the device.
Please contact technical support personnel.
Cause 407: The number of PIM peers exceeded the limit threshold supported by the device.
Please contact technical support personnel.
Cause 408: The number of Multicast FRR exceeded the specification of the forwarding engine resources.
Please contact technical support personnel.
Cause 409: The number of Multicast FRR exceeded 95% of the specification of the forwarding engine resources
Please contact technical support personnel.
Cause 410: The number of subscribed mac exceeded the specifications of the resources.
Please contact technical support personnel.
Cause 549: The number of TBTP resource exceeded the specifications of the forwarding engine resources(the whole is 4K).
Please contact technical support personnel.
Cause 550: The number of TBTP resource exceeded the specifications of the forwarding engine resources(the whole is 16K).
Please contact technical support personnel.
Cause 605: No multicast forwarding table resource can be requested for Layer 2 multicast
Please contact technical support personnel.
Cause 606: No multicast forwarding table resource can be requested for IPv6 Layer 2 multicast.
Please contact technical support personnel.
Cause 611: The number of P2MP TE TMGID exceeded the specification of the forwarding engine resources.
Check whether The P2MP TE service exceeds the service spec. If yes, please delete unneeded P2MP TE configurations.
Cause 612: The number of system P2MP TE TMGID exceeded 95% of the forwarding engine resources.
The P2MP TE service arrive 95% of the service spec. The service may not be affected. Please plan the P2MP TE services properly.
Cause 613: The number of MLDP TMGID exceeded the specification of the forwarding engine resources.
Check whether The MLDP service exceeds the service spec. If yes, please delete unneeded MLDP configurations.
Cause 614: The number of system MLDP TMGID exceeded 95% of the forwarding engine resources.
The MLDP service arrive 95% of the service spec. The service may not be affected. Please plan the MLDP services properly.
Cause 615: The number of entries in the P2MP ELB select table exceeded the upper limit supported by the forwarding engine.
1. Check P2MP TE and mLDP configuration and determine whether the number of FRR paths for P2MP TE or mLDP exceeded a specified upper limit.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary IPv6 multicast groups. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 616: The number of entries in the P2MP ELB select table exceeded 95% of the upper limit supported by the forwarding engine.
1. Check P2MP TE and mLDP configuration and determine whether the number of FRR paths for P2MP TE or mLDP exceeded 95% of a specified upper limit.
- If yes, go to Step 2.
- If no, go to Step 3.
2. The functions are not affected temporarily. Properly plan P2MP tunnels.

3. Collect trap, log, and configuration information, and contact technical support personnel.
Cause 704: No multicast forwarding table resource can be requested for IPv4 Layer 3 multicast.
1. Check whether the number of IPv4 multicast groups exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary IPv4 multicast groups. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 705: No multicast forwarding table resource can be requested for IPv6 Layer 3 multicast.
1. Check whether the number of IPv6 multicast groups exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary IPv6 multicast groups. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 706: The number of TBTP resource exceeded the specifications of the forwarding engine resources.
Please contact technical support personnel.
Cause 769: The number of BIER tunnels exceeded the upper limit allowed by the device.
1. Check whether the number of configured BIER tunnels exceeds the upper limit allowed by the device.
- If yes, go to step 2.
- If no, go to step 3.
2. Delete unnecessary BIER tunnels.
- If the alarm is cleared, go to step 4.
- If the alarm persists, go to step 3.
3. Collect alarm, log, and configuration information, and contact Huawei technical support personnel.

4. End.
Cause 770: The number of BIER TMGIDs exceeded the specification of the forwarding engine resources.
1. Check whether the number of BIER multicast groups exceeds the upper limit.
- If yes, go to step 2.
- If no, go to step 3.
2. Reduce the number of BIER multicast groups.
- If the alarm is cleared, go to step 4.
- If the alarm persists, go to step 3.
3. Collect alarm, log, and configuration information, and contact Huawei technical support personnel.

4. End.
Cause 814: No multicast forwarding table resource can be requested for broadcast trunk load balancing services.
1. Check whether the number of multicast groups for broadcast trunk load balancing services exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary multicast groups for broadcast trunk load balancing services. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 815: No multicast forwarding table resource can be requested for VLAN-based IPv4 Layer 2 multicast routers' interfaces.
1. Check whether the number of multicast groups for VLAN-based IPv4 Layer 2 multicast routers' interfaces exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary multicast groups for VLAN-based IPv4 Layer 2 multicast routers' interfaces. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 816: No multicast forwarding table resource can be requested for VSI-based IPv4 Layer 2 multicast routers' interfaces.
1. Check whether the number of multicast groups for VSI-based IPv4 Layer 2 multicast routers' interfaces exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary multicast groups for VSI-based IPv4 Layer 2 multicast routers' interfaces. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 817: No multicast forwarding table resource can be requested for BD-based IPv4 Layer 2 multicast routers' interfaces.
1. Check whether the number of multicast groups for BD-based IPv4 Layer 2 multicast routers' interfaces exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary multicast groups for BD-based IPv4 Layer 2 multicast routers' interfaces. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 818: No multicast forwarding table resource can be requested for IPv4 Layer 2 multicast PW redundancy protocol packets.
1. Check whether the number of multicast groups for IPv4 Layer 2 multicast PW redundancy protocol packets exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary multicast groups for IPv4 Layer 2 multicast PW redundancy protocol packets. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 819: No multicast forwarding table resource can be requested for the PIM FRR backup multicast group.
1. Check whether the number of PIM FRR backup multicast groups exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary PIM FRR backup multicast groups. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 820: No multicast forwarding table resource can be requested for VLAN-based IPv6 Layer 2 multicast routers' interfaces.
1. Check whether the number of multicast groups for VLAN-based IPv6 Layer 2 multicast routers' interfaces exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary multicast groups for VLAN-based IPv6 Layer 2 multicast routers' interfaces. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 821: No multicast forwarding table resource can be requested for VSI-based IPv6 Layer 2 multicast routers' interfaces.
1. Check whether the number of multicast groups for VSI-based IPv6 Layer 2 multicast routers' interfaces exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary multicast groups for VSI-based IPv6 Layer 2 multicast routers' interfaces. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 822: No multicast forwarding table resource can be requested for multicast groups in the broadcast domain when the outbound interface of IPv4 Layer 2 multicast protocol packets is a QinQ stacking/mapping interface.
1. Check whether the number of multicast groups for the IPv4 Layer 2 multicast protocol packets whose outbound interface is a QinQ stacking/mapping interface exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary multicast groups for the IPv4 Layer 2 multicast protocol packets whose outbound interface is a QinQ stacking/mapping interface. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 823: No multicast forwarding table resource can be requested for BRAS multicast protocol packet hardware replication.
1. Check whether the number of multicast groups for BRAS multicast protocol packet hardware replication exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary multicast groups for BRAS multicast protocol packet hardware replication exceeds the specification. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 824: No multicast forwarding table resource can be requested for multicast NAT.
1. Check whether the number of multicast groups for multicast NAT exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary multicast groups for multicast NAT exceeds the specification. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 825: No multicast forwarding table resource can be requested for DSVPNs.
1. Check whether the number of multicast groups for DSVPNs exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary multicast groups for DSVPNs. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 826: No broadcast forwarding table resource can be requested for BDs.
1. Check whether the number of broadcast groups for BD services exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary broadcast groups for BD services. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 827: No broadcast forwarding table resource can be requested for Layer 2 protocol hardware replication.
1. Check whether the number of broadcast groups for Layer 2 protocol hardware replication exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary broadcast groups for Layer 2 protocol hardware replication. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 828: No broadcast forwarding table resource can be requested for VLANs.
1. Check whether the number of broadcast groups for VLAN services exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary broadcast groups for VLAN services. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 829: No broadcast forwarding table resource can be requested for L2VPNs.
1. Check whether the number of broadcast groups for L2VPN services exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary broadcast groups for L2VPN services. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 830: No broadcast forwarding table resource can be requested for L2VPN APS.
1. Check whether the number of broadcast groups for L2VPN APS services exceeds the specification.
- If yes, go to Step 2.
- If no, go to Step 3.
2. Delete unnecessary broadcast groups for L2VPN APS services. Then, check whether the alarm is cleared.
- If the alarm is cleared, go to Step 4.
- If the alarm persists, go to Step 3.
3. Collect trap, log, and configuration information, and contact technical support personnel.

4. End.
Cause 927: The number of BIERv6 Traffic Management Group Indexes (TMGIDs) exceeded the specification of the forwarding engine resources.
1. Check whether the number of BIERv6 multicast groups exceeds the upper limit.
- If yes, go to step 2.
- If no, go to step 3.
2. Reduce the number of BIERv6 multicast groups.
- If the alarm is cleared, go to step 4.
- If the alarm persists, go to step 3.
3. Collect alarm, log, and configuration information, and contact Huawei technical support personnel.

4. End.