• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 67
  • Last Modified:

Vmware connections to Storage.

Vmware connections to Storage.

In Vmware we can have so many VMs in so Many Vlans.
seeing that ESX hosts connect to the storage via Storage Switch, the question is  whether the storage is also  mapped to vlan of the VMs ?

for instance we have VLANS 10,20,30,40 on ESX host.  The storage is presented to ESX host and assigned IP address 192.168.20.15/24. Now will only VMs on VLAN 20 be able to access the storage or other VMs on VLANs 10,30,40 also can access the storage ?

Thank you
0
jskfan
Asked:
jskfan
  • 9
  • 7
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Storage is configured and added to each host via a Network.

VMs are then stored on that storage.

I would need to see networking information, if VMs Networks share Storage Network this is not Best Practice.

So please provide some screenshots of networking information.
0
 
jskfanAuthor Commented:
you have  4 ESX hosts in the subnet 192.168.25.0/24
You have a storage device in the subnet 192.168.30.0/24

there are many VLANs in ESX hosts, some in 10.10.10.0/24 network, some 172.16.0.0/16 network

Now when you create new VM ND  put it in Vlan 172.16.0.0/16 , will you be able to create the Disk in the storage which is in the subnet 192.168.30.0/24  ?
0
 
jskfanAuthor Commented:
OR  you will have to create a storage in the subnet 172.16.0.0/16
0
Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
what is the IP Address of the iSCSI SAN ?

I assume it's iSCSI, what is the IP Address in iSCSI settings ?

Now when you create new VM ND  put it in Vlan 172.16.0.0/16 , will you be able to create the Disk in the storage which is in the subnet 192.168.30.0/24  ?

Yes probably. because the host is connected to storage network or STORAGE using LAN - 192.168.30.0. The VM does not have access to this LAN.
0
 
jskfanAuthor Commented:
what is the IP Address of the iSCSI SAN ?
172.16.0.24/16

I believe when Storage is presented to ESX Host, the IP address of the storage should match the subnet on which the IP address of ESX host management interface is on.
0
 
jskfanAuthor Commented:
I am also not clear when you have an ESX host with management interface is on the subnet 192.168.30.0/24, whether all VMs in that ESX host have to be in VLANs 192.168.30.0/24
for instance if you have an ESX host with Management interface 192.168.30.30/24, you cannot have VMs in it in Vlan 10.10.10/0/24
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
172.16.0.24/16

I believe when Storage is presented to ESX Host, the IP address of the storage should match the subnet on which the IP address of ESX host management interface is on.

Rubbish. You can pick any network you like for storage, and any different network you like for Management of ESXi.

I am also not clear when you have an ESX host with management interface is on the subnet 192.168.30.0/24, whether all VMs in that ESX host have to be in VLANs 192.168.30.0/24
for instance if you have an ESX host with Management interface 192.168.30.30/24, you cannot have VMs in it in Vlan 10.10.10/0/24

Not at all, you could have a Host in the cloud on 1.1.1.1, and all your VMs would be on different networks for all your clients!

Your clients are not managing the host, they are just purchasing a service!
0
 
jskfanAuthor Commented:
Andrew,

I am not using CLoud, everything in the local DataCenter.

how would ESX host in the subnet 192.168.30.0/24 be able to have its VMs storage that is in network 10.10.10.0/24. ?

My only Guesses:
1- ESX host Trunks all networks (VLans on which VMs are located)  to a Switch (assuming it is L3), then the L3 switch VLAN interface connects to Storage switch (L3 switch VLAN Interface should be on the same subnet as Storage switch Interface)

2- ESX Host physical port Trunks to Storage Switch directly (regardless of the subnet on which Vmkernel port for Storage is on) will still be able to connect to a storage switch port.
for instance Vmkernel port for storage in ESX is on 192.168.30.0 subnet, it will still be able to connect to a storage switch port  on172.16.0.0/16
or they have to be on the same subnet ?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I am not using CLoud, everything in the local DataCenter.

Open in new window


That was an example!

how would ESX host in the subnet 192.168.30.0/24 be able to have its VMs storage that is in network 10.10.10.0/24. ?

