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 2212 and the
file were not marked to be loaded at any specified time, the view of the software in the IBM 2212 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 “Copying a File Using the Copy Command” on page E-17) or use the
lock command to keep the configuration file from being overwritten.
Viewing the Files
Question How do I display the state of the operational software image and configuration files stored on
the IBM 2212?
Answer
To use the change management tool in the command line interface to view the operational
software image and the configuration files, follow these steps:
1. From the OPCON prompt (*), type talk 6 and press Enter to reach the
Config
>
prompt. If
the
Config
>
prompt does not appear, press Enter again.
2. Type boot and press Enter. You will see the prompt
Boot config
>
.
3. Type list and press Enter. You will see a list similar to this one:
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 - NONE
CONFIG 4 - NONE
CONFIG 4 - NONE
Each bank represents one image of the operational code. The images stored in BANK A and
BANK B are stored on the hard drive or compact flash. The Configs represent the configuration
files that are stored with each bank.
IMAGE refers to the status of the operational software and
CONFIG refers to the status of the configuration files.
Appendix E. Common Tasks
E-25
Summary of Contents for Cloud Object Storage System Slicestor 2212...
Page 1: ...2212 Access Utility Service and Maintenance Manual GY27 0362 02...
Page 8: ...viii 2212 Service and Maintenance...
Page 28: ...1 20 2212 Service and Maintenance...
Page 86: ...3 8 2212 Service and Maintenance...
Page 98: ...5 4 2212 Service and Maintenance...
Page 110: ...Testing the Adapters 6 12 2212 Service and Maintenance...
Page 112: ...Assembly 1 Final Assembly IBM 2212 Models 10x A 2 2212 Service and Maintenance...
Page 114: ...Assembly 2 Final Assembly IBM 2212 Models 15x A 4 2212 Service and Maintenance...
Page 116: ...Assembly 3 Final Assembly IBM 2212 Models 1xx A 6 2212 Service and Maintenance...
Page 118: ...Assembly 4 Final Assembly IBM 2212 Models 1xx A 8 2212 Service and Maintenance...
Page 120: ...Assembly 5 Final Assembly IBM 2212 Models 40x A 10 2212 Service and Maintenance...
Page 122: ...Assembly 6 Final Assembly IBM 2212 Models 45x A 12 2212 Service and Maintenance...
Page 124: ...Assembly 7 Final Assembly IBM 2212 Models 4xx A 14 2212 Service and Maintenance...
Page 126: ...Assembly 8 Final Assembly IBM 2212 Models 4xx A 16 2212 Service and Maintenance...
Page 130: ...A 20 2212 Service and Maintenance...
Page 138: ...D 2 2212 Service and Maintenance...
Page 166: ...E 28 2212 Service and Maintenance...
Page 195: ......
Page 197: ...Spine information 2212 Access Utility Service and Maintenance Manual...