cc/td/doc/product/dsl_prod/c6100/userdoc/rel220
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

System Maintenance

System Maintenance

This chapter explains how to maintain the Cisco 6100 system for optimal performance.

Chapter Structure

Each subsection details the following information about system maintenance.


Note If following the procedures suggested in "Action" is unsuccessful, please contact Cisco TAC.

Checklist of System Maintenance Procedures

The following table lists the system maintenance procedures described in this chapter and section names relative to the procedure.


Table 1-1: System Maintenance Checklist
Maintenance Description Section Name

Upgrading Cisco 6100 software

"Upgrading Cisco 6100 Software"

Save Configuration (NVRAM) Release 1.x

"Save Configuration (NVRAM) Release 1.x"

Restore Configuration (NVRAM) Release 1.x

"Restore Configuration (NVRAM) Release 1.x"

Save Configuration (NVRAM) Release 2.x

"Save Configuration (NVRAM) Release 2.2"

Restore Configuration (NVRAM) Release 2.x

"Restore Configuration (NVRAM) Release 2.2"

1.1 Upgrading Cisco 6100 Software

Maintenance Description

Downloading new/updated software from Cisco to fix problems and/or to upgrade your system. See the ViewRunner for Windows Provisioning and Operation Manual for more complete information on this utility.

Probable Impact

Updating your system provides you with fixes to problems associated with a previous release and installs new system features. The whole procedure, including saving and restoring the NVRAM, takes less than 20 minutes.


Note NVRAM is where all the provisioning and configuration information for the 6100 system is stored.

Since the only failsafe way to revert back to a prior 6100 configuration and images is to restore a saved "backup" of a .nss file, we recommend that you use the Save Configuration utility (see the ViewRunner for Windows Provisioning and Operation Manual or the "Save Configuration (NVRAM) Release 1.x" section in this manual for more information) to save your current configuration before beginning the upgrade procedure.

Action

    1. Access the update options under the Tools menu on the ViewRunner main menu toolbar.


Note Use the Save Configuration and Restore Configuration wizards to save the current provisioning information and system configuration out to a file. This is so you can recover your configuration as quickly as possible. See the "Save Configuration (NVRAM) Release 1.x"section for details about how to use the Save Configuration and Restore Configuration wizards.

Figure 1-1: Tools Menu


    2. Select the Tools >> View LoopRunner Software Image Data option to find out information about the current software images. This will help you determine which images are current and which should be updated.


Figure 1-2: LoopRunner Software Images


    3. Select Tools >> Upgrade LoopRunner Software option from the ViewRunner main menu. The command will only be enabled if a 6100 has been discovered and the system controller (SC) SwVersion matches a release in the release definition file (.RDF) with support for this feature. ViewRunner will display a progress bar along with a description of status, while the upgrade is taking place.

    4. The user will be presented with a wizard that will be a guide throughout the process.The first wizard window describes the upgrade procedure. Please read each wizard window carefully to understand various warnings and consequences of continuing the procedure. Select Next to continue.


Figure 1-3: Software Upgrade Wizard



Note If you have a BOOTP server present, the SC image used will be the one specified in the BOOTP table, not the one restored.

    5. In the second window, ViewRunner searches for all installed releases (.RDF files). It will present to the user, a list of installed releases for the user to choose from. Select one from the list provided or use the Browse button to find the images you want. The user will be asked to confirm a choice.


Figure 1-4: Software Upgrade System Software Version


    6. You will be asked to confirm your software download choice.


Figure 1-5: Confirm System Software Version


    7. The third wizard window identifies a default IP Address and IP Path. The user has the choice of changing both. The IP address is the one for the TFTP server. In many cases, this will be the IP address of the PC where ViewRunner is running since ViewRunner for windows functions as a TFTP server. The TFTP path is to the images to which you want to upgrade.


Figure 1-6: Software Upgrade TFTP Address/Path


    8. Depending on your choices of download, in the fourth window, you are informed of certain conditions encountered and once the process begins, service may be affected. You may choose Next to continue or Cancel to stop the process before the download begins.


Note Figures 1-7 through 1-9 illustrate some of the conditions that may be encountered.

