vRealize Deployment

[ChevUribe]

There is one deployment where there are 3 sites with each vCenter and 2 datacenters each.

Site 1:

1 vCenter

2 Datacenter (FT enabled clusters)

20 Hosts

300 VMs

Site 2:

1 vCenter

2 Datacenter (FT enabled clusters)

30 Hosts

400 VMs

Site 3:

1 vCenter

2 Datacenter (DRS enabled clusters)

10 Hosts

100 VMs

1. Can I deploy 1 vROPs appliance in Site 3 and add the 3 vCenter Servers in different sites to manage?

2. For the Licensing of vROPs, Can I use the VSOM Enterprise Plus license of Site 2 since they have a the most number of licenses?

[rcporto]

1. Can I deploy 1 vROPs appliance in Site 3 and add the 3 vCenter Servers in different sites to manage?

Yes, each vROPs can support up to 50 vCenter instances. But depending of the bandwidth available between site, you will may need to deploy a vROPs remote collector in each site. For vROPs sizing guidelines, see: vRealize Operations Manager 6.5 Sizing Guidelines (2148829) | VMware KB

2. For the Licensing of vROPs, Can I use the VSOM Enterprise Plus license of Site 2 since they have a the most number of licenses?

For each group of hosts you can assign different license through the use of licensing groups, see: Nothingworks: Using vRealize Operations License Groups

[ChevUribe]

What will happen if I use the vSOM license of Site 2 to license vROPs in Site 3 and did not do the license groups as stated?

Will I not get ACCURATE reporting for Site 1 and 3 components?

Thanks!

[ChevUribe]

UP!

[sxnxr]

It would in theory work. I am not a legal licence expert but i think what you are asking would violate the licence agreement.

If i am reading right you would deploy the 30 vSOM licences to site 2 but want to use the vrops portion of the vsom licences in site 1 and 3. Doing this i think would violate the licencing because the vrops licence can legal only monitor what the vsom licence is assigned to (in this case site 3) dont forget all the vsom licence is is the base esxi licence with the vrops bundled in so where you apply the base licence is where you can monitor with the vrops part.

There is nothing stopping you (if all 3 sites are part of the same company) splitting the 30 vsom licences in two ( 1 x 10 and 1 x 30) and assigning them to site 1 and 3) and combining site 1 and site 3 into one 3 licence and assigning to site 2.

Again the hosts where you assign the vsom licence is the only place you can legally monitor. You can run vrops on any of the sites it does not need the underlining hosts it is running on to be vsom licenced

Hope this answers your question

[ChevUribe]

The reason why we're trying deploying VROPs in Datacenter 3 using VSOM license in Datacenter 2 because Datacenter 1 and 2. are running FT enabled clusters. There is no available hosts that can be added on Datacenter 1 and 2 for vROPs. vROPs needs for DRS to be enabled right?

If you say legally monitor, what would it mean?

[sxnxr]

I hope this is what you are after.

From a licence point of view it does not matter where you deploy VROPS what does matter is what you monitor. As long as you monitor the hosts that are VSOM licences then you are fine.

What i mean legally is it does not matter what vrops is licences under ( VSOM, vCloud suite etc) the license key is added into vrops so in theory you could use the key and monitor hosts that are esxi standard edition but technically that is not legal or if the key is for unlimited licences you could monitor every environment regardless of the hosts licences. It is left up to the company to manage the licences within the end user agreement.

So long story short deploy vrops where you need it and only monitor what you are licenced for

DRS was needed in the 5.x days as the deployment created a resource pool for the two vms. It was the resource pool that required DRS not vcops ( you could get around it by deploying to a esxi hosts not managed by vcenter and then add the host in) now the deployment does not create a resource pool you wont get the error. I have not tested this for 6.x so i hope i am not wrong