Probe Release Notes:
- CA Unified Infrastructure Management Server v8.2 or later, including SNMP Collector 2.1 or later,
- Robot version 5.23 or later
- Java Virtual Machine (JVM) version 1.7 or later (deployed as part of the probe package)
- CA Network Flow Analysis R9.3.1 or later
WCF Activation under .NET Framework 3.5.1
Make sure that Windows Communication Foundation HTTP/Non-HTTP Activation is enabled for .Net framework in 'Windows features.
WCF Activation has to be installed/enabled on the server hosting the NFA console.
To enable it, go to 'Control panel' --> click 'Programs & Features'/'Add/Remove programs' --> click 'Turn Windows Feature on or off' --> from listing expand 'Microsoft .Net framework 3.5.1 (/your version)' --> check both 'Windows Communication Foundation HTTP Activation' & 'Windows Communication Foundation Non-HTTP Activation' --> click 'OK'.
When WCF is NOT enabled you may see these types of errors from the nfa_inventory log
Jun 30 16:00:22:987 [Connection tester - 0, nfa_inventory] **** NFA API URI: http://xxx.xxx.xxx.xx:80/ReporterDataSource/InventoryWS.svc/GetNFAUrls
Jun 30 16:00:23:277 [Connection tester - 0, nfa_inventory] HTTP request to NFA status line: HTTP/1.1 404 Not Found
Jun 30 16:00:23:277 [Connection tester - 0, nfa_inventory] Response from HTTP request to NFA was: 404
Jun 30 16:00:23:278 [Connection tester - 0, nfa_inventory] org.apache.http.client.HttpResponseException: Response from API was not 200 OK. The status code was: 404
Note also that the wasp probe/UMP server must be in the same hub domain as NFA.