FIB/2/hwLCfwdResourceOverload_active

Message

FIB/2/hwLCfwdResourceOverload_active: The board forwarding engine resources were overloaded. (EntityPhysicalIndex=[EntityPhysicalindex], EntPhysicalIndex=[EntPhysicalindex], EntPhysicalName=[EntPhysicalName], Slot=[SlotStr], Reason=[ReasonId], ReasonDescription=[Reason])

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

Description

The board forwarding engine resources were overloaded.

Parameters

Parameter Name Parameter Meaning

EntityPhysicalindex

Index of a physical entry

EntPhysicalindex

Index of a physical entry

EntPhysicalName

Name of a physical entry

SlotStr

Slot information

ReasonId

Possible cause of the trap

Reason

Detailed cause of the trap

Possible Causes

  • Cause 1: The number of established MPLS connections (TE) exceeded the specification of the forwarding engine resources
  • Cause 2: The number of IPv4 FIBs exceeded the specification of the forwarding engine resources
  • Cause 3: The number of IPv6 FIBs exceeded the specification of the forwarding engine resources
  • Cause 4: The number of ARPs exceeded the specification of the forwarding engine resources
  • Cause 5: The number of IPv6 NDs exceeded the specification of the forwarding engine resources
  • Cause 6: The number of enabled statistics exceeded the specification of the forwarding engine resources
  • Cause 7: The numbers of the applied traffic classification-based policies and CARs exceeded the specification of the forwarding resources
  • Cause 8: The number of established L2VPN connections exceeded the specifications of the forwarding engine resources
  • Cause 9: The number of multicast replication downstream interfaces exceeded the specification of the forwarding engine resources
  • Cause 10: The number of BFD ACLs exceeded the specification of the forwarding engine resources
  • Cause 11: The number of IPv4 multicast FIBs exceeded the specification of the forwarding engine resources
  • Cause 12: The number of IPv6 multicast FIBs exceeded the specification of the forwarding engine resources
  • 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 indexes exceeded the specifications of the forwarding engine resources
  • Cause 21: The number of Ring Index exceeded the specifications of the forwarding engine resources
  • Cause 25: The number of MLID exceeded the specification of the forwarding engine resources.
  • Cause 27: The host table prefix resource usage has exceeded 90%.
  • Cause 28: The route table prefix resource usage has exceeded 90%.
  • Cause 29: The next hop resource usage for equal-cost routes has exceeded 90%.
  • Cause 30: The Layer 3 interface table resource usage has exceeded 90%.
  • Cause 31: The next hop resource usage has exceeded 90%.
  • Cause 32: The tunnel decapsulation table resource usage has exceeded 90%.
  • Cause 33: The number of QINQ tag pairs exceeds the specification of the forwarding engine resources.
  • Cause 35: Certain IPv4 full rules cannot be delivered, resulting in interruption of some services refer to ipv4 full rulse lose efficacy.
  • Cause 36: Certain IPv4 mask rules cannot be delivered, causing involved services to fail to take effect.
  • Cause 37: Certain IPv6 full rules cannot be delivered, causing involved services to fail to take effect.
  • Cause 38: Certain IPv6 mask rules cannot be delivered, causing involved services to fail to take effect.
  • Cause 39: Certain characteristic code rules cannot be delivered, causing involved services to fail to take effect.
  • Cause 40: Certain complex rules cannot be delivered, causing involved services to fail to take effect.
  • Cause 41: Certain Tcp Flag rules cannot be delivered, causing involved services to fail to take effect.
  • Cause 42: The number of enabled ccm send numbers exceeded the specifications of the forwarding engine resources
  • Cause 43: The number of enabled ccm receive numbers exceeded the specifications of the forwarding engine resources
  • Cause 44: The number of enabled slm instance numbers exceeded the specifications of the forwarding engine resources
  • Cause 45: The number of enabled 1dm instance numbers exceeded the specifications of the forwarding engine resources
  • Cause 46: The number of enabled 2dm instance numbers exceeded the specifications of the forwarding engine resources
  • Cause 47: The IPv6 route table prefix resource usage has exceeded 90%.
  • Cause 48: The number of IPv4 multicast group flow statistic ID exceeded the specifications of the forwarding engine resources
  • Cause 49: The number of IPv6 multicast group flow statistic ID exceeded the specifications of the forwarding engine resources
  • Cause 50: The number of nhp numbers exceeded the specifications of the forwarding engine resources
  • Cause 51: The number of netstream Index numbers exceeded the specifications of the forwarding engine resources
  • Cause 52: The number of enabled dlm instance numbers exceeded the specifications of the forwarding engine resources
  • Cause 53: The number of IPv4 BGP statistic ID exceeded the specifications of the forwarding engine resources
  • Cause 54: The number of IPv6 bgp statistic ID exceeded the specifications of the forwarding engine resources
  • Cause 55: The number of Link Layer Encapsulation database exceeded the specification of the forwarding engine resources
  • Cause 57: The number of Large Exactly Match database exceeded the specification of the forwarding engine resources
  • Cause 58: The number of Logical Interfaces 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 61: The number of applied BGPFLOW VTCAM resources exceeded the specification of the forwarding engine resources
  • Cause 62: The number of ACL Group exceeded the specification of the forwarding engine resources
  • Cause 63: The number of Meter exceeded the specification of the forwarding engine resources
  • Cause 64: The number of Counter exceeded the specification of the forwarding engine resources
  • Cause 65: The number of Outbound ACL Entry exceeded the specification of the forwarding engine resources
  • Cause 66: The number of Outbound ACL Group exceeded the specification of the forwarding engine resources
  • Cause 67: The number of Outbound Meter exceeded the specification of the forwarding engine resources
  • Cause 68: The number of Outbound Counter exceeded the specification of the forwarding engine resources
  • Cause 69: The number of Multicast Index exceeded the specification of the forwarding engine resources
  • Cause 70: The number of IPFPM loss-measure continual enable or delay-measure continual enable numbers exceeded the specifications of the forwarding engine resources.
  • Cause 71: The number of bind table exceeded the specifications of the forwarding engine resources.
  • Cause 72: ACL failed to be delivered.
  • Cause 73: The number of ARP entries exceeded 95% of the forwarding engine's resource specification.
  • Cause 103: The number of AT indexes exceeds the specifications of the forwarding engine resources.
  • Cause 104: The number of flexible access sub-interfaces exceeds the specification of the forwarding engine resources.
  • Cause 105: The number of Inbound flow-wred exceeded the specification of the forwarding engine resources
  • Cause 106: The number of Outbound flow-wred exceeded the specification of the forwarding engine resources
  • Cause 109: The number of Inbound flow-queue wfq exceeded the specification of the forwarding engine resources.
  • Cause 110: The number of Outbound flow-queue wfq exceeded the specification of the forwarding engine resources.
  • Cause 111: The number of Inbound flow-queue cbs exceeded the specification of the forwarding engine resources.
  • Cause 112: The number of Outbound flow-queue cbs exceeded the specification of the forwarding engine resources.
  • Cause 113: The number of Inbound flow-queue pbs exceeded the specification of the forwarding engine resources.
  • Cause 114: The number of Outbound flow-queue pbs exceeded the specification of the forwarding engine resources.
  • Cause 115: The number of Inbound user-queue exceeded the specification of the forwarding engine resources.
  • Cause 116: The number of Outbound user-queue exceeded the specification of the forwarding engine resources.
  • Cause 117: The number of Inbound user-queue template exceeded the specification of the forwarding engine resources.
  • Cause 118: The number of Outbound user-queue template exceeded the specification of the forwarding engine resources.
  • Cause 119: The number of Inbound service-template exceeded the specification of the forwarding engine resources.
  • Cause 120: The number of Outbound service-template exceeded the specification of the forwarding engine resources.
  • Cause 121: The number of Inbound user-group-queue exceeded the specification of the forwarding engine resources.
  • Cause 122: The number of Outbound user-group-queue exceeded the specification of the forwarding engine resources.
  • Cause 123: The number of Inbound user-group-queue template exceeded the specification of the forwarding engine resources.
  • Cause 124: The number of Outbound user-group-queue template exceeded the specification of the forwarding engine resources.
  • Cause 125: The number of CAR IDs for upstream traffic exceeded the forwarding engine resource specification.
  • Cause 126: The number of CAR IDs for downstream traffic exceeded the forwarding engine resource specification.
  • Cause 127: The number of CAR remark templates for upstream traffic exceeded the forwarding engine resource specification.
  • Cause 128: The number of CAR remark templates for downstream traffic exceeded the forwarding engine resource specification.
  • Cause 129: The number of GIDs exceeded the forwarding engine resource specification.
  • Cause 130: The number of flow CAR indexes for upstream traffic exceeded the forwarding engine resource specification.
  • Cause 131: The number of flow CAR indexes for downstream traffic exceeded the forwarding engine resource specification.
  • Cause 132: The number of Behavior RE exceeded the specification of the forwarding engine resources.
  • Cause 133: The number of Behavior NHP exceeded the specification of the forwarding engine resources.
  • Cause 134: The number of IPv4 TCAM indexes for upstream traffic exceeded the forwarding engine resource specification.
  • Cause 135: The number of IPv6 TCAM indexes for upstream traffic exceeded the forwarding engine resource specification.
  • Cause 136: The number of IPv4 TCAM indexes for downstream traffic exceeded the forwarding engine resource specification.
  • Cause 137: The number of IPv6 TCAM indexes for downstream traffic exceeded the forwarding engine resource specification.
  • Cause 138: The number of Inbound Qppb car exceeded the specification of the forwarding engine resources.
  • Cause 139: The number of Outbound Qppb car exceeded the specification of the forwarding engine resources.
  • Cause 140: The number of Inbound Mirror table exceeded the specification of the forwarding engine resources.
  • Cause 141: The number of Outbound Mirror table exceeded the specification of the forwarding engine resources.
  • Cause 142: The number of Inbound Capture packet mirror table exceeded the specification of the forwarding engine resources.
  • Cause 143: The number of Outbound Capture Packet mirror table exceeded the specification of the forwarding engine resources.
  • Cause 144: The number of inbound suppression car exceeded the specification of the forwarding engine resources.
  • Cause 145: The number of outbound suppression car exceeded the specification of the forwarding engine resources.
  • Cause 146: The number of Inbound mirror car exceeded the specification of the forwarding engine resources.
  • Cause 147: The number of Outbound mirror car exceeded the specification of the forwarding engine resources.
  • Cause 148: The number of Behavior nst exceeded the specification of the forwarding engine resources.
  • Cause 149: The number of Inbound Profile Suppression car exceeded the specification of the forwarding engine resources.
  • Cause 150: The number of Outbound Profile Suppression car exceeded the specification of the forwarding engine resources.
  • Cause 151: The number of Inbound Profile Suppression car stat exceeded the specification of the forwarding engine resources.
  • Cause 152: The number of Outbound Profile Suppression car stat exceeded the specification of the forwarding engine resources.
  • Cause 153: The number of Inbound Profile single car exceeded the specification of the forwarding engine resources.
  • Cause 154: The number of Outbound Profile single car exceeded the specification of the forwarding engine resources.
  • Cause 155: The number of inbound profile single car stat exceeded the specification of the forwarding engine resources.
  • Cause 156: The number of outbound profile single car stat exceeded the specification of the forwarding engine resources.
  • Cause 157: The number of ACL statistics indexes for upstream traffic exceeded the forwarding engine resource specification.
  • Cause 158: The number of ACL statistics indexes for downstream traffic exceeded the forwarding engine resource specification.
  • Cause 159: The number of ACL CAR statistics indexes exceeded the forwarding engine resource specification.
  • Cause 160: The number of CAR statistics indexes for upstream traffic exceeded the forwarding engine resource specification.
  • Cause 161: The number of CAR statistics indexes for downstream traffic exceeded the forwarding engine resource specification.
  • Cause 162: The number of L2 TCAM indexes for upstream traffic exceeded the forwarding engine resource specification.
  • Cause 163: The number of L2 TCAM indexes for downstream traffic exceeded the forwarding engine resource specification.
  • Cause 165: The number of MPLS ARP table numbers exceeded the specifications of the forwarding engine resources
  • Cause 166: The number of MPLS ARP table numbers exceeded the threshold of the forwarding resources
  • Cause 167: The number of the Layer 2 traffic suppression statistic exceeds the specification of the forwarding engine resources
  • Cause 169: The number of SNOOP exceeded the specifications of the forwarding engine resources
  • Cause 176: The trunk loadbalance dynamic adjustment resource usage has exceeded 90%.
  • Cause 177: The number of Flexible Access exceeds 90% of the specification of the forwarding engine resources.
  • Cause 178: The number of Main and Subif exceeds 90% of the specification of the forwarding engine resources.
  • Cause 179: The number of DCN statistics exceeds 90% of the specification of the forwarding engine resources.
  • Cause 180: The number of Statistics exceeds 90% of the specification of the forwarding engine resources.
  • Cause 181: The number of EOAM exceeded the 90% of the forwarding engine resources.
  • Cause 182: The number of Y.1564 exceeded 90% of the specification of the forwarding engine resources.
  • Cause 183: The number of L2VPN exceeds 90% of the specification of the forwarding engine resources.
  • Cause 184: The number of Vlan exceeded the 90% of the forwarding engine resources
  • Cause 185: The number of Bridge Domain exceeded the 90% of the forwarding engine resources
  • Cause 186: The number of VRRP resource usage has exceeded 90%
  • Cause 187: The number of TWAMP resource usage has exceeded 90%
  • Cause 188: The number of BFD resource usage has exceeded 90%
  • Cause 189: The number of QINQ tag pairs exceeds 90% of the specification of the forwarding engine resources.
  • Cause 190: The number of EVC exceeds 90% of the specification of the forwarding engine resources.
  • Cause 191: The number of Inbound BehaviorSuppCar id exceeded the specification of the forwarding engine resources.
  • Cause 192: The number of Outbound BehaviorSuppCar id exceeded the specification of the forwarding engine resources.
  • Cause 193: The number of QPPB ACL Entry exceeded the specification of the forwarding engine resources.
  • Cause 194: The number of QPPB Gid exceeded the specification of the forwarding engine resources.
  • Cause 195: The tunnel decapsulation table resource exceeded the specifications of the forwarding engine resources.
  • Cause 196: The number of IPFPM exceeded 90% of the specification of the forwarding engine resources.
  • Cause 197: The number of RFC2544 exceeded 90% of the specification of the forwarding engine resources.
  • Cause 198: The number of available NHP entries was insufficient, and the dynamic load balancing adjustment result became ineffective.
  • Cause 199: The number of the Layer 2 traffic suppression statistic exceeds 90% of the specification of the forwarding engine resources.
  • Cause 200: The trunk loadbalance dynamic adjustment resource usage has exceeded 90%.
  • Cause 201: The number of linear-RE index exceeded the specification of the forwarding engine resources.
  • Cause 202: The numbers of the applied CP IPv4 ACL exceeded the specification of the forwarding resources.
  • Cause 203: The numbers of the applied CP IPv6 ACL exceeded the specification of the forwarding resources.
  • Cause 241: The number of DP exceeded the specification of the forwarding engine resources.
  • Cause 242: The number of inbound GQ shaper exceeded the specification of the forwarding engine resources.
  • Cause 243: The number of outbound GQ shaper exceeded the specification of the forwarding engine resources.
  • Cause 244: The number of inbound VI exceeded the specification of the forwarding engine resources.
  • Cause 245: The number of outbound VI exceeded the specification of the forwarding engine resources.
  • Cause 246: The number of inbound VI shaper exceeded the specification of the forwarding engine resources.
  • Cause 247: The number of outbound VI shaper exceeded the specification of the forwarding engine resources.
  • Cause 248: The number of inbound VI template exceeded the specification of the forwarding engine resources.
  • Cause 249: The number of outbound VI template exceeded the specification of the forwarding engine resources.
  • Cause 250: The number of port-wred exceeded the specification of the forwarding engine resources.
  • Cause 253: The number of pop-go RE exceeded the specification of the forwarding engine resources.
  • Cause 255: The number of APS exceeds 90% of the specification of the forwarding engine resources.
  • Cause 256: The number of MPLS OAM/TPOAM exceeds 90% of the specification of the forwarding engine resources.
  • Cause 257: The number of inbound chip user-queue exceeded the specification of the forwarding engine resources.
  • Cause 258: The number of outbound chip user-queue exceeded the specification of the forwarding engine resources.
  • Cause 260: The number of PW Hqos exceeded the specification of the forwarding engine resources.
  • Cause 261: The number of MPLS OAM/TPOAM single-ended frame loss measurement exceeded 90% of the specification of the forwarding engine resources.
  • Cause 262: The number of MPLS-TP OAM one-way frame delay measurement exceeded 90% of the specification of the forwarding engine resources.
  • Cause 263: The number of MPLS OAM/TPOAM two-way frame delay measurement exceeded 90% of the specification of the forwarding engine resources.
  • Cause 264: The number of MPLS-TP OAM dual-ended frame loss measurement exceeded 90% of the specification of the forwarding engine resources.
  • Cause 265: The number of MPLS OAM/TPOAM single-ended frame loss measurement exceeded the specification of the forwarding engine resources.
  • Cause 266: The number of MPLS-TP OAM one-way frame delay measurement exceeded the specification of the forwarding engine resources.
  • Cause 267: The number of MPLS OAM/TPOAM two-way frame delay measurement exceeded the specification of the forwarding engine resources.
  • Cause 268: The number of MPLS-TP OAM dual-ended frame loss measurement exceeded the specification of the forwarding engine resources.
  • Cause 269: The number of MPLS OAM/TPOAM exceeded the specification of the forwarding engine resources.
  • Cause 270: The number of MPLS APS exceeded the specification of the forwarding engine resources.
  • Cause 271: The number of TM inbound SQ resources usage has exceeded 90%.
  • Cause 272: The number of TM outbound SQ resources usage has exceeded 90%.
  • Cause 273: The number of SLOT inbound SQ resources usage has exceeded 90%.
  • Cause 274: The number of SLOT outbound SQ resources usage has exceeded 90%.
  • Cause 276: The number of Inbound random-discard exceeded the specification of the forwarding engine resources.
  • Cause 277: The number of Outbound random-discard exceeded the specification of the forwarding engine resources.
  • Cause 280: The number of CGN or IPsec ACL TCAM exceeded 90% of the forwarding engine resource specification.
  • Cause 281: The number of the applied CP IPv4 ACLs exceeded 90% of the specification of the forwarding resources.
  • Cause 282: The number of the applied CP IPv6 ACLs exceeded 90% of the specification of the forwarding resources.
  • Cause 285: The number of ERPS exceeds 90% of the specification of the forwarding engine resources.
  • Cause 286: The number of the applied BEHAVIOR_VPNGROUPs exceeded the specification of the forwarding resources.
  • Cause 287: The number of the applied BEHAVIOR_VPNGROUPs exceeded 90% of the specification of the forwarding resources.
  • Cause 288: The number of the applied DHCPSNP_BINDTBLs exceeded 80% of the specification of the forwarding resources.
  • Cause 289: The number of the applied QPPB_IPV4_ACL_INs exceeded 90% of the specification of the forwarding resources.
  • Cause 290: The number of the applied QPPB_IPV6_ACL_INs exceeded 90% of the specification of the forwarding resources.
  • Cause 291: The number of the applied QPPB_IPV4_ACL_OUTs exceeded 90% of the specification of the forwarding resources.
  • Cause 292: The number of the applied QPPB_IPV6_ACL_OUTs exceeded 90% of the specification of the forwarding resources.
  • Cause 293: The number of the applied REFLUENCE_VTCAMs exceeded 90% of the specification of the forwarding resources.
  • Cause 294: The number of the applied BGPFLOW_VTCAMs exceeded 90% of the specification of the forwarding resources.
  • Cause 295: The number of multicast out-interfaces exceeded 90% of the specification of the forwarding engine resources.
  • Cause 300: The number of VPLS exceeds 90% of the specification of the forwarding engine resources.
  • Cause 301: The number of EVPN exceeds 90% of the specification of the forwarding engine resources.
  • Cause 302: The number of L2TPV3 exceeds 90% of the specification of the forwarding engine resources.
  • Cause 304: The number of L2 multicast FIBs exceeded 95% of the specification of the forwarding engine resources.
  • Cause 305: The number of CAR IDs for upstream traffic exceeded 95% of the forwarding engine resource specification.
  • Cause 306: The number of CAR IDs for downstream traffic exceeded 95% of the forwarding engine resource specification.
  • Cause 307: The number of GIDs exceeded 95% of the forwarding engine resource specification.
  • Cause 308: The number of ACL statistics indexes for upstream traffic exceeded 95% of the forwarding engine resource specification.
  • Cause 309: The number of ACL statistics indexes for downstream traffic exceeded 95% of the forwarding engine resource specification.
  • Cause 310: The number of flow CAR indexes for upstream traffic exceeded 95% of the forwarding engine resource specification.
  • Cause 311: The number of flow CAR indexes for downstream traffic exceeded 95% of the forwarding engine resource specification.
  • Cause 312: The number of IPv4 TCAM indexes for upstream traffic exceeded 95% of the forwarding engine resource specification(The uplink and downlink share resources, and pre-alarms may be generated in both directions).
  • Cause 313: The number of IPv4 TCAM indexes for downstream traffic exceeded 95% of the forwarding engine resource specification(The uplink and downlink share resources, and pre-alarms may be generated in both directions).
  • Cause 314: The number of IPv6 TCAM indexes for upstream traffic exceeded 95% of the forwarding engine resource specification(The uplink and downlink share resources, and pre-alarms may be generated in both directions).
  • Cause 315: The number of IPv6 TCAM indexes for downstream traffic exceeded 95% of the forwarding engine resource specification(The uplink and downlink share resources, and pre-alarms may be generated in both directions).
  • Cause 316: The number of VPLS exceeds the specification of the forwarding engine resources.
  • Cause 317: The number of EVPN exceeds the specification of the forwarding engine resources.
  • Cause 318: The number of IPv4 FIB entries exceeded 95% of the forwarding engine's resource specification.
  • Cause 319: The number of IPv6 FIB entries exceeded 95% of the forwarding engine's resource specification.
  • Cause 320: The number of IPv6 NDH entries exceeded 95% of the forwarding engine's resource specification.
  • Cause 321: The number of IPv4 multicast FIBs exceeded 95% of the specification of the forwarding engine resources.
  • Cause 322: The number of IPv6 multicast FIBs exceeded 95% of the specification of the forwarding engine resources.
  • Cause 323: The number of PW-VE or remote interface's index exceeded 90% of the specification of the forwarding engine resources.
  • Cause 325: The number of resources in the IPv4 GRE tunnel decapsulation table exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 326: The number of resources in the IPv6 GRE tunnel decapsulation table exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 328: The number of PBB exceeds 90% of the specification of the forwarding engine resources.
  • Cause 329: The number of PBB exceeds the specification of the forwarding engine resources.
  • Cause 334: The number of IPv4 UCL TCAM indexes for upstream traffic exceeded 95% of the forwarding engine resource specification.
  • Cause 335: The number of IPv4 UCL TCAM indexes for downstream traffic exceeded 95% of the forwarding engine resource specification.
  • Cause 336: The number of IPv6 UCL TCAM indexes for upstream traffic exceeded 95% of the forwarding engine resource specification.
  • Cause 337: The number of IPv6 UCL TCAM indexes for downstream traffic exceeded 95% of the forwarding engine resource specification.
  • Cause 338: The number of IPv4 UCL TCAM indexes for upstream traffic exceeded the forwarding engine resource specification.
  • Cause 339: The number of IPv4 UCL TCAM indexes for downstream traffic exceeded the forwarding engine resource specification.
  • Cause 340: The number of IPv6 UCL TCAM indexes for upstream traffic exceeded the forwarding engine resource specification.
  • Cause 341: The number of IPv6 UCL TCAM indexes for downstream traffic exceeded the forwarding engine resource specification.
  • Cause 342: The number of CGN or IPsec ACL TCAM exceeded the forwarding engine resource specification.
  • Cause 343: The number of TM inbound GQ resources usage has exceeded 90%.
  • Cause 344: The number of TM outbound GQ resources usage has exceeded 90%.
  • Cause 345: The segment routing LabelStack table resource usage exceeded the specification of the forwarding engine resources
  • Cause 346: The segment routing table resource usage has exceeded 95% of the forwarding engine specification.
  • Cause 347: The number of enabled statistics exceeded 95% of the specification of the forwarding engine resources.
  • Cause 348: The number of NHP indexes exceeded 95% of the forwarding engine resource specification.
  • Cause 349: The number of NHP indexes exceeded the forwarding engine resource specification.
  • Cause 350: The number of NST indexes exceeded 95% of the forwarding engine resource specification.
  • Cause 351: The number of NST indexes exceeded the forwarding engine resource specification.
  • Cause 352: The number of MLID resource exceeded 95% of the forwarding engine resource specification.
  • Cause 354: The number of L2PT resource exceeds 90% of the specification of the forwarding engine resources.
  • Cause 355: The number of L2PT resource exceeded the specification of the forwarding engine resources.
  • Cause 357: The number of pool-0 flow-queue wfq exceeded the specification of the forwarding engine resources.
  • Cause 358: The number of pool-1 flow-queue wfq exceeded the specification of the forwarding engine resources.
  • Cause 359: The number of pool-0 flow-queue cbs exceeded the specification of the forwarding engine resources.
  • Cause 360: The number of pool-1 flow-queue cbs exceeded the specification of the forwarding engine resources.
  • Cause 361: The number of pool-0 flow-queue pbs exceeded the specification of the forwarding engine resources.
  • Cause 362: The number of pool-1 flow-queue pbs exceeded the specification of the forwarding engine resources.
  • Cause 363: The number of pool-0 user-queue exceeded the specification of the forwarding engine resources.
  • Cause 364: The number of pool-1 user-queue exceeded the specification of the forwarding engine resources.
  • Cause 365: The number of pool-0 user-queue template exceeded the specification of the forwarding engine resources.
  • Cause 366: The number of pool-1 user-queue template exceeded the specification of the forwarding engine resources.
  • Cause 367: The number of pool-0 service-template exceeded the specification of the forwarding engine resources.
  • Cause 368: The number of pool-1 service-template exceeded the specification of the forwarding engine resources.
  • Cause 369: The number of pool-0 user-group-queue exceeded the specification of the forwarding engine resources.
  • Cause 370: The number of pool-1 user-group-queue exceeded the specification of the forwarding engine resources.
  • Cause 371: The number of pool-0 user-group-queue template exceeded the specification of the forwarding engine resources.
  • Cause 372: The number of pool-1 user-group-queue template exceeded the specification of the forwarding engine resources.
  • Cause 373: The number of pool-0 chip user-queue exceeded the specification of the forwarding engine resources.
  • Cause 374: The number of pool-1 chip user-queue exceeded the specification of the forwarding engine resources.
  • Cause 383: The number of pool-0 flow-wred exceeded the specification of the forwarding engine resources
  • Cause 384: The number of pool-1 flow-wred exceeded the specification of the forwarding engine resources
  • Cause 387: The bandwidth of large buffer usage has exhausted.
  • Cause 388: The number of the user defined flow applied CP IPv4 ACLs exceeded 90% of the specification of the forwarding resources.
  • Cause 389: The number of the dynamic link protection applied CP IPv4 ACLs exceeded 90% of the specification of the forwarding resources.
  • Cause 390: The number of PW source tunnels exceeds the specifications of the forwarding engine.
  • Cause 393: The number of BGP flowspec RE exceeded the specification of the forwarding engine resources.
  • Cause 394: The number of BGP flowspec RE exceeded 90% of the specification of the forwarding engine resources.
  • Cause 395: The number of VXLAN resource exceeds 90% of the specification of the forwarding engine resources.
  • Cause 396: The number of VXLAN resource exceeded the specification of the forwarding engine resources.
  • Cause 397: The number of ETH-Test instances exceeded the specification of the forwarding engine resources.
  • Cause 398: The sum of all member interfaces' weights of a trunk interface exceeded the maximum value supported by the board.
  • Cause 399: The number of resources in the IPv4 VXLAN tunnel decapsulation table exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 400: The number of IPFPM resource usage has exceeded the specifications of the forwarding engine resources.
  • Cause 401: The number of TWAMP resource usage has exceeded the specifications of the forwarding engine resources.
  • Cause 402: The number of user-queue CIR template exceeded the specification of the forwarding engine resources.
  • Cause 403: The number of user-queue EIR template exceeded the specification of the forwarding engine resources.
  • Cause 404: The number of flow-queue shaping template exceeded the specification of the forwarding engine resources.
  • Cause 405: The number of flow-queue share-shaping template exceeded the specification of the forwarding engine resources.
  • Cause 410: The number of VNI*peer resources exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 411: The number of the dynamic link protection applied CP IPv4 ACLs exceeded the specification of the forwarding resources.
  • Cause 412: The number of the user defined flow applied CP IPv4 ACLs exceeded the specification of the forwarding resources.
  • Cause 413: The number of RFC2544 exceeded the specification of the forwarding engine resources.
  • Cause 414: The number of Main and Subif exceeds the specification of the forwarding engine resources.
  • Cause 415: The number of Statistics exceeds the specification of the forwarding engine resources.
  • Cause 416: The number of resources in the static-cr-lsp source interface check table exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 417: The number of resources in the static-cr-lsp source interface check table exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 418: The number of IPv6 ACL TCAM resources usage has exceeded 90%.
  • Cause 419: The number of IPv6 ACL TCAM resources usage has exhausted.
  • Cause 420: The number of remote-interface exceeded 90% of the forwarding engine resource specification.
  • Cause 421: The number of remote-interface exceeded the forwarding engine resource specification.
  • Cause 422: The number of Priority Car Statistics exceeds 90% of the specification of the forwarding engine resources.
  • Cause 423: The number of Priority Car Statistics exceeds the specification of the forwarding engine resources.
  • Cause 424: The numbers of the applied CP L2 ACL exceeded the specification of the forwarding resources.
  • Cause 425: The number of the applied CP L2 ACLs exceeded 90% of the specification of the forwarding resources.
  • Cause 426: The number of the CAR indexes for arpvlancar and soc defend exceeded 90% of the forwarding engine resource specification.
  • Cause 427: The number of the CAR indexes for arpvlancar and soc defend exceeded the forwarding engine resource specification.
  • Cause 428: The number of the statistics indexes for arpvlancar and soc defend exceeded 90% of the forwarding engine resource specification.
  • Cause 429: The number of the statistics indexes for arpvlancar and soc defend exceeded the forwarding engine resource specification.
  • Cause 430: The number of the CAR indexes for port vlan car and igmp vlan car exceeded 90% of the forwarding engine resource specification.
  • Cause 431: The number of the CAR indexes for port vlan car and igmp vlan car exceeded the forwarding engine resource specification.
  • Cause 432: The number of the statistics indexes for port vlan car and igmp vlan car exceeded 90% of the forwarding engine resource specification.
  • Cause 433: The number of the statistics indexes for port vlan car and igmp vlan car exceeded the forwarding engine resource specification.
  • Cause 434: The number of the CAR indexes for BGPFLOW exceeded the forwarding engine resource specification.
  • Cause 435: The number of the CAR indexes for BGPFLOW exceeded 90% of the forwarding engine resource specification.
  • Cause 436: The number of Inbound Mirror table exceeded 90% of the specification of the forwarding engine resources.
  • Cause 437: The number of Outbound Mirror table exceeded 90% of the specification of the forwarding engine resources.
  • Cause 438: The number of Inbound Capture packet mirror table exceeded 90% of the specification of the forwarding engine resources.
  • Cause 439: The number of Outbound Capture Packet mirror table exceeded 90% of the specification of the forwarding engine resources.
  • Cause 440: The number of Inbound mirror car exceeded 90% of the specification of the forwarding engine resources.
  • Cause 441: The number of Outbound mirror car exceeded 90% of the specification of the forwarding engine resources.
  • Cause 442: The number of the inbound CAR indexes for QPPB exceeded the forwarding engine resource specification.
  • Cause 443: The number of the inbound CAR indexes for QPPB exceeded 90% of the forwarding engine resource specification.
  • Cause 444: The number of the outbound CAR indexes for QPPB exceeded the forwarding engine resource specification.
  • Cause 445: The number of the outbound CAR indexes for QPPB exceeded 90% of the forwarding engine resource specification.
  • Cause 446: The number of the QPPB IPv4 inbound statistics indexes for QPPB exceeded the forwarding engine resource specification.
  • Cause 447: The number of the QPPB IPv4 inbound statistics indexes for QPPB exceeded 90% of the forwarding engine resource specification.
  • Cause 448: The number of the QPPB IPv4 outbound statistics indexes for QPPB exceeded the forwarding engine resource specification.
  • Cause 449: The number of the QPPB IPv4 outbound statistics indexes for QPPB exceeded 90% of the forwarding engine resource specification.
  • Cause 450: The number of the QPPB IPv6 inbound statistics indexes for QPPB exceeded the forwarding engine resource specification.
  • Cause 451: The number of the QPPB IPv6 inbound statistics indexes for QPPB exceeded 90% of the forwarding engine resource specification.
  • Cause 452: The number of the QPPB IPv6 outbound statistics indexes for QPPB exceeded the forwarding engine resource specification.
  • Cause 453: The number of the QPPB IPv6 outbound statistics indexes for QPPB exceeded 90% of the forwarding engine resource specification.
  • Cause 454: The number of the QPPB car statistics indexes for QPPB exceeded the forwarding engine resource specification.
  • Cause 455: The number of the QPPB car statistics indexes for QPPB exceeded 90% of the forwarding engine resource specification.
  • Cause 456: The number of the DHCPSNP statistics indexes for DHCPSNP exceeded 90% of the forwarding engine resource specification.
  • Cause 457: The number of the RE indexes for REDIRECT exceeded the forwarding engine resource specification.
  • Cause 458: The number of the RE indexes for REDIRECT exceeded 90% of the forwarding engine resource specification.
  • Cause 459: The number of the NST indexes for REDIRECT exceeded the forwarding engine resource specification.
  • Cause 460: The number of the NST indexes for REDIRECT exceeded 90% of the forwarding engine resource specification.
  • Cause 461: The number of the NHP indexes for REDIRECT exceeded the forwarding engine resource specification.
  • Cause 462: The number of the NHP indexes for REDIRECT exceeded 90% of the forwarding engine resource specification.
  • Cause 465: The number of BGPFLOW GIDs exceeded 90% of the forwarding engine resource specification.
  • Cause 466: The number of BGPFLOW Gids exceeded the specification of the forwarding engine resources.
  • Cause 469: The number of resources in the MPLS ARP exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 470: The number of resources in the MPLS ARP exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 471: The number of resources in the TE statistics exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 472: The number of resources in the TE statistics exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 473: The number of resources in the LSPCAR index exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 474: The number of resources in the LSPCAR index exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 475: The number of resources in the P2MP MRE table exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 476: The number of resources in the P2MP MRE table exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 477: The number of resources in the RECYCLE OUTSEGMENT index exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 478: The number of resources in the RECYCLE OUTSEGMENT index exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 479: The number of resources in theRECYCLE INSEGMENT index exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 480: The number of resources in the RECYCLE INSEGMENT index exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 481: The number of resources in the MPLS NST index exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 482: The number of resources in the MPLS NST index exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 483: The number of resources in the statistics ID exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 484: The number of resources in the statistics ID exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 485: The number of resources in the P2MP BUD insegment table exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 486: The number of resources in the P2MP BUD insegment table exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 487: The number of resources in the MLDP RE index exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 488: The number of resources in the MLDP RE index exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 489: The number of resources in the MLDP RECYCLE INSEGMENT index exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 490: The number of resources in the MLDP RECYCLE INSEGMENT index exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 491: The number of resources in the MLDP RECYCLE OUTSEGMENT index exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 492: The number of resources in the MLDP RECYCLE OUTSEGMENT index exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 493: The number of resources in the MLDP BUD insegment index exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 494: The number of resources in the MLDP BUD insegment index exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 495: The number of resources in the P2MP NST index exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 496: The number of resources in the P2MP NST index exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 497: The number of VLL hard pipe services exceeds the specification of the forwarding engine resources.
  • Cause 498: The number of BFD GIDs exceeded the forwarding engine resource specification.
  • Cause 499: The number of VPLS PW NHP resources exceeded the specification of the forwarding engine resources.
  • Cause 500: The number of 1588 exceeded the 90% of the forwarding engine resources.
  • Cause 501: The number of used virtual access service resources exceeded 90% of the total resources on the forwarding engine.
  • Cause 502: The number of the INSEG_VRF entries exceeds the forwarding engine specifications.
  • Cause 503: The number of dynamic load balancing IDs exceeds the forwarding engine specifications.
  • Cause 504: The number of the community entries exceeds the forwarding engine specifications.
  • Cause 505: The number of the IPv4 Tunnel indexes exceeds the forwarding engine resource specification.
  • Cause 506: The number of SMA AS indexes exceeded the specification of the forwarding engine resources.
  • Cause 507: The number of SMA FIBV6 exceeds the specification of the forwarding engine resources.
  • Cause 508: The number of the applied QPPB ACLs exceeded 90% of the specification of the forwarding resources.
  • Cause 509: The number of QPPB ACLs exceeded the specification of the forwarding engine resources.
  • Cause 510: The number of the applied inbound QPPB EXTACTIONs exceeded 90% of the specification of the forwarding resources.
  • Cause 511: The number of inbound QPPB EXTACTIONs exceeded the specification of the forwarding engine resources.
  • Cause 512: The number of the applied outbound QPPB EXTACTIONs exceeded 90% of the specification of the forwarding resources.
  • Cause 513: The number of outbound QPPB EXTACTIONs exceeded the specification of the forwarding engine resources.
  • Cause 516: The number of mirror observe table exceeded 90% of the specification of the forwarding engine resources.
  • Cause 517: The number of mirror observe table exceeded the specification of the board forwarding engine resources.
  • Cause 518: The number of Mirror filter table exceeded 90% of the specification of the forwarding engine resources.
  • Cause 519: The number of Mirror filter table exceeded the specification of the board forwarding engine resources.
  • Cause 520: The number of mirror statistics table exceeded 90% of the specification of the forwarding engine resources.
  • Cause 521: The number of mirror statistics table exceeded the specification of the board forwarding engine resources.
  • Cause 522: The number of downstream interfaces to which mirror data is replicated to exceeded 90% of the specification supported by the entire system.
  • Cause 523: The number of downstream interfaces to which mirror data is replicated to exceeded the specification supported by the entire system.
  • Cause 524: The number of resources in the MLDP BUD outsegment index exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 525: The number of resources in the MLDP BUD outsegment index exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 526: The number of resources in the MLDP egress nodes statistics exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 527: The number of resources in the MLDP egress nodes statistics exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 528: The number of resources in the MLDP ingress nodes statistics exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 529: The number of resources in the MLDP ingress nodes statistics exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 530: The number of resources in the MPLS TE ingress NHP index exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 531: The number of resources in the MPLS TE ingress NHP index exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 532: The number of resources in the MPLS P node loadbalance RE table index exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 533: The number of resources in the MPLS P node loadbalance RE table index exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 534: The number of resources in the MPLS E node tunnel index exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 535: The number of resources in the MPLS E node tunnel index exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 536: The number of NQA exceeded 90% of the specification of the forwarding engine resources.
  • Cause 537: The number of NQA exceeded the specification of the forwarding engine resources.
  • Cause 538: The number of resources in the P2MP BUD outsegment table exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 539: The number of resources in the P2MP BUD outsegment table exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 540: The number of resources in the P2MP egress nodes satistics exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 541: The number of resources in the P2MP egress nodes statistics exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 542: The number of resources in the P2MP ingress nodes satistics exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 543: The number of resources in the P2MP ingress nodes statistics exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 544: The number of resources in the LSP OUT MIB satistics exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 545: The number of resources in the LSP OUT MIB statistics exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 546: The number of MPLS TE indexes for downstream traffic exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 547: The number of MPLS TE indexes for downstream traffic exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 548: The number of PW-VE or remote interface's index exceeded the specification of the forwarding engine resources.
  • Cause 549: The number of the bgpflow car statistics indexes exceeded the forwarding engine resource specification.
  • Cause 550: The number of the bgpflow car statistics indexes exceeded 90% of the forwarding engine resource specification.
  • Cause 551: The number of the CAR indexes for layer 2 protocol tunnel exceeded 90% of the forwarding engine resource specification.
  • Cause 552: The number of the CAR indexes for layer 2 protocol tunnel exceeded the forwarding engine resource specification.
  • Cause 553: The number of vpls pw suppression statistics services exceeded the specification of the forwarding engine resources.
  • Cause 554: The number of vpls pw suppression statistics services exceeded 90% of the specification of the forwarding engine resources.
  • Cause 555: The number of Mirror user rule table exceeded 90% of the specification of the forwarding engine resource.
  • Cause 556: The number of Mirror user rule table exceeded the specification of the forwarding engine resources.
  • Cause 557: The number of Mirror table exceeded 90% of the specification of the forwarding engine resources.
  • Cause 558: The number of Mirror table exceeded the specification of the forwarding engine resources.
  • Cause 559: The number of mirror car exceeded 90% of the specification of the forwarding engine resources.
  • Cause 560: The number of mirror car exceeded the specification of the forwarding engine resources.
  • Cause 561: The number of Y.1564 exceeded the specification of the forwarding engine resources.
  • Cause 562: The number of VPLS PW HQoS services exceeded the specification of the forwarding engine resources.
  • Cause 563: The number of the BGP Flowspec IPv6 ACL exceeded the forwarding engine resource specification.
  • Cause 564: The number of the applied BGP Flowspec IPv6 ACL exceeded 90% of the specification of the forwarding resources.
  • Cause 565: The number of L2TPV3 tunnel exceeds the specification of the forwarding engine resources
  • Cause 566: The number of the applied BGP Flowspec IPv6 refluence exceeded 90% of the specification of the forwarding resources.
  • Cause 567: The number of Mirror user offset table exceeded 90% of the specification of the forwarding engine resource.
  • Cause 568: The number of Mirror user offset table exceeded the specification of the forwarding engine resources.
  • Cause 569: The number of TM outbound VI resources usage has exceeded 90%.
  • Cause 572: Downstream mirroring resources failed to be to allocated to the APS service because the number of used downstream mirroring resources exceeded the forwarding engine specification.
  • Cause 573: MPLS-ARP resources failed to be to allocated to the low-speed service because the number of used MPLS-ARP resources exceeded the forwarding engine specification.
  • Cause 574: The number of the applied BGP Flowspec IPv6 refluence exceeded the forwarding engine resource specification.
  • Cause 577: The number of MAC accounting statistics entries exceeds the specification of the forwarding engine.
  • Cause 582: The number of EVC sub-interface validity check entries exceeded the maximum number supported by the forwarding engine.
  • Cause 583: The number of the statistics indexes for random-discard exceeded the forwarding engine resource specification.
  • Cause 584: L2mcV6 mre stat resources useage exceeded 90% of the specification of the forwarding resources.
  • Cause 585: L2mcV6 mre stat resources useage exceeded the specification of the forwarding resources.
  • Cause 586: The number of L2 Traffic Suppression Inbound statistics exceeded 90% of the specification of the forwarding engine resource.
  • Cause 587: The number of L2 Traffic Suppression Inbound statistics exceeded the specification of the forwarding engine resource.
  • Cause 588: The number of L2 Traffic Suppression Outbound statistics exceeded 90% of the specification of the forwarding engine resource.
  • Cause 589: The number of L2 Traffic Suppression Outbound statistics exceeded the specification of the forwarding engine resource.
  • Cause 590: The number of user exceeded the specification of the forwarding engine resources
  • Cause 591: The number of Lac user exceeded the specification of the forwarding engine resources
  • Cause 595: The number of user on card0 exceeded 90% of the specification of the forwarding engine resources
  • Cause 596: The number of user on card1 exceeded the 90% of the specification of the forwarding engine resources
  • Cause 597: The number of user on card0 exceeded the specification of the forwarding engine resources
  • Cause 598: The number of user on card1 exceeded the specification of the forwarding engine resources
  • Cause 603: The number of the applied DHCPSNP_ACLs exceeded 90% of the specification of the forwarding resources.
  • Cause 604: The number of the applied DHCPSNP_ACLs exceeded the forwarding engine resource specification.
  • Cause 605: The number of IPv6 L2 multicast FIBs exceeded 95% of the specification of the forwarding engine resources.
  • Cause 606: The number of MLIB resource exceeded 95% of the forwarding engine resource specification.
  • Cause 607: The number of MLIB exceeded the specification of the forwarding engine resources.
  • Cause 608: The number of resources in the 4over6 tunnel decapsulation table exceeded the specification of resources allowed by the forwarding engine.
  • Cause 609: The number of IPv6 Address in the IPB table exceeded the specification of resources allowed by the forwarding engine.
  • Cause 610: The number of interface URPF ACL Entry exceeded the forwarding engine resource specification.
  • Cause 611: The number of interface URPF ACL Entry exceeded 90% of the forwarding engine resource specification.
  • Cause 612: The number of the hqos's arithmetic table exceeded the specification of the forwarding engine resources.
  • Cause 613: The number of the DHCPSNP statistics indexes for DHCPSNP exceeded the forwarding engine resources specification.
  • Cause 616: The token-nse table resource usage has exceeded 90%.
  • Cause 617: The token-nse table resource exceeded the specifications of the forwarding engine resources.
  • Cause 618: The number of resources in the P2MP te statistics exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 619: The number of resources in the P2MP te statistics exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 620: The number of resources in the multicast ap replication tunnel vlink loopback protection NHP table exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 621: The number of resources in the multicast ap replication tunnel vlink loopback protection NHP table exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 622: The number of resources in the multicast ap replication tunnel vlink loopback protection NST table exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 623: The number of resources in the multicast ap replication tunnel vlink loopback protection NST table exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 624: The number of resources in the multicast ap ingress NHP table exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 625: The number of resources in the multicast ap ingress NHP table exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 626: The number of resources in the multicast ap ingress NST table exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 627: The number of resources in the multicast ap ingress NST table exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 628: The number of resources in the P2MP trunk load sharing NHP exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 629: The number of resources in the P2MP trunk load sharing NHP exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 630: The number of resources in the MLDP leaf exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 631: The number of resources in the MLDP leaf exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 632: The number of resources in the P2MP leaf exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 633: The number of resources in the P2MP leaf exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 634: The number of BFD resource usage has exceeded the specifications of the forwarding engine resources.
  • Cause 635: The number of EOAM resource usage has exceeded the specifications of the forwarding engine resources.
  • Cause 636: The number of VRRP resource usage has exceeded the specifications of the forwarding engine resources.
  • Cause 637: Loopback forwarding services configured on VBDIF interfaces exceeded 90% of the total loopback forwarding resources supported by the forwarding engine.
  • Cause 638: The number of VBDIF interfaces enabled with loopback forwarding exceeded the specification of the forwarding engine.
  • Cause 639: The number of portcar exceeded the 90% of the specification of the forwarding engine resources.
  • Cause 640: The number of portcar exceeded the specification of the forwarding engine resources.
  • Cause 641: The number of portcarstat exceeded the 90% of the specification of the forwarding engine resources.
  • Cause 642: The number of portcarstat exceeded the specification of the forwarding engine resources.
  • Cause 643: The number of UDFV6_VTCAM exceeded the 90% of the specification of the forwarding engine resources.
  • Cause 644: The number of UDFV6_VTCAM exceeded the specification of the forwarding engine resources.
  • Cause 645: The number of DLPV6_VTCAM exceeded the 90% of the specification of the forwarding engine resources.
  • Cause 646: The number of DLPV6_VTCAM exceeded the specification of the forwarding engine resources.
  • Cause 647: The number of GTSM_VTCAM exceeded the 90% of the specification of the forwarding engine resources.
  • Cause 648: The number of GTSM_VTCAM exceeded the specification of the forwarding engine resources.
  • Cause 649: The number of GTSM_VTCAMV6 exceeded the 90% of the specification of the forwarding engine resources.
  • Cause 650: The number of GTSM_VTCAMV6 exceeded the specification of the forwarding engine resources.
  • Cause 651: The number of label statistical tables exceeded the forwarding engine specification.
  • Cause 652: The number of label statistical tables exceeded 95% of the forwarding engine specification.
  • Cause 653: The number of local SID tables for SRv6 exceeded the forwarding engine specification.
  • Cause 654: The number of millisecond-level configuration table resources collected by Telemetry exceeded 95% of the upper limit supported by the forwarding engine.
  • Cause 655: The number of millisecond-level configuration table resources collected by Telemetry exceeded the upper limit supported by the forwarding engine.
  • Cause 656: The number of second-level configuration table resources collected by Telemetry exceeded 95% of the upper limit supported by the forwarding engine.
  • Cause 657: The number of second-level configuration table resources collected by Telemetry exceeded the upper limit supported by the forwarding engine.
  • Cause 658: The number of 30-second-level configuration table resources collected by Telemetry exceeded 95% of the upper limit supported by the forwarding engine.
  • Cause 659: The number of 30-second-level configuration table resources collected by Telemetry exceeded the upper limit supported by the forwarding engine.
  • Cause 660: The number of BGP Flowspec based on interface GIDs exceeded 90% of the forwarding engine resource specification.
  • Cause 661: The number of BGP Flowspec based on interface GIDs exceeded the specification of the forwarding engine resources.
  • Cause 662: The number of the applied BGP flowspec based on interface ACL exceeded 90% of the specification of the forwarding resources.
  • Cause 663: The number of the applied BGP flowspec based on interface ACL exceeded the forwarding engine resource specification.
  • Cause 664: The number of NHRP peer tables exceeds the forwarding engine specification.
  • Cause 665: The number of dynamic NHRP peer statistical entries exceeds the forwarding engine specification.
  • Cause 666: The number of dhcp snooping whitelist statistics exceeded the specification of the forwarding engine resources.
  • Cause 667: The number of dhcp snooping whitelist statistics exceeded 90% of the specification of the forwarding engine resources.
  • Cause 668: Resources in the TNL6_OTNLINF exceeded the upper limit supported by the forwarding engine.
  • Cause 669: The number of ERPS NSE resource exceeded the specification of the forwarding engine resources.
  • Cause 670: The number of eap tbl reasource for user exceeded the specification of the forwarding engine resources.
  • Cause 671: The number of Service-class track BFD indexes exceeded the forwarding engine resource specification.
  • Cause 672: The number of filter MAC exceeded the 90% of the specification of the forwarding engine resources.
  • Cause 673: The number of filter MAC exceeded the specification of the forwarding engine resources.
  • Cause 703: No dual-device hot-backup forwarding table resource can be requested multicast.
  • Cause 707: No Mre Stat resources can be requested for IPv4 Layer 3 multicast.
  • Cause 708: No Mre Stat resources can be requested for IPv6 Layer 3 multicast.
  • Cause 709: No MreExt table resource can be requested for IPv4 Layer 3 multicast.
  • Cause 710: No MreExt table resource can be requested for IPv6 Layer 3 multicast.
  • Cause 715: The number of the applied virtual user-queue resources exceeded the specifications supported by the forwarding engine of a board.
  • Cause 716: The number of the applied virtual user-group-queue resources exceeded the specifications supported by the forwarding engine of a board.
  • Cause 717: The number of the applied virtual sub-port-queue resources exceeded the specifications supported by the forwarding engine of a board.
  • Cause 721: No unicast SRv6 table resource can be requested for IPv6 Layer 3 unicast .
  • Cause 722: No unicast DSVPN table resources can be requested for IPv4 Layer 3 unicast.
  • Cause 725: The resource usage of ipv4 whitelist session-car has exceeded the forwarding resource specifications
  • Cause 726: The resource usage of ipv4 whitelist session-car has exceeded 90% of the forwarding resource specifications
  • Cause 727: The resource usage of ipv4 whitelist session-car statistics has exceeded the forwarding resource specifications
  • Cause 728: The resource usage of ipv4 whitelist session-car statistics has exceeded 90% of the forwarding resource specifications
  • Cause 729: The l2vpn qos nse table resources usage has exceeded 90% of the forwarding engine resources specification.
  • Cause 730: The l2vpn qos nse table resources exceeded the specifications of the forwarding engine resources.
  • Cause 731: The MRE statistics table resources cannot be obtained for the IPv4 Layer 3 multicast source clone service.
  • Cause 733: The number of interface URPF statistics resources exceeded the forwarding engine resource specification.
  • Cause 734: The number of interface URPF statistics resources exceeded 90% of the forwarding engine resource specification.
  • Cause 735: The number of IP traffic statistics resources exceeds the specification of the forwarding engine resources.
  • Cause 737: The number of multicast leaves exceeds 4096.
  • Cause 738: The resource usage of IPv6 whitelist session-car has exceeded the forwarding resource specifications.
  • Cause 739: The resource usage of IPv6 whitelist session-car has exceeded 90% of the forwarding resource specifications.
  • Cause 740: The resource usage of IPv6 whitelist session-car statistics has exceeded the forwarding resource specifications.
  • Cause 741: The resource usage of IPv6 whitelist session-car statistics has exceeded 90% of the forwarding resource specifications.
  • Cause 742: The resource usage of l2 whitelist session-car has exceeded the forwarding resource specifications.
  • Cause 743: The resource usage of l2 whitelist session-car has exceeded 90% of the forwarding resource specifications.
  • Cause 744: The resource usage of l2 whitelist session-car statistics has exceeded the forwarding resource specifications.
  • Cause 745: The resource usage of l2 whitelist session-car statistics has exceeded 90% of the forwarding resource specifications.
  • Cause 759: The number of the applied car resources of session users exceeded the specifications supported by the forwarding engine of a board.
  • Cause 760: The number of the applied car resources of family users exceeded the specifications supported by the forwarding engine of a board.
  • Cause 763: The number of the applied car statistics resources of session users exceeded the specifications supported by the forwarding engine of a board.
  • Cause 764: The number of the applied car statistics resources of family users exceeded the specifications supported by the forwarding engine of a board.
  • Cause 767: The number of MPLS-in-UDP address verification services exceeded the threshold supported by the forwarding engine.
  • Cause 768: The node where the BIER MVPN's outbound tunnel resides failed to apply for BIER VPN forwarding entries.
  • Cause 769: The number of resources in the discoverflow table exceeded the specification of resources supported by the forwarding engine.
  • Cause 770: The number of resources in the esqm table exceeded the specification of resources supported by the forwarding engine.
  • Cause 773: The number of BIFT entries exceeded the upper limit allowed by the board.
  • Cause 775: The number of statistics indexes for multicast egress exceeded the forwarding engine resource specification.
  • Cause 778: The number of CAR resources used to limit the rate of upstream traffic in a profile exceeds 95% of the total number of forwarding engine resources.
  • Cause 779: The number of CAR resources used to limit the rate of downstream traffic in a profile exceeds 95% of the total number of forwarding engine resources.
  • Cause 780: The number of inbound statistics resources for CAR in the QoS profile exceeded 95% of the forwarding engine's resource specification.
  • Cause 781: The number of outbound statistics resources for CAR in the QoS profile exceeded 95% of the forwarding engine's resource specification.
  • Cause 783: The number of the ACL indexes for nd vlan car exceeded 90% of the forwarding engine resource specification.
  • Cause 784: The number of the ACL indexes for nd vlan car exceeded the forwarding engine resource specification.
  • Cause 785: The number of the CAR indexes for nd vlan car exceeded 90% of the forwarding engine resource specification.
  • Cause 786: The number of the CAR indexes for nd vlan car exceeded the forwarding engine resource specification.
  • Cause 787: The number of the statistics indexes for nd vlan car exceeded 90% of the forwarding engine resource specification.
  • Cause 788: The number of the statistics indexes for nd vlan car exceeded the forwarding engine resource specification.
  • Cause 789: The number of L3VPN instances on the board exceeded the forwarding engine resource specification.
  • Cause 790: The number of IFIT exceeded 90% of the specification of the forwarding engine resources.
  • Cause 791: The number of IFIT resource usage has exceeded the specifications of the forwarding engine resources.
  • Cause 800: The index resources of the 100 ms telemetry for CAR statistics are insufficient.
  • Cause 801: The number of 100 ms telemetry index resources for CAR statistics exceeds 95% of the specification supported by the forwarding engine of the board.
  • Cause 802: The index resources of the 1s telemetry for CAR statistics are insufficient.
  • Cause 803: The number of 1s telemetry index resources for CAR statistics exceeds 95% of the specification supported by the forwarding engine of the board.
  • Cause 804: The index resources of the 30s telemetry for CAR statistics are insufficient.
  • Cause 805: The number of 30s telemetry index resources for CAR statistics exceeds 95% of the specification supported by the forwarding engine of the board.
  • Cause 806: The index resources of the 100 ms telemetry for ACL rule statistics are insufficient.
  • Cause 807: The number of 100 ms telemetry index resources for ACL rule statistics exceeds 95% of the specification supported by the forwarding engine of the board.
  • Cause 808: The index resources of the 1s telemetry for ACL rule statistics are insufficient.
  • Cause 809: The number of 1s telemetry index resources for ACL rule statistics exceeds 95% of the specification supported by the forwarding engine of the board.
  • Cause 810: The index resources of the 30s telemetry for ACL rule statistics are insufficient.
  • Cause 811: The number of 30s telemetry index resources for ACL rule statistics exceeds 95% of the specification supported by the forwarding engine of the board.
  • Cause 812: The number of resource in the SRPOLICY statistics exceeded 95% of the maximum number of resource allowed by the forwarding engine.
  • Cause 813: The number of resources in the SRPOLICY statistics exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 814: The number of the CAR indexes for arpvlancar exceeded 90% of the forwarding engine resource specification.
  • Cause 815: The number of the CAR indexes for arpvlancar exceeded the forwarding engine resource specification.
  • Cause 831: The number of LocalArpv6 entries exceeds the specification of the forwarding engine.
  • Cause 836: The number of remote sid entries exceeds the specification of the forwarding engine.
  • Cause 838: The number of SCAN tables used to store traffic statistics collected through SRv6 TE Policy telemetry at an interval of 30s exceeds the upper threshold.
  • Cause 840: The number of SCAN tables used to store traffic statistics collected through SRv6 TE Policy telemetry at an interval of 1s exceeds the upper threshold.
  • Cause 842: The number of RE entries regarding the service that redirects public network traffic to SRv6 Policies reaches the upper limit.
  • Cause 844: The number of Segment list entries exceeds the upper threshold.
  • Cause 846: The number of statistical entries of SRv6 TE Policies exceeds the upper threshold.
  • Cause 848: The number of resources in the IPv6 VXLAN tunnel decapsulation table exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 849: The number of EMDI ACL Entry exceeded the specification of the forwarding engine resources.
  • Cause 850: The number of SRv6 SFC Layer 3 forwarding RE entries exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 852: The number of SRv6 SFC Layer 2 forwarding RE entries exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 853: The number of test instances for which dual-ended frame loss measurement with an interval set to 100 ms is enabled exceeded the forwarding engine resource specification.
  • Cause 870: The number of inbound 8queue mode user-queue exceeded the specification of the forwarding engine resources.
  • Cause 871: The number of inbound 8queue-enhance mode user-queue exceeded the specification of the forwarding engine resources.
  • Cause 872: The number of outbound 4queue mode user-queue exceeded the specification of the forwarding engine resources.
  • Cause 873: The number of outbound 8queue mode user-queue exceeded the specification of the forwarding engine resources.
  • Cause 874: The number of outbound 8queue-enhance mode user-queue exceeded the specification of the forwarding engine resources.
  • Cause 907: The number of TM inbound 8queue mode user-queue exceeded the specification of the forwarding engine resources.
  • Cause 908: The number of TM inbound 8queue-enhance mode user-queue exceeded the specification of the forwarding engine resources.
  • Cause 909: The number of TM outbound 4queue mode user-queue exceeded the specification of the forwarding engine resources.
  • Cause 910: The number of TM outbound 8queue mode user-queue exceeded the specification of the forwarding engine resources.
  • Cause 911: The number of TM outbound 8queue-enhance mode user-queue exceeded the specification of the forwarding engine resources.
  • Cause 920: The numbers of used CP IPv4 and IPv6 ACLs exceeded 90% of total forwarding resources.
  • Cause 921: The numbers of used CP IPv4 and IPv6 ACLs exceeded the upper limit of the forwarding resources.
  • Cause 922: The aib ext table resource usage has exceeded 95% of the forwarding engine specification.
  • Cause 923: The number of resources in the SRv6 Network Slice SliceOportinfo table exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 929: The node where the BIERv4/BIERv6 MVPN's outbound tunnel resides failed to apply for BIERv4/BIERv6 VPN forwarding entries.
  • Cause 930: The node where BIERv6 MVPN services enter a tunnel failed to apply for BIERv6 Incoming Label Map IPv6 (ILMv6) forwarding entries.
  • Cause 934: The number of resources in the SRv6 Network Slice SegmentlistSliceMap table exceeded the maximum number of resources allowed by the forwarding engine.
  • Cause 935: The number of the applied DHCPv6 Snooping bind table exceeded 90% of the specification of the forwarding resources.
  • Cause 936: The number of DHCPv6 Snooping bind table exceeded the specifications of the forwarding engine resources.
  • Cause 937: The number of the DHCPv6 Snooping statistics indexes resource for DHCPv6 Snooping exceeded 90% of the forwarding engine resource specification.
  • Cause 938: The number of the DHCPv6 Snooping statistics indexes resource for DHCPv6 Snooping exceeded the forwarding engine resources specification.
  • Cause 939: The number of the applied DHCPv6 Snooping statistics table exceeded 90% of the specification of the forwarding resources.
  • Cause 940: The number of DHCPv6 Snooping statistics table exceeded the specifications of the forwarding engine resources.
  • Cause 941: The number of CAR ACLs for upstream traffic exceeded the forwarding engine resource specification.
  • Cause 949: The statistical resources for BIER IPv6 flow-based upstream statistics collection are insufficient.
  • Cause 950: The forwarding entry resources for BIER IPv6 flow-based upstream statistics collection are insufficient.
  • Cause 951: The number of color-sliceid mapping table resources exceeded the forwarding engine resource specifications.
  • Cause 968: The BGPFLOW REFLUENCE TCAM resources are insufficient.
  • Cause 979: The usage of CAR statistics resources of the value-added service exceeds the forwarding engine specification of the board.
  • Cause 980: The number of traffic-class-map entries exceeds the specification of the forwarding engine.
  • Cause 982: The CAR statistics resource usage of the upstream interface CAR exceeds 95% of the forwarding engine specification.
  • Cause 983: The CAR statistics resource usage of the downstream interface CAR exceeds 95% of the forwarding engine specification.

