Booting over the Network:
ProblemYou want to load an IOS image that is too large to store on your router’s local flash.
You can load an IOS image that is larger than your router’s flash by configuring the router to first use TFTP to download the image and before booting:
booting from remote IOS images presents some unique challenges. Therefore, we decided to dedicate an entire recipe to remote booting.
One of the most important advantages of booting an IOS image over the network is that it allows you to use images that are larger than your router’s flash. Like any other software, each new IOS image tends to be slightly larger than the previous versions. So it is relatively common to discover that you can’t load the latest IOS version because it is too big to fit in an older router’s flash.
Booting over the network also provides a way of loading a backup IOS image if the primary image fails.Even if you have a lot of flash storage, you may find that you can’t store two IOS images at once. So booting over the network is actually a reasonable way of providing a backup image.
Booting over the network also poses an important security problem because,
it is virtually impossible to secure a UDP-based service like TFTP. In addition, it makes the router dependant on the TFTP server for its boot images. Network booting also has performance issues. Loading an IOS over the network can significantly increase the time it takes your router to reload, particularly if it has to traverse slower WAN links. We certainly do not recommend relying solely on remote booting in a production environment.
However, in a lab or testing environment, it can be extremely useful to be able to load an IOS image that is larger than your router’s flash. This lets you work with IOS versions that you could not otherwise load and test. The following show version command output was taken from a router that was booted in this way:
This shows that the router is running the new version of IOS, which it loaded by using TFTP. In this example, we put the TFTP boot first:
If the TFTP file transfer had failed, the router would have loaded its old IOS image from its local flash. If we had reversed the order of these commands, the router would have tried first to boot from flash, and would have resorted to TFTP if the router had trouble with the file on the flash.
For redundancy purposes, you can configure the router to boot from multiple TFTP servers. Simply copy the same IOS image to an alternate set of TFTP servers and include a boot system command per server. This reduces the dependency of the router to a single TFTP server, although the router has to try each successive server and time out before moving on to the next one, which can increase the boot time.