*********************************************************************** BAY NETWORKS, INC. Copyright (c) 1996-1998 All Rights Reserved Accelar 1000 Series Routing Switch Software Version 1.3.0 *********************************************************************** Accelar 1000 Series Software Upgrade Procedure ============================================== This document describes the procedure for upgrading the flash firmware in an Accelar 1000 Series routing switch. 1) From v1.1.6 (or 1.1.x) to v1.3.0 firmware. 2) From v1.0 to v1.3.0 firmware Accelar 1000 Series routing switches have two software images that reside in flash memory: the boot monitor and the runtime image. The boot monitor image is low-level code that initializes the devices on the Silicon Switch Fabric (SSF) module and starts the boot process. The runtime image is the code that executes initializing the I/O modules and provides full routing switch functionality. Prerequisites: ============== To upgrade the flash images, you will need the following: - the new 1.3.0 runtime and boot monitor image files - a TFTP server - a network connection to the TFTP server - a direct console connection (9600, 8, N, 1) or a telnet connection Note: A direct console connection is recommended when performing the upgrade procedure because it is REQUIRED if it is necessary to reverse the upgrade procedure. Flash Memory Overview: ====================== The boot monitor image is stored in a reserved area in flash memory that cannot be accessed directly. The boot monitor image is updated by executing a boot monitor updater that in turn updates the boot monitor image. The runtime image is stored in flash memory in an area that is accessible using the command line interface (CLI). Note: Upgrading flash memory requires rebooting the switch and will disrupt network operation. The upgrade procedure should be performed during network downtime. The Accelar 1000 Series routing switch has 4 MB of flash memory for images. Typical sizes for the various files mentioned in this document are as follows: a runtime image is less than 1 MB, a boot monitor updater is less than 100K, and the log file is 128K. Flash Memory Update Procedure: ============================== /* From v1.1.6 to v1.3.0 firmware */ ======================================= This procedure assumes you will be updating both the boot monitor image and the runtime image in flash to version 1.3.0. Be sure to read and understand the procedure below BEFORE attempting to upgrade the software. WARNING: It is VERY IMPORTANT that you follow the instructions below to simplify the downgrading of the software to v1.1.6, should that be necessary. The procedure for reverting to a pre-upgrade state is covered at the end of this document; it is recommended you also review that procedure prior to starting the software upgrade. Step 1: Remove the redundant SSF module. ---------------------------------------- For Accelar 1200 chassis with redundant SSF modules, the upgrade should be focused on one SSF module at a time to avoid confusion. If present, the standby SSF module should be removed from the chassis. The flash memory update procedure will need to be repeated on the second SSF module to ensure the flash image versions are synchronized. The upgrade procedure requires rebooting the SSF module. If the redundant SSF module is not removed, rebooting the active SSF will cause SSF modules to swap active and standby roles, adding complication to the upgrade process. Step 2: Login to the Runtime CLI. --------------------------------- The update procedure can be performed at the local console or through a telnet connection. The console port on the SSF module is a serial DTE device operating at 9600 bps, 8 data bits, no parity and 1 stop bit. Note: The console port is the preferred method because you must be at the console to downgrade to v1.1.6 if necessary. At the CLI 'Login:' prompt, enter the password for read-write or read-write-all access privileges. ******************************** * Bay Networks,Inc. * * Copyright (c) 1996-1997 * * All Rights Reserved * * Accelar 1100 * * Software Release 1.1.6 * ******************************** Login: *** Password: *** Bay> Step 3: Copy the v1.3.0 runtime image into flash. ----------------------------------------------- The 1.3.0 runtime image is loaded into the Accelar switch via a TFTP copy operation initiated at the Accelar CLI. Before attempting a TFTP copy operation, it is useful to verify that the TFTP server is reachable and responding. This can be done using the 'ping' command, initated at the CLI prompt. In the example below, the TFTP server has an address of 10.10.20.100. Bay> ping 10.10.20.100 10.10.20.100 is alive Bay> The runtime CLI 'copy' command allows the copying of files to and from flash memory, PCMCIA cards and TFTP servers. To copy the new runtime image file from the TFTP server to flash memory, use the copy command as shown below, specifying the TFTP server's TCP/IP address and the path to the new runtime image file as follows: Bay> copy tftp flash Enter source tftp server address [0.0.0.0]: 10.10.20.100 Enter source file []: /tftpboot/acc1.3.0 programming flash:3 ... xxxxxx bytes verifying flash:3 ... done tftp result: success Bay> The runtime image is a large file and can take about 1 minute to download. The runtime CLI copy command works silently and does not indicate the progress of the TFTP copy. Note: Some Windows-based TFTP servers do not support long filenames even though long filenames are displayed. If your TFTP server does not support long filenames, you may experience TFTP failures. You can rename the image files without affecting the upgrade process. Step 4: Rearrange files in flash. --------------------------------- To simplify the upgrade and downgrade process, the new runtime image should be moved to the first file position in the flash file system. The files are rearranged in flash using the copy, delete, and squeeze commands as shown below. In this step, the current (1.1.6) runtime image (flash:1) and the log file (flash:2) will be copied to the end of flash; the 1.3.0 runtime image will remain as file three (flash:3). Bay> directory flash Device: flash FN Name Flags Length -- ---- ----- ------ 1 acc1.1.6 XZN 1000443 2 syslog LN 131072 3 acc1.3.0 XZN 1362138 -- ------ 3 files bytes used= 2642004 free=1552300 Bay> Copy files 1 & 2 to be files 4 & 5. Bay> copy fl:1 fl:4 Bay> copy fl:2 fl:5 Now delete files 1 and 2, and squeeze the flash file system. This has the effect of renumbering the files so that the v1.3.0 runtime image is now the first file in flash (flash:1), the v1.1.6 runtime image is the second file (flash:2), and the system log file is the third file (flash:3). The 'delete' command marks a file for deletion; the 'squeeze' command actually deletes the files and compresses the file system, renumbering the files in the process. Bay> delete flash:1 Bay> delete flash:2 Bay> squeeze flash recovering deleted file space ... success Bay> directory flash Device: flash FN Name Flags Length -- ---- ----- ------ 1 acc1.3.0 XZN 1362138 2 acc1.1.6 XZN 1000443 3 syslog LN 131072 -- ------ 3 files bytes used= 2642004 free=1552300 Step 5: Back up v1.1.6 configuration file. --------------------------------------- The v1.1.6 configuration file can be used by the v1.3.0 runtime, but the v1.1.6 runtime will not read v1.3.0 configuration files. For this reason, you should copy the currentv1.1.6 configuration file to flash in case you must revert to the v1.1.6 runtime. Before backing up the current configuration, change the primary boot choice to flash:2, which is the v1.1.6 runtime image. This selection will then be saved in the configuration you copy to the flash file system. Bay> config sys set primary flash:2 Bay> save Bay> copy config flash programming flash:4 ... 4376 bytes Bay> Step 6: Set primary boot choice to v1.3.0 runtime. ------------------------------------------------ Set the primary boot choice to the first file in the flash file system, that is, the v1.3.0 runtime image. Bay> config sys set primary flash:1 Bay> save Bay> Step 7: Copy v1.3.0 boot monitor updater to flash ------------------------------------------------ Copy the v1.3.0 boot monitor updater into the flash via tftp. Bay> copy tftp flash Enter source tftp server address [10.10.20.100]: 10.10.20.100 Enter source file [acc1.3.0]: accboot1.3.0.gz programming flash:5 ... 85543 bytes verifying flash:5 ... done tftp result: success Bay> Step 8: Upgrade the boot monitor. --------------------------------- WARNING: This step reboots the routing switch and will disrupt network operation. The boot monitor upgrade process involves running a boot monitor updater image (an executable) from the TFTP server. This updater image will load the new boot monitor into the nonvolatile RAM of your Accelar switch. You may upgrade your boot monitor by invoking the boot monitor updater image located on your TFTP server by means of the "boot net" command. The syntax of this command is 'boot net ,' where: is the IP address of the tftp server and is the file to download and execute (in that order) on the tftp server. Note: If you are performing the upgrade when connected to the switch with a telnet connection, you will lose connectivity after the boot command executes. Additionally, when the boot monitor is updated and the switch boots with the v1.3.0 runtime, the banners will not be visible via telnet, but instead will appear on the local console (if attached). You will be able to re-establish the telnet connection to complete the upgrade when the switch is fully booted in a few minutes. Bay> boot tftp ip 10.10.20.100 file /tftpboot/accboot1.3.0 tftp result: success Note: If you are running Boot Monitor v1.3.0, the system will NOT automatically reset after the TFTP. You must continue on in the process by typing 'reset' at the next Bay> prompt. Bay> reset If you invoked the boot net command via a telnet session, your connection will be dropped at this point. When the upgrade process completes in a few seconds, the switch will reboot into the new runtime image, retaining your previous switch configuration. When this reboot is complete, typically in a couple of minutes, you should be able to re-establish your telnet session with the Accelar switch. If you invoked the boot net command from the local console, then you will see upgrade and boot messages similar to the following: ############### ACCELAR CPU BOOT FLASH Update ################ File ACCBOOT.ROM found in loaded image Boot Monitor Version v1.3.0 Image size: text 132988 data 26848 bss 11240 Number of flash sectors to be programmed: 3 WARNING: You are about to re-program your Boot Monitor FLASH image. Do NOT turn off power or press reset until this procedure is completed. Otherwise the card may be permanently damaged!!! Do you wish to continue? (y or n)y Erase of 3 sectors completed -Verifying new FLASH Image... 196608 matches, 0 mismatches Update complete! Press any key to reboot Accelar Monitor v1.3.0 CPU: 60Mhz PPC 403GCX Type 2 Rev 1 in Slot 5 DRAM: 16M Chassis: 1200 Reason for Last Reset: PWR/BUTTON/SOFT Slot 1 is occupied Slot 7 is occupied Power supply 2 not present Press any key to stop autoboot After the boot monitor is upgraded, the routing switch will automatically reboot and load the v1.3.0 runtime image. Accelar Monitor v1.3.0 CPU: 60Mhz PPC 403GCX Type 2 Rev 1 in Slot 5 DRAM: 16M Chassis: 1200 Reason for Last Reset: PWR/BUTTON/SOFT Slot 1 is occupied Slot 7 is occupied Power supply 2 not present running boot script at 0x8000f004 monitor> boot flash:1 Booting from [flash:1] on-board flash memory Configuration from [nvram] ... Unzipping file acc1.3.0 Details /export/home2/projects/first/rel1.3/rel1.3.0/main/hw/acc1.3.0.st on Fri Sep 4 16:15:46 PDT 1998 from 0x761000b0 to 0x80010000 1361962 to 7257934 bytes Attaching network interface nicEvb0... done. Null 0.0.0.0 inet address for interface nicEvb. Attaching network interface lo0... done. Initializing card in slot #1 ... OK Initializing card in slot #7 ... OK [000 00:00:16:850] INFO: Code=0x0 Task=rcStart: System is ready Accelar System Software Release 1.3.0 Copyright (c) 1996-1998 Bay Networks, Inc. [000 00:00:02:383] INFO: Code=0x0 Task=rcStart: System boot [000 00:00:02:416] INFO: Code=0x0 Task=rcStart: Accelar System Software Release 1.3.0 [000 00:00:02:450] INFO: Code=0x0 Task=rcStart: System log file flash:system log file:0:43 ******************************** * Bay Networks,Inc. * * Copyright (c) 1996-1998 * * All Rights Reserved * * Accelar 1200 * * Software Release 1.3.0 * ******************************** Login: rwa Password: *** Step 9: Verify routing switch operation. ---------------------------------------- After performing the boot monitor upgrade, the Accelar switch should reboot into the 1.3.0 runtime image (flash:1) and use the configuration stored in nvram. At this point, you should log into your switch via either the local console or telnet, and verify that your switch is configured and operating properly in the new 1.3.0 environment. The v1.3.0 runtime has three levels of access (read-only, read-write and read-write-all). Both a username and password must be specified. The default username and password for read-write access is 'rw'. ******************************** * Bay Networks,Inc. * * Copyright (c) 1996-1998 * * All Rights Reserved * * Accelar 1100 * * Software Release 1.3.0 * ******************************** Login: rw Password: ** Accelar-1200# If the routing switch is not operating properly, use the v1.1.6 downgrade procedure described below. Note: You will need to be at the routing switch console to downgrade the software to v1.1.6. There is no difference in the format of the v1.1.6 & v1.3.0 filesystem. No separate procedure is required. Step 10: Repeat process for second SSF module. ---------------------------------------------- By following the steps above, the flash images have been updated on one SSF module. For Accelar 1200 chassis with redundant SSF modules, the process should be repeated on the second SSF module to ensure the flash image versions are synchronized. Downgrade Procedure to v1.1.6 =========================== The downgrade procedure from v1.3.0 to v1.1.6 described below . Note: The downgrade procedure MUST be performed at the local routing switch console. Step 1: Login to v1.3.0 runtime CLI. ----------------------------------- The v1.3.0 runtime has three levels of access (read-only, read-write and read-write-all). Both a username and password must be specified. The default username and password for read-write access is 'rw'. ******************************** * Bay Networks,Inc. * * Copyright (c) 1996-1998 * * All Rights Reserved * * Accelar 1100 * * Software Release 1.3.0 * ******************************** Login: rw Password: ** Accelar-1200# Step 2: Copy v1.1.6 config to nvram. ----------------------------------- During the upgrade procedure, the v1.1.6 configuration with primary boot choice of flash:2 was saved to flash memory. You can use the directory command to locate the file: Bay> directory flash Device: flash FN Name Flags Length -- ---- ----- ------ 1 acc1.3.0 XZN 1362138 2 acc1.1.6 XZN 1000443 3 syslog LN 131072 4 config CN 4376 5 accboot1.1.1 XZN 87345 -- ------ 4 files bytes used= 2733725 free=1460579 Bay> In the directory listing above, the saved configuration is flash:4. Copy the configuration to nvram: Accelar-1200# copy flash:4 nvram nvram configuration updated Accelar-1200#save Accelar-1200# Step 3: Boot the switch with v1.1.6 boot monitor updater in the flash. ----------------------------------------------------------------------- Note: You MUST perform this step at the routing switch local console because you must confirm downgrading the boot monitor image and press a key to reset the routing switch. During the upgrade procedure, the v1.1.6 boot monitor updater was copied to flash memory. In the directory listing above, it is flash:5. Boot flash:5 to downgrade to the v1.1.6 boot monitor: Accelar-1200# boot flash:5 Accelar Monitor v1.1.6 CPU: 50Mhz PPC 403GCX Type 3 Rev 2 in Slot 4 DRAM: 16M Chassis: 1100 Reason for Last Reset: PWR/BUTTON/SOFT Slot 3 is occupied Power supply 2 not present running boot script at 0x8000f004 monitor> boot flash:5 Booting from [flash:5] on-board flash memory Configuration from [nvram] ... Unzipping file /export/acura3/projects/first/rel1.1/rel1.1.6 /boot/403_EVB/openbios/flash/flshbo Details rel1.1/rel1.1.6/boot/403_EVB/openbios/flash on from 0x762000b0 to 0x80010038 85367 to 576992 bytes ############### ACCELAR CPU BOOT FLASH Update ################ File ACCBOOT.IMG found in loaded image Boot Monitor Version v1.1.6 Image size: text 129428 data 26448 bss 10872 Number of flash sectors to be programmed: 3 WARNING: You are about to re-program your Boot Monitor FLASH image. Do NOT turn off power or press reset until this procedure is completed. Otherwise the card may be permanently damaged!!! Do you wish to continue? (y or n)y Erase of 3 sectors completed -Verifying new FLASH Image... 196608 matches, 0 mismatches Update complete! Press any key to reboot Step 4: Confirm routing switch operation. ----------------------------------------- After rebooting the routing switch, you will be running the same configuration and runtime software run prior to performing the v1.3.0 upgrade. The flash file system will have additional files and the primary boot choice may be different, but the switch will be operating the same way prior to upgrading the software. ------------------------------------------------------------------------ Flash Memory Update Procedure: ============================== /* From v1.0 to v1.3.0 firmware */ ======================================= This procedure assumes you will be updating both the boot monitor image and the runtime image in flash to version 1.3.0. Be sure to read and understand the procedure below BEFORE attempting to upgrade the software. WARNING: It is VERY IMPORTANT that you follow the instructions below. The downgrading of the software to v1.0 is NOT POSSIBLE. Should that be necessary, Please contact Bay Networks Technical Support Center. Step 1: Remove the redundant SSF module. ---------------------------------------- For Accelar 1200 chassis with redundant SSF modules, the upgrade should be focused on one SSF module at a time to avoid confusion. If present, the standby SSF module should be removed from the chassis. The flash memory update procedure will need to be repeated on the second SSF module to ensure the flash image versions are synchronized. The upgrade procedure requires rebooting the SSF module. If the redundant SSF module is not removed, rebooting the active SSF will cause SSF modules to swap active and standby roles, adding complication to the upgrade process. Step 2: Login to the Runtime CLI. --------------------------------- The update procedure can be performed at the local console or through a telnet connection. The console port on the SSF module is a serial DTE device operating at 9600 bps, 8 data bits, no parity and 1 stop bit. At the CLI 'Login:' prompt, enter the password for read-write or read-write-all access privileges. ******************************** * Bay Networks,Inc. * * Copyright (c) 1996-1997 * * All Rights Reserved * * Accelar 1100 * * Software Release 1.0.0 * ******************************** Login: ****** Bay> Step 3: Copy the v1.3.0 runtime image into flash. ----------------------------------------------- The 1.3.0 runtime image is loaded into the Accelar switch via a TFTP copy operation initiated at the Accelar CLI. Before attempting a TFTP copy operation, it is useful to verify that the TFTP server is reachable and responding. This can be done using the 'ping' command, initated at the CLI prompt. In the example below, the TFTP server has an address of 10.10.20.100. Bay> ping 10.10.20.100 10.10.20.100 is alive Bay> The runtime CLI 'copy' command allows the copying of files to and from flash memory, PCMCIA cards and TFTP servers. To copy the new runtime image file from the TFTP server to flash memory, use the copy command as shown below, specifying the TFTP server's TCP/IP address and the path to the new runtime image file as follows: Bay> copy tftp flash Enter source tftp server address [0.0.0.0]: 10.10.20.100 Enter source file []: /tftpboot/acc1.3.0 programming flash:3 ... xxxxxx bytes verifying flash:3 ... done tftp result: success Bay> The runtime image is a large file and can take about 1 minute to download. The runtime CLI copy command works silently and does not indicate the progress of the TFTP copy. Note: Some Windows-based TFTP servers do not support long filenames even though long filenames are displayed. If your TFTP server does not support long filenames, you may experience TFTP failures. You can rename the image files without affecting the upgrade process. Step 4: Rearrange files in flash. --------------------------------- To simplify the upgrade and downgrade process, the new runtime image should be moved to the first file position in the flash file system. The files are rearranged in flash using the copy, delete, and squeeze commands as shown below. In this step, the current (1.0.0) runtime image (flash:1) and the log file (flash:2) will be copied to the end of flash; the 1.3.0 runtime image will remain as file three (flash:3). Bay> dir fl Device: flash ------ File 1: /export/acura3/projects/first/rel1.0/rel1.0.0/main/hw/accelar.st Version: rel1.0/rel1.0.0/main on Fri Jan 9 11:28:28 PST Length: 895550 EntryPoint: 0x10000 Flags: XZ (0x300) CRC: 0x6e79 File 2: system log file Version: 1.0 Length: 130896 EntryPoint: 0x0 Flags: L (0x102) CRC: 0x0 blocks: 256 used: 41,0 free: 214,256 File 3: 1.3.0.st on Fri Sep 4 16:15:46 PDT 1998 Version: /export/home2/projects/first/rel1.3/rel1.3.0/main/hw/acc1.3.0.b23.st on Fri Sep 4 16:15:46 PDT 1998 Length: 1361962 EntryPoint: 0x10000 Flags: XZ (0x700) CRC: 0x4065 Copy files 1 & 2 to be files 4 & 5. Bay> copy fl:1 fl:4 Bay> copy fl:2 fl:5 Now delete files 1 and 2, and squeeze the flash file system. This has the effect of renumbering the files so that the v1.3.0.b23 runtime image is now the first file in flash (flash:1), the v1.1.4 runtime image is the second file (flash:2), and the system log file is the third file (flash:3). The 'delete' command marks a file for deletion; the 'squeeze' command actually deletes the files and compresses the file system, renumbering the files in the process. Bay> delete flash:1 Bay> delete flash:2 Bay> squeeze flash recovering deleted file space formatting flash ... done programming flash:1 ... 948423 bytes verifying flash:1 ... done programming flash:2 ... 897850 bytes verifying flash:2 ... done programming flash:3 ... 131072 bytes verifying flash:3 ... done 2 files squeezed from device flash Files: 3 BlocksUsed: 31 BytesUsed: 2031616 BlocksFree: 33 BytesFree: 2162688 Bay> dir fl Device: flash ------ File 1: rel.13.0.b23.st on Fri Sep 4 16:15:46 PDT 1998 Version: /export/home2/projects/first/rel1.3/rel1.3.0.b23/main/hw/acc1.3.0.b23.st on Fri Sep 4 16:15:46 PDT 1998 Length: 1361962 EntryPoint: 0x10000 Flags: XZ (0x700) CRC: 0x4065 File 2: /export/acura3/projects/first/rel1.0/rel1.0.0/main/hw/accelar.st Version: rel1.0/rel1.0.0/main on Fri Jan 9 11:28:28 PST Length: 895550 EntryPoint: 0x10000 Flags: XZ (0x300) CRC: 0x6e79 File 3: system log file Version: 1.0 Length: 130896 EntryPoint: 0x0 Flags: L (0x102) CRC: 0x0 blocks: 256 used: 41,0 free: 214,256 Step 5: The v1.0.0 configuration file. --------------------------------------- The v1.0.0 configuration file can be used by the v1.3.0.b23 runtime. The v1.3.0.b23 configuration cannot be run by v1.0.0 runtime image. Step 6: Set primary boot choice to v1.3.0.b23 runtime. ------------------------------------------------ Set the primary boot choice to the first file in the flash file system, that is, the v1.3.0.b23 runtime image. Bay> sys set primary flash:1 Bay> save Bay> Step 7: Copy v1.3.0.b23 boot monitor updater to flash ------------------------------------------------ Bay> copy tftp flash Enter source tftp server address [10.10.20.100]: 10.10.20.100 Enter source file [acc1.3.0.b23]: accboot1.3.0.b23.gz programming flash:5 ... 85543 bytes verifying flash:5 ... done tftp result: success Bay> Step 8: Upgrade the boot monitor. --------------------------------- WARNING: This step reboots the routing switch and will disrupt network operation. The boot monitor upgrade process involves running a boot monitor updater image (an executable) from the TFTP server. This updater image will load the new boot monitor into the nonvolatile RAM of your Accelar switch. You may upgrade your boot monitor by invoking the boot monitor updater image located on your TFTP server by means of the "boot net" command. The syntax of this command is 'boot net ,' where: is the IP address of the tftp server and is the file to download and execute (in that order) on the tftp server. Note: If you are performing the upgrade when connected to the switch with a telnet connection, you will lose connectivity after the boot command executes. Additionally, when the boot monitor is updated and the switch boots with the v1.3.0.b23 runtime, the banners will not be visible via telnet, but instead will appear on the local console (if attached). You will be able to re-establish the telnet connection to complete the upgrade when the switch is fully booted in a few minutes. Bay> boot net 10.10.20.100 accboot1.3.0.b23 tftp result: success Note: If you are running Boot Monitor v1.3.0.b23, the system will NOT automatically reset after the TFTP. You must continue on in the process by typing 'reset' at the next Bay> prompt. Bay> reset If you invoked the boot net command via a telnet session, your connection will be dropped at this point. When the upgrade process completes in a few seconds, the switch will reboot into the new runtime image, retaining your previous switch configuration. When this reboot is complete, typically in a couple of minutes, you should be able to re-establish your telnet session with the Accelar switch. If you invoked the boot net command from the local console, then you will see upgrade and boot messages similar to the following: Accelar Monitor v1.0.0 CPU: 50Mhz PPC 403GCX Type 3 Rev 2 in Slot 4 DRAM: 16M Chassis: 1100 Reason for Last Reset: PWR/BUTTON/SOFT Slot 3 is occupied Power supply 2 not present running boot script at 0x8000f004 monitor> boot dram 0x80c54538 Booting from [dram] System Memory... Unzipping file enbios/flash/accboot1.3.0.b23 on Tue Mar 3 16: Version /export/acura3/projects/first/rel1.3/rel1.3.0.b23 /boot/403_EVB/openbios/flash/accboot1.3.0.b23 on Tue Mar 3 16: from 0x804000b0 to 0x80010038 87041 to 576992 bytes ############### ACCELAR CPU BOOT FLASH Update ################ File ACCBOOT.ROM found in loaded image Boot Monitor Version v1.3.0.b23 Image size: text 132924 data 26848 bss 11240 Number of flash sectors to be programmed: 3 WARNING: You are about to re-program your Boot Monitor FLASH image. Do NOT turn off power or press reset until this procedure is completed. Otherwise the card may be permanently damaged!!! Do you wish to continue? (y or n)y Erase of 3 sectors completed -Verifying new FLASH Image... 196608 matches, 0 mismatches Update complete! Press any key to reboot After the boot monitor is upgraded, the routing switch will automatically reboot and load the v1.3.0.b23 runtime image. Accelar Monitor v1.3.0.b23 CPU: 50Mhz PPC 403GCX Type 3 Rev 2 in Slot 4 DRAM: 16M Chassis: 1100 Reason for Last Reset: PWR/BUTTON/SOFT Slot 3 is occupied Power supply 2 not present Press any key to stop autoboot User Selected Boot Sources Primary = flash:1 Secondary = flash: Tertiary = net Config = nvram Booting from [flash:1] on-board flash memory Configuration from [nvram] ... Unzipping file acc1.3.0.b23 Details /export/home2/projects/first/rel1.3/rel1.3.0.b23/main/hw/acc1.3.0.b23.st on Fri Sep 4 16:15:46 PDT 1998 from 0x761200b0 to 0x80010000 1361962 to 7257934 bytes Attaching network interface nicEvb0... done. Null 0.0.0.0 inet address for interface nicEvb. Attaching network interface lo0... done. Accelar System Software Release 1.3.0.b23 Copyright (c) 1996-1998 Bay Networks, Inc. [000 00:00:02:383] INFO: Code=0x0 Task=rcStart: System boot [000 00:00:02:416] INFO: Code=0x0 Task=rcStart: Accelar System Software Release 1.3.0.b23 [000 00:00:02:450] INFO: Code=0x0 Task=rcStart: System log file flash:system log file:0:43 ** Using configuration from nvram ** [000 00:00:06:316] INFO: Code=0x0 Task=rcStart: System is ready ******************************** * Bay Networks,Inc. * * Copyright (c) 1996-1998 * * All Rights Reserved * * Accelar 1200 * * Software Release 1.3.0.b23 * ******************************** Login: *** Password: *** Step 9: Verify routing switch operation. ---------------------------------------- After performing the boot monitor upgrade, the Accelar switch should reboot into the 1.3.0.b23 runtime image (flash:1) and use the configuration stored in nvram. At this point, you should log into your switch via either the local console or telnet, and verify that your switch is configured and operating properly in the new 1.3.0.b23 environment. The v1.3.0.b23 runtime has three levels of access (read-only, read-write and read-write-all). Both a username and password must be specified. The default username and password for read-write access is 'rw'. ******************************** * Bay Networks,Inc. * * Copyright (c) 1996-1998 * * All Rights Reserved * * Accelar 1100 * * Software Release 1.3.0.b23 * ******************************** Login: rw Password: ** Accelar-1200# Step 10: Convert to v1.3.0.b23 file system. ------------------------------------- Note: Before completing this step, please verify the routing switch is operating properly with the v1.3.0.b23 software. Once the file system is converted to the v1.3.0.b23 format, the v1.0 runtime image will not load. The procedure to get a v1.0 runtime image on a routing switch with a v1.3.0.b23 file system requires local console access and that the flash be completely erased. The flash file system has been enhanced in v1.3.0.b23, so the existing files must be upgraded to the new format. The v1.3.0.b23 firmware supports both file numbers and file names in the flash file system, whereas v1.0 only supported file numbers. In the sample directory below, the 'N' flag indicates the file has been updated to the new file naming format. Bay> dir fl Device: flash ------ File 1: rel.13.0.b23.st on Fri Sep 4 16:15:46 PDT 1998 Version: /export/home2/projects/first/rel1.3/rel1.3.0.b23/main/hw/acc1.3.0.b23.st on Fri Sep 4 16:15:46 PDT 1998 Length: 1361962 EntryPoint: 0x10000 Flags: XZ (0x700) CRC: 0x4065 File 2: /export/acura3/projects/first/rel1.0/rel1.0.0/main/hw/accelar.st Version: rel1.0/rel1.0.0/main on Fri Jan 9 11:28:28 PST Length: 895550 EntryPoint: 0x10000 Flags: XZ (0x300) CRC: 0x6e79 File 3: system log file Version: 1.0 Length: 130896 EntryPoint: 0x0 Flags: L (0x102) CRC: 0x0 blocks: 256 used: 41,0 free: 214,256 To convert all files in flash (or PCMCIA) to the v1.3.0.b23 file system format, use the recover command. Accelar-1200# recover flash recovering files ... success Accelar-1200# directory flash Device: flash FN Name Flags Length -- ---- ----- ------ 1 acc1.3.0.b23 XZN 944692 2 accelar.st XZN 895483 3 syslog LN 130896 4 config CN 4376 -- ------ 4 files bytes used= 1047447 free=2097152 Accelar-1200# Step 11: Repeat process for second SSF module. ---------------------------------------------- By following the steps above, the flash images have been updated on one SSF module. For Accelar 1200 chassis with redundant SSF modules, the process should be repeated on the second SSF module to ensure the flash image versions are synchronized. Downgrade Procedure to v1.0 =========================== The downgrade procedure from v1.3.0.b23 to v1.0.0 is not supported. *********************************************************************** Contact Information: Technical Support for North and South America 1-800-252-6926 Technical Support for Europe, Middle East and Africa 33-492-966-968 Technical Support for Australia, Asia and the Pacific 61-2-9927-8800 ***********************************************************************