Procedure

  • Cause 1: The number of established MPLS connections (TE) exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 2: The number of IPv4 FIBs exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 3: The number of IPv6 FIBs exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 4: The number of ARPs exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 5: The number of IPv6 NDs exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 6: The number of enabled statistics exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 7: The numbers of the applied traffic classification-based policies and CARs exceeded the specification of the forwarding resources

    Contact technical support engineers.

  • Cause 8: The number of established L2VPN connections exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 9: The number of multicast replication downstream interfaces exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 10: The number of BFD ACLs exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 11: The number of IPv4 multicast FIBs exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 12: The number of IPv6 multicast FIBs exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 13: The number of forward tokens in the board space exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 14: The number of FVRFs exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 15: The number of NDIndex exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 16: The number of Tunnel Index exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 17: The number of BFD Index exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 18: The number of VPLS LearnId exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 19: The number of broadcast domain Index exceeded the specifications of the forwarding engine resources

    Please check the number of broadcast domain configuration exceeds the upper limit or not.

  • Cause 20: The number of NS indexes exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 21: The number of Ring Index exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 25: The number of MLID exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 27: The host table prefix resource usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 28: The route table prefix resource usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 29: The next hop resource usage for equal-cost routes has exceeded 90%.

    Contact technical support engineers.

  • Cause 30: The Layer 3 interface table resource usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 31: The next hop resource usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 32: The tunnel decapsulation table resource usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 33: The number of QINQ tag pairs exceeds the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 35: Certain IPv4 full rules cannot be delivered, resulting in interruption of some services refer to ipv4 full rulse lose efficacy.

    Contact technical support engineers.

  • Cause 36: Certain IPv4 mask rules cannot be delivered, causing involved services to fail to take effect.

    Contact technical support engineers.

  • Cause 37: Certain IPv6 full rules cannot be delivered, causing involved services to fail to take effect.

    Contact technical support engineers.

  • Cause 38: Certain IPv6 mask rules cannot be delivered, causing involved services to fail to take effect.

    Contact technical support engineers.

  • Cause 39: Certain characteristic code rules cannot be delivered, causing involved services to fail to take effect.

    Contact technical support engineers.

  • Cause 40: Certain complex rules cannot be delivered, causing involved services to fail to take effect.

    Contact technical support engineers.

  • Cause 41: Certain Tcp Flag rules cannot be delivered, causing involved services to fail to take effect.

    Contact technical support engineers.

  • Cause 42: The number of enabled ccm send numbers exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 43: The number of enabled ccm receive numbers exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 44: The number of enabled slm instance numbers exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 45: The number of enabled 1dm instance numbers exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 46: The number of enabled 2dm instance numbers exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 47: The IPv6 route table prefix resource usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 48: The number of IPv4 multicast group flow statistic ID exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 49: The number of IPv6 multicast group flow statistic ID exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 50: The number of nhp numbers exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 51: The number of netstream Index numbers exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 52: The number of enabled dlm instance numbers exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 53: The number of IPv4 BGP statistic ID exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 54: The number of IPv6 bgp statistic ID exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 55: The number of Link Layer Encapsulation database exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 57: The number of Large Exactly Match database exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 58: The number of Logical Interfaces exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 59: The number of Mac Multicast Index exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 61: The number of applied BGPFLOW VTCAM resources exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 62: The number of ACL Group exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 63: The number of Meter exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 64: The number of Counter exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 65: The number of Outbound ACL Entry exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 66: The number of Outbound ACL Group exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 67: The number of Outbound Meter exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 68: The number of Outbound Counter exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 69: The number of Multicast Index exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 70: The number of IPFPM loss-measure continual enable or delay-measure continual enable numbers exceeded the specifications of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 71: The number of bind table exceeded the specifications of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 72: ACL failed to be delivered.

    Contact technical support engineers.

  • Cause 73: The number of ARP entries exceeded 95% of the forwarding engine's resource specification.

    Contact technical support engineers.

  • Cause 103: The number of AT indexes exceeds the specifications of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 104: The number of flexible access sub-interfaces exceeds the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 105: The number of Inbound flow-wred exceeded the specification of the forwarding engine resources

    Check the flow-wred configuration.

  • Cause 106: The number of Outbound flow-wred exceeded the specification of the forwarding engine resources

    Check the flow-wred configuration.

  • Cause 109: The number of Inbound flow-queue wfq exceeded the specification of the forwarding engine resources.

    Check the flow-queue wfq configuration.

  • Cause 110: The number of Outbound flow-queue wfq exceeded the specification of the forwarding engine resources.

    Check the flow-queue wfq configuration.

  • Cause 111: The number of Inbound flow-queue cbs exceeded the specification of the forwarding engine resources.

    Check the flow-queue cbs configuration.

  • Cause 112: The number of Outbound flow-queue cbs exceeded the specification of the forwarding engine resources.

    Check the flow-queue cbs configuration.

  • Cause 113: The number of Inbound flow-queue pbs exceeded the specification of the forwarding engine resources.

    Check the flow-queue pbs configuration.

  • Cause 114: The number of Outbound flow-queue pbs exceeded the specification of the forwarding engine resources.

    Check the flow-queue pbs configuration.

  • Cause 115: The number of Inbound user-queue exceeded the specification of the forwarding engine resources.

    Check the user-queue configuration.

  • Cause 116: The number of Outbound user-queue exceeded the specification of the forwarding engine resources.

    Check the user-queue configuration.

  • Cause 117: The number of Inbound user-queue template exceeded the specification of the forwarding engine resources.

    Check the user-queue template configuration.

  • Cause 118: The number of Outbound user-queue template exceeded the specification of the forwarding engine resources.

    Check the user-queue template configuration.

  • Cause 119: The number of Inbound service-template exceeded the specification of the forwarding engine resources.

    Check the service-template configuration.

  • Cause 120: The number of Outbound service-template exceeded the specification of the forwarding engine resources.

    Check the service-template configuration.

  • Cause 121: The number of Inbound user-group-queue exceeded the specification of the forwarding engine resources.

    Check the user-group-queue configuration.

  • Cause 122: The number of Outbound user-group-queue exceeded the specification of the forwarding engine resources.

    Check the user-group-queue configuration.

  • Cause 123: The number of Inbound user-group-queue template exceeded the specification of the forwarding engine resources.

    Check the user-group-queue template configuration.

  • Cause 124: The number of Outbound user-group-queue template exceeded the specification of the forwarding engine resources.

    Check the user-group-queue template configuration.

  • Cause 125: The number of CAR IDs for upstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applying car stat resource.

  • Cause 126: The number of CAR IDs for downstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applying car stat resource.

  • Cause 127: The number of CAR remark templates for upstream traffic exceeded the forwarding engine resource specification.

    Check the car remark configuration.

  • Cause 128: The number of CAR remark templates for downstream traffic exceeded the forwarding engine resource specification.

    Check the car remark configuration.

  • Cause 129: The number of GIDs exceeded the forwarding engine resource specification.

    Check the configuration that applying acl stat resource.

  • Cause 130: The number of flow CAR indexes for upstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applying car stat resource.

  • Cause 131: The number of flow CAR indexes for downstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applying car stat resource.

  • Cause 132: The number of Behavior RE exceeded the specification of the forwarding engine resources.

    Check the number configuration that applied RE resource.

  • Cause 133: The number of Behavior NHP exceeded the specification of the forwarding engine resources.

    Check the configuration that applied NHP resource .

  • Cause 134: The number of IPv4 TCAM indexes for upstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applied IPv4 TCAM resource .

  • Cause 135: The number of IPv6 TCAM indexes for upstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applied IPv6 TCAM resource .

  • Cause 136: The number of IPv4 TCAM indexes for downstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applied IPv4 TCAM resource .

  • Cause 137: The number of IPv6 TCAM indexes for downstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applied IPv6 TCAM resource .

  • Cause 138: The number of Inbound Qppb car exceeded the specification of the forwarding engine resources.

    Check the configuration that applying car stat resource.

  • Cause 139: The number of Outbound Qppb car exceeded the specification of the forwarding engine resources.

    Check the configuration that applying car stat resource.

  • Cause 140: The number of Inbound Mirror table exceeded the specification of the forwarding engine resources.

    Check the configuration that applying mirror table resource.

  • Cause 141: The number of Outbound Mirror table exceeded the specification of the forwarding engine resources.

    Check the configuration that applying mirror table resource.

  • Cause 142: The number of Inbound Capture packet mirror table exceeded the specification of the forwarding engine resources.

    Check the configuration that applying mirror table resource.

  • Cause 143: The number of Outbound Capture Packet mirror table exceeded the specification of the forwarding engine resources.

    Check the configuration that applying mirror table resource.

  • Cause 144: The number of inbound suppression car exceeded the specification of the forwarding engine resources.

    Check the configuration that applying car stat resource.

  • Cause 145: The number of outbound suppression car exceeded the specification of the forwarding engine resources.

    Check the configuration that applying car stat resource.

  • Cause 146: The number of Inbound mirror car exceeded the specification of the forwarding engine resources.

    Check the configuration that applying car stat resource.

  • Cause 147: The number of Outbound mirror car exceeded the specification of the forwarding engine resources.

    Check the configuration that applying car stat resource.

  • Cause 148: The number of Behavior nst exceeded the specification of the forwarding engine resources.

    Check the configuration that applying nst resource.

  • Cause 149: The number of Inbound Profile Suppression car exceeded the specification of the forwarding engine resources.

    Check the configuration that applying car stat resource.

  • Cause 150: The number of Outbound Profile Suppression car exceeded the specification of the forwarding engine resources.

    Check the configuration that applying car stat resource.

  • Cause 151: The number of Inbound Profile Suppression car stat exceeded the specification of the forwarding engine resources.

    Check the configuration that applying car stat resource.

  • Cause 152: The number of Outbound Profile Suppression car stat exceeded the specification of the forwarding engine resources.

    Check the configuration that applying car stat resource.

  • Cause 153: The number of Inbound Profile single car exceeded the specification of the forwarding engine resources.

    Check the configuration that applying car stat resource.

  • Cause 154: The number of Outbound Profile single car exceeded the specification of the forwarding engine resources.

    Check the configuration that applying car stat resource.

  • Cause 155: The number of inbound profile single car stat exceeded the specification of the forwarding engine resources.

    Check the configuration that applying car stat resource.

  • Cause 156: The number of outbound profile single car stat exceeded the specification of the forwarding engine resources.

    Check the configuration that applying car stat resource.

  • Cause 157: The number of ACL statistics indexes for upstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applying acl stat resource.

  • Cause 158: The number of ACL statistics indexes for downstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applying acl stat resource.

  • Cause 159: The number of ACL CAR statistics indexes exceeded the forwarding engine resource specification.

    Check the configuration that applying car stat resource.

  • Cause 160: The number of CAR statistics indexes for upstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applying car stat resource.

  • Cause 161: The number of CAR statistics indexes for downstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applying car stat resource.

  • Cause 162: The number of L2 TCAM indexes for upstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applied L2 tcam resource .

  • Cause 163: The number of L2 TCAM indexes for downstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applied L2 tcam resource .

  • Cause 165: The number of MPLS ARP table numbers exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 166: The number of MPLS ARP table numbers exceeded the threshold of the forwarding resources

    Contact technical support engineers.

  • Cause 167: The number of the Layer 2 traffic suppression statistic exceeds the specification of the forwarding engine resources

    Please check the number of Layer 2 traffic suppression statistic configuration exceeds the upper limit or not.

  • Cause 169: The number of SNOOP exceeded the specifications of the forwarding engine resources

    Contact technical support engineers.

  • Cause 176: The trunk loadbalance dynamic adjustment resource usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 177: The number of Flexible Access exceeds 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 178: The number of Main and Subif exceeds 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 179: The number of DCN statistics exceeds 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 180: The number of Statistics exceeds 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 181: The number of EOAM exceeded the 90% of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 182: The number of Y.1564 exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 183: The number of L2VPN exceeds 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 184: The number of Vlan exceeded the 90% of the forwarding engine resources

    Contact technical support engineers.

  • Cause 185: The number of Bridge Domain exceeded the 90% of the forwarding engine resources

    Contact technical support engineers.

  • Cause 186: The number of VRRP resource usage has exceeded 90%

    Contact technical support engineers.

  • Cause 187: The number of TWAMP resource usage has exceeded 90%

    Contact technical support engineers.

  • Cause 188: The number of BFD resource usage has exceeded 90%

    Contact technical support engineers.

  • Cause 189: The number of QINQ tag pairs exceeds 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 190: The number of EVC exceeds 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 191: The number of Inbound BehaviorSuppCar id exceeded the specification of the forwarding engine resources.

    Check the BehaviorSuppCar configuration.

  • Cause 192: The number of Outbound BehaviorSuppCar id exceeded the specification of the forwarding engine resources.

    Check the BehaviorSuppCar configuration.

  • Cause 193: The number of QPPB ACL Entry exceeded the specification of the forwarding engine resources.

    Check the QPPB-policy configuration.

  • Cause 194: The number of QPPB Gid exceeded the specification of the forwarding engine resources.

    Check the QPPB-policy configuration.

  • Cause 195: The tunnel decapsulation table resource exceeded the specifications of the forwarding engine resources.

    Please contact technical support personnel.

  • Cause 196: The number of IPFPM exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 197: The number of RFC2544 exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 198: The number of available NHP entries was insufficient, and the dynamic load balancing adjustment result became ineffective.

    Contact technical support engineers.

  • Cause 199: The number of the Layer 2 traffic suppression statistic exceeds 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 200: The trunk loadbalance dynamic adjustment resource usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 201: The number of linear-RE index exceeded the specification of the forwarding engine resources.

    Check the number of linear-RE resource applied for l3vpn pop-go service, please contact Huawei technical support personnel.

  • Cause 202: The numbers of the applied CP IPv4 ACL exceeded the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 203: The numbers of the applied CP IPv6 ACL exceeded the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 241: The number of DP exceeded the specification of the forwarding engine resources.

    Check the DP configuration.

  • Cause 242: The number of inbound GQ shaper exceeded the specification of the forwarding engine resources.

    Check the GQ shaper configuration.

  • Cause 243: The number of outbound GQ shaper exceeded the specification of the forwarding engine resources.

    Check the GQ shaper configuration.

  • Cause 244: The number of inbound VI exceeded the specification of the forwarding engine resources.

    Check the VI configuration.

  • Cause 245: The number of outbound VI exceeded the specification of the forwarding engine resources.

    Check the VI configuration.

  • Cause 246: The number of inbound VI shaper exceeded the specification of the forwarding engine resources.

    Check the VI shaper configuration.

  • Cause 247: The number of outbound VI shaper exceeded the specification of the forwarding engine resources.

    Check the VI shaper configuration.

  • Cause 248: The number of inbound VI template exceeded the specification of the forwarding engine resources.

    Check the VI template configuration.

  • Cause 249: The number of outbound VI template exceeded the specification of the forwarding engine resources.

    Check the VI template configuration.

  • Cause 250: The number of port-wred exceeded the specification of the forwarding engine resources.

    Check the port-wred configuration.

  • Cause 253: The number of pop-go RE exceeded the specification of the forwarding engine resources.

    Check the number configuration that applied RE resource.

  • Cause 255: The number of APS exceeds 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 256: The number of MPLS OAM/TPOAM exceeds 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 257: The number of inbound chip user-queue exceeded the specification of the forwarding engine resources.

    Check the chip user-queue configuration.

  • Cause 258: The number of outbound chip user-queue exceeded the specification of the forwarding engine resources.

    Check the chip user-queue configuration.

  • Cause 260: The number of PW Hqos exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 261: The number of MPLS OAM/TPOAM single-ended frame loss measurement exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 262: The number of MPLS-TP OAM one-way frame delay measurement exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 263: The number of MPLS OAM/TPOAM two-way frame delay measurement exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 264: The number of MPLS-TP OAM dual-ended frame loss measurement exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 265: The number of MPLS OAM/TPOAM single-ended frame loss measurement exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 266: The number of MPLS-TP OAM one-way frame delay measurement exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 267: The number of MPLS OAM/TPOAM two-way frame delay measurement exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 268: The number of MPLS-TP OAM dual-ended frame loss measurement exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 269: The number of MPLS OAM/TPOAM exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 270: The number of MPLS APS exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 271: The number of TM inbound SQ resources usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 272: The number of TM outbound SQ resources usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 273: The number of SLOT inbound SQ resources usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 274: The number of SLOT outbound SQ resources usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 276: The number of Inbound random-discard exceeded the specification of the forwarding engine resources.

    Check the random-discard configuration.

  • Cause 277: The number of Outbound random-discard exceeded the specification of the forwarding engine resources.

    Check the random-discard configuration.

  • Cause 280: The number of CGN or IPsec ACL TCAM exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 281: The number of the applied CP IPv4 ACLs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 282: The number of the applied CP IPv6 ACLs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 285: The number of ERPS exceeds 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 286: The number of the applied BEHAVIOR_VPNGROUPs exceeded the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 287: The number of the applied BEHAVIOR_VPNGROUPs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 288: The number of the applied DHCPSNP_BINDTBLs exceeded 80% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 289: The number of the applied QPPB_IPV4_ACL_INs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 290: The number of the applied QPPB_IPV6_ACL_INs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 291: The number of the applied QPPB_IPV4_ACL_OUTs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 292: The number of the applied QPPB_IPV6_ACL_OUTs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 293: The number of the applied REFLUENCE_VTCAMs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 294: The number of the applied BGPFLOW_VTCAMs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 295: The number of multicast out-interfaces exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 300: The number of VPLS exceeds 90% of the specification of the forwarding engine resources.

    Check the configuration that applying vpls table resource.

  • Cause 301: The number of EVPN exceeds 90% of the specification of the forwarding engine resources.

    Check the configuration that applying evpn table resource.

  • Cause 302: The number of L2TPV3 exceeds 90% of the specification of the forwarding engine resources.

    Check the configuration that applying L2TPV3 table resource.

  • Cause 304: The number of L2 multicast FIBs exceeded 95% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 305: The number of CAR IDs for upstream traffic exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 306: The number of CAR IDs for downstream traffic exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 307: The number of GIDs exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 308: The number of ACL statistics indexes for upstream traffic exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 309: The number of ACL statistics indexes for downstream traffic exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 310: The number of flow CAR indexes for upstream traffic exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 311: The number of flow CAR indexes for downstream traffic exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 312: The number of IPv4 TCAM indexes for upstream traffic exceeded 95% of the forwarding engine resource specification(The uplink and downlink share resources, and pre-alarms may be generated in both directions).

    Contact technical support engineers.

  • Cause 313: The number of IPv4 TCAM indexes for downstream traffic exceeded 95% of the forwarding engine resource specification(The uplink and downlink share resources, and pre-alarms may be generated in both directions).

    Contact technical support engineers.

  • Cause 314: The number of IPv6 TCAM indexes for upstream traffic exceeded 95% of the forwarding engine resource specification(The uplink and downlink share resources, and pre-alarms may be generated in both directions).

    Contact technical support engineers.

  • Cause 315: The number of IPv6 TCAM indexes for downstream traffic exceeded 95% of the forwarding engine resource specification(The uplink and downlink share resources, and pre-alarms may be generated in both directions).

    Contact technical support engineers.

  • Cause 316: The number of VPLS exceeds the specification of the forwarding engine resources.

    Check the vpls configuration.

  • Cause 317: The number of EVPN exceeds the specification of the forwarding engine resources.

    Check the vpls configuration.

  • Cause 318: The number of IPv4 FIB entries exceeded 95% of the forwarding engine's resource specification.

    Contact technical support engineers.

  • Cause 319: The number of IPv6 FIB entries exceeded 95% of the forwarding engine's resource specification.

    Contact technical support engineers.

  • Cause 320: The number of IPv6 NDH entries exceeded 95% of the forwarding engine's resource specification.

    Contact technical support engineers.

  • Cause 321: The number of IPv4 multicast FIBs exceeded 95% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 322: The number of IPv6 multicast FIBs exceeded 95% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 323: The number of PW-VE or remote interface's index exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 325: The number of resources in the IPv4 GRE tunnel decapsulation table exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 326: The number of resources in the IPv6 GRE tunnel decapsulation table exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 328: The number of PBB exceeds 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 329: The number of PBB exceeds the specification of the forwarding engine resources.

    Check the PBB configuration.

  • Cause 334: The number of IPv4 UCL TCAM indexes for upstream traffic exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 335: The number of IPv4 UCL TCAM indexes for downstream traffic exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 336: The number of IPv6 UCL TCAM indexes for upstream traffic exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 337: The number of IPv6 UCL TCAM indexes for downstream traffic exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 338: The number of IPv4 UCL TCAM indexes for upstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applied IPv4 UCL TCAM resources.

  • Cause 339: The number of IPv4 UCL TCAM indexes for downstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applied IPv4 UCL TCAM resources.

  • Cause 340: The number of IPv6 UCL TCAM indexes for upstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applied IPv6 UCL TCAM resources.

  • Cause 341: The number of IPv6 UCL TCAM indexes for downstream traffic exceeded the forwarding engine resource specification.

    Check the configuration that applied IPv6 UCL TCAM resources.

  • Cause 342: The number of CGN or IPsec ACL TCAM exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 343: The number of TM inbound GQ resources usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 344: The number of TM outbound GQ resources usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 345: The segment routing LabelStack table resource usage exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 346: The segment routing table resource usage has exceeded 95% of the forwarding engine specification.

    Contact technical support engineers.

  • Cause 347: The number of enabled statistics exceeded 95% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 348: The number of NHP indexes exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 349: The number of NHP indexes exceeded the forwarding engine resource specification.

    Check the configuration that applied NHP resource.

  • Cause 350: The number of NST indexes exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 351: The number of NST indexes exceeded the forwarding engine resource specification.

    Check the configuration that applied NST resource.

  • Cause 352: The number of MLID resource exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 354: The number of L2PT resource exceeds 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 355: The number of L2PT resource exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 357: The number of pool-0 flow-queue wfq exceeded the specification of the forwarding engine resources.

    Check the flow-queue wfq configuration.

  • Cause 358: The number of pool-1 flow-queue wfq exceeded the specification of the forwarding engine resources.

    Check the flow-queue wfq configuration.

  • Cause 359: The number of pool-0 flow-queue cbs exceeded the specification of the forwarding engine resources.

    Check the flow-queue cbs configuration.

  • Cause 360: The number of pool-1 flow-queue cbs exceeded the specification of the forwarding engine resources.

    Check the flow-queue cbs configuration.

  • Cause 361: The number of pool-0 flow-queue pbs exceeded the specification of the forwarding engine resources.

    Check the flow-queue pbs configuration.

  • Cause 362: The number of pool-1 flow-queue pbs exceeded the specification of the forwarding engine resources.

    Check the flow-queue pbs configuration.

  • Cause 363: The number of pool-0 user-queue exceeded the specification of the forwarding engine resources.

    Check the user-queue configuration.

  • Cause 364: The number of pool-1 user-queue exceeded the specification of the forwarding engine resources.

    Check the user-queue configuration.

  • Cause 365: The number of pool-0 user-queue template exceeded the specification of the forwarding engine resources.

    Check the user-queue template configuration.

  • Cause 366: The number of pool-1 user-queue template exceeded the specification of the forwarding engine resources.

    Check the user-queue template configuration.

  • Cause 367: The number of pool-0 service-template exceeded the specification of the forwarding engine resources.

    Check the service-template configuration.

  • Cause 368: The number of pool-1 service-template exceeded the specification of the forwarding engine resources.

    Check the service-template configuration.

  • Cause 369: The number of pool-0 user-group-queue exceeded the specification of the forwarding engine resources.

    Check the user-group-queue configuration.

  • Cause 370: The number of pool-1 user-group-queue exceeded the specification of the forwarding engine resources.

    Check the user-group-queue configuration.

  • Cause 371: The number of pool-0 user-group-queue template exceeded the specification of the forwarding engine resources.

    Check the user-group-queue template configuration.

  • Cause 372: The number of pool-1 user-group-queue template exceeded the specification of the forwarding engine resources.

    Check the user-group-queue template configuration.

  • Cause 373: The number of pool-0 chip user-queue exceeded the specification of the forwarding engine resources.

    Check the chip user-queue configuration.

  • Cause 374: The number of pool-1 chip user-queue exceeded the specification of the forwarding engine resources.

    Check the chip user-queue configuration.

  • Cause 383: The number of pool-0 flow-wred exceeded the specification of the forwarding engine resources

    Check the flow-wred configuration.

  • Cause 384: The number of pool-1 flow-wred exceeded the specification of the forwarding engine resources

    Check the flow-wred configuration.

  • Cause 387: The bandwidth of large buffer usage has exhausted.

    Contact technical support engineers.

  • Cause 388: The number of the user defined flow applied CP IPv4 ACLs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 389: The number of the dynamic link protection applied CP IPv4 ACLs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 390: The number of PW source tunnels exceeds the specifications of the forwarding engine.

    Check the static pw configuration.

  • Cause 393: The number of BGP flowspec RE exceeded the specification of the forwarding engine resources.

    Please check the configuration that applied RE resource.

  • Cause 394: The number of BGP flowspec RE exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 395: The number of VXLAN resource exceeds 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 396: The number of VXLAN resource exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 397: The number of ETH-Test instances exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 398: The sum of all member interfaces' weights of a trunk interface exceeded the maximum value supported by the board.

    Check the configurations of the trunk member interfaces.

  • Cause 399: The number of resources in the IPv4 VXLAN tunnel decapsulation table exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 400: The number of IPFPM resource usage has exceeded the specifications of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 401: The number of TWAMP resource usage has exceeded the specifications of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 402: The number of user-queue CIR template exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 403: The number of user-queue EIR template exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 404: The number of flow-queue shaping template exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 405: The number of flow-queue share-shaping template exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 410: The number of VNI*peer resources exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 411: The number of the dynamic link protection applied CP IPv4 ACLs exceeded the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 412: The number of the user defined flow applied CP IPv4 ACLs exceeded the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 413: The number of RFC2544 exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 414: The number of Main and Subif exceeds the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 415: The number of Statistics exceeds the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 416: The number of resources in the static-cr-lsp source interface check table exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 417: The number of resources in the static-cr-lsp source interface check table exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 418: The number of IPv6 ACL TCAM resources usage has exceeded 90%.

    Check the IPv6 ACL configuration or contact Huawei technical support personnel.

  • Cause 419: The number of IPv6 ACL TCAM resources usage has exhausted.

    Check the IPv6 ACL configuration or contact Huawei technical support personnel.

  • Cause 420: The number of remote-interface exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 421: The number of remote-interface exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 422: The number of Priority Car Statistics exceeds 90% of the specification of the forwarding engine resources.

    Please check priority car configuration.

  • Cause 423: The number of Priority Car Statistics exceeds the specification of the forwarding engine resources.

    Please check priority car configuration.

  • Cause 424: The numbers of the applied CP L2 ACL exceeded the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 425: The number of the applied CP L2 ACLs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 426: The number of the CAR indexes for arpvlancar and soc defend exceeded 90% of the forwarding engine resource specification.

    Please contact technical support personnel.

  • Cause 427: The number of the CAR indexes for arpvlancar and soc defend exceeded the forwarding engine resource specification.

    Please contact technical support personnel.

  • Cause 428: The number of the statistics indexes for arpvlancar and soc defend exceeded 90% of the forwarding engine resource specification.

    Please contact technical support personnel.

  • Cause 429: The number of the statistics indexes for arpvlancar and soc defend exceeded the forwarding engine resource specification.

    Please contact technical support personnel.

  • Cause 430: The number of the CAR indexes for port vlan car and igmp vlan car exceeded 90% of the forwarding engine resource specification.

    Please contact technical support personnel.

  • Cause 431: The number of the CAR indexes for port vlan car and igmp vlan car exceeded the forwarding engine resource specification.

    Please contact technical support personnel.

  • Cause 432: The number of the statistics indexes for port vlan car and igmp vlan car exceeded 90% of the forwarding engine resource specification.

    Please contact technical support personnel.

  • Cause 433: The number of the statistics indexes for port vlan car and igmp vlan car exceeded the forwarding engine resource specification.

    Please contact technical support personnel.

  • Cause 434: The number of the CAR indexes for BGPFLOW exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 435: The number of the CAR indexes for BGPFLOW exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 436: The number of Inbound Mirror table exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 437: The number of Outbound Mirror table exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 438: The number of Inbound Capture packet mirror table exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 439: The number of Outbound Capture Packet mirror table exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 440: The number of Inbound mirror car exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 441: The number of Outbound mirror car exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 442: The number of the inbound CAR indexes for QPPB exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 443: The number of the inbound CAR indexes for QPPB exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 444: The number of the outbound CAR indexes for QPPB exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 445: The number of the outbound CAR indexes for QPPB exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 446: The number of the QPPB IPv4 inbound statistics indexes for QPPB exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 447: The number of the QPPB IPv4 inbound statistics indexes for QPPB exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 448: The number of the QPPB IPv4 outbound statistics indexes for QPPB exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 449: The number of the QPPB IPv4 outbound statistics indexes for QPPB exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 450: The number of the QPPB IPv6 inbound statistics indexes for QPPB exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 451: The number of the QPPB IPv6 inbound statistics indexes for QPPB exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 452: The number of the QPPB IPv6 outbound statistics indexes for QPPB exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 453: The number of the QPPB IPv6 outbound statistics indexes for QPPB exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 454: The number of the QPPB car statistics indexes for QPPB exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 455: The number of the QPPB car statistics indexes for QPPB exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 456: The number of the DHCPSNP statistics indexes for DHCPSNP exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 457: The number of the RE indexes for REDIRECT exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 458: The number of the RE indexes for REDIRECT exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 459: The number of the NST indexes for REDIRECT exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 460: The number of the NST indexes for REDIRECT exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 461: The number of the NHP indexes for REDIRECT exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 462: The number of the NHP indexes for REDIRECT exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 465: The number of BGPFLOW GIDs exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 466: The number of BGPFLOW Gids exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 469: The number of resources in the MPLS ARP exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 470: The number of resources in the MPLS ARP exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 471: The number of resources in the TE statistics exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 472: The number of resources in the TE statistics exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 473: The number of resources in the LSPCAR index exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 474: The number of resources in the LSPCAR index exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 475: The number of resources in the P2MP MRE table exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 476: The number of resources in the P2MP MRE table exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 477: The number of resources in the RECYCLE OUTSEGMENT index exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 478: The number of resources in the RECYCLE OUTSEGMENT index exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 479: The number of resources in theRECYCLE INSEGMENT index exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 480: The number of resources in the RECYCLE INSEGMENT index exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 481: The number of resources in the MPLS NST index exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 482: The number of resources in the MPLS NST index exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 483: The number of resources in the statistics ID exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 484: The number of resources in the statistics ID exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 485: The number of resources in the P2MP BUD insegment table exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 486: The number of resources in the P2MP BUD insegment table exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 487: The number of resources in the MLDP RE index exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 488: The number of resources in the MLDP RE index exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 489: The number of resources in the MLDP RECYCLE INSEGMENT index exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 490: The number of resources in the MLDP RECYCLE INSEGMENT index exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 491: The number of resources in the MLDP RECYCLE OUTSEGMENT index exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 492: The number of resources in the MLDP RECYCLE OUTSEGMENT index exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 493: The number of resources in the MLDP BUD insegment index exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 494: The number of resources in the MLDP BUD insegment index exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 495: The number of resources in the P2MP NST index exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 496: The number of resources in the P2MP NST index exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 497: The number of VLL hard pipe services exceeds the specification of the forwarding engine resources.

    Please contact technical support personnel.

  • Cause 498: The number of BFD GIDs exceeded the forwarding engine resource specification.

    Please contact technical support personnel.

  • Cause 499: The number of VPLS PW NHP resources exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 500: The number of 1588 exceeded the 90% of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 501: The number of used virtual access service resources exceeded 90% of the total resources on the forwarding engine.

    Please contact technical support personnel.

  • Cause 502: The number of the INSEG_VRF entries exceeds the forwarding engine specifications.

    Please contact technical support personnel.

  • Cause 503: The number of dynamic load balancing IDs exceeds the forwarding engine specifications.

    Please contact technical support personnel.

  • Cause 504: The number of the community entries exceeds the forwarding engine specifications.

    Please contact technical support personnel.

  • Cause 505: The number of the IPv4 Tunnel indexes exceeds the forwarding engine resource specification.

    Please contact technical support personnel.

  • Cause 506: The number of SMA AS indexes exceeded the specification of the forwarding engine resources.

    Please contact technical support personnel.

  • Cause 507: The number of SMA FIBV6 exceeds the specification of the forwarding engine resources.

    Please contact technical support personnel.

  • Cause 508: The number of the applied QPPB ACLs exceeded 90% of the specification of the forwarding resources.

    Please contact technical support personnel.

  • Cause 509: The number of QPPB ACLs exceeded the specification of the forwarding engine resources.

    Check the QPPB-policy configuration.

  • Cause 510: The number of the applied inbound QPPB EXTACTIONs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 511: The number of inbound QPPB EXTACTIONs exceeded the specification of the forwarding engine resources.

    Check the QPPB-policy configuration.

  • Cause 512: The number of the applied outbound QPPB EXTACTIONs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 513: The number of outbound QPPB EXTACTIONs exceeded the specification of the forwarding engine resources.

    Check the QPPB-policy configuration.

  • Cause 516: The number of mirror observe table exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 517: The number of mirror observe table exceeded the specification of the board forwarding engine resources.

    Contact technical support engineers.

  • Cause 518: The number of Mirror filter table exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 519: The number of Mirror filter table exceeded the specification of the board forwarding engine resources.

    Contact technical support engineers.

  • Cause 520: The number of mirror statistics table exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 521: The number of mirror statistics table exceeded the specification of the board forwarding engine resources.

    Contact technical support engineers.

  • Cause 522: The number of downstream interfaces to which mirror data is replicated to exceeded 90% of the specification supported by the entire system.

    Contact technical support engineers.

  • Cause 523: The number of downstream interfaces to which mirror data is replicated to exceeded the specification supported by the entire system.

    Contact technical support engineers.

  • Cause 524: The number of resources in the MLDP BUD outsegment index exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 525: The number of resources in the MLDP BUD outsegment index exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 526: The number of resources in the MLDP egress nodes statistics exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 527: The number of resources in the MLDP egress nodes statistics exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 528: The number of resources in the MLDP ingress nodes statistics exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 529: The number of resources in the MLDP ingress nodes statistics exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 530: The number of resources in the MPLS TE ingress NHP index exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 531: The number of resources in the MPLS TE ingress NHP index exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 532: The number of resources in the MPLS P node loadbalance RE table index exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 533: The number of resources in the MPLS P node loadbalance RE table index exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 534: The number of resources in the MPLS E node tunnel index exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 535: The number of resources in the MPLS E node tunnel index exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 536: The number of NQA exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 537: The number of NQA exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 538: The number of resources in the P2MP BUD outsegment table exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 539: The number of resources in the P2MP BUD outsegment table exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 540: The number of resources in the P2MP egress nodes satistics exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 541: The number of resources in the P2MP egress nodes statistics exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 542: The number of resources in the P2MP ingress nodes satistics exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 543: The number of resources in the P2MP ingress nodes statistics exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 544: The number of resources in the LSP OUT MIB satistics exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 545: The number of resources in the LSP OUT MIB statistics exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 546: The number of MPLS TE indexes for downstream traffic exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 547: The number of MPLS TE indexes for downstream traffic exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 548: The number of PW-VE or remote interface's index exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 549: The number of the bgpflow car statistics indexes exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 550: The number of the bgpflow car statistics indexes exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 551: The number of the CAR indexes for layer 2 protocol tunnel exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 552: The number of the CAR indexes for layer 2 protocol tunnel exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 553: The number of vpls pw suppression statistics services exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 554: The number of vpls pw suppression statistics services exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 555: The number of Mirror user rule table exceeded 90% of the specification of the forwarding engine resource.

    Contact technical support engineers.

  • Cause 556: The number of Mirror user rule table exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 557: The number of Mirror table exceeded 90% of the specification of the forwarding engine resources.

    The number of mirror services exceeds 90% of the service specifications. Plan the mirroring services properly.

  • Cause 558: The number of Mirror table exceeded the specification of the forwarding engine resources.

    Check whether the number of mirror tables exceeds the specifications. If yes, delete unneeded mirror configurations (such as port mirror and flow mirror).

  • Cause 559: The number of mirror car exceeded 90% of the specification of the forwarding engine resources.

    The number of mirror CAR services exceeds 90% of the service specifications. Plan the mirror CAR services properly.

  • Cause 560: The number of mirror car exceeded the specification of the forwarding engine resources.

    Check whether the number of mirror CAR service configurations exceeds the specifications. If yes, delete unneeded mirror CAR service configurations (such as port mirror CAR and flow mirror CAR).

  • Cause 561: The number of Y.1564 exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 562: The number of VPLS PW HQoS services exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 563: The number of the BGP Flowspec IPv6 ACL exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 564: The number of the applied BGP Flowspec IPv6 ACL exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 565: The number of L2TPV3 tunnel exceeds the specification of the forwarding engine resources

    Please check the L2TPV3 tunnel configuration.

  • Cause 566: The number of the applied BGP Flowspec IPv6 refluence exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 567: The number of Mirror user offset table exceeded 90% of the specification of the forwarding engine resource.

    Contact technical support engineers.

  • Cause 568: The number of Mirror user offset table exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 569: The number of TM outbound VI resources usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 572: Downstream mirroring resources failed to be to allocated to the APS service because the number of used downstream mirroring resources exceeded the forwarding engine specification.

    Contact technical support engineers.

  • Cause 573: MPLS-ARP resources failed to be to allocated to the low-speed service because the number of used MPLS-ARP resources exceeded the forwarding engine specification.

    Contact technical support engineers.

  • Cause 574: The number of the applied BGP Flowspec IPv6 refluence exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 577: The number of MAC accounting statistics entries exceeds the specification of the forwarding engine.

    Contact technical support engineers.

  • Cause 582: The number of EVC sub-interface validity check entries exceeded the maximum number supported by the forwarding engine.

    Contact technical support engineers.

  • Cause 583: The number of the statistics indexes for random-discard exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 584: L2mcV6 mre stat resources useage exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 585: L2mcV6 mre stat resources useage exceeded the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 586: The number of L2 Traffic Suppression Inbound statistics exceeded 90% of the specification of the forwarding engine resource.

    Contact technical support engineers.

  • Cause 587: The number of L2 Traffic Suppression Inbound statistics exceeded the specification of the forwarding engine resource.

    Contact technical support engineers.

  • Cause 588: The number of L2 Traffic Suppression Outbound statistics exceeded 90% of the specification of the forwarding engine resource.

    Contact technical support engineers.

  • Cause 589: The number of L2 Traffic Suppression Outbound statistics exceeded the specification of the forwarding engine resource.

    Contact technical support engineers.

  • Cause 590: The number of user exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 591: The number of Lac user exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 595: The number of user on card0 exceeded 90% of the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 596: The number of user on card1 exceeded the 90% of the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 597: The number of user on card0 exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 598: The number of user on card1 exceeded the specification of the forwarding engine resources

    Contact technical support engineers.

  • Cause 603: The number of the applied DHCPSNP_ACLs exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 604: The number of the applied DHCPSNP_ACLs exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 605: The number of IPv6 L2 multicast FIBs exceeded 95% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 606: The number of MLIB resource exceeded 95% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 607: The number of MLIB exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 608: The number of resources in the 4over6 tunnel decapsulation table exceeded the specification of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 609: The number of IPv6 Address in the IPB table exceeded the specification of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 610: The number of interface URPF ACL Entry exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 611: The number of interface URPF ACL Entry exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 612: The number of the hqos's arithmetic table exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 613: The number of the DHCPSNP statistics indexes for DHCPSNP exceeded the forwarding engine resources specification.

    Contact technical support engineers.

  • Cause 616: The token-nse table resource usage has exceeded 90%.

    Contact technical support engineers.

  • Cause 617: The token-nse table resource exceeded the specifications of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 618: The number of resources in the P2MP te statistics exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 619: The number of resources in the P2MP te statistics exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 620: The number of resources in the multicast ap replication tunnel vlink loopback protection NHP table exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 621: The number of resources in the multicast ap replication tunnel vlink loopback protection NHP table exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 622: The number of resources in the multicast ap replication tunnel vlink loopback protection NST table exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 623: The number of resources in the multicast ap replication tunnel vlink loopback protection NST table exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 624: The number of resources in the multicast ap ingress NHP table exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 625: The number of resources in the multicast ap ingress NHP table exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 626: The number of resources in the multicast ap ingress NST table exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 627: The number of resources in the multicast ap ingress NST table exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 628: The number of resources in the P2MP trunk load sharing NHP exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 629: The number of resources in the P2MP trunk load sharing NHP exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 630: The number of resources in the MLDP leaf exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 631: The number of resources in the MLDP leaf exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 632: The number of resources in the P2MP leaf exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 633: The number of resources in the P2MP leaf exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 634: The number of BFD resource usage has exceeded the specifications of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 635: The number of EOAM resource usage has exceeded the specifications of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 636: The number of VRRP resource usage has exceeded the specifications of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 637: Loopback forwarding services configured on VBDIF interfaces exceeded 90% of the total loopback forwarding resources supported by the forwarding engine.

    Contact technical support engineers.

  • Cause 638: The number of VBDIF interfaces enabled with loopback forwarding exceeded the specification of the forwarding engine.

    Contact technical support engineers.

  • Cause 639: The number of portcar exceeded the 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 640: The number of portcar exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 641: The number of portcarstat exceeded the 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 642: The number of portcarstat exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 643: The number of UDFV6_VTCAM exceeded the 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 644: The number of UDFV6_VTCAM exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 645: The number of DLPV6_VTCAM exceeded the 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 646: The number of DLPV6_VTCAM exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 647: The number of GTSM_VTCAM exceeded the 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 648: The number of GTSM_VTCAM exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 649: The number of GTSM_VTCAMV6 exceeded the 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 650: The number of GTSM_VTCAMV6 exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 651: The number of label statistical tables exceeded the forwarding engine specification.

    Check for multi-PE route configuration and determine whether the number of multi-PE routes exceeds the label statistical table specification. If the table specification is exceeded, delete the redundant multi-PE routes.

  • Cause 652: The number of label statistical tables exceeded 95% of the forwarding engine specification.

    Check for multi-PE route configuration and determine whether the number of multi-PE routes exceeds the label statistical table specification.

  • Cause 653: The number of local SID tables for SRv6 exceeded the forwarding engine specification.

    Check the SRv6 configuration and check whether the number of entries in the local SID table exceeds the upper limit.

  • Cause 654: The number of millisecond-level configuration table resources collected by Telemetry exceeded 95% of the upper limit supported by the forwarding engine.

    The configured number of instances collected by Telemetry exceeded the upper limit. Change the collection interval.

  • Cause 655: The number of millisecond-level configuration table resources collected by Telemetry exceeded the upper limit supported by the forwarding engine.

    The configured number of instances collected by Telemetry exceeded the upper limit. Change the collection interval.

  • Cause 656: The number of second-level configuration table resources collected by Telemetry exceeded 95% of the upper limit supported by the forwarding engine.

    The configured number of instances collected by Telemetry exceeded the upper limit. Change the collection interval.

  • Cause 657: The number of second-level configuration table resources collected by Telemetry exceeded the upper limit supported by the forwarding engine.

    The configured number of instances collected by Telemetry exceeded the upper limit. Change the collection interval.

  • Cause 658: The number of 30-second-level configuration table resources collected by Telemetry exceeded 95% of the upper limit supported by the forwarding engine.

    The configured number of instances collected by Telemetry exceeded the upper limit. Change the collection interval.

  • Cause 659: The number of 30-second-level configuration table resources collected by Telemetry exceeded the upper limit supported by the forwarding engine.

    The configured number of instances collected by Telemetry exceeded the upper limit. Change the collection interval.

  • Cause 660: The number of BGP Flowspec based on interface GIDs exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 661: The number of BGP Flowspec based on interface GIDs exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 662: The number of the applied BGP flowspec based on interface ACL exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 663: The number of the applied BGP flowspec based on interface ACL exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 664: The number of NHRP peer tables exceeds the forwarding engine specification.

    Check the NHRP peer configuration for the DSVPN service and determine whether the number of NHRP peers exceeds the specification.

  • Cause 665: The number of dynamic NHRP peer statistical entries exceeds the forwarding engine specification.

    Check the NHRP peer configuration for the DSVPN service and determine whether the number of NHRP peers exceeds the specification.

  • Cause 666: The number of dhcp snooping whitelist statistics exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 667: The number of dhcp snooping whitelist statistics exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 668: Resources in the TNL6_OTNLINF exceeded the upper limit supported by the forwarding engine.

    Check 6RD tunnel configurations and check whether the number of 6RD tunnel exceeds the upper limit of the TNL6_OTNLINFO table resources. If the number of 6RD tunnel exceeds the upper limit, delete some 6RD tunnels.

  • Cause 669: The number of ERPS NSE resource exceeded the specification of the forwarding engine resources.

    Please check the erps configuration.

  • Cause 670: The number of eap tbl reasource for user exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 671: The number of Service-class track BFD indexes exceeded the forwarding engine resource specification.

    1. Check if the service-class track BFD configuration exceeds the specification.

    • If the specification is exceeded, please go to Step 2.
    • If the specification is not exceeded, please go to Step 3.

    2. Reduce configured service-class track BFD.

    3. Please collect alarm information, log information, and configuration information, then contact Huawei technical support personnel.

  • Cause 672: The number of filter MAC exceeded the 90% of the specification of the forwarding engine resources.

    Please check the MAC filter configuration and determine whether the number of MAC filter exceeds the 90% of the specification.

  • Cause 673: The number of filter MAC exceeded the specification of the forwarding engine resources.

    Please check the MAC filter configuration and determine whether the number of MAC filter exceeds the specification.

  • Cause 703: No dual-device hot-backup forwarding table resource can be requested multicast.

    1. Run the display feicommon slot slot-id frame frm-pool use-info | include MC_HSB_STATUS command in the diagnostic view to check the values of ResMaxSize and UsedSize fields in the command output.

    • If the UsedSize value exceeds the ResMaxSize value, go to Step 2.
    • If the UsedSize value does not exceed the ResMaxSize value, go to Step 3.

    2. Delete unnecessary multicast hot backup configurations. 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 Huawei technical support personnel.

    4. End.

  • Cause 707: No Mre Stat resources 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 708: No Mre Stat resources 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 709: No MreExt table resource can be requested for IPv4 Layer 3 multicast.

    1. Check whether the number of MreExt entries for IPv4 multicast MoFRR and NG MVPN services exceeds the specification.

    • If yes, go to Step 2.
    • If no, go to Step 3.

    2. Delete unneeded IPv4 multicast MoFRR and NG MVPN configurations. 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 710: No MreExt table resource can be requested for IPv6 Layer 3 multicast.

    1. Check whether the number of MreExt entries for IPv6 multicast MoFRR and NG MVPN services exceeds the specification.

    • If yes, go to Step 2.
    • If no, go to Step 3.

    2. Delete unneeded IPv6 multicast MoFRR and NG MVPN configurations. 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 715: The number of the applied virtual user-queue resources exceeded the specifications supported by the forwarding engine of a board.

    Contact technical support engineers.

  • Cause 716: The number of the applied virtual user-group-queue resources exceeded the specifications supported by the forwarding engine of a board.

    Contact technical support engineers.

  • Cause 717: The number of the applied virtual sub-port-queue resources exceeded the specifications supported by the forwarding engine of a board.

    Contact technical support engineers.

  • Cause 721: No unicast SRv6 table resource can be requested for IPv6 Layer 3 unicast .

    1. Check whether the SRv6 BE configuration exceeds the specification.

    • If yes, go to Step 2.
    • If no, go to Step 3.

    2. Run the undo peer ipv6-address prefix-sid command to delete unnecessary SRv6 BE configurations.

    • If the alarm is cleared, go to Step 4.
    • If the alarm persists, go to Step 3.

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

    4. no further action is required.

  • Cause 722: No unicast DSVPN table resources can be requested for IPv4 Layer 3 unicast.

    1. Check whether the number of dynamic DSVPN tunnels exceeds the specification.

    • If yes, go to Step 2.
    • If no, go to Step 3.

    2. Run the undo network or undo tunnel shutdown command to delete unnecessary DSVPN dynamic tunnel configurations.

    • 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 technical support personnel.

    4. no further action is required.

  • Cause 725: The resource usage of ipv4 whitelist session-car has exceeded the forwarding resource specifications

    Contact technical support engineers.

  • Cause 726: The resource usage of ipv4 whitelist session-car has exceeded 90% of the forwarding resource specifications

    Contact technical support engineers.

  • Cause 727: The resource usage of ipv4 whitelist session-car statistics has exceeded the forwarding resource specifications

    Contact technical support engineers.

  • Cause 728: The resource usage of ipv4 whitelist session-car statistics has exceeded 90% of the forwarding resource specifications

    Contact technical support engineers.

  • Cause 729: The l2vpn qos nse table resources usage has exceeded 90% of the forwarding engine resources specification.

    Contact technical support engineers.

  • Cause 730: The l2vpn qos nse table resources exceeded the specifications of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 731: The MRE statistics table resources cannot be obtained for the IPv4 Layer 3 multicast source clone service.

    1. Check whether the number of IPv4 multicast groups configured exceeds the upper limit.

    • If the number of IPv4 multicast groups configured exceeds the upper limit, go to Step 2.
    • If the number of IPv4 multicast groups configured does not exceed the upper limit, go to Step 3.

    2. Delete unnecessary IPv4 multicast group configurations.

    • 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 733: The number of interface URPF statistics resources exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 734: The number of interface URPF statistics resources exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 735: The number of IP traffic statistics resources exceeds the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 737: The number of multicast leaves exceeds 4096.

    Reduce the multicast outbound interface configuration.

  • Cause 738: The resource usage of IPv6 whitelist session-car has exceeded the forwarding resource specifications.

    Contact technical support engineers.

  • Cause 739: The resource usage of IPv6 whitelist session-car has exceeded 90% of the forwarding resource specifications.

    Contact technical support engineers.

  • Cause 740: The resource usage of IPv6 whitelist session-car statistics has exceeded the forwarding resource specifications.

    Contact technical support engineers.

  • Cause 741: The resource usage of IPv6 whitelist session-car statistics has exceeded 90% of the forwarding resource specifications.

    Contact technical support engineers.

  • Cause 742: The resource usage of l2 whitelist session-car has exceeded the forwarding resource specifications.

    Contact technical support engineers.

  • Cause 743: The resource usage of l2 whitelist session-car has exceeded 90% of the forwarding resource specifications.

    Contact technical support engineers.

  • Cause 744: The resource usage of l2 whitelist session-car statistics has exceeded the forwarding resource specifications.

    Contact technical support engineers.

  • Cause 745: The resource usage of l2 whitelist session-car statistics has exceeded 90% of the forwarding resource specifications.

    Contact technical support engineers.

  • Cause 759: The number of the applied car resources of session users exceeded the specifications supported by the forwarding engine of a board.

    Contact technical support engineers.

  • Cause 760: The number of the applied car resources of family users exceeded the specifications supported by the forwarding engine of a board.

    Contact technical support engineers.

  • Cause 763: The number of the applied car statistics resources of session users exceeded the specifications supported by the forwarding engine of a board.

    Contact technical support engineers.

  • Cause 764: The number of the applied car statistics resources of family users exceeded the specifications supported by the forwarding engine of a board.

    Contact technical support engineers.

  • Cause 767: The number of MPLS-in-UDP address verification services exceeded the threshold supported by the forwarding engine.

    Contact technical support engineers.

  • Cause 768: The node where the BIER MVPN's outbound tunnel resides failed to apply for BIER VPN forwarding entries.

    1. Check whether the number of MVPNs connected to the BIER tunnel exceeds the upper limit.

    • If yes, go to step 2.
    • If no, go to step 3.

    2. Reduce the number of MVPNs connected to the BIER tunnel.

    • 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 769: The number of resources in the discoverflow table exceeded the specification of resources supported by the forwarding engine.

    Contact technical support engineers.

  • Cause 770: The number of resources in the esqm table exceeded the specification of resources supported by the forwarding engine.

    Contact technical support engineers.

  • Cause 773: The number of BIFT entries exceeded the upper limit allowed by the board.

    1. Check whether the number of tunnel neighbors exceeds the upper limit.

    • If yes, go to step 2.
    • If no, go to step 3.

    2. Reduce the number of tunnel neighbors.

    • 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 775: The number of statistics indexes for multicast egress exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 778: The number of CAR resources used to limit the rate of upstream traffic in a profile exceeds 95% of the total number of forwarding engine resources.

    Check whether the number of applied CAR resources reaches 95% of the specifications.

  • Cause 779: The number of CAR resources used to limit the rate of downstream traffic in a profile exceeds 95% of the total number of forwarding engine resources.

    Check whether the number of applied CAR resources reaches 95% of the specifications.

  • Cause 780: The number of inbound statistics resources for CAR in the QoS profile exceeded 95% of the forwarding engine's resource specification.

    Check whether the number of applied CAR statistics resources reaches 95% of the specifications.

  • Cause 781: The number of outbound statistics resources for CAR in the QoS profile exceeded 95% of the forwarding engine's resource specification.

    Check whether the number of applied CAR statistics resources reaches 95% of the specifications.

  • Cause 783: The number of the ACL indexes for nd vlan car exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 784: The number of the ACL indexes for nd vlan car exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 785: The number of the CAR indexes for nd vlan car exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 786: The number of the CAR indexes for nd vlan car exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 787: The number of the statistics indexes for nd vlan car exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 788: The number of the statistics indexes for nd vlan car exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 789: The number of L3VPN instances on the board exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 790: The number of IFIT exceeded 90% of the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 791: The number of IFIT resource usage has exceeded the specifications of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 800: The index resources of the 100 ms telemetry for CAR statistics are insufficient.

    Check whether the number of telemetry index resources exceeds the specification.

  • Cause 801: The number of 100 ms telemetry index resources for CAR statistics exceeds 95% of the specification supported by the forwarding engine of the board.

    Check whether the number of telemetry index resources approximates the specification.

  • Cause 802: The index resources of the 1s telemetry for CAR statistics are insufficient.

    Check whether the number of telemetry index resources exceeds the specification.

  • Cause 803: The number of 1s telemetry index resources for CAR statistics exceeds 95% of the specification supported by the forwarding engine of the board.

    Check whether the number of telemetry index resources approximates the specification.

  • Cause 804: The index resources of the 30s telemetry for CAR statistics are insufficient.

    Check whether the number of telemetry index resources exceeds the specification.

  • Cause 805: The number of 30s telemetry index resources for CAR statistics exceeds 95% of the specification supported by the forwarding engine of the board.

    Check whether the number of telemetry index resources approximates the specification.

  • Cause 806: The index resources of the 100 ms telemetry for ACL rule statistics are insufficient.

    Check whether the number of telemetry index resources exceeds the specification.

  • Cause 807: The number of 100 ms telemetry index resources for ACL rule statistics exceeds 95% of the specification supported by the forwarding engine of the board.

    Check whether the number of telemetry index resources approximates the specification.

  • Cause 808: The index resources of the 1s telemetry for ACL rule statistics are insufficient.

    Check whether the number of telemetry index resources exceeds the specification.

  • Cause 809: The number of 1s telemetry index resources for ACL rule statistics exceeds 95% of the specification supported by the forwarding engine of the board.

    Check whether the number of telemetry index resources approximates the specification.

  • Cause 810: The index resources of the 30s telemetry for ACL rule statistics are insufficient.

    Check whether the number of telemetry index resources exceeds the specification.

  • Cause 811: The number of 30s telemetry index resources for ACL rule statistics exceeds 95% of the specification supported by the forwarding engine of the board.

    Check whether the number of telemetry index resources approximates the specification.

  • Cause 812: The number of resource in the SRPOLICY statistics exceeded 95% of the maximum number of resource allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 813: The number of resources in the SRPOLICY statistics exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 814: The number of the CAR indexes for arpvlancar exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 815: The number of the CAR indexes for arpvlancar exceeded the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 831: The number of LocalArpv6 entries exceeds the specification of the forwarding engine.

    Check whether the number of local ND entries exceeds the LocalArpv6 specification.

  • Cause 836: The number of remote sid entries exceeds the specification of the forwarding engine.

    Contact technical support engineers.

  • Cause 838: The number of SCAN tables used to store traffic statistics collected through SRv6 TE Policy telemetry at an interval of 30s exceeds the upper threshold.

    Contact technical support engineers.

  • Cause 840: The number of SCAN tables used to store traffic statistics collected through SRv6 TE Policy telemetry at an interval of 1s exceeds the upper threshold.

    Contact technical support engineers.

  • Cause 842: The number of RE entries regarding the service that redirects public network traffic to SRv6 Policies reaches the upper limit.

    Contact technical support engineers.

  • Cause 844: The number of Segment list entries exceeds the upper threshold.

    Contact technical support engineers.

  • Cause 846: The number of statistical entries of SRv6 TE Policies exceeds the upper threshold.

    Contact technical support engineers.

  • Cause 848: The number of resources in the IPv6 VXLAN tunnel decapsulation table exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 849: The number of EMDI ACL Entry exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 850: The number of SRv6 SFC Layer 3 forwarding RE entries exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 852: The number of SRv6 SFC Layer 2 forwarding RE entries exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 853: The number of test instances for which dual-ended frame loss measurement with an interval set to 100 ms is enabled exceeded the forwarding engine resource specification.

    Contact Huawei technical support.

  • Cause 870: The number of inbound 8queue mode user-queue exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 871: The number of inbound 8queue-enhance mode user-queue exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 872: The number of outbound 4queue mode user-queue exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 873: The number of outbound 8queue mode user-queue exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 874: The number of outbound 8queue-enhance mode user-queue exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 907: The number of TM inbound 8queue mode user-queue exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 908: The number of TM inbound 8queue-enhance mode user-queue exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 909: The number of TM outbound 4queue mode user-queue exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 910: The number of TM outbound 8queue mode user-queue exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 911: The number of TM outbound 8queue-enhance mode user-queue exceeded the specification of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 920: The numbers of used CP IPv4 and IPv6 ACLs exceeded 90% of total forwarding resources.

    Contact technical support engineers.

  • Cause 921: The numbers of used CP IPv4 and IPv6 ACLs exceeded the upper limit of the forwarding resources.

    Contact technical support engineers.

  • Cause 922: The aib ext table resource usage has exceeded 95% of the forwarding engine specification.

    Contact technical support engineers.

  • Cause 923: The number of resources in the SRv6 Network Slice SliceOportinfo table exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 929: The node where the BIERv4/BIERv6 MVPN's outbound tunnel resides failed to apply for BIERv4/BIERv6 VPN forwarding entries.

    1. Check whether the number of VPNs connected to the BIERv4/BIERv6 tunnel exceeds the upper limit.

    • If yes, go to Step 2.
    • If no, go to Step 3.

    2. Reduce the number of multicast VPNs connected to the BIERv4/BIERv6 tunnel.

    • 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. The procedure ends.

  • Cause 930: The node where BIERv6 MVPN services enter a tunnel failed to apply for BIERv6 Incoming Label Map IPv6 (ILMv6) forwarding entries.

    1. Check whether the number of MVPNs connected to the BIERv6 tunnel exceeds the upper limit.

    • If yes, go to step 2.
    • If no, go to step 3.

    2. Reduce the number of MVPNs connected to the BIERv6 tunnel.

    • 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 934: The number of resources in the SRv6 Network Slice SegmentlistSliceMap table exceeded the maximum number of resources allowed by the forwarding engine.

    Contact technical support engineers.

  • Cause 935: The number of the applied DHCPv6 Snooping bind table exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 936: The number of DHCPv6 Snooping bind table exceeded the specifications of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 937: The number of the DHCPv6 Snooping statistics indexes resource for DHCPv6 Snooping exceeded 90% of the forwarding engine resource specification.

    Contact technical support engineers.

  • Cause 938: The number of the DHCPv6 Snooping statistics indexes resource for DHCPv6 Snooping exceeded the forwarding engine resources specification.

    Contact technical support engineers.

  • Cause 939: The number of the applied DHCPv6 Snooping statistics table exceeded 90% of the specification of the forwarding resources.

    Contact technical support engineers.

  • Cause 940: The number of DHCPv6 Snooping statistics table exceeded the specifications of the forwarding engine resources.

    Contact technical support engineers.

  • Cause 941: The number of CAR ACLs for upstream traffic exceeded the forwarding engine resource specification.

    Check whether the CAR configuration on the upstream interface that applies for ACL resources exceeds the specification.

  • Cause 949: The statistical resources for BIER IPv6 flow-based upstream statistics collection are insufficient.

    Contact technical support engineers.

  • Cause 950: The forwarding entry resources for BIER IPv6 flow-based upstream statistics collection are insufficient.

    Contact technical support engineers.

  • Cause 951: The number of color-sliceid mapping table resources exceeded the forwarding engine resource specifications.

    Contact technical support engineers.

  • Cause 968: The BGPFLOW REFLUENCE TCAM resources are insufficient.

    1. Check whether the number of BGPFLOW REFLUENCE services exceeds the specification.

    • If yes, go to Step 2.
    • If no, go to Step 3.

    2. Reduce the number of BGPFLOW REFLUENCE services.

    • 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 979: The usage of CAR statistics resources of the value-added service exceeds the forwarding engine specification of the board.

    Check whether the number of CAR statistical resources applied for value-added services reaches the specification.

  • Cause 980: The number of traffic-class-map entries exceeds the specification of the forwarding engine.

    Contact technical support engineers.

  • Cause 982: The CAR statistics resource usage of the upstream interface CAR exceeds 95% of the forwarding engine specification.

    Contact technical support engineers.

  • Cause 983: The CAR statistics resource usage of the downstream interface CAR exceeds 95% of the forwarding engine specification.

    Contact technical support engineers.

Parent Topic: FIB
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >