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

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