Good afternoon,
I'm a little confused about the best way to connect our storage switches to our hosts for VSAN.
We have 4x Dell R730xd with 2 disk groups in each. I have them connected to a pair of Brocade VDX-6720s that are joined by ISL fabric.
Currently The dedicated VSAN DV Switch is configured with both VDX1 and VDX2 set as active uplinks, routing based on originating virtual port.I have the VLAN set at the switch, untagged across the 4 ports on each switch.
However I have two documents that seem to configure it different ways; the Brocade-EVO Rail guide tagging the ports as individuals:
"20. Configure the server-facing network interfaces
Configure the ports on the switch which connect to the EVO:RAIL nodes
interface tengig 1/0/1-4
Next put the port into trunk mode by entering the following two commands:
switchport
switchport trunk mode"
No mention of LAG except for edge ports connecting the Brocade back to the main LAN.
Or the VSAN Network Design guide referencing Architecture 2 - Stacked Switches indicating that the two switches should have their common host ports joined in a LAG:
"Table 5 lists network adapter teaming policies supported when switches are stacked. To achieve bandwidth
aggregation, the “Route based on IP hash” policy with all adapters’ being active should be set in the distributed
port group for Virtual SAN and other port groups that share the same uplinks. All other policies can result in load
sharing, but not load balancing, regardless of whether the teaming is in active–standby or active–active mode,
as with architecture 1.
With IP hash-based load-balancing policy, all physical switch ports connected to the active vmnic uplinks must
be configured with static EtherChannel or LACP. This ensures that the same hash algorithm is used for traffic
returning in the opposite direction. And IP hash-based load balancing should be set for all port groups using the
same set of uplinks. All vmnics in the team can be used for Virtual SAN traffic.
So does this mean that the EVO-Rail design guide will result in load sharing, rather than load balancing?
I'd like to do it right the first time.
Brad