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
Introduction to Integrity NonStop NS-Series
Operations
HP Integrity NonStop NS-Series Operations Guide—529869-001
1-12
Overview of OSM Applications
Overview of OSM Applications
HP NonStop Open System Management (OSM) applications perform a variety of
functions, such as:
•
The OSM Low-Level Link Application is primarily used for down-system support,
such as Two startup event stream windows and two startup TACL windows are
automatically launched on the system console configured to receive them. on
page 15-6, Recovery Operations for Processors on page 9-9, and configuring
IOAM and P-switch modules (see the Integrity NonStop NS-Series Hardware
Installation Manual).
•
The OSM Service Connection is used to monitor, inventory, and perform actions
on system and ServerNet Cluster components. See Using OSM to Monitor the
System on page 3-7 for an overview of how the OSM Service Connection is used
to monitor your system components.
•
The OSM Event Viewer is used for Section 4, Monitoring EMS Event Messages.
•
The OSM Notification Director is used for Monitoring Problem Incident Reports on
page 3-12 and dialing out information to your service provider.
Launching OSM Applications
Several operations tasks in this guide require you to log on to one of the OSM
applications. Assuming that all OSM client components have been installed on the
system console, launch the desired application as described below, then see the online
help (or default home page, for the browser-based OSM applications) for log-on
instructions.
To launch OSM applications: Start>Programs>HP OSM. Then select the name of the
application to launch:
•
OSM Service Connection
•
OSM Low-Level Link Application
•
OSM Notification Director>Start/Stop
•
OSM Event Viewer
The OSM Service Connection and the OSM Event Viewer are browser-based
applications. Assuming that the OSM Console Tools component has been installed on
the system console, the Start menu shortcuts launch a default web page for these two
applications. From that page, you can select the system of your choice from the list of
bookmarks displayed in the left column of the page (available bookmarks include those
that were user-created during previous sessions and those converted automatically
from an existing OSM system list). If no bookmarks are available, the web page also
contains instructions on how to access these applications by entering a system URL as
an Internet Explorer address. The system console-based OSM Console Tools
component is not required to use the OSM Service Connection and the OSM Event
Viewer applications; it merely installs the Start menu shortcuts and default home pages