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

S9300, S9300E, and S9300X V200R013C00

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).
L3MB

L3MB

L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.5 hwBoardL3FwdResLack

Description

L3MB/4/FwdResLack:OID [OID] The layer 3 resource usage has reached or exceeded [Threshold]%.(EntPhysicalindex=[GAUGE],EntPhysicalName=[OCTET],Slot=[OCTET],ResourceType=[INTEGER])

The Layer 3 resource usage reaches or exceeds the upper threshold. Except the IPv4 route prefix entries, all Layer 3 resources have an upper usage threshold of 85%, which cannot be changed.

NOTE:

You can use the fib threshold-alarm command to set the upper threshold of the IPv4 route prefix entries.

By default, the upper threshold of the IPv4 route prefix entries is 85%.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.1.5 Warning equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
Threshold This object indicates the upper threshold of the layer 3 resource usage.
EntPhysicalindex This object indicates the index of a physical entity.
EntPhysicalName This object indicates the name of a physical entity.
Slot This object indicates the slot ID.
ResourceType This object indicates the ID of a Layer 3 resource.
  • hostTablePrefixTable(27) indicates the host route prefix entry.
  • routingTablePrefixTable(28) indicates the IPv4 route prefix entry.
  • ecmpNextHopTable(29) indicates the next hop entry of the equal-cost route.
  • layer3InterfaceTable(30) indicates the Layer 3 outbound interface entry.
  • nextHopTable(31) indicates the next hop entry.
  • tunnelDecapsulationTable(32) indicates the tunnel encapsulation and decapsulation entry.
  • ipv6RoutingTablePrefixTable(47) indicates the IPv6 route prefix entry.
  • ipv6DefipTable(767) indicates an IPv6 prefix entry of a route with a 128-bit mask.
  • tunnel6EncapsulationTable(742) indicates a IPv6 tunnel encapsulation and decapsulation entry.
  • tunnelEncapsulationTable(743) indicates a IPv4 tunnel encapsulation and decapsulation entry.
  • reTable(744) indicates a RE entry.
  • aibTable(745) indicates a AIB entry.
  • nstTable(746) indicates a NST entry.
  • vrrpTable(747) indicates a VRRP entry.
  • ipv6amTable(748) indicates a IPv6 AM entry.

Impact on the System

When the Layer 3 resource usage exceeds the upper threshold, services are not affected. If the usage of all Layer 3 resources reaches 100%, new Layer 3 services are unavailable.

Possible Causes

When the Layer 3 resource usage exceeds the upper threshold, an alarm is generated. When the usage reaches 100%, an alarm is generated again.

Procedure

  1. Lower the Layer 3 resource usage.

    • Delete unnecessary host routes, and ND and ARP entries to release host route prefix resources.
    • Delete unnecessary network segment routes to release IPv4 route prefix resources.
    • Delete unnecessary equal-cost routes to release next hop resources.
    • Delete unnecessary Layer 3 interfaces to release Layer 3 interface resources.
    • Delete unnecessary routes including host routes and network segment routes, and ND and ARP entries to release next hop resources.
    • Delete tunnels to release tunnel encapsulation and decapsulation resources.
    • Delete unnecessary network segment routes to release IPv6 route IPv6 prefix entries.
    • IPv6 prefix entries of routes with a 128-bit mask: Delete unnecessary network segment routes to release route prefix resources.
    • IPv6 tunnel encapsulation and decapsulation entry: Delete IPv6 tunnels to release tunnel encapsulation and decapsulation resources.
    • IPv4 tunnel encapsulation and decapsulation entry: Delete IPv4 tunnels to release tunnel encapsulation and decapsulation resources.
    • RE entry: Delete unnecessary routes to release RE resources.
    • AIB entry: Delete unnecessary ARP entries to release AIB resources.
    • NST entry: Delete unnecessary ECMP routes to release NSTB resources.
    • VRRP entry: Delete unnecessary VRRP configuration to release VRRP resources.
    • IPv6 AM entry: Delete unnecessary IPv6 routes to release IPv6 AM resources.

  2. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.
  3. End.

Related Information

None

L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.6 hwBoardL3FwdResLackResume

Description

L3MB/4/FwdResResume:OID [OID] The layer 3 resource usage is restored to be lower than [Threshold]%.(EntPhysicalindex=[GAUGE],EntPhysicalName=[OCTET],Slot=[OCTET],ResourceType=[INTEGER])

The Layer 3 resource usage is restored to be lower than the lower threshold. Except the IPv4 route prefix entries, all Layer 3 resources have a lower usage threshold of 65%, which cannot be changed.

NOTE:

You can use the fib threshold-alarm command to set the lower threshold of the IPv4 route prefix entries.

By default, the lower threshold of the IPv4 route prefix entries is 75%.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.1.6 Warning equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
Threshold This object indicates the lower threshold of the layer 3 resource usage.
EntPhysicalindex This object indicates the index of a physical entity.
EntPhysicalName This object indicates the name of a physical entity.
Slot This object indicates the slot ID.
ResourceType This object indicates the ID of a Layer 3 resource.
  • hostTablePrefixTable(27) indicates the host route prefix entry.
  • routingTablePrefixTable(28) indicates the IPv4 route prefix entry.
  • ecmpNextHopTable(29) indicates the next hop entry of the equal-cost route.
  • layer3InterfaceTable(30) indicates the Layer 3 outbound interface entry.
  • nextHopTable(31) indicates the next hop entry.
  • tunnelDecapsulationTable(32) indicates the tunnel encapsulation and decapsulation entry.
  • ipv6RoutingTablePrefixTable(47) indicates the IPv6 route prefix entry.
  • ipv6DefipTable(767) indicates an IPv6 prefix entry of a route with a 128-bit mask.
  • tunnel6EncapsulationTable(742) indicates a IPv6 tunnel encapsulation and decapsulation entry.
  • tunnelEncapsulationTable(743) indicates a IPv4 tunnel encapsulation and decapsulation entry.
  • reTable(744) indicates a RE entry.
  • aibTable(745) indicates a AIB entry.
  • nstTable(746) indicates a NST entry.
  • vrrpTable(747) indicates a VRRP entry.
  • ipv6amTable(748) indicates a IPv6 AM entry.

Impact on the System

Services are not affected.

Possible Causes

The Layer 3 resource usage is restored to be lower than the lower threshold.

Procedure

  1. This message is informational only, and no action is required.

Related Information

None

L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.7 hwBoardL3ACLResLack

Description

L3MB/4/ACLRESOURCELACK: OID [OID] [OCTET] (Slot=[OCTET],ReasonID=[INTEGER])

