DETAILED STEPS
Step 1 Click the Software Install Wizard icon in the toolbar (see Figure 12-2).
Figure 12-2 Software Install Wizard Icon
You see the Select Switches dialog box with all switches selected by default.
Figure 12-3 Select Switches Dialog Box
Step 2 Deselect the check box for the switch(es) for which you do not want to install images on. You must have at least one switch selected to proceed (see Figure 12-3).
Step 3 Click
Next
when finished.
Step 4 (Optional) Check the
Skip Image Download
check box and click Next to use images that are already downloaded (the file is already on the bootflash). Proceed to Step 11.
You see the Specify Software Image(s) by Model Dialog Box shown in Figure 12-4.
Figure 12-4 Specify Software Image(s) by Model Dialog Box
Step 5 Click the Use Saved Settings check box to load and display the previously saved settings. Settings are saved each time the Next button is clicked.
Step 6 Click the radio button for either:
a. Local FM TFTP to transfer files from local computer.
b. Remote to transfer files from a remote computer.
Step 7 If you select Local FM TFTP, proceed to Step 10.
Step 8 If you select Remote, click one of the Copy Files Via radio buttons transfers files (SFTP, SCP, FTP).
Step 9 Enter the server name, user name and password.
Step 10 Enter the version and the image path and then click Apply.
Note You can manually provide the file name, if you had choosen Local FM TFTP in step 6. To do that you may double-click the table, and choose the file form the Open dialog box or manually type the file name in the cell under system.
When you enter the version string and image path, DCNM-SAN tries retrieves the default file name and the calculate the flash space required to accommodate the image file. Version string should be the current version of the version to be installed. Image path is the path to locate the software image as shown in the following example:
Image URI: /tftpboot/rel/qa/5_0_0_201/gdb/m9500-sf2ek9-mzg.5.0.0.201.bin.S2 Path – /tftpboot/rel/qa/5_0_0_201/gdb Version String – 5.0.0.201.S2
Step 11 Click the row under the System, Kickstart or SSI columns to enter image URIs. You must specify at least one image for each switch to proceed.
Step 12 Click Verify Remote Server and Path.
DCNM-SAN will validate the file path and server credentials. You see the output as shown in Figure 12-5
Figure 12-5 Validation Result
Step 13 Click OK and then click Next in the Specify Software Images by Model dialog box.
You see the Check Flash Free Space dialog box (see Figure 12-6). This dialog box shows the active (and standby, if applicable) bootflash space on each switch, and shows the status (whether there is enough space for the new images). If any switch has insufficient space, you cannot proceed. Deselect the switch without enough bootflash by going back to the first screen and unchecking the check box for that switch.
Figure 12-6 Check Flash Free Space Dialog Box
Step 14 Click Next.
You see the Start Install dialog box shown in .
Figure 12-7 Start Install Dialog Box
Note There is no limit on the number of switches you can upgrade.
Step 15 Click one of the the radio buttons:
a. Serialized to upgrade one switch at a time.
b. Parallel to simultaneously upgrade multiple switches.
Step 16 (Optional) Check the Version Check Only check box to complete the version check first and then prompt for your input to continue with installation.
Step 17 (Optional) Click Finish to start installation.
You see the Version Check Results dialog box shown in .
Figure 12-8 Version Check Results Dialog box
Step 18 (Optional) Check the Install without Version check Prompting check box to continue with the installation.
Note The version check provides information about the impact of the upgrade for each module on the switch. It also shows any incompatibilities that might result. You see a final dialog box at this stage, prompting you to confirm that this check should be performed. We recommend that you do not ignore the version check results.
Caution If Install without Version check Prompting is checked, the upgrade will proceed even if the current switch version is newer than the version you are installing.
Step 19 Click OK to close the wizard.
Step 20 Click Continue to install to start the installation.
You see the Download and Install Status dialog box shown in Figure 12-9.
Figure 12-9 Download and Install Status Dialog Box
Note On hosts where the TFTP server cannot be started, a warning is displayed. The TFTP server may not start because an existing TFTP server is running or because access to the TFTP port 69 has been denied for security reasons (the default setting on Linux). In these cases, you cannot transfer files from the local host to the switch.
Note Before exiting the session, be sure the upgrade process is complete. The wizard will display a status as it goes along. Check the lower left-hand corner of the wizard for the status message Upgrade Finished. First, the wizard displays the message Success followed a few seconds later by InProgress Polling. Then the wizard displays a second message Success before displaying the final Upgrade Finished.
Using the install all Command
Note Ensure that there is enough space available on the active and standby supervisor module bootflash: to store the images being installed, even if the images are supplied in slot0:. The system will automatically synchronize the images to the standby supervisor module.
To perform an automated software upgrade on any switch, follow these steps:
Step 1 Log into the switch through the console, Telnet, or SSH port of the active supervisor module.
Step 2 Create a backup of your existing configuration file, if required.
Step 3 Verify that you have enough free space available on the active and standby supervisor module bootflash:. The download site on Cisco.com shows the size of the system image file in bytes. If there is not adequate space, delete files using the
delete
filename
EXEC command.
12288 Jan 01 00:01:06 1980 lost+found/ 14765056 Mar 21 15:35:06 2005 m9500-sf1ek9-kickstart-mz.2.1.1.bin 15944704 Apr 06 16:46:04 2005 m9500-sf1ek9-kickstart-mz.2.1.1a.bin 48063243 Mar 21 15:34:46 2005 m9500-sf1ek9-mz.2.1.1.bin 48036239 Apr 06 16:45:41 2005 m9500-sf1ek9-mz.2.1.1a.bin Usage for bootflash://sup-local Mod Ports Module-Type Model Status --- ----- -------------------------------- ------------------ ------------ 2 32 Storage Services Module DS-X9032-SSM ok 5 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 active * 6 0 Supervisor/Fabric-1 DS-X9530-SF1-K9 ha-standby
The
show module
command output shows that the standby supervisor is in slot 6. Use the
attach
command to access the supervisor module.
switch(standby)# dir bootflash: 12288 Jan 01 00:01:06 1980 lost+found/ 14765056 Mar 21 15:35:06 2005 m9500-sf1ek9-kickstart-mz.2.1.1.bin 15944704 Apr 06 16:46:04 2005 m9500-sf1ek9-kickstart-mz.2.1.1a.bin 48063243 Mar 21 15:34:46 2005 m9500-sf1ek9-mz.2.1.1.bin 48036239 Apr 06 16:45:41 2005 m9500-sf1ek9-mz.2.1.1a.bin Usage for bootflash://sup-local
Step 4 Download a Cisco NX-OS system image to the active supervisor module bootflash: from a TFTP server, if necessary.
switch# copy tftp://10.16.10.100/system-img bootflash:system-img Trying to connect to tftp server......
Note Ensure that you download the correct Cisco NX-OS system image. The system image for Supervisor-1 modules is different from the system image for Supervisor-2 modules.
Step 5 Download a kickstart image to the active supervisor module bootflash: from a TFTP server, if necessary.
switch# copy tftp://10.16.10.100/kickstart-img bootflash:kickstart-img Trying to connect to tftp server......
Step 6 Perform the upgrade by issuing the
install all
command.
Note On a dual supervisor module switch, always use the default bootflash: in the install all command syntax. Do not qualify it with “//sup-active/” or “//sup-local”. Always use the following syntax:
install all system bootflash:filename kickstart bootflash:filename.
switch# install all system bootflash:system-img kickstart bootflash:kickstart-img Verifying image bootflash:/kickstart-img [####################] 100% -- SUCCESS Verifying image bootflash:/system-img [####################] 100% -- SUCCESS Extracting “slc” version from image bootflash:/system-img. [####################] 100% -- SUCCESS Extracting “ips” version from image bootflash:/system-img. [####################] 100% -- SUCCESS Extracting “system” version from image bootflash:/system-img. [####################] 100% -- SUCCESS Extracting “kickstart” version from image bootflash:/kickstart-img. [####################] 100% -- SUCCESS Extracting “loader” version from image bootflash:/kickstart-img. [####################] 100% -- SUCCESS Compatibility check is done: Module bootable Impact Install-type Reason ------ -------- -------------- ------------ ------ 1 yes non-disruptive rolling 2 yes disruptive rolling Hitless upgrade is not supported 3 yes disruptive rolling Hitless upgrade is not supported 4 yes non-disruptive rolling 5 yes non-disruptive reset 6 yes non-disruptive reset Images will be upgraded according to following table: Module Image Running-Version New-Version Upg-Required ------ ---------- -------------------- -------------------- ------------ 1 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 2 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 3 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 4 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 5 system 1.3(2a) 1.3(1) yes 5 kickstart 1.3(2a) 1.3(1) yes 5 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 5 loader 1.2(2) 1.2(2) no 6 system 1.3(2a) 1.3(1) yes 6 kickstart 1.3(2a) 1.3(1) yes 6 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 6 loader 1.2(2) 1.2(2) no Do you want to continue with the installation (y/n)? [n] y Install is in progress, please wait. Syncing image bootflash:/kickstart-img to standby. [####################] 100% -- SUCCESS Syncing image bootflash:/system-img to standby. [####################] 100% -- SUCCESS Jan 18 23:40:03 Hacienda %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configuring console from Performing configuration copy. [####################] 100% -- SUCCESS Module 6: Waiting for module online. Auto booting bootflash:/kickstart-img bootflash:/system-img... Booting kickstart image: bootflash:/kickstart-img.... .....................................Image verification OK INIT: version 2.78 booting Checking all filesystems..r.r.. done. Uncompressing system image: bootflash:/system-img CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC INIT: Entering runlevel: 3
Step 7 Exit the switch console and open a new terminal session to view the upgraded supervisor module using the
show module
command.
If the configuration meets all guidelines when the
install all
command is issued, all modules (supervisor and switching) are upgraded. This is true for any switch in the Cisco MDS 9000 Family.
Sample install all Commands
Example 12-4 displays the result of the
install all
command issued from a console terminal that is connected to the active supervisor module. Once a switchover happens, you can see the rest of the output from the console terminal of the standby supervisor module. Example 12-5 displays the file output continuation of the
install all
command on the console of the standby supervisor module. Example 12-6 displays the result of the
install all
command issued from a console terminal for a system that contains an SSI image.
Similarly, you can view the results of the
install all
command issued from the SSH or Telnet terminal that is connected to the active supervisor module. Once a switchover happens, you need to log back into the switch and issue the
show install all status
command (see the “Upgrade Status Verification” section).
Example 12-4 Successful install all Command Issued from the Active Console
Hacienda# install all system bootflash:system-img kickstart bootflash:kickstart-img Verifying image bootflash:/kickstart-img [####################] 100% -- SUCCESS Verifying image bootflash:/system-img [####################] 100% -- SUCCESS Extracting “slc” version from image bootflash:/system-img. [####################] 100% -- SUCCESS Extracting “ips” version from image bootflash:/system-img. [####################] 100% -- SUCCESS Extracting “system” version from image bootflash:/system-img. [####################] 100% -- SUCCESS Extracting “kickstart” version from image bootflash:/kickstart-img. [####################] 100% -- SUCCESS Extracting “loader” version from image bootflash:/kickstart-img. [####################] 100% -- SUCCESS Compatibility check is done: Module bootable Impact Install-type Reason ------ -------- -------------- ------------ ------ 1 yes non-disruptive rolling 2 yes disruptive rolling Hitless upgrade is not supported 3 yes disruptive rolling Hitless upgrade is not supported 4 yes non-disruptive rolling 5 yes non-disruptive reset 6 yes non-disruptive reset Images will be upgraded according to following table: Module Image Running-Version New-Version Upg-Required ------ ---------- -------------------- -------------------- ------------ 1 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 2 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 3 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 4 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 5 system 1.3(2a) 1.3(1) yes 5 kickstart 1.3(2a) 1.3(1) yes 5 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 5 loader 1.2(2) 1.2(2) no 6 system 1.3(2a) 1.3(1) yes 6 kickstart 1.3(2a) 1.3(1) yes 6 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 6 loader 1.2(2) 1.2(2) no Do you want to continue with the installation (y/n)? [n] y Install is in progress, please wait. Syncing image bootflash:/kickstart-img to standby. [####################] 100% -- SUCCESS Syncing image bootflash:/system-img to standby. [####################] 100% -- SUCCESS Jan 18 23:40:03 Hacienda %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configuring console from Performing configuration copy. [####################] 100% -- SUCCESS Module 6: Waiting for module online. Auto booting bootflash:/kickstart-img bootflash:/system-img... Booting kickstart image: bootflash:/kickstart-img.... .....................................Image verification OK INIT: version 2.78 booting Checking all filesystems..r.r.. done. Uncompressing system image: bootflash:/system-img CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC INIT: Entering runlevel: 3
Example 12-5 displays the file output continuation of the
install all
command on the console of the standby supervisor module.
Example 12-5 Successful install all Command Output Continued from the Standby Console
Auto booting bootflash:/kickstart-img bootflash:/system-img... Booting kickstart image: bootflash:/kickstart-img.... .....................................Image verification OK INIT: version 2.78 booting Checking all filesystems..r.r.. done. Uncompressing system image: bootflash:/system-img CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC INIT: Entering runlevel: 3 Continue on installation process, please wait. The login will be disabled until the installation is completed. Module 6: Waiting for module online. Jan 18 23:43:02 Hacienda %PORT-5-IF_UP: Interface mgmt0 is up Jan 18 23:43:19 Hacienda %LICMGR-3-LOG_LIC_NO_LIC: No license(s) present for feature FM_SERVER_PKG. Application(s) shutdown in 53 days. Jan 18 23:43:19 Hacienda %LICMGR-3-LOG_LIC_NO_LIC: No license(s) present for feature ENTERPRISE_PKG. Application(s) shutdown in 50 days. Jan 18 23:43:19 Hacienda %LICMGR-3-LOG_LIC_NO_LIC: No license(s) present for feature SAN_EXTN_OVER_IP. Application(s) shutdown in 50 days. Jan 18 23:43:19 Hacienda %LICMGR-3-LOG_LICAPP_NO_LIC: Application port-security running without ENTERPRISE_PKG license, shutdown in 50 days Jan 18 23:43:19 Hacienda %LICMGR-4-LOG_LICAPP_EXPIRY_WARNING: Application Roles evaluation license ENTERPRISE_PKG expiry in 50 days Jan 18 23:44:54 Hacienda %BOOTVAR-5-NEIGHBOR_UPDATE_AUTOCOPY: auto-copy supported by neighbor, starting... Module 1: Non-disruptive upgrading. [# ] 0%Jan 18 23:44:56 Hacienda %MODULE-5-STANDBY_SUP_OK: Supervisor 5 is standby Jan 18 23:44:55 Hacienda %IMAGE_DNLD-SLOT1-2-IMG_DNLD_STARTED: Module image download process. Please wait until completion... Jan 18 23:45:12 Hacienda %IMAGE_DNLD-SLOT1-2-IMG_DNLD_COMPLETE: Module image download process. Download successful. Jan 18 23:45:48 Hacienda %MODULE-5-MOD_OK: Module 1 is online [####################] 100% -- SUCCESS Module 4: Non-disruptive upgrading. [# ] 0%Jan 18 23:46:12 Hacienda %IMAGE_DNLD-SLOT4-2-IMG_DNLD_STARTED: Module image download process. Please wait until completion... Jan 18 23:46:26 Hacienda %IMAGE_DNLD-SLOT4-2-IMG_DNLD_COMPLETE: Module image download process. Download successful. Jan 18 23:47:02 Hacienda %MODULE-5-MOD_OK: Module 4 is online [####################] 100% -- SUCCESS Module 2: Disruptive upgrading. Module 3: Disruptive upgrading. Install has been successful.
Example 12-6 displays the result of the
install all
command issued from a console terminal for a system that contains an SSI image. The install all command syncs the SSI image to the standby supervisor module.
Note You can use the install all command for the SSM only if the SSM is already up and running. For first time SSM installations.
Example 12-6 Successful install all Command Including an SSI Image
Cisco-MDS# install all system bootflash:isan-2-1-1a kickstart bootflash:boot-2-1-1a ssi bootflash:ssi-2.1.1a Verifying image bootflash:/ssi-2.1.1a [####################] 100% -- SUCCESS Verifying image bootflash:/boot-2-1-1a [####################] 100% -- SUCCESS Verifying image bootflash:/isan-2-1-1a [####################] 100% -- SUCCESS Extracting "slc" version from image bootflash:/isan-2-1-1a. [####################] 100% -- SUCCESS Extracting "ips4" version from image bootflash:/isan-2-1-1a. [####################] 100% -- SUCCESS Extracting "system" version from image bootflash:/isan-2-1-1a. [####################] 100% -- SUCCESS Extracting "kickstart" version from image bootflash:/boot-2-1-1a. [####################] 100% -- SUCCESS Extracting "loader" version from image bootflash:/boot-2-1-1a. [####################] 100% -- SUCCESS Compatibility check is done: Module bootable Impact Install-type Reason ------ -------- -------------- ------------ ------ 2 yes non-disruptive rolling 3 yes disruptive rolling Hitless upgrade is not supported 4 yes disruptive rolling Hitless upgrade is not supported 5 yes non-disruptive reset Images will be upgraded according to following table: Module Image Running-Version New-Version Upg-Required ------ ---------- -------------------- -------------------- ------------ 2 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 3 bios v1.0.8(08/07/03) v1.1.0(10/24/03) yes 4 ips4 2.0(3) 2.1(1a) yes 4 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 5 system 2.0(3) 2.1(1a) yes 5 kickstart 2.0(3) 2.1(1a) yes 5 bios v1.1.0(10/24/03) v1.1.0(10/24/03) no 5 loader 1.2(2) 1.2(2) no Do you want to continue with the installation (y/n)? [n] y Install is in progress, please wait. Module 6:Force downloading. Syncing image bootflash:/ssi-2.1.1a to standby. [####################] 100% -- SUCCESS Syncing image bootflash:/boot-2-1-1a to standby. [####################] 100% -- SUCCESS Syncing image bootflash:/isan-2-1-1a to standby. [####################] 100% -- SUCCESS [####################] 100% -- SUCCESS Performing configuration copy. [####################] 100% -- SUCCESS Module 3:Upgrading Bios/loader/bootrom. [####################] 100% -- SUCCESS Module 6:Waiting for module online. "Switching over onto standby". -----------------------------
Note If you perform the install all command to downgrade to a Cisco MDS SAN-OS release that does not support the SSM module, you must power down the SSM module when prompted by the CLI console. The boot variables for the SSM module are lost.
Example 12-7 displays the result of the
install all
command if the system and kickstart files are automatically downloaded using a remote (TFTP, FTP, SCP, or SFTP) download option. It shows an accurate and complete example.
Caution Specify the complete path of the remote location. The system will not allow you to proceed if the entire path is not accurately specified. Here are examples of incomplete
install all commands:
switch#
install all system bootflash:system-image kickstart tftp:
Please provide a complete URI
switch#
install all system scp:
Please provide a complete URI
Example 12-7 A Sample of the install all Command Issued Using a Remote Download
switch# install all system scp://user@10.10.1.1/tftpboot/HKrel/qa/final/m9500-sf1ek9-mz.1.3.2a.bin kickstart scp://user@10.10.1.1/tftpboot/HKrel/qa/final/m9500-sf1ek9-kickstart-mz.1.3.2a.bin For scp://user@10.10.1.1, please enter password: For scp://user@10.10.1.1, please enter password: Copying image from scp://user@10.10.1.1/tftpboot/HKrel/qa/final/m9500-sf1ek9-kickstart-mz.1.3.2a.bin to bootflash:///m9500-sf1ek9-kickstart-mz.1.3.2a.bin. [####################] 100% -- SUCCESS Copying image from scp://user@10.10.1.1/tftpboot/HKrel/qa/final/m9500-sf1ek9-mz.1.3.2a.bin to bootflash:///m9500-sf1ek9-mz.1.3.2a.bin. [####################] 100% -- SUCCESS Verifying image bootflash:///m9500-sf1ek9-kickstart-mz.1.3.2a.bin [####################] 100% -- SUCCESS Verifying image bootflash:///m9500-sf1ek9-mz.1.3.2a.bin [####################] 100% -- SUCCESS Extracting “slc” version from image bootflash:///m9500-sf1ek9-mz.1.3.2a.bin. [####################] 100% -- SUCCESS Extracting “ips” version from image bootflash:///m9500-sf1ek9-mz.1.3.2a.bin. [####################] 100% -- SUCCESS Extracting “system” version from image bootflash:///m9500-sf1ek9-mz.1.3.2a.bin. [####################] 100% -- SUCCESS Extracting “kickstart” version from image bootflash:///m9500-sf1ek9-kickstart-mz.1.3.2a.bin. [####################] 100% -- SUCCESS Extracting “loader” version from image bootflash:///m9500-sf1ek9-kickstart-mz.1.3.2a.bin. [####################] 100% -- SUCCESS Compatibility check is done: Module bootable Impact Install-type Reason ------ -------- -------------- ------------ ------ 1 yes non-disruptive rolling 2 yes disruptive rolling Hitless upgrade is not supported 3 yes non-disruptive rolling 4 yes non-disruptive rolling 5 yes non-disruptive reset 6 yes non-disruptive reset 7 yes non-disruptive rolling 8 yes non-disruptive rolling 9 yes disruptive rolling Hitless upgrade is not supported Images will be upgraded according to following table: Module Image Running-Version New-Version Upg-Required ------ ---------- -------------------- -------------------- ------------ 1 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 2 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 3 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 4 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 5 system 1.3(1) 1.3(2a) yes 5 kickstart 1.3(1) 1.3(2a) yes 5 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 5 loader 1.2(2) 1.2(2) no 6 system 1.3(1) 1.3(2a) yes 6 kickstart 1.3(1) 1.3(2a) yes 6 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 6 loader 1.2(2) 1.2(2) no 7 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 8 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 9 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no Do you want to continue with the installation (y/n)? [n]
Example 12-8 displays the
install all
command output of a failed operation due to a lack of disk space.
Example 12-8 Failed Operation Due to a Full bootflash: File System
switch# install all system bootflash:isan-1.3.2a kickstart bootflash:boot-1.3.2a Verifying image bootflash:/boot-1.3.2a [####################] 100% -- SUCCESS Verifying image bootflash:/isan-1.3.2a [####################] 100% -- SUCCESS Extracting “slc” version from image bootflash:/isan-1.3.2a. [####################] 100% -- SUCCESS Extracting “ips” version from image bootflash:/isan-1.3.2a. [####################] 100% -- SUCCESS Extracting “system” version from image bootflash:/isan-1.3.2a. [####################] 100% -- SUCCESS Extracting “kickstart” version from image bootflash:/boot-1.3.2a. [####################] 100% -- SUCCESS Extracting “loader” version from image bootflash:/boot-1.3.2a. [####################] 100% -- SUCCESS Compatibility check is done: Module bootable Impact Install-type Reason ------ -------- -------------- ------------ ------ 1 yes non-disruptive rolling 2 yes disruptive rolling Hitless upgrade is not supported 3 yes non-disruptive rolling 4 yes non-disruptive rolling 5 yes non-disruptive reset 6 yes non-disruptive reset 7 yes non-disruptive rolling 8 yes non-disruptive rolling 9 yes disruptive rolling Hitless upgrade is not supported Images will be upgraded according to following table: Module Image Running-Version New-Version Upg-Required ------ ---------- -------------------- -------------------- ------------ 1 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 2 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 3 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 4 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 5 system 1.3(1) 1.3(2a) yes 5 kickstart 1.3(1) 1.3(2a) yes 5 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 5 loader 1.2(2) 1.2(2) no 6 system 1.3(1) 1.3(2a) yes 6 kickstart 1.3(1) 1.3(2a) yes 6 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 6 loader 1.2(2) 1.2(2) no 7 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 8 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no 9 bios v1.1.0(10/24/03) v1.0.8(08/07/03) no Do you want to continue with the installation (y/n)? [n] y Install is in progress, please wait. Syncing image bootflash:/boot-1.3.2a to standby. [####################] 100% -- SUCCESS Syncing image bootflash:/isan-1.3.2a to standby. [# ] 0% -- FAIL. Return code 0x401E0008 (request was aborted, standby disk may be full). Install has failed. Return code 0x40930013 (Syncing images to standby failed). Please identify the cause of the failure, and try 'install all' again. Dec 15 19:36:42 switch %SYSMGR-3-SERVICE_TERMINATED: Service “installer” (PID 5470) has finished with error code SYSMGR_EXITCODE_FAILURE_NOCALLHOME (20).
Example 12-9 displays the
install all
command output of a failed operation due to an invalid image.
Example 12-9 Failed Operation Due to an Invalid Image
install all system bootflash:junk kickstart bootflash:junk Verifying image bootflash:/junk [# ] 0% -- FAIL. Return code 0x4045001E (mismatch between actual image type and boot variable). Compatibility check failed. Return code 0x40930011 (Image verification failed). Hacienda# Jan 19 00:20:35 Hacienda %SYSMGR-3-SERVICE_TERMINATED: Service “installer” (PID 5664) has finished with error code SYSMGR_EXITCODE_FAILURE_NOCALLHOME (20).