VMware Communities: vCenter Server across more than one ...

VMware

Up to Discussions in VMware vCenter™ Server

This Question is Possibly Answered

1 "correct" answer available (10 pts)

8 Replies Last post: Nov 7, 2009 3:13 AM by amvmware

vCenter Server across more than one domain posted: Nov 6, 2009 1:25 AM

mikesf

4 posts since
Nov 3, 2009

Please could anybody shed some light on a problem that I am having. We recently upgraded to Exchange 2007, therafter we had to add our vCenter Server to the domain as this wasnt done so previously to allow Backup Exec to see the Exchange Store for backup purposes.

We have two domains on site, one that we have added the vCenter Server to and another which some of the VM's are joined to. The problem I am having is that the Client will not connect to the Server to allow me to administer the setup. Prior to adding it to the domain I could connect without a problem and see all VM's in both domains. Now when I connect the server either times out or does not find the address, even when using localhost, IP's or hostnames.

VMWare support have suggetsed that I re-install the vCenter Server application on our server, the question I would like answered is, if I go ahead and do this would it affect my current config. In other words would it do an install over the top of the current software or would I need to treat it as a "new" install, point it to the databases etc?

Re: vCenter Server across more than one domain

1. Nov 6, 2009 1:39 AM

in response to: mikesf

NTurnbull

429 posts since
Feb 11, 2008

Hi, can you RDP to your vCenter server and if you can then does the client timeout when run locally on the vCenter server?

With regards to the re-install, you can re-install the binaries and point it to your existing VC Database so that it doesn't loose your config. If your worried then just backup your database. You could try a fresh install with a new database to see if that solves it then restore your DB over the top of the blank one and see if the problem comes back - if it does then the problem is in your DB.

Thanks,
Neil

Re: vCenter Server across more than one domain

2. Nov 6, 2009 4:23 AM

in response to: NTurnbull

mikesf

4 posts since
Nov 3, 2009

Hi,

I can RDP to the box and all the services are started. At the moment I have removed the box from the domain and returned it to a workgroup server. I'm now getting a login and the client opens but the data in the view pane is timing out, any ideas as what to look at for that specific problem? I'm more concerned about getting the client up and running at the moment.

Re: vCenter Server across more than one domain

3. Nov 6, 2009 4:32 AM

in response to: mikesf

amvmware

117 posts since
Feb 26, 2007

It could be something as basic as DNS name resolution.

Can you ping the IP addresses of any server in the other domain - if you can then try using nslookup and see if you can connect to the servers by their fully qualified domain names. By adding the computer to a domain external name resolution (outside of the domain) will be via the DNS servers in that domain - if they can't resolve the names or IP addresses of the servers in the other domain then that may be the reason.

Do you have trusts in place beteen these domains.

Or DNS forwarding between domains enabled.

Re: vCenter Server across more than one domain

4. Nov 6, 2009 4:57 AM

in response to: mikesf

NTurnbull

429 posts since
Feb 11, 2008

As pointed out check the DNS resolution - especially for the SQL server name used in the ODBC DSN if it's a remote DB. Could always add an entry into the localhosts file to test?

Thanks,
Neil

Re: vCenter Server across more than one domain

5. Nov 6, 2009 5:02 AM

in response to: amvmware

mikesf

4 posts since
Nov 3, 2009

Thanks for all the info guys.

Ok so I have got the client working now. My biggest problem will be getting the server to be able to authenticate on both domains in future (mainly for exchange backup purposes).

I have a couple of problems, 1) one domain is a windows AD based one, I need to add the vServer to this domain but it then has problems running the client. 2) When the vServer is added to the domain it has problems "seeing" all the rest of the servers in the "other" domain, I would imaging this is a authentication and trust issue. 3) The "other" domain consists only of Linux based servers and a couple of Windows serves but no actual DC. 4) Check the DNS configuration and ensure that SQL dns is correct ( SQL Express database is local to the vServe)

What I'd like to know if the following:

I'm planning to add the vServer to the domain again next week and run the install of vServer over the original install and connect it to the existing database. Once that is done I'll then try and see if the client connects and if I can browse the virtual infrastructure.

Would this be the recommened solution or would it be worth while looking into having a separate Media Server within the domain to take care of the backups for servers within the domain and run vServer as it is to be able to administer both domains?

Re: vCenter Server across more than one domain

6. Nov 6, 2009 5:17 AM

in response to: mikesf

amvmware

117 posts since
Feb 26, 2007

Not quite sure what your Infra looks like.

The other domain is not a WIndows domain - so the microsoft servers must be in a workgroup or standalone - I assume you mean they share the same DNS domain namespace.

If they do - then there must be DNS deployed in that domain to allow for name resolution.

If not then you might have to consider using hosts files on the computer you install the vCenter on and add the records for the servers in the other "domain" to that host file.

Re: vCenter Server across more than one domain

7. Nov 7, 2009 1:13 AM

in response to: amvmware

mikesf

4 posts since
Nov 3, 2009

Thanks for all the info again.

I think you guys are correct in the DNS area. The Windows servers in the "other" domain are in a workgroup setup but do share the same DNS NameSpace and there are Linux DNS servers setup in that domain. I think that must be where the problem lies, the Linux and Windows DNS servers will both need to altered in both domains to reflect the changes in the DNS namespace.

So my plan of action is re-add the vServer to the domain and alter the DNS records on both domains so that they are correct and check the Host File on the vServer as there are entries there currently for various servers including the vServer itself. There are two NICS for two different IP ranges for either domains so that would have to be carfeully setup correctly so that both ranges can address the vServer with the corresponding DNS address. I'll create a backup of the exisintg SQL Express database. Once this has been sorted I'll then re-install the vServer application, point it to the existing database and hopefully this will allow both domains to connect to the vServer and Backup Exec to see both domains for backup purposes. I might have to re-deploy the Backup Exec agents to the servers but that shouldnt be too much of a task.

Would you agree?

Cheers!

Re: vCenter Server across more than one domain

8. Nov 7, 2009 3:13 AM

in response to: mikesf

amvmware

117 posts since
Feb 26, 2007

I would take it steady and make as few changes as is required - if you go and make lots of changes you could be creating additional issues for yourself.

I would look to see if DNS forwarding can be configured between the different DNS namespaces or failing that add host or A records in each DNS zone for the servers from the other DNS zone.

You may also have to add records in the reverse DNS zone as well.

Go to original post

Search VMware Communities Advanced Search

Actions

View as PDF

Up to Discussions in VMware vCenter™ Server