Forgot password?
 Register now
Products

Troubleshooting LACP negotiation fails between the switch of Ruijie and other Brand Reply
Troubleshooting LACP negotiation fails between the switch of Ruijie and other Brand
6854 3 2018-4-9 10:14:51
LACP negotiation fails between the switch of Ruijie and other Brand.

0 2018-4-9 18:53:26 View all replies
Possible Causes
1. The switch hardware is faulty, which causes that the switch cannot normally negotiate interface parameters.
2. The duplex modes, Speed and media-type on the two-side switches are not consistent.
3. The switches of other enterprises do not use the standard LACP protocol. For example, the Cisco switches enable PAGP (a proprietary protocol) and therefore cannot form an aggregate link with Ruijie switches.
4. LACP parameters on switches at the two ends are incorrect such as wrong LACP mode. For example, if the switches are configured with the "passive mode-passive mode", you need to manually change it to "active mode-active mode" or "active mode-passive mode".
5. LACPDU packets fail to be received. For example, link faults causepacket loss and then negotiation failure.
6. LACPDU packet negotiation fails because the key fields of the packetsdo not match.
Troubleshooting Procedure
Step 1: Check the interface attributes of the switches at the two ends.
Step 2: Check the LACP configurations of the switches at the two ends.
Step 3: Check the transmission of LACP packets of the switches.
Step 4: Check the LACP negotiation between the switches.
Step 5: Collect fault information and submit cases to Ruijie Service Portal.
Step1: Check the interface attributes of the switches atthe two ends.
1. Run the showinterface XX command to check the interface attributes. Focus on the rates, traffic control policies and medium types of the interfaces, and configure the interfaces to work in the full-duplex mode.
Forexample:
Ruijie#show int gigabitEthernet 1/1
Index(dec):17(hex):11
GigabitEthernet1/1 is DOWN  , line protocol is DOWN   
Hardwareis Broadcom 5464 GigabitEthernet
Interfaceaddress is: no ip address
MTU1500 bytes, BW 1000000 Kbit
  Encapsulation protocol is Bridge, loopbacknot set
  Keepalive interval is 10 sec , set
  Carrier delay is 2 sec
  Rxload is 1/255, Txload is 1/255
  Switchport attributes:
    interface's description:""
admin medium-type is Copper, opermedium-type is Copper
    lastchange time:0 Day: 0 Hour: 1 Minute:22Second
    Priority is 0
admin duplex mode is AUTO, operduplex is Unknown
    admin speed is AUTO, oper speed is Unknown
flow control admin status is OFF, flow control oper status is Unknown
    Storm Control: Broadcast is OFF, Multicastis OFF, Unicast is OFF
  Port-type: access
    Vlan id: 1
  5 minutes input rate 0 bits/sec, 0packets/sec
  5 minutes output rate 0 bits/sec, 0packets/sec
    0 packets input, 0 bytes, 0 no buffer, 0dropped
    Received 0 broadcasts, 0 runts, 0 giants
    0 input errors, 0 CRC, 0 frame, 0 overrun,0 abort
    0 packets output, 0 bytes, 0 underruns , 0dropped
    0 output errors, 0 collisions, 0 interfaceresets

2. Check the log information on the switches during negotiation or run the showlog command to display logs.
1) If the rates at two ends are different, the following information is displayed during negotiation:
*Aug 2621:58:50: %LACP-5-NOTCOMPATIBLE: Interface GigabitEthernet 1/3 is notcompatible with aggregators.(Port speed of GigabitEthernet 1/3 is 100M,GigabitEthernet 1/4 is 1000M).
Thefollowing information is displayed by usingshow lacp summary command:
Ruijie#show lacp summary
SystemId:32768, 001a.a97d.8fc3
Flags:  S - Device is requesting Slow LACPDUs   F - Device is requesting Fast LACPDUs.
A -Device is in active mode.        P -Device is in passive mode.
Aggregateport 1:
Localinformation:
                               LACP port       Oper   Port    Port
Port      Flags    State       Priority        Key    Number  State
----------------------------------------------------------------------
Gi1/3     SP       sups        32768           0x1     0x3    0x44
Gi1/4     SA       bndl        32768           0x1     0x4    0x3d

