Errors in System Status page in NetOps portal for NFA datasources


Article ID: 197109


Updated On:


CA Network Flow Analysis (NetQos / NFA) CA Performance Management - Usage and Administration


Performance Management 3.7.2 upgraded to NetOps 20.2.1.

The upgrade went fine with no errors.

On system status page the "Network Flow Analysis" section shows as "Failed" with the NFA data sources having status "Unreachable". 

NFA 10.0.4 (new install)

Also configuration changes in CAPC to the Harvester/Application settings in the NFA data source configuration page on the Netops Portal result in a 500 error when saved


-TCP port 8981 [NFA data read via OData API] needs to be open between CA PC / CA NPC Console  and NFA console.

-Make sure "CA NFA Odata Service" is running on the NFA Console

-Confirm that the NFA console is configured with an IPV4 address and not IPV6 address.




Release : 20.2


NFA 10.0.x


Message "Failed in sending REST: http://[0000:0000:0000:0000:0000:0000:0000:0001]:8981/odata/api/AuthToken"

Can also verify by checking in NetOps portal if the NFA datasource is recorded with ipv6 address for OdataUrl

To add/modify the reg entry through UI,  can refer to the following screenshots:

If the environment doesn't have the registry entry called 'DisabledComponents', which is required and should have appropriate value can add the entry through the command line as mentioned in the article above or can use the regedit UI.

Please take backup of registry before any changes 

Change the name to 'DisabledComponents':

Edit the value as per the requirement (refer the article). (Hex 20 for 'Prefer IPv4 over IPv6. Hex FF for 'Disable IPv6')

Note: Please make sure that the NFA console machine is restarted after the registry change. 


Port 8981 has to be open on the NFA console machine for communication to happen between CAPC and NFA for NFA admin pages and SystemStatus.

NFA documentation has updated for OData API port:

The NetOps documentation has been updated with the OData API port (8981) in the firewall configuration and also in requirements section:

Additional Information

NFA Admin->System Status Page shows errors from Watchdog Service but configuration is correct

KB: ConnectException invoking http://<nfa hostname>:8681/NFARS/ribsource/rib/soap?wsdl: Connection refused

KB: ConsoleEventProducer: Failed to forward events to Event Manager because The remote name could not be resolved: 'hostname'