Interface is shown in the Data Aggregator component view but not in Dx NetOps Portal or no data is seen for interface

Products

• 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 Dx NetOps Portal.  Or you see the interface in the DA and Dx NetOps Portal but there is no data for the interface, yet the interface is polling successfully.

Environment

DX NetOps CAPM all releases

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 Dx NetOps Portal, and the not present item could take precedence when viewing or requesting data from the DA.

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 23.3.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 item. This setting is ONLY needed if you need to report on Not Present items (this includes OpenAPI).
     If you do not need to report on Not Present items, then this option should not be selected. Without this selected, this issue does not occur.

2) Remove the not present item:

TechDocs : DX NetOps 23.3 - 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

Additional Information

To list all the present and not present interfaces on a device, a tunneled get request can be used:

URL:  PROTOCOL://DA:PORT/rest/ports/filtered
METHOD: POST
Content-Type: application/xml
BODY:
<FilterSelect xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="filter.xsd">
      <Filter>
           <DeviceComponent.DeviceItemID type="EQUAL">DADEVICEIDHERE</DeviceComponent.DeviceItemID>
      </Filter>
      <Select use="exclude"  isa="exclude">
           <Item use="exclude"> 
                <Name use="include"/>
           </Item>
           <DeviceComponent use="exclude">
              <IndexList use="include"/>
            </DeviceComponent>
            <Retired use="include"/>
            <Pollable use="exclude">
                <IsPolled use="include"/>
                <IsExcludedFromReports use="include"/>
            </Pollable>
      </Select>
</FilterSelect> 

In the REST body, you can see: DADEVICEIDHERE

You'd replace that with the ItemID of the device from the Monitored Devices device admin page on the Details tab.

Then look for interfaces with the same index where one has a retired timestamp and one does not. The retired one would be the not present interface and will also be isPolled false, and IsExcludedFromReports = false if "Synchronize component items that are not currently present on the monitored device" is enabled.

Example pair:

Not Present interface:

  <Port version="1.0.0">
        <ID>22776</ID>
        <DeviceComponent version="1.0.0">
            <IndexListList>
                <IndexList>19612</IndexList>
            </IndexListList>
        </DeviceComponent>
        <Pollable version="1.1.1">
            <IsExcludedFromReports>false</IsExcludedFromReports>
            <IsPolled>false</IsPolled>
        </Pollable>
        <Retired version="1.0.0">
            <TimeStamp>Wed Apr 12 6:16:44 2023 +0000</TimeStamp>
        </Retired>
        <Item version="1.0.0">
            <Name>eth0/2</Name>
        </Item>
    </Port>
    
Present interface:

     <Port version="1.0.0">
        <ID>37082</ID>
        <DeviceComponent version="1.0.0">
            <IndexListList>
                <IndexList>19612</IndexList>
            </IndexListList>
        </DeviceComponent>
        <Pollable version="1.1.1">
            <IsExcludedFromReports>false</IsExcludedFromReports>
            <IsPolled>true</IsPolled>
        </Pollable>
        <Item version="1.0.0">
            <Name>eth0/4</Name>
        </Item>
    </Port> 

For more information on tunneled get requests see:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/performance-management/22-2/apis/data-aggregator-rest-webservices.html