IBM Nways 2216, Руководство по обслуживанию и ремонту

Страница: 121 / 168

Example of Sending a File from the Configuration Program
For example, suppose that this is the view of the software that is displayed by the
list command:
Boot Config
>
list
BANK A BANK B
IMAGE - ACTIVE IMAGE - AVAIL
CONFIG 1 - ACTIVE CONFIG 1 - AVAIL
CONFIG 2 - AVAIL CONFIG 2 - AVAIL
CONFIG 3 - NONE CONFIG 3 - AVAIL
CONFIG 4 - NONE CONFIG 4 - NONE
The Configuration Program sends a config file to BANK A, CONFIG 2. If the
configuration is marked in the Configuration Program to be loaded immediately, the
IBM 2216 performs a reset immediately after it received the new configuration. The
Send command of the Configuration Program in this situation is composed of these
two actions:
1. Send Config to CONFIG 2 as PENDING
2. Reset
After these two actions, the IBM 2216 configuration looks like this:
BANK A BANK B
IMAGE - ACTIVE IMAGE - AVAIL
CONFIG 1 - AVAIL CONFIG 1 - AVAIL
CONFIG 2 - ACTIVE CONFIG 2 - AVAIL
CONFIG 3 - NONE CONFIG 3 - AVAIL
CONFIG 4 - NONE CONFIG 4 - NONE
CONFIG 1 has become AVAIL and CONFIG 2 has become ACTIVE.
If the Configuration Program were now used to send down a new configuration to
the IBM 2216 and the file were not marked to be loaded at any specified time, the
view of the software in the IBM 2216 would look like this:
BANK A BANK B
IMAGE - ACTIVE IMAGE - AVAIL
CONFIG 1 - AVAIL CONFIG 1 - AVAIL
CONFIG 2 - ACTIVE CONFIG 2 - AVAIL
CONFIG 3 - AVAIL CONFIG 3 - AVAIL
CONFIG 4 - NONE CONFIG 4 - NONE
After this action, CONFIG 3 is AVAIL. The new configuration file has been loaded
in this location.
Note: You should exercise caution here because any on-board configuration
changes could result in overwriting the CONFIG 3 file. Because the configuration
file in CONFIG 3 was sent down without any time specified for resetting the server,
it is currently not in use. It can be overwritten either when another file is sent from
the Configuration Program or when a file is saved using the write command from
the command line interface. You can use the Copy command to move it to another
location to protect it (see “Using the Copy Command” on page D-9).
Appendix D. Managing Operational Code and Configuration Files
D-7