Figure 1-7: Download Conditions (1)



Figure 1-8: Download Conditions (2)



Figure 1-9: Begin Download Procedure



Note The user has not manually placed the system into Maintenance state. Service is not interrupted until as late as possible. Once the software download procedure is started, no further operator intervention is allowed except at the end to select whether or not to reset the system now or to defer it until later.

    9. If the user continues, the following dialog displays showing the progress of the download. The remainder of the procedure will run unattended.


Figure 1-10: Software Upgrade Progress Window


    10. Transparently to you, the Save and Restore Configuration utility was used to store the NVRAM of the older system, replacing all configuration items but updating all software images. You are alerted when the process is complete asking that you reset the SC. You may choose to reset the SC now or wait until later.


Figure 1-11: Process Complete Window


    11. See the customer premise equipment (CPE) Cisco 675 and/or Cisco FireRunner documentation for procedures on how to download software to those devices.

1.2 Save Configuration (NVRAM) Release 1.x

Maintenance Description

Uploading NVRAM to out-of-node storage provides a backup of node configuration data. Then downloading NVRAM back into an SC enables recovery from a corrupted or replaced SC.


Note NVRAM is where all the provisioning and configuration information for the 6100 system is stored.

Probable Impact

Prevents manual re-entry of node configuration data which is time consuming and error prone. The major impact difference between the two versions is that this one version requires that the user attend the entire process and participate by performing tasks, such as connecting a serial cable to reset the SC, removing the line concentration module, and so forth. The newer version is described in later sections.

Warning DO NOT EDIT THIS FILE. Cisco cannot be responsible for what may happen if you have manually edited this file. The wizard is designed to prevent mistakes and system outages

Action

    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.


Figure 1-12: File Menu - Save Configuration


    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.


Figure 1-13: Save As Window


    3. The first window for the Save Configuration wizard in ViewRunner follows. Be sure to read the windows carefully to understand the warnings and the consequences of continuing this procedure.


Figure 1-14: Save Configuration Window


    4. The second window of the Save Configuration wizard asks you to reset the SC. Remove the SC module from the multiplexer chassis (MC) and re-insert it. Service will be interrupted during this process because a reset of the SC occurs. The interruption is slight.


Figure 1-15: Warning SC Reset


    5. Select Next for the system to discover the reset SC image.


Figure 1-16: System Discovery


    6. Select Next to continue with the configuration save. The window warns that the process cannot be interrupted, so make sure you want to continue before pressing Next.


Figure 1-17: Process Interruption Warning


    7. The last window of the Save Configuration wizard shows the progress of the save. Note that there is a warning here reminding you not to edit this saved file. If you do edit the file, you risk corrupting the configuration.


Figure 1-18: Progress Window


    8. See the CPE Cisco 675 and/or Cisco FireRunner documentation for procedures on how to save NVRAM configurations for those devices.

1.3 Restore Configuration (NVRAM) Release 1.x

Maintenance Description

Uploading NVRAM to out-of-node storage provides a backup of node configuration data. Then downloading NVRAM back into an SC enables recovery from a corrupted or replaced SC. It also allows for restoring the configuration after a software upgrade.


Note NVRAM is where all the provisioning and configuration information for the 6100 system is stored.

Probable Impact

Prevents manual re-entry of node configuration data which is time consuming and error prone.

Warning DO NOT EDIT THIS FILE. Cisco cannot be responsible for what may happen if you have manually edited this file. The wizard is designed to prevent mistakes and system outages.

Action

    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.


Figure 1-19: File Menu - Restore Configuration


    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 preceding Save Configuration step.


Figure 1-20: File Open


    3. The first window of the Restore Configuration wizard in ViewRunner follows. Be sure to read the window carefully to understand the warnings and consequences of continuing with the restore.


Figure 1-21: Restore Configuration


    4. Remove the line interface module (LIM) controller (if you have a DOH configuration). Select Next to continue. Be sure to note the warnings on the windows.


Figure 1-22: Remove LIM Controller


    5. Connect the PC to the SC. Follow the instructions on the window and heed all warnings. Then select Next to continue.


Figure 1-23: Connect PC to the SC


    6. Heed the warning that the process cannot be interrupted and select Next when you are ready to proceed.


