PIM/3/INVREG:OID [oid] Invalid Register message. (GroupMappingOrigin=[integer], GroupMappingAddressType=[integer], GrpAddr=[binary], GrpPfxLen=[gauge], GroupMappingRPAddressType=[integer], RPAddr=[binary], GroupMappingPimMode=[integer], InvRegAddressType=[integer], InvRegOriginAddr=[binary], InvRegGrpAddr=[binary], InvRegRpAddr=[binary], InstanceID=[integer], InstanceName=[string])
A switch received an invalid Register message.
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.149.4.0.2 |
Minor |
processingErrorAlarm(4) |
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
GroupMappingOrigin |
Indicates the type of a group-RP mapping.
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:
|
GrpAddr |
Indicates the group address. |
GrpPfxLen |
Indicates the mask length of a multicast address. |
GroupMappingRPAddressType |
Indicates the inetAddressType of an RP address.
The value can be:
|
RPAddr |
Indicates the RP address. |
GroupMappingPimMode |
Indicates the group mapping mode.
NOTE:
Currently, the device supports only the
2, 3, and 5 modes. |
InvRegAddressType |
Indicates the inetAddressType of the invalid
Register message address. The value can be:
|
InvRegOriginAddr |
Indicates the source address carried in the invalid Register message. |
InvRegGrpAddr |
Indicates the multicast address carried in the invalid Register message. |
InvRegRpAddr |
Indicates the RP address carried in the invalid Register message. |
InstanceID |
Indicates the instance ID. |
InstanceName |
Indicates the instance name. |
After the RP receives an invalid Register message, the source fails to register with the RP. This has impact on multicast services.
An (S, G) entry was not created for a received Register message, the group address in the Register message was in the ASM address range, and the RP address on the switch was different from that contained in the Register message.
If so, go to Step 3.
If not, go to Step 2.
If it is a static RP, run the static-rp rp-address preferred command in the PIM view on the DR on the source side and the local switch to configure correct and identical static RP. The static RP is preferred. Then, go to Step 1.
If it is a dynamic RP, confirm whether no dynamic RP is faulty. Then, go to Step 1.
If so, go to Step 4.
If not, go to Step 6.
If so, go to Step 6.
If not, go to Step 5.
If so, go to Step 6.
If not, go to Step 7.