A Layer 3 service failed because of insufficient ACL resources.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.1.7 Warning equipmentAlarm (5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
[OCTET] Indicates a type of Layer 3 service. The value can be:
  • Failed to enable nd snooping: failed to enable the neighbor discovery (ND) snooping function.
  • Failed to enable ipv6: failed to enable the IPv6 function.
  • Failed to start nqa-rtp instance: failed to start an NQA RTP test instance.
Slot Indicates a slot number.
ReasonID Indicates an alarm reason ID.
  • l3aclFailed (72): failed to deliver an ACL.

Impact on the System

The Layer 3 service specified in the alarm is unavailable.

Possible Causes

ACL resources were insufficient.

Procedure

  1. Run the display acl resource [ slot slot ] command to view information about ACL resources, including ACL4 and ACL6 resources.
  2. Run the display current-configuration command to check the current configuration on the switch.
  3. Check the services that occupy ACL resources based on ACL resource information and the current configuration as follows, and delete unnecessary services to release ACL resources.

    • Check whether NAC, IPSG, MQC, and ACL-based simplified traffic policy services that occupy a large amount of ACL resources exist on the switch.
    • Check the services that occupy ACL resources based on fields in the ACL resource information. For example, MQC, ACL-based simplified traffic policy, SVF, MPLS, and BFD for VPLS services occupy UDF ACL resources. If a large amount of UDF ACL resources are occupied, check these services first.

  4. If the fault persists, collect alarm information and configuration information, and then contact technical support personnel.You can collect diagnostic information using the display diagnostic-information command.

Related Information

None.

L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.12 hwBoardServiceFailed

Description

L3MB/4/SERVICEFAILED: OID [OID] Failed to execute the command.(Command=[OCTET],ViewName=[OCTET],ReasonID=[INTEGER],ReasonDescr=[OCTET],Slot=[OCTET])

The card fails to execute the globally delivered command due to insufficient Layer 2 user entries.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.1.12 Warning equipmentAlarm (5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
Command Indicates the command name.
ViewName Indicates the view name.
ReasonID Indicates an alarm reason ID.
  • l2UserEntryOverload(92): insufficient Layer 2 user entries.
ReasonDescr Indicates the alarm reason description.
Slot Indicates the slot ID.

Impact on the System

The card fails to execute the command.

Possible Causes

The Layer 2 user entries on the card are insufficient.

Procedure

  1. Check whether some MAC addresses have been configured as BPDU MAC addresses using the bpdu mac-address command. If so, delete unnecessary BPDU MAC addresses to release entry resources used by BPDU MAC addresses.
  2. Check the VRRP configuration on the switch and delete unnecessary VRRP groups to release entry resources used by VRRP virtual MAC addresses.
  3. Check the interface configuration on the switch and delete unnecessary VLANIF interfaces and Layer 3 subinterfaces to release MAC address entry resources used by these interfaces.
  4. Release entry resources using the preceding steps, delete the globally delivered command that fails to be executed by the card in the system view, and then execute this command again.
  5. If the preceding steps cannot resolve the entry insufficiency issue, collect alarms, logs, and configurations on the switch and contact technical support personnel.

Related Information

None

L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.44 hwBoardL3NDResLack

Description

L3MB/3/IPV6NDFULL: OID [OID] Fail to download ND entry because of hash collision.(IPv6Address=[OCTET],VrfID=[INTEGER],Slot=[OCTET])

ND entries failed to be saved because of a hash conflict.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.1.44 Minor processingErrorAlarm(4)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
IPv6Address IPv6 address with the hash conflict.
VrfID VRF ID.
Slot Slot ID.

Impact on the System

The switch could not forward IPv6 traffic matching the ND entries.

Possible Causes

A hash conflict occurred when the ND entries were saved.

Procedure

  1. Run the display ipv6 routing-table command to check IPv6 routes on the switch.
  2. Delete unused IPv6 routes based on service requirements and the networking. Check whether the trap is still reported.
    • If the trap is still reported, go to step 3.
    • If the trap is not reported, no action is required.
  3. Collect alarm information and configuration information, and then contact technical support personnel.

Related Information

None

L3MB_1.3.6.1.4.1.2011.5.25.227.2.3.1 hwFwdEntryConflict

Description

L3MB/4/L3FWDCONFLICT:OID [OID] L3 forward entry regularly check abnormal. (Slot=[OCTET], ReasonId=[INTEGER])

The switch detected an anomaly when periodically checking l3-forward-entries.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.3.1 Warning equipmentAlarm (5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
Slot=[OCTET] Indicates a slot ID.
ReasonId=[INTEGER]
Indicates an alarm reason ID:
  • nextHopTable(31) l3-forward-entries are abnormal.

Impact on the System

Layer 3 services involved in the alarm may become unavailable.

Possible Causes

By default, the switch periodically checks l3-forward-entries to ensure realtime and validity of bottom-layer forwarded data and records the check result. The check result can help locate problems of Layer 3 forwarding software resource leak and residual Layer 3 forwarding hardware entries. When the switch detects an anomaly during l3-forward-entry check, an alarm is generated.

Procedure

  1. This alarm is informational only, and no action is required.

Related Information

None

L3MB_1.3.6.1.4.1.2011.5.25.227.2.3.2 hwFwdEntryConflictResume

Description

L3MB/4/L3FWDCONFLICTRESUME:OID [OID] L3 forward entry regularly check normal.(Slot=[OCTET], ReasonId=[INTEGER])

The switch detected that l3-forward-entries return to normal.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.3.2 Warning equipmentAlarm (5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
Slot=[OCTET] Indicates a slot ID.
ReasonId=[INTEGER]
Indicates the alarm reason ID:
  • nextHopTable(31) l3-forward-entries are abnormal.

Impact on the System

The system is not affected.

Possible Causes

The switch detected that l3-forward-entries returned to normal.

Procedure

  1. This alarm is informational only, and no action is required.

Related Information

None

L3MB_1.3.6.1.4.1.2011.5.25.227.2.1.55 hwBoardL3ResFull

Description

L3MB/4/L3FWDRESFULL:OID [OID] The layer 3 entry resource has been exhausted.(Slot=[OCTET],ResourceType=[INTEGER])

The layer 3 resource usage of the switch has reached 100%.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.1.55 Warning equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
Slot This object indicates the slot ID.
ResourceType This object indicates the type of a Layer 3 resource.
  • hostTablePrefixTable(27) indicates a host route prefix entry.
  • routingTablePrefixTable(28) indicates an IPv4 route prefix entry.
  • ecmpNextHopTable(29) indicates the next hop entry of an equal-cost route.
  • layer3InterfaceTable(30) indicates a Layer 3 outbound interface entry.
  • nextHopTable(31) indicates a next hop entry.
  • tunnelDecapsulationTable(32) indicates a tunnel encapsulation and decapsulation entry.
  • ipv6RoutingTablePrefixTable(47) indicates an IPv6 route prefix entry.
  • ipv6DefipTable(767) indicates an IPv6 prefix entry of a route with a 128-bit mask.
  • tunnel6EncapsulationTable(742) indicates a IPv6 tunnel encapsulation and decapsulation entry.
  • tunnelEncapsulationTable(743) indicates a IPv4 tunnel encapsulation and decapsulation entry.
  • reTable(744) indicates a RE entry.
  • aibTable(745) indicates a AIB entry.
  • nstTable(746) indicates a NST entry.
  • vrrpTable(747) indicates a VRRP entry.
  • ipv6amTable(748) indicates a IPv6 AM entry.

Impact on the System

If the usage of all Layer 3 resources reaches 100%, new Layer 3 services are unavailable.

Possible Causes

All routing entries have been occupied because the switch has learned many routes.

Procedure

  1. Lower the Layer 3 resource usage.

    • Host route prefix entry: Delete unnecessary host routes, and ND and ARP entries to release host route prefix resources.
    • IPv4 route prefix entry: Delete unnecessary network segment routes to release IPv4 route prefix resources.
    • Next hop entry of an equal-cost route: Delete unnecessary equal-cost routes to release next hop resources.
    • Layer 3 outbound interface entry: Delete unnecessary Layer 3 interfaces to release Layer 3 interface resources.
    • Next hop entry: Delete unnecessary routes including host routes and network segment routes, and ND and ARP entries to release next hop resources.
    • Tunnel encapsulation and decapsulation entry: Delete tunnels to release tunnel encapsulation and decapsulation resources.
    • IPv6 route prefix entry: Delete unnecessary network segment routes to release IPv6 route IPv6 prefix entries.
    • IPv6 prefix entries of routes with a 128-bit mask: Delete unnecessary network segment routes to release route prefix resources.
    • IPv6 tunnel encapsulation and decapsulation entry: Delete IPv6 tunnels to release tunnel encapsulation and decapsulation resources.
    • IPv4 tunnel encapsulation and decapsulation entry: Delete IPv4 tunnels to release tunnel encapsulation and decapsulation resources.
    • RE entry: Delete unnecessary routes to release RE resources.
    • AIB entry: Delete unnecessary ARP entries to release AIB resources.
    • NST entry: Delete unnecessary ECMP routes to release NSTB resources.
    • VRRP entry: Delete unnecessary VRRP configuration to release VRRP resources.
    • IPv6 AM entry: Delete unnecessary IPv6 routes to release IPv6 AM resources.

  2. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.
  3. End.

Related Information

None

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 3449

Downloads: 2

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