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
Determining Your System Configuration
HP Integrity NonStop NS-Series Operations Guide—529869-001
2-3
Terms Used to Describe System Hardware
Components
Terms Used to Describe System Hardware Components
The terms used to describe system-hardware components vary. These terms include:
•
Device
•
System resource or object
Device
A device can be a physical device or a logical device. A physical device is a physical
component of a computer system that is used to communicate with the outside world
or to acquire or store data. A logical device is a process used to conduct input or
output with a physical device.
System Resource or Object
The term “system resource” is used in OSM documentation to refer to server
components that OSM software displays, monitors, and often controls. The term
“object” is often used when referring to a specific resource, such as “the Disk object.”
All system resources are displayed in hierarchical form in the tree pane of the OSM
Service Connection; many are also displayed in Physical or Inventory views of the view
pane. The effect of selecting an object in either pane is the same: for example, you can
view attributes for the selected system resource in the Attributes tab, view alarms for
that resource (if any exist) in the Alarms tab, or right-click on the resource object and
select Actions, to display the Actions dialog box (from which you can select and
perform actions on the selected system resource). Besides physical hardware
components, such as IOAM enclosures, power supplies, ServerNet adapters, and disk
and tape drives, system resources also include logical entities that OSM supports,
such as logical processors, ServerNet fabrics, and LIFs (logical interfaces).
Recording Your System Configuration
As a system operator, you need to understand how your system is configured so you
can confirm that the hardware and system software are operating normally. If problems
do occur, knowing your configuration allows you to pinpoint problems more easily. If
your system configuration is corrupted, documentation about your configuration is
essential for recovery. You should be familiar with the system organization, system
configuration, and naming conventions.
Several methods are available for researching and recording your system
configuration:
•
Maintaining records in hard-copy format
•
Using the OSM Service Connection to inventory your system
In the OSM Service Connection tree pane, select the System object. From the
View pane drop-down menu, select Inventory to display a list of the system’s
hardware resources. Click Save to save this list to a Microsoft Excel file.










