No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).



PIM-STD/4/INVALID_REG:PIM receives an invalid register message. (GroupMappingOrigin=[GroupMappingOrigin], GroupMappingAddressType=[GroupMappingAddressType], GrpAddr=[GrpAddr], GrpPfxLen=[GrpPfxLen], GroupMappingRPAddressType=[GroupMappingRPAddressType], RPAddr=[RPAddr], GroupMappingPimMode=[GroupMappingPimMode], InvRegAddressType=[InvRegAddressType], InvRegOriginAddr=[InvRegOriginAddr], InvRegGrpAddr=[InvRegGrpAddr], InvRegRpAddr=[InvRegRpAddr])


PIM received invalid Register messages.


Parameter Name Parameter Meaning
GroupMappingOrigin RP type
GroupMappingAddressType Group address type
GrpAddr Group address of the Registered messages
GrpPfxLen Mask length of the multicast group address
GroupMappingRPAddressType RP address type
RPAddr Address of the RP serving the multicast group
GroupMappingPimMode Current PIM mode
InvRegAddressType Address type of the invalid Register messages
InvRegOriginAddr Source address of the invalid Register messages
InvRegGrpAddr Group address of the invalid Register messages
InvRegRpAddr Destination address of the invalid Register messages

Possible Causes

PIM received invalid Register messages.


  • Check whether the SSM group address ranges configured on the source's DR and the RP are consistent.

    • If the SSM group address ranges are consistent, check whether the RP configurations on the source's DR and the local device generating the log are consistent. If not, correct the RP configurations.
    • If the SSM group address ranges are inconsistent, run the ssm-policy command to reconfigure the SSM group address ranges.

Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 169599

Downloads: 110

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next