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

E9000 Server V100R001 HMM Alarm Handling 19

This document describes E9000 server alarms in terms of the meaning, impact on the system, possible causes, and solutions.
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

LACP

LACP_1.3.6.1.4.1.2011.5.25.41.3.2 hwLacpNegotiateFailed

Description

The member of LAG negotiation failed. (TrunkIndex=[TrunkIndex], PortIfIndex=[PortIfIndex], TrunkId=[TrunkId], TrunkName=[TrunkName], PortName=[PortName], Reason=[ReasonCode])

The LAG negotiation failed.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwLacpNegotiateFailed

Trap OID

1.3.6.1.4.1.2011.5.25.41.3.2

Alarm ID

0x09360000

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

LACP_1.3.6.1.4.1.2011.5.25.41.3.13 hwLacpNegotiateResume

Parameters

Parameter

Description

TrunkIndex

Index of a trunk

PortIfIndex

Index of a member interface

TrunkId

ID of a trunk interface

TrunkName

Name of a trunk interface

PortName

Name of a member interface

Reason

Reason for an unsuccessful negotiation

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.41.1.3.3.1.2

hwTrunkIfID

hwTrunkIndex

1.3.6.1.2.1.31.1.1.1.1

ifName

ifIndex

1.3.6.1.2.1.31.1.1.1.1

ifName

ifIndex

Impact on the System

The link cannot transmit services.

Possible Causes

Cause 1: Interface physical link is down.

Cause 2: No LACP packet was received from the remote end when the timer expired.

Cause 3: Interface is loopback.

Cause 4: Bandwidth of interface is 0.

Cause 5: System ID is not valid.

Cause 6: Remote end can't be aggregated.

Cause 7: Remote end delay to be aggregated.

Cause 8: Local end delay to be aggregated.

Cause 9: Interface negiotation state is unusable.

Cause 10: Interface key of local end is not match with reference port's key.

Cause 11: Number of current active ports is less than least active-number.

Cause 12: Number of current active ports is greater than max active-number.

Cause 13: Local end can't be aggregated.

Cause 14: Interface physical link is downing.

Cause 15: Interface key of remote end is not match with reference port's key.

Cause 16: System ID of remote end is not match with reference port's key.

Cause 17: Remote end can't be synchronized.

