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) l3intflistTable(833) mcpmskTable(834) vplsMcTable(859)

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 device exceeds the threshold.
Cause 2: The MFIBv6 resource usage on the device exceeds the threshold.
Cause 3: The L2MC resource usage on the device exceeds the threshold.
Cause 4: The IPMC resource usage on the device exceeds the threshold.
Cause 5: The IPMC_VLAN resource usage on the device exceeds the threshold.
Cause 6: The MLIB resource usage on the device exceeds the threshold.
Cause 7: The ELB resource usage on the device exceeds the threshold.
Cause 8: The FDB resource usage on the device exceeds the threshold.
Cause 9: The VIDX resource usage on the device exceeds the threshold.
Cause 10: The TCAM resource usage on the device exceeds the threshold.
Cause 11: The MLL resource usage on the device exceeds the threshold.
Cause 12: The L3INTFLIST resource usage on the device exceeds the threshold.
Cause 13: The MCPMSK resource usage on the device exceeds the threshold.
Cause 14: The VSI-based multicast forwarding resource usage on the device exceeds the threshold.

Procedure

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.
Check whether the fault is rectified. If not, contact technical support.