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

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs 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).
IFNET/2/linkdown_active

IFNET/2/linkdown_active

Message

IFNET/2/linkdown_active: The interface status changes. (ifName=[ifName], AdminStatus=[ifAdminStatus], OperStatus=[ifOperStatus], Reason=[Reason], mainIfname=[mainIf])

Description

The interface status changes.

Parameters

Parameter Name Parameter Meaning

ifName

Interface name

AdminStatus

Interface management status

OperStatus

The current interface status

Reason

Alarm cause

mainIfname

Name of the main interface

Possible Causes

Cause 1: Interface physical link is down

Cause 2: LACP negotiation failed

Cause 10: CHAP authentication failed

Cause 11: PAP authentication failed

Cause 12: Keepalive timer expires

Cause 14: EFM DOWN.

Cause 16: The interface is shut down

Cause 17: The link protocol is down

Cause 20: The main interface is down

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

Cause 25: The interface is deleted

Cause 26: BFD session is down

Cause 30: DLDP detect down

Cause 32: VRRP FLOW DOWN

Cause 36: The interface is error down

Cause 37: CRC ERR DOWN

Cause 39: Transceiver speed does not match the speed configured on the port

Cause 40: The port does not support current transceiver

Cause 41: Transceiver does not support the negotiation configuration on the port

Cause 43: The interface is trigger down

