Evaluating license and product usage trends

You can track your usage of BMC Server Automation agents and view trends in agent deployment through the Health and Value Dashboard and by generating reports using BLCLI commands. Since RSCD agents do not need to be explicitly licensed, the agent usage information that you obtain in these reports can be used for the evaluation of your product licenses.

The topic includes the following sections:

The video at right demonstrates the process of generating and interpreting license and agent usage reports.

  https://youtu.be/HSZlMuD-gE8

Note

The methods described in this topic are relevant for BMC Server Automation versions 8.7 and later. If you are still using earlier versions of RSCD agents in your environment, note the following guidelines:

  • For RSCD agents of versions 8.2 until 8.6, BMC recommends using a script provided by BMC; obtain this script from BMC Communities.
  • For very old RSCD agents, version 8.1 or earlier, you must still license the agents, as described in Licensing RSCD Agents from older product versions.
    If you upgrade an agent from a pre-8.2 release, the agent becomes fully licensed.

List of license types

The following table lists the types of licenses and corresponding entitlements.

LicenseApplies to these job types
BMC BladeLogic Server Automation Suite  All types of jobs
BMC Server Automation - License Add-onAll types of jobs
BMC BladeLogic Server Automation – Compliance Module
Compliance, SCAP, Audit, Snapshot
BMC Server Automation – Compliance License Add-on
Compliance, SCAP, Audit, Snapshot
BMC BladeLogic Server Automation – Configuration ModuleNSH, Deploy
BMC Server Automation – Configuration License Add-onNSH, Deploy
BMC BladeLogic Server Automation – Provisioning ModuleBare Metal , Virtual Guest Job
BMC Server Automation – Provisioning License Add‐onBare Metal , Virtual Guest Job
BMC Server Automation – Patch License Add‐on
Patch Analysis

Licensing considerations in server management

Any server that you add in BMC Server Automation and on which you installed an RSCD Agent is counted for licensing purposes. As you manage your servers over time, ensure that you follow the proper procedures for adding and decommissioning servers, so that the licensing status of servers is updated accurately.

The following table provides guidelines for special scenarios in server management:

ScenarioGuidelines

The server was registered with an incorrect name or IP address, and you want to correct the server name.

OR

You want to change the server name to a fully qualified name.

First decommission the server that you originally registered, and only then add the server with its new name.

Otherwise, both the old and new server will be counted as two separate servers for licensing purposes.

A server is being deleted from the environment.

You need to delete a server from your environment. For example, you are deleting a VM from an ESX server or removing a physical server.

In such a case, remember to decommission the server. Otherwise, the deleted server will continue to be counted for licensing.

Evaluating product usage trends

On the Health and Value Dashboard, select the Product Usage Trends option:

When you select the Product Usage Trends option, the following report is displayed. There are two sections to the report:

  • License Usage Trends –This graph provides information about the number of BMC Server Automation licenses purchased against the number of licenses actually being used each month, for a period of one year (by default). The threshold line represents the number of BMC Server Automation Suite Level licenses that you have purchased.  Note that a device that has a valid BMC Server Automation agent installed or deployed is considered for license counts. A device that is enrolled but does not have an active agent installed on it, is not considered for license counts, although some jobs are run against such a device.
  • Agent Deployment Trends –This graph provides information about the number of BMC Server Automation agents that have been added (commissioned) against the number of agents that have been removed (decommissioned) each month, for a period of one year (by default).

You can also perform the following tasks for the graphs:

TaskDescription
To populate or refresh the graphs

To populate or refresh the dashboard, do one of the following:

  • Run the Dashboard Update Job from the console (Jobs > BMC Maintenance > Dashboard >  Dashboard Report Job).
  • Execute the following BLCLI command:
    blcli -v <profile name> -r BLAdmins Utility generateDashboardReport
Once the job or command completes successfully, the report will be populated.

To change the time period for the  License Usage Trends  graph

Run the following command using the BMC Server Automation Application Server Administration console (the  blasadmin  utility):

Dashboard LicenseInfoDisplayTimePeriod <months>

Where <months> is the number of months for which you want the report displayed. The default is 12 months.

Displaying the number of licenses trend line in the License Usage Trends graph

Run the following commands using the blasadmin  utility:

CommandUsed to...
show licenseusage Provide a list of types of licenses.
set licenseusage <licenseSKUType> <no. of licenses>

Set number of licenses for a particular module type, where <licenseSKUType> is one of the following:

  • NumberOfSuiteLicenses
  • NumberOfSuiteAddonLicenses
  • NumberOfComplianceLicenses
  • NumberOfComplianceAddonLicenses
  • NumberOfConfigurationLicenses
  • NumberOfConfigurationAddonLicenses
  • NumberOfProvisioningLicenses
  • NumberOfProvisioningAddonLicenses
  • NumberOfPatchAddonLicenses

For example:
set licenseusage NumberOfComplianceLicenses 15000

Generating summary and detail reports in CSV format for license usage

You can use the following BLCLI commands to generate license usage reports:

Before you begin

