FIB/4/hwBoardFwdResThresholdExceed_active

Message

FIB/4/hwBoardFwdResThresholdExceed_active: The board forwarding engine resources exceeded the threshold. (EntityPhysicalIndex=[EntiyPhysicalindex], EntPhysicalIndex=[EntPhysicalindex], EntPhysicalName=[EntPhysicalName], Slot=[SlotStr], ReasonId=[ReasonId], ReasonDescription=[Reason])

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

Description

The board forwarding engine resources exceeded the threshold.

Parameters

Parameter Name Parameter Meaning

EntiyPhysicalindex

The index for this entry.

EntPhysicalindex

The index for this entry.

EntPhysicalName

The textual name of the entity.

SlotStr

The information for the slot.

ReasonId

The probable cause of trap.

Reason

The detailed cause of the trap.

Possible Causes

  • Cause 15: The percentage of ND indexes exceeded the upper threshold supported by the forwarding engine.
  • Cause 16: The percentage of tunnel indexes exceeded the upper threshold supported by the forwarding engine.
  • Cause 17: The percentage of BFD indexes exceeded the upper threshold supported by the forwarding engine.
  • Cause 18: The percentage of VPLS LearnIDs exceeded the upper threshold supported by the forwarding engine.
  • Cause 19: The percentage of VSI indexes exceeded the upper threshold supported by the forwarding engine.
  • Cause 20: The percentage of NS indexes exceeded the upper threshold supported by the forwarding engine.
  • Cause 21: The percentage of ring indexes exceeded the upper threshold supported by the forwarding engine.
  • Cause 99: The number of tokens on the board exceeds the threshold of the forwarding engine specification.
  • Cause 103: The percentage of AT indexes exceeded the upper threshold supported by the forwarding engine.
  • Cause 325: The number of resources in the IPv4 GRE tunnel decapsulation table exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 326: The number of resources in the IPv6 GRE tunnel decapsulation table exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 375: The number of TM pool-0 SQ resources usage has exceeded 90%.
  • Cause 376: The number of TM pool-1 SQ resources usage has exceeded 90%.
  • Cause 377: The number of slot pool-0 SQ resources usage has exceeded 90%.
  • Cause 378: The number of slot pool-1 SQ resources usage has exceeded 90%.
  • Cause 379: The number of TM pool-0 GQ resources usage has exceeded 90%.
  • Cause 380: The number of TM pool-1 GQ resources usage has exceeded 90%.
  • Cause 399: The number of resources in the IPv4 VXLAN tunnel decapsulation table exceeded 90% of the maximum number of resources allowed by the forwarding engine.
  • Cause 410: The number of VNI*peer resources exceeded 90% of the maximum number of resources allowed by the forwarding engine.
  • Cause 577: The number of MAC accounting statistics entries exceeds 90% of the specification of the forwarding engine.
  • Cause 608: The number of resources in the 4over6 tunnel decapsulation table exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 609: The number of resources in the IPv6 address table exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 664: The number of NHRP peer tables exceeds 95% of the forwarding engine specification.
  • Cause 666: The number of dynamic NHRP peer statistical entries exceeds 95% of the forwarding engine specification.
  • Cause 668: The number of used resources in the TNL6_OTNLINFO table exceeded 95% of the upper limit supported by the forwarding engine.
  • Cause 700: The number of dual-device hot-backup state indexes for multicast exceeded 95% of the forwarding engine resource specification.
  • Cause 711: IPv4 Layer 3 multicast Mre Stat resources useage exceeded 95% of the specification of the forwarding resources.
  • Cause 712: IPv6 Layer 3 multicast Mre Stat resources useage exceeded 95% of the specification of the forwarding resources.
  • Cause 713: The number of IPv4 multicast MreExt table exceeded 95% of the forwarding engine resources.
  • Cause 714: The number of IPv6 multicast MreExt table exceeded 95% of the forwarding engine resources.
  • Cause 718: The number of the applied virtual user-queue resources exceeded 90% of the specifications supported by the forwarding engine of a board.
  • Cause 719: The number of the applied virtual user-group-queue resources exceeded 90% of the specifications supported by the forwarding engine of a board.
  • Cause 720: The number of the applied virtual sub-port-queue resources exceeded 90% of the specifications supported by the forwarding engine of a board.
  • Cause 723: The number of used IPv6 Layer 3 unicast SRv6 table exceeds 95% of the forwarding engine of the board.
  • Cause 724: The number of used IPv4 Layer 3 unicast DSVPN table resources exceeds 95% of the forwarding engine specification of an interface board.
  • Cause 732: The number of MRE statistics table resources for the IPv4 Layer 3 multicast source clone service exceeds 95% of the upper limit.
  • Cause 733: The number of IP traffic statistics resources exceeds 95% of the specification of the forwarding engine resources.
  • Cause 736: The number of multicast leaf nodes exceeds 95% of the specification of the forwarding resources.
  • Cause 771: The number of BIER VPN forwarding tables in the system exceeded 95% of the forwarding engine resource specification.
  • Cause 774: The number of BIFT entries exceeded 95% of the upper limit allowed by the board.
  • Cause 776: The number of statistics indexes for multicast egress exceeded 95% of the forwarding engine resource specification.
  • Cause 777: The number of L3VPN instances on the board exceeded 95% of the forwarding engine resource specification.
  • Cause 780: The number of MPLS-in-UDP address verification services exceeded 95% of the threshold supported by the forwarding engine.
  • Cause 781: The number of resources in the discoverflow table exceeded 90% of the maximum number of resources allowed by the forwarding engine.
  • Cause 782: The number of resources in the esqm table exceeded 90% of the maximum number of resources allowed by the forwarding engine.
  • Cause 832: The number of LocalArpv6 entries exceeds 95% of the forwarding engine specification.
  • Cause 835: The number of local SID tables for SRv6 tunnels exceeded 95% of the forwarding engine specification.
  • Cause 837: The number of remote sid entries exceeds 95% of the forwarding engine specification.
  • Cause 839: The number of SCAN tables used to store traffic statistics collected through SRv6 TE Policy telemetry at an interval of 30s exceeds 95% of the upper threshold.
  • Cause 841: The number of SCAN tables used to store traffic statistics collected through SRv6 TE Policy telemetry at an interval of 1s exceeds 95% of the upper threshold.
  • Cause 843: The number of RE entries regarding the service that redirects public network traffic to SRv6 Policies exceeds 95% of the maximum number of entries supported.
  • Cause 845: The number of Segment list entries exceeds 95% of the upper threshold.
  • Cause 847: The number of statistical entries of SRv6 TE Policies exceeds 95% of the upper threshold.
  • Cause 849: The number of resources in the IPv6 VXLAN tunnel decapsulation table exceeded 95% of the maximum number of resources allowed by the forwarding engine.
  • Cause 850: The number of EMDI ACL Entry exceeded 90% of the forwarding engine resource specification.
  • Cause 851: The number of SRv6 SFC Layer 3 forwarding RE entries exceeds 95% of the upper threshold.
  • Cause 853: The number of SRv6 SFC Layer 2 forwarding RE entries exceeds 95% of the upper threshold.
  • Cause 860: The number of slot inbound 8queue mode user-queue resources usage has exceeded 90%.
  • Cause 861: The number of slot inbound 8queue-enhance mode user-queue resources usage has exceeded 90%.
  • Cause 862: The number of TM inbound 8queue mode user-queue resources usage has exceeded 90%.
  • Cause 863: The number of TM inbound 8queue-enhance mode user-queue resources usage has exceeded 90%.
  • Cause 864: The number of slot outbound 4queue mode user-queue resources usage has exceeded 90%.
  • Cause 865: The number of slot outbound 8queue mode user-queue resources usage has exceeded 90%.
  • Cause 866: The number of slot outbound 8queue-enhance mode user-queue resources usage has exceeded 90%.
  • Cause 867: The number of TM outbound 4queue mode user-queue resources usage has exceeded 90%.
  • Cause 868: The number of TM outbound 8queue mode user-queue resources usage has exceeded 90%.
  • Cause 869: The number of TM outbound 8queue-enhance mode user-queue resources usage has exceeded 90%.
  • Cause 924: The number of resources in the SRv6 Network Slice SliceOportinfo table exceeded 95% of the upper threshold.
  • Cause 931: The number of BIERv4/BIERv6 VPN forwarding tables in the system exceeded 95% of the forwarding engine resource specification.
  • Cause 932: The number of BIERv6 Incoming Label Map IPv6 (ILMv6) forwarding tables in the system exceeded 95% of the forwarding engine resource specification.
  • Cause 933: The number of TM shared GQ Resource usage has exceeded 90%.
  • Cause 935: The number of resources in the SRv6 Network Slice SegmentlistSliceMap table exceeded 95% of the upper threshold.
  • Cause 952: The number of color-sliceid mapping table resources exceeded 95% of the forwarding engine resource specifications.
  • Cause 981: The number of traffic-class-map entries exceeds 95% of the specification of the forwarding engine.

