VMware Cloud Community
jbriskin
Contributor
Contributor
Jump to solution

Standard Network Naming

I have three hosts \[vm01, vm02, vm03\] in a single cluster \[CL01\]. On each host I have one virtual switch with two standard networks - one for mgmt and one port group. On vm01 I named these VM01Network and VM01MgmtNetwork. On VM02 and 03 I simply changed the numbers in the names to match. Therefore, each host has two networks and the cluster has three port group networks... VM01Network VM02Network, and VM03Network - in other words, each host has a different virtual network name...

Is this correctly configured? I plan on using FT and HA. Do I need all these names to be the same? Is making them different the better way? TO be clear, if you look at a map of the cluster you see three unconnected maps.

0 Kudos
1 Solution

Accepted Solutions
jpdicicco
Hot Shot
Hot Shot
Jump to solution

The names MUST be identical for vMotion (and I would assume) FT to work. This is because the name is what the NIC in the VM properties is tied to. When the VM moves to a different host, it finds the correct port group by matching the name.

Happy virtualizing!

JP

Please consider awarding points for correct and/or helpful answers

Happy virtualizing! JP Please consider awarding points to helpful or correct replies.

View solution in original post

0 Kudos
6 Replies
jpdicicco
Hot Shot
Hot Shot
Jump to solution

The names MUST be identical for vMotion (and I would assume) FT to work. This is because the name is what the NIC in the VM properties is tied to. When the VM moves to a different host, it finds the correct port group by matching the name.

Happy virtualizing!

JP

Please consider awarding points for correct and/or helpful answers

Happy virtualizing! JP Please consider awarding points to helpful or correct replies.
0 Kudos
weinstein5
Immortal
Immortal
Jump to solution

Welcome to the forums - yes for FT the portgroup name needs to be the same for the VM and FT network - and BTWit will also need to be the same for vmotion, DRS and HA to work as well -

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos
jbriskin
Contributor
Contributor
Jump to solution

yes.. as I further went through configuring it became pretty apparent.... thanks for the confirmation.

0 Kudos
AntonVZhbankov
Immortal
Immortal
Jump to solution

In this case you won't be able to move VMs between hosts. VMs are attached to networks, not to vSwitches. It your job to place appropriate network on particular vSwitch and provide network connectivity so VMs can be migrated seamlessly.


---

MCSA, MCTS, VCP, VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda
0 Kudos
jbriskin
Contributor
Contributor
Jump to solution

I named the network the same... do I need to name the Management networks the same as well? i.e. turn VM01MgmtNetwork, VM02MgmtNetwork, and VM03MgmtNetwork on the three different hosts in the cluster to all be something like VMMgmtNetwork?

I am guessing I do need this change. Might this difference be the reason why VMs on one host cannot "see" Data Stores on other hosts?

0 Kudos
AntonVZhbankov
Immortal
Immortal
Jump to solution

Not sure about management networks, but actually there is no need to name them different.


---

MCSA, MCTS, VCP, VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda
0 Kudos