Configure to Send Usage Data

You can configure
DX NetOps Performance Management
to collect and send telemetry data, or product usage and system configuration data Broadcom
You can configure
DX NetOps Performance Management
to collect and send telemetry data, or product usage and system configuration data, to Broadcom. Telemetry is a foundational element of the Enterprise Software Portfolio License Agreement (PLA) subscription model. Broadcom uses the data to offer additional products from the portfolio in support of the PLA subscription model.
If you are licensed to use
DX NetOps Performance Management
under a PLA, you must activate
DX NetOps Performance Management
and configure it to collect and send
DX NetOps Performance Management
-specific usage data. If you are licensed to use
DX NetOps Performance Management
under a standard license that the Broadcom Support site issues, you can consent to
DX NetOps Performance Management
collecting and sending usage data. By default,
DX NetOps Performance Management
does not collect and send usage data.
You can access the collected usage data on the
System Status
page.
For more information about how to access usage data, see View the Health of the System.
DX NetOps Performance Management
also stores uploaded metrics in a file that is located in the
<
PC Install Directory
>/PC/bin/esdplatelemetry/
directory.
DX NetOps Performance Management
does
not
collect personally identifiable information (PII) or sensitive information, including user data.
For more information about how
DX NetOps Performance Management
collects and uses personal information, see our Privacy Policy.
What Data Do We Collect
The following table describes the data that customers provide:
Data
Description
Opt-In (Yes/No)
Send diagnostic and usage data to Broadcom. If you have a PLA in your contract with Broadcom, specify
Yes
to consent to
DX NetOps Performance Management
collecting and sending usage data.
PLA Agreement (Yes/No)
If you have a PLA in your contract with Broadcom, specify
Yes
.
Domain name
Your company's domain name (the last part of your company's email address). For example, in [email protected], the domain name is company.com.
Enterprise site ID
Your company's site ID that is listed on the Broadcom Support portal.
Description
(Optional) Specify a department or cost center that you use for internal tracking. For example: IT-Sales-1234.
Use Proxy (Yes/No)
(Optional) Details of the proxy server and user credentials to access the proxy server. The user credentials are required only if your proxy requires it. If the
api.segment.io
Segment endpoint is not reachable through port 443 from this machine, you can configure a proxy server to transmit anonymous usage data. Provide these details only when the telemetry service cannot be reached through the outgoing port 443 from
DX NetOps Performance Management
.
Selecting
Yes
provides you the following fields to enter proxy server credentials:
  • Proxy URL:
    (Optional) The URL proxy address. Use a secure protocol (https), for example: https://myproxy.company.com.
  • Proxy Username:
    (Optional) Specify the username on the proxy to direct usage data through.
  • Proxy Password:
    (Optional) Specify the password on the proxy to direct usage data through.
The following table describes the data that
DX NetOps Performance Management
generates:
Field
Description
version
Specifies the data source version.
tenant_count
Specifies the number of tenants that are associated with this data source.
domain_count
Specifies the number of IP domains that are associated with this data source.
active
Specifies if the data source is enabled.
source_id
Specifies the unique identifier for the represented data source.
active_device_count
Specifies the number of active devices that are associated with this data source.
retired_device_count
Specifies the number of retired devices that are associated with this data source.
monitored_item_count
Specifies the count of monitored items that are associated with this data source.
consumed_license_count
Specifies the count of the items consuming the licenses.
ha_da_enabled
Indicates whether the data aggregator is configured for a fault tolerant environment.
data_collector_count
Specifies the count of data collectors that are associated with this data source.
wap_count
Specifies the count of wireless access points that are associated with
DX NetOps Virtual Network Assurance
. This value influences the number of license items that
DX NetOps Virtual Network Assurance
consumes in the usage data.
NetOps Portal
usage data takes into account only the items that are synced to
NetOps Portal
. It does take into account the 200 ports per licensed device coming from
DX NetOps Spectrum
or the data aggregator.
CA Application Delivery Analysis
,
DX NetOps Network Flow Analysis
, and
DX NetOps Virtual Network Assurance
use different licensing count logic because the licensing agreements for those products count differently.
How Frequently Do We Collect the Usage Data
By default,
DX NetOps Performance Management
collects and stores usage data daily at 12.00 a.m. If the scheduler is not active at 12.00 a.m.,
DX NetOps Performance Management
collects the data only in the next day run. It collects the data only once per day.
How to Configure
DX NetOps Performance Management
to Collect and Send Usage Data to Broadcom
As an administrator, you can configure
DX NetOps Performance Management
to collect and send usage data to Broadcom either using
NetOps Portal
or using the REST API.
To configure using
NetOps Portal
, perform the following steps:
  1. Hover over
    Administration
    ,
    Configuration Settings
    , and then click
    Usage Data
    .
    The
    Usage Data
    page appears.
  2. Click
    Change Configuration
    .
    The
    Edit Usage Data Sharing Settings
    dialog appears.
  3. Complete the fields. If you have a PLA in your contract with Broadcom, specify
    Yes
    for the
    Opt-In
    field to consent to
    DX NetOps Performance Management
    collecting and sending usage data to Broadcom.
  4. Click
    Save
    .
To configure using the REST API, post the following to
http://<
PCHOST
>:<
Port
>/pc/center/webservice/insights/config
:
<Configure> <CompanyDomain>ca.com</CompanyDomain> <EnterpriseSiteID>105246</EnterpriseSiteID> <InternalIdentifier> IT Sales</InternalIdentifier> <Opt-In>true</Opt-In> <PLAAgreement>true</PLAAgreement> <UseProxy>false</UseProxy> </Configure>
If you have a PLA in your contract with Broadcom, consent to
DX NetOps Performance Management
collecting and sending usage data by setting the
Opt-In
property to
true
.
Specify a department or cost center that you use for internal tracking in the
InternalIdentifier
parameter. For example, "IT Sales."
More fields for using a proxy are
ProxyURI
,
ProxyUsername
, and
ProxyPassword
.
How you Know if
DX NetOps Performance Management
Failed to Collect or Send Usage Data
DX NetOps Performance Management
generates the
TELEMETRY_FAILURE (553)
event to indicate that it failed to collect or send usage data. It generates the
trapTelemetryFail (553)
trap to indicate that it failed to
successfully
collect and send usage data.