Interface Metrics display data in Octets or Bytes

Document ID : KB000095233
Last Modified Date : 28/03/2019
Show Technical Document Details
How can CA Performance Management be set to display Interface Metric data in Octets or Bytes?
Sometimes it is more useful to see actual data points rather than calculated percentages or averages.
All supported CA Performance Management releases
CA Performance Management comes with sample files that can be used to extend the Interface Metric Family Certifications.

These over-ride out of the box functionality. The results in the display of Interface Metrics as Octets or Bytes.

Two methods exist for implementation of this functionality.
  1. REST API using the XML code from the sample files as the body.
  2. Certification Installer directed to the XML sample file(s)
The simple solution is the Certification Installer which is what these instructions will focus on.

Important! Enabling Bytes metrics for the interface metric family may affect system performance.

Support strongly recommends testing in a non-production environment before going live with changes.

To download the Certification Installer:

Follow these steps:

  1. To verify that you have the latest version, download the certification installer from the following URL:

    Important! If you do not use the latest version, an error message appears when you try to install the certification.

    To run the Certification Installer on a Microsoft Windows system, log in as the Administrator, or run the installer as the administrator.

  2. Select a language for the installer.
  3. Specify the following information when the corresponding prompts appear:
    • DA Hostname
    • DA REST port
  4. To specify the type of installation, select Certification or Extension.
  5. Select one of the following options:
    • Install a single certification or extension.
    • Install a collection (ZIP) of certifications or extensions.
    • Install all the certifications or extensions in a directory.

      Note: The certification installer does not search subdirectories.

  6. Click Install.
    The installer checks the version of each certification or extension during the installation process. If the Data Aggregator indicates that a certification or extension is already installed, the installer tries to update the certification or extension.
    The installer imports the vendor certification or extension. If the installer fails to upgrade the certification or extension, an error appears to specify the reason for the failure. Review the error details in the log files that the installer creates in the Home directory of your computer.
To download the XML sample files:

Enable Bytes Metrics

To enable the Bytes, Bytes In, and Bytes Out metrics for individual vendor certifications, extend the certification. The XML to enable the metric is included in the following directory:


Select the file appropriate for your intended use.
Standard Speed Interface Vendor Certification? Use the bytes_ext_IfTableMib.xml
High Speed Interface Vendor Certification? Use the bytes_ext_IfXTableMib.xml

When the Certification Installer and required XML file are downloaded run the installer to import the extension.
Additional Information:
Certification Installer instructions: 

Enable Bytes Metrics instructions: 

Additional Notes regarding the potential impact from enabling this feature:
  • Impact is due to the need to calculate the values during polling cycles, send those to DA, and store them in DB. 
  • If they are baseline'd metrics, we also need to calculate the baselines, same for 95% or other defined values as well as rollups for the data. 
  • It's the same possible impact when adding any new metrics to the system. 
  • The reason it's called out in this area, is the tendency for many more interface items being present in the system than other items that would be impacted when adding metrics or custom certifications. As a result applying the changes to great numbers of interfaces can show deeper impacts than other custom certifications and changes applied to smaller sets of items. 
  • It's also called out as related to added overhead since we're already collecting bits data, and the bytes data is the same, just divide by 8. 
  • There is no formal testing performed that would allow me to provide a reference for what to expect. 
  • The decision to enable this comes down to:
    • Is the metric really needed when bits data is already available?
    • If it is required:
      • Set it up in a test environment.
      • Apply the change to a small set of interfaces to start.
      • Validate the metric data provides what is sought.
      • Expand the solution to more interfaces in sets vs. all at once, while also monitoring performance and resource usage.
      • Base production application of the change on those testing results. 

To have further testing and recommendations provided for this would be an Enhancement Request that can be submitted to the Community Forum as an Idea Request.