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
Overview of Monitoring and Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
3-7
Monitoring and Resolving Problems—An Approach
Monitoring and Resolving Problems—An
Approach
A useful approach to identifying and resolving problems in your system is to first use
OSM to locate the focal point of a hardware problem and then use SCF to gather all
the related data from the subsystems that control or act on the hardware. In this way,
you can develop a larger picture that encompasses the whole environment, including
communications links and other objects and services that might be contributing to the
problem or affected by it.
To get comprehensive online descriptions of all the available SCF commands, use the
SCF HELP command.
The following subsections give instructions for using OSM and SCF to monitor and
resolve problems.
Using OSM to Monitor the System
This section deals mostly with the OSM Service Connection, the primary OSM
interface for system monitoring and serviceability.
See Overview of OSM Applications on page 1-12 for examples of how the other OSM
applications are used for monitoring-related functions.
Using the OSM Service Connection
The OSM Service Connection can be used in a variety of ways to monitor your system,
including:
•
Use of colors and symbols to direct you to the source of any problems
•
Attribute values for system resources, displayed in the Attributes tab and in many
dialog boxes.
•
Alarms, displayed in the Alarms tab and Alarm Summary dialog box.
The following section presents one model for using the OSM Service Connection to
monitor your system, along with a few other options.
A Top-Down Approach
The Management (or main) window of the OSM Service Connection uses a series of
colors and symbols to notify you that problems exist within the system. You can tell at a
high-level glance when problem conditions exist, then drill-down, or expand the tree
pane to find the component reporting the problem. Figure 3-1 illustrates how both the
the rectangular system icon (located at the top of the view pane) and the system object
in the tree pane indicate problems within the system. The system icon, which is green
when OSM is reporting no problems on the system, has turned yellow. The system
icon in the tree pane is displaying a yellow arrow to indicate a problem within.