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-11
Reloading a Single Processor on a Running Server
Using TACL RELOAD to Perform Reload
Run the RELOAD utility to reload the remaining processors after the first processor in a
system has been brought up, or to recover a processor that has failed.
The H-series RELOAD utility allows you to omit (or exclude) a slice from the reload
operation. This allows you get the processor running for the PEs on the other slices,
take a dump of the PE on the omitted slice, and then reintegrate it back into the
running processor. The OMITSLICE parameter allows you to specify the slice (A, B, or
C) to be excluded from the reload or, used without specifying a particular slice,
OMITSLICE selects a slice to be excluded.
1. Select File>Start Terminal Emulator.
2. From the menu, select For Startup TACL. Two OutsideView windows appear.
3. In the Enter Telnet IP Address box, type the IP address that is currently configured
for your primary service connection. If the processor for the primary service
connection IP address is down, type the IP address that is currently configured for
your backup service connection.
4. Click OK. The OutsideView window is active, and the TACL1> prompt appears.
5. Enter the super ID (255,255) and press Enter.
6. Type the password and press Enter.
A $SYSTEM STARTUP 1> prompt appears (the prompt depends on your defaults).
7. Use the RELOAD command as appropriate for your scenario.
run-option
is any of the options described in the RUN[D|V] Command, in the HP NonStop
TACL Reference Manual.
cpu-set
is a set of processors (and options) to be reloaded. Specify cpu-set as:
{ cpu-range } [, option, option, ... ]
{ ( cpu-range, cpu-range, ...) }
{ * }
cpu-range
is one of these:
cpu
cpu-cpu
Note. If you plan to dump the PE for one slice after reloading, use RELOAD with the
OMITSLICE parameter. If you don’t know which slice to specify, use OMITSLICE without
specifying A, B, or C. RELOAD will choose an appropriate slice, and reply with the letter of
the slice that was omitted. Use this to specify the slice in the RCVDUMP command.
RELOAD [ / run-option [ , run-option ] ... / ]
cpu-set [; cpu-set ] ...










