We are reconfiguring our FAS2040 using an MSLA setup for load balance. Our switching infrastructure is a 3750 stack of 4 members and the clients connecting to the Filer are 6 ESXi 5.1 servers via NFS/iSCSI as well Windows machines via CIFS.
NFS Subnet / VLAN: 10.1.200.0 / 200
iSCSI Subnet / VLAN: 10.1.300.0 / 300
Mangement Subnet / VLAN: 10.1.400.0 / 400
CIFS Subnet / VLAN: 10.1.500.0 / 500
ESXi NFS VMkernel IP: 10.1.200.15
ESXi iSCSI VMkernel IP: 10.1.300.15
Load Balancing options: Route based on IP hash
I'm thinking that e0a and e0b can be put into a VIF to serve NFS/management traffic so I would assign the following IP and aliases to the LACP VIF:
10.1.200.26, 10.1.200.226, 10.1.400.26
I'm put e0c and e0d in another VIF for iSCSI and CIFS:
10.1.300.26, 10.1.300.226, 10.1.500.26
Within vSphere I would have to divide the datastore load evenly between 10.1.200.26 and 10.1.200.226, correct?
The goal is to serve iSCSI/NFS/CIFS and management traffic through the 4 ports in the filer. Splitting the load between the 2 ports in each VIF is ideal, although I could also split it among all four ports by creating a single 4-port VIF with 4 iSCSI IP's, 4 NFS IP's and 1 IP for MGMT and CIFS...
What would be your recommendation? Also I need to tag a VLAN id to each IP.
Below is what I am planning on running:
vif create lacp vif1 -b ip e0a e0b
vlan create vif1 200 400
ifconfig vif1-200 10.1.200.26 netmask 255.255.255.0 mtusize 1500
ifconfig vif1-200 alias 10.1.200.226 netmask 255.255.255.0
ifconfig vif1-400 alias 10.1.400.26 netmask 255.255.255.0
vif create lacp vif2 -b ip e0c e0d
vlan create vif2 300 500
ifconfig vif2-300 10.1.300.26 netmask 255.255.255.0 mtusize 1500
ifconfig vif2-300 alias 10.1.300.226 netmask 255.255.255.0
ifconfig vif2-500 alias 10.1.500.26 netmask 255.255.255.0
route add default 10.1.500.1 1
routed on
reboot
Do you want to see the switching setup as well?