hi,
i need some help with my vcops.
i have two vcenters, both are physical machines, i register the first vcenter in Vcops and then when i try to register the other one he says that the UUID from the vcenters are the same.I can´t register both, if i try to register the other one that is already registered drops the connection from vcops.
thanks
it's possible that one was cloned from the other and then upgraded to 2008...
I dug up a bit and couldn't find a 'clean' way to change the UUID
Besides reinstall, you can change the UUID value in the file, and then reset the VC database like that http://kb.vmware.com/kb/2031295
But you still loose all data in VC, so reinstall is a better option.
It's worth checking with vmware support, they might know a better way.
Hi
Welcome to VCOps communities. Couple of questions:
1) Are the two vCenters come from a common image (one installation)?
2) Are you using Admin UI to register them or you are registering them as separate adapters from Custom UI?
3) Which version of VCOps you are using?
Thanks,
Alex D.
Hi!
thanks for the answer!
1) No the vcenters are physical machines, with different versions of windows!
2) I´m using admin UI to register
3) i´m using Vcenter Operations Manager enterprise 5.6 ( my vcenter is 5.0)
thanks!
Leandro
Hi tharosfire,
the UUID is the unique identifier of each virtual center instance, which is generated upon it's installation.
most likely you have cloned one setup from the other, hence your UUIDs are the same.
there is no way to register both of them with vCenter Operations, as UUID is what's used internaly to identify different vCenters.
You can either:
-reinstall one of your vCenters
- try to update UUID of a vCenter. I am not quite sure how/if this can be done.
It is also possible that there's something else wrong with your setup though...
For example, if you've had one of those VCs registered already, and data was collected, you *might* also get such error.
Additional info on what you did might help.
Are they linked vcs? did you already try to connecting once before and got hungup? Might be a hangover from that attempted connection.
"For example, if you've had one of those VCs registered already, and data was collected, you *might* also get such error.
Additional info on what you did might help"
yes, this could have happened, I'm deploying the vcops again, i unregistered all vcenters, deleted the vapp. let´s see if this would help.
tomorrow i will try register the vcenters again. my link to the other vcenter is down so i can´t test right now.
thanks for all the answers! tomorrow i update you guys!
Leandro Bertolino
No they are not linked!
thanks!
Leandro Bertolino
i´ve reinstalled vcops and the problem remains the same
don´t know what to do!
this is the massage when i try to register
thanks
So it seems that most likely, somehow, you have both the UUIDs the same
You can't do anything from vc_ops side to rectify the situation You can reinstall one of the VCs or try to change it's UUID
See below KB:
It´s strange because they unique id are already diferent. one is 7 and the other is 55.
reinstall one of the vcenters is not a good idea, one has 700 vm and the other 500 vm, i think 20 peoples are using this vcenter right now.
Hmm, so maybe that's not exactly the UUID there (cause it's not a one-digit, but a long string of numbers/chars, like "3CA1EC1B-676A-42C8-867F-4DAD4F462778").
one place to look it up should be on the VC machine, in a file like this:
%ALLUSERSPROFILE%\All Users\Application Data\VMware\VMware VirtualCenter\instance.cfg
can you check on your systems whether that is the same or different for both VCs, to clarify the situation
Not very probable but a wild guess from my side:
Are you absolutely sure that the two IP addresses go actually to two VCs?
Probably open a VI client to the two IPs to verify they are actually two different VC servers.
Alex D.
yes, i think it´s just a identifier for the vcenters, i will talk to my client to see what i can do, i think i not going to add this vcenter to the vcops.
if i only restart one of the vcenters the uuid will change?i think this is a possible try.
thnaks
UUID won't change if you restart the VC. It is persistent between restarts.
vmware team.... is it possible to use this KB (
to remove the data and allow him to move ahead without re-installs?
well, he sees the erro even in fresh install of vcops, where the internal DBs are clean... so nothing to cleanup
i looked up for the files, and this is very strange the uuid on both files are the same!
they are physical machines, with diferent instalation, diferent windows versions 2003 and 2008.
it's possible that one was cloned from the other and then upgraded to 2008...
I dug up a bit and couldn't find a 'clean' way to change the UUID
Besides reinstall, you can change the UUID value in the file, and then reset the VC database like that http://kb.vmware.com/kb/2031295
But you still loose all data in VC, so reinstall is a better option.
It's worth checking with vmware support, they might know a better way.
yes, my client will reinstall from a new machine the vcenter with windows 2003, he´ll add the vcenter to the vcops later.
thanks for the help gradinka!!
thanks to the others too!!