Ruijie Community

Title: Troubleshooting link-aggregation fails or packet forwarding interrupt [Print this page]

Author: Crystal Time: 2018-4-9 10:14
Title: Troubleshooting link-aggregation fails or packet forwarding interrupt

Link aggregation fails or the traffic interrupt after the aggregationsucceeds.

Author: admin Time: 2018-4-9 18:50
Possible Causes

1. The physical link is faulty.

2. LACP negotiation fails.

3. Traffic can’t be load balancing among the ports in the link-aggregation, in the case that ip or mac address didn’t change.

4. The duplex modes (only the port with full-duplex can be aggregated), Speed,media type and Layer2&3 port attribute must be consistent.

Troubleshooting ProcedureStep1: Check whether the configurations are correct.

1. If the local end is configuredas a static aggregate port (AP), the peer end should also be configured as astatic AP.

2. If the local end is configuredwith dynamic LACP aggregation, the peer end should also be configured with dynamic LACP aggregation.

Ruijie#show run int gi x/y //Check the configurations of the aggregate member interfaces.

Step 2: Check whether the aggregate member interfaces havelink faults.

1. Run show interface status command to check whether the aggregate member ports are in the Up state.

2. If not, check the physical links. Ensure that the member interfaces are in the Up state. If conditions permit, you can replace the member ports with other interfaces to exclude physical failure and find out the faulty memberports.

3. After the aggregate member ports are in the “Up” state, check whether the fault is rectified. If the yes, stop further troubleshooting.

4. If the fault remains after the member ports are replaced, collect information and submit cases to Ruijie Service Portal.

Step3: Shut down the member ports one by one and keep only one member ports in the Up state at a time to test whether the communication will recover.

Notes

This operation can be performed only after permitted by customer services because it may interrupt the service connection on the aggregate interfaces. Even though it is approved by customers, it is recommended to perform this operation at low-traffic periods.

Step4: Fault Information Collection

1. Collecting basic information:

--------Collectinformation in the privileged EXEC mode (ruijie#)----------

show aggregateport aggregate x load-balance

//Fill in the aggregate interface number based on the actual conditions.For example, if the aggregate interface number is 2, the command is show aggregateport 2 load-balance.

show aggregate port aggregation x summary

//Fill in the aggregate interface number based on the actual conditions.For example, if the aggregate interface number is 2, the command is show aggregateport 2 summary.

show running-config

show int gi x/y

r//Fill in the member interface number based on the actual conditions. Forexample, the command can be show intg0/1.

show int ag aggregation x

//Fill in the aggregate interface number based on the actual conditions.For example, if the aggregate interface number is 2, the command is show int ag 2.

Show lacp summary

show log

2. Collecting debugging information (Ifthere is no output with Telnet used, use the Console port to access the switchfor information collection.)

ruijie>enable

ruijie#terminal monitor

ruijie#config t

ruijie(config)#logging on

ruijie(config)#logging console

ruijie(config)#exit

Welcome to Ruijie Community (https://community.ruijienetworks.com/)