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

Starting and Stopping the System
HP Integrity NonStop NS-Series Operations Guide—529869-001
15-8
Starting Other System Components
Configuration File
Normally, you select Current (CONFIG), the default system configuration file. For the
system disk volume you select to load the system, CONFIG represents the system
configuration database that is currently running or was last running.
If you cannot load the system using Current (CONFIG), you might need to use these
files to recover:
•
Saved Version (CONFxxyy) is a saved system configuration file. Use this file to
recover from a configuration change that causes a problem. If you cannot load the
system using the CONFIG file, you can use a saved version in the form xx.yy, if
one is available. For example, the CONF0205 file would be specified as 02.05.
Use this method to recover from a configuration change that caused a problem
(such as a system freeze). When the system starts and displays a TACL prompt,
you can log on and start the rest of the system applications.
•
Base (CONFBASE) is the most basic configuration required for system startup.
Although you will probably never need to load the system from the CONFBASE
file, you might need to use this file if you cannot load the system using any other
method.
For more information about when to use CONFSAVE or CONFBASE, see Recovering
From a System Load Failure on page 15-20
Starting Other System Components
HP recommends that you bring your system up in stages, verifying each stage, to
facilitate recovery if any step fails. When the system starts, many individual devices,
processes, applications, and communications lines start automatically, but others might
need to be started using start up files. Follow your site’s procedures for starting your
applications.
•
Many processes are configured by default to be started automatically by the $ZPM
persistence monitor. These processes include the Kernel subsystem, SLSA
subsystem, storage subsystem, and WAN subsystem. The manager processes for
these subsystem start disks, SWAN concentrators, some LAN devices, and many
processes.
•
You can use SCF to configure other processes, typically monitor or manager
processes, to start automatically as generic processes when the system starts.
14 Mirror $SYSTEM-M 1 Y
15 Mirror backup $SYSTEM-M 1 X
16 Mirror backup $SYSTEM-M 1 Y
Table 15-1. System Load Paths in Order of Use
Data Travels










