No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

CloudEngine 12800 and 12800E V200R005C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
FEI_1.3.6.1.4.1.2011.5.25.227.2.1.18 hwBoardResThresholdExceed

FEI_1.3.6.1.4.1.2011.5.25.227.2.1.18 hwBoardResThresholdExceed

Description

The number of forwarding resources reaches the alarm threshold. (Slot=[hwFwdResLackSlotStr], Threshold=[hwFwdResThreshold]%, Reason=[hwFwdResLackReasonId], Description:[hwReasonDescription])

The remaining forwarding resources on the device are used up. The usage of forwarding resources exceeds the alarm threshold.

Attribute

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwBoardResThresholdExceed

Trap OID

1.3.6.1.4.1.2011.5.25.227.2.1.18

Alarm ID

0x095e2022

Alarm Type

processingErrorAlarm

Raise or Clear

Raise

Match trap

FEI_1.3.6.1.4.1.2011.5.25.227.2.1.19 hwBoardResThresholdExceedResume

Parameters

Parameter Meaning

hwFwdResLackSlotStr

Specifies a slot ID.

hwFwdResThreshold

Indicates the alarm threshold of forwarding resources.

hwFwdResLackReasonId

Indicates the ID of alarm cause.

hwReasonDescription

Indicates the description of alarm cause.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.227.1.2

hwFwdResLackSlotStr

N/A

1.3.6.1.4.1.2011.5.25.227.1.4

hwFwdResThreshold

N/A

1.3.6.1.4.1.2011.5.25.227.1.3

hwFwdResLackReasonId

N/A

1.3.6.1.4.1.2011.5.25.227.1.8

hwReasonDescription

N/A

Impact on the System

2: Some IPv4 FIB entries cannot be delivered. As a result, some IPv4 service traffic may be interrupted or a forwarding error may occur.

3: Some IPv6 unicast entries cannot be delivered. As a result, some IPv6 service traffic may be interrupted or a forwarding error may occur.

5: Some ND entries cannot be delivered. As a result, some IPv6 service traffic may be interrupted.

8: Some L2VPN connections will be unavailable.

10: The ACL entries of the new BFD sessions cannot be delivered. As a result, the new BFD sessions may flap.

11: The multicast service is unavailable.

12: The multicast service is unavailable.

13: Some MPLS and VPLS service traffic may be interrupted.

16: Some service traffic using tunnels is interrupted.

23: The multicast service is unavailable.

29: The service is unavailable.
NOTE:
When ECMP resources are insufficient on CE12800E series switches that have the ED-E/EG-E/EGA-E series cards installed, only a single next hop in the new ECMP load balancing forwarding group is used for packet forwarding. To check the specific forwarding path, run the display ip fib command in any view.

30: The service is unavailable.

31: The service is unavailable.

32: The service is unavailable.

55: The service is unavailable.

56: The service is unavailable.

57: The service is unavailable.

58: The service is unavailable.

59: The service is unavailable.

60: Some TRILL service traffic may be interrupted.

61: Some functions may be unavailable.

62: The service is unavailable.

63: The service is unavailable.

64: The service is unavailable.

65: The service is unavailable.

66: The service is unavailable.

67: The service is unavailable.

68: The service is unavailable.

69: The service is unavailable.

83: The service is unavailable.

170: The alarm does not affect services; however, if the LEM resource usage still increases, the resource usage may reach 100%. If new Layer 2 and Layer 3 services are configured in this case, the services will be unavailable.

171: The alarm does not affect services; however, if the MAC address resource usage still increases, the resource usage may reach 100%. If new Layer 2 services are configured in this case, the services will be unavailable.

172: The service is unavailable.

173: The service is unavailable.

174: The service is unavailable.

175: Some TRILL service traffic may be interrupted.

195: The forwarding service traffic using tunnel encapsulation is interrupted, and the GRE, 6over4, and 6to4 services are affected.

275: The FRR fast update and TE tunnel hot standby services may be unavailable.

276: The VPN traffic may fail to be forwarded.

277: The service is unavailable.

278: The service is unavailable.

327: The TRILL multicast service is unavailable.

350: Certain host routes cannot be delivered, resulting in interruption of some ARP or ND services or forwarding errors.

351: Certain network segment routes cannot be delivered, resulting in interruption of some IPv4 or IPv6 services or forwarding errors.

391: The service is unavailable.

392: The service is unavailable.

408: Certain VXLAN and MPLS may be unavailable.

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

556: The service is unavailable.

570: The service is unavailable.

577: The service is unavailable.

578: The service is unavailable.

581: The service is unavailable.

582: The service is unavailable.

585: Memory resources are insufficient and the multicast service may not take effect.

613: Certain L3VPN connections may be unavailable.

614: Memory resources are insufficient and the IPv4 FIBs service may not take effect.

615: Memory resources are insufficient and the IPv6 FIBs service may not take effect.

616: Memory resources are insufficient and the ARP service may not take effect.

617: Memory resources are insufficient and the ND service may not take effect.

Possible Causes

2: The number of IPv4 FIB entries exceeds the specifications of the forwarding engine, or hash conflict occurred during delivery of IPv4 FIBs entries to the chip.