Figure 1-24: Process Interruption Warning


    7. The next window is shows the progress of the restore. Select Next to continue when the restore completes.


Figure 1-25: Progress Window


    8. Insert the LIM controller and either select Finish to automatically rediscover the 6100 or select Cancel to rediscover later.


Figure 1-26: Insert LIM Controller and Discover


1.4 Save Configuration (NVRAM) Release 2.2

Maintenance Description

Uploading NVRAM to out-of-node storage provides a backup of node configuration data. Then downloading NVRAM back into an SC enables recovery from a corrupted or replaced SC.


Note NVRAM is where all the provisioning and configuration information for the 6100 system is stored.

Probable Impact

Prevents manual re-entry of node configuration data which is time consuming and error prone. The major impact difference between the two versions is that the old wizard required that the user attend the entire process and participate by performing tasks, such as connecting a serial cable to reset the SC, removing the line concentration module, and so forth. This newer version does not require that the user attend the entire process.

Warning DO NOT EDIT THIS FILE. Cisco cannot be responsible for what may happen if you have manually edited this file. The wizard is designed to prevent mistakes and system outages.

Action

    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.


Figure 1-27: File Menu - Save Configuration


    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.


Figure 1-28: Save As Window



Note The Save Configuration wizard copies both the entire SC NVRAM configuration (including the software images) to a file that can later be restored to the same or other nodes.

    3. The first window for the Save Configuration wizard in ViewRunner follows. Be sure to read the windows carefully to understand the warnings and the consequences of continuing this procedure. Select Next to continue.


Figure 1-29: Save Configuration


    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.


Figure 1-30: System Discovery


    5. Select Next to continue with the configuration save. The window warns that the process cannot be interrupted, so make sure you want to continue before pressing Next.


Figure 1-31: Process Interruption Warning


    6. The fourth window of the Save Configuration wizard shows the progress of the save. Note that there is a warning here reminding you not to edit this saved file. If you do edit the file, you risk corrupting the configuration.


Figure 1-32: Progress Window


    7. When the process is complete a message appears at the bottom of window 4 of 4 letting you know it is done.


Figure 1-33: Progress Complete Window


    8. See the CPE Cisco 675 and/or Cisco FireRunner documentation for procedures on how to save NVRAM configurations for those devices.

1.5 Restore Configuration (NVRAM) Release 2.2

Maintenance Description

Uploading NVRAM to out-of-node storage provides a backup of node configuration data. Then downloading NVRAM back into an SC enables recovery from a corrupted or replaced SC. It also allows for restoring the configuration with a software upgrade.


Note NVRAM is where all the provisioning and configuration information for the 6100 system is stored.

Probable Impact

Prevents manual re-entry of node configuration data which is time consuming and error prone. Restoring a .nss file to a 6100, which is loaded with the same images as in the .nss file being restored, does not result in any software image upgrades. This is always the case when saving the configuration and then restoring it on the same node. Only the 6100 configurations will be restored, not the images.

If the .nss file being restored contains images that are not currently stored on the SC, new images must be retrieved.

Warning DO NOT EDIT THE SAVED FILE.

Action

    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.


Figure 1-34: File Menu - Restore Configuration


    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 previous Save Configuration step.


Figure 1-35: File Open


    3. The first window of the Restore Configuration wizard in ViewRunner follows. Be sure to read the window carefully to understand the warnings and consequences of continuing with the restore.


Figure 1-36: Restore Configuration


    4. If the .nss file being restored contains images that are not currently stored on the SC, new images must be retrieved.


Figure 1-37: Restore Configuration



Note If either the images or the TFTP server is not available, then the restore operation will fail.

    5. The next window is shows the progress of the restore.


Figure 1-38: Progress Window


    6. When the process completes, a message appears at the bottom of window 3 of 4. Select Next to continue.


Figure 1-39: Progress Complete Window


    7. Select Finish to automatically rediscover the 6100 or select Cancel to rediscover later.


Figure 1-40: Rediscover the 6100



hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Nov 16 11:44:18 PST 1999
Copyright 1989-1999©Cisco Systems Inc.