1 Rookie
•
66 Posts
0
34
S4048-ON [OS9]: Creating a static port-channel (No LACP)??
We have two S4048-ON switches configured in VLT with four Windows 2019 servers attached to them. Each server has two 2-port NICs teamed using Switch Embedded Teaming (SET). Each server has one link from each team member to the switch. For example, NIC-A connects to VLT-Switch-A and NIC-B connects to VLT-Switch-B. These are just independent links. There is nothing more than some VLAN config on the interfaces for the servers.
This works well, but we were wondering if we could improve the failover time in the event of a NIC team member or link failure. Someone recommended that we configure a port-channel without LACP (because SET does not support LACP) for the switch ports connected to the servers. We figure that since we are using VLT, that this would have to be a VLT port-channel.
However, we can't figure out how to add interfaces to a VLT port-channel without LACP. Is this just not possible in OS9, and must interfaces be added to a VLT port-channel in LACP mode?
DELL-Chris H
Moderator
Moderator
•
8.8K Posts
1
August 9th, 2024 20:16
"NOTE: To benefit from the protocol negotiations, Dell EMC Networking recommends configuring VLTs used as facing hosts/switches with LACP. Ensure both peers use the same port channel ID
Let me know if this helps.
The_LostIT_Guy
1 Rookie
1 Rookie
•
66 Posts
0
August 9th, 2024 20:27
@DELL-Chris H Thanks for the information. Are you aware of any testing that Dell has maybe done with Switch Embedded Teaming? It would be awesome if there were some White Papers related to the topic.
DELL-Joey C
Moderator
Moderator
•
3.4K Posts
1
August 12th, 2024 01:46
Hi,
Tried to search for any, but there is none. The only one is related to Windows 2022 stop error. No white papers nor best practices.
The_LostIT_Guy
1 Rookie
1 Rookie
•
66 Posts
0
August 12th, 2024 13:31
For confused future readers . . . it's
channel-memberinterfacebtw. How I forgot, since it's how you statically add interfaces to the VLTi, I do not know. Long week . . .