3: The number of IPv6 unicast entries exceeds the specifications of the forwarding engine, or hash conflict occurred during delivery of IPv6 unicast entries to the chip.

5: The number of IPv6 ND entries exceeds the specifications of the forwarding engine.

8: The number of configured L2VPN connections exceeds the specifications of the forwarding engine.

10: The number of ACL entries that the BFD has applied for exceeds the specification of the forwarding engine.

11: The number of multicast chip entries exceeded the specification of the resources, or a hash conflict occurred during delivery of multicast entries to the chip.

12: The multicast LPU forwarding table resources are overloaded.

13: The number of board space tokens exceeds the specifications of the forwarding engine.

16: The number of tunnel indexes exceeds the specifications of the forwarding engine.

19: Broadcast domain resources are limited, and so applying for resources fails.

23: Multicast outbound interface resources are overloaded.

29: Used ECMP resources on the LPU exceed the specifications of the forwarding engine.

30: Used Layer 3 interface entry resources on the LPU exceed the specifications of the forwarding engine.

31: Used next hop resources on the LPU exceed the specifications of the forwarding engine.

32: The number of used tunnel decapsulation table resources on an LPU exceeds the specifications of the forwarding engine.

55: Link-layer encapsulation entry resources are overloaded.

56: Tunnel encapsulation entry resources are overloaded.

57: Accurate matching entry resources are overloaded.

58: Fail to apply layer2 forwarding resources because of limitation of logical interfaces.

59: Multicast MAC index resources are overloaded.

60: Virtual port entry resources are overloaded.

61: ACL rule resources are insufficient.

62: ACL group resources are insufficient.

63: Meter resources are overloaded.

64: Counter resources are overloaded.

65: Outbound ACL rule resources are insufficient.

66: Outbound ACL group resources are insufficient.

67: Outbound meter resources are overloaded.

68: Outbound counter resources are overloaded.

69: Multicast IP index resources are overloaded.

83: Multicast IP forwarding entry resources are overloaded.

170: LEM resources exceed the alarm threshold.

171: L2Entry resources exceed the alarm threshold.

172: Multicast MAC forwarding entry resources are overloaded.

173: Snoop resources are insufficient.

174: ARP resources are overloaded.

175: The number of TRILL routes exceeds the specifications of the forwarding engine.

195: Used tunnel decapsulation entry resources exceed the specifications of the forwarding engine, or hash conflict occurred during delivery of host routes entries to the chip.

277: VLAN change table resources are overloaded.

275: Protection group resources are overloaded.

276: Forwarding VRF resources are overloaded.

278: Downlink VLAN change table resources are overloaded.

327: TRILL multicast outbound interface resources are overloaded.

350: The number of host routes exceeded the specification of forwarding engine resources, or hash conflict occurred during delivery of host routes entries to the chip.

351: The number of network segment routes exceeded the specification of forwarding engine resources, or hash conflict occurred during of network segment routes entries to the chip.

391: The number of GLEM exceeded the specification of the forwarding engine resources.

392: The number of Local Encapsulation Database exceeded the specification of the forwarding engine resources.

408: The number of next-hop resources used by the tunnel exceeded the maximum number supported by the forwarding engine.

549: The overlay next hop resource usage exceeded the specification of the forwarding engine resource.

556: The number of VLAN Encapsulation database exceeded the maximum number supported by the forwarding engine.

570: IPv6 routes with masks greater than 64 bits and less than 128 bits are insufficient.

577: The number of SMAC resource usage exceeded the specification of the forwarding engine resources.

578: The number of layer2 forwarding database exceeded the specification of the forwarding engine resources.

581: The number of ICIB_PP exceeded the specification of the forwarding engine resources.

582: The number of ICIB exceeded the specification of the forwarding engine resources.

585: Memory resources are insufficient.

613: The number of vclabel encapsulation database entries exceeded the maximum number of forwarding engine resources.

614: Memory resources are insufficient.

615: Memory resources are insufficient.

616: Memory resources are insufficient.

617: Memory resources are insufficient.

Procedure

  • Use independent and common queues for the cause "173: Snoop resources are insufficient." Services use the independent queue preferentially. When the independent queue resources are insufficient, the common queue is used for some specific services. During card replacement, some preferentially delivered services may occupy all independent queue resources, so that some services that can only use the independent queue cannot be delivered due to insufficient snoop resources. To solve this problem, delete some delivered services based on their priorities and redeliver the important services that can only use the independent queue. After all these important services are successfully delivered, reconfigure the deleted services to adjust snoop resource usage.
  • For the cause "174: ARP resources are overloaded.", properly plan network deployment and reduce the number of terminals connected to the device to prevent the situation where all Layer 3 packets are forwarded by the local device. In addition, run the arp resource-mode command in the system view to increase the number of ARP forwarding resources available to the device.
  • Delete the unused LAG, BFD, and TE configuration for the cause "275: Protection group resources are overloaded."
  • Delete the unused VPN instance for the cause "276: Forwarding VRF resources are overloaded."
  • Run the assign forward ipv6 longer-mask resource command in the system view to allocate resources for the cause "570: IPv6 routes with masks greater than 64 bits and less than 128 bits are insufficient."
  • For other causes, contact technical support personnel.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039527

Views: 75449

Downloads: 21

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next