Procedure
  • Cause 1: Interface physical link is down.
    1. Run the display this command in the interface view to check whether the local or remote interface is shut down.
      • If either interface is shut down, run the undo shutdown command to enable the interface, and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 2.
      • If no interface is shut down, go to Step 2.
    2. Check whether the physical link of the interface works improperly. That is, check whether the hardware such as the network cable or optical module is disconnected or loosely connected.
      • If the physical link works improperly, you need to correctly connect the physical link and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 3.
      • If the physical link works properly, go to Step 3.
    3. Collect information about configurations, trap messages, and log messages, and then contact technical support personnel.
  • Cause 2: No LACP packet was received from the remote end when the timer expired.
    1. Run the display this command in the interface view to check whether the local or remote interface is shut down.
      • If either interface is shut down, run the undo shutdown command to enable the interface, and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 2.
      • If no interface is shut down, go to Step 2.
    2. Check whether the physical link of the interface works improperly. That is, check whether the hardware such as the network cable or optical module is disconnected or loosely connected.
      • If the physical link works improperly, you need to correctly connect the physical link and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 3.
      • If the physical link works properly, go to Step 3.
    3. Run the display interface eth-trunk command in the system view to check whether a local or remote interface is removed from an Eth-Trunk.
      • If the interface is incorrectly removed from the Eth-Trunk, run the eth-trunk command in the member interface view or the trunkport command in the Eth-Trunk interface view to re-add the interface to the Eth-Trunk, and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 4.
      • If the interface is correctly removed from the Eth-Trunk, go to Step 4.
    4. Collect information about configurations, trap messages, and log messages, and then contact technical support personnel.
  • Cause 3: Interface is loopback.
    1. Run the display this command in the Eth-Trunk member interface view to check whether the loopback internal
      • If the loopback function has been enabled on the member interface, run the undo loopback command to disable the loopback function and then check whether the alarm is cleared.

        If the alarm persists, go to Step 2.

      • If the loopback function is not enabled on the member interface, go to Step 2.
    2. Collect information about trap messages, and then contact technical support personnel.
  • Cause 4: Bandwidth of interface is 0.
    1. Run the display interface eth-trunk command in any view to check whether the Current BW field is 0.
      • If the Current BW field is 0, go to Step 2.
      • If the Current BW field is not 0, go to Step 3.
    2. Run the display this command in the Eth-Trunk member interface view to check whether the member interface is shut down.
      • If the member interface is shut down, run the undo shutdown command in the Eth-Trunk member interface view to activate the interface and then check whether the alarm is cleared.

        If the alarm persists, go to Step 3.

      • If the interface is not shut down, go to Step 3.
    3. Collect information about trap messages, and then contact technical support personnel.
  • Cause 5: System ID is not valid.

    Collect information about trap messages, and then contact technical support personnel.

  • Cause 6: Remote end can't be aggregated.
    1. On the peer device, run the display interface eth-trunk command in any view to check whether member interfaces are added to the Eth-Trunk interface.
      • If no member interfaces are added to the Eth-Trunk interface, run the eth-trunk trunk-id command in the Eth-Trunk interface view to add member interfaces to the Eth-Trunk interface and then check whether the alarm is cleared.

        If the alarm persists, go to Step 2.

      • If member interfaces are added to the Eth-Trunk interface, go to Step 2.
    2. Collect information about trap messages, and then contact technical support personnel.
  • Cause 7: Remote end delay to be aggregated.

    Collect information about trap messages, and then contact technical support personnel.

  • Cause 8: Local end delay to be aggregated.

    Collect information about trap messages, and then contact technical support personnel.

  • Cause 9: Interface negiotation state is unusable.
    1. Run the display this command in the interface view to check whether the local or remote interface is shut down.
      • If either interface is shut down, run the undo shutdown command to enable the interface, and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 2.
      • If no interface is shut down, go to Step 2.
    2. Check whether the physical link of the interface works improperly. That is, check whether the hardware such as the network cable or optical module is disconnected or loosely connected.
      • If the physical link works improperly, you need to correctly connect the physical link and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 3.
      • If the physical link works properly, go to Step 3.
    3. Run the display interface eth-trunk command in the system view to check whether a local or remote interface is removed from an Eth-Trunk.
      • If the interface is incorrectly removed from the Eth-Trunk, run the eth-trunk command in the member interface view or the trunkport command in the Eth-Trunk interface view to re-add the interface to the Eth-Trunk, and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 4.
      • If the interface is correctly removed from the Eth-Trunk, go to Step 4.
    4. Collect information about trap messages, and then contact technical support personnel.
  • Cause 10: Interface key of local end is not match with reference port's key.
    1. On the local device, run the display eth-trunk command in any view to check whether Eth-Trunk member interfaces have the same value in the PortKey field.
      • If Eth-Trunk member interfaces have different values in the PortKey field, run the undo eth-trunk command in the view of the Eth-Trunk member interface with the different PortKey value to remove the member interface from the Eth-Trunk interface and then check whether the alarm is cleared.

        If the alarm persists, go to Step 2.

      • If Eth-Trunk member interfaces have the same value in the PortKey field, go to Step 2.
    2. Collect information about trap messages, and then contact technical support personnel.
  • Cause 11: Number of current active ports is less than least active-number.
    1. Run the display eth-trunk command in any view to check the value of the Least Active-linknumber field.
      • If the value of the Least Active-linknumber field is greater than the number of member interfaces, run the least active-linknumber link-number command to configure the minimum number of Up member links as a value less than the number of member interfaces and then check whether the alarm is cleared.

        If the alarm persists, go to Step 2.

      • If the value of the Least Active-linknumber field is less than the number of member interfaces, go to Step 2.
    2. Collect information about trap messages, and then contact technical support personnel.
  • Cause 12: Number of current active ports is greater than max active-number.
    1. Run the display eth-trunk command in any view to check the value of the Max Active-linknumber field.
      • If the value of the Max Active-linknumber field is less than the number of member interfaces, run the max active-linknumber link-number command to configure the maximum number of Up member links as a value greater than the number of member interfaces and then check whether the alarm is cleared.

        If the alarm persists, go to Step 2.

      • If the value of the Max Active-linknumber field is greater than the number of member interfaces, go to Step 2.
    2. Collect information about trap messages, and then contact technical support personnel.
  • Cause 13: Local end can't be aggregated.
    1. On the local device, run the display interface eth-trunk command in any view to check whether member interfaces are added to the Eth-Trunk interface.
      • If no member interfaces are added to the Eth-Trunk interface, run the eth-trunk trunk-id command in the Eth-Trunk interface view to add member interfaces to the Eth-Trunk interface and then check whether the alarm is cleared.

        If the alarm persists, go to Step 2.

      • If member interfaces are added to the Eth-Trunk interface, go to Step 2.
    2. Collect information about trap messages, and then contact technical support personnel.
  • Cause 14: Interface physical link is downing.
    1. Run the display this command in the interface view to check whether the local or remote interface is shut down.
      • If either interface is shut down, run the undo shutdown command to enable the interface, and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 2.
      • If no interface is shut down, go to Step 2.
    2. Check whether the physical link of the interface works improperly. That is, check whether the hardware such as the network cable or optical module is disconnected or loosely connected.
      • If the physical link works improperly, you need to correctly connect the physical link and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 3.
      • If the physical link works properly, go to Step 3.
    3. Run the display interface eth-trunk command in the system view to check whether a local or remote interface is removed from an Eth-Trunk.
      • If the interface is incorrectly removed from the Eth-Trunk, run the eth-trunk command in the member interface view or the trunkport command in the Eth-Trunk interface view to re-add the interface to the Eth-Trunk, and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 4.
      • If the interface is correctly removed from the Eth-Trunk, go to Step 4.
    4. Collect information about trap messages, and then contact technical support personnel.
  • Cause 15: Interface key of remote end is not match with reference port's key.
    1. On the peer device, run the display eth-trunk command in any view to check whether Eth-Trunk member interfaces have the same value in the PortKey field.
      • If Eth-Trunk member interfaces have different values in the PortKey field, run the undo eth-trunk command in the view of the Eth-Trunk member interface with the different PortKey value to remove the member interface from the Eth-Trunk interface and then check whether the alarm is cleared.

        If the alarm persists, go to Step 2.

      • If Eth-Trunk member interfaces have the same value in the PortKey field, go to Step 2.
    2. Collect information about trap messages, and then contact technical support personnel.
  • Cause 16: System ID of remote end is not match with reference port's key.
    1. On the peer device, run the display eth-trunk command in any view to check whether Eth-Trunk member interfaces have the same value in the System-ID field.
      • If Eth-Trunk member interfaces have different values in the System-ID field, run the undo eth-trunk command in the view of the Eth-Trunk member interface with the different System-ID value to remove the member interface from the Eth-Trunk interface and then check whether the alarm is cleared.

        If the alarm persists, go to Step 2.

      • If Eth-Trunk member interfaces have the same value in the System-ID field, go to Step 2.
    2. Collect information about trap messages, and then contact technical support personnel.
  • Cause 17: Remote end can't be synchronized.

    Collect information about trap messages, and then contact technical support personnel.