Procedure

  • Cause 15: The percentage of ND indexes exceeded the upper threshold supported by the forwarding engine.

    Please contact technical support personnel.

  • Cause 16: The percentage of tunnel indexes exceeded the upper threshold supported by the forwarding engine.

    Please contact technical support personnel.

  • Cause 17: The percentage of BFD indexes exceeded the upper threshold supported by the forwarding engine.

    Please contact technical support personnel.

  • Cause 18: The percentage of VPLS LearnIDs exceeded the upper threshold supported by the forwarding engine.

    Please contact technical support personnel.

  • Cause 19: The percentage of VSI indexes exceeded the upper threshold supported by the forwarding engine.

    Please contact technical support personnel.

  • Cause 20: The percentage of NS indexes exceeded the upper threshold supported by the forwarding engine.

    Please contact technical support personnel.

  • Cause 21: The percentage of ring indexes exceeded the upper threshold supported by the forwarding engine.

    Please contact technical support personnel.

  • Cause 99: The number of tokens on the board exceeds the threshold of the forwarding engine specification.

    Please contact technical support personnel.

  • Cause 103: The percentage of AT indexes exceeded the upper threshold supported by the forwarding engine.

    Please contact technical support personnel.

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

    Please contact technical support personnel.

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

    Please contact technical support personnel.

  • Cause 375: The number of TM pool-0 SQ resources usage has exceeded 90%.

    Please contact technical support personnel.

  • Cause 376: The number of TM pool-1 SQ resources usage has exceeded 90%.

    Please contact technical support personnel.

  • Cause 377: The number of slot pool-0 SQ resources usage has exceeded 90%.

    Please contact technical support personnel.

  • Cause 378: The number of slot pool-1 SQ resources usage has exceeded 90%.

    Please contact technical support personnel.

  • Cause 379: The number of TM pool-0 GQ resources usage has exceeded 90%.

    Please contact technical support personnel.

  • Cause 380: The number of TM pool-1 GQ resources usage has exceeded 90%.

    Please contact technical support personnel.

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

    Please contact technical support personnel.

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

    Please contact technical support personnel.

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

    Please check whether the number of mac accouting statistics tables for mac accouting exceeded 90% of the forwarding engine specification.

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

    Please contact technical support personnel.

  • Cause 609: The number of resources in the IPv6 address table exceeded 95% of the maximum number of resources allowed by the forwarding engine.

    Please contact technical support personnel.

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

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

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

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

  • Cause 668: The number of used resources in the TNL6_OTNLINFO table exceeded 95% of 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.

  • Cause 700: The number of dual-device hot-backup state indexes for multicast exceeded 95% of the forwarding engine resource specification.

    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 95% of the ResMaxSize value, go to Step 2.
    • If the UsedSize value does not exceed 95% of 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 711: IPv4 Layer 3 multicast Mre Stat resources useage exceeded 95% of the specification of the forwarding resources.

    This alarm has no impact on the system.

  • Cause 712: IPv6 Layer 3 multicast Mre Stat resources useage exceeded 95% of the specification of the forwarding resources.

    This alarm has no impact on the system.

  • Cause 713: The number of IPv4 multicast MreExt table exceeded 95% of the forwarding engine resources.

    The number of IPv4 multicast MreExt table arrive 95% of the service spec. The service may not be affected.

  • Cause 714: The number of IPv6 multicast MreExt table exceeded 95% of the forwarding engine resources.

    The number of IPv6 multicast MreExt table arrive 95% of the service spec. The service may not be affected.

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

    Please contact technical support personnel.

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

    Please contact technical support personnel.

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

    Please contact technical support personnel.

  • Cause 723: The number of used IPv6 Layer 3 unicast SRv6 table exceeds 95% of the forwarding engine of the board.

    This alarm has no impact on the system.

  • Cause 724: The number of used IPv4 Layer 3 unicast DSVPN table resources exceeds 95% of the forwarding engine specification of an interface board.

    This alarm has no impact on the system.

  • Cause 732: The number of MRE statistics table resources for the IPv4 Layer 3 multicast source clone service exceeds 95% of the upper limit.

    This alarm has no impact on the system.

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

    Please contact technical support personnel.

  • Cause 736: The number of multicast leaf nodes exceeds 95% of the specification of the forwarding resources.

    Reduce the multicast outbound interface configuration.

  • Cause 771: The number of BIER VPN forwarding tables in the system exceeded 95% of the forwarding engine resource specification.

    This alarm has no impact on the system.

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

    This alarm has no impact on the system.

  • Cause 776: The number of statistics indexes for multicast egress exceeded 95% of the forwarding engine resource specification.

    This alarm has no impact on the system.

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

    This alarm has no impact on the system.

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

    This alarm has no impact on the system.

  • Cause 781: The number of resources in the discoverflow table exceeded 90% of the maximum number of resources allowed by the forwarding engine.

    Please contact technical support personnel.

  • Cause 782: The number of resources in the esqm table exceeded 90% of the maximum number of resources allowed by the forwarding engine.

    This alarm has no impact on the system.

  • Cause 832: The number of LocalArpv6 entries exceeds 95% of the forwarding engine specification.

    Check whether the number of resources in the LocalArpv6 table exceeds 95% of the forwarding engine specification.

  • Cause 835: The number of local SID tables for SRv6 tunnels exceeded 95% of the forwarding engine specification.

    Please check whether the number of local SID tables for SRv6 tunnels exceeded 95% of the forwarding engine specification.

  • Cause 837: The number of remote sid entries exceeds 95% of the forwarding engine specification.

    This alarm has no impact on the system.

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

    This alarm has no impact on the system.

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

    This alarm has no impact on the system.

  • Cause 843: The number of RE entries regarding the service that redirects public network traffic to SRv6 Policies exceeds 95% of the maximum number of entries supported.

    This alarm has no impact on the system.

  • Cause 845: The number of Segment list entries exceeds 95% of the upper threshold.

    This alarm has no impact on the system.

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

    This alarm has no impact on the system.

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

    Please contact technical support personnel.

  • Cause 850: The number of EMDI ACL Entry exceeded 90% of the forwarding engine resource specification.

    This alarm has no impact on the system.

  • Cause 851: The number of SRv6 SFC Layer 3 forwarding RE entries exceeds 95% of the upper threshold.

    Please contact technical support personnel.

  • Cause 853: The number of SRv6 SFC Layer 2 forwarding RE entries exceeds 95% of the upper threshold.

    Please contact technical support personnel.

  • Cause 860: The number of slot inbound 8queue mode user-queue resources usage has exceeded 90%.

    This alarm has no impact on the system.

  • Cause 861: The number of slot inbound 8queue-enhance mode user-queue resources usage has exceeded 90%.

    This alarm has no impact on the system.

  • Cause 862: The number of TM inbound 8queue mode user-queue resources usage has exceeded 90%.

    This alarm has no impact on the system.

  • Cause 863: The number of TM inbound 8queue-enhance mode user-queue resources usage has exceeded 90%.

    This alarm has no impact on the system.

  • Cause 864: The number of slot outbound 4queue mode user-queue resources usage has exceeded 90%.

    This alarm has no impact on the system.

  • Cause 865: The number of slot outbound 8queue mode user-queue resources usage has exceeded 90%.

    This alarm has no impact on the system.

  • Cause 866: The number of slot outbound 8queue-enhance mode user-queue resources usage has exceeded 90%.

    This alarm has no impact on the system.

  • Cause 867: The number of TM outbound 4queue mode user-queue resources usage has exceeded 90%.

    This alarm has no impact on the system.

  • Cause 868: The number of TM outbound 8queue mode user-queue resources usage has exceeded 90%.

    This alarm has no impact on the system.

  • Cause 869: The number of TM outbound 8queue-enhance mode user-queue resources usage has exceeded 90%.

    This alarm has no impact on the system.

  • Cause 924: The number of resources in the SRv6 Network Slice SliceOportinfo table exceeded 95% of the upper threshold.

    Please contact technical support personnel.

  • Cause 931: The number of BIERv4/BIERv6 VPN forwarding tables in the system exceeded 95% of the forwarding engine resource specification.

    This alarm has no impact on the system.

  • Cause 932: The number of BIERv6 Incoming Label Map IPv6 (ILMv6) forwarding tables in the system exceeded 95% of the forwarding engine resource specification.

    This alarm has no impact on the system.

  • Cause 933: The number of TM shared GQ Resource usage has exceeded 90%.

    Please contact technical support personnel.

  • Cause 935: The number of resources in the SRv6 Network Slice SegmentlistSliceMap table exceeded 95% of the upper threshold.

    This alarm has no impact on the system.

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

    Please contact technical support personnel.

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

    Please contact technical support personnel.

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