Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 258
  • Last Modified:

Setting up a separate network for VMWare and SAN

Hi everyone, trying to understand in a little bit more detail how I could go about setting up a separate physical network to segregate a VMWare Server & iSCSI SAN traffic from the rest of the LAN. I'm not currently using switched that support any VLANing.

My VMWare Server has multiple NICs as does my SAN. Currently I have them assigned static IP addresses of
VMWare: 10.200.1.10
SAN: 10.200.1.11
Subnet: 255.255.248.0
Gateway: 10.200.0.1

I'm a little confused about a few things.
1.) To separate their traffic is it as simple as adding another physical switch that has each of their NICs plugged into the switch (existing NICs and IPs referenced) and a 3rd cable connecting the switch to the main network switch? Or does this defeat the purpose?

2.) If option one is incorrect the proper way I would assume would be to add another physical switch and configure a 2nd NIC on each device and plug that into the new separate switch and setup the new NICs as the way the VMWare Server and SAN communicate. Is this correct? Leave the current NICs and IPs there so that I can remotely manage the appliances right?

3.) If option 2 is the correct idea what IP address/subnet do I configure for the new NICs? Can I use my existing subnet or is that defeating the purpose? IE: could I setup the new NICs as
IP-10.200.1.12
Subnet - 255.255.248.0
Gateway - 10.200.0.1

Also is it relevant that the new NICs & switch wouldn't be connected to the main network and therefore be unable to reach our gateway of 10.200.0.1?

Thanks! Any advice or help is appreciated!
0
MikeC7
Asked:
MikeC7
  • 2
2 Solutions
 
Paul SolovyovskyCommented:
What kind of switching environment do you have?  If it supports VLANs you can separate using VLANs (essentially creating multiple layer 2 switches on the same switch).  iSCSI traffic should not be routed so in most environments there is no need for a default gateway
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
1. Ideally it would be completely isolated, and not connected to any production network.

2. Correct

3. Use a different IP Address Scheme, 192.168 or 10.10.

Yes the default gateway would be uncreachable as the storage network is completey isolated.
0
 
MikeC7Author Commented:
The switches I'm using aren't setup for VLANs
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
and when setting up your new storage network enable Jumbo Frames if SAN and Network Switches support Jumbo Frames


HOW TO: Enable Jumbo Frames on a VMware vSphere Hypervisor (ESXi 5.0) host server using the VMware vSphere Client
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now