jonas-p
asked on
Network Setu
Hi,
I'm setting up SAN environment for my two ESXi servers.
The SAN i'm using is a Starwind Serer according to PDF (attachment)
For my two server i'm using: Windows Server 2008R2 and have following network setup:
Server 1:
NIC1: 192.168.1.241 (ip), 255.255.255.0 (subnet), 192.168.1.1 (gateway)
NIC2: 192.168.2.241(ip), 255.255.255. (subnet), ?? 192.168.2.1 gateway) ??
Server 2:
NIC1: 192.168.1.242 (ip), 255.255.255.0 (subnet), 192.168.1.1 (gateway)
NIC2: 192.168.2.242(ip), 255.255.255. (subnet), ?? 192.168.2.1 gateway) ??
Both NIC2 are connected to eachother with a crosscable.
First question problem i have is: must i fill in the gateway? They can't ping to eachother?
Second question i have how do I need to setup my ESXi servers for good network performance? (see image) I am using VMware vCenter for HA between the two servers.
Now important remark is that also my ESXi are using two nic's for one server. Now this is just for sharing networking load. Because i'm using only one switch.
Thanks in advance.
StarWind-HA-ESX.pdf
VMNetwork.jpg
I'm setting up SAN environment for my two ESXi servers.
The SAN i'm using is a Starwind Serer according to PDF (attachment)
For my two server i'm using: Windows Server 2008R2 and have following network setup:
Server 1:
NIC1: 192.168.1.241 (ip), 255.255.255.0 (subnet), 192.168.1.1 (gateway)
NIC2: 192.168.2.241(ip), 255.255.255. (subnet), ?? 192.168.2.1 gateway) ??
Server 2:
NIC1: 192.168.1.242 (ip), 255.255.255.0 (subnet), 192.168.1.1 (gateway)
NIC2: 192.168.2.242(ip), 255.255.255. (subnet), ?? 192.168.2.1 gateway) ??
Both NIC2 are connected to eachother with a crosscable.
First question problem i have is: must i fill in the gateway? They can't ping to eachother?
Second question i have how do I need to setup my ESXi servers for good network performance? (see image) I am using VMware vCenter for HA between the two servers.
Now important remark is that also my ESXi are using two nic's for one server. Now this is just for sharing networking load. Because i'm using only one switch.
Thanks in advance.
StarWind-HA-ESX.pdf
VMNetwork.jpg
Neil Russell
does each server only have the two physical NICs?
Turn-off firewalls, and no there is no need for a gateway, unless you need to route traffic.
If your ESXi servers only have two NICs
1. do you want resilience and load balancing?
2. do you want a dedicated storage network?
If you do not want network teaming and a storage network, I would leave as is, otherwise move vmnic1 to vSwitch0, and create an VMKernel Port on vSwitch0.
If your ESXi servers only have two NICs
1. do you want resilience and load balancing?
2. do you want a dedicated storage network?
If you do not want network teaming and a storage network, I would leave as is, otherwise move vmnic1 to vSwitch0, and create an VMKernel Port on vSwitch0.
in an ideal world, you would add more physical NICs to your ESXi servers.
ASKER
Okay,
@Nielsr: yes every servers has two NIC's.
@hanccocka: i want to go for option 1
What i already did was remove the gateway from NIC2.
I added the storage according to the manuel. My VMnetwork has following lay-out (see image).
So far so good for my VMware's
1.) If I want load balacing should I reconfigure the network? Should i move the VMotion vkernel port to swtich 1? What should i do with my VMNetwork?
2.) I want to use the same SAN (HA-Storage) for my workstations (Win 7). So i added both targets true the iSCSI initiator, but now i has two disks. I just want to see one HA-storage and you synch automatic. Is it possible to provide a SMB share or should i configure for each client the iSCSI initiator?
Can it be on the same HA-storage drive as for the VM's or should i configure a second HA-storage true Starwind for my workstations and other clients, maybe if possible SMB share?
Already thanks in advance.
Kind regards.
VMNetwork-v2.jpg
Datastores.jpg
iSCSI-initiator.jpg
iSCSI-initiator2.jpg
iSCSI-initiator3.jpg
@Nielsr: yes every servers has two NIC's.
@hanccocka: i want to go for option 1
What i already did was remove the gateway from NIC2.
I added the storage according to the manuel. My VMnetwork has following lay-out (see image).
So far so good for my VMware's
1.) If I want load balacing should I reconfigure the network? Should i move the VMotion vkernel port to swtich 1? What should i do with my VMNetwork?
2.) I want to use the same SAN (HA-Storage) for my workstations (Win 7). So i added both targets true the iSCSI initiator, but now i has two disks. I just want to see one HA-storage and you synch automatic. Is it possible to provide a SMB share or should i configure for each client the iSCSI initiator?
Can it be on the same HA-storage drive as for the VM's or should i configure a second HA-storage true Starwind for my workstations and other clients, maybe if possible SMB share?
Already thanks in advance.
Kind regards.
VMNetwork-v2.jpg
Datastores.jpg
iSCSI-initiator.jpg
iSCSI-initiator2.jpg
iSCSI-initiator3.jpg
1.) If I want load balacing should I reconfigure the network? Should i move the VMotion vkernel port to swtich 1? What should i do with my VMNetwork?
Okay, you will need to destroy vSwitch1.
Move the vmnic1 onto vSwitch0, re-create VMKernel on vSwitch0.
2.) I want to use the same SAN (HA-Storage) for my workstations (Win 7). So i added both targets true the iSCSI initiator, but now i has two disks. I just want to see one HA-storage and you synch automatic. Is it possible to provide a SMB share or should i configure for each client the iSCSI initiator?
Can it be on the same HA-storage drive as for the VM's or should i configure a second HA-storage true Starwind for my workstations and other clients, maybe if possible SMB share?
DO NOT MIX VMWARE AND WINDOWS iSCSI LUNs, YOU WILL HAVE ISSUES.
You need to use Access rules, in Starwind, to ensure, that Windows Workstations and VMware Servers are isolated.
e.g. Windows cannot see VMware LUNs, VMware Servers cannot see Windows LUNs.
You cannot share iSCSI LUNs between Windows Workstations.
If you want to share a iSCSI LUN on a Workstation, you need to add the iSCSI LUN, and then create a folder on the disk, and share it.
then workstations can access the share and data.
e.g. Windows cannot see VMware LUNs, VMware Servers cannot see Windows LUNs.
You cannot share iSCSI LUNs between Windows Workstations.
If you want to share a iSCSI LUN on a Workstation, you need to add the iSCSI LUN, and then create a folder on the disk, and share it.
then workstations can access the share and data.
ASKER
Okay hanccoka thanks for the information but i don't understand it very good:
1.) I have now on both of my servers 4.7 TB storage available.
Should i configure a Starwind iSCSI LUN let's say for example 2TB. Then connect this HA-storage to my ESXi servers, this according the manual from Starwind. This is clear for me and no problems to complete.
2.) They other storage 2.7TB I want to use for documents, drawings, ... on my workstations.
How should i do this? Provide a second HA-storage with the starwind servers? But how will I get them in my workstations as one disk? Suggestions?
Kind regards.
1.) I have now on both of my servers 4.7 TB storage available.
Should i configure a Starwind iSCSI LUN let's say for example 2TB. Then connect this HA-storage to my ESXi servers, this according the manual from Starwind. This is clear for me and no problems to complete.
2.) They other storage 2.7TB I want to use for documents, drawings, ... on my workstations.
How should i do this? Provide a second HA-storage with the starwind servers? But how will I get them in my workstations as one disk? Suggestions?
Kind regards.
1. Correct, but we prefer to use smalkler LUNs, but that's up to your personal preferences. You can always grow a LUN, but shrinking is more difficult.
2. Why not just create s share on this server for ALL the workstations to access? I do not think there is any point, in creating a single LUN to present to a single workstation, and then that workstation share that disk?
2. Why not just create s share on this server for ALL the workstations to access? I do not think there is any point, in creating a single LUN to present to a single workstation, and then that workstation share that disk?
But how will I get them in my workstations as one disk? Suggestions?
You cannot use iSCSI. You must use a WIndows SHARE.
ASKER
Okey thanks again for the usefull information.
I just have one comment/question:
- Indeed i think the best way i to setup a windows share or smb share, ...
I can do this on one server but how will it synch between the other server?
Both server must have the same 4.7TB (2TB for VM's backup) and (2.7TB for documents backup)
How is that possible for the documents share?
I just have one comment/question:
- Indeed i think the best way i to setup a windows share or smb share, ...
I can do this on one server but how will it synch between the other server?
Both server must have the same 4.7TB (2TB for VM's backup) and (2.7TB for documents backup)
How is that possible for the documents share?
If you want to sync shares, you will have to look at third party software.
free software, robocopy, DFS, Windows replication.
free software, robocopy, DFS, Windows replication.
ASKER
Okay thanks for the information just for i close this question.
hanccocka:
1.) If I want load balacing should I reconfigure the network? Should i move the VMotion vkernel port to swtich 1? What should i do with my VMNetwork?
Okay, you will need to destroy vSwitch1.
Move the vmnic1 onto vSwitch0, re-create VMKernel on vSwitch0.
I can' to do this because off the ESXi 5 then i can't acces the vmkernel port on my software scsi.
What the correct procedure for load ballacing?
hanccocka:
1.) If I want load balacing should I reconfigure the network? Should i move the VMotion vkernel port to swtich 1? What should i do with my VMNetwork?
Okay, you will need to destroy vSwitch1.
Move the vmnic1 onto vSwitch0, re-create VMKernel on vSwitch0.
I can' to do this because off the ESXi 5 then i can't acces the vmkernel port on my software scsi.
What the correct procedure for load ballacing?
if you want to load balance NICs, you will need to add both physical nics, vmnic0 and vmnic1, to vSwitch0.
leave your VM Network on vSwitch0.
and use a single VMKernel for iSCSI.
You;ve now got a load balanced, and fault tolerent vSwitch0 for VMs and Management Network, VMKernel.
Traffic will, load balance between NICs onto the network.
otherwise, you will have to add more physical NICs, one physical nic to vSwitch0 and vSwitch1.
Not alot you can really do for resilience and load balancing with two single NICs, unless you pair them
leave your VM Network on vSwitch0.
and use a single VMKernel for iSCSI.
You;ve now got a load balanced, and fault tolerent vSwitch0 for VMs and Management Network, VMKernel.
Traffic will, load balance between NICs onto the network.
otherwise, you will have to add more physical NICs, one physical nic to vSwitch0 and vSwitch1.
Not alot you can really do for resilience and load balancing with two single NICs, unless you pair them
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.