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

ME60 Troubleshooting Guide V1.0 (VRPv8)

This document provides the maintenance guide of the device, including daily maintenance, emergence maintenance, and typical troubleshooting.
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).
Eth-Trunk Interface Troubleshooting

Eth-Trunk Interface Troubleshooting

This chapter describes common causes of Eth-Trunk interface faults and provides troubleshooting flowcharts and procedures, alarms, and logs to help identify and rectify these faults.

Eth-Trunk Interfaces Cannot Forward Traffic

This section describes how to troubleshoot Eth-Trunk interfaces' traffic forwarding failures.

Common Causes

Common causes are as follows:

  • Eth-Trunk member interfaces are faulty.
  • Configurations are inconsistent on the Eth-Trunk member interfaces at the two ends of the Eth-Trunk link.
  • The number of Eth-Trunk member interfaces in the Up state is less than the allowed minimum number of active member interfaces.
  • The number of Eth-Trunk member interfaces in the Up state is greater than the allowed maximum number of active member interfaces.
  • Eth-Trunk interfaces in static LACP mode fail to negotiate on member interfaces.
  • BFD used to monitor Eth-Trunk member interfaces is incorrectly configured.
Troubleshooting Flowchart

On the network shown in Figure 4-30, Eth-Trunk interfaces cannot forward traffic.

Figure 4-30 Networking diagram of Eth-Trunk interfaces
NOTE:

Interfaces 1 through 3 in this example are GE 1/0/1, GE 1/0/2, and GE 1/0/3, respectively.



The troubleshooting roadmap is as follows:
  • Check that the Eth-Trunk member interfaces are working properly.
  • Check that the configurations are consistent on the Eth-Trunk member interfaces at the two ends of the Eth-Trunk link.
  • Check that the number of member interfaces in the Up state is greater than the allowed minimum number of active member interfaces.
  • Check that the number of Eth-Trunk member interfaces in the Up state is less than the allowed maximum number of active member interfaces.
  • Check that LACP negotiation succeeds if the Eth-Trunk interface works in static LACP mode.
  • Check that BFD configurations are correct if BFD is configured to monitor Eth-Trunk member interfaces.

Figure 4-31 shows the troubleshooting flowchart.

Figure 4-31 Flowchart for troubleshooting Eth-Trunk interfaces' traffic forwarding failures

Troubleshooting Procedure

