
System image handling task list
60
IPLink Software Configuration Guide
6 • System image handling
Note
When returning to the factory-config by using the
copy factory-config star-
tup-config
command, all user-specific configurations saved in nvram:
remain even after reload.
Figure 9. IPLink memory regions logically defined in IPLink software
System image handling task list
To load and maintain system images, perform the tasks described in the following sections:
•
Displaying system image information
•
Copying system images from a network server to the Flash memory (see
page 61
)
•
Copying the driver software from a network server to the Flash memory (see
page 62
)
Displaying system image information
This procedure displays information about system images and driver software
Volatile
Persistent
nvram :
• Factory
Configuration
“factory-config”
(read-only)
• Startup
Configuration
“startup-config”
• User specific
Configuration
“user-config”
system:
• current Running
Configuration
“running-config”
tftp:
• Configuration
Files
• Batchfiles for
System Image
download
flash:
• Application Image
• Bootloader Image
• Microcode Image
Memory Regions in
Embedded Software
Storing the current Configuration locally
Configuration File Upload
Storing the current Running Configuration remotely
Remote
(TFTP Server)
Local
(Intelligent Acess Device)
Image / Microcode Download
Configuration File Download
Only on Startup to execute the
Startup or Factory Configuration