Unsolved
This post is more than 5 years old
6 Posts
0
3263
October 12th, 2018 22:00
Configuring 3 nodes vSAN 6.7 using S4128F
Hello,
I am in the midst of configuring 3 nodes vSAN 6.7 using 4 switches as below: -
- Cisco 2960X (1) for vMotion and ESXi Management traffic
- Cisco 2960X (2) for vMotion and ESXi Management traffic (for redundancy)
- S4128F (A) only for vSAN traffic
- S4128F (B) only for vSAN traffic (for redundancy)
Note: NO additional vlan created (only default vlan1) since Dell switches only for vSAN traffic.
I have no issue to configure the Cisco switches, but I need guidance on the Dell switches. Below are the CLI I extract from "Dell EMC Networking - Deploying VMware vSAN with OS10 Enterprise Edition".
Kindly advise if I miss any important commands. Much appreciated!
S4128F(A)
=========
## OOB (A)
interface mgmt 1/1/1
no ip address dhcp
ip address 192.168.0.1/24
no shutdown
management route 192.168.0.0/24 192.168.0.254
## VLTi (A) for 2 100GbE QSFP28 ports
interface ethernet1/1/29-1/1/30
description VLTi
no shutdown
no switchport
vlt-domain 127
backup destination 192.168.0.2
discovery-interface ethernet1/1/29-1/1/30
## Node-Facing (A) for all 28 ports
interface ethernet1/1/1
no shutdown
switchport mode trunk
switchport access vlan 1
mtu 9216
spanning-tree port type edge
S4128F (B)
==========
## OOB (B)
interface mgmt 1/1/1
no ip address dhcp
ip address 192.168.0.2/24
no shutdown
management route 192.168.0.0/24 192.168.0.254
## VLTi (B) for 2 100GbE QSFP28 ports
interface ethernet1/1/29-1/1/30
description VLTi
no shutdown
no switchport
vlt-domain 127
backup destination 192.168.0.1
discovery-interface ethernet1/1/29-1/1/30
## Node-Facing (B) for all 28 ports
interface ethernet1/1/1
no shutdown
switchport mode trunk
switchport access vlan 1
mtu 9216
spanning-tree port type edge
Thanks.


ascll
6 Posts
0
October 15th, 2018 02:00
Mattwww
4 Posts
0
October 16th, 2018 10:00
I don't have any direct feedback on your switch config, but hopefully this will point you in the right direction.
vSAN does not support two VMK's with the vSAN service enabled on the same subnet. So you would need to "air-gap" the network in order to accomplish what you are wanting to do.
More information here: https://storagehub.vmware.com/t/vmware-vsan/vmware-r-vsan-tm-network-design/configuration-2/
in short, you would need to create two vlan's with two separate network. i.e. on vsan interface on a 10.10.10.x network and another on a 192.168.10.x network, each on their own VLAN.