NonStop NS-Series Operations Guide (H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Guide
- 1 Introduction to Integrity NonStop NSSeries Operations
- When to Use This Section
- Understanding the Operational Environment
- What Are the Operator Tasks?
- Monitoring the System and Performing Recovery Operations
- Preparing for and Recovering from Power Failures
- Stopping and Powering Off theSystem
- Powering On and Starting the System
- Creating Startup and Shutdown Files
- Performing Preventive Maintenance
- Operating Disk Drives and Tape Drives
- Responding to Spooler Problems
- Updating Firmware
- Determining the Cause of a Problem: A Systematic Approach
- Logging On to an Integrity NonStop Server
- Service Procedures
- 2 Determining Your System Configuration
- 3 Overview of Monitoring and Recovery
- 4 Monitoring EMS Event Messages
- 5 Processes: Monitoring and Recovery
- 6 Communications Subsystems: Monitoring and Recovery
- 7 ServerNet Resources: Monitoring and Recovery
- 8 I/O Adapters and Modules: Monitoring and Recovery
- 9 Processors and Components: Monitoring and Recovery
- When to Use This Section
- Overview of the NonStop Blade Complex
- Monitoring and Maintaining Processors
- Identifying Processor Problems
- Recovery Operations for Processors
- Recovery Operations for a Processor Halt
- Halting One or More Processors
- Reloading a Single Processor on a Running Server
- Recovery Operations for a System Hang
- Enabling/Disabling Processor and System Freeze
- Freezing the System and Freeze-Enabled Processors
- Dumping a Processor to Disk
- Backing Up a Processor Dump to Tape
- Replacing Processor Memory
- Replacing the Processor Board and Processor Entity
- Submitting Information to Your Service Provider
- Related Reading
- 10 Disk Drives: Monitoring and Recovery
- 11 Tape Drives: Monitoring and Recovery
- 12 Printers and Terminals: Monitoring and Recovery
- 13 Applications: Monitoring and Recovery
- 14 Power Failures: Preparation and Recovery
- 15 Starting and Stopping the System
- When to Use This Section
- Powering On a System
- Starting a System
- Minimizing the Frequency of Planned Outages
- Stopping Application, Devices, and Processes
- Stopping the System
- Powering Off a System
- Troubleshooting and Recovery Operations
- Fans Are Not Turning
- System Does Not Appear to Be Powered On
- Green LED Is Not Lit After POSTs Finish
- Amber LED on a Component Remains Lit After the POST Finishes
- Components Fail When Testing the Power
- Recovering From a System Load Failure
- Getting a Corrupt System Configuration File Analyzed
- Recovering From a Reload Failure
- Exiting the OSM Low-Level Link
- Opening Startup Event Stream and Startup TACL Windows
- Related Reading
- 16 Creating Startup and Shutdown Files
- Automating System Startup and Shutdown
- Processes That Represent the System Console
- Example Command Files
- CIIN File
- Writing Efficient Startup and Shutdown Command Files
- How Process Persistence Affects Configuration and Startup
- Tips for Startup Files
- Startup File Examples
- Tips for Shutdown Files
- Shutdown File Examples
- 17 Preventive Maintenance
- A Operational Differences Between Systems Running GSeries and HSeries RVUs
- B Tools and Utilities for Operations
- When to Use This Appendix
- BACKCOPY
- BACKUP
- Disk Compression Program (DCOM)
- Disk Space Analysis Program (DSAP)
- EMSDIST
- Event Management Service Analyzer (EMSA)
- File Utility Program (FUP)
- Measure
- MEDIACOM
- NonStop NET/MASTER
- NSKCOM and the Kernel-Managed Swap Facility (KMSF)
- OSM Package
- PATHCOM
- PEEK
- RESTORE
- SPOOLCOM
- Subsystem Control Facility (SCF)
- HP Tandem Advanced Command Language (TACL)
- TMFCOM
- Web ViewPoint
- ViewPoint
- ViewSys
- C Related Reading
- D Converting Numbers
- Safety and Compliance
- Index

Determining Your System Configuration
HP Integrity NonStop NS-Series Operations Guide—529869-001
2-5
SCF Configuration Files
SCF Configuration Files
Your system is delivered with a standard set of configuration files:
•
The $SYSTEM.SYSnn.CONFBASE file contains the minimal configuration
required to load the system.
•
The $SYSTEM.ZSYSCONF.CONFIG file contains a standard system configuration
created by HP. This basic configuration includes such objects as disk drives, tape
drives, ServerNet adapters, the local area network (LAN) and wide area network
(WAN) subsystem manager processes, the OSM server processes, and so on.
You typically use this file to load the system.
•
The $SYSTEM.ZSYSCONF.CONFIG file is also saved on your system as the
ZSYSCONF.CONF0000 file.
All subsequent changes to the system configuration are made using SCF. The system
saves configuration changes on an ongoing basis in the ZSYSCONF.CONFIG file. You
have the option to save a stable copy of your configuration at any time in
ZSYSCONF.CONFxxyy using the SCF SAVE command. For example:
-> SAVE CONFIGURATION 01.02
You can save multiple system configurations by numbering them sequentially based on
a meaningful convention that reflects, for example, different hardware configurations.
Each time you load the system from CONFBASE or CONFxxyy, the system
automatically saves in a file called ZSYSCONF.CONFSAVE a copy of the
configuration file used for the system load.
For guidelines on how to recover if your system configuration files are corrupted, refer
to Troubleshooting and Recovery Operations on page 15-18.
For certain SCF subsystems, configuration changes are persistent. The changes
persist through processor and system loads unless you load the system with a different
configuration file. Examples of these subsystems are the Kernel, ServerNet LAN
Systems Access (SLSA), the storage subsystem, and WAN. For other SCF
subsystems, the changes are not persistent. You must reimplement them after a
system or processor load. Examples of these subsystems are General Device Support
(GDS), Open System Services (OSS), and SQL communication subsystem (SCS).










