Cisco CRS-1 - Carrier Routing System Router Migration Manual page 242

Upgrading Your File System From FAT16 to FAT32
Step 4 When the turboboot installation is complete the optional PIEs can be added and activated from admin
mode.
Example
The complete installation takes about 1 hour and 30 minutes.
•
•
•
•
Upgrading Your File System From FAT16 to FAT32
This section discusses how to change the file system on the flash disk from the FAT16 format to the
FAT32 format or from the FAT32 format back to the FAT16 format. In each of these scenarios, we
assume the flash disk has been upgraded to a 4GB flash disk. Although it's possible to have a 1GB or
2GB Flash Disk with FAT32, it offers no benefit over FAT16 thus we don't recommending using FAT32
with those size flash disks.
Also if your 4GB flash disk has been partitioned into two 2GB partitions upgrading your file system from
the FAT16 format to the FAT32 format offers no benefits over remaining with the FAT16 format. So the
only reason to change to FAT32 is to partition a 4GB flash disk as a 3.5GB and 0.5GB partition. This
type of partition is recommended in order to partition the amount of space. This may be required for
future versions of Cisco IOS XR software that require more than 2GB of flash space.
This can be done as soon as you upgrade to Cisco IOS XR software Release 3.8 and higher or you can
wait until the image will exceed the 2GB partition.
Rolling back down to Cisco IOS XR software Release 3.7.2 or lower (which does not support a FAT32
Warning
boot disk) is much more difficult after the file system and partition has been changed to the FAT32
format. If you want to have an easy rollback capability, do not change the file system to FAT32 until
you are upgrading from a Split Boot supported image to another Split Boot support image. Changing
the file system is only possible when running Cisco IOS XR software Release 3.8 or higher.
Also, using the CLI based format command will change the file system back to FAT16.
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
A-4
Standby node last went not ready Wed Oct 13 09:33:14 2010: 29 seconds ago
Standby node last went ready Wed Oct 13 09:33:15 2010: 28 seconds ago
There have been 0 switch-¦-overs since reload
Active node reload "Cause: Turboboot completed successfully"
Standby node reload "Cause: MBI-¦-HELLO reloading node on receiving reload
notification"
router(admin)# install add source tftp://10.1.1.1/users/bla/ hfr-¦-mcast-¦- px.pie-¦-
4.0.0.T hfr-¦-mgbl-¦-px.pie-¦-4.0.0.T hfr-¦-mpls-¦-px.pie-¦-4.0.0.T hfr-¦-
k9sec-¦-px.pie-¦-4.0.0.T hfr-¦- diags-¦-px.pie-¦-4.0.0.T sync
router(admin)# install activate disk0:hfr-¦-mcast-¦-4.0.0.T disk0:hfr-¦-mgbl-¦-
4.0.0.T disk0:hfr-¦-k9sec-¦-4.0.0.T disk0:hfr-¦-mpls-¦-4.0.0.T disk0:hfr-¦-
diags-¦-4.0.0.T sync
8 minutes to tftp hfr-¦-mini-¦-px.vm-¦-4.0.0.T and CRC check etc.
30 minutes for Turboboot to complete
12 minutes for the system to reload and boot up to standby ready state and all line cards in IOS XR
RUN
35 minutes to add and activate the optional PIEs
Appendix A Turbo Boot Procedure
OL-13669-03