ToR Configuration for Servers Switch

[amedinaj]

Hi all, we have 2 VSP-4900 that will be installed in a rack as ToR for hypervisors servers (Hyper-V and VMWare). This 2 tor switches are already configured to connect to the core switches with Fabric (2 core switches with Fabric and vIST).

Each server will be connected to each ToR switch. My question is, this ToR should be configured as a vIST cluster and configure a MLT for each server?

Thanks and best regards.

Amedina

[JDoug]

gfriedl is correct... if the connections from the server to the ToRs is going to be in a LAG then the ToRs need to be in an SMLT Cluster, if the links from the server to the ToRs are not going to LAG then dont SMLT cluster the ToRs.  And of course make sure the 'server guys' are on board either way, in my experience this can be the hardest part as the 'server world' uses different terminalogy compared to the 'network world'

[gfriedl · Accepted solution]

this depends on what you want to achieve/use on server side (HYper-V / VMware) . both vendors tend to recommend LAG-free redundancy mechanics. like VM-based load-balancing. In this case you must NOT use SMLT connections to these hosts and there is no need for a VIST connection between your TOR nodes. in other modes you might require SMLT, if you want to stay with LAG-based load-balancing. it's just your decision, which must be agreed with the people, that do the setup on server side.

[stevediaz]

Hello

Yes, configuring the ToR switches as a vIST cluster is recommended for redundancy & load balancing. By creating an MLT (Multi-Link Trunking) for each server, you ensure better reliability and optimal use of both switches. Just make sure the servers are configured with NIC teaming / similar features to support this setup.

Best regards!🙂