because host is connected to both!

Your are forgetting a MAJOR ARCHITECTURAL COMPONENT OF ESXi!

VMKernel Portgroup which is a HOST ONLY Portgroup which the Host uses to communicate with SANs.

and every VMKernel Portgroup  needs an IP Address.

Do not get confused between HOST ONLY and GUEST Networks!

1- ESX host Trunks all networks (VLans on which VMs are located)  to a Switch (assuming it is L3), then the L3 switch VLAN interface connects to Storage switch (L3 switch VLAN Interface should be on the same subnet as Storage switch Interface)

Lets forget VMs for the moment....

How does ESXi communicate with a HDD installed in the server ?

Do you understand the Concept of HOST and GUEST ?
0
 
jskfanAuthor Commented:
Screen-Shot-2018-03-11-at-2.56.12-PM.png
both ESX hosts in the diagram have each:
BLUEUE :one interface for Management and they are both in the same subnet
ORANGE:one interface to connect to the Storage Switch and they are both in the same subnet

When you create a VM, can you assign it an IP address different from the subnet of the Management interface and different from the subnet of the Storage switch port ?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
When you create a VM, can you assign it an IP address different from the subnet of the Management interface and different from the subnet of the Storage switch port ?

When you create a VM, you DO NOT Assign it an IP Address, you connect it to a virtual machine portgroup.

So what VIRTUAL MACHINE PORTGROUPS DO YOU HAVE AVAILABLE ? to connect the VM to ?

BLUE and ORANGE networks in your diagram, are networks which are connected to VMKernel Portgroups these are NOT virtual machine portgroups.

But there is nothing stopping you create virtual machine portgroups on BLUE and ORANGE, that you can connect to.
0
 
jskfanAuthor Commented:
OK

When VMs are in VMPortGroups, the VM Portgroups can have different Vlans: 192.168.30.0/24, 10.10.10.0/24 , 172.16.0.0/16v etc ?
Vmkernel Portgroup for storage : will this also be able to have different VLANs or just one VLAN on the same subnet as the storage switch port Ip address ?

Vmkernel portgroup for  Vmotion: will this be able to have many VLANs , or just one VLAN.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Virtual Machine Portgroups can have VLANs assigned to them.

What IP Address range has been decided for those VLANs has got nothing to do with ESXi, VMware, vCenter Server.

You IP Address ranges has been decided already by Network Team.

VMKernel Portgroups are used for Management Network, iSCSI, NFS, vMotion, Storage vMotion and Fault Tolerance, and Vsan, they are special portgroups which are allocated IP Addresses so they can be used by the Hypervisor for communications.

Again you can allocate a single VLAN Tag Number to each VMKernel Portgroups

So a single portgroup can have a single VLAN
0
 
jskfanAuthor Commented:
So a single portgroup can have a single VLAN

OK..I guess I started  getting it.

If I want t create VMs in multiple VLANs , I will have to create separate VM portgroup for each VLAN.
That's clear

Vmkernel PortGroup for Vmotion IP address :Can that be different from the VLANs subnet specified on the VM Portgroups ?


regarding
 VMkernel portgroup for Storage : does it have to be in the same subnet as the Storage ?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
f I want t create VMs in multiple VLANs , I will have to create separate VM portgroup for each VLAN.
That's clear

that is correct, Virtual Machine Portgroup.

Vmkernel PortGroup for Vmotion IP address :Can that be different from the VLANs subnet specified on the VM Portgroups ?

Again Network Design dictates what IP Address you use for VMLKernel Portgroup for vMotion - it could be anything, any VLAN

It would be terribly unwise and stupid not to follow Best Practice and use a VLAN which is already in use because the vMotion Network is supposed to be completely isolated with no traffic from anything else.

VMkernel portgroup for Storage : does it have to be in the same subnet as the Storage ?

What do you think ? If it was not in the same subnet  network traffic would not be able to communicate with the SAN Storage.

Possibly you could route it, but that's a bad idea.
0
 
jskfanAuthor Commented:
Thank you
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

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