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_1.3.6.1.4.1.2011.5.25.149.4.0.1 hwPimNeighborLoss

PIM_1.3.6.1.4.1.2011.5.25.149.4.0.1 hwPimNeighborLoss

Description

PIM/2/NBRLOSS:OID [oid] PIM neighbor loss. (NbrIntIndex=[integer], NbrAddrType=[integer], NbrAddr=[binary], NbrUpTime=[timetick], NbrIntName=[string], InstanceID=[integer], InstanceName=[string], NeighborLossReason=[integer])

The PIM neighbor was lost.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.149.4.0.1

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

NbrIntIndex

Indicates the index of a neighbor.

NbrAddrType

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

  • 2: IPv6 address

NbrAddr

Indicates the address of a neighbor.

NbrUpTime

Indicates the period during which the neighbor relationship is in the Up state.

NbrIntName

Indicates the name of the neighbor interface.

InstanceID

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

InstanceName

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

NeighborLossReason

Indicates a possible cause for PIM neighbor loss.
  • 1: The neighbor relationship expires.

  • 7: Hello messages with the holdtime 0 are received.

  • 8: The BFD session goes Down.

  • 9: A user manually tears down the PIM neighbor relationship.

Impact on the System

The PIM neighbor is disconnected, which has impact on multicast services.

Possible Causes

1. The timer of the PIM neighbor expired.

2. The switch received a Hello message with the Holdtime value being 0.

Procedure

  1. Run the display pim interface interface-type interface-number command on the neighboring switch to check whether PIM is enabled on the interface that connects the local switch.

    • If so, go to Step 3.

    • If not, go to Step 2.

  2. Run the pim dm or pim sm command on the interface that connects the local switch to enable PIM. Run the display pim neighbor neighbor-address command on the neighboring switch to check whether the PIM neighbor of the local switch is established.

    • If so, go to Step 6.

    • If not, go to Step 3.

  3. Run the display ip routing-table ip-address command on the neighboring switch to check whether the route to the local switch exists.

    • If so, go to Step 5.

    • If not, go to Step 4.

  4. Confirm that no unicast route is faulty. Run the display pim neighbor neighbor-address command on the neighboring switch to check whether the PIM neighborship is established between the local switch and its neighbor.

    • If so, go to Step 6.

    • If not, go to Step 5.

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

Related Information

None

Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000142054

Views: 180729

Downloads: 44

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