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-15
Enabling/Disabling Processor and System Freeze
Enabling/Disabling Processor and System Freeze
The system and processors are freeze-disabled by default. You can check the current
state through the following attributes:
•
System Freeze—In the OSM Low-Level Link, under the System object, the System
Freeze attribute indicates whether System Freeze is currently Enabled or Disabled.
•
Processor Freeze—Check either:
°
In the OSM Low-Level Link, under each Processor object, the Processor
Freeze attribute indicates whether Processor Freeze is currently Enabled or
Disabled for that processor.
°
In the OSM Service Connection, under each Logical Processor object, the
Processor Freeze State attribute indicates whether Processor Freeze is
currently Enabled or Disabled for that processor.
To enable or disable System Freeze, use Enable System Freeze action, located under
the System object in the OSM Low-Level Link. After a System Freeze action is
performed, the System Freeze attribute is automatically set back to Disabled.
To enable or disable Processor Freeze, you can use either the OSM Low-Level Link or
the OSM Service Connection:
•
In the OSM Low-Level Link, use the Enable Freeze or Disable Freeze actions,
located under the Processor object.
•
In the OSM Service Connection, use the Enable Processor Freeze or Disable
Processor Freeze actions, located under the Logical Processor object.
Freezing the System and Freeze-Enabled Processors
In the OSM Low-Level Link, under the System object, perform the System Freeze
action. This action halts all freeze-enabled processors in the system.
Confirm that the action success Processor Freeze State for each processor is now
Enabled. In addition to the attribute values described earlier, in the LLL Processor
Status dialog box, each processor should now display an “F” appears next to its name
Dumping a Processor to Disk
Dump options for NonStop NS-series servers are different than for S-series servers.
While dumping to tape is not option for NS-series, there are many new options for
dumping an entire processor or just the processor element (PE) needed.
Caution. Enabling Processor Freeze and System Freeze should only be done by, or under the
direction of, your service provider. When System Freeze is enabled and one freeze-enabled
processor halts, all other freeze-enabled processors in the system also halt. When enabled,
ServerNet disruptions such as cable replacement or CRU/FRU insertion can generate a
system freeze. If System Freeze is enabled, disable it before performing a service operation.










