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
Determining Your System Configuration
HP Integrity NonStop NS-Series Operations Guide—529869-001
2-10
Displaying SCF Configuration Information for
Subsystems
Kernel Subsystem
Before using commands listed in Table 2-3, type this command to make the Kernel
subsystem the default object:
> SCF ASSUME PROCESS $ZZKRN
Generic processes are part of the SCF Kernel subsystem. Generic processes can be
created by the operating system or by a user. Examples of generic processes created
by the operating system are the Kernel, SLSA, the storage subsystem, and WAN
subsystem manager processes. Examples of generic processes created by a user are
a Pathway program, a third-party program, or a user-written program that you
configure to be controlled by the operating system. The $ZPM persistence manager
starts and monitors all generic processes.
Storage Subsystem
The storage subsystem manages disk and tape drives as well as SCSI and HP
NonStop Storage Management Foundation (SMF) devices. Use the commands listed
in Table 2-4 to display desired information.
Table 2-3. Displaying Information for the Kernel Subsystem ($ZZKRN)
To Display Information About These
Configured Objects Enter This Command
The Kernel subsystem manager and
ServerNet process names
LISTDEV KERNEL
All Kernel subsystem object and process
names
NAMES $ZZKRN
All generic processes INFO *
Detailed information about a generic
process
INFO #generic-process, DETAIL
Table 2-4. Displaying Information for the Storage Subsystem ($ZZST0)
To Display Information About These
Configured Objects Enter This Command
All disk and tape drives (list) LISTDEV STORAGE
All storage subsystem objects and
processes (by name)
NAMES $ZZSTO
All disk drives (list) LISTDEV TYPE 3
All disk drives (summary information) INFO DISK $*
A specific disk drive (detailed information) INFO DISK $name, DETAIL
All tape drives (list) LISTDEV TYPE 4
All tape drives (summary information) INFO TAPE $*
A specific tape drive (detailed information) INFO TAPE $name, DETAIL