PIM_1.3.6.1.4.1.2011.5.25.149.4.0.32 hwPimVrfTypeSGExceed

Trap Buffer Description

The number of existed routing entries exceeded the vpn upper limit. (LimitType=[LimitType], AddressFamily=[AddressFamily], VpnName=[VpnName], CurrentCount=[CurrentCount], LimitCount=[LimitCount],SrcAddr=[SrcAddr], GrpAddr=[GrpAddr])

The number of PIM-SM entries in the VPN instance reached or exceeded the configured limit.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	PIM_VRF_ROUTE_EXCEED
Trap OID	1.3.6.1.4.1.2011.5.25.149.4.0.32
MIB	HUAWEI-PIM-STD-MIB
Alarm ID	0x00F102bb
Alarm Name	PIM_VRF_ROUTE_EXCEED
Alarm Type	qualityOfServiceAlarm
Raise or Clear	Raise
Match trap	PIM_1.3.6.1.4.1.2011.5.25.149.4.0.33 hwPimVrfTypeSGExceedClear

Trap Buffer Parameters

Parameter	Description
LimitType	Type of entry for which an entry number limit takes effect, which is one of the followings: PIM-SM (*, G) entry PIM-SM (S, G) entry
AddressFamily	Address family.
VpnName	VPN name.
CurrentCount	Current count of entries.
LimitCount	Limit count of routing entries.
SrcAddr	Source address.
GrpAddr	Group address.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.149.4.1.74	hwPimNotificationLimitType	-
1.3.6.1.4.1.2011.5.25.149.4.1.62	hwPimNotificationAddressType	-
1.3.6.1.4.1.2011.5.25.149.4.1.60	hwPimInstanceName	-
1.3.6.1.4.1.2011.5.25.149.4.1.72	hwPimNotificationTypeTotalCount	-
1.3.6.1.4.1.2011.5.25.149.4.1.73	hwPimNotificationTypeLimit	-
1.3.6.1.4.1.2011.5.25.149.4.1.69	hwPimNotificationSrcAddr	-
1.3.6.1.4.1.2011.5.25.149.4.1.70	hwPimNotificationGrpAddr	-

Impact on the System

If the number of PIM SM entries reaches the upper limit, new PIM SM entries cannot be created.

Possible Causes

Cause 1: New entries were added, the limit on the number of PIM-SM entries in the VPN instance was changed to a smaller value, or the alarm trigger threshold was changed to a smaller value.
Cause 2: Configuration change

Procedure

Cause 1: New entries were added, the limit on the number of PIM-SM entries in the VPN instance was changed to a smaller value, or the alarm trigger threshold was changed to a smaller value.
1. Check whether AddressFamily is IPv4. If AddressFamily is IPv4, the alarm is triggered in the IPv4 address family of a VPN instance. Perform the following operations:
- a. Run the display multicast pim sm statistics command to check whether the alarm trigger threshold or the number limit is low.
- If the alarm trigger threshold or the number limit is low, go to Step b.
- If the alarm trigger threshold or the number limit is not low, go to Step c.
- b. Run the multicast limit pim sm command to adjust the alarm trigger threshold or the number limit. Then check whether the fault is rectified.
- If the fault is rectified, go to Step d.
- If the fault is not rectified, go to Step c.
- c. Collect alarm information and configuration information, and then contact technical support personnel.
- d. End.
2. Check whether AddressFamily is IPv6. If AddressFamily is IPv6, the alarm is triggered in the IPv6 address family of a VPN instance. Perform the following operations:
- a. Run the display multicast ipv6 pim sm statistics command to check whether the alarm trigger threshold or the number limit is low.
- If the alarm trigger threshold or the number limit is low, go to Step b.
- If the alarm trigger threshold or the number limit is not low, go to Step c.
- b. Run the multicast ipv6 limit pim sm command to adjust the alarm trigger threshold or the number limit. Then check whether the fault is rectified.
- If the fault is rectified, go to Step d.
- If the fault is not rectified, go to Step c.
- c. Collect alarm information and configuration information, and then contact technical support personnel.
- d. End.
Cause 2: Configuration change
The same as Cause 1.