Cause 48: CFM DOWN

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. In the case of a sub-interface, you need to check whether a VLAN ID has been configured on the sub-interface and its peer sub-interface.

      • 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. Please Collect alarm information and configuration information, and then 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. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 3: Receive ConfReq packet
    1. Run the display interface command in the system view to check whether the PPP protocol of the remote device is works properly.

      • If the PPP protocol of the remote device works properly, run the display interface command to check the physical link statuses of the devices (including the intermediate device), such as the number of lost packets and error packets. If the physical link statuses are normal but the alarm is not cleared, go to Step 2.
      • If the PPP protocol of the remote device works improperly, contact the engineer responsible for the remote device to rectify the fault. If the fault is rectified but the alarm is not cleared, go to Step 2.

    2. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 4: Receive ConfAck packet
    1. Run the display interface command in the system view to check whether the PPP protocol of the remote device is works properly.

      • If the PPP protocol of the remote device works properly, run the display interface command to check the physical link statuses of the devices (including the intermediate device), such as the number of lost packets and error packets. If the physical link statuses are normal but the alarm is not cleared, go to Step 2.
      • If the PPP protocol of the remote device works improperly, contact the engineer responsible for the remote device to rectify the fault. If the fault is rectified but the alarm is not cleared, go to Step 2.

    2. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 5: Receive Nak packet
    1. Run the display interface command in the system view to check whether the PPP protocol of the remote device is works properly.

      • If the PPP protocol of the remote device works properly, run the display interface command to check the physical link statuses of the devices (including the intermediate device), such as the number of lost packets and error packets. If the physical link statuses are normal but the alarm is not cleared, go to Step 2.
      • If the PPP protocol of the remote device works improperly, contact the engineer responsible for the remote device to rectify the fault. If the fault is rectified but the alarm is not cleared, go to Step 2.

    2. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 6: Receive Term packet
    1. Run the display interface command in the system view to check whether the PPP protocol of the remote device is works properly.

      • If the PPP protocol of the remote device works properly, run the display interface command to check the physical link statuses of the devices (including the intermediate device), such as the number of lost packets and error packets. If the physical link statuses are normal but the alarm is not cleared, go to Step 2.
      • If the PPP protocol of the remote device works improperly, contact the engineer responsible for the remote device to rectify the fault. If the fault is rectified but the alarm is not cleared, go to Step 2.

    2. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 7: Receive TermAck packet
    1. Run the display interface command in the system view to check whether the PPP protocol of the remote device is works properly.

      • If the PPP protocol of the remote device works properly, run the display interface command to check the physical link statuses of the devices (including the intermediate device), such as the number of lost packets and error packets. If the physical link statuses are normal but the alarm is not cleared, go to Step 2.
      • If the PPP protocol of the remote device works improperly, contact the engineer responsible for the remote device to rectify the fault. If the fault is rectified but the alarm is not cleared, go to Step 2.

    2. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 8: Receive CodeRej packet
    1. Run the display interface command in the system view to check whether the PPP protocol of the remote device is works properly.

      • If the PPP protocol of the remote device works properly, run the display interface command to check the physical link statuses of the devices (including the intermediate device), such as the number of lost packets and error packets. If the physical link statuses are normal but the alarm is not cleared, go to Step 2.
      • If the PPP protocol of the remote device works improperly, contact the engineer responsible for the remote device to rectify the fault. If the fault is rectified but the alarm is not cleared, go to Step 2.

    2. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 9: Receive ProtoRej packet
    1. Run the display interface command in the system view to check whether the PPP protocol of the remote device is works properly.

      • If the PPP protocol of the remote device works properly, run the display interface command to check the physical link statuses of the devices (including the intermediate device), such as the number of lost packets and error packets. If the physical link statuses are normal but the alarm is not cleared, go to Step 2.
      • If the PPP protocol of the remote device works improperly, contact the engineer responsible for the remote device to rectify the fault. If the fault is rectified but the alarm is not cleared, go to Step 2.

    2. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 10: 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. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 11: 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. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 12: Keepalive timer expires
    1. Run the display interface command in the system view to check whether the PPP protocol of the remote device is works properly.

      • If the PPP protocol of the remote device works properly, run the display interface command to check the physical link statuses of the devices (including the intermediate device), such as the number of lost packets and error packets. If the physical link statuses are normal but the alarm is not cleared, go to Step 2.
      • If the PPP protocol of the remote device works improperly, contact the engineer responsible for the remote device to rectify the fault. If the fault is rectified but the alarm is not cleared, go to Step 2.

    2. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 14: EFM DOWN
    1. Run the display efm session command in the system view to check whether the EFM state field is displayed as Detect.

      • If the EFM state field is displayed as Detect, go to Step 3.
      • If the EFM state field is not displayed as Detect, go to Step 2.

    2. Run the display efm command in the system view to check whether the EFM enable flag field is displayed as enabled.

      • If the EFM enable flag field is displayed as enabled, recheck the physical link and then check whether the alarm is cleared. If the alarm is not cleared, go to Step 3.
      • If the EFM enable flag field is not displayed as enabled, run the efm enable command in the interface view and system view. Then, check whether the alarm is cleared. If the alarm is not cleared, go to Step 3.

    3. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 15: The tunnel is down
    1. Run the display interface command in the system view to check whether the physical link status of the tunnel interface is Down.

      • If the physical link status of the tunnel interface is 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 the physical link status of the tunnel interface is Up, go to Step 3.

    2. Check whether the physical link of the tunnel 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 of the tunnel interface 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 of the tunnel interface works properly, go to Step 3.

    3. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 16: The interface is shut down
    1. Run the display this command in the interface view to check whether the local or remote interface is shut down. In the case of a sub-interface, you need to check whether a VLAN ID has been configured on the sub-interface and its peer sub-interface.

      • 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. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 17: The link protocol is down
    1. Run the display this command in the interface view to check whether the local or remote interface is shut down. In the case of a sub-interface, you need to check whether a VLAN ID has been configured on the sub-interface and its peer sub-interface.

      • 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. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 20: The main interface is 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. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 22: TThe conditions for the activation of the interface are 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. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 25: The interface is deleted

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

  • Cause 26: BFD session is 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. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 30: DLDP is detected Down.
    1. Check the logs to determine the fault cause.
    2. The possible causes are as follows:

      • The single channel is faulty.

      • The complect channel is faulty.

      • A loopback operation fails.

    3. Check the physical connection.
    4. Properly install physical cables, and run the dldp reset command to reset the DLDP status.

      • The single channel is faulty.

      • The complect channel is faulty.

      • A loopback operation fails.

    5. Wait three times the DLDP period, and run the display dldp command to check the DLDP status.

      • If the DLDP status is Up, go to Step 7.

      • If the DLDP status is Down, go to Step 6.

    6. Please Collect alarm information and configuration information, and then contact technical support personnel.
    7. End.
  • Cause 32: VRRP FLOW DOWN
    1. Run the display vrrp command in the system view to check VRRP information.

      • If the mVRRP group is Down, refer to the VRRP troubleshooting guide and rectify the fault.

      • If the mVRRP group is Up, go to Step 2.

    2. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 37: 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. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 39: Transceiver speed does 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. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 40: The port does not support 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. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 41: 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. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 43: 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 log is cleared. If the log persists, go to Step 4.
    4. Please Collect alarm information and configuration information, and then contact technical support personnel.
  • Cause 48: CFM DOWN
    1. Check the CFM status information.

      • If the CFM status is normal, go to Step 2.

      • If the CFM status is abnormal, see CFM-related troubleshooting.

    2. Please Collect alarm information and configuration information, and then contact technical support personnel.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 114945

Downloads: 85

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