• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Stretched datacenter topology

M

moto316

n00b
Joined
Sep 22, 2005
Messages
59
I manage a site that has two data centers in separate buildings connected via single-mode fiber, the fiber run is less than 300 meters so latency is on par with a LAN (<1ms). We have a stretched VMware cluster spanning across those two sites backed by a NetApp metrocluster storage system. Currently we have two pairs of S4810's for switching and routing at each datacenter. One pair is dedicated to LAN services (VM traffic, clients, endpoints, access layer connections, etc) and the other pair is for NFS storage and vMotion traffic originating from our VMware ESXi hosts and NetApp storage systems. These two separate pairs are currently airgapped with no connection whatsoever between LAN and SAN switches. What I need to do is connect these two separate switching fabrics together.

The current layout with the two separate fabrics with the VLT domains and bridge priorities configured as is: http://i.imgur.com/FXUfVuj.png?1

The network topology of what I am proposing to connect the two fabrics together, with unique VLT domain ID's for each stack: http://i.imgur.com/cEitx8N.png

Do any of you see any issue's with STP in my proposed layout? Should I keep incrementing the bridge priorities for the new switches being brought into the LAN fabric? (ie 16384, 20480, etc.) Do you know if I can reconfigure VLT domain ID's without disruption?
 
You must log in or register to reply here.
Back
Top