Step 1 |
Install the VNMC virtual machine. For information, see the Cisco Virtual Network Management Center 2.0 Quick Start Guide. |
Step 2 |
Uninstall the VSG policy agents. Connect the Secure Shell to the VSG console for this task. This step does not cause a traffic disruption.
Example:vsg# conf t
vsg (config)# vnmc-policy-agent
vsg (config-vnmc-policy-agent)# no policy-agent-image
Note |
Perform this step for all VSGs that are associated with the VNMC that you are restoring. |
|
Step 3 |
Disable the ASA 1000V policy agent.
Example:ASA-154# conf t
ASA-154(config)# no vnmc policy-agent |
Step 4 |
Uninstall the VSM policy agents. Connect the Secure Shell to the VSM console for this task. This step does not cause a traffic disruption.
Example:vsm# conf t
vsm (config)# vnmc-policy-agent
vsm (config-vnmc-policy-agent)# no policy-agent-image
Note |
Perform this step for all VSMs that are associated with the VNMC you are restoring. |
|
Step 5 |
Restore the VNMC database. Connect the Secure Shell to the VNMC CLI for this task. Depending upon your VNMC backup location, restore using FTP, SCP, or SFTP.
Example:vnmc# connect local-mgmt
vnmc(local-mgmt)# restore scp://username@server/path |
Step 6 |
In the VNMC UI, choose Administration > Service Registry > Clients, and in the General tab, do the following:
-
Wait until each registered VSM displays the operational status as lost-visibility.
-
Choose each VSM, and click Delete Client.
|
Step 7 |
In the VNMC UI, choose Resource Management > Resources > Virtual Supervisor Modules, and verify that the deleted VSMs are not visible. |
Step 8 |
Reregister the VSMs associated with VNMC by entering the following commands for each VSM:
Example:VSM# conf t
VSM (config)# vnmc-policy-agent
VSM (config-vnmc-policy-agent)# registration-ip vsm-ip-address
VSM (config-vnmc-policy-agent)# shared-secret password |
Step 9 |
Reinstall the VSM policy agents.
Note |
If the VSM policy agents must be upgraded, install the new software now. |
Example:VSM# conf t
VSM (config)# vnmc-policy-agent
VSM (config-vnmc-policy-agent)# policy-agent-image bootflash:vnmc-vsmpa.1.0.1g.bin |
Step 10 |
Wait until all the VSMs have registered in the Service Registry and are displayed under Resource Management > Resources > Virtual Supervisor Modules. |
Step 11 |
Reregister the VSGs associated with VNMC by entering the following commands for each VSG:
Example:VSG# conf t
VSG (config)# vnmc-policy-agent
VSG (config-vnmc-policy-agent)# registration-ip vsg-ip-address
VSG (config-vnmc-policy-agent)# shared-secret password |
Step 12 |
Reinstall the VSG policy agents.
Note |
If the VSG policy agents must be upgraded, install the new software now. |
Example:VSG# conf t
VSG (config)# vnmc-policy-agent
VSG (config-vnmc-policy-agent)# policy-agent-image bootflash:vnmc-vsgpa.1.0.1g.bin |
Step 13 |
Re-enable the ASA 1000V policy agent.
Example:ASA-154# conf t
ASA-154(config)# vnmc policy-agent
ASA-154(config-vnmc-policy-agent)# shared-secret password
ASA-154(config-vnmc-policy-agent)# registration host host-ip-address |
Step 14 |
Verify the following states after the restore process is complete:
Note |
The restore process could take a few minutes depending upon your setup environment. |
-
Using the VSG CLI, verify that your configurations are restored to their earlier state.
-
Using the VNMC UI, verify that your objects and policies are restored to their earlier state.
-
Using the ASA 1000V CLI, verify that your configurations are restored to their earlier state.
|