VMware Cloud Community
kwolton10
Contributor
Contributor

Sepertate Vmware management network without AD/DNS

Hi,

I have performed a few installs now, and im not sure it it's best practice but i always like to keep my ESXi/vcentre network separate from my main corporate network. Reason being i normally virtualize everything and if it all came crashing down i know i can still access my hosts/vcentre to fix it. Is this not best practice? Do Vmware really want you to rely on your visualized AD to run the backbone of your network? Also if it's a new installation, where am i going to get AD/DNS from as i would not have been able to install any VM's yet?

I have two hosts i want to deploy and before i would just keep them on a separate subnet, not use DNS and just manage them with a separate network card on my management server/workstation. I have tried to replicate this with 5.5, however i now find that i cannot login to the hosts, i just get

'503 Service Unavailable' which is because it cannot find a hostname in DNS apparently.

Is this because Vmware have moved everything across to a stupid web gui and are trying to push everyone to use that? I am more then happy using the client and will continue to do so until i am forced to move.

How can i make this install work, baring in mind it is being setup with no DNS servers present and will not be part of a AD (because it has no need to be). How can i get rid of the 503 Service Unavailable error?

Any help would be greatly appreciated as i have to get these out into production soon.

Kris

Reply
0 Kudos
0 Replies