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.3 PimInvalidJoinPrune

PIM-STD_1.3.6.1.2.1.157.0.3 PimInvalidJoinPrune

Description

PIM-STD/3/PUBLIC_INVJP:OID [oid] Invalid Join/Prune message. (GroupMappingOrigin=[integer], GroupMappingAddrType=[integer], GrpAddr=[binary], GrpPfxLen=[gauge], GroupMappingRPAddrType=[integer], RPAddr=[binary], NbrIfIndex=[integer], NbrAddrType=[integer], NbrAddr=[binary], GroupMappingPimMode=[integer], InvJPAddrType=[integer], InvJPOriginAddr=[binary], InvJPGrpAddr=[binary], InvJPRpAddr=[binary], NbrUpTime=[timetick])

An invalid Join or Prune message was received.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.157.0.3

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.

GroupMappingAddrType

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

GroupMappingRPAddrType

Indicates the inetAddressType of an RP address. The value can be:
  • 1: IPv4 address

  • 2: IPv6 address

RPAddr

RP address

NbrIfIndex

Index of a neighbor interface

NbrAddrType

Indicates the inetAddressType of a neighbor address. The value can be:
  • 1: IPv4 address

  • 2: IPv6 address

NbrAddr

Address of a neighbor

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.

InvJPAddrType

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

  • 2: IPv6 address

InvJPOriginAddr

Source address in an invalid packet

InvJPGrpAddr

Group address in an invalid packet

InvJPRpAddr

RP address in an invalid packet

NbrUpTime

Time elapsed since a neighbor relationship was established

Impact on the System

After the RP receives an invalid Join or Prune message, information about multicast members fails to reach the RP.

Possible Causes

Cause 1:

The RP address carried in the received Join message was different from that specified on the switch.

Cause 2:

A Join or Prune message of (*.G) or (S, G, RPT) type was received but its group address was in the SSM range specified on the switch.

Procedure

  1. Run the display pim rp-info command to view information about the RP that serves the group address on the local switch and the device that sends the Join or Prune message. Check whether the RP information on both devices is the same.

    • 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 command on the local switch and the device that sends the Join or Prune message. Proceed with either of the following operations based on a static or dynamic RP:

    • If a static RP is used, run the static-rp(IPv4) rp-address command in the PIM view to configure the same and correct static RP on the local switch and the device that sends the Join or Prune message. Then go to step 1.

    • If a dynamic RP is used, 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 local switch and the device that sends the Join or Prune message. 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 and the device that sends the Join or Prune message. Check whether the SSM ranges on the two devices are the same.

    • 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 to specify an ACL on the local end the same as that configured on the peer end that sends Join/Prune packets. This allows the sending end and the local end to have the same SSM range. Then check whether the trap is cleared.

    • 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: 181614

Downloads: 44

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