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).
LDP_1.3.6.1.2.1.10.166.4.0.4 Session-Down-MIB

LDP_1.3.6.1.2.1.10.166.4.0.4 Session-Down-MIB

Description

The LDP session status is Down. (PeerLsrId=[PeerLsrId], VrfName=[VrfName], SessionType=[SessionType], IfName=[IfName], SubReason=[SubReason], Reason=[Reason])

The status of the LDP session was Down, and LSPs maintained by the session were deleted.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Alert

Mnemonic Code

Session-Down-MIB

Trap OID

1.3.6.1.2.1.10.166.4.0.4

Alarm ID

0x09020000

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

LDP_1.3.6.1.2.1.10.166.4.0.3 Session-Up-MIB

Parameters

Parameter Description

PeerLsrId

Peer LSR ID

VrfName

VRF for an LDP session

SessionType

LDP session type:
  • Local
  • Remote
  • Local and remote

IfName

Name of an LDP peer interface

SubReason

Detailed cause for an alarm

When an LDP session goes Down because an incorrect packet or a Notify message is received, the specific error packet type or Notify message type is displayed. The typical enumerated can be:

  • 1: Incorrect LDP ID carried in the packet
  • 2: Incorrect version number carried in the packet
  • 3: Incorrect PDU length
  • 5: Incorrect message length
  • 7: Incorrect TLV carried in the packet
  • 9: The received Notify message indicates that the Hello packet times out.
  • 10: The received Notify message indicating a shutdown instruction.
  • 20: The received Notify message indicates the keepalive message times out. When an LDP session goes Down because an incorrect socket is received, an error code is displayed.

When an LDP session goes Down because an incorrect socket is received, the detail error reason or an error code is displayed. For example:

  • 54: TCP connection reset by peer.
  • 60: TCP connection time out.

This field is 0 if the LDP session goes Down due to other causes.

Reason

Alarm cause

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.10.166.4.1.3.3.1.2

mplsLdpSessionState

N/A

1.3.6.1.2.1.10.166.4.1.3.3.1.8

mplsLdpSessionDiscontinuityTime

N/A

1.3.6.1.2.1.10.166.4.1.3.4.1.1

mplsLdpSessionStatsUnknownMesTypeErrors

N/A

1.3.6.1.2.1.10.166.4.1.3.4.1.2

mplsLdpSessionStatsUnknownTlvErrors

N/A

Impact on the System

All the services based on this LDP session will be interrupted.

Possible Causes

  1. The Hello Hold timer of the LDP session expired.
  2. The Keepalive Hold timer of the LDP session expired.
  3. The reset mpls ldp command was run.
  4. GR was enabled for the LDP session.
  5. The value of the Keepalive Hold timer was changed.
  6. The transport address of the LDP session was changed.
  7. An LSR ID of the LDP session was changed.
  8. A Notification message was received to instruct the local LSR to reestablish the LDP session.
  9. LDP failed to establish an LDP session for a long time.
  10. An incorrect protocol message was received.
  11. An incorrect socket was received.
  12. The LDP session was deleted.
  13. Capability was configured for a session.
  14. The configuration of MPLS LDP was deleted.
  15. The configuration of MPLS LDP Remote was deleted.
  16. The label advertisement mode for the session was changed.
  17. The session protection timer expired.
  18. Excessive messages were received from a peer.

