FIB_1.3.6.1.4.1.2011.5.25.227.2.1.15 hwBoardFwdResThresholdExceed

Trap Buffer Description

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

The board forwarding engine resources exceeded the threshold.

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

Trap Attributes

Trap Attribute Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

hwBoardFwdResThresholdExceed

Trap OID

1.3.6.1.4.1.2011.5.25.227.2.1.15

MIB

HUAWEI-FWD-RES-TRAP-MIB

Alarm ID

0x00F10034

Alarm Name

hwBoardFwdResThresholdExceed

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

FIB_1.3.6.1.4.1.2011.5.25.227.2.1.16 hwBoardFwdResThresholdExceedResume

Trap Buffer Parameters

Parameter Description

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.

VB Parameters

VB OID VB Name VB Index

1.3.6.1.4.1.2011.5.25.227.1.1

hwEntPhysicalindex

-

1.3.6.1.2.1.47.1.1.1.1.7

entPhysicalName

entPhysicalIndex

1.3.6.1.4.1.2011.5.25.227.1.2

hwFwdResLackSlotStr

-

1.3.6.1.4.1.2011.5.25.227.1.3

hwFwdResLackReasonId

-

Impact on the System

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

    The percentages of configured services have exceeded the upper thresholds, but service functions are not affected. If services continue to be configured and their quantities reach the maximum specification, new service configuration may fail to take effect.

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

    The percentages of configured services have exceeded the upper thresholds, but service functions are not affected. If services continue to be configured and their quantities reach the maximum specification, new service configuration may fail to take effect.

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

    The percentages of configured services have exceeded the upper thresholds, but service functions are not affected. If services continue to be configured and their quantities reach the maximum specification, new service configuration may fail to take effect.

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

    The percentages of configured services have exceeded the upper thresholds, but service functions are not affected. If services continue to be configured and their quantities reach the maximum specification, new service configuration may fail to take effect.

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

    The percentages of configured services have exceeded the upper thresholds, but service functions are not affected. If services continue to be configured and their quantities reach the maximum specification, new service configuration may fail to take effect.

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

    The percentages of configured services have exceeded the upper thresholds, but service functions are not affected. If services continue to be configured and their quantities reach the maximum specification, new service configuration may fail to take effect.

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

    The percentages of configured services have exceeded the upper thresholds, but service functions are not affected. If services continue to be configured and their quantities reach the maximum specification, new service configuration may fail to take effect.

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

    The number of tokens on the board has exceeded the threshold of the forwarding engine specification. If new services are deployed, the services will be affected.

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

    The percentages of configured services have exceeded the upper thresholds, but service functions are not affected. If services continue to be configured and their quantities reach the maximum specification, new service configuration may fail to take effect.

  • 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.

    Services are not affected. However, if more IPv4 GRE services are configured and the number of resources in the IPv4 GRE tunnel decapsulation table reaches the maximum number allowed by the forwarding engine, excess IPv4 GRE services will fail to take effect.

  • 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.

    Services are not affected. However, if more IPv6 GRE services are configured and the number of resources in the IPv6 GRE tunnel decapsulation table reaches the maximum number allowed by the forwarding engine, excess IPv6 GRE services will fail to take effect.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    Services may not be interrupted. But if continue to use the resources, certain services may be interrupted.

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

    Services may not be interrupted. But if continue to use the resources, certain services may be interrupted.

  • 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.

    Services are not affected. However, if more IPv4 VXLAN services are configured and the number of resources in the IPv4 VXLAN tunnel decapsulation table reaches the maximum number allowed by the forwarding engine, excess IPv4 VXLAN services will fail to take effect.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    The number of MAC accounting statistics entries has exceeded 90% of the service specification. Services are not affected currently. However, if the number reaches the specification as statistics entries continue to be generated, new statistics entries become invalid.

  • 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.

    Services are not affected. However, if more 4over6 services are configured and the number of resources in the 4over6 tunnel decapsulation table reaches the maximum number allowed by the forwarding engine, excess 4over6 services will fail to take effect.

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

    Services are not affected. However, if more 4over6 services are configured and the number of resources in the 4over6 tunnel decapsulation table reaches the maximum number allowed by the forwarding engine, excess 4over6 services will fail to take effect.

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

    The configuration of NHRP peers is not affected currently. However, if DSVPN services continue to be configured until the number reaches the forwarding engine specification, the newly configured DSVPN services do not take effect.

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

    The number of DSVPN statistical entries has exceeded 95% of the service specification. The DSVPN function is not affected currently. However, if the number of services reaches the specification as statistical entries continue to be added, the new statistical entries become invalid.

  • Cause 668: The number of used resources in the TNL6_OTNLINFO table exceeded 95% of the upper limit supported by the forwarding engine.

    The number of configured 6RD tunnels exceeded 95% of the upper limit supported in the testing. If more 6RD tunnels are configured and outnumber the upper limit, new 6RD tunnels fail to transmit traffic.

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

    Services are not affected temporarily. However, if more dual-device hot-backup state indexes for multicast are configured and the maximum number of indexes is reached, new service configurations fail to take effect.

  • 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. However, the hardware resource usage may reach 100% if the resources continue to be consumed.

  • 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. However, the hardware resource usage may reach 100% if the resources continue to be consumed.

  • 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. But if continue to add the service and arrive 100% of the service spec, certain configuration may not becom effective.

  • 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. But if continue to add the service and arrive 100% of the service spec, certain configuration may not becom effective.

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

    Services are not affected for now. However, if the upper limit is reached after your continual configuration, new services will not take effect.

  • 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.

    Services are not affected for now. However, if the upper limit is reached after your continual configuration, new services will not take effect.

  • 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.

    Services are not affected for now. However, if the upper limit is reached after your continual configuration, new services will not take effect.

  • 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. However, the hardware resource usage may reach 100% if the resources continue to be consumed.

  • 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. However, the hardware resource usage may reach 100% if the resources continue to be consumed.

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

    The number of tokens on the board has exceeded the threshold of the forwarding engine specification.

    If new services are deployed, the services will be affected.

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

    The number of tokens on the board has exceeded the threshold of the forwarding engine specification.

    If new services are deployed, the services will be affected.

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

    The number of configured multicast leaf services has exceeded 95% of the system specification, which does not affect service use. If the number of configured multicast leaf services exceeds the system specification, the multicast service configuration fails.

  • 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. However, the hardware resource usage may reach 100% if the resources continue to be consumed.

  • 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. However, the hardware resource usage may reach 100% if the resources continue to be consumed.

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

    The existing multicast egress statistics are not affected. However, if the upper limit is reached after your continual configuration, new multicast egress statistics will not take effect.

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

    Services are not affected. However, if new L3VPN instances continue to be configured and the number reaches the forwarding engine resource specification on the board, binding these new L3VPN instances does not take effect.

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

    No impact is posed. If MPLS-in-UDP address verification services continue to be configured and the number of MPLS-in-UDP address verification services reaches the upper limit, subsequent configurations do not take effect.

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

    Services are not affected. However, if more flow-recognition services are configured and the number of resources in the discoverflow table reaches the maximum number allowed by the forwarding engine, excess flow-recognition services will fail to take effect.

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

    Services are not affected for now. However, if the upper limit is reached after your continual configuration, new services will not take effect.

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

    Currently, no impact exists. However, if the specification is reached, the fast reply function of the newly configured local ND entries does not take effect.

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

    The use of an SRv6 tunnel is not affected currently. However, if SRv6 services continue to be configured until the number reaches the forwarding engine specification, the newly configured SRv6 services do not take effect.

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

    Currently, services are not affected. However, if the configuration reaches the maximum specification, the newly configured protection service on the SRv6 VPN egress node does not take effect.

  • 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 problem does not affect services temporarily. However, if more SRv6 TE Policy telemetry-based sampling tasks whose sampling interval is greater than or equal to 30s are configured until the number of SCAN tables reaches the upper threshold, the newly configured sampling tasks do not take effect.

  • 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 problem does not affect services temporarily. However, if more SRv6 TE Policy telemetry-based sampling tasks whose sampling interval is greater than or equal to 1s are configured until the number of SCAN tables reaches the upper threshold, the newly configured sampling tasks do not take effect.

  • 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.

    The number of configured services that redirect public network traffic to SRv6 Policies has exceeded 95% of the upper limit, which does not affect functions. However, if you continue to configure such services so that the upper limit is reached, the newly configured service does not take effect.

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

    This alarm does not affect services temporarily. However, if new SRv6 TE Policies or TI-LFA paths are configured so that the upper threshold for the number of Segment list entries is reached, the newly configured SRv6 TE Policies or TI-LFA paths fail to take effect.

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

    This alarm does not affect services temporarily. If SRv6 TE Policies continue to be configured and statistics collection is enabled, statistics collection fails for excess statistical entries of SRv6 TE Policies.

  • 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.

    Services are not affected. However, if more IPv6 VXLAN services are configured and the number of resources in the IPv6 VXLAN tunnel decapsulation table reaches the maximum number allowed by the forwarding engine, excess IPv6 VXLAN services will fail to take effect.

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

    Services are not affected for now. However, if the upper limit is reached after your continual configuration, new services will not take effect.

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

    Currently, this does not affect services. If more SRv6 SFC Layer 3 services are configured and the upper threshold is reached, the newly configured SRv6 SFC Layer 3 services do not take effect.

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

    Currently, this does not affect services. If more SRv6 SFC Layer 2 services are configured and the upper threshold is reached, the newly configured SRv6 SFC Layer 2 services do not take effect.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    Services may not be interrupted.But if continue to use the resources, certain services may be interrupted.

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

    Currently, services are not affected. However, if the configuration reaches the maximum specification, the newly configured SRv6 Network Slice services does not take effect.

  • 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. However, the hardware resource usage may reach 100% if the resources continue to be consumed.

  • 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. However, the hardware resource usage may reach 100% if the resources continue to be consumed.

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

    If the shared GQ resource usage exceedes 90%, services, temporarily, may not be interrupted. But if continue to use the resources, certain services may be interrupted because of the over configuration.

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

    Currently, services are not affected. However, if the configuration reaches the maximum specification, the newly configured SRv6 Network Slice services does not take effect.

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

    Currently, the mapping between the color and slice ID is not affected. If the mapping between the color and slice ID continues to be configured and the number of configured mappings reaches the upper limit, the newly configured mapping between the color and slice ID does not take effect.

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

    Currently, services are not affected. If you continue to configure the mapping between service classes and SRv6 TE Flow Groups until the number of services reaches the upper limit, the newly configured mapping between service classes and SRv6 TE Flow Groups does not take effect.

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.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >