IBM FlashSystem 900, Installation And Maintenance Manual

Page: 279 / 390

Appendix E. Managing Operational Code and Configuration
Files
This chapter explains how to manage the operation code images and configuration
files
Reconfiguring
Configuration errors are difficult to detect.
A configuration error can initially appear to be a hardware problem because the
multiaccess enclosure will not start or data will not flow through a port.
In addition, problems with configuration may not result in an error initially; an error
may occur only when specific conditions are encountered or when heavy network
traffic occurs.
If you cannot resolve a problem after making a few changes to your configuration
or after restoring the active configuration file, it is recommended that you generate
a new configuration. Too many changes to a configuration often compound the
problem, whereas you can usually generate and test a new configuration within a
few hours.
How Software Files Are Managed
To help you manage operational software upgrades and configurations, the
multiaccess enclosure has a software change management feature. This utility
enables you to determine which operational software file and which configuration
file is active while the multiaccess enclosure is running.
How to View the Files
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 command line interface (
*
prompt) (see “Accessing the Operational
Diagnostics from the Service Processor” on page 5-42), type talk 6 and press
Enter. The
Config
>
prompt appears.
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 - NONE
CONFIG 2 - NONE CONFIG 2 - NONE
CONFIG 3 - NONE CONFIG 3 - NONE
CONFIG 4 - NONE CONFIG 4 - NONE

Copyright IBM Corp. 1998, 1999
E-1