Partnerinformation:
                    LACP port                  Oper    Port     Port
Port      Flags    Priority      Dev ID       Key    Number   State
---------------------------------------------------------------------
Gi1/3     SP       0             0000.0000.0000   0x0    0x0      0x0
Gi1/4     SA       32768     001a.a916.11b6   0x1    0x14     0x3d

Notes

If the interface status is sups, it means that when the interface link is in the Up state the interface is suspended (displayed in the sups state) through packet negotiation because the peer interface is not enabled with LACP or the interface attributes are different from those of the primary interface. Interfaces in the sups state are not involved in the data packet forwarding of the aggregate group.
2) If the duplex modes are different, the following information is displayed during negotiation:
*Aug 2622:01:51: %LACP-5-NOTCOMPATIBLE: Interface GigabitEthernet 1/3 is notcompatible with aggregators.(GigabitEthernet 1/3 is half duplex.)
The same information as above is displayed by using the following command:
Ruijie#show lacp summary

Step2: Check the LACP configurations of the switches at the two ends.
1. Check the LACP configurations of the two-side aggregate switches. Check whether they use the non-standard LACP protocol and whether their LACP negotiation mode is configured to "passive mode-passive mode".
1) If a Cisco switch is connected, ensure that the Cisco switch is enabled with LACP instead of PAGP (Cisco-proprietary).
2) LACP interfaces have two modes: active and passive. If both the two switch interfaces are configured to work in the passive mode, aggregation cannot be established. To enable aggregation, the two peer interfaces must work both in the active mode, or one is in the active mode and the other in the passive mode.

Step3: Check the transmission of LACP packets on the switches at the two ends.
Debugging operations cause risks (The worst case is to restart the switch for recovery). Perform debugging only after informing customers of the risks and get them accepted. It is recommended debugging at low-trafficperiods (Be more cautious when dealing with core switches). If packet capturingis also required for troubleshooting, remember to collect information by debugging and packet capturing at the same time.


1. Check LACP packet interaction. Mirror the LACP aggregate port to another interface of the switch for packet capturing and then run the debug lacp event and debug lacp packet commands forchecking.
2. LACPDU packets are sent every 30 seconds. Check the transmission ofLACPDU packets on the switches to verify whether the packets are discarded. If the local switch does not send LACPDU packets, the local switch is faulty. If the peer switch does not receive LACPDU packets, the peer switch is faulty or the connected link is faulty.
*Aug 26 22:27:23: %7: [lacp packet]send a lacp pdu to ifx 19 success.
*Aug 2622:27:24: %7: [lacp timer]port 19 hold_while expired
*Aug 2622:27:25: %7: [lacp packet]port[19] rcvd LACP PDU packet
*Aug 2622:27:25: %7: [lacp packet]received a pdu from 19.
*Aug 2622:27:25: %7: Actor   sys pri:32768 sysid:001a.a97d.8fc3 port pri:32768 port no:3 port key:1
*Aug 2622:27:25: %7: Passive  Aggregate In syncCollecting  Distributing   
*Aug 2622:27:25: %7: Partner sys pri:32768 sys id:001a.a916.11b6 port pri:32768 portno:19 port key:1
*Aug 2622:27:25: %7: Active   Aggregate In syncCollecting  Distributing   
*Aug 2622:27:25: %7: port sys pri:32768 sys id:001a.a916.11b6 port pri:32768 portno:19 port key:1
*Aug 2622:27:25: %7: Active   Aggregate In syncCollecting  Distributing   
*Aug 2622:27:25: %7: pdu sys pri:32768 sys id:001a.a916.11b6 port pri:32768 port no:19port key:1
*Aug 2622:27:25: %7: Active   Aggregate In syncCollecting  Distributing   
*Aug 2622:27:25: %7: [lacp timer]start current long while timer for port 19.
*Aug 2622:27:53: %7: [lacp stm]port 19 tx machine ntt.
*Aug 2622:27:53: %7: [lacp timer]port 19 start tx_scheduler.
*Aug 2622:27:53: %7: [lacp stm]port 19 tx machine txd.
*Aug 2622:27:53: %7: [lacp packet]port 19 tx pdu.
*Aug 2622:27:53: %7: [lacp packet]get port 19 default vid 1
*Aug 2622:27:53: %7: Actor   sys pri:32768 sysid:001a.a916.11b6 port pri:32768 port no:19 port key:1
*Aug 2622:27:53: %7: Active   Aggregate In syncCollecting  Distributing   
*Aug 2622:27:53: %7: Partner sys pri:32768 sys id:001a.a97d.8fc3 port pri:32768 portno:3 port key:1
*Aug 2622:27:53: %7: Passive  Aggregate In syncCollecting  Distributing   
*Aug 26 22:27:53: %7: [lacp packet]send a lacp pdu to ifx 19 success.
*Aug 2622:27:54: %7: [lacp timer]port 19 hold_while expired
*Aug 2622:27:57: %7: [lacp packet]port[19] rcvd LACP PDU packet
*Aug 2622:27:57: %7: [lacp packet]received a pdu from 19.
*Aug 2622:27:57: %7: Actor   sys pri:32768 sysid:001a.a97d.8fc3 port pri:32768 port no:3 port key:1
*Aug 2622:27:57: %7: Passive  Aggregate In syncCollecting  Distributing   
*Aug 2622:27:57: %7: Partner sys pri:32768 sys id:001a.a916.11b6 port pri:32768 portno:19 port key:1
*Aug 2622:27:57: %7: Active   Aggregate In syncCollecting  Distributing   
*Aug 2622:27:57: %7: port sys pri:32768 sys id:001a.a916.11b6 port pri:32768 portno:19 port key:1
*Aug 2622:27:57: %7: Active   Aggregate In syncCollecting  Distributing   
*Aug 2622:27:57: %7: pdu sys pri:32768 sys id:001a.a916.11b6 port pri:32768 port no:19port key:1
*Aug 2622:27:57: %7: Active   Aggregate In syncCollecting  Distributing   
*Aug 2622:27:57: %7: [lacp timer]start current long while timer for port 19.
3. If the fault remains, go to Step 4 for furthertroubleshooting.

