|
|
The configuration save and restore feature allows you to upload Non-Volatile Random Access Memory (NVRAM) to out-of-node storage to provide a backup of node configuration data. Downloading NVRAM back into a system controller (SC) enables recovery from a corrupted or replaced SC. It also allows you to generate a "template" to be used to configure multiple Cisco 6100s at a time.
 | Caution DO NOT EDIT THE SAVED FILE. Restoration of the configuration is unpredictable if the file is edited and could result in a corruption of the system and loss of service for subscribers. |
It is recommended that you use the TFTP server on the same workstation as the ViewRunner server. The TFTP server must be configured correctly on the workstation. The TFTP IP address and TFTP path are configured during ViewRunner installation. The wizard will validate that the images are present in the TFTP path on the ViewRunner server workstation, even if another workstation has been selected as the TFTP server. If the images are not found, then a warning message is displayed, and the user is given the choice to cancel or to continue. The user is not given a chance to change the path to locate the images, however.
Only Cisco 6100s loaded with 2.1 images or later can be saved and restored. The Cisco 6100 does not need to be attended during the process. Software images and relationships to module hardware are also saved and restored. Therefore, a restore configuration restores the software release executing on the Cisco 6100 at the time of the save in addition to the restoring the chassis, module, port, subscriber, pool, and service provisioning information. That is, if you restore configuration data from a node to another node running a different software version, the restore will change that node's software version.
Some things to remember when saving a configuration are:
The saved configuration files are placed in $VRS_HOME/NSS/<ip_address>/<name>. The name consists of the <ip_address>.<date>.<time>.NSS. The number of saved configurations can be varied using parameters in $VRS_HOME/conf/vrconstants.conf. The default is five files per Cisco 6100. The file format is compatible with both ViewRunner for HP OpenView and ViewRunner for Windows. The file can be used as a template for provisioning multiple Cisco 6100s with the same configuration or for disaster recovery. The images must be located in the directory specified by the TFTP path which is configured during ViewRunner installation.
| Caution DO NOT EDIT THE SAVED .NSS FILE. Cisco cannot be responsible for what may happen if you have edited this file by hand. The wizard is designed to prevent mistakes and system outages. |
To use the Save Configuration wizard, follow the steps below:
Step 1 In the View Map window, select the Cisco 6100s that you want to save by using the left mouse button to drag the mouse around the Cisco 6100 icons whose configurations you want to save. Additional Cisco 6100s can be added to the list before the operation is started through the right click menu option.
Step 2 Select Save Configuration from the Configuration menu on the ViewRunner Submap window (or right click the mouse) to use the Save Configuration wizard to save NVRAM out to a file.
Step 3 Alternatively, you may select Save Configuration from the File menu on the Chassis View window.
Step 4 The first screen for the Save Configuration wizard in ViewRunner follows. The screen explains the wizard and lists the Cisco 6100s you selected for configuration save.
Step 5 Verify that the Cisco 6100 choices are correct and select to continue with the configuration save. While the configurations are being saved, the progress will be reported in the Configuration Wizard window.
Step 6 Double click on any of the Cisco 6100s in the save list to view the status of the progress for that individual Cisco 6100.
Step 7 Continue monitoring the status until all the configurations have been completed. If you do not want to attend the configuration saves, you can always consult the log files later. The Cancel button will close the wizard, but it does not stop the processes that are already in progress.
A restore configuration restores saved software images and relationships to module hardware. Therefore, a restore configuration restores the software release executing on the Cisco 6100 at the time of the save in addition to restoring the chassis, module, port, subscriber, pool, and service provisioning information. That is, if you restore configuration data from a node to another node running a different software version, the restore will change that node's software version.
Restore configuration procedure requires a TFTP server. It is recommended that you use the TFTP server on the same workstation as the ViewRunner servers. The TFTP server must be configured correctly on the workstation. The TFTP IP address and TFTP path are configured during ViewRunner installation.
The wizard will validate that the images are present in the TFTP path on the ViewRunner server workstation, even if another workstation has been selected as the TFTP server. If images are not found, then a warning message is displayed and the user is given the choice to cancel or continue.
ViewRunner supports restoring to nodes managed through the inband channel, provided that both the current SC software version and the SC version saved in the NSS file support inband upgrades.
Some things to remember when restoring a configuration are:
| Caution DO NOT EDIT THE SAVED FILE. Cisco cannot be responsible for what may happen if you have edited this file by hand. The wizard is designed to prevent mistakes and system outages. |
To use the Restore Configuration wizard, follow the steps below:
Step 1 In the View Map window, select the Cisco 6100s that you want to restore using the left mouse button to drag the mouse around the Cisco 6100 icons whose configurations you want to restore. Additional Cisco 6100s can be added to the list before the operation is started through the right mouse click menu.
Step 2 Select Restore Configuration from the Configuration menu on the ViewRunner submap window (or right click the mouse). The Restore Configuration wizard starts.
Step 3 Alternatively, you may select Restore Configuration from the File menu on the Chassis View window.
Step 4 The first panel of the Restore Configuration wizard in ViewRunner follows. The screen explains the wizard and lists the Cisco 6100s you selected. Be sure to read the window carefully to understand the warnings and consequences of continuing with the restore.
Step 5 Select the configuration file you wish to restore. You can enter the save file name or browse the directory $VRS_HOME/NSS/ for the file you wish to restore.
The restore wizard allows you to optionally select to restore the subtend information that was saved in the .NSS file. To restore with optional subtend info, continue and use the following steps.
Step 6 Enter or browse for the NSS file you would like to restore.
After selecting the NSS file, if the Wizard detects that the NSS file was saved from the same node you are restoring, then the Restore Subtend Info will be checked by default. Otherwise, the option will not be checked. You can change the default by clicking on the check box.
Step 7 On screen 2, if the Restore Subtend Connection Information is checked, then the subtend information will be restored.
Step 8 Verify that all the information for the restore is correct, then click OK to proceed.
Step 9 If the .NSS file being restored contains images that are not currently located in the TFTP path which is configured during ViewRunner installation, you will get a warning message similar to the following one telling you that the images needed for the restore are not in the expected TFTP path.
Step 10 Monitor the status of the restore in the status line of each Cisco 6100 as it happens or view the log file at any time. You can get a detailed status of the progress of the restore for any Cisco 6100 by double clicking on that Cisco 6100 in the progress list.
Step 11 Continue to monitor progress of the restore in the status line.
Step 12 Double click on the status line of a Cisco 6100 that shows a restore failure to get a log of the exact problems encountered as shown in the next screen.
The progress complete window appears as follows.
Posted: Fri Apr 23 14:29:39 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.