Unsolved

1 Rookie

 • 

21 Posts

18

October 27th, 2025 17:44

OS10.6 LACP

We have a pair of S4128T switches that connect our VxRails and their iDRACs. Someone else programmed the switches, and there is no documentation. The open ports all look like this:

interface ethernet1/1/15
 description "Servers VLAN 13"
 no shutdown
 switchport access vlan 13
 flowcontrol receive on

I have a Debian 13 server with two NICs, which I am trying to connect to both switches via LACP.  They need to be trunked. My understanding is I have to create a port-channel, add the interfaces, and make them active, with the same details on both switches.

Everything looks good on both the server and switches, but there is no connectivity and I cannot ping the gateway. Only when I leave the switch programming as is and the server's NICs unmanaged, can I connect.

Can someone point me in the right direction? It goes without saying that I can't disrupt the VxRails. Thanks

Moderator

 • 

2.9K Posts

October 28th, 2025 10:51

Hi,

I would check on switch side below ones.

 

Create a port-channel and add your two switch ports to it.

Set the port-channel to trunk mode, and allow VLAN 13.

Enable LACP active mode on the physical interfaces.

 

But i'm not sure debian side. If the switches are not stacked or in a VLT domain, LACP across two switches might be won’t work. In that case, you can use active-backup mode instead of LACP. Make sure VLAN 13 is tagged on the trunk and matches on both ends. 

 

 

1 Rookie

 • 

21 Posts

October 28th, 2025 13:33

I should have mentioned there is a VLT domain. In any event, I tried active-backup and that didn't work, either.

Domain ID                              : 100
Unit ID                                : 2
Role                                   : primary
Version                                : 3.1
Local System MAC address               : 50:9a:4c:ee:5b:30
Role priority                          : 1000
VLT MAC address                        : 00:00:00:00:00:01
IP address                             : fda5:74c8:b79e:1::2
Delay-Restore timer                    : 90 seconds
Peer-Routing                           : Enabled
Peer-Routing-Timeout timer             : 0 seconds
Multicast peer-routing timer           : 300 seconds
VLTi Link Status
    port-channel1000                   : up

VLT Peer Unit ID    System MAC Address    Status    IP Address             Version
----------------------------------------------------------------------------------
  1                 50:9a:4c:ee:5d:30      up       fda5:74c8:b79e:1::1     3.1

Moderator

 • 

2.9K Posts

October 28th, 2025 13:55

Since you're using VLT, LACP across both switches is supported that’s one of the perks of VLT. Just make sure the basics are in place:

Set the switch ports to trunk mode and ensure VLAN 13 is tagged.

Create a port-channel on both switches using the same ID.

Add the physical interfaces to the port-channel with channel-group X mode active.

On the port-channel itself, set it to trunk and allow VLAN 13.

On the server side, configure bonding mode 802.3ad, then create a VLAN interface on top of the bond. Assign your IP to the VLAN interface  not directly to the bond.

No Events found!

Top