Dana D
asked on
VM shows as orphaned in vcenter server inventory and are not showing at all on both esxi hosts.
Here is my exact setup notes:
vcenter server - 5.0.0
2 esxi 5.0.0 host servers
12 windows production servers across the 2 hosts
All production servers show as orphaned on both hosts in vcenter server. And when I vsphere into each host there are no VM's listed at all. Yet I could RDP to all 12 windows production servers and they are up and running properly!
I attempted to use this as a solution:
https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.troubleshooting.doc_50%2FGUID-BFD8C9BC-30FB-4A92-AFEC-2FC9FF387920.html
Which explains how to migrate the vm from one host to another in vcenter server. This process was only able to add a new instance of the VM to the other host in inventory and it was in the powered off mode!
This did nothing but complicate things so I was able to migrate the vm back to its orginal host using the same process in vcenter server - this made it show up on the original host so I vsphered into that host and removed the new instance from the hosts inventory and now was back at square one.
I also followed this resolution:
https://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1003490
to restart the management agents on each host but it still did not resolve the issue. both hosts servers are still showing NO vm's but yet the VM's are still up and running properly and they can be accessed via RDP.
Is there a non disruptive way to get them to re-register with the hosts and show in inventory?
Thank you in advanced for your suggestions!
vcenter server - 5.0.0
2 esxi 5.0.0 host servers
12 windows production servers across the 2 hosts
All production servers show as orphaned on both hosts in vcenter server. And when I vsphere into each host there are no VM's listed at all. Yet I could RDP to all 12 windows production servers and they are up and running properly!
I attempted to use this as a solution:
https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.troubleshooting.doc_50%2FGUID-BFD8C9BC-30FB-4A92-AFEC-2FC9FF387920.html
Which explains how to migrate the vm from one host to another in vcenter server. This process was only able to add a new instance of the VM to the other host in inventory and it was in the powered off mode!
This did nothing but complicate things so I was able to migrate the vm back to its orginal host using the same process in vcenter server - this made it show up on the original host so I vsphered into that host and removed the new instance from the hosts inventory and now was back at square one.
I also followed this resolution:
https://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1003490
to restart the management agents on each host but it still did not resolve the issue. both hosts servers are still showing NO vm's but yet the VM's are still up and running properly and they can be accessed via RDP.
Is there a non disruptive way to get them to re-register with the hosts and show in inventory?
Thank you in advanced for your suggestions!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
That seems a very small file, check all MDBs on the server file system
restart network management services on the host
restart vCenter Server service
restart network management services on the host
restart vCenter Server service
Hi,
you're welcome! I hope we'll have a chance to resolve this with you.
When speaking of storage paths, I was referring to the multiple storage paths you could have for each datastore, depending of your hardware and configuration.
But I don't know your type of hardware, Netgear RD5200 NAS, and if you use it in vSphere with iSCSI or NFS. I looked at its specs and I think there could be only one path for each LUN.
You could look at your storage paths health going in vcenter to hosts and clusters / manage / storage / software adapter (if using iSCSI) / and paths tab at bottom. You'll see all existing paths, and if they are dead or alive..
An important thing IMHO : this hardware is supported for ESXi 5.0 update 1 minimum, so tell us your ESXi build for I can check that you are in a supported configuration.
As said by Andrew this is a pretty small file for a vcenter db, but most of all it is weird that you can't find it ! If possible I would try to backup it up (the DB) soon before making changes.
And maybe check again DB file path, or if you miss something to find it, because if there is no file you should not have the possibiaccess the DB with SQL management studio! Did you connect to the right DB on the right SQL instance on the right server, etc... just to be sure.
you're welcome! I hope we'll have a chance to resolve this with you.
When speaking of storage paths, I was referring to the multiple storage paths you could have for each datastore, depending of your hardware and configuration.
But I don't know your type of hardware, Netgear RD5200 NAS, and if you use it in vSphere with iSCSI or NFS. I looked at its specs and I think there could be only one path for each LUN.
You could look at your storage paths health going in vcenter to hosts and clusters / manage / storage / software adapter (if using iSCSI) / and paths tab at bottom. You'll see all existing paths, and if they are dead or alive..
An important thing IMHO : this hardware is supported for ESXi 5.0 update 1 minimum, so tell us your ESXi build for I can check that you are in a supported configuration.
an odd thing is that i can see the DB file in sql management studio but when i try to find the file in explorer at the following location I am unable to find the file.Yes, odd!
As said by Andrew this is a pretty small file for a vcenter db, but most of all it is weird that you can't find it ! If possible I would try to backup it up (the DB) soon before making changes.
And maybe check again DB file path, or if you miss something to find it, because if there is no file you should not have the possibiaccess the DB with SQL management studio! Did you connect to the right DB on the right SQL instance on the right server, etc... just to be sure.
Hi again,
I find this kb with a quick google search, I think you should have a look at it, if not already done :
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007541
Cause : This issue may be caused by a corrupt inventory file on the ESX host
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003742
I find this kb with a quick google search, I think you should have a look at it, if not already done :
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007541
Cause : This issue may be caused by a corrupt inventory file on the ESX host
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003742
ASKER
Thank you all but this is nothing more than my own stupidity! I completely forgot that i had deployed a brand new host to this client and I obviously didnt cleanup well and left the old vcenter server and the 2 old hosts running! UG So sorry for wasting your time and thank you again!
ASKER
Thanks!
Hi,
ok, you're welcome.
Well, you found the explanation, that's all what matters!
ok, you're welcome.
Well, you found the explanation, that's all what matters!
ASKER
I am using sql express for vcenter server and the vim_vcdb.mdb file is 485 MB.
an odd thing is that i can see the DB file in sql management studio but when i try to find the file in explorer at the following location I am unable to find the file.
C:\Program Files\Microsoft SQL Server\MSSQL10_50.TOCTTARG
Any idea why this is?
Mr tortur - thanks for your response as well!
I did not try deleting them from inventory and readding them yet and i am unsure why this happened in the first place. I have a netgear 5200 NAS unit that is connected via a virtual switch and a physical switch in the rack to the ESXI host servers. I will need to log into the physical switch to investigate if it went down at some point recently.
The storage path is up and running and browsable with no problems so it looks like the datastore connection to the host is fine at this time.
Vcenter is virtual and is itself orphaned in vcenter server????
Scott,
I am not sure the problems is with vcenter server since when i log into each host seperately there are no Vm's listed so I dont beleive disconnecing and reconnecting the managed host in vcenter server will resolve the issue. Also thanks to you scott for responding!