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-19
Backing Up a Processor Dump to Tape
Troubleshooting and Recovery Operations for Disk Dumps
If a message indicates that the dump was not successful, repeat Dumping a Processor
to Disk on page 9-13 using the other ServerNet fabric.
If a halt code for the selected processor appears in the Processor Status dialog box of
the OSM Low-Level Link, look it up in the Processor Halt Codes Manual for further
information about the cause of failure and the appropriate recovery procedure.
Backing Up a Processor Dump to Tape
Back up a processor dump to tape from the compressed disk file generated by the
TACL RECEIVEDUMP command (or the RCVDUMP utility):
1. Follow the instructions in Dumping a Processor to Disk on page 9-15.
2. Use the BACKUP utility to copy the processor dump to tape, as described in
Section 10, Disk Drives: Monitoring and Recovery.
3. See Submitting Information to Your Service Provider on page 9-19.
Replacing Processor Memory
Processor memory is field-replaceable for all Integrity NonStop systems. Call your
service provider. If memory units cannot be replaced, the memory board must be
replaced.
If the Service State attribute of a Slice object is not OK (see Monitoring Processor
Performance Using ViewSys on page 9-7), the memory board might need to be
replaced. Contact your service provider. For information, refer to the CSSI Web.
Replacing the Processor Board and Processor Entity
Processor boards and entities are field-replaceable for all Integrity NonStop systems.
Call your service provider.
Submitting Information to Your Service Provider
To help with the analysis of a processor dump, submit a backup tape of other system
configuration and operations files and some additional information.
•
Submitting Tapes of Processor Dumps on page 9-20
•
Submitting Tapes of Configuration and Operations Files on page 9-20
•
Additional Information Required by Your Service Provider on page 9-21