Missing FLOW data in portal for some devices that show other SNMP data

Products

• CA Performance Management
• Network Observability

Issue/Introduction

Stacked protocol Trend Out/In data does not populate in the DX NetOps Portal for specific devices, even though SNMP metrics like interface utilization are appearing correctly.

This often indicates an ID translation issue where the Portal cannot map a global item to the Network Flow Analysis (NFA) data source.

Symptoms

In the PCService.log or wrapper logs, the following informational errors appear:

INFO | jvm 1 | Reason: {Global item ID: #### has no local data source translation. Data source ID: #### is not aware of the Global item.}

Health Status: {UNSUPPORTED_ITEM}

Additionally, the DMService.log may show:

ERROR | com.ca.im.rib.engine.query.tgt.TargetedRIBQueryInvoker | ID Translation issue

Environment

DX NetOps :: All Supported Versions

Cause

These are informational errors noting that an item does not have an item on a data source that corresponds to the PC item ID.

The problem device is not present in the NFA data source. Because NFA has no record of the device or its flows, the Portal cannot translate the Global ID into a local ID for NFA to retrieve flow data.

Common reasons for this include:

1. The device is not configured to send NetFlow/IPFIX data to the NFA Harvester.
2. A firewall is blocking flow data (UDP 9995 by default) from the device to the Harvester.
3. The device has not been discovered or added to the NFA console.

 

Resolution

These log items are informational, unless you are seeing a specific issue in a view/dashboard/context page that corresponds with the error, they can be ignored.

Ensure the device is correctly sending flow data to the NFA Harvester:

1. Verify the device configuration to ensure it points to the correct Harvester IP and port.
2. Confirm that network firewalls allow traffic from the device to the Harvester.
3. Log into the NFA Console and verify the device appears under Administration > System > flow Statistics.
4. Once the device is present in NFA, the Portal will automatically synchronize and begin displaying flow metrics.

Additional Information

If the item is missing from the NFA data source, make sure it is configured to send flow data to the NFA harvester so that it will be added to portal.

For further assistance, see [Contact Broadcom Support].