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

S600-E 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).
LACP_1.3.6.1.4.1.2011.5.25.41.3.3 hwLacpTotalLinkLoss

LACP_1.3.6.1.4.1.2011.5.25.41.3.3 hwLacpTotalLinkLoss

Description

LACP/2/TLL:OID [oid] Link bandwidth lost totally. (TrunkIndex=[INTEGER], TrunkIfIndex=[INTEGER], TrunkId=[INTEGER], TrunkName=[OCTET])

All the link bandwidths were lost.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.3.3 Major operationalViolation(8)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

TrunkIndex

Indicates the index of a Trunk.

TrunkIfIndex

The value of this object identifies the index of a Trunk interface.

TrunkId

Indicates the ID of a Trunk interface.

TrunkName

Indicates the name of a Trunk interface.

Impact on the System

Services are interrupted.

Possible Causes

A TLL trap was generated when all links between two devices were disconnected and packets failed to be forwarded.

Procedure

  1. Run the display interface brief command to check whether the interface is Down.

    • If the alarm is cleared, go to Step 2

    • If the alarm is not cleared, go to Step 4

  2. Run the undo shutdown command to check whether the alarm is cleared.

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

    • If the alarm is not cleared, go to Step 3.

  3. Check whether the physical link is faulty.

    • If so, go to Step 7.

    • If not, go to Step 4.

  4. Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ] ] command to check whether there are member interfaces in the LAG.

    • If so, go to Step 5.

    • If not, go to Step 8.

  5. Run the display trunkmembership eth-trunk trunk-id command to check whether the lower threshold of Eth-Trunk member links that can be Up in the LAG is correctly set. (An incorrect lower threshold causes the negotiation failure between the Eth-Trunk member interfaces.)

    • If so, go to Step 6.

    • If not, go to Step 9.

  6. In the Eth-Trunk interface view, run the least active-linknumber link-number command to correctly set the lower threshold of Trunk member links that can be Up. Then, check whether the fault is rectified.

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

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

  7. Repair the physical link and then check whether the alarm is cleared.

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

    • If the alarm is not cleared, go to Step 4.

  8. Run the eth-trunk trunk-id command in the interface view and add the current Ethernet interface to the Eth-Trunk interface as required. Then, check whether the alarm is cleared.

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

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

  9. Collect alarm information and configuration information, and then contact technical support personnel.
  10. End.

Related Information

None.

Translation
Download
Updated: 2019-04-18

Document ID: EDOC1000141873

Views: 113659

Downloads: 14

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