Introduction
58
IPLink Software Configuration Guide
6 • System image handling
Introduction
This chapter describes how to load, maintain, and update the various software images in the IPLink. The
IPLink software system software consists of the application image and the driver images. The images are stored
in persistent (non-volatile) memory. The application image is the software which actually operates the IPLink.
Driver images are used to operate the various optional PMC interface cards.
This chapter includes the following sections:
•
Memory regions in IPLink software
•
System image handling task list (see
page 60
)
•
Boot procedure and bootloader (see
page 65
)
Note
Section
“System image handling task list”
on page 60 describes the standard
way to upgrade the IPLink software. If you encounter problems that won’t
let you upgrade using the standard method, refer to section
“Bootloader”
on
page 67 as appropriate.
•
Factory configuration (see
page 70
)
Patton IPLink devices are shipped with default system software which is stored in persistent memory. Along
with the default system software (application image and driver images), a factory configuration, factory-config,
has been loaded into the IPLink at the factory. This configuration file sets the initial basic operating parameters
of the IPLink, such as enabling the Ethernet ports, setting the default IP addresses and the DHCP server.
Other configuration files may be stored in the IPLink persistent memory. A configuration file is an ordered list
of commands. Some of the various configuration files are
•
factory-config (read-only)
•
startup-config
•
running-config
•
user-config1, user-config2, etc. (these are specific application configurations created by the user)
Backups of the configuration files can be stored on a remote trivial file transfer protocol (TFTP) server. The
remote tftp server must be accessible via one of the IPLink IP interfaces. Tftp cannot be used from the console
interface.
The following sections focus on IPLink software memory regions, as well as the software components you can
copy into the memory or move between a TFTP server and the memory of the IPLink. As IPLink software uses
a specific vocabulary in naming those software components, refer to appendix A,
“Terms and definitions”
on
304 to ensure that you understand the concepts.
Memory regions in IPLink software
The IPLink’s memory contains several logical regions and several physical regions as shown in
figure 9
on
page 60, each separate from the other.
Note
You will use a remote TFTP server for uploading and downloading the
application image, the driver images, and the various configuration files to