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-8
Processor Halts
Processor Halts
When certain errors occur (such as when data integrity is at risk), the operating system
cannot correct the problem and must halt all application and system processes running
in the associated processor. The remaining running processors in the system each
send a message, reporting the halted processor as down. The other processors in the
system, including the backup to the halted processor, are not affected by the errors
that caused the processor to halt unless they are freeze-enabled. Two types of
processor halts display a processor halt code in the Processor Status dialog box:
•
A halt instruction results in a processor halt.
When the operating system detects a millicode or software error that it cannot
correct, it can execute a halt instruction to suspend all application and system
processes running in the associated processor. The status of the halted processor
becomes:
Halt code = %nnnnnn
Unlike a freeze instruction, a halt instruction affects only one processor.
•
A processor can be halted by a freeze instruction.
A freeze-enabled processor can be frozen by another frozen processor. When a
freeze instruction is executed, any processors that are freeze-enabled also freeze
immediately. When the operating system detects a software error that it cannot
correct, it can execute a freeze instruction to suspend all application and system
processes running in the associated processor. The status of the frozen processor
becomes:
Freeze code = %nnnnnn
If system freeze is enabled, the status for all other freeze-enabled processors
becomes:
Frozen by other processor
The Processor Halt Codes Manual documents processor halt codes.
OSM Alarms and Attribute Values
When the OSM Service Connection displays processor-related alarms or problem
attributes, the alarm and attribute details often indicate the appropriate recovery action.
Recovery actions might call for:
•
Trying the Recovery Operations for Processors on page 9-9.
•
Trying the Slice (NonStop Blade Element) and LSU troubleshooting tips,
documented on the CSSI web site.
•
Contacting your service provider.
Note. Do not freeze-enable a processor unless instructed to do so by your service provider.










