Prerequisites:
1. Versa director install and configured
2. Should have access to Versa Director-CLI
3. New Controller should have same (eth0) IP address as old Controller.
4. Please export the running config from the old controller to save as backup before we proceed
Configuration:
- First login into the Versa Director cli:
- Disconnect the old controller from the Versa Director using cli command:
Administrator@Director> request devices device < Controller Name > disconnect
Please Note: We should still have reachability to the new controller from Versa Director using the same IP address.
3. Copy the file /var/lib/vs/.ckey from old Controller to the New Controller.
sudo chown root:versa /var/lib/vs/.ckey
sudo chmod 0700 /var/lib/vs/.ckey
Restart the Versa services on the New Controller.
P.S.: If the max tenant count of the old Controller is > 32 [Default], please update the Max-Tenant count to match what is set on the Older Controller and restart the Versa Services before proceeding to Step-4.
admin@Old-Controller-cli> show configuration system service-options max-tenants
max-tenants 32;
4. Disconnect the reachability of the Old Controller to the Director, and connect the new controller to the Versa Director using the Director cli command:
Administrator@Director> request devices device <Controller Name> connect
5. Fetch SSH keys from the new controller using the Versa Director cli command:
Administrator@Director> request devices device <Controller Name> ssh fetch-host-keys
6. Push the Versa Director SSH keys into the controller using the Versa Director shell command:
/opt/versa/vnms/scripts/push_keys_to_device.sh <controller mgmt. IP> <password>
7. Once disconnected the faulty controller from Versa Director cli, then login to Versa Director GUI.
8. In the director GUI navigate to Administration tab and Click on Appliance -> Select the controller on right pane click on Sync to Appliance.
With this step, Versa Director adds old controller’s configuration to the new controller.
