I think the subject states the question fully, but said another way:
if there are two sites, each with it's own vcenter, can one vCops instance connect to both? Or would we by definition have to have 2 vCops installations/licenses in this situation?
No adding a second vCenter does not replace the first one. Not sure why it happened with mine. the second time it worked fine. So i think i did something wrong.
So the bottom line is you can go ahead and do it. It should work.
If you found my answer useful, consider awarding points by choosing correct and helpful answers
During installation you register VCOPS to a particular vCenter so Im fairly positive that its one VCOPS per vCenter.
You can connect vC Ops to multiple vCenters. The first vCenter you register to using vC Ops is used for licensing for the entire solution. You can have multiple vC Ops appliances for each vCenter. However, the LAST (most recent) vC Ops that was registered to that vCenter will have the extension registered and be visible using the Web Client.
I'm not sure how the licensing works but i have connected two vcenters in my vCOPS. I think i used enterprise license. We partners anyway get evaluation licenses so not really sure if it works with standard. But if you need to add the second vCenter you will need to have Custom UI access and also you need to add the new vCenter using the VMware adapter.
Additional vCenters are added to vC Ops via the /admin UI, not the /custom UI.
I really don't remember well. But I'm sure you can add more than one.
You can also add it from Custom UI. If you add the second vcenter from admin UI it will replace the existing connection. Just confirmed it!
Folks:
1) When using the vApp flavour of vcops, Registration/Unregistration of VCs should be done only via Admin-UI.
You shouldn't tocuh the adapter-instances in custom-ui. Only updates from AdminUI will properly propagate across the product!
(if one is using the standalone flavour, there is no adminUI not vsphereUI. There you can use the adapter-instances page. But again - only for standalone, and NOT for the vApp)
2) AFAIK, only the total # of VMs being monitored is what matters from licensing perspective. Meaning, you can register multiple VCs, as long as the total VMs across all VCs is <= the license.
Oh ok. i did not know that point. I just wanted to mention it can be done. thanks for the info anyway
And yes the licensing works on the number of VM's. I tried adding it from admin UI and it replaced the first vcenter. Not sure what went wrong. Second time i did it it worked fine.
ok -
so, it seems we can register multiple vcenters. But since I right now talking about standard, and since standard does not have a custom UI (I believe that is correct, is it not?) then -- does adding a 2nd vcenter in the admin UI "replace" the original one, or not?
If this works, that would be so great - to be able to see stats from both vcenters! Yes!
No adding a second vCenter does not replace the first one. Not sure why it happened with mine. the second time it worked fine. So i think i did something wrong.
So the bottom line is you can go ahead and do it. It should work.
If you found my answer useful, consider awarding points by choosing correct and helpful answers