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

E9000 Server V100R001 HMM Alarm Handling 19

This document describes E9000 server alarms in terms of the meaning, impact on the system, possible causes, and solutions.
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).
FES

FES

FES_1.3.6.1.4.1.2011.5.25.227.2.1.1 hwWholeFwdResLack

Description

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

The whole device forwarding engine resources were overloaded.

Attributes

Attribute

Description

Trap OID

1.3.6.1.4.1.2011.5.25.227.2.1.1

Trap severity

Major

Match trap

FES_1.3.6.1.4.1.2011.5.25.227.2.1.2 hwWholeFwdResLackResume

Parameters

Parameter

Description

EntiyPhysicalindex

The index of physical entry

EntPhysicalindex

The index of physical entry

EntPhysicalName

The name of physical entry

Reason

The probable cause of trap

Impact on the System

1: Cetain MPLS and VPLS service may be unavailable.

2: Certain VPN service may be unavailable.

3: Certain IPv6 service may be broken.

4: Certain service carried by tunnel may be broken.

5: Certain BFD service may be broken.

6: Certain VPLS service may be broken.

7: Certain VPLS service may be broken.

8: Certain NetStream service may be broken.

9: Certain service carried by VlanIf may be broken.

10: Certain multicast replication services (multicast, VLAN, and VPLS) may be unavailable.

11: Certain downstream interfaces to which data (multicast, VLAN, and VPLS data) is replicated to may be unavailable.

12: Certain multicast group can not be established, and the multicast stream can not be forwarded successfully.

13: Cetain TRILL service may be unavailable.

14: Cannot establish more bfd session.

Possible Causes

Cause 1: The number of forward tokens exceeded the specifications of the forwarding engine resources.

Cause 2: The number of FVRFs exceeded the specifications of the forwarding engine resources.

Cause 3: The number of ATIndex exceeded the specifications of the forwarding engine resources.

Cause 4: The number of Tunnel Index exceeded the specifications of the forwarding engine resources.

Cause 5: The number of Bfd Index exceeded the specifications of the forwarding engine resources .

Cause 6: The number of VPLS LearnId exceeded the specifications of the forwarding engine resources.

Cause 7: The number of VSI Index exceeded the specifications of the forwarding engine resources.

Cause 8: The number of Ns Index exceeded the specifications of the forwarding engine resources.

Cause 9: The number of Ring Index exceeded the specifications of the forwarding engine resources.

Cause 10: The number of configured multicast replication services (for multicast, VLAN, and VPLS) exceeded the specification supported by the entire system.

Cause 11: The number of downstream interfaces to which data (multicast, VLAN, and VPLS data) is replicated to exceeded the specification supported by the entire system.

Cause 12: The number of TMGID exceeded the specification of the forwarding engine resources.

Cause 13: The number of trill nhpIndex exceeded the specifications of the forwarding engine resources.

Cause 14: The number of BFD sessions exceeded the specifications of the global bfd sessions.

Procedure
  • Please contact Huawei technical support personnel.

FES_1.3.6.1.4.1.2011.5.25.227.2.1.2 hwWholeFwdResLackResume

Description

The whole device forwarding engine resources overload is recovered. (EntiyPhysicalindex=[EntiyPhysicalindex], EntPhysicalindex=[EntPhysicalindex], EntPhysicalName=[EntPhysicalName], Reason=[ReasonId])

The whole device forwarding engine resources overload is recovered.

Attributes

Attribute

Description

Trap OID

1.3.6.1.4.1.2011.5.25.227.2.1.2

Trap severity

Major

Match trap

FES_1.3.6.1.4.1.2011.5.25.227.2.1.1 hwWholeFwdResLack

Parameters

Parameter

Description

EntiyPhysicalindex

The index of physical entry

EntPhysicalindex

The index of physical entry

EntPhysicalName

The name of physical entry

Reason

The probable cause of trap

Impact on the System

The alarm of the whole device forwarding engine resources overload is cleared.

Possible Causes

Cause: After the overload alarm is generated for the whole device forwarding engine resources, if some services are deleted and the forward resource requirement can be satisfied, the elimination of the alarm will be reported.

Procedure
  • This trap message is informational only, and no action is required.

FES_1.3.6.1.4.1.2011.5.25.227.2.1.3 hwBoardFwdResLack

Description

The board forwarding engine resources were overloaded. (EntiyPhysicalindex=[EntiyPhysicalindex], EntPhysicalindex=[EntPhysicalindex], EntPhysicalName=[EntPhysicalName], Slot=[SlotStr], Reason=[ReasonId])

The device forwarding engine resources were overloaded.

Attributes

Attribute

Description

Trap OID

1.3.6.1.4.1.2011.5.25.227.2.1.3

Trap severity

Major

Match trap

FES_1.3.6.1.4.1.2011.5.25.227.2.1.4 hwBoardFwdResLackResume

Parameters

Parameter

Description

EntiyPhysicalindex

The index of physical entry

EntPhysicalindex

The index of physical entry

EntPhysicalName

The name of physical entry

Slot

stack id

Reason

The probable cause of trap

Impact on the System

1: Certain services may be interrupted, including MPLS services (TE).

2: Certain IPv4 FIB entries cannot be delivered, resulting in interruption of some IPv4 services or forwarding errors.

4: Certain ARP entries cannot be delivered, resulting in interruption of some IPv4 forwarding services.

6: Certain statistics functions are invalid, including the interface statistics, statistics on various tunnels, and statistics on traffic policies.

7: Certain traffic classification-based policies and CAR rules may become invalid.

8: Certain L2VPN connections may be unavailable.

9: Certain Multicast Out Interface entries cannot be delivered, resulting in interruption of some Multicast forwarding services.

10: Certain new BFD session may be up and down.

11: Certain IPv4 multicast FIB entries cannot be delivered, resulting in interruption of some IPv4 multicast services or forwarding errors.

13: Cetain MPLS and VPLS service may be unavailable.

14: Certain VPN service may be unavailable.

16: Certain service carried by tunnel may be broken.

17: Certain BFD service may be broken.

18: Certain VPLS service may be broken.

19: Certain VPLS service may be broken.

20: Certain NetStream service may be broken.

21: Certain service carried by vlanIf may be broken.

22: Certain leaf of multicast group can not be established, and multicast stream from some interfaces can not be forwarded successfully.

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

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

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

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

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

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

30: Certain IPv4 full rules cannot be delivered, result in some services refer to ipv4 full rulse lose efficacy.

31: Certain IPv4 mask rules cannot be delivered, result in some services refer to ipv4 mask rulse lose efficacy.

34: Certain characteristic code rules cannot be delivered, result in some services refer to characteristic code rules rulse lose efficacy.

35: Certain complex rules cannot be delivered, result in some services refer to complex rules rulse lose efficacy.

36: Certain Tcp Flag rules cannot be delivered, result in some services refer to Tcp Flag rules rulse lose efficacy.

37: Certain ccm send instance may become invalid.

38: Certain ccm receive instance may become invalid.

39: Certain slm send instance may become invalid.

40: Certain 1dm send instance may become invalid.

41: Certain 2dm send instance may become invalid.

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

43: Certain IPV4 multicast stream of some group can not be forwarded successfully.

45: Certain NHP entries cannot be delivered, resulting in forwarding errors.

46: Certain NetStream entries cannot be delivered, resulting in NetStream forwarding services can not be restored.

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 4: The number of ARPs 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 13: The number of forward tokens 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 ATIndex 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 VSI Index exceeded the specifications of the forwarding engine resources.

Cause 20: The number of Ns Index exceeded the specifications of the forwarding engine resources.

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

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

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

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

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

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

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

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

Cause 30: Certain IPv4 mask rules cannot be delivered, result in some services refer to IPv4 full rulse lose efficacy.

Cause 31: Certain IPv4 mask rules cannot be delivered, result in some services refer to IPv4 mask rulse lose efficacy.

Cause 34: Certain characteristic code rules cannot be delivered, result in some services refer to characteristic code rules rulse lose efficacy.

Cause 35: Certain complex rules cannot be delivered, result in some services refer to complex rules rulse lose efficacy.

Cause 36: Certain Tcp Flag rules cannot be delivered, result in some services refer to Tcp Flag rules rulse lose efficacy.

Cause 37: The number of enabled ccm send numbers exceeded the specifications of the forwarding engine resources.

Cause 38: The number of enabled ccm receive numbers exceeded the specifications of the forwarding engine resources.

Cause 39: The number of enabled slm instance numbers exceeded the specifications of the forwarding engine resources.

Cause 40: The number of enabled ldm instance numbers exceeded the specifications of the forwarding engine resources.

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

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

Cause 45: The number of nhp numbers exceeded the specifications of the forwarding engine resources.

Cause 46: The number of netstream Index numbers exceeded the specifications of the forwarding engine resources.

Procedure
  • Please contact Huawei technical support personnel.

FES_1.3.6.1.4.1.2011.5.25.227.2.1.4 hwBoardFwdResLackResume

Description

The board forwarding engine resources overload is recovered. (EntiyPhysicalindex=[EntiyPhysicalindex], EntPhysicalindex=[EntPhysicalindex], EntPhysicalName=[EntPhysicalName], Slot=[SlotStr], Reason=[ReasonId])

The device forwarding engine resources overload is recovered.

Attributes

Attribute

Description

Trap OID

1.3.6.1.4.1.2011.5.25.227.2.1.4

Trap severity

Major

Match trap

FES_1.3.6.1.4.1.2011.5.25.227.2.1.3 hwBoardFwdResLack

Parameters

Parameter

Description

EntiyPhysicalindex

The index of physical entry

EntPhysicalindex

The index of physical entry

EntPhysicalName

The name of physical entry

Slot

stack id

Reason

The probable cause of trap

Impact on the System

The alarm of the device forwarding engine resources overload is cleared.

Possible Causes

Cause: After the overload alarm is generated for the device forwarding engine resources, if some services are deleted and the forward resource requirement can be satisfied, the elimination of the alarm will be reported.

Procedure
  • This trap message is informational only, and no action is required.
Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 192896

Downloads: 1565

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