To generate license reports, the Health and Value Dashboards must be active and populated with data. If this is not the case, perform one or both of the following actions:

Generating reports within a specified relative date range

To generate summary and detail reports of active agents, and the kinds of jobs performed on these agents within a specified relative date range, enter the following BLCLI Utility command:

agentLicenseUsageReportByRelativeDateRange <reportFilePath> <relativeRangeValue>

Where:

  • reportFilePath is the path to the location where you want to write the CSV report and the filename. The report names will have _summary.csv and _details.csv as suffixes. For example: using /tmp/reportName would output reports names reportName_summary.csv and reportName_details.csv in the /tmp dir.
  • relativeRangeValue is the number of days, months, or years
  • daysMonthsOrYears is the relative time frame to use for the reports. You can choose day(s), month(s), or year(s)

The following example shows how to use this command to obtain a report for the last month.

blcli Utility agentLicenseUsageReportByRelativeDateRange /mydir/report 1 month

Generating reports within an absolute date range

To generate summary and details report of active agents and the types of jobs performed on these agents within an absolute date range, use following BLCLI Utility command:

agentLicenseUsageReportByAbsoluteDateRange < reportFilePath> <"startDateString"> <"endDateString">

Where:

  • reportFilePath is the path to the location where you want to write the CSV report and the filename. The report names will have _summary.csv and _details.csv as suffixes.  For example: using /tmp/reportName would output reports names reportName_summary.csv and reportName_details.csv in the /tmp dir.
  • startDateString is the start date for the report, enclosed in double quotes. Use the format "yyyy/MM/dd HH:mm:ss"
  • endDateString is the ending date for the report, enclosed in double quotes. Use the format "yyyy/MM/dd HH:mm:ss" or "" (an empty string) to indicate the current date and time.

The following example shows how to use this command to obtain a report for a specific date range:

blcli Utility agentLicenseUsageReportByAbsoluteDateRange /mydir/report "2010/01/12 01:02:04--‐0500" ""

Summary report example

The following is an example of a summary report that is generated in CSV format.

Reading the Summary report

The Summary report presents monthly data for your servers, one row for each month, with the following columns:

Column

Description

Example

yyyymm

Year and month

2015-9

Max managed servers

Maximum number of servers active during the month.
The number of servers from last month is carried forward + new activations from this month.

16

Servers running configuration

Number of servers that used the Configuration feature during this month

4

Servers running compliance

Number of servers that used the Compliance feature during this month

0

Servers running provisioning

Number of servers that used the Provisioning feature during this month

4

Servers running patching

Number of servers that used the Patching feature during this month

0

# of servers added

Number of new servers that were added this month

16

# of servers decommissioned

Number of servers that were decommissioned this month

3

Detailed report example

The following is an example of the detailed report that is generated in CSV format.

 Reading the Detailed report

The Detailed report presents monthly data for each server that was added or decommissioned during the month, in chronological order of commissioning/decommissioning. Each row presents data for one server during a specific month. For each server row, the following columns of data are displayed:

Column

Description

yyyymmYear and month
Time stampThe date and time (month/day/year and HH:MM) that the server was added
Device IDThe device ID of the RSCD agent on the server
Server nameServer host name or IP address
Date createdThe date and time that the agent was commissioned on the server
Date modifiedThe date and time that server definitions were modified most recently
Activation

   Activation index

Indication of server activation status:

  • 1 — agent commissioned on the server
  • -1 — agent decommissioned on the server

Note that the servers are organized in chronological order of commissioning/decommissioning.

   Cumulative managed server countA running total of the number of managed servers (that is, a row-by-row sum of activation indexes)
Configuration module

   Configuration index

Indication of usage of the Configuration module:

  • 0 — This server did not use the Configuration module
  • 1 — This server used the Configuration module
  • -1 — This server was using the Configuration module and it is now decommissioned
   Cumulative ConfigurationA running total of the number of servers using the Configuration module (that is, a row-by-row sum of Configuration indexes)
Compliance module
   Compliance indexIndication of usage of the Compliance module:
  • 0 — This server did not use the Compliance module
  • 1 — This server used the Compliance module
  • -1 — This server was using the Compliance module and it is now decommissioned
   Cumulative ComplianceA running total of the number of servers using the Compliance module (that is, a row-by-row sum of Compliance indexes)
Patching module
   Patching indexIndication of usage of the Patching module:
  • 0 — This server did not use the Patching module
  • 1 — This server used the Patching module
  • -1 — This server was using the Patching module and it is now decommissioned
   Cumulative PatchingA running total of the number of servers using the Patching module (that is, a row-by-row sum of Patching indexes)
Provisioning module
   Provisioning indexIndication of usage of the Provisioning module:
  • 0 — This server did not use the Provisioning module
  • 1 — This server used the Provisioning module
  • -1 — This server was using the Provisioning module and it is now decommissioned
   Cumulative ProvisioningA running total of the number of servers using the Provisioning module (that is, a row-by-row sum of Provisioning indexes)

Was this page helpful? Yes No Submitting... Thank you

Comments