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-10
Halting One or More Processors
Processor Problems on page 9-7), and contact your service provider to help you
determine the appropriate course of action.
This section describes the various options for Dumping a Processor to Disk and
Reloading a Single Processor on a Running Server that you might be directed to use.
Halting One or More Processors
To place a selected processor or processors in a halt state and set the status and
registers of the processor or processors to an initial state:
1. Log on to the OSM Low-Level Link.
2. On the toolbar, click Processor Status button.
3. In the Processor Status dialog box, select the processor to be halted or select all
the processors to halt all of them.
4. Select Processor Actions>Halt.
5. Click Perform action.
6. A message box appears and asks whether you are sure you want to perform a halt
on the selected processor or processors. Click OK.
Reloading a Single Processor on a Running Server
Sometimes one or more processors in a running server are not operating. For
information on how to determine whether a processor is operating, see Monitoring
Processor Performance Using ViewSys on page 9-7.
Unlike NonStop S-series, you don’t always have to wait until you dump the processor
before reloading it. This section describes how, when appropriate, to exclude the
processor element (PE) from one slice (or NonStop Blade Element) during the reload
operation, so you can get the rest of the processor running, take the dump, then
reintegrate the PE back into the running processor.
After you have determined that a processor is not operating, check that the processor
is halted. If it needs to be halted, see Halting One or More Processors on page 9-10).
Collect information about the reason for the halt (as described in Identifying Processor
Problems on page 9-7) to send to your service provider along with the dump file. In the
Low-Level Link Processor Status dialog box, write down the halt code and status
message for the processor.
Your options for reloading a processor on a running server are:
•
Using TACL RELOAD to Perform Reload on page 9-11
•
Using the OSM Service Connection to Perform Reload on page 9-13
Following the reload, if TFDS is not configured to take the dump automatically, you can
perform a dump of the omitted PE while normal operations resume on the reloaded
PEs within that logical processor. See the Dumping a Processor to Disk on page 9-15.










