Update the Data Collector

You can migrate the Data Collector without having to rediscover network devices and components or lose historical data. For example, if you are a tool administrator, your server administrator can instruct you to relocate Data Collector to another host. Data Collector is polling 500,000 devices and components, and you do not want to lose data or perform rediscovery.
capm320
You can migrate the Data Collector without having to rediscover network devices and components or lose historical data. For example, if you are a tool administrator, your server administrator can instruct you to relocate Data Collector to another host. Data Collector is polling 500,000 devices and components, and you do not want to lose data or perform rediscovery.
The Data Collector component can be moved even if you have device packs installed.
Note the following considerations:
  • The amount of data loss is equal to the amount of time that has elapsed from the time the old Data Collector component is shut down to the time when the new Data Collector component has been deployed.
  • If the old Data Collector component happens to start accidentally, the SNMP data is polled twice. A warning appears in the Data Aggregator karaf log:
    WARN | Session Task-810 | 2013-01-02 13:52:09,062 | DCHeartBeatLog | ore.collector.interfaces |
    | HeartBeat message not received. Expected: 93, Received: 255
    To fix this problem, stop or uninstall the old Data Collector component.
To move Data Collector to another system, follow this process:
Backup and restore is not required for the Data Collector. For installations that use CA Mediation Manager, migrate the device packs before you install the Data Collector on the new host.
Determine the Unique Identifier for Data Collector
Determine the unique identifier for Data Collector before moving this component to another host.
Retrieve the Data Collector ID using
one
of the following methods:
  • Log in to
    Performance Center
    as a user with the Administrator role, and do the following steps:
    1. Select
      Administration
      , and select a Data Aggregator data source from the menu.
      The Data Aggregator Admin UI opens.
    2. Select
      System Status
      ,
      Data Collectors
      from the menu.
    3. Find the Data Collector component that you want to move and notate its ID.
      The format of the Data Collector component ID is HOSTNAME:UUID.
  • Open a web browser and issue the following web service call:
    http://DA_hostname:port/rest/dcms
    DA_hostname:port
    Specifies the Data Aggregator host name and the port number.
    Default port:
    8581
    Find the <DataCollectionMgrInfo> section whose HostName and IPAddress match the one you want to move. Note the value for <DcmID>.
Stop Data Collector
Stop the Data Collector services on the current host before moving Data Collector to another host.
Follow these steps:
  1. If you have installed device packs for this Data Collector, take the following steps. If no device packs are installed, proceed to Step 2.
    1. Log in to
      Performance Center
      as a user with the Administrator role.
    2. Select
      Administration
      , and then select a Data Aggregator data source from the menu.
      The Data Aggregator Admin UI opens.
    3. Select
      EMS Integration Profiles
      from the
      Monitoring Configuration
      menu.
    4. Right-click on a profile that is associated with this Data Collector host, and select
      Stop
      . Do this step for every EMS profile that is related to this Data Collector host.
    5. Archive CA Mediation Manager artifacts by running this command:
      tar -zcvf filename /opt/IMDataCollector/apache-karaf-{n.n.n}/MediationCenter
      • filename
        Specifies the name of the archive file, which is moved to the new Data Collector host.
  2. Log on to the Data Collector host and run the following command:
    service dcmd stop
  3. Verify that Data Collector has stopped:
    1. Log in to
      Performance Center
      as a user with the Administrator role.
    2. Select
      Administration
      , and select a Data Aggregator data source from the menu.
    3. Select
      System Status
      ,
      Data Collectors
      from the menu.
    4. Verify that the Data Collector status is "Not Connected".
Reinstall the Data Collector on a Clean Host
After you stop the Data Collector services on the original host, reinstall the Data Collector on a clean host. Use the same
DCM_ID
. Doing so allows the Data Collector to retrieve the original Data Collector configuration from the Data Aggregator when the new Data Collector process starts.
Verify that
CA Mediation Manager
and
CA Virtual Network Assurance
point to the correct Data Collectors:
Follow these steps:
  1. (
    CA Mediation Manager
    only) Migrate your device packs. On the old Data Collector host, run the
    $CAMM_HOME
    /tools/migratePMtoCAMM script with the - t flag.
    This step assumes that you are running the script on a Data Collector server where a Local Controller is installed. You must also have the CA Mediation Manager Console running on another server. For more information, see the
    CA Mediation Manager
    documentation
    .
  2. (
    CA Virtual Network Assurance
    only) For
    CA Virtual Network Assurance
    , see the
    CA Virtual Network Assurance
    documentation
    .
  3. Log in to the new host system and open a command shell session.
  4. Set an environment variable with the ID of the data collector by running this command:
    export DCM_ID=
    data collector id
    • data collector id
      The DcmID that we obtained as the unique identifier for the Data Collector in the previous section.
  5. Install Data Collector from the same session by running the
    install.bin
    binary. For more information, see Install the Data Collectors.
  6. Install the CA Mediation Manager LC on the same server.
  7. If you have previously installed device packs for this Data Collector, perform these additional steps:
    1. Copy the zip files that you created previously with the migration script to local directories on this host.
    2. Use the CA Mediation Manager web console to deploy these device packs and start them.
      You do not need to redeploy the certification packs to the Data Aggregator host.
  8. (Optional) After several polling cycles, verify that data is being collected on the new host.Uninstall the old Data Collector, and delete any associated EMS profiles.