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-4
Monitoring IOPs
Monitoring IOPs
For a list of manuals that provide more information about monitoring I/O processes
(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.
Monitoring Generic Processes
Because generic processes are configured using the SCF interface to the Kernel
subsystem, you specify the $ZZKRN Kernel subsystem manager process when
monitoring a generic process. These SCF commands are available for monitoring
$ZZKRN and other generic processes:
Monitoring the Status of $ZZKRN
To monitor the status of the $ZZKRN Kernel subsystem manager process, at a TACL
prompt:
> SCF STATUS SUBSYS $ZZKRN
This example shows the output produced by this command:
Monitoring the Status of All Generic Processes
To monitor the status of all generic processes controlled by $ZZKRN, at a TACL
prompt:
> SCF STATUS PROCESS $ZZKRN.#*
$ZLM01 1,342 200 P 015 255,255 $SYSTEM.SYS14.LANMON $ZHOME
$ZTC0 B 1,352 200 P 011 255,255 $SYSTEM.SYS14.TCPIP $ZHOME
$ZTNT B 1,355 149 001 255,255 $SYSTEM.SYS14.TELSERV $ZHOME
$ZPORT B 1,357 149 001 255,255 $SYSTEM.SYS14.LISTNER $ZHOME
$KLA9E 1,424 147 001 255,255 $DATA2.KMZTT.LOGGER $ZTNT.#PTBY5D
$ZTM02 2,5 200 P 017 255,255 $SYSTEM.SYS14.TMFMON2 $YMIOP.#CLCI
$GRD2 2,243 147 P 001 255,255 $DATA2.QA9050.RUNNER $ZTNT.#PTBY5CV
$ZP02A B 2,300 195 001 255,255 $SYSTEM.ZRPC.PORTMAP $ZHOME
$ZCMOM B 2,303 150 001 255,255 $SYSTEM.SYS14.CIMOM $ZHOME
INFO Displays configuration information for the specified objects
NAMES Displays a list of subordinate object types and names for the
specified objects
STATUS Displays current status information about the specified objects
1 -> STATUS SUBSYS $ZZKRN
NONSTOP KERNEL - Status SUBSYS \COMM.$ZZKRN
Name State Processes
(conf/strd)
\COMM.$ZZKRN STARTED ( 25/22 )