|
|
The configuration save and restore feature allows you to upload 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 quickly recover your configuration after downloading updated Cisco 6100 software (see "Updating Cisco 6100 Software").
ViewRunner for Windows is the craft interface for the Cisco 6100 for its. It is bundled with the Cisco 6100 multiplexer chassis or may be downloaded from Cisco Connection Online (CCO).
The ViewRunner for Windows 2.3.5 release supports the following Cisco 6100 releases:
The following matrix more fully describes the compatibility among Cisco 6100 and ViewRunner for Windows releases.
| Cisco 6100 Releases | |||||
|---|---|---|---|---|---|
| Release 2.3.0 | Releases 2.2.1/2.2.5 | Release 2.2.0 | Release 2.1.3 | Release 2.1.2 |
| ViewRunner for Windows |
|
|
|
|
|
Release 2.3.5 | X | X | X | X | X |
Release 2.3.0 | Cisco 6100 2.2.1 | X | X | X | X |
Release 2.2.1 | Cisco 6100 2.2.0 | Cisco 6100 2.2.0 | X | X | X |
Release 2.2.0 | Cisco 6100 2.2.0 | Cisco 6100 2.2.0 | X | Cisco 6100 2.2.0 | X |
Release 2.1.0 | Cisco 6100 2.1.x | Cisco 6100 2.1.x | Cisco 6100 2.1.x | Cisco 6100 2.1.x | X |
Legend: | X - ViewRunner presents a feature set customized to this Cisco 6100 release's capabilities. Cisco 6100 X.Y.Z -ViewRunner presents a feature set corresponding to the specified Cisco 6100 X.Y.Z release's capabilities. ViewRunner prompts the user when the chassis view displays that the feature set is not recognized and a default feature set is being used. | ||||
Saving the configuration of the Cisco 6100 will not disrupt service. Restoring the Cisco 6100 configuration will reset the system, causing a temporary loss of service.
Only Cisco 6100 systems loaded with 2.1 images or later can be saved and resored. The Cisco 6100 does not need to be attended during the process. Software images and relationships to module hardware are also saved and resored. Therefore, a restore configuration now 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.
When saving a configuration, remember:
An error was encountered, check the ViewRunner Log Window and try again.
![]() | 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 Select Save Configuration from the File menu on the ViewRunner main menu to use the Save Configuration wizard to save NVRAM out to a file.

Step 2 Indicate where you want the configuration file to be saved in the Windows Save As dialog box that appears when you start the wizard. You may give it a different name than the default, but use the .NSS extension.

Step 3 The first screen for the Save Configuration wizard in ViewRunner follows. Read the screens carefully to understand the warnings and the consequences of continuing this procedure. Select Next to continue.

Step 4 Select Next for the system to rediscover the SC image, or if you are sure you want to skip this step, check the Skip re-discovery box and then select Next.

Step 5 Select Next to continue with the configuration save. The screen warns that the process cannot be interrupted, so make sure you want to continue before pressing Next.The next two screens show the configuration save progress with the warning against altering the saved file. If you do edit the file, you risk corrupting the configuration.

Step 6 Once the save is complete a message will appear at the bottom of screen 4 of 4 stating so.

Step 7 See the CPE product documentation for procedures on how to save NVRAM configurations for those devices.
ViewRunner for Windows saves and restores 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 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.
When saving a configuration:
![]() | 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 Restore Configuration wizard, follow the steps below:
Step 1 Select Restore Configuration from the File menu on the ViewRunner main menu to use the Restore Configuration wizard to restore the NVRAM with the configuration that was saved out to a file.
Step 2 Indicate from where you want to restore the configuration file in the Windows File Open dialog box that appears when you start the wizard. This is the file you saved in the Save Configuration step above.

Step 3 The first screen of the Restore Configuration wizard in ViewRunner follows. Be sure to read the screen carefully to understand the warnings and consequences of continuing with the restore.
The Restore wizard allows the user to select the option to restore the subtend information that was saved in the .NSS file. The subtend information is used by ViewRunner for OpenView.
If the Restore Configuration is used to recover a node from a system failure of some kind, and the .NSS file was saved from the same Cisco 6100, then you would typicaly want to restore the subtend information.
If the Restore Configuration is being used as a template for bulk provisioning and the .NSS file was saved from a different Cisco 6100, then you would typically choose not to restore subtend information.

Step 4 In the second screen of five you must select the Local or Remote TFTP Server. The local server is the PC currently executing ViewRunner for Windows. In this case, ViewRunner will use its own TFTP server to transfer the files. If the remote server is selected, ViewRunner will use the TFTP server on the remote machine.
Enter the IP address of the TFTP server you will use to get the new software images to restore to the node (usually the IP address of the PC where ViewRunner is installed) and the path to the images themselves. The default location for the images is
c:\Program Files\Cisco.
Use the "Browse" or "Search" button to locate the sub-directory which contains the correct images. For example, c6100 - 2.3.0 where 2.3.0 is the 6100 version.
The search button will search all sub-directories below the directory listed in the path edit box until it finds the complete set of images.
Step 5 Select Next to continue.
Step 6 Select the Next button on the third screen of five to begin the restore.

Step 7 The next few screens show the progress of the restore.

Step 8 When the restore is complete, a message appears at the bottom of the screen stating so. Press Next to continue.

Step 9 Select Finish to automatically rediscover the Cisco 6100 or select Cancel to rediscover later.

![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Mon Oct 11 22:23:08 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.