LACP_1.3.6.1.4.1.2011.5.25.41.3.3 hwLacpTotalLinkLoss

Description

Link bandwidth lost totally. (TrunkIndex=[TrunkIndex], TrunkIfIndex=[TrunkIfIndex], TrunkId=[TrunkId], TrunkName=[TrunkName], Reason=[Reason])

All the link bandwidths were lost.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwLacpTotalLinkLoss

Trap OID

1.3.6.1.4.1.2011.5.25.41.3.3

Alarm ID

0x09360001

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

LACP_1.3.6.1.4.1.2011.5.25.41.3.14 hwLacpTotalLinkLossResume

Parameters

Parameter

Description

TrunkIndex

Index of a trunk

TrunkIfIndex

Index of a trunk interface

TrunkId

ID of a trunk interface

TrunkName

Name of a trunk interface

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.41.1.3.3.1.2

hwTrunkIfID

hwTrunkIndex

1.3.6.1.2.1.31.1.1.1.1

ifName

ifIndex

Impact on the System

Services are interrupted.

Possible Causes

Cause: No link is selected.

Procedure
  1. Run the display interface brief command to check whether the interface is Down.
  • If so, go to Step 2.
  • If not, go to Step 4.
  1. Run the undo shutdown command to check whether the alarm is cleared.

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

  2. Check whether the physical link is faulty.

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

  3. 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 7.
    • If not, go to Step 6.

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

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

  5. 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 so, go to Step 8.
    • If not, go to Step 7.

  6. Collect information about configurations, trap messages, and log messages, and then contact technical support personnel.
  7. End.

