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-16
Dumping a Processor to Disk
For automatic dumping and reloading of halted processors, use the HP Tandem
Failure Data System (TFDS). To dump automatically, TFDS must be configured on the
system before the halt occurs. However, you can also bring up TFDS following a halt
and use the TFDSCOM command ANALYZE CPU to obtain information about the
failure.
If you did not have TFDS configured to take the processor dump, you can use the
RCVDUMP utility to take the dump.
•
If your service provider determines that a processor halt is divergence-related, you
might be directed to dump the entire processor before reloading it. In this case, use
the RCVDUMP command, as follows:
°
Use SLICE ALL parameter option.
°
Do not specify ONLINE or PARALLEL parameters.
See Using RCVDUMP to Dump a Processor to Disk on page 9-17.
•
If your service provider determines that a processor halt is not divergence-related,
you might be directed to reload the processor while excluding the PE for one slice,
which is then dumped before being reintegrated. In this case, perform the reload
(see Reloading a Single Processor on a Running Server on page 9-10), then use
the RCVDUMP command as follows:
°
If more than one slice is in the Stopped state, use the SLICE parameter and
specify the sliceId (A, B, or C) of the PE to be dumped. (If only one slice is in
the Stopped state, it is not necessary to use the SLICE parameter.)
°
Specify the PARALLEL parameter.
See Using RCVDUMP to Dump a Processor to Disk on page 9-17.
•
If a dump is to be taken following a system load, as described in Performing a
System Load From a Specific Processor on page 15-11, options for taking dumps
include:
°
After the processor (0 or 1) has been loaded with a slice omitted, use
RCVDUMP with the PARALLEL option.
°
You can dump any of the remaining processors either by dumping the entire
processor before reloading them (use RCVDUMP without specifying the
ONLINE or PARALLEL options), or reload with a slice omitted, then dump that
slice using RCVDUMP with the PARALLEL option.
•
If you are directed to dump a single PE that is running, use the RCVDUMP
command, as follows:
°
Specify the ONLINE parameter.
°
Do not specify the slice ID (RCVDUMP will choose the first running PE).
See Using RCVDUMP to Dump a Processor to Disk on page 9-17.










