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

HP Integrity NonStop NS-Series Operations Guide—529869-001
A-1
A
Operational Differences Between
Systems Running G-Series and
H-Series RVUs
Users familiar with systems running G-series RVUs will find several major differences
in the operational environment of systems running H-series RVUs. Although many of
the operations to be performed remain the same, the tools you use to execute these
operations might differ significantly. For H-series RVUs, these changes have been
made:
•
TSM is not supported in H-series. You must use OSM. Also, OSM’s graphical
representation of modular systems has a different look in H-series.
•
In power failures, there is no memory hold-up for H-series. Ride-through is
available only if the customer has a site uninterruptible power supply (UPS) or an
in-cabinet UPS for all the affected cabinets.
•
TAPEBOOT is not supported in H-series.
•
In H-series, native compilers and linkers have new names. Therefore, automated
scripts might require changing.
•
Subvol for public libraries is SYSnn in G-series. In H-series, it is ZDLLnnn and
requires changing scripts.
•
REPLACEBOOT only applies to TNS and TNS/R. It does not apply to TNS/E.
•
On G-series servers, the OSS shell command ls displays the contents of
directories without visually distinguishing between subdirectories and files. On H-
series servers, ls displays the contents of directories with a visual distinction
between subdirectories and files -- subdirectory names are suffixed with a slash (/).
This difference affects any OSS shell script that relied upon processing the output
of the ls command.
•
For H-series, DSM/SCM installation default is Manage OSS Files. For G-series,
the default is not to manage OSS files.
•
KMSF swap files have a larger memory size. It is now four times memory size per
processor.
•
Changes to automated debugging and dump mechanisms are required in H-series
because of the new debuggers and debugger commands.
•
The H-series OSS environment does not support TNS execution. OSS programs
must be migrated to TNS/E native mode to run on an H-series system.










