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).
DLDP_1.3.6.1.4.1.2011.5.25.173.3.1 hwDldpUnidirectionalLink

DLDP_1.3.6.1.4.1.2011.5.25.173.3.1 hwDldpUnidirectionalLink

Description

Link layer state of the port changed to one way. (IfIndex=[IfIndex], IfName=[IfName], FaultReason=[FaultReason])

DLDP detects a unidirectional link in either single- or multi-peer deployment.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwDldpUnidirectionalLink

Trap OID

1.3.6.1.4.1.2011.5.25.173.3.1

Alarm ID

0x09aa0000

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

DLDP_1.3.6.1.4.1.2011.5.25.173.3.2 hwDldpLinkResume

Parameters

Parameter Description

IfIndex

Interface index

Ifname

Interface name

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.173.2.1

hwDldpTrapInterfaceIndex

None

1.3.6.1.4.1.2011.5.25.173.2.2

hwDldpTrapIfName

None

1.3.6.1.4.1.2011.5.25.173.2.3

hwDldpTrapFaultReason

None

Impact on the System

Services on a unidirectional link cannot run properly.

Possible Causes

  • Cause 1: single-channel. A fiber became defective.

  • Cause 2: complect-channel. Both ends of a fiber were connected to either TX or RX.

  • Cause 3: error-loopback. DLDPDUs were transmitted in a loop.

  • Cause 4: control-packet. The port received control packets (Disable and LinkDown packets) and was closed.

Procedure

  • Cause 1: single-channel. A fiber became defective.
    1. Run the display interface interface-type interface-num command to view statistics about DLDPDUs on the interface. Check whether the physical link between the two directly connected devices is Down based on the statistics.

      • If the physical link is Down, go to Step 2.
      • If the physical link is not Down, go to Step 5.

    2. Check whether the fibers are connected securely to the RX ends.

      • If a fiber is not connected securely to the RX end, go to Step 3.

      • If all fibers are connected securely to the RX ends, go to Step 5.

    3. Re-insert the fiber to the RX end.
    4. Check whether the alarm is cleared.

      • If the alarm persists, go to Step 5.

      • If the alarm is cleared, go to Step 6.

    5. Collect trap, log, and configuration information, and contact technical support personnel.
    6. End.
  • Cause 2: complect-channel. Both ends of a fiber were connected to either TX or RX.
    1. Check whether the fiber is connected properly between two directly connected devices, with one end to TX and the other to RX.

      • If the fiber is not connected properly, go to Step 2.

      • If the fiber is connected properly, go to Step 4.

    2. Connect the fiber properly between two directly connected devices, with one end to TX and the other to RX.
    3. Check whether the alarm is cleared.

      • If the alarm persists, go to Step 4.

      • If the alarm is cleared, go to Step 5.

    4. Collect trap, log, and configuration information, and contact technical support personnel.
    5. End.
  • Cause 3: error-loopback. DLDPDUs were transmitted in a loop.
    1. Check whether the fiber is connected with one end to TX and the other to RX on the same port.

      • If the fiber is connected to the RX and TX ends on the same port, go to Step 2.

      • If the fiber is not connected to the RX and TX ends on the same port, go to Step 4.

    2. Reconnect the fiber with one end to TX on the local port and the other end to RX on the peer port.
    3. Check whether the alarm is cleared.

      • If the alarm persists, go to Step 4.

      • If the alarm is cleared, go to Step 5.

    4. Collect trap, log, and configuration information, and contact technical support personnel.
    5. End.
  • Cause 4: control-packet. The port received control packets (Disable and LinkDown packets) and was closed.
    1. Run the display dldp command to check whether the port is in Disable state.

      • If the port is not in Disable state, go to Step 2.

      • If the port is in Disable state, go to Step 3.

    2. Run the display interface interface-type interface-num command on the peer device to check whether the port on the peer device is physically Down.

      • If the port is Down, go to Step 4.

      • If the port is Up, go to Step 5.

    3. Analyze the causes of the fault for troubleshooting and check whether the alarm is cleared.

      • If the alarm persists, go to Step 5.

      • If the alarm is cleared, go to Step 6.

    4. Check whether the physical link is securely connected.

      • If the physical link is not securely connected, remove and re-insert the fiber to ensure that the physical link is Up. Then go to Step 5.

      • If the physical link is securely connected, go to Step 6.

    5. Check whether the alarm is cleared.

      • If the alarm persists, go to Step 6.

      • If the alarm is cleared, go to Step 7.

    6. Collect trap, log, and configuration information, and contact technical support personnel.
    7. End.
Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 25697

Downloads: 31

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