How are licenses used and implemented in DX NetOps?
search cancel

How are licenses used and implemented in DX NetOps?

book

Article ID: 41798

calendar_today

Updated On:

Products

CA Spectrum DX NetOps

Issue/Introduction

This article will outline how licenses are used and calculated within the various components of DX NetOps.

Environment

All Supported Releases

Resolution

Deployment for Fault Monitoring

Count all discovered devices from all landscapes (e.g. entity type of ROUTER, SWITCH, WIRELESS_CONTROLLER, CONTROLLER, VIRTUAL_MACHINE, HYPERVISOR, APPLIANCE) with interfaces, as per the following formula:

 

<= 200 interfaces = 1 Device
> 200 and <= 400 interfaces = 2 Devices
>400 interfaces = 3 Devices

 

 
Exceptions:
- Wireless Access points (entity type, ACCESS_POINT) shouldn’t be considered as pingable, rather accounting will be done as 5 AP’s = 1 Device. Also, they’re counted in a segregated manner, depending on the source if it’s SNMP or via VNA.
- The inventory from UIM coming via Spectrum Gateway probe shouldn’t be considered as pingable, rather accounting will be done as per standard device formula.
- Do Not count, models representing devices managed via traps in Southbound Gateway.
- Do Not count any AppNeta monitoring point Appliance as device.
- Do Not count devices like VMs from SysEdge / AIM’s e.g. vCenter, UCS.
 

In Spectrum we have a usageTelemetryV2 REST call which returns the last saved daily telemetry record.

e.g. https://<OneClick_Server>:<port>/spectrum/restful/telemetry/usageTelemetryV2
 

In Spectrum we now have a usageTelemetryRange REST call which returns the high water mark for every month of the last quarter or the high water mark of the given date range.

e.g. https://<OneClick_Server>:<port>/spectrum/restful/telemetry/usageTelemetryRange?startDate=2024-08-01&endDate=2024-10-30
 
In the above example (Date range is spread across 3rd and 4th CY quarters) - Monthly high water mark data of August, September, October months with 4th quarter's high water mark data (as endDate falls in 4th quarter) will be returned. (only 1 quarterly record)


Deployment for Performance Monitoring

Count all devices from DA (e.g. entity type of APPLIANCE, CONTROLLER, GATEWAY, HYPERVISOR, MONITORED_TARGET, ROUTER, SWITCH, VIRTUAL_MACHINE, VROUTER, VSWITCH, WIRELESS_CONTROLLER) with interfaces, as per the following formula:

<= 200 interfaces = 1 Device
> 200 and <= 400 interfaces = 2 Devices
>400 interfaces = 3 Devices

Any discovered device, without an interface should be considered as a ‘Pingable’, (e.g., entity type CAMERA) where accounting should be done as 10 Pingable entitles = 1 Device.

Count a retired item if we have as-polled data retained for the item. If as-polled (rate data) is set to 45 days and the item is retired, count it if the item is within the 45 days retention period. After the retention period, stop counting it.

Exceptions:
- Do Not count devices from CAMM.
- Wireless Access points (entity type, ACCESS_POINT) shouldn’t be considered as pingable, rather accounting will be done as 5 AP’s = 1 Device.
- Do Not count any AppNeta monitoring point Appliance as device.
- Do Not count devices like VMs from SysEdge / AIM’s e.g. vCenter.
 

Deployment for Flow Monitoring

A Device with up to 5 IPflow interfaces is counted as 1 Device. If the Device has greater than 5 IPflow interfaces, to determine the number of licenses needed, divide the total number of IPflow interfaces by 5 and round up to the next whole number, with a maximum capped value of 3.

e.g. A router having 6 to 10 interfaces enabled for IPflow requires 2 licenses, while a router having 18 interfaces enabled for IPflow requires 3 licenses.
 

Deployment for Fault and SDx Monitoring:

In this scenario, VNA is creating non-SNMP devices in Spectrum, like SDN_ROUTER, SDN_SWITCH …etc. which are counted as real devices using the following formula:
<= 200 interfaces = 1 Device
> 200 and <= 400 interfaces = 2 Devices
> 400 interfaces = 3 Devices

Additionaly, apply the treatment of 10:1 ratio for counting number of devices, against VNA entity types of CAMERA, ENVIRONMENTAL_SENSOR, ACI Endpoint, WIRELESS_SENSOR.
 

Deployment for SDx Monitoring with Portal

Follow the guidelines from Section 2. Additionally, Wireless Access points (entity type, ACCESS_POINT) shouldn’t be considered as pingable, rather accounting will be done as 5 AP’s = 1 Device. Any device coming from Data source VNA, without an interface should be considered in a special manner, (e.g., entity type CAMERA, ENVIRONMENTAL_SENSOR, WIRELESS_SENSOR) where accounting should be done as 10 such entitles = 1 Device.