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

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.
Check whether the L2MCINDEXISRESUME notification is generated. If not, go to step 3.
Contact technical support.