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 8800, 7800, 6800, and 5800 V200R005C10

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).
FIB_1.3.6.1.4.1.2011.5.25.227.2.1.3 hwBoardFwdResLack

FIB_1.3.6.1.4.1.2011.5.25.227.2.1.3 hwBoardFwdResLack

Description

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

The device forwarding engine resources were overloaded.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwBoardFwdResLack

Trap OID

1.3.6.1.4.1.2011.5.25.227.2.1.3

Alarm ID

0x08710000

Alarm Type

processingErrorAlarm

Raise or Clear

Raise

Match trap

FIB_1.3.6.1.4.1.2011.5.25.227.2.1.4 hwBoardFwdResLackResume

Parameters

Parameter Description

EntityPhysicalindex

Index of a physical entity

EntPhysicalindex

Index of a physical entry

EntPhysicalName

Name of a physical entry

Slot

Slot information

Reason

Possible cause for the trap

ReasonDescription

The detailed cause of the trap.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.227.1.1

hwEntPhysicalindex

N/A

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

N/A

1.3.6.1.4.1.2011.5.25.227.1.3

hwFwdResLackReasonId

N/A

Impact on the System

1: Certain services may be interrupted, including MPLS services (TE).Only support LPUI-100C.

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

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

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

5: Certain ND entries cannot be delivered, resulting in interruption of some IPv6 forwarding services.

6: Certain statistics functions are invalid, including the interface statistics, sub-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.

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

13: Cetain MPLS service may be unavailable.

14: Certain VPN service may be unavailable.

15: Certain IPV6 service may be broken.

16: Certain service carried by tunnel may be broken.

17: Certain BFD service may be broken.

20: Certain NetStream service may be broken.

21: Certain service carried by vlanIf may be broken.

25: Certain leaf of multicast group can not be established, and multicast stream from some.

27: This alarm does not affect services temporarily. However, if you continue to use unassigned Layer 3 resources, hardware resource usage may reach 100%. In this case, when you configure some Layer 3 services, these Layer 3 services are unavailable.

28: This alarm does not affect services temporarily. However, if you continue to use unassigned Layer 3 resources, hardware resource usage may reach 100%. In this case, when you configure some Layer 3 services, these Layer 3 services are unavailable.

29: This alarm does not affect services temporarily. However, if you continue to use unassigned Layer 3 resources, hardware resource usage may reach 100%. In this case, when you configure some Layer 3 services, these Layer 3 services are unavailable.

30: This alarm does not affect services temporarily. However, if you continue to use unassigned Layer 3 resources, hardware resource usage may reach 100%. In this case, when you configure some Layer 3 services, these Layer 3 services are unavailable.

31: This alarm does not affect services temporarily. However, if you continue to use unassigned Layer 3 resources, hardware resource usage may reach 100%. In this case, when you configure some Layer 3 services, these Layer 3 services are unavailable.

32: This alarm does not affect services temporarily. However, if you continue to use unassigned Layer 3 resources, hardware resource usage may reach 100%. In this case, when you configure some Layer 3 services, these Layer 3 services are unavailable.

33: Certain QVCT entries cannot be delivered, resulting in interruption of some QINQ services or forwarding errors.

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

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

37: Certain IPv6 full rules cannot be delivered, result in some services refer to IPv6 full rulse lose efficacy.

38: Certain IPv6 mask rules cannot be delivered, result in some services refer to IPv6 mask rulse lose efficacy.

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

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

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

42: Certain ccm send instance may become invalid.

43: Certain ccm receive instance may become invalid.

44: Certain slm send instance may become invalid.

45: Certain 1dm send instance may become invalid.

46: Certain 2dm send instance may become invalid.

47: This alarm does not affect services temporarily. However, if you continue to use unassigned Layer 3 resources, hardware resource usage may reach 100%. In this case, when you configure some Layer 3 services, these Layer 3 services are unavailable.

48: Certain IPv4 multicast stream of some group can not be forwarded successfully.

49: Certain IPv6 multicast stream of some group can not be forwarded successfully.

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

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

52: Certain dlm send instance may become invalid.

53: Certain IPv4 bgp can not be forwarded successfully.

54: Certain IPv6 bgp can not be forwarded successfully.

55: Service may be unavailable.

57: Service may be unavailable.

58: Service may be unavailable.

59: Service may be unavailable.

61: Service may be unavailable.

62: Service may be unavailable.

63: Service may be unavailable.

64: Service may be unavailable.

65: Service may be unavailable.

66: Service may be unavailable.

67: Service may be unavailable.

68: Service may be unavailable.

69: Service may be unavailable.

70: Certain IPFPM loss-measure continual enable or delay-measure continual enable may become invalid.

71: Certain bind table may become invalid.

72: Some operation of layer 3 may be invalid.

73: No effects, but will take other tblm resource.

26: Cetain TRILL service may be unavailable.

103: Some IPv4 services are interrupted.

104: The QVCT entries on some flexible access sub-interfaces fail to be delivered, which may cause some flexible access services to be interrupted or the traffic to be forwarded incorrectly.

106: Hqos service may be unavailable.

107: Hqos service may be unavailable.

108: Hqos service may be unavailable.

109: Hqos service may be unavailable.

110: Hqos service may be unavailable.

111: Hqos service may be unavailable.

112: Hqos service may be unavailable.

113: Hqos service may be unavailable.

114: Hqos service may be unavailable.

115: Hqos service may be unavailable.

116: Hqos service may be unavailable.

117: Hqos service may be unavailable.

118: Hqos service may be unavailable.

119: Hqos service may be unavailable.

120: Hqos service may be unavailable.

121: Hqos service may be unavailable.

122: Hqos service may be unavailable.

123: Hqos service may be unavailable.

124: Hqos service may be unavailable.

125: Ifnet car inbount may be unavailable.

126: Ifnet car outbount may be unavailable.

127: Car remark Template in inbount may be unavailable.

128: Car remark Template in outbount may be unavailable.

129: Traffic policy may be unavailable.

130: Traffic policy car in inbound may be unavailable.

131: Traffic policy car in outbound may be unavailable.

132: Traffic policy Re table may be unavailable.

133: Traffic policy NHP table may be unavailable.

134: Traffic policy IPv4 acl in inbound may be unavailable.

135: Traffic policy IPv6 acl in inbound may be unavailable.

136: Traffic policy IPv4 acl in outbound may be unavailable.

137: Traffic policy IPv6 acl in outbound may be unavailable.

138: Qppb car in inbound may be unavailable.

139: Qppb car in outbound may be unavailable.

140: Mirror in outbound may be unavailable.

141: Mirror in outbound may be unavailable.

142: Obtaining packet header in inbound may be unavailable.

143: Obtaining packet header in outbound may be unavailable.

144: Suppresion Car in inbound may be unavailable.

145: Suppresion Car in outbound may be unavailable.

146: Mirror Car in inbound may be unavailable.

147: Mirror Car in outbound may be unavailable.

148: Traffic policy NST table may be unavailable.

149: Profile Suppresion car in inbound may be unavailable.

150: Profile Suppresion car in outbound may be unavailable.

151: Profile Suppresion stat in inbound may be unavailable.

152: Profile Suppresion stat in outbound may be unavailable.

153: Profile single car in inbound may be unavailable.

154: Profile single car in outbound may be unavailable.

155: Profile single car stat in inbound may be unavailable.

156: Profile single car stat in outbound may be unavailable.

157: ACL stat in inbound may be unavailable.

158: ACL stat in outbound may be unavailable.

159: ACL car stat may be unavailable.

160: Ifnetcar stat in inbound may be unavailable.

161: Ifnetcar stat in outbound may be unavailable.

162: Traffic policy L2 ACL in inbound may be unavailable.

163: Traffic policy L2 acl in outbound may be unavailable.

Possible Causes

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

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

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

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

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

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

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

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

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

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

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

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

Cause 13: The number of forward tokens 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 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 25: The number of MLID exceeded the specification of the forwarding engine resources.

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

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

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

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

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

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

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

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

Cause 37: Certain IPv6 full rules cannot be delivered, result in some services refer to ipv6 full rulse lose efficacy.

Cause 38: Certain IPv6 mask rules cannot be delivered, result in some services refer to ipv6 mask rulse lose efficacy.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Cause 53: The number of IPV4 bgp statistic ID exceeded the specifications of the forwarding engine resources.

Cause 54: The number of IPV6 bgp statistic ID exceeded the specifications of the forwarding engine resources.

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

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

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

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

Cause 61: The number of ACL Entry exceeded the specification of the forwarding engine resources.

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

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

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

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

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

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

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

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

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

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

Cause 72: ACL failed to be delivered.

Cause 73: The number of ARP table numbers exceeded the specifications of the forwarding engine resources.

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

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

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

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

Cause 107: The number of Inbound flow-mapping exceeded the specification of the forwarding engine resources.

Cause 108: The number of Outbound flow-mapping exceeded the specification of the forwarding engine resources.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Cause 125: The number of Inbound Car id exceeded the specification of the forwarding engine resources.

Cause 126: The number of Outbound Car id exceeded the specification of the forwarding engine resources.

Cause 127: The number of Inbound Car remark template exceeded the specification of the forwarding engine resources.

Cause 128: The number of Outbound Car remark template exceeded the specification of the forwarding engine resources.

Cause 129: The number of Gid exceeded the specification of the forwarding engine resources.

Cause 130: The number of Inbound Behavior car exceeded the specification of the forwarding engine resources.

Cause 131: The number of Outbound Behavior car exceeded the specification of the forwarding engine resources.

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

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

Cause 134: The number of Inbound ipv4 tcam exceeded the specification of the forwarding engine resources.

Cause 135: The number of Inbound ipv6 tcam exceeded the specification of the forwarding engine resources.

Cause 136: The number of Outbound ipv4 tcam exceeded the specification of the forwarding engine resources.

Cause 137: The number of Outbound ipv6 tcam exceeded the specification of the forwarding engine resources.

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

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

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

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

Cause 142: The number of Inbound packet header obtaining mirror entries exceeded the specification of the forwarding engine resources.

Cause 143: The number of Outbound packet header obtaining mirror entries exceeded the specification of the forwarding engine resources.

Cause 144: The number of Inbound Suppresion car exceeded the specification of the forwarding engine resources.

Cause 145: The number of Outbound Suppresion exceeded the specification of the forwarding engine resources.

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

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

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

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

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

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

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

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

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

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

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

Cause 157: The number of Inbound acl stat exceeded the specification of the forwarding engine resources.

Cause 158: The number of Outbound acl stat exceeded the specification of the forwarding engine resources.

Cause 159: The number of Acl car stat exceeded the specification of the forwarding engine resources.

Cause 160: The number of Inbound Ifnetcar stat exceeded the specification of the forwarding engine resources.

Cause 161: The number of Outbound Ifnetcar stat exceeded the specification of the forwarding engine resources.

Cause 162: The number of Inbound L2 tcam exceeded the specification of the forwarding engine resources.

Cause 163: The number of Outbound L2 tcam exceeded the specification of the forwarding engine resources.

Procedure

  • Please contact technical support personnel technical support personnel.
Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 17238

Downloads: 25

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