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

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

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_1.3.6.1.4.1.2011.5.25.149.4.0.2 invalid-register

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.2 invalid-register

Description

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], PimInstanceID=[PimInstanceID], PimInstanceName=[PimInstanceName])

PIM received invalid Register messages.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

invalid-register

Trap OID

1.3.6.1.4.1.2011.5.25.149.4.0.2

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the matching trap.

Parameters

Parameter Description

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.

InstanceID

The ID of the instance to which the neighbor interface belongs.

InstanceName

The name of the instance to which the neighbor interface belongs.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.149.4.1.13.1.7

hwPimGroupMappingPimMode

hwPimGroupMappingOrigin;

hwPimGroupMappingAddressType;

hwPimGroupMappingGrpAddress;

hwPimGroupMappingGrpPrefixLength;

hwPimGroupMappingRpAddressType;

hwPimGroupMappingRpAddress;

1.3.6.1.4.1.2011.5.25.149.4.1.33

hwPimInvalidRegisterAddressType

N/A

1.3.6.1.4.1.2011.5.25.149.4.1.34

hwPimInvalidRegisterOrigin

N/A

1.3.6.1.4.1.2011.5.25.149.4.1.35

hwPimInvalidRegisterGroup

N/A

1.3.6.1.4.1.2011.5.25.149.4.1.36

hwPimInvalidRegisterRp

N/A

1.3.6.1.4.1.2011.5.25.149.4.1.57

hwPimInstanceID

N/A

1.3.6.1.4.1.2011.5.25.149.4.1.60

hwPimInstanceName

N/A

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

Cause 1: The interface that received the Register message was not the RP that serves the group address in the Register message.

Cause 2: The group address in the received Register message was within the SSM range specified on the local device.

Procedure

  • Cause 1: The interface that received the Register message was not the RP that serves the group address in the Register message.
    1. Run the display pim rp-info command to check whether the local device functions as the RP to which the group address in the Register message corresponds.

      • If the local device functions as the RP to which the group address in the Register message corresponds, go to Step 2.
      • If the local device does not function as the RP to which the group address in the Register message corresponds, ensure that the configured RP to which the group corresponds on the source DR is the same as that on the local device.

    2. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.
  • Cause 2: The group address in the received Register message was within the SSM range specified on the local device.
    1. Run the display current-configuration command to check whether the group address in the received Register message is within the SSM group address range on the local device.

      • If the group address in the received Register message is within the SSM group address range on the local device, go to Step 2.
      • If the group address in the received Register message is not within the SSM group address range on the local device, configure a same SSM group address range for the group address in the received Register message and the local device.

    2. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.
Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 21616

Downloads: 30

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