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
Processes: Monitoring and Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
5-6
Recovery Operations for Processes
In nearly all circumstances, items that are essential to system operations that must be
running at all times restart automatically if they are stopped for any reason while the
NonStop Kernel operating system is running.
Some OSM processes stop after executing a macro that runs during system load or
during the reload of processor 0 or 1. Those processes include $ZOLHI.
Optionally, you can also configure other processes such as the Expand subsystem
manager process, $ZEXP, and the Safeguard monitor process, $ZSMP, as generic
processes.
Recovery Operations for Processes
For recovery operations on generic processes, use the SCF interface to the Kernel
subsystem and specify the PROCESS object. These SCF commands are available for
controlling generic processes:
Generic processes that are configured to be persistent usually do not require operator
intervention for recovery. In most circumstances, persistent generic processes restart
automatically.
For recovery operations on IOPs, refer to the WAN Subsystem Configuration and
Management Manual, the SWAN Concentrator and WAN Subsystem Troubleshooting
Guide, and the Expand Configuration and Management Manual.
For recovery operations on system processes, refer to the Guardian User’s Guide.
TFDSHLP $ZTH13 STOPPED None None
TFDSHLP $ZTH14 STOPPED None None
TFDSHLP $ZTH15 STOPPED None None
ZEXP $ZEXP STARTED 0 ,13 1 ,15 255,255
ZHOME $ZHOME STARTED 0 ,289 1 ,295 255,255
ZLOG $ZLOG STARTED 0 ,308 1 ,329 255,255
ZZKRN $ZZKRN STARTED 0 ,293 1 ,319 255,255
ZZLAN $ZZLAN STARTED 0 ,292 1 ,297 255,255
ZZSCL $ZZSCL STARTED 1 ,290 2 ,279 255,255
ZZSMN $ZZSMN STARTED 1 ,289 2 ,282 255,255
ZZSTO $ZZSTO STARTED 0 ,291 1 ,320 255,255
ZZWAN $ZZWAN STARTED 2 ,296 3 ,289 255,255
ABORT Terminates operation of a generic process. This command is not
supported for the subsystem manager processes.
START Initiates the operation of a generic process.