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
Communications Subsystems: Monitoring and
Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
6-4
Monitoring Communications Subsystems and Their
Objects
Monitoring Communications Subsystems and
Their Objects
Monitoring and recovery operations for communications subsystems can be complex.
An error in any of the components—service providers, clients, objects, adapters,
processes, and so on—can generate multiple error messages from many
interdependent subsystems and processes. Analyzing and solving an error that
originates in an object controlled by a LAN or a WAN often requires that you
methodically gather status information about the affected services and then eliminate
objects that are working normally.
Detailed monitoring and recovery techniques for devices and processes related to
communications subsystems are discussed in detail in the manuals for each
subsystem. For more information, refer to Related Reading on page 6-13.
This guide provides some basic commands you can use to identify and resolve
common problems. Your most powerful tool for monitoring and collecting information
about subsystem objects is the SCF facility. You can use SCF commands to get
information and status for subsystem objects by name, device type, or device subtype.
Subdevices are defined if a subsystem potentially operates on numerous, separately
addressable objects, such as stations on a multipoint line; the line is a device, and the
stations are subdevices.
For a list of subsystems with their device type numbers and device subtypes, see
Using SCF to Determine Your System Configuration on page 2-4.
Monitoring the SLSA Subsystem
This subsection describes how to obtain the status of adapters, SACs, LIFs, and PIFs.
For more information on the SLSA subsystem, refer to the LAN Configuration and
Management Manual.
Monitoring the Status of an Adapter and Its Components
1. To monitor the status of an adapter:
> SCF STATUS ADAPTER adapter-name
A listing similar to this example is sent to your home terminal:
->STATUS ADAPTER $ZZLAN.G11123
SLSA Status ADAPTER
Name State
$ZZLAN.G11123 STARTED