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

Reminder

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

upgrade

Alarm Handling

S9300, S9300E, and S9300X V200R010C00

This document provides the explanations, causes, and recommended actions of alarms 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_1.3.6.1.2.1.157.0.2 pimInvalidRegister

PIM-STD_1.3.6.1.2.1.157.0.2 pimInvalidRegister

Description

PIM-STD/3/PUBLIC_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])

An invalid Register message was received.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.157.0.2

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, 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

GrpAddr

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.

InvRegAddressType

Indicates the inetAddressType of the invalid Register message address. The value can be:
  • 1: IPv4 address

  • 2: IPv6 address

InvRegOriginAddr

Source address in the Register packet

InvRegGrpAddr

Group address in the Register packet

InvRegRpAddr

RP address in the Register packet

Impact on the System

After the RP receives an invalid Register message, the source that sends the message fails to register with the RP.

Possible Causes

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 router's RP address was different from that contained in the Register message.

Procedure

  1. Run the display pim rp-info group-address command to view information about the RP that serves the group address on the source-side DR and local switch. Check whether the RP information on the source-side DR is the same as that on the local switch.

    • If the two devices have the same RP information, go to step 3.

    • If the two devices have different RP information, go to step 2.

  2. Run the display pim rp-info group-address command to check the RP configured on the source-side DR and the local switch. Proceed with either of the following operations based on a static or dynamic RP:

    • If a static RP is configured, run the static-rp rp-address preferred command in the PIM view to configure the same and correct static RP on the source-side DR and local switch. The preferred parameter is configured to preferentially select the static RP. Then go to step 1.

    • If a dynamic RP is configured, rectify the fault in the dynamic RP. After the fault is rectified, go to step 1.

  3. Run the display this command in PIM view on the source-side DR and the local switch. Check whether the ssm-policy { basic-acl-number | acl-name acl-name } command has been run.

    • If the command has been run, go to step 4.

    • If the command has not been run, go to step 6.

  4. Run the display acl { name acl-name | acl-number } command on the local switch. Check whether the SSM range on the source-side DR is the same as that on the local switch.

    • If the SSM ranges are the same, go to step 6.

    • If the SSM ranges are different, go to step 5.

  5. Run the ssm-policy { basic-acl-number | acl-name acl-name } command on the local switch to specify an ACL the same as that on the source-side DR. After that, the local switch and the source-side DR have the same SSM range. Check whether the trap is displayed.

    • If the trap is displayed, go to step 6.

    • If the trap is cleared, go to step 7.

  6. Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

None

Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000142054

Views: 192501

Downloads: 44

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next