NFA Data Source synchronization failure in DX NetOps Portal web UI

Products

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

Issue/Introduction

The DX NetOps Performance Management (PM) Portal web UI is showing synchronization failure for the Network Flow Analysis (NFA) Data Source (DS).

The communication Test option for the NFA DS fails. It reports "Communication with the data source failed."

The following error is seen in the DMService.log file found in the (default path) /opt/CA/PerformanceCenter/DM/logs directory.

ERROR | RIB/Engine               | 2021-10-11 00:06:13,797 | com.ca.im.rib.engine.sources.SourceScanner                       
      | Failed to scan RIB source
java.util.concurrent.ExecutionException: com.ca.im.rib.engine.sources.RIBSourceException: Unexpected error occurred while scanning a RIB source
  RIB Source URL: http://<NFA_HostName>:8681/NFARS/ribsource/rib/soap?wsdl
...
Caused by: com.ca.im.rib.engine.sources.RIBSourceException: Unexpected error occurred while scanning a RIB source
  RIB Source URL: http://<NFA_HostName>:8681/NFARS/ribsource/rib/soap?wsdl
...
Caused by: javax.xml.ws.WebServiceException: Could not send Message.
...
Caused by: java.net.UnknownHostException: UnknownHostException invoking http://<NFA_HostName>:8681/NFARS/ribsource/rib/soap?wsdl: <NFA_HostName>
...
Caused by: java.net.UnknownHostException: <NFA_HostName>

Environment

All supported DX NetOps Performance Management releases integrated with DX NetOps Network Flow Analysis

Cause

Environmental network issue, likely DNS related, is causing failures when attempts to communicate with the defined NFA host are made from the NetOps Portal server.

Resolution

Resolve the communication issue between the NetOps Portal and NFA host to resolve the failure.

Additional Information

Tips for investigation:

• Is the correct host name seen in the error message? If not set the correct name in the Data Source to see if it resolves the problem.
• Should the name be set to use FQHN instead of the short host name? If using short name update to FQHN to see if the issue is resolved.
• Is DNS working? From PC to NFA to resolve the <NFA_HostName> hostname for NFA? What does the following command, run on the PC host CLI, return?
  • nslookup <NFA_HostName>