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-14
Recovery Operations for a Down Disk or Down Disk
Path
Recovery Operations for a Down Disk or Down Disk Path
To restart a disk or disk path:
1. If a path is down due to a ServerNet fabric failure, determine the affected paths.
From an SCF prompt:
-> STATUS DISK $*-*, SUB MAGNETIC
The output indicates:
•
$DATA06-M and $DATA06-MB are stopped in the DOWN substate.
•
$WD8-M and $WD8-MB are stopped in the HARDOWN substate.
•
$DATA00-P and $DATA00-B are stopped in the HARDDOWN substate.
2. Reset disk drives that are in the HARDDOWN substate. At an SCF prompt:
-> RESET DISK $volume
For example:
-> RESET DISK $WD8
Resetting a disk in the HARDDOWN substate places it in the DOWN substate.
3. Restart the disk. At an SCF prompt:
-> START DISK $volume
If the disk does not start, the disk might need replacement. If neither half of a mirrored
volume starts, the database might need recovery. Contact your service provider.
STORAGE - Status DISK \ALPHA12.$DATA06-*
LDev Path Status State Substate Primary Backup
PID PID
116 PRIMARY ACTIVE STARTED 0,285 1,268
116 BACKUP INACTIVE STARTED 0,285 1,268
116 MIRROR INACTIVE STOPPED DOWN 0,285 1,268
116 MIRROR-BACKUP INACTIVE STOPPED DOWN 0,285 1,268
STORAGE - Status DISK \ALPHA12.$WD8-*
LDev Path Status State Substate Primary Backup
PID PID
96 PRIMARY ACTIVE STARTED 0,23 1,12
96 BACKUP INACTIVE STARTED 0,23 1,12
96 MIRROR INACTIVE STOPPED HARDDOWN 0,23 1,12
96 MIRROR-BACKUP INACTIVE STOPPED HARDDOWN 0,23 1,12
STORAGE - Status DISK \ALPHA12.$DATA00-*
LDev Path Status State Substate Primary Backup
PID PID
121 PRIMARY INACTIVE STOPPED HARDDOWN 0,284 1,267
121 BACKUP INACTIVE STOPPED HARDDOWN 0,284 1,267
121 MIRROR ACTIVE STARTED 0,284 1,267
121 MIRROR-BACKUP INACTIVE STARTED 0,284 1,267
Total Errors = 0 Total Warnings = 9










