Initial Configuration › Configure CA Network Flow Analysis to Work with CA Performance Center › Configure Flow Collection › Add DSAs (Three-Tier Deployment)

Add DSAs (Three-Tier Deployment)

If you have a three-tier architecture deployment, add one or more DSAs (Data Storage Appliances) to store the 15-minute (historical) data. If you have a standalone system or two-tier architecture, you do not add any DSAs.

We recommend that you add at least one DSA within 30 minutes of starting flow collection. Until you add a DSA to your three-tier deployment, 15-minute data is not available for reports. Reports that show a time range of more than 2 hours do not show any data.

Note: Do not add a DSA instance instead of editing the IP address of a retired DSA. In this case, routers continue to send data to the retired DSA--and that data is not available in reports. If you have to delete a DSA, contact CA Support for assistance.

Follow these steps:

1. Open the NFA console, logged in with Administrator rights.
2. Display the DSA page in the NFA console user interface:
   1. Select Administration from the NFA console menu.

      The Administration page opens.

   2. Select System: DSA from the Administration menu.

      The DSA page opens and shows a list of the current DSAs.

3. Click Add.

   The Add DSA dialog opens.

4. Enter the IP address for the DSA server.
5. Click Test Connection.

   A connection test is performed to determine whether the NFA console server can contact the DSA server and can verify that MySQL is installed. If the test succeeds, a "Test success" message opens.

6. Respond to the test results:
   1. If the Test success message opens, click OK to close it.
   2. If an error message opens, close the error message and respond as described in Troubleshoot DSA Addition.
7. Once the test completes successfully, click Save in the Add DSA dialog.

   The connection test is performed, followed by a test to locate DSA settings on the target server.

8. Note the test results:
   • If no error message opens, the tests have succeeded. The following events result:
     • The dialog closes and the DSA is added to the DSA list.
     • The Harvesters begin to include the new DSA in the destinations for new enabled interfaces that report 15-minute data.
     • The NFA console pushes settings down to the new DSA.
     • The DSA is configured to retrieve 15-minute data files from the NFA console.
     • Data from the DSA begins to be available for reports in approximately 30 minutes.
   • If an error message opens, close the error message and respond as described in Troubleshoot DSA Addition.

Notes:

• If a DSA does not begin to collect the 15-minute data within 30 minutes after flow collection begins, problems can result. The processed data accumulates on the NFA console server and processing slows. If the problem continues, the NFA console stops collecting the 15-minute data and unprocessed data accumulates on the Harvesters. If Watchdog traps are configured, the Watchdog sends out alerts that the Harvester or Reaper is falling behind. If the problem is left unchecked, the CA Network Flow Analysis services on the Harvesters may stop running.
• Each DSA is enabled to collect data for a maximum of 5,000 enabled interfaces that have reported data.
• For information about the data types, storage lifespan, minimum thresholds, and report types for the 15-minute data that is stored on DSA servers, see the topic 15-Minute Data in the CA Network Flow Analysis Administrator Guide.