Is there a document procedure for Migrating CAMM to new servers and Upgrading it from 20.2.6 to 22.2.5
search cancel

Is there a document procedure for Migrating CAMM to new servers and Upgrading it from 20.2.6 to 22.2.5

book

Article ID: 260144

calendar_today

Updated On:

Products

DX NetOps

Issue/Introduction

I am working with a customer that has 20.2.6 on old RHEL systems, and is moving CAMM to new RHEL8 systems,

Environment

Release : 22.2

Resolution

 follow the steps below for CAMM migration:

  1. Before migration, 
    1. Backup the Engine directories from LC located at <CAMM_HOME>/COMPONENTS/ENGINE_<DevicePackName>/tmp/input/* . 
      • .histroyFile.inventory from here can be used for restore in step 7 below. 
    2. Backup the device packs using the backup steps under Backup and Restore:
      • Run backup script from MC machine: <CAMM_HOME/tools/cammBackup <destination_dir>
    3. Instead of taking backup, if they can reconfigure all device packs, please ask them to note the configurations for each device pack and redeploy them after installation
  2. First, install MC.
  3. Next, install LC's. Install the LC with Presenter on the same DC as before ie., on the new RHEL 8 DC that replaces the old RHEL 6 DC which had LC with Presenter. 
  4. Now, restore the device packs using the restore steps under Backup and Restore:
    • Run restore script from MC machine: <CAMM_HOME/tools/cammRestore <backed_up_zip>
  5. If you restore the device packs to a system other than from where it was backed up, ensure to rename the MultiController or LocalController(rename the restored LC directories under <CAMM_HOME>/MC/repository with the respective LC names. Make sure the LC with Presenter is renamed correctly). 
  6. Restart CAMM. The restored device packs should now show up in the UI
  7. In the destination LocalController, if you want to prevent the download and process of the already polled data, follow the steps here:
    1. Stop the engines.
    2. Browse to the following location in the destination LocalController <CAMM_HOME>/COMPONENTS/ENGINE_<devicepack name>
    3. Create the tmp, input, performance, and inventory folders in the following order
      • <CAMM_HOME>/COMPONENTS/ENGINE_<devicepack name>/tmp/input/performance
      • <CAMM_HOME>/COMPONENTS/ENGINE_<devicepack name>/tmp/input/inventory
    4. Cut the .historyFile.inventory from the following locations in the source LocalController and paste them in the corresponding folders created above in the destination LocalControllers
      • <CAMM_HOME>/COMPONENTS/ENGINE_<devicepack name>/tmp/input/performance
      • <CAMM_HOME>/COMPONENTS/ENGINE_<devicepack name>/tmp/input/inventory
    5. Start the engines