Interface is shown in the Data Aggregator component view but not in CA Performance Center (CAPC) or no data is seen for interface

Products

• CA Infrastructure Management
• CA Infrastructure Management
• CA Performance Management - Usage and Administration

Issue/Introduction

An interface is shown in the Data Aggregator (DA) component view but not in CA Performance Center (CAPC).  Or you see the interface in the DA and CAPC but there is no data for the interface, yet the interface is polling successfully.

Cause

Synchronize component items that are not currently present on the monitored device is enabled for the DA data source and the items are not being managed per the documentation.

This can cause a present and not present  DA interfaces to consolidate to the same item in CAPC, and the not present item could take precedence when viewing or requesting data from the DA.

Environment

DX NetOps CAPM all releases

Resolution

If you are going to check "Synchronize component items that are not currently present on the monitored device" for the Data Aggregator data source you must manage the items per the documentation:

Broadcom TechDocs : CAPM 21.2.x - Configure a Data Source

Synchronize component items that are not currently present on the monitored device

When the Data Aggregator finds a device component that is no longer present in the environment, that status of the component is set to Not Present.  By default, the Data Aggregator does not synchronize these items because data can no longer be collected for the item. Historical data that has not reached the data retention limit is still available for these items.

Important! If the properties of an active component match the identifying properties of the not present component, the components are indistinguishable.  Data from the old component might contribute to group based dashboards instead of data from the active component. Enable this feature only under the following circumstances:

• You want to report on historical data for items that are no longer present in the environment.
• You can ensure that the not present item does not conflict with an actively monitored item.
• You can identify the not present items so that you can exclude the items from groups.

As noted, you need to manage conflicts if this is set.

When you have a conflict you can do one of three things:

1) Choose not to sync not present items if you really don't need to.

2) Remove the not present item:

TechDocs : DX NetOps 21.2 - Delete Components That Are Not Present

3) If you really need both, split the interfaces by adding an additional index:

KB : How to split interfaces when a not polled interface consolidates with a polled interface in DX Netops Performance Management