05-08-2020 06:33 AM
Hello
I'm working with a 3750x-48PS switch currently running IOS 15.0(2)SE11. I'm running ports 1-4 as an LACP group with the following configuration:
interface GigabitEthernet1/0/1-4
description xxxxxxxx
channel-protocol lacp
channel-group 1 mode active
Please let me know if any additional information is necessary to help understand my environment.
I've tried to upgrade to 15.2.4E10 and the group stops working. Any suggestions?
Thanks in advance,
Eric
05-08-2020 07:51 AM
Hi,
Can you elaborate on what is the issue?
Also, what does this Porchannel connect to? Does it connect to another switch, servers, storage, etc?.
Can you post the output of "sh run" and "show ether-ch summary" for all devices involved in this configuration?
HTH
05-08-2020 08:21 AM
05-08-2020 10:12 AM
Hi Eric,
Thanks for the info!
1 Po1(SD) LACP Gi1/0/1(I) Gi1/0/2(I) Gi1/0/3(I)
So, the Po is down. Are the physical interfaces in up and up mode "sh ip int bri g1/0/1" same command for other 3.
If they are in up and up mode, can you shut down the po interface and bring it back up.
config t
int po1
sh
no sh
use "sh int po1" to see if the po is up. Can you post the output?
Also, is the po supposed to be configured as access mode or trunk mode as I don't see any config under the interface po1 right now?
HTH
05-08-2020 10:38 AM
I went ahead and booted 15.2 – these are the results:
Here is the results of the sh ip commands for each line:
WentzSW#sh ip int bri g1/0/1
Interface IP-Address OK? Method Status Protocol
GigabitEthernet1/0/1 unassigned YES unset up down
WentzSW#sh ip int bri g1/0/2
Interface IP-Address OK? Method Status Protocol
GigabitEthernet1/0/2 unassigned YES unset up down
WentzSW#sh ip int bri g1/0/3
Interface IP-Address OK? Method Status Protocol
GigabitEthernet1/0/3 unassigned YES unset up down
WentzSW#sh ip int bri g1/0/4
Interface IP-Address OK? Method Status Protocol
GigabitEthernet1/0/4 unassigned YES unset up down
WentzSW#sh int po1
Port-channel1 is down, line protocol is down (notconnect)
Hardware is EtherChannel, address is 0000.0000.0000 (bia 0000.0000.0000)
MTU 1500 bytes, BW 10000 Kbit/sec, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Auto-duplex, Auto-speed, link type is auto, media type is unknown
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
I’m supposed to be configured just as access mode – this is not a trunk. Like I said, it’s a connection to the interface bond (4 NICs) on my Synology file server.
Thanks again
Eric
05-08-2020 11:03 AM
Ok, the Po is down and the interfaces are not part of the Po.
Can you delete the po and also undo the commands under the interfaces and redo them.
no int po1
int g1/0/1
no chann-group 1
no chann protocol lacp
do this for all interface and than start redo them by adding the physical interfaces to the po first.
example
int g1/0/1
chann-group 1 mode active
When you issue above command, this will create po1 for you and no need for the channel protocol lacp command at this time.
do the same for all interfaces.
Once this is done, go to the po interface and do a "no sh" to bring it up
config t
int po1
no sh
Now check the status of the physical interfaces and the po interface.
HTH
05-08-2020 11:04 AM
Here's another interesting set of logging messages. I tried to shutdown and reopen the po1 interface:
WentzSW(config)#int po1
WentzSW(config-if)#sh
WentzSW(config-if)#no sh
WentzSW(config-if)#
*Jan 2 00:35:33.919: %LINK-5-CHANGED: Interface GigabitEthernet1/0/1, changed state to administratively down
*Jan 2 00:35:33.927: %LINK-5-CHANGED: Interface GigabitEthernet1/0/2, changed state to administratively down
*Jan 2 00:35:33.927: %LINK-5-CHANGED: Interface GigabitEthernet1/0/3, changed state to administratively down
*Jan 2 00:35:33.944: %LINK-5-CHANGED: Interface GigabitEthernet1/0/4, changed state to administratively down
*Jan 2 00:35:33.944: %LINK-5-CHANGED: Interface Port-channel1, changed state to administratively down
*Jan 2 00:35:36.200: %LINK-3-UPDOWN: Interface Port-channel1, changed state to down
*Jan 2 00:35:36.200: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down
*Jan 2 00:35:36.209: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/2, changed state to down
*Jan 2 00:35:36.226: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/3, changed state to down
*Jan 2 00:35:36.226: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/4, changed state to down
*Jan 2 00:35:39.069: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up
*Jan 2 00:35:39.162: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/3, changed state to up
*Jan 2 00:35:39.313: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/2, changed state to up
*Jan 2 00:35:39.388: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/4, changed state to up
*Jan 2 00:35:45.243: %EC-5-L3DONTBNDL2: Gi1/0/1 suspended: LACP currently not enabled on the remote port.
*Jan 2 00:35:45.579: %EC-5-L3DONTBNDL2: Gi1/0/2 suspended: LACP currently not enabled on the remote port.
*Jan 2 00:35:45.696: %EC-5-L3DONTBNDL2: Gi1/0/3 suspended: LACP currently not enabled on the remote port.
*Jan 2 00:35:45.797: %EC-5-L3DONTBNDL2: Gi1/0/4 suspended: LACP currently not enabled on the remote port.
I thought I understood configuring the LACP interfaces, obviously not...
05-08-2020 12:07 PM
This is the correct behavior. When you shutdown a po interface, it will also shutdown all the physical interfaces associated with it. The same for "no sh"
HTH
05-08-2020 04:48 PM
I tried the configuration as suggested - still no luck. Here is a log of my session.
I "defaulted" g1/0/1-4 before doing all this and removed the po1 interface.
05-08-2020 04:58 PM
Hi again and thanks. I finally got it running - turns out that I had neglected to establish the LACP on the Synology end - apparently 15.0 was more tolerant of this configuration error. Let's put this to bed. Thanks for your help and time.
Eric
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide