IFNET_1.3.6.1.6.3.1.1.5.3 linkdown

Trap Buffer Description

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

The interface status changes.

Trap Attributes

Trap Buffer Parameters

VB Parameters

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.

  • In the case of a sub-interface, run the vlan-type dot1q command on the sub-interface to configure a correct VLAN ID, 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. Collect alarm information and configuration information, and then contact technical support personnel.

• Cause 13: The PVC is Down

  1. Run the display this command in the sub-interface view to check whether the interfaces on both ends are shut down.

  • If the interfaces are shut down, go to Step 4.
  • If the interfaces are not shut down, go to Step 2.

  2. Run the display fr interface command in the system view to check the physical and protocol status of the main interface.

  • If the physical status of the main interface is Down, go to Step 5.
  • If the physical status of the main interface is Up but the protocol status is Down, go to Step 6.
  • If the both the physical and protocol status of the main interface is Up, go to Step 3.

  3. Ask engineers of the peer end to check whether the PVC status is Active.

  • If the PVC status on the peer end is Active, go to Step 7.
  • If the PVC status on the peer end is Inactive, go to Step 8.

  4. Run the undo shutdown command to start the sub-interface.

  5. Check the physical connection of the main interface.

  6. Check the LMI configurations.

  7. Collect alarm information and configuration information, and then contact technical support personnel.

  8. End.

• 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 EFM enable flag is not enabled, run the efm enable command in the system viedw and interface view according to the configuration guide. Then check whether the alarm is cleared. If the alarm persists, go to Step 3.

  3. 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 tunnel link is Down.

  • If the physical status of the interface is Down, run the undo shutdown command to enable the interface and check whether the alarm is cleared. If the alarm persists, go to Step 2.
  • If the physical status of the interface is Up, go to Step 3.

  2. Check whether the physical connection is normal, including whether the network cable and optical module are loose or disconnected.

  • If the physical link is abnormal, reconnect the physical link and check whether the alarm is cleared. If the alarm persists, go to Step 3.
  • If the physical link works properly, go to step 3.

  3. Run the display this command in the interface view to check whether MPLS TE and MPLS RSVP-TE are configured on the interface and node of the tunnel.

  • If MPLS TE and MPLS RSVP-TE are configured on the tunnel interface and node, go to Step 4.
  • If MPLS TE or MPLS RSVP-TE is not configured on the tunnel interface or node, run the mpls te and mpls rsvp-te commands in the MPLS view to reconfigure the tunnel interface and node, and then check whether the alarm is cleared. If the alarm persists, go to Step 4.

  4. Collect alarm and configuration information and contact technical support engineers.

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

  • In the case of a sub-interface, run the vlan-type dot1q command on the sub-interface to configure a correct VLAN ID, 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. 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.

  • In the case of a sub-interface, run the vlan-type dot1q command on the sub-interface to configure a correct VLAN ID, 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 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 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. Collect alarm information and configuration information, and then contact technical support personnel.

• Cause 22: The 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 least active-linkup number.

  • If the number of trunk member interfaces on the local and remote ends is less than least active-linkup number, run the least active-linknumber command to change least active-linkup number so that the former is greater than or equal to the latter.
  • If the number of trunk member interfaces on the local and remote ends is greater than least active-linkup number, go to Step 4.

  4. 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. Collect alarm information and configuration information, and then contact technical support personnel.

• Cause 30: DLDP detect down

  1. Check the traps to determine the fault cause.

  2. Check the possible causes.

• Cause 32: 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 alarm information and configuration information, and then contact technical support personnel.

• Cause 34: VE FLOW DOWN

  1. Run the display interface virtual-ethernet ve-number command to check VE interface information.

  • If the VE interface is Down, go to Step 2.
  • If the VE interface is Up, go to Step 4.

  2. Collect the main interface configuration.

  • If it matches the L2VPN termination interface, see the L2VPN troubleshooting guide and rectify the fault.
  • If it matches the L3VPN termination interface, go to Step 3.

  3. Collect the L3VPN termination sub-interface configuration, and check whether the sub-interface has a VLAN ID and IPv4 address configured.

  • If the configuration is not correct, go to Step 4.
  • If the configuration is correct but the alarm persists, go to Step 4.

  4. Collect alarm information and configuration information, and then contact technical support personnel.

• Cause 36: The interface is error down

  For details about handling suggestions, see "ERROR-DOWN_1.3.6.1.4.1.2011.5.25.257.2.1 hwErrordown" Handling Procedure.

• 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. 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. 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. 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. Collect alarm information and configuration information, and then contact technical support personnel.

• Cause 43: The interface is trigger 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 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.