Disparity for last flow between NFA Console and CA PC Monitoring status

Products

• CA Network Flow Analysis (NetQos / NFA)

Issue/Introduction

For "Disabled" interfaces that where previously enabled, the "Last Flow" time in Netops Portal doesn't match the "Last Updated" time displayed on the interface within NFA itself. The "Last Updated" time in NFA stopped updating when the interface was Disabled, but the "Last Flow" time in Netops Portal continued to update.

Cause

This is working as designed in the scenario where an interface that still has incoming netflow is marked as "Disabled." 

The two different screens show different values because they're actually monitoring different things.

Resolution

The "Last Updated" time isn't updating in NFA because we don't have any data points for it in "/datafiles" (because the interface is Disabled).  However, the "Last Flow" time in CAPM is still updating because it is looking at the data from the *.FLT files that the Pump service gets from the Harvester, and this is showing that netflow was present (even though the interface is marked as Disabled).