PIM-STD_1.3.6.1.2.1.157.0.4 PimRPMappingChange

Description

PIM-STD/3/PUBLIC_RPCHG:OID [oid] RP changed. (GroupMappingOrigin=[integer], GroupMappingAddressType=[integer], szGrpAddr=[binary], GrpPfxLen=[gauge], GroupMappingRPAddressType=[integer], RPAddr=[binary], GroupMappingPimMode=[integer], Precedence=[gauge])

Information about an RP that serves a specific multicast group on a network was changed. The trap is not displayed when an RP is added or deleted.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.2.1.157.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	Group address
GrpPfxLen	Mask length of the multicast group address
GroupMappingRPAddressType	Indicates the inetAddressType of an RP address. The value can be: 1: IPv4 address 2: IPv6 address
RPAddr	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

Impact on the System

The change of the RP causes the source and multicast members fail to communicate. This will adversely affect multicast services.

Possible Causes

Cause 1:

A static RP was reconfigured and the preferred parameter was configured to preferentially select the static RP.

Cause 2:

A C-RP with a higher priority than the existing ones existed.

Procedure

Check whether RP information can be changed based on the network plan.
- If RP information can be changed, go to step 5.
- If the RP information cannot be changed, go to step 2.
Run the display pim rp-info group-address command to check whether the RP on the network is a static RP or a dynamic RP.
- If a static RP is configured, run the distatic-rp rp-address preferred command in the PIM view to configure a static PR and allow the static PR to be preferentially selected. Then go to step 3.
- If a dynamic RP is configured, run the c-rp priority priority or c-rp interface-type interface-number priority priority command in the PIM view on the switch that is expected to be a C-RP to set a smaller priority value to increase the priority. Then go to step 3.
Run the display pim rp-info group-address command to check whether RP information is identical with the networking plan.
- If RP information is identical with the networking plan, go to step 5.
- If RP information is not identical with the networking plan, go to step 4.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

None