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-20
Recovering From a System Load Failure
Recovering From a System Load Failure
If a system load is not successful or if the system halts:
1. Check for messages in the System Load dialog box of the OSM Low-Level Link.
2. Check the Processor Status dialog box of the OSM Low-Level Link for halt codes.
Look up the halt codes in the Processor Halt Codes Manual for further information
about the cause of failure and the appropriate recovery procedure.
3. Check the startup event message window for any event messages. Record the
event messages, and refer to the appropriate documentation for recovery
information. Refer to the Operator Messages Manual for further information about
the cause, effect, and recovery procedure for an event.
4. Check that the disk you selected to load from is in the specified location.
5. Check that the disk is properly configured as a system disk.
6. Correct the problems, and try loading the system again. If you cannot correct the
problem, contact your service provider.
7. If you continue to have problems, load the system from each disk path for both the
primary and mirror $SYSTEM drives.
8. If you cannot load the system using the current configuration file, load the system
using a saved version of the system configuration file. See Configuration File on
page 15-8.
9. If you still cannot load the system or if a CONFxxyy is not available, load the
system from an alternate system disk if one is available.
10. If you cannot load the system from an alternate system disk, contact your service
provider. You might be able to load the system from the CONFBASE configuration
file and restore a previously backed-up configuration file. If you use this option,
many additional steps are required to restore your system to normal working order.
a. Load the system as described in Starting a System
on page 15-5. In the
Configuration File box, select Base (CONBASE) as the configuration file.
b. Reload the remaining processors. See Reloading Processors
on page 15-12.
c. From the Startup TACL window, configure a tape drive.
d. Restore a previously backed-up configuration file.
e. Load the system as described in Starting a System on page 15-5 from the
current configuration file (CONFIG). Check that the CIIN file is enabled.
11. After you load a system from a saved version (CONFxxyy) of the system
configuration database file or the CONFBASE, verify that no pending changes to
system attributes appear. From a TACL prompt:
INFO SUBSYS $ZZKRN










