计算机硬件及网络博科三层交换机课件.pptVIP

The Essentials File Management The flash memory is divided into two different storage areas. This allows you to have two different software image versions stored in the flash memory. Secondary Flash is storage space for Upgrade Code: Put new code in secondary flash Schedule a reload to boot on secondary flash during low traffic periods. Unsuccessful reloads will cause the system to revert back to primary flash. When confidence is established in upgrade code, execute a “copy flash flash primary” to overwrite old software image with upgrade image in primary flash. To view the contents of the flash memory, enter the command: SW-FastIronshow flash Looking at the output above, you can see what images are stored in the primary and secondary flash areas. Configuration flies are also stored in both the primary and secondary flash partitions. Only 1 is accessable by the user. The second is a copy for system reliability, it uses a checksum and if not valid, will use the second copy for boot configuration. SW-FastIron#write memory – Will save your configuration SW-FastIron#show config – Will display your configuration * File Management (Cont.) Specify where to boot from You can specify where to boot from with the: “boot system flash” command. By default, you will boot from the primary flash, but you can have your system boot from secondary flash, from a tftp server, or a bootp server. If you enter boot system commands from the Privileged level, the system will immediately reboot. If entered at the CONFIG level, they will be executed at the next reboot. Booting from TFTP RAM memory is erased when the system shuts down. When the system reboots, by default,it will look in Flash Primary for its image to boot on and loads this into RAM. If you have chosen to boot from a TFTP server, after booting you must copy the booted image file from the TFTP server to Flash Primary so that the next system boot will maintain your current functions independent of the TFTP server connec