MRM_1.3.6.1.4.1.2011.5.25.149.1.2.17 hwMcastEntryExceed

Trap Buffer Description

Multicast routing total entries of all instances cannot be created because the limit is reached. (LimitType=[LimitType], AddressFamily=[AddressFamily], LimitCount=[LimitCount])

Multicast routing entry cannot be created because the multicast routing entry limit is reached.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	hwVsMcastEntryExceed
Trap OID	1.3.6.1.4.1.2011.5.25.149.1.2.17
MIB	HUAWEI-IPMCAST-MIB
Alarm ID	0x0a592001
Alarm Name	hwMcastEntryExceed
Alarm Type	qualityOfServiceAlarm
Raise or Clear	Raise
Match trap	MRM_1.3.6.1.4.1.2011.5.25.149.1.2.18 hwMcastEntryExceedClear

Trap Buffer Parameters

Parameter	Description
LimitType	Limit type
AddressFamily	Address family
LimitCount	Limit value

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.149.1.1.1.33	hwMcastEntryLimitType	-
1.3.6.1.4.1.2011.5.25.149.1.1.1.34	hwMcastNotificationAddressType	-
1.3.6.1.4.1.2011.5.25.149.1.1.1.35	hwMcastEntryTotalCount	-

Impact on the System

Multicast routing entry cannot be created because the number of multicast routing entries reaches the upper limit.

Possible Causes

Cause 1: A New entry was added, so that the number of multicast routing entries in all instances reached the limit.
Cause 2: The limit on the number of multicast routing entries in all instance was changed to a smaller value, so that the number of multicast routing entries in all instances reached the limit.

Procedure

The procedures of cause 1 and cause 2 are the same.

1. Run the display virtual-system resource command to check whether the m4route resource limit value is low.

If the limit is low, go to Step 2.
If the limit is not low, go to Step 3.

2. Run the resource m4route upper-limit resource-limit command on the VS that the alarm is generated, change the resource limit value to a lager value. Check whether the alarm is cleared.

If the alarm is cleared, go to Step 4.
If the alarm persists, go to Step 3.

3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.