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

MCAST

MCAST_1.3.6.1.4.1.2011.5.25.227.2.1.8 hwBoardL2mcResLack

Description

MCAST/4/L2MCINDEXISLACK: OID [OID] The l2mc index resource usage has exceeded [GAUGE]%. (Slot=[OCTET], ResourceType=[INTEGER])

The Layer 2 multicast index resource usage exceeded the upper limit.

Attribute

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

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
GAUGE Upper limit of the Layer 2 multicast index resource usage.
OCTET Slot ID.
INTEGER Cause of the alarm.

Impact on the System

If the number of Layer 2 multicast MAC address-based forwarding entries continues increasing, the hardware resources may be used up, causing failures to forwarding new multicast streams.

Possible Causes

The number of Layer 2 multicast MAC address-based forwarding entries exceeded the upper limit.

Procedure

  1. Perform following operations for different types of multicast forwarding entries:

    • For dynamic Layer 2 multicast forwarding entries, run the display igmp-snooping port-info or display mld-snooping port-info command to check whether there are too many IPv4 or IPv6 Layer 2 multicast forwarding entries for IP address-based forwarding. If so, run the reset igmp-snooping group { all | vlan { all | vlan-id [ [ source-address source-address ] group-address group-address ] } } or reset mld-snooping group { all | vlan vlan-id [ [ source-address source-ipv6-address ] group-address group-ipv6-address ] } command to delete unnecessary IPv4 or IPv6 entries.
    • For static Layer 2 multicast forwarding entries, run the undo l2-multicast static-group [ source-address source-ip-address ] group-address group-ip-address vlan { all | { vlan-id1 [ to vlan-id2 ] } &<1-10> } command in the interface view to delete the static group configuration.

  2. Check whether the L2MCINDEXISRESUME notification is generated. If not, go to step 3.
  3. Contact technical support.

MCAST_1.3.6.1.4.1.2011.5.25.227.2.1.9 hwBoardL2mcResLackResume

Description

MCAST/4/L2MCINDEXISRESUME: OID [OID] The l2mc index resource usage has fallen below [GAUGE]%. (Slot=[OCTET], ResourceType=[INTEGER])

The Layer 2 multicast index resource usage restored to the normal range.

Attribute

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

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
GAUGE Upper limit of the Layer 2 multicast index resource usage.
OCTET Slot ID.
INTEGER Cause of the alarm.

Impact on the System

None.

Possible Causes

The number of Layer 2 multicast entries restored to the normal range.

Procedure

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

MCAST_1.3.6.1.4.1.2011.5.25.227.2.1.10 hwBoardIpmcResLack

Description

MCAST/4/IPMCINDEXISLACK: OID [OID] The ipmc index resource usage has exceeded [GAUGE]%. (Slot=[OCTET], ResourceType=[INTEGER])

The IP multicast index resource usage exceeded the upper limit.

Attribute

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

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
GAUGE Upper limit of the IP multicast index resource usage.
OCTET Slot ID.
INTEGER Cause of the alarm.

Impact on the System

If the number of Layer 3 multicast forwarding entries or Layer 2 multicast IP-based forwarding entries continues increasing, the hardware resources may be used up, causing failures to forwarding new multicast streams.

Possible Causes

The number of Layer 3 multicast forwarding entries or Layer 2 multicast IP-based forwarding entries exceeded the upper limit.

