Skip to content
CA Network Flow Analysis - 9.3.2
Documentation powered by DocOps

UIM Integration

Last update August 31, 2015

CA Network Flow Analysis (CA NFA) integration with CA Unified Infrastructure Management (CA UIM) requires the following:

  • Integration is enabled by the nfa_inventory probe
    This is a local or remote probe used to send CA NFA inventory to UDM for reconciliation with snmpcollector.
  • The nq_services probe, which makes services internally available to CA NFA and other NetQoS products
    This allows these products to interrogate CA UIM for data.
  • NFA inventory information is synced to UIM where it is correlated with inventory from other sources
  • SNMP profiles are synced from CA UIM to CA NFA
  • In CA UIM, NFA data displays along with SNMP data

The steps required to accomplish the integration are:

  1. Deployment
  2. Configuration


To deploy the necessary components to integrate CA Network Flow Analysis with CA Unified Infrastructure Management:

  1. Download CA UIM 8.31.
  2. Download CA NFA 9.3.2.
  3. Install CA NFA 9.3.2.
  4. Install CA UIM 8.31.
  5. From the CA UIM Admin Console, import the nfa_inventory probe into the Local Archive from the Web Archive.
  6. From the CA UIM Admin Console, deploy the nfa_inventory probe to a robot either installed on the NFA console or remote to the NFA console.

    Note: We recommend that you install a robot on the NFA console server, but it is not required.
  7. Deploy the nq_services probe on the same robot as the UGS probe.
  8. Deploy snmpcollector to a hub in the same domain as the NFA robot.  


  1. Configure routers to send NetFlow to CA Network Flow Analysis.
  2. Using the CA UIM Admin Console, configure the nfa_inventory probe to point at the NFA console (by specifying the IP Address).
  3. On a periodic basis, the nfa_inventory probe queries NFA for inventory information (routers, interfaces, data access and cross-launch URLs).

    Note: If the nfa_inventory probe is on a non-wasp hub, the  /ump_common/nfa_inventory key must be added to the wasp config using Raw Configure in the Admin Console.
    The value of the nfa_inventory key should be the bus address ( /domain/hub/robot/nfa_inventory) for the nfa_inventory probe. 
  4. Configure snmpcollector so that all snmpcollector instances and NFA have the same origin.

System Data Flow

  1. The nfa_inventory probe calls NFA and gets current routers and interfaces, creates a CTD and puts it on the bus.
  2. The nfa_inventory probe calls NFA to get the data and cross-launch URLs (which for UIM 8.31 are stored locally, and made available via the get_info() call).
  3. DiscoveryServer consumes the CTD while additionally doing correlation with any routers or interfaces found by other probes (for example, snmpcollector).
  4. The DiscoveryServer inserts IPDevices and NetworkInterfaces into UDM.

User Data Flow

  1. In USM, the user selects a router of interest, and then selects an interface.
  2. USM calls the MetricsAPI, with the master interface ID, and timeframe.
  3. The MetricsAPI calls UDM to get the local interface ID and the IP Address of the NFA console.
  4. The MetricsAPI calls the data web service on NFA, transforms the data into the format expected by USM, and returns that data to be displayed.

Was this helpful?

Please log in to post comments.