< Home

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 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)
  • mcfibv4Num(321)
  • mcfibv6Num(322)
  • l2mcTable(749)
  • ipmcTable(750)
  • ipmcVlanTable(751)
  • mlibTable(752)
  • elbTable(753)
  • fdbTable(754)
  • vidxTable(755)
  • tcamTable(756)
  • mllTable(758)
  • l3intflistTable(833)
  • mcpmskTable(834)

Impact on the System

Multicast services cannot be forwarded due to insufficient ACL resources or hardware resources.

Possible Causes

  • Cause 1: The L2MC index resources on the device are used up.
  • Cause 2: The IPMC index resources on the device are used up.
  • Cause 3: The ACL resources on the device are used up.
  • Cause 4: The MFIBv4 resources on the device are used up.
  • Cause 5: The MFIBv6 resources on the device are used up.
  • Cause 6: The L2MC table resources on the device are used up.
  • Cause 7: The IPMC table resources on the device are used up.
  • Cause 8: The IPMC_VLAN table resources on the device are used up.
  • Cause 9: The MLIB table resources on the device are used up.
  • Cause 10: The ELB table resources on the device are used up.
  • Cause 11: The FDB table resources on the device are used up.
  • Cause 12: The VIDX table resources on the device are used up.
  • Cause 13: The TCAM table resources on the device are used up.
  • Cause 14: The MLL table resources on the device are used up.
  • Cause 15: The L3INTFLIST table resources on the device are used up.
  • Cause 16: The MCPMSK table resources on the device are used up.

Procedure

  1. 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.

  2. For other resource types, perform the following operations for different types of multicast forwarding entries:

    • If the fault occurs on a VPLS network, run the display igmp-snooping port-info command to check whether there are too many Layer 2 multicast forwarding entries for MAC address-based forwarding. If so, run the reset igmp-snooping group { all | vsi { all | name vsi-name [ [ source-address source-address ] group-address group-address ] } } command to delete unnecessary 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 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 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.

  3. 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.

Parent Topic: MCAST
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >