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-4
Monitoring and Maintaining Processors
In summary, these terms describe the NSAA processor:
Monitoring and Maintaining Processors
To monitor processors, use OSM, the ViewSys product, and other tools. Monitoring
and maintaining processors includes:
•
Monitoring Processors Automatically Using TFDS on page 9-4
•
Monitoring Processor Status Using the OSM Low-Level Link on page 9-5
•
Monitoring Processor Status Using the OSM Service Connection on page 9-5
•
Monitoring Processor Performance Using ViewSys on page 9-7
•
Monitoring EMS Event Messages on page 4-1
Monitoring Processors Automatically Using TFDS
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 the type of recovery operation needed and:
•
If TFDS determines that the entire processor should be dumped be reloading, it
automatically dumps, then reloads the processor.
•
If TFDS determines that only the processor element (PE) for one slice needs to be
dumped, it reloads the processor, excluding that slice, dumps the slice, then
reintegrates it back into the running processor.
•
Collects the files necessary to analyze the problem.
•
Sends halt information message to the EMS collector. If configured in OSM, a
dial-out message is sent to HP Global Support to notify them of the halt.
For more information on configuring and using TFDS, see the Tandem Failure Data
System (TFDS) Manual.
Term Description
Blade
Complex
Consists of two Blade Elements (in a duplex system) or three Blade
Elements (in a triplex system) and up to four logical processors and their
associated LSUs. An Integrity NonStop system includes up to four Blade
Complexes.
Blade
Element
Consists of a chassis, processor board containing two or four PEs (one
representing each logical processor in the Blade Complex), memory, I/O
interface board, midplane, optics adapters, fans, and power supplies.
Blade Elements are mounted in a 19-inch computer equipment rack.
Processor
element (PE)
A single Itanium microprocessor with its associated memory. A PE is
capable of executing an individual instruction stream and I/O
communication through fiber-optic links.
Logical
processor
One PE from each Blade Element executing a single instruction stream. A
duplex system has two PEs forming a logical processor. A triplex system
has three PEs.