Procedure

  1. Perform following operations for different types of multicast forwarding entries:

    • IPv4 and IPv6 Layer 2 multicast forwarding entries share index resources. Run the display igmp-snooping port-info or display mld-snooping port-info command to check whether there are too many IPv4 or IPv6 Layer 2 multicast forwarding entries for IP address-based forwarding. If so, run the reset igmp-snooping group { all | vlan { all | vlan-id [ [ source-address source-address ] group-address group-address ] } } or reset mld-snooping group { all | vlan vlan-id [ [ source-address source-ipv6-address ] group-address group-ipv6-address ] } command to delete unnecessary entries. If static Layer 2 multicast forwarding entries are configured, run the undo l2-multicast static-group [ source-address source-ip-address ] group-address group-ip-address vlan { all | { vlan-id1 [ to vlan-id2 ] } &<1-10> } command in the interface view to delete static group configuration. If the number of IPv4 or IPv6 Layer 2 multicast forwarding entries for IP address-based forwarding is normal, go to step 3.
    • IPv4 and IPv6 Layer 3 forwarding entries share index resources. Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] forwarding-table or display multicast ipv6 forwarding-table command to check whether there are too many IPv4 or IPv6 Layer 3 multicast forwarding entries. If so, run the reset multicast [ vpn-instance vpn-instance-name | all-instance ] forwarding-table { group-address [ mask { group-mask | group-mask-length } ] | source-address [ mask { source-mask | source-mask-length } ] } or reset multicast ipv6 forwarding-table { ipv6-group-address [ ipv6-group-mask-length ] | ipv6-source-address [ ipv6-source-mask-length ] | incoming-interface { interface-type interface-number | register } } * command to delete unnecessary forwarding entries. If not, go to step 3.

  2. Check whether the IPMCINDEXISRESUME notification is generated. If not, go to step 3.
  3. Contact technical support.

MCAST_1.3.6.1.4.1.2011.5.25.227.2.1.11 hwBoardIpmcResLackResume

Description

MCAST/4/IPMCINDEXISRESUME: OID [OID] The ipmc index resource usage has fallen below [GAUGE]%. (Slot=[OCTET], ResourceType=[INTEGER])

The IP multicast index resource usage restored to the normal range.

Attribute

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

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
GAUGE Upper limit of the IP multicast index resource usage.
OCTET Slot ID.
INTEGER Cause of the alarm.

Impact on the System

None.

Possible Causes

The number of Layer 3 multicast entries restored to the normal range.

Procedure

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

MCAST_1.3.6.1.4.1.2011.5.25.227.2.1.53 hwBoardMcResFull

Description

MCAST/4/MCASTRESOURCEFULL:OID [OID] The multicast entry resource has been exhausted. (Slot=[OCTET], ResourceType=[INTEGER])

This alarm is generated when multicast L2MC, IPMC, or ACL resources on the device are used up.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.1.53 Warning environmentalAlarm(6)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
Slot Slot of the card that generates the alarm.
ResourceType Type of the resource for the forwarding engine:
  • l2mcindex(74)
  • ipmcindex(75)
  • ACL(212)
  • mcfibv4NumExceedThresHold(321)
  • mcfibv6NumExceedThresHold(322)
  • l2mcTable(749)
  • ipmcTable(750)
  • ipmcVlanTable(751)
  • mlibTable(752)
  • elbTable(753)
  • fdbTable(754)
  • vidxTable(755)
  • tcamTable(756)
  • mllTable(758)

Impact on the System

  • ResourceType = l2mcindex(74): If the number of Layer 2 multicast MAC address-based forwarding entries continues increasing, the hardware resources may be used up, causing failures to forwarding new multicast streams.
  • ResourceType = ipmcindex(75): If the number of Layer 3 multicast forwarding entries or the number of Layer 2 multicast IP address-based forwarding entries continues increasing, the hardware resources may be used up, causing failures to forwarding new multicast streams.
  • ResourceType = ACL(212): If more public MTunnel outbound interfaces are added or if member interfaces are added to the Eth-Trunk that functions as the public multicast loopback interface when multicast VPN is configured, multicast traffic may fail to be forwarded due to insufficient ACL resources.

Possible Causes

  • Cause 1: The L2MC resources on the card are used up.
  • Cause 2: The IPMC resources on the card are used up.
  • Cause 2: The ACL resources on the card are used up.

