Configure to Send Usage Data
You can configure
DX NetOps Performance Managementto collect and send telemetry data, or product usage and system configuration data Broadcom
You can configure
DX NetOps Performance Managementto 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 Managementunder a PLA, you must activate
DX NetOps Performance Managementand configure it to collect and send
DX NetOps Performance Management-specific usage data. If you are licensed to use
DX NetOps Performance Managementunder a standard license that the Broadcom Support site issues, you can consent to
DX NetOps Performance Managementcollecting and sending usage data. By default,
DX NetOps Performance Managementdoes not collect and send usage data.
You can access the collected usage data on the
For more information about how to access usage data, see View the Health of the System.
DX NetOps Performance Managementalso stores uploaded metrics in a file that is located in the
PC Install Directory>/PC/bin/esdplatelemetry/
DX NetOps Performance Managementdoes
notcollect personally identifiable information (PII) or sensitive information, including user data.
For more information about how
What Data Do We Collect
The following table describes the data that customers provide:
Send diagnostic and usage data to Broadcom. If you have a PLA in your contract with Broadcom, specify
Yesto consent to
DX NetOps Performance Managementcollecting and sending usage data.
PLA Agreement (Yes/No)
If you have a PLA in your contract with Broadcom, specify
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.
(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.ioSegment 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.
Yesprovides you the following fields to enter proxy server credentials:
The following table describes the data that
DX NetOps Performance Managementgenerates:
Specifies the data source version.
Specifies the number of tenants that are associated with this data source.
Specifies the number of IP domains that are associated with this data source.
Specifies if the data source is enabled.
Specifies the unique identifier for the represented data source.
Specifies the number of active devices that are associated with this data source.
Specifies the number of retired devices that are associated with this data source.
Specifies the count of monitored items that are associated with this data source.
Specifies the count of the items consuming the licenses.
Indicates whether the data aggregator is configured for a fault tolerant environment.
Specifies the count of data collectors that are associated with this data source.
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 Assuranceconsumes in the usage data.
NetOps Portalusage 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 Spectrumor the data aggregator.
CA Application Delivery Analysis,
DX NetOps Network Flow Analysis, and
DX NetOps Virtual Network Assuranceuse different licensing count logic because the licensing agreements for those products count differently.
How Frequently Do We Collect the Usage Data
DX NetOps Performance Managementcollects and stores usage data daily at 12.00 a.m. If the scheduler is not active at 12.00 a.m.,
DX NetOps Performance Managementcollects the data only in the next day run. It collects the data only once per day.
How to Configure
DX NetOps Performance Managementto Collect and Send Usage Data to Broadcom
As an administrator, you can configure
DX NetOps Performance Managementto collect and send usage data to Broadcom either using
NetOps Portalor using the REST API.
To configure using
NetOps Portal, perform the following steps:
- Hover overAdministration,Configuration Settings, and then clickUsage Data.TheUsage Datapage appears.
- ClickChange Configuration.TheEdit Usage Data Sharing Settingsdialog appears.
- Complete the fields. If you have a PLA in your contract with Broadcom, specifyYesfor theOpt-Infield to consent toDX NetOps Performance Managementcollecting and sending usage data to Broadcom.
To configure using the REST API, post the following to
<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 Managementcollecting and sending usage data by setting the
Specify a department or cost center that you use for internal tracking in the
InternalIdentifierparameter. For example, "IT Sales."
More fields for using a proxy are
How you Know if
DX NetOps Performance ManagementFailed to Collect or Send Usage Data
DX NetOps Performance Managementgenerates 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
successfullycollect and send usage data.