Procedure

  1. Run the display mpls ldp session peer-id command to check the LDP session status. Ensure that the value of the parameter peer-id is the same as the value of the PeerLdpId field in the trap information.

    • If the value of the Status field in the command output is Operational, go to Step 2.
    • If no information is displayed or the value of the Status field in the command output is not Operational, go to Step 3.

  2. If the LDP session is already re-established, it indicates that the session may flap. In this case, services may have been interrupted. For further analysis based on the log information, go to Step 19.
  3. Run the display mpls ldp peer peer-id command to check whether there is information about the peer. Ensure that the value of the parameter peer-id is the same as the value of the PeerLdpId field in the trap information.

    • If the command output is displayed, go to Step 4.
    • If no information is displayed, check whether the IfName field in the trap information is null.
      • If so, go to Step 7.
      • If not, go to Step 13.

  4. Run the display mpls ldp session peer-id command repeatedly to check whether the LDP session flaps. Ensure that the value of the parameter peer-id is the same as the value of the PeerLdpId field in the trap information. If the Status field in the command output is sometimes displayed as Operational and sometimes displayed as Nonexistent, or no information is displayed, it indicates that the LDP session flaps.

    • If so, go to Step 5.
    • If not, go to Step 7.

  5. If the LDP session flaps, check whether the configurations are modified frequently.

    • If so, go to Step 6.
    • If not, go to Step 7.

  6. Stop modifying the configurations. Two minutes later, go to Step 18.
  7. Run the display mpls ldp peer peer-id command to check the TransportAddress field in the command output. Ensure that the value of the parameter peer-id is the same as the PeerLdpId field in the trap information. Then, run the display ip routing-table ip-address command to check whether information about the route to the peer exists. Ensure that the value of the parameter ip-address is the same as the value of the TransportAddress field in the display mpls ldp peer peer-id command output.

    • If so, go to Step 10.
    • If not, go to Step 8.

  8. Check whether the IGP route is correctly configured.

    • If OSPF is used as an IGP, run the display current-configuration configuration ospf command in the OSPF view to check whether OSPF has advertised the routes destined for the addresses of loopback interfaces and corresponding interfaces.
      • If so, go to Step 11.
      • If not, go to Step 9.
    • If IS-IS is used as an IGP, run the display this command in the loopback interface view and the corresponding interface view to check whether IS-IS is enabled.
      • If so, go to Step 11.
      • If not, go to Step 9.

  9. Restore the routing protocol configurations, and then check whether the configurations are normal according to Step 8.

    • If so, go to Step 7.
    • If not, go to Step 19.

  10. Check whether the TCP status is normal. Run the display mpls ldp peer peer-id command to check the Peer Transport Address field (remarked as S) and the Peer Discovery Source field. Ensure that the value of the parameter peer-id is the same as the value of the PeerLdpId field in the trap information. Then, run the display mpls ldp interface interface-type interface-number command to check the Transport Address field (remarked as D). Ensure that the value of the parameter interface-type interface-number is the same as the value of the Peer Discovery Source field in the display mpls ldp peer peer-id command output. Run the display tcp status command to check whether the Local Add:port field is displayed as D and whether the Foreign Add:port field is displayed as S. If the Local Add:port field is displayed as D and the Foreign Add:port field is displayed as S, it indicates that the TCP status is normal.

    • If so, go to Step 18.
    • If not, go to Step 11.

  11. Run the ping -a source-ip -c destination-address command for more than 100 times to check whether packet loss occurs. Ensure that the parameter source-ip is the same as the value of the Peer Transport Address field in Step 10 and the value of the parameter destination-address is the same as the value of the Transport Address field in Step 10.

    • If packet loss occurs, go to Step 12.
    • If packet loss does not occur, go to Step 19.

  12. If the link is unstable, it indicates that the line is abnormal or there is heavy traffic on the link. Then, check the link and ensure that the link is stable, and then go to Step 18.
  13. Run the display mpls ldp interface interface-type interface-number command on both ends of the link to check the interface status. Ensure that the value of the parameter interface-type interface-number is the same as the value of the Peer Discovery Source field in Step 10.

    • If the corresponding interface exists, but the Status field is displayed as Inactive, go to Step 16.
    • If the corresponding interface does not exist, go to Step 14.

  14. Run the display this command in the interface view to check whether LDP is enabled.

    • If mpls ldp is displayed in the command output, go to Step 19.
    • If mpls ldp is not displayed in the command output, go to Step 15.

  15. Run the mpls ldp command in the interface view, and then go to Step 18.
  16. Run the display this command in the interface view to check whether the interface is shut down.

    • If shutdown is displayed in the command output, go to Step 17.
    • If shutdown is not displayed in the command output, go to Step 19.

  17. Run the undo shutdown command in the interface view, and then go to Step 18.
  18. If the trap LDPP2P_1.3.6.1.2.1.10.166.4.0.3 mplsLdpSessionUp is displayed, it indicates that the trap LDP_1.3.6.1.2.1.10.166.4.0.4 mplsLdpSessionDown is cleared. Then, go to Step 20.
  19. Collect alarm information and configuration information, and then contact technical support personnel..
  20. End.
Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 17446

Downloads: 25

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