PIM_1.3.6.1.4.1.2011.5.25.149.4.0.3 hwPimInvalidJoinPrune

Description

PIM/3/INVJP:OID [oid] Invalid Join/Prune message. (GroupMappingOrigin=[integer], GroupMappingAddrType=[integer], GrpAddr=[binary], GrpPfxLen=[gauge], GroupMappingRPAddrType=[integer], RPAddr=[binary], NbrIfIndex=[integer], NbrAddrType=[integer], NbrAddr=[binary], GroupMappingPimMode=[integer], InvJPAddrType=[integer], InvJPOriginAddr=[binary], InvJPGrpAddr=[binary], InvJPRpAddr=[binary], NbrUpTime=[timetick], NbrIfName=[string], InstanceID=[integer], InstanceName=[string])

A switch received an invalid Join/Prune message.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.149.4.0.3	Minor	processingErrorAlarm(4)

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, 6 types of group-RP mappings.
GroupMappingAddrType	Indicates the inetAddressType of mapping group address. The value can be: 1: IPv4 address 2: IPv6 address
GrpAddr	Indicates the group address.
GrpPfxLen	Indicates the mask length of a multicast address.
GroupMappingRPAddrType	Indicates the inetAddressType of an RP address. The value can be: 1: IPv4 address 2: IPv6 address
RPAddr	Indicates the RP address.
NbrIfIndex	Indicates the index of a neighboring interface.
NbrAddrType	Indicates the inetAddressType of a neighbor address. The value can be: 1: IPv4 address 2: IPv6 address
NbrAddr	Indicates the address of a neighbor.
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.
InvJPAddrType	Indicates the inetAddressType of the invalid message address. The value can be: 1: IPv4 address 2: IPv6 address
InvJPOriginAddr	Indicate the source address carried in the invalid message.
InvJPGrpAddr	Indicate the multicast address carried in the invalid message.
InvJPRpAddr	Indicate the RP address carried in the invalid message.
NbrUpTime	Indicates the period during which the neighbor relationship is in the Up state.
NbrIfName	Indicates the name of the neighbor interface.
InstanceID	Indicates the instance ID.
InstanceName	Indicates the instance name.

Impact on the System

After the RP receives an invalid Join or Prune message, information about multicast members fails to reach the RP. This has impact on multicast services.

Possible Causes

1. The RP address carried in the received Join message is different from the address of the RP that serves the group on the switch.

2. The Join/Prune message of the (*.G) or (S,G,RPT) type was received but its group address was in the SSM range.

Procedure

Run the display pim rp-info command to check whether the RP information on the switch that sends the Join or Prune message is the same as RP information on the local switch.
- If so, go to Step 3.
- If not, go to Step 2.
Run the display pim rp-info command to check the RP configured on the switch that sends the Join or Prune message and the local switch is a static RP or a dynamic RP.
- If it is a static RP, run the static-rp rp-address command in the PIM view on the end of sending the Join/Prune message and the local switch to configure correct and identical static RP. Then, go to Step 1.
- If it is a dynamic RP, confirm that no dynamic RP is faulty. Then, go to Step 1.
Run the display this command in the PIM view on the switch that sends the Join or Prune message and the local switch to check whether the ssm-policy basic-acl-number command is configured.
- If so, go to Step 4.
- If not, go to Step 6.
Run the display acl acl-number command on the switch that is configured with the ssm-policy basic-acl-number command to check whether the SSM ranges of the end of sending the Join/Prune message and the local switch are the same.
- If so, go to Step 6.
- If not, go to Step 5.
Configure the ACL specified in the ssm-policy basic-acl-number command on the local switch and the end of sending the Join/Prune message so that the SSM ranges of the end of sending the Join/Prune message and the local switch are the same. Then, check whether the trap persists.
- If so, go to Step 6.
- If not, go to Step 7.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

None