IBM Cloud Object Storage System Slicestor 2212..., Service And Maintenance Manual

Page: 85 / 197

Managing the Operational and Configuration Software
Operational Software
The IBM 2212 comes from the factory with two copies of its operational software
loaded on its hard drive or compact flash and an abbreviated copy (for recovery in
case the software or hard drive/compact flash is bad) on the system card flash.
¹
If the operational software needs an upgrade or replacement, you have to
reload it. See “Updating the Operational Code” on page E-23 for instructions
on updating the operational software.
¹
If the operational code on the hard drive or compact flash fails, the recovery
version on the system card flash is automatically booted.
¹
If the IBM 2212 fails when a new version of the operational software is
activated, the backup versions can be restored. See “Restoring a Backup
Version of Code” on page E-19 for instructions.
¹
If the bootstrap (stored in system card flash) needs updating, use the
procedure in “Updating the Bootstrap Code on System Card Flash” on
page E-23.
Configuration Software
The IBM 2212 is capable of storing on its hard drive or compact flash four copies of
configuration information for each copy of operational software. You can create
binary configuration files using the Configuration Program and upload them to the
IBM 2212. You can also do the configuration by attaching an ASCII terminal to the
IBM 2212’s service port or Telnetting into the IBM 2212 after the initial configuration
is complete, and accessing the command-line interface.
Changes to the configuration are activated immediately, after a user-configured
timed interval, or at the next restart or reload. See the
Access Integration Services
Software User's Guide to determine the configuration parameters that are activated
immediately. See the
Configuration Program User’s Guide for instructions on using
the Configuration Program to activate configuration changes at timed-intervals.
Chapter 3. Accessing the IBM 2212
3-7