LACP_1.3.6.1.4.1.2011.5.25.41.3.4 hwLacpPartialLinkLoss

Description

Link bandwidth lost partly. (TrunkIndex=[TrunkIndex], TrunkIfIndex=[TrunkIfIndex], TrunkId=[TrunkId], TrunkName=[TrunkName], Reason=[Reason])

Part of the bandwidth of a link was lost.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwLacpPartialLinkLoss

Trap OID

1.3.6.1.4.1.2011.5.25.41.3.4

Alarm ID

0x09360002

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

LACP_1.3.6.1.4.1.2011.5.25.41.3.15 hwLacpPartialLinkLossResume

Parameters

Parameter

Description

TrunkIndex

Index of a trunk

TrunkIfIndex

Index of a trunk interface

TrunkId

ID of a trunk interface

TrunkName

Name of a trunk interface

Reason

indicates the cause for.

Reason why part of the bandwidth of a link was lost

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.41.1.3.3.1.2

hwTrunkIfID

hwTrunkIndex

1.3.6.1.2.1.31.1.1.1.1

ifName

ifIndex

Impact on the System

Part of services were interrupted.

Possible Causes

Cause: The number of the Eth-Trunk member links that were Up was smaller than the lower threshold value that was set, which caused the LAG to become Down. As a result, a PLL trap was generated.

Procedure
  1. Run the display interface brief command to check whether the interface is Down.
  • If so, go to Step 2.
  • If not, go to Step 4.
  1. Run the undo shutdown command to check whether the alarm is cleared.

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

  2. Check whether the physical link is faulty.

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

  3. 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.

  4. Run the display trunkmembership eth-trunk trunk-id command to check whether the lower threshold for Eth-Trunk member links is set in the LAG; whether the number of Eth-Trunk member links that are successfully negotiated is smaller than the lower threshold for the Eth-Trunk member links that can be Up.

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

  5. 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 alarm is cleared.

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

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

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

  7. 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 so, go to Step 10.
    • If not, go to Step 5.

  8. Collect information about configurations, trap messages, and log messages, and then contact technical support personnel.
  9. End.

LACP_1.3.6.1.4.1.2011.5.25.41.3.13 hwLacpNegotiateResume

Description

Link negotiation failure is resumed. (TrunkIndex=[TrunkIndex], PortIfIndex=[PortIfIndex], TrunkId=[TrunkId], TrunkName=[TrunkName], PortName=[PortName], Reason=[ReasonCode])

The member link negotiation succeeded.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwLacpNegotiateResume

Trap OID

1.3.6.1.4.1.2011.5.25.41.3.13

Alarm ID

0x09360000

Alarm Type

communicationsAlarm

Raise or Clear

Clear

Match trap

LACP_1.3.6.1.4.1.2011.5.25.41.3.2 hwLacpNegotiateFailed

Parameters

Parameter

Description

TrunkIndex

Index of a trunk

PortIfIndex

Index of a member interface

TrunkId

ID of a trunk interface

TrunkName

Name of a trunk interface

PortName

Name of a member interface

Reason

Reason why the member link negotiation succeeded

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.41.1.3.3.1.2

hwTrunkIfID

hwTrunkIndex

1.3.6.1.2.1.31.1.1.1.1

ifName

ifIndex

1.3.6.1.2.1.31.1.1.1.1

ifName

ifIndex

Impact on the System

The link can transmit services.

Possible Causes

Cause 1: Member links negotiation succeeded for the first time.

Cause 2: When the member link negotiation failed, the trap hwLacpNegotiateFailed was generated. After the fault was rectified, the trap hwLacpNegotiateResume was generated.

Procedure
  • This alarm message is informational only, and no action is required.

LACP_1.3.6.1.4.1.2011.5.25.41.3.14 hwLacpTotalLinkLossResume

Description

Link bandwidth lost totally is resumed. (TrunkIndex=[TrunkIndex], TrunkIfIndex=[TrunkIfIndex], TrunkId=[TrunkId], TrunkName=[TrunkName], Reason=[Reason])

All the bandwidth of a link is resumed.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwLacpTotalLinkLossResume

Trap OID

1.3.6.1.4.1.2011.5.25.41.3.14

Alarm ID

0x09360001

Alarm Type

communicationsAlarm

Raise or Clear

Clear

Match trap

LACP_1.3.6.1.4.1.2011.5.25.41.3.3 hwLacpTotalLinkLoss

Parameters

Parameter

Description

TrunkIndex

Index of a trunk

TrunkIfIndex

Index of a trunk interface

TrunkId

ID of a trunk interface

TrunkName

Name of a trunk interface

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.41.1.3.3.1.2

hwTrunkIfID

hwTrunkIndex

1.3.6.1.2.1.31.1.1.1.1

ifName

ifIndex

Impact on the System

Services are resumed.

Possible Causes

Cause: The trap hwLacpTotalLinkLoss was generated when no interface was selected. When the fault was rectified, the trap hwLacpTotalLinkLossResume was generated.

Procedure
  • This alarm message is informational only, and no action is required.

LACP_1.3.6.1.4.1.2011.5.25.41.3.15 hwLacpPartialLinkLossResume

Description

Link bandwidth lost partly is resumed. (TrunkIndex=[TrunkIndex], TrunkIfIndex=[TrunkIfIndex], TrunkId=[TrunkId], TrunkName=[TrunkName], Reason=[Reason])

Part of the bandwidth of a link is resumed.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwLacpPartialLinkLossResume

Trap OID

1.3.6.1.4.1.2011.5.25.41.3.15

Alarm ID

0x09360002

Alarm Type

communicationsAlarm

Raise or Clear

Clear

Match trap

LACP_1.3.6.1.4.1.2011.5.25.41.3.4 hwLacpPartialLinkLoss

Parameters

Parameter

Description

TrunkIndex

Index of a trunk

TrunkIfIndex

Index of a trunk interface

TrunkId

ID of a trunk interface

TrunkName

Name of a trunk interface

Reason

Reason why part of the bandwidth of a link is resumed

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.41.1.3.3.1.2

hwTrunkIfID

hwTrunkIndex

1.3.6.1.2.1.31.1.1.1.1

ifName

ifIndex

Impact on the System

Some services resume.

Possible Causes

Cause: Because the number of trunk member links that could go Up through negotiation was below the minimum number of Up member links, the link aggregation group went Down, and thus the trap hwLacpPartialLinkLoss was generated. When the fault was rectified, the trap hwLacpPartialLinkLossResume was generated.

Procedure
  • This alarm message is informational only, and no action is required.
Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 195664

Downloads: 1571

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