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

Disk Drives: Monitoring and Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
10-8
Monitoring Disk Drives With SCF
To display the detailed status of the disk $DATA01:
-> STATUS $DATA01, DETAIL
To display status of all paths for $DATA00:
-> STATUS DISK $DATA00-*
The output from this example indicates that $DATA00:
•
Is a mirrored volume (primary and mirror paths)
•
Has a mirror disk that is being revived (SubState REVIVE)
STORAGE - Detailed Status DISK \SHARK.$DATA01
Disk Path Information:
LDev Path PathStatus State SubState Primary Backup
PID PID
63 PRIMARY ACTIVE STARTED 0,267 1,266
63 BACKUP INACTIVE STARTED 0,267 1,266
63 MIRROR ACTIVE STARTED 0,267 1,266
63 MIRROR-BACKUP INACTIVE STARTED 0,267 1,266
General Disk Information:
Device Type........... 3 Device Subtype........... 53
Primary Drive Type.... BF0365 Mirror Drive Type........ BF0365
Physical Record Size.. 4096 Priority................. 220
Library File..........
Program File.......... \SHARK.$SYSTEM.SYS00.TSYSDP2
Protection............ MIRRORED
Usage Information:
Capacity (MB)....... 36419.03 Free Space (MB)........33671.23 (92.45%
Free Extents........ 14 Largest Free Extent (MB). 33516.31
Hardware Information:
Path Location Power Physical Status
(group,module,slot)
PRIMARY EXTERNAL DUAL PRESENT
MIRROR EXTERNAL DUAL PRESENT
STORAGE - Status DISK \ALM171.$DATA00-*
LDev Path PathStatus State SubState Primary Backup
PID PID
6 PRIMARY ACTIVE STARTED 0,10 1,10
6 BACKUP INACTIVE STARTED 0,10 1,10
6 MIRROR ACTIVE STARTING REVIVE 0,10 1,10
6 MIRROR-BACKUP INACTIVE STARTING REVIVE 0,10 1,10
LDev Logical device number
Path Disk path assignment
PathStatus Status of the disk path; whether that path is the current path
(ACTIVE) or not (INACTIVE)
State Current SCF state of the disk path
SubState Current SCF substate of the disk path
Primary PID Primary processor number and process identification number (PIN)
of the specified device
Backup PID Backup processor number and PIN of the specified device