Step4: Check the LACP negotiation between the switches at the two ends.
1. Analyze the fields in the LACPDU packets captured and check whether the fault is caused by abnormal packets.
1) A normal LACPDU packet is as follows:
A normal LACPDU packet.png

2) An LACPDU packet failing in negotiation is as follows:
Switch1:

An LACPDU packet.png
Switch 2:
switch2.png


Step5: Collect fault information and submit cases toRuijie Service Portal.
If the fault remains after the preceding operations are performed, collect the following fault information and submit cases to Ruijie Service Portal for help.
When a fault occurs, collect log information (pay attention to the time stamp and the time accuracy) for background analysis.
[Devicedebugging information, configuration, hardware models, software versions,device logs and operation logs]
show run
show version
show version slot
show logging
debug lacp event
debug lacp packet
debug lacp stm  //Check the LACP state machine.
debug lacp timer //Checkthe LACP timer.
Debugging operations cause risks (The worst case is to restartthe switch for recovery). Perform debugging only after informing customers ofthe risks and get them accepted. It is recommended debugging at low-traffic periods (Be more cautious when dealing with core switches). If packet capturingis also required for troubleshooting, remember to collect information by debugging and packet capturing at the same time.


0 2022-7-13 12:09:42 View all replies
I regularly visit your website and find a lot of interesting information. There are not only good articles but also great comments. Thank you and hope my page grows bigger and bigger. retro games

0 2022-8-10 21:39:13 View all replies
What is there that can’t get better by marketing directly to gamers? Razer and lifestyle company tumi backpack game have teamed up to create the limited-run line of gaming-themed luggage.
The new capsule-series includes four products: a carry-onbag, backpack, sling bag, and laptop sleeve. The Razer redesign included a new black and neon green look and design inspired by esports. The slideshow below shows you four of the products.

Share this topic to

Cancel

This site contains user submitted content, comments and opinions and is for informational purposes only. Ruijie may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Ruijie can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Ruijie disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Ruijie Community Terms of Use.

More ways to get help: Visit Support Videos, call us via Service Hotline, Facebook or Live Chat.

©2000-2022 Ruijie Networks Co,Ltd