Procedure

  1. Check that the Eth-Trunk member interfaces are working properly.

    Run the display eth-trunk 1 command in any view to check the status of the Eth-Trunk interface.

    [HUAWEI] display eth-trunk 1
    Eth-Trunk1's state information is:
    WorkingMode: NORMAL         Hash arithmetic: According to flow
    Least Active-linknumber: 3  Max Bandwidth-affected-linknumber: 16
    Operate status: down        Number Of Up Ports In Trunk: 0
    --------------------------------------------------------------------------------
    PortName                Status      Weight
    GigabitEthernet1/0/1    Down        1
    GigabitEthernet1/0/2    Down        1
    GigabitEthernet1/0/3    Down        1
    

    • If member interfaces are Down, troubleshoot the physical interfaces that are Down. For the detailed troubleshooting procedure, see "Physical Interconnection Troubleshooting".

    • If member interfaces are Up, go to Step 2.

  2. Check that the configurations are consistent on the Eth-Trunk member interfaces at the two ends of the Eth-Trunk link.

    • Run the display eth-trunk 1 command to check configurations about the member interfaces of the Eth-Trunk interface on Device A.

      [~DeviceA] display eth-trunk 1
      Eth-Trunk1's state information is:
      WorkingMode: NORMAL         Hash arithmetic: According to flow
      Least Active-linknumber: 3  Max Bandwidth-affected-linknumber: 16
      Operate status:  down       Number Of Up Ports In Trunk: 3
      --------------------------------------------------------------------------------
      PortName                Status      Weight
      GigabitEthernet1/0/1    Up          1
      GigabitEthernet1/0/2    Up          1
      GigabitEthernet1/0/3    Up          1
      
    • Run the display eth-trunk 1 command to check configurations about the member interfaces of the Eth-Trunk interface on Device B.

      [~DeviceB] display eth-trunk 1
      Eth-Trunk1's state information is:
      WorkingMode: NORMAL         Hash arithmetic: According to flow
      Least Active-linknumber: 3  Max Bandwidth-affected-linknumber: 16
      Operate status:  down       Number Of Up Ports In Trunk: 2
      --------------------------------------------------------------------------------
      PortName                Status      Weight
      GigabitEthernet1/0/1    Up          1
      GigabitEthernet1/0/2    Up          1
      

    • If the number of Eth-Trunk member interfaces on Device A is different from that on Device B, add a required number of Eth-Trunk member interfaces so that the numbers on the two devices are the same.

    • If the number of Eth-Trunk member interfaces on Device A is the same as that on Device B, go to Step 3.

  3. Check that the allowed minimum number of active member interfaces is configured on the Eth-Trunk interfaces on Device A and Device B.

    Run the display eth-trunk 1 command on Device A and Device B to check configurations of Eth-Trunk interfaces.

    [~DeviceA] display eth-trunk 1
    Eth-Trunk1's state information is:
    WorkingMode: NORMAL         Hash arithmetic: According to flow
    Least Active-linknumber: 3  Max Bandwidth-affected-linknumber: 16
    Operate status: down        Number Of Up Ports In Trunk: 2
    --------------------------------------------------------------------------------
    PortName                Status      Weight
    GigabitEthernet1/0/1    Up          1
    GigabitEthernet1/0/2    Up          1
    GigabitEthernet1/0/3    Down        1
    

    This command output shows that the minimum number of active member interfaces is set to 3. However, there are only two member interfaces in the Up state in the Eth-Trunk interface.

    • If the threshold for the minimum number of active member interfaces is configured, but the actual number of active member interfaces is less than the threshold, set the threshold to a proper value.

    • If the threshold for the minimum number of Up member interfaces is not configured, go to Step 4.

  4. Check that the allowed maximum number of active member interfaces is configured on the Eth-Trunk interfaces on Device A and Device B.

    Run the display eth-trunk 1 command on Device A and Device B to check configurations of Eth-Trunk interfaces.

    [~DeviceA] display eth-trunk 1
    Eth-Trunk1's state information is:
    WorkingMode: NORMAL         Hash arithmetic: According to flow
    Least Active-linknumber: 3  Max Bandwidth-affected-linknumber: 3
    Operate status: down        Number Of Up Ports In Trunk: 4
    --------------------------------------------------------------------------------
    PortName                Status      Weight
    GigabitEthernet1/0/1    Up          1
    GigabitEthernet1/0/2    Up          1
    GigabitEthernet1/0/3    Up          1
    GigabitEthernet1/0/4    Up          1
    

    This command output shows that the maximum number of active member interfaces is set to 3. However, there are four member interfaces in the Up state in the Eth-Trunk interface, which causes the Eth-Trunk interface to go Down.

    • If the threshold for the maximum number of active member interfaces is configured, but the actual number of active member interfaces is greater than the threshold, set the threshold to a proper value.

    • If the threshold for the maximum number of Up member interfaces is not configured, go to Step 5.

  5. Check that the Eth-Trunk interfaces on Device A and Device B work in static LACP mode.

    Run the display eth-trunk 1 command on Device A and Device B to check configurations of Eth-Trunk interfaces.

    [~DeviceA] display eth-trunk 1
    Eth-Trunk1's state information is:
    Local:
    LAG ID: 1                   WorkingMode: STATIC
    Preempt Delay: Disabled     Hash arithmetic: According to flow
    System Priority: 32768      System ID: 00e0-fc12-3457
    Least Active-linknumber: 3  Max Active-linknumber: 16
    Operate status: down        Number Of Up Ports In Trunk: 0
    --------------------------------------------------------------------------------
    ActorPortName          Status   PortType PortPri PortNo PortKey PortState Weight
    GigabitEthernet1/0/1   Unselect 1GE      32768   264    305     11100010  1
    GigabitEthernet1/0/2   Unselect 1GE      32768   265    305     11100010  1
    GigabitEthernet1/0/3   Unselect 1GE      32768   266    305     11100011  1
    
    Partner:
    --------------------------------------------------------------------------------
    ActorPortName          SysPri    SystemID  PortPri PortNo  PortKey   PortState
    GigabitEthernet1/0/1   0      00e0-fc12-3458  0      0     0         11100011
    GigabitEthernet1/0/2   0      00e0-fc12-3458  0      0     0         11100011
    GigabitEthernet1/0/3   0      00e0-fc12-3458  0      0     0         11100011
    

    • If Eth-Trunk interfaces are configured to work in static LACP mode, but no physical interface is selected, LACP negotiation fails. Possible causes for unsuccessful LACP negotiation are as follows:
      • Member interfaces are faulty, causing LACP negotiation to time out.

        Troubleshoot the member interfaces.

      • The Eth-Trunk interface at one end of the Eth-Trunk link is configured to work in static LACP mode, whereas the Eth-Trunk interface at the other end of the Eth-Trunk link is not.

        Correct the configurations of the two ends on the Eth-Trunk link to make them consistent.

      If the preceding fault is rectified and LACP negotiation succeeds, the output of the display eth-trunk 1 command is as follows:

      [~DeviceB] display eth-trunk 1
      Eth-Trunk1's state information is:
      Local:
      LAG ID: 1                   WorkingMode: STATIC
      Preempt Delay: Disabled     Hash arithmetic: According to flow
      System Priority: 32768      System ID: 00e0-fc12-3457
      Least Active-linknumber: 3  Max Active-linknumber: 16
      Operate status: up          Number Of Up Ports In Trunk: 3
      --------------------------------------------------------------------------------
      ActorPortName          Status   PortType PortPri PortNo PortKey PortState Weight
      GigabitEthernet1/0/1   Selected 1GE      32768   264    305     11111100  1
      GigabitEthernet1/0/2   Selected 1GE      32768   265    305     11111100  1
      GigabitEthernet1/0/3   Selected 1GE      32768   266    305     11111100  1
      
      Partner:
      --------------------------------------------------------------------------------
      ActorPortName          SysPri    SystemID  PortPri PortNo  PortKey   PortState
      GigabitEthernet1/0/1   32768  00e0-fc12-3456  32768  2056  305       11111100
      GigabitEthernet1/0/2   32768  00e0-fc12-3456  32768  2057  305       11111100
      GigabitEthernet1/0/3   32768  00e0-fc12-3456  32768  2058  305       11111100
      

      If LACP negotiation remains unsuccessfully after the preceding fault is rectified, go to Step 6.

    • If the Eth-Trunk interface is not configured to work in static LACP mode, go to Step 6.

  6. Check that BFD is configured to monitor Eth-Trunk member interfaces.

    To check whether BFD is configured, run the display current-configuration command to check the configuration files of the devices at the two ends of the Eth-Trunk link.

    • If bfd Eth-Trunk bind peer-ip default-ip interface gigabitethernet 1/0/1 is configured, the device has BFD configured.

      Run the display bfd session all for-ip command to check information about a BFD session. The State field indicates the BFD session status.

      • If the BFD session is in the Down state, rectify this fault.
      • If BFD session is in the Up state, go to Step 6.
    • If no device has BFD configured, go to Step 6.

  7. Please contact technical support personnel and provide the following information:

    • Results of this troubleshooting procedure

    • Configuration, log, and alarm files

Relevant Alarms and Logs
Relevant Alarms

None

Relevant Logs

None

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 5241

Downloads: 211

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