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

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.
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_1.3.6.1.4.1.2011.5.25.149.4.0.2 hwPimInvalidRegister

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.2 hwPimInvalidRegister

Description

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 router received an invalid Register message.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.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

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:
  • 1: IPv4 address

  • 2: IPv6 address

RPAddr

Indicates the 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

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.

Impact on the System

After the RP receives an invalid Register message, the source fails to register with the RP. This has impact on multicast services.

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

Procedure

  1. Run the display pim rp-info group-address command on the DR on the source side and the local router to check whether the interface that receives the Register message is the RP to which the group address in the Register message corresponds.

    • If so, go to Step 3.

    • If not, go to Step 2.

  2. Run the display pim rp-info group-address command to check the RP configured on the DR on the source side and the local router is a static RP or a dynamic RP.

    • 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 router 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.

  3. Run the display this command in the PIM view on the DR on the source side and the local router to check whether the ssm-policy { basic-acl-number | acl-name acl-name } command is configured.

    • If so, go to Step 4.

    • If not, go to Step 6.

  4. Run the display acl { name acl-name | acl-number } command on the router that is configured with the ssm-policy { basic-acl-number | acl-name acl-name } command and check whether the SSM ranges of the DR on the source side and the local router are the same.

    • If so, go to Step 6.

    • If not, go to Step 5.

  5. Configure the ACL specified in the ssm-policy { basic-acl-number | acl-name acl-name } command on the local router so that the SSM ranges of the DR on the source side and the local router are the same. Then, check whether the trap persists.

    • If so, go to Step 6.

    • If not, 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-03-06

Document ID: EDOC1100041475

Views: 75325

Downloads: 47

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