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
ServerNet Resources: Monitoring and Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
7-6
Monitoring the ServerNet Fabrics Using SCF
Normal ServerNet Fabric States
Normal states for a path on the ServerNet fabrics can be one of:
•
UP
The path from the processor in the FROM row to the processor in the TO column is
up. The status for all ServerNet connections between existing processors in a
system should be UP.
•
<-DOWN (for an entire row)
The processor in the FROM row is down or nonexistent. If the processor in the
FROM row does not exist on your system, this status is normal. Otherwise, refer to
Identifying ServerNet Fabric Problems on page 7-6.
•
UNA (unavailable)
The processor in the TO column is down or nonexistent. Therefore, the path from
the processor in the FROM row to the processor in the TO column is down. If the
processor in the TO column does not exist on your system, this status is normal.
Otherwise, refer to Identifying ServerNet Fabric Problems on page 7-6.
Identifying ServerNet Fabric Problems
Depending on how your system is configured, these states for a path on the ServerNet
fabrics might indicate a problem:
•
DIS (disabled)
The ServerNet fabric is down at the TO location. As a result, the path from the
processor in the FROM row to the processor in the TO column is down for
receiving; that is, the processor in the TO column cannot receive from any other
processor or from I/O devices. DIS overrides both UP and DN.
•
DN (down)
The path from the processor in the FROM row to the processor in the TO column is
down because the path is failing. The processor in the FROM row cannot send to
the processor in the TO column.
•
<- DOWN (for an entire row)
The processor in the FROM row is down or nonexistent. For a processor that does
exist on your system, this status is abnormal.
•
ERROR nnn (for an entire row)
The processor in the FROM row unexpectedly returned a file-system error to that
ServerNet fabric.
•
UNA (unavailable)