Procedure

  1. If ResourceType is l2mcindex(74):

    Perform following operations for different types of multicast forwarding entries:
    • For dynamic Layer 2 multicast forwarding entries, run the display igmp-snooping port-info or display mld-snooping port-info command to check whether there are too many IPv4 or IPv6 Layer 2 multicast forwarding entries for IP address-based forwarding. If so, run the reset igmp-snooping group { all | vlan { all | vlan-id [ [ source-address source-address ] group-address group-address ] } } or reset mld-snooping group { all | vlan vlan-id [ [ source-address source-ipv6-address ] group-address group-ipv6-address ] } command to delete unnecessary IPv4 or IPv6 entries.
    • For static Layer 2 multicast forwarding entries, run the undo l2-multicast static-group [ source-address source-ip-address ] group-address group-ip-address vlan { all | { vlan-id1 [ to vlan-id2 ] } &<1-10> } command in the interface view to delete the static group configuration.

  2. If ResourceType is ipmcindex(75):

    Perform following operations for different types of multicast forwarding entries:
    • IPv4 and IPv6 Layer 2 multicast forwarding entries share index resources. Run the display igmp-snooping port-info or display mld-snooping port-info command to check whether there are too many IPv4 or IPv6 Layer 2 multicast forwarding entries for IP address-based forwarding. If so, run the reset igmp-snooping group { all | vlan { all | vlan-id [ [ source-address source-address ] group-address group-address ] } } or reset mld-snooping group { all | vlan vlan-id [ [ source-address source-ipv6-address ] group-address group-ipv6-address ] } command to delete unnecessary entries. If static Layer 2 multicast forwarding entries are configured, run the undo l2-multicast static-group [ source-address source-ip-address ] group-address group-ip-address vlan { all | { vlan-id1 [ to vlan-id2 ] } &<1-10> } command in the interface view to delete static group configuration.
    • IPv4 and IPv6 Layer 3 forwarding entries share index resources. Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] forwarding-table or display multicast ipv6 forwarding-table command to check whether there are too many IPv4 or IPv6 Layer 3 multicast forwarding entries. If so, run the reset multicast [ vpn-instance vpn-instance-name | all-instance ] forwarding-table { group-address [ mask { group-mask | group-mask-length } ] | source-address [ mask { source-mask | source-mask-length } ] } or reset multicast ipv6 forwarding-table { ipv6-group-address [ ipv6-group-mask-length ] | ipv6-source-address [ ipv6-source-mask-length ] | incoming-interface { interface-type interface-number | register } } * command to delete unnecessary forwarding entries.

  3. If ResourceType is ACL(212):

    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 log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.

Related Information

None.

MCAST_1.3.6.1.4.1.2011.5.25.227.2.1.62 hwBoardMcResLack

Description

MCAST/4/MCASTRESOURCELACK:OID [OID] The multicast entry resource usage has exceeded [GAUGE]%. (Slot=[OCTET], ResourceType=[INTEGER])

The usage of multicast entry resources exceeds the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.1.62 Warning environmentalAlarm(6)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
GAUGE Indicates the threshold. You can set the threshold using the multicast threshold-alarm upper-limit upper-limit lower-limit lower-limit command.
Slot Indicates the slot ID of the card that generates the alarm.
ResourceType Indicates the type of multicast entry resources.
  • mcfibv4NumExceedThresHold(321)
  • mcfibv6NumExceedThresHold(322)
  • l2mcTable(749)
  • ipmcTable(750)
  • ipmcVlanTable(751)
  • mlibTable(752)
  • elbTable(753)
  • fdbTable(754)
  • vidxTable(755)
  • tcamTable(756)
  • mllTable(758)

Impact on the System

Attempting to add more Layer 2 multicast MAC address-based forwarding entries, Layer 3 multicast entries, or Layer 2 multicast IP address-based forwarding entries will consume hardware resources and ultimately cause multicast traffic forwarding to fail.

Possible Causes

  • Cause 1: The MFIBv4 resource usage on the card exceeds the threshold.
  • Cause 2: The MFIBv6 resource usage on the card exceeds the threshold.
  • Cause 3: The L2MC resource usage on the card exceeds the threshold.
  • Cause 4: The IPMC resource usage on the card exceeds the threshold.
  • Cause 5: The IPMC_VLAN resource usage on the card exceeds the threshold.
  • Cause 6: The MLIB resource usage on the card exceeds the threshold.
  • Cause 7: The ELB resource usage on the card exceeds the threshold.
  • Cause 8: The FDB resource usage on the card exceeds the threshold.
  • Cause 9: The VIDX resource usage on the card exceeds the threshold.
  • Cause 10: The TCAM resource usage on the card exceeds the threshold.
  • Cause 11: The MLL resource usage on the card exceeds the threshold.

Procedure

  1. Perform the following operations for different types of multicast forwarding entries:

    • If the device is configured to generate more dynamic Layer 2 multicast forwarding entries, run the display igmp-snooping port-info or display mld-snooping port-info command to check whether there are too many IPv4 or IPv6 Layer 2 multicast forwarding entries for IP address-based forwarding. If so, run the following commands to delete unnecessary entries: reset igmp-snooping group { all | vlan { all | vlan-id [ [ source-address source-address ] group-address group-address ] } } and reset mld-snooping group { all | vlan vlan-id [ [ source-address source-ipv6-address ] group-address group-ipv6-address ] }
    • If the device is configured to generate more static Layer 2 multicast forwarding entries, run the following command in the interface view to delete multicast forwarding entries: undo l2-multicast static-group [ source-address source-ip-address ] group-address group-ip-address vlan { all | { vlan-id1 [ to vlan-id2 ] } &<1-10> }
    • If the device is configured to generate more Layer 3 multicast forwarding entries, run the display multicast [ vpn-instance vpn-instance-name | all-instance ] forwarding-table and display multicast ipv6 forwarding-table commands to check whether there are too many IPv4 or IPv6 Layer 3 multicast forwarding entries on the device. If so, run the reset multicast [ vpn-instance vpn-instance-name | all-instance ] forwarding-table { group-address [ mask { group-mask | group-mask-length } ] | source-address [ mask { source-mask | source-mask-length } ] } and reset multicast ipv6 forwarding-table { ipv6-group-address [ ipv6-group-mask-length ] | ipv6-source-address [ ipv6-source-mask-length ] | incoming-interface { interface-type interface-number | register } } * commands to delete unnecessary Layer 3 multicast forwarding entries.

  2. Check whether the fault is rectified. If not, contact technical support.

MCAST_1.3.6.1.4.1.2011.5.25.227.2.1.63 hwBoardMcResLackResume

Description

MCAST/4/MCASTRESOURCERESUME:OID [OID] The multicast entry resource usage has fallen below [GAUGE]%. (Slot=[OCTET], ResourceType=[INTEGER])

The multicast entry resource usage is restored to below the threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.1.63 Warning environmentalAlarm(6)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
GAUGE Indicates the threshold. You can set the threshold using the multicast threshold-alarm upper-limit upper-limit lower-limit lower-limit command.
Slot Indicates the slot ID of the card that generates the alarm.
ResourceType Indicates the type of multicast entry resources.
  • mcfibv4NumExceedThresHold(321)
  • mcfibv6NumExceedThresHold(322)
  • l2mcTable(749)
  • ipmcTable(750)
  • ipmcVlanTable(751)
  • mlibTable(752)
  • elbTable(753)
  • fdbTable(754)
  • vidxTable(755)
  • tcamTable(756)
  • mllTable(758)

Impact on the System

None

Possible Causes

  • Cause 1: The MFIBv4 resource usage on the card is restored to below the threshold.
  • Cause 2: The MFIBv6 resource usage on the card is restored to below the threshold.
  • Cause 3: The L2MC resource usage on the card is restored to below the threshold.
  • Cause 4: The IPMC resource usage on the card is restored to below the threshold.
  • Cause 5: The IPMC_VLAN resource usage on the card is restored to below the threshold.
  • Cause 6: The MLIB resource usage on the card is restored to below the threshold.
  • Cause 7: The ELB resource usage on the card is restored to below the threshold.
  • Cause 8: The FDB resource usage on the card is restored to below the threshold.
  • Cause 9: The VIDX resource usage on the card is restored to below the threshold.
  • Cause 10: The TCAM resource usage on the card is restored to below the threshold.
  • Cause 11: The MLL resource usage on the card is restored to below the threshold.

Procedure

  1. This alarm message is informational only. No action is required.
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 3499

Downloads: 2

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