PIM_1.3.6.1.4.1.2011.5.25.149.4.0.4 hwPimRpMappingChange

Description

PIM/3/RPCHG:OID [oid] RP changed. (GroupMappingOrigin=[integer], GroupMappingAddressType=[integer], szGrpAddr=[binary], GrpPfxLen=[gauge], GroupMappingRPAddressType=[integer], RPAddr=[binary], GroupMappingPimMode=[integer], Precedence=[gauge], InstanceID=[integer], InstanceName=[string])

For a group, there is only one RP in the entire network. The trap was generated when the entries of a group existed on the switch and RP information about the group changed.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.149.4.0.4	Minor	communicationsAlarm(2)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
GroupMappingOrigin	Indicates the type of a group-RP mapping. 1: mapping between an RP and a link-local or unreachable group address 2: mapping between a local static RP and a group 3: mapping between an RP and a group address in the local SSM address range 4: mapping learned through the PIM BSR mechanism 5: mapping learned through the auto-RP mechanism 6: mapping learned through the embedded-RP mechanism 7: mapping learned through other mechanisms NOTE: Currently, the device supports only the 2, 4, 5, 6 types of group-RP mappings.
GroupMappingAddressType	Indicates the inetAddressType of mapping group address. The value can be: 1: IPv4 address 2: IPv6 address
szGrpAddr	Indicates the address of a multicast group.
GrpPfxLen	Indicates the mask length of a multicast address.
GroupMappingRPAddressType	Indicates the inetAddressType of an RP address. The value can be: 1: IPv4 address 2: IPv6 address
RPAddr	Indicates an RP address.
GroupMappingPimMode	Indicates the group mapping mode. 1: mapping without groups 2: PIM-SSM 3: PIM-ASM 4: BIDR-PIM 5: PIM-DM 6: others NOTE: Currently, the device supports only the 2, 3, and 5 modes.
Precedence	Indicates the preference of the mapping mode. 0: embedded-RP 1: auto-RP 2: PIM BSR 3: static RP 4: others
InstanceID	Indicates the instance ID.
InstanceName	Indicates the instance name.

Impact on the System

The change of the RP causes the source and multicast members to fail to communicate. This has impact on multicast services.

Possible Causes

1. A static RP was re-configured in the network. The command used to configure static RP contains preferred, the static RP is preferred.

2. A C-RP with higher priority emerged in the network.

Procedure

Check whether RP information is expected to change.
- If so, go to Step 5.
- If not, go to Step 2.
Run the display pim rp-info group-address command to check whether the RP in the network is a static RP or a dynamic RP.
- If it is a static RP, run the static-rp rp-address preferred command in the PIM view to configure the original RP as a static RP on every switch. The static RP is preferred. Then, go to Step 3.
- If it is a dynamic RP, run the c-rp priority priority or c-rp interface-type interface-number priority priority command in the PIM view to reduce the priority value of the C-RP, that is, increase the priority of the C-RP on the switch that is expected to serve as the RP. Then, go to Step 3.
Run the display pim rp-info group-address command to check whether RP information meets requirements.
- If so, go to Step 5.
- If not, go to Step 4.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

None