Availability Guide for Problem Management

Preventing Unplanned Outages
Availability Guide for Problem Management–125509
2-8
System Configuration Documentation
System Configuration Documentation
Maintain documentation that describes your system in its “normal” state. Include
descriptions of all major system components, their configurations, and how they deliver
services. Be able to identify what is, and what should be, running on your system.
•
Maintain charts, diagrams, and lists that describe the physical and logical
configuration or your system. See the forms included in the S-series server
Installation Documentation Packet, described in the Himalaya S-Series Installation
Guide and the Himalaya S-Series Planning and Configuration Guide. See also the
configuration worksheets in the TSM Configuration and Management Guide.
•
Use the SCF INFO command to display system configuration information for a
specified device object (for example, DISK, TAPE, or ADAPTER), including the
current attribute values for that object. Refer to the SCF Reference Manual for the
Storage Subsystem for a detailed description of the SCF INFO command.
•
Use the SCF STATUS command to display the current status of a specified object.
To display the status of all disks, use the SCF DISK $* command. To display the
status of all tape devices, use the SCF TAPE * command. Refer to the SCF
Reference Manual for the Storage Subsystem for a detailed description of the SCF
STATUS command.
•
Generate a process pair directory (PPD) listing just after system and application
startup to provide a quick reference of process names and their primary and backup
processors.
•
Keep listings from SCF INFO, LISTDEV, and STATUS commands to capture the
status of terminals, printers, and communications lines. Refer to the SCF Reference
Manual for Himalaya S-Series Servers and the ServerNet Communications
Configuration and Management Manual for detailed information about these
commands for device types other than disk or tape.
•
Generate a listing of the spooler configuration file to show the normal spooler
configuration and the names of the spooler components. The spooler interface
(SPOOLCOM) commands allow you to print the current configuration and the
spooler routing structure.
•
Keep the CONFLIST and CONFTEXT listings and other configuration reports
generated by DSM/SCM. (DSM/SCM is used to generate a new system image and
to install new software releases.)
•
Keep application configuration listings to help the staff monitor applications and
ensure that all required processes are running.
•
Keep database configuration listings that show the major databases and the
applications that access them. You can use these listings to monitor disk I/O load
balancing and identify the applications that might be affected by a disk failure.
•
Keep NonStop SQL/MP catalog listings, which show where the NonStop SQL/MP
catalogs are located on the network.