Upgrade or Register with CA Performance Center

The NFA console or standalone server must be registered as a data source with a supported version of CA Performance Center or CA NetQoS Performance Center:

• Upgrade from CA NetQoS ReporterAnalyzer 9.0.1: Operate with CA Performance Center 2.2.x, CA Performance Center 2.3.x, or CA NetQoS Performance Center 6.1.194.
• Upgrade from CA NetQoS ReporterAnalyzer 9.1.00 or later: Operate with CA Performance Center 2.2.x or 2.3.x.

The registration task depends on your upgrade type:

• If you previously unregistered from CA NetQoS Performance Center or CA Performance Center and you have completed the CA Network Flow Analysis upgrade, follow the steps in this topic to register as a data source for CA Performance Center 2.2.x or 2.3.x.
• If you have not unregistered and you have CA Performance Center 2.1.x currently installed, perform the upgrade to CA Performance Center version 2.2.x or the incremental upgrades to version 2.3.x now. For instructions, see the CA Performance Center Installation Guide.
• If you upgraded from CA NetQoS ReporterAnalyzer 9.0.1 and you want to keep using CA NetQoS Performance Center 6.1.194, you should already be registered. In this case, skip this step.

Follow these steps:

1. Log in to the CA Performance Center Console as a user with the Administrator role.
2. Navigate to the Manage Data Sources page.

   The Manage Data Sources page displays the current list of registered data sources.

3. Click Add.

   The Add Data Source dialog opens.

4. Select CA Network Flow Analysis from the Source Type list.

   Note: All CA products that can be registered as CA Performance Center data sources are shown in the Source Type list. The list is not filtered to show installed products.

5. Select the data source status. Select Disabled if you want to delay polling of this data source while still registering it.

   No data from this data source is reported until you edit the data source to select the Enabled status. Views from this data source display a message stating, "No data to display".

6. Enter the Host Name: Use the IP address or DNS hostname of the NFA console server.
7. Enter the port to use when contacting the data source. The port that you enter depends on the protocol you select.

   For more information, see the CA Single Sign-On User Guide.

8. Select the protocol to use to contact the data source. Select https if your network is using SSL for communications. Verify that you have configured the system correctly before you select the https option.

   Note: SSL can be used for communications between CA Performance Center and the data source products. For more information, see the CA Single Sign-On User Guide.

9. (Optional) Enter a Display Name for the data source.

   By default, the data source type and the hostname are combined to create the display name. You can supply another name here. For example, instead of NetworkFlowAnalysis@xxx.x.x.xx, you can name the data source NetworkFlowAnalysis_NewYork.

10. Click Save to register the data source.

    The Data Source List shows the CA Network Flow Analysis deployment that you registered.

11. Review the results in the CA Performance Center Console and make any adjustments that are needed. Review the list of potential changes that are described in the topic about unregistering. For example, revise the following elements as needed:
    • Tenants and domains: Recreate any custom tenants and domains that are missing. Reassign groups, user accounts, devices, and interfaces to the custom tenants and domains. Restore the protocol names, ToS labels, AS names, and IP addresses that were in custom domains.
    • Users: Check or spot-check the user accounts, their settings, and their assigned groups and domains.
    • Groups:
      • Relocate groups as needed.
      • Delete any duplicate groups.
      • Restore any deleted groups, including any dynamic groups such as cross-product groups.
    • SNMP profiles: Check the SNMP profiles and any domain assignments that they had before the unregister process.
    • LDAP and other Single Sign-On customizations: Check.

      Note: If you upgrade from CA NetQoS ReporterAnalyzer 9.0.1, you also will change to a new SSO version. Update any previous SSO LDAP configuration and check other SSO customizations. Options from the previous SSO version may not match the current options or may not comprise a full set of the current options. For information about configuring SSO, see the Single Sign-On User Guide.

12. Check the effects of your revisions in the NFA console. For example, review the following locations:
    • Active Interfaces page:
      1. Select Administration, Interfaces: Physical & Virtual.
      2. Verify that expected routers and interfaces are shown.
      3. Check the domain assignments for interfaces: Select an interface, click Edit, and verify that the expected tenant / domain setting is shown in the Edit Interface dialog.
      4. Verify that the Domain list contains the expected domains.
    • Available Interfaces page: Select Administration, System: Enable Interfaces. Verify that the expected routers and interfaces are shown as enabled.
    • Interface Index Group tab: Select Interfaces, Group tab. Verify that the group tree in the left pane has the expected contents and structure.

      If an HTTP Request Error opens when you attempt to display the Group tab, clear your browser cache. The error may indicate that you browser is attempting to reload an outdated page.

    • Harvester page: Select Administration, System: Harvester. Verify that the Harvester tenant / domain assignments are correct.
    • Domain-specific ToS labels: Select Administration, Groups: ToS Groups. Verify that the expected ToS labels are shown for each ToS group with domain-specific ToS labels.
    • Domain-specific protocol names: Select Administration, Groups: Protocol Groups. Verify that the expected protocol names are shown for each protocol group when you select the group and click List.
    • Domain-specific AS names: Select Administration, Define an Application: AS Names. Verify that the expected AS names are shown for each domain that you select.
    • Enterprise Overview page, Interfaces pages, and report pages: Verify that the expected contents are visible to users who have varying types of access.