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 12800 and 12800E V200R005C00

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).
MSDP_1.3.6.1.3.92.1.1.0.2 backward

MSDP_1.3.6.1.3.92.1.1.0.2 backward

Description

MSDP peer exit the established state. (RemoteAddr=[RemoteAddr], PeerState=[PeerState], InstanceName=[InstanceName], ExitReason=[ExitReason])

The status of the MSDP peer relationship changes from Established to another one.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

backward

Trap OID

1.3.6.1.3.92.1.1.0.2

Alarm ID

0x08840001

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

MSDP_1.3.6.1.3.92.1.1.0.1 msdpEstablished

Parameters

Parameter Description

RemoteAddr

MSDP peer address

PeerState

Status of the MSDP peer relationship

InstanceName

Instance name

ExitReason

Causes triggering the alarm

VB

VB OID

VB Name

VB Index

1.3.6.1.3.92.1.1.5.1.3

msdpPeerState

msdpPeerRemoteAddress

Impact on the System

The MSDP peer relationship is interrupted or fails to be established, the route is unreachable, and MSDP forwarding services are interrupted.

Possible Causes

Cause 1: HoldTime expired.

Cause 2: Socket error.

Cause 3: Receive invalid TLV.

Cause 4: Receive notification TLV.

Cause 5: User operation.

Procedure

  • Cause 1: HoldTime expired.
    1. Run the ping command to check whether the link between the MSDP peers is up.

      • If the link is up, go to Step 3.
      • If the link is down, go to Step 2.

    2. Run the display ip routing-table command to check whether the unicast route from the local device to the peer device works properly.

      • If the route works properly, go to Step 3.
      • If the route works improperly, you can clear the alarm by rectifying the routing fault.

    3. Run the display msdp peer-status command in the MSDP view of both MSDP peers to check whether the MSDP peer relationship is in the Up state.

      • If the MSDP peer relationship is the Up state, go to Step 4.
      • If the MSDP peer relationship is in the Shutdown state, run the undo shutdown command in the MSDP view of both MSDP peers to clear the alarm.
      • If the MSDP peer relationship is in the Down state, check whether the interface address used for establishing the TCP connection is correct.
        • If the interface address is correct, go to Step 4.
        • If the interface address is incorrect, run the peer peer-address connect-interface interface-type interface-number command in the MSDP view to configure a correct interface address to clear the alarm.
      • If the MSDP peer relationship is in another state, check whether the authentication configurations on both MSDP peers are the same.
        • If the MD5 or Keychain authentication configurations are the same, go to Step 4.
        • If the MD5 or Keychain configurations are different, configure the same MSDP authentication on both MSDP peers to clear the alarm.

    4. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.
  • Cause 2: Socket error.
    1. Run the ping command to check whether the link between the MSDP peers is up.

      • If the link is up, go to Step 3.
      • If the link is down, go to Step 2.

    2. Run the display ip routing-table command to check whether the unicast route from the local device to the peer device works properly.

      • If the route works properly, go to Step 3.
      • If the route works improperly, you can clear the alarm by rectifying the routing fault.

    3. Run the display current-configuration command to check whether multicast is enabled on both MSDP peers.

      • If multicast is enabled on both MSDP peers, go to Step 4.
      • If multicast is not enabled on both MSDP peers, run the multicast routing-enable command to enable multicast to clear the alarm.

    4. Run the display this command in the MSDP view of both MSDP peers to check whether the MSDP peer relationship is configured.

      • If the MSDP peer relationship is configured, go to Step 5.
      • If no MSDP peer relationship is configured, run the peer peer-address connect-interface interface-type interface-number command in the MSDP view to configure the MSDP peer relationship to clear the alarm.

    5. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.
  • Cause 3: Receive invalid TLV.
    1. The MSDP implementations on both peers may be different. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.
  • Cause 4: Receive notification TLV.
    1. Check whether the reset msdp peer command is run in the user view on the peer device.

      • If the command is run, wait till the peer relationship is re-established.
      • If the command is not run, go to Step 2.

    2. Run the display this command in the MSDP view of the peer device to check whether the MSDP peer relationship is configured.

      • If the MSDP peer relationship is configured, go to Step 3.
      • If no MSDP peer relationship is configured, run the peer peer-address connect-interface interface-type interface-number command in the MSDP view to configure the MSDP peer relationship to clear the alarm.

    3. Run the display interface brief command to check whether the shutdown command is run on interfaces connecting the MSDP peers.

      • If the shutdown command is run, run the undo shutdown command in the interface view to clear the alarm.
      • If no shutdown command is run, go to Step 4.

    4. Collect the alarm information, log information, and configuration information, and then contact technical support personnel.

  • Cause 5: User operation.
    1. Check whether the reset msdp peer command is run in the user view.

      • If the command is run, wait till the peer relationship is re-established.
      • If the command is not run, go to Step 2.

    2. Run the display this command in the MSDP view to check whether the MSDP peer relationship is configured.

      • If the MSDP peer relationship is configured, go to Step 3.
      • If no MSDP peer relationship is configured, run the peer peer-address connect-interface interface-type interface-number command in the MSDP view to configure the MSDP peer relationship to clear the alarm.

    3. Run the display interface brief command to check whether the shutdown command is configured on interfaces connecting the MSDP peers.

      • If the shutdown command is run, run the undo shutdown command in the interface view to clear the alarm.
      • If no shutdown command is run, go to Step 4.

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

Document ID: EDOC1100039527

Views: 80216

Downloads: 21

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