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).
IFNET

IFNET

IFNET_1.3.6.1.6.3.1.1.5.3 linkdown

Description

The interface status changes. (ifName=[ifName], AdminStatus=[ifAdminStatus], OperStatus=[ifOperStatus], Reason=[Reason], mainIfname=[mainIf])

The interface status changes.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

linkdown

Trap OID

1.3.6.1.6.3.1.1.5.3

Alarm ID

0x08520003

Alarm Type

equipmentAlarm

Raise or Clear

Raise

Match trap

IFNET_1.3.6.1.6.3.1.1.5.4 linkup

Parameters

Parameter

Description

ifName

Interface name

AdminStatus

Configured interface status

OperStatus

Current interface status

Reason

Reason for trap generation

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.2.2.1.1

ifIndex

ifIndex

1.3.6.1.2.1.2.2.1.2

ifDescr

ifIndex

Impact on the System

The interface cannot forward packets normally.

Possible Causes

Cause 1: The physical link status of an interface became Down.

Cause 2: LACP negotiation failed.

Cause 3: The CHAP authentication failed.

Cause 4: The PAP authentication failed.

Cause 5: The interface was shut down.

Cause 6: The link protocol is Down.

Cause 7: The main interface is Down.

Cause 8: The conditions for the activation of the interface are not met.

Cause 9: The interface is deleted.

Cause 10: BFD session is down.

Cause 11: VRRP FLOW DOWN.

Cause 12: The interface is error down.

Cause 13: The interface was error Down.

Cause 14: CRC ERR DOWN.

Cause 15: CRC ERR UP.

Cause 16: Transceiver speed did not match the speed configured on the port.

Cause 17: The port did not support the current transceiver.

Cause 18: The transceiver did not support the negotiation configuration on the port.

Cause 19: Cause 42: The interface is trigger down.

Procedure
  • Cause 1: The physical link status of an interface became 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.
      • 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 trap messages and contact technical support personnel.
  • Cause 2: LACP negotiation failed.
    1. Run the display interface command in the system view to check whether the local or remote interface is Down.
      • If either interface is Down, run the undo shutdown command in the interface view, and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 2.
      • If the interface status is Up, go to Step 2.
    2. Run the display interface eth-trunk command in the system view to check whether the number of local and remote interfaces that are added to an Eth-Trunk is greater than the upper threshold for the number of member links.
      • If the number of local and remote interfaces that are added to the Eth-Trunk is greater than the upper threshold for the number of member links, run the max active-linknumber command in the Eth-Trunk interface view to configure a proper upper threshold for the number of member links, and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 4.
      • If the number of local and remote interfaces that are added to the Eth-Trunk is smaller than the upper threshold for the number of member links, go to Step 3.
    3. Run the display interface eth-trunk command in the system view to check whether the number of local and remote interfaces that are added to an Eth-Trunk is smaller than the lower threshold for the number of member links.
      • If the number of local and remote interfaces that are added to the Eth-Trunk is smaller than the lower threshold for the number of member links, run the least active-linknumber command in the Eth-Trunk interface view to configure a proper lower threshold for the number of member links, and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 4.
      • If the number of local and remote interfaces that are added to the Eth-Trunk is smaller than the lower threshold for the number of member links is greater than the lower threshold of member links on the Eth-Trunk interface, go to Step 4.
    4. Collect trap messages and contact technical support personnel.
  • Cause 3: The CHAP authentication failed.
    1. Run the display this command in the interface view to check whether the local end is a server end (authenticating end) or a client end (authenticated end).
      • If the local end is the server end, check whether the user and password configured on the remote end are correct. If they are incorrect, run the local-user password command in the AAA view to re-configure them. Then, check whether the alarm is cleared. If the alarm is not cleared, go to Step 2.
      • If the local end is the client end, run the display this command to check whether the user and password configured on the local end are correct. If they are incorrect, run the local-user password command in the AAA view to re-configure them. Then, check whether the alarm is cleared. If the alarm is not cleared, go to Step 2.
    2. Collect trap messages and contact technical support personnel.
  • Cause 4: The PAP authentication failed.
    1. Run the display this command in the interface view to check whether the local end is a server end (authenticating end) or a client end (authenticated end).
      • If the local end is the server end, check whether the user and password configured on the remote end are correct. If they are incorrect, run the local-user password command in the AAA view to re-configure them. Then, check whether the alarm is cleared. If the alarm is not cleared, go to Step 2.
      • If the local end is the client end, run the display this command to check whether the user and password configured on the local end are correct. If they are incorrect, run the local-user password command in the AAA view to re-configure them. Then, check whether the alarm is cleared. If the alarm is not cleared, go to Step 2.
    2. Collect trap messages and contact technical support personnel.
  • Cause 5: The interface was shut 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.
      • If no interface is shut down, go to Step 2.
    2. Collect trap messages and contact technical support personnel.
  • Cause 6: The link layer protocol became 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.
      • If no interface is shut down, go to Step 2.
    2. Check the cause of the Down status of the link layer protocol.
      • If the link layer protocol can go Up, the fault is rectified.
      • If the link layer protocol still cannot go Up. go to Step 3.
    3. Collect trap messages and contact technical support personnel.
  • Cause 7: The main interface became Down.
    1. Run the display this command in the interface view to check whether the interface on each end is shut down.
      • If the interface is shut down, run the undo shutdown command to enable the interface. After that, check whether the alarm is cleared. If the alarm is not cleared, go to Step 2.
      • If the interface is not 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 trap messages and contact technical support personnel.
  • Cause 8: The conditions for interface activation were not met.
    1. Run the display interface command in the system view to check whether the physical statuses of the local and remote interfaces are Up.
      • If physical statuses of the local and remote interfaces are Down, run the undo shutdown command in the interface view to enable the interface, and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 2.
      • If physical statuses of the local and remote interfaces are Up, go to Step 2.
    2. Run the display eth-trunk command in the system view to check whether the number of trunk member interfaces on the local and remote ends is larger than the max active-linkup number.
      • If the number is larger than the max active-linkup number, it indicates a normal situation in the LACP protocol negotiation process, and no action is required.
      • If the number is smaller than the max active-linkup number, go to Step 3.
    3. Run the display eth-trunk command in the system view to check whether the number of trunk member interfaces on the local and remote ends is smaller than the least active-linkup number.
      • If the number is smaller than the least active-linkup number, run the least active-linknumber command to re-configure the least active-linup number, making it equal to or less than the number of trunk member interfaces.
      • If the number is greater than the least active-linkup number, go to Step 4.
    4. Collect trap messages and contact technical support personnel.
  • Cause 9: The interface was deleted.

    Usually, it was because a user had deleted a logical interface. This alarm message is informational only, and no action is required.

  • Cause 10: The BFD session became Down.
    1. Run the display bfd session command in the system view to check BFD session information.
      • If the interface is bound to a BFD session and the BFD session is in the Down state, refer to the BFD troubleshooting guide and rectify the fault.
      • If the interface is bound to a BFD session and the BFD session is in the Up state, go to Step 2.
    2. Collect trap messages and contact technical support personnel.
  • Cause 11: VRRP FLOW DOWN.
    1. Run the display vrrp command in the system view to check VRRP information.
      • If the mVRRP backup group is Down, refer to the VRRP troubleshooting guide and rectify the fault.
      • If the mVRRP backup group is Up, go to Step 2.
    2. Collect trap messages and contact technical support personnel.
  • Cause 12: The interface is error Down.

    For details about how to troubleshoot the problem, see Troubleshooting Procedure.

  • Cause 13: The interface was error Down.

    For details about how to troubleshoot the problem, see Troubleshooting Procedure.

  • Cause 14: CRC ERR DOWN.
    1. Run the display interface [ interface-type [ interface-number ] | slot slot-number ] command to check the status of the link layer protocol on the interface.
      • If the status of the link layer protocol on the interfaces is Up (Bit-error-detection down), BER exceeds the BER alarm threshold, go to Step 2.
      • If the status of the link layer protocol on the interfaces is Down (Bit-error-detection down), go to Step 3.
    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 trap messages and contact technical support personnel.
  • Cause 15: CRC ERR UP.

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

  • Cause 39: Transceiver speed did not match the speed configured on the port.
    1. Delete the speed configuration on the port and check whether the alarm is cleared. If the alarm persists, 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 trap messages and contact technical support personnel.
  • Cause 16: The port did not support the current transceiver.
    1. Replace the current transceiver with a transceiver that the port supports and check whether the alarm is cleared. If the alarm persists, 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 trap messages and contact technical support personnel.
  • Cause 17: The transceiver did not support the negotiation configuration on the port.
    1. Delete the negotiation configuration on the port and check whether the alarm is cleared. If the alarm persists, 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 trap messages and contact technical support personnel.
  • Cause 18: Transceiver does not support the negotiation configuration on the port
    1. Delete the negotiation configuration on the port and check whether the alarm is cleared. If the alarm persists, 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 trap messages and contact technical support personnel.
  • Cause 19: The interface was triggered down.
    1. Run the display interface [ interface-type [ interface-number ] | slot slot-number ] command and check whether the specified interface status is TRIGGER DOWN.
      • If the interface status is TRIGGER DOWN, go to Step 2.
      • If the interface status is not TRIGGER DOWN, go to Step 4.
    2. Check the cause following the TRIGGER DOWN field and view the associated service, for example, TRIGGER DOWN (MONITOR GROUP).
      • If a cause is displayed, go to Step 3.
      • If no cause is displayed, go to Step 4.
    3. Check and restore the associated service. Check whether the trap is cleared. If the trap persists, go to Step 4.
    4. Collect trap messages and contact technical support personnel.

IFNET_1.3.6.1.6.3.1.1.5.4 linkup

Description

The interface status changes. (ifName=[ifName], AdminStatus=[ifAdminStatus], OperStatus=[ifOperStatus], Reason=[Reason], mainIfname=[mainIfname])

The interface status changes.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

linkup

Trap OID

1.3.6.1.6.3.1.1.5.4

Alarm ID

0x08520003

Alarm Type

equipmentAlarm

Raise or Clear

Clear

Match trap

IFNET_1.3.6.1.6.3.1.1.5.3 linkdown

Parameters

Parameter

Description

ifName

Interface name

AdminStatus

Configured interface status

OperStatus

Current interface status

Reason

Reason for trap generation

mainIfname

Main interface name

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.2.2.1.1

ifIndex

ifIndex

Impact on the System

Traffic will be recovered.

Possible Causes

Cause 1: The link layer protocol became Up.

Cause 2: The physical link became Up.

Cause 3: The conditions for interface activation were met.

Cause 4: The tunnel became Up.

Cause 5: The BFD session became Up.

Cause 6: The EFM session become Up.

Cause 7: VRRP FLOW UP.

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

Document ID: EDOC1000015902

Views: 193111

Downloads: 1567

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