my personal blog about systemcenter

Virtual Machine Manager , Networking and Trailing Spaces

I recently ran into a issue where I was unable to set the network on a
virtual machine.

image_thumb[9]

There was a working logical network , VM that spanned the Hyper-V cluster and
everything was working

image_thumb[11]

For the purpose of reproduction I called the “broken” logical network
Trailing Spaces

image_thumb[14]

When I try to set the logical network on the virtual machine

Warning (25133)
Selected Virtual Network Switch (Trailing Spaces) is not
available as a highly available clustered virtual network combination.

Recommended Action
Please choose different highly available virtual
network or if possible another one would be automatically chosen for you.

Warning (25134)
Selected Highly Available Virtual Machine’s logical
network (Trailing Spaces) is not available as a highly available available
clustered virtual network combination.

Recommended Action
Please choose different logical network or set the
appropriate logical networks on all nodes of the cluster.

I get the error that the network is not avaialble

a get-virtualnetwork shows that the network is on all 5 Hyper-V hosts so
after a lot of digging around I see that the

image_thumb[18]

Name on HV05 have a trailing space and after digging around on the Hyper-V
hosts

Virtual Network Manager on HV1-4

image_thumb[6]


Virtual Network Manager on HV05

image_thumb[4]

I can see that HV05 indeed have a trailing space after its display name

image_thumb[22]

So I removed the trailing space on the Virtual Network and refreshed the
cluster

image_thumb[24]

And then I was able to set the correct virtual network and everyone was
happy.

Will you ever run into this ? most likely not

All Virtual Networks was created manually , never trust something that needs
to be done 5 times in a row

Everything should be scripted Smile