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-21
Using the Status LEDs to Monitor the System
Power Middle
Green
Flashes when EMU is operational and
performing locate.
On when EMU is operational. An EMU or
an enclosure fault might still exist.
Off when power has just been applied to
an enclosure, or when an enclosure fault
exists.
Enclosure Sta-
tus
Amber Flashes when EMU is operational and
performing locate.
On when EMU is operational, but an
enclosure fault exists.
Off when EMU is operational, or power
has just been applied to an enclosure, or
when an EMU fault exists that is not an
enclosure fault, or when an enclosure
fault exists.
FC-AL I/O Mod-
ule
Power-on Middle
Green
Lights when power is on and module is
available for normal operation. If light is
off, the module is nonoperational: check
FCSAs, cables, and power supplies.
Port 1 Bottom
Green
Lights when carrier on Port 1 is opera-
tional.
Port 2 Top Green Lights when carrier on Port 2 is opera-
tional.
Fibre Channel
ServerNet
adapter (FCSA)
Power-on Green Lights when the adapter is receiving
power.
Service Amber Lights to indicate internal failure or ser-
vice action required.
Gigabit Ethernet
4-port Server-
Net adapter
(G4SA)
Power-on Green Lights when the adapter is receiving
power.
Service Amber Lights to indicate internal failure or ser-
vice action required.
LSU I/O PIC Power-on Green Lights when power is on and adapter is
available for normal operation.
Service Amber Lights when a POST is in progress,
board is being reset, or a fault exists.
LSU optics
adapter connec-
tor
Power-on Green Lights when NonStop Blade Element
optic or ServerNet link is functional.
Table 3-4. Status LEDs and Their Functions (page2of3)
Location LED Name Color Function










