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
Tape Drives: Monitoring and Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
11-7
Monitoring the Status of Labeled-Tape Operations
Monitoring the Status of Labeled-Tape Operations
Use the MEDIACOM STATUS TAPEDRIVE and STATUS TAPEMOUNT commands to
determine the current status of labeled-tape operations on your system.
For additional information about MEDIACOM, the listings it generates, and the tasks it
enables you to perform:
•
DSM/Tape Catalog Operator Interface (MEDIACOM) Manual
•
DSM/Tape Catalog User’s Guide
•
Guardian User’s Guide
Identifying Tape Drive Problems
Table 11-1 lists some of the most common tape drive problems and their possible
causes. Additionally, OSM alarm repair actions, degraded attribute values, and EMS
event details can help you determine the appropriate cause of action
Table 11-1. Common Tape Drive Problems
Symptom Problem Possible Causes
File-system error
48
A security violation has
occurred.
An attempted operation was not
allowed.
File-system error
49
Various An unexpired labeled tape was used.
File-system error
51
A runaway tape has been
detected.
The system has tried to read a blank
tape.
File-system error
66
Various A hardware failure has occurred, or
the tape drive has been purposely
brought down.
File-system error
100
A device is not ready. A tape drive has been brought down,
or the drive is not online.
File-system error
195
An operation requires use of
$ZSVR, but it is not running.
Tape operation is not allowed.
$ZSVR has been purposely stopped.
File-system error
218
An interrupt timeout occurs. An
I/O process cannot
communicate with a tape drive.
A ServerNet addressable controller
(SAC) has failed.
No error A tape label record is missing
or incorrect.
An attempt was made to access a
tape with a missing or incorrect label.
No error A tape fails to respond to a
BACKUP command.
A tape with an inappropriate label
type was mounted in error.
No error A tape continues to spin
beyond the load point.
The load point has fallen off.
No error Every time a tape is mounted, it
is unloaded.
A labeled tape is being mounted in a
drive that is open for unlabeled use.