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

Processors and Components: Monitoring and
Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
9-9
Recovery Operations for Processors
Recovery Operations for Processors
The architecture of Integrity NonStop NS-series servers offers recovery options not
available in NonStop S-series. Because a logical processor has a physical processor
element (PE) in each of up to three NonStop Blade Elements (slices), in some cases,
you no longer have to choose between taking the time to dump entire processors and
skipping the dump to reload the system as quickly as possible. In those cases, you can
reload a halted processor immediately, while excluding the PE for one slice, then dump
that excluded PE before reintegrating the slice into the running processor.
Processor recovery operations for your NS-series system might include:
•
Recovery Operations for a Processor Halt on page 9-9
•
Halting One or More Processors on page 9-10
•
Reloading a Single Processor on a Running Server on page 9-10
•
Recovery Operations for a System Hang on page 9-14
•
Enabling/Disabling Processor and System Freeze on page 9-15
•
Freezing the System and Freeze-Enabled Processors on page 9-15
•
Dumping a Processor to Disk on page 9-15
•
Backing Up a Processor Dump to Tape on page 9-19
•
Replacing Processor Memory on page 9-19
•
Replacing the Processor Board and Processor Entity on page 9-19
•
Submitting Information to Your Service Provider on page 9-19
Recovery Operations for a Processor Halt
HP Tandem Failure Data System (TFDS) should be used to proactively monitor
processors and manage processor halts. Configured and running before a halt occurs,
TFDS can help determine and perform the type of recovery operation needed (see
Monitoring Processors Automatically Using TFDS
on page 9-4). For information on
configuring and using TFDS, see the Tandem Failure Data System (TFDS) Manual.
If all processors have halted (the system is down), TFDS cannot perform an automatic
dump or reload. You must load the system, as described in Performing a System Load
From a Specific Processor on page 15-11. You can omit one slice from the load
operation, to dump after the system is running. You can also dump the remaining
processors as needed—dump the entire processor before reloading, or reload and
omit slice to dump later. For more information, see Dumping a Processor to Disk on
page 9-15.
The best manual recovery operation for your processor halt scenario depends on the
type of halt. You should record the halt information (as described in Identifying










