How do we calculate licenses correctly for VMware vCenter Server 6 Standard Instance when there is 1 license per managing cluster?

book

Article ID: 16796

calendar_today

Updated On:

Products

CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction



How do we calculate licenses correctly for VMware vCenter Server 6 Standard Instance when there is 1 license per managing cluster? 

Currently, CA Software Asset Manager miscalculates each ESXi host to have 1 instance. As per VMware's licensing rules, only 1 vCenter license is needed per managing cluster. This means 1 cluster having 18 physicals hosts would still require 1 instance license only. 

The problem is that CA Software Asset Manager  maps the hosts to a cluster, but since the cluster is not a 'device' per say, how do we enter the data to obtain a correct calculation? 

 

Environment

CA Software Asset Manager 4.x releases

Resolution

Perform the following resolution steps: 

1. In “Catalog > License metrics > Tiers” create a new tier

<Please see attached file for image>

src="/servlet/servlet.FileDownload?file=0150c000004AKhqAAG" alt="VmWare1.png" width="333" height="248">

2. Go to “Catalog > License metrics > Tiers > Tier ranges” and create following range

<Please see attached file for image>

src="/servlet/servlet.FileDownload?file=0150c000004AKhrAAG" alt="VMWare2.png" width="371" height="370">

3. Navigate to “Catalog > License metrics” and create a metric based on the new tier. Select “Topology” as scope to count each cluster only once.

 

<Please see attached file for image>

src="/servlet/servlet.FileDownload?file=0150c000004AKhsAAG" alt="VMWare3.png" width="394" height="387">

4. Make sure the product reported as installed on the ESX hosts has the new metric assigned

<Please see attached file for image>

src="/servlet/servlet.FileDownload?file=0150c000004AKhtAAG" alt="VMWare4.png" width="467" height="334">

5. Refresh effective demand (run cron job)

6. Check the result via the Topology graph.  See that the whole cluster counts as 1 demand

 

<Please see attached file for image>

src="/servlet/servlet.FileDownload?file=0150c000004AKhuAAG" alt="VMWare5.png" width="440" height="434">

 

 

 

Attachments

1558719137782000016796_sktwi1f5rjvs16v7m.png get_app
1558719135744000016796_sktwi1f5rjvs16v7l.png get_app
1558719133748000016796_sktwi1f5rjvs16v7k.png get_app
1558719131669000016796_sktwi1f5rjvs16v7j.png get_app
1558719083452000016796_sktwi1f5rjvs16v7i.png get_app