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
Power Failures: Preparation and Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
14-2
When to Use This Section
When to Use This Section
Use this section for information about how to prepare for power failures and how to
recover if a power failure occurs.
System Response to Power Failures
NonStop NS-Series Cabinets (Modular Cabinets)
NonStop NS-series servers are designed to operate in a computer-room environment
containing a site UPS. Without a UPS, a system will stop uncontrollably when the
power is lost. An optional UPS module can be installed in a modular cabinet to provide
power if no site UPS is available.
If AC power to a NonStop NS-series server is lost, the system will shut down after a
preset time as long as UPS power is available. If the system shuts down, it will be
necessary to restart the system manually when AC power is restored.
If modular cabinets lose power without a UPS, recovery of lost data will be difficult and
files might be corrupted.
Regardless of system power-fail scenario, if site air conditioning fails and the
computer-room temperature rises, the system might shut itself down uncontrollably as
each processor reaches its critical temperature. Refer to the NonStop NS-Series Site
Preparation Guide.
NonStop S-Series I/O Enclosures
NonStop S-series I/O enclosures have internal batteries and do not require a UPS.
NonStop S-series enclosures must shut down before their battery power is lost. For
information about power fail for I/O enclosures, refer to the NonStop NS-Series
Planning Guide.
External Devices
External (peripheral), devices, such as tape drives, external disk drives, LAN routers,
and SWAN concentrators, are not backed up by internal batteries. External devices
behave differently than a system during power failure according to the UPS support
provided:
No UPS Peripheral devices will fail immediately if not supported by a UPS.
With a Site UPS A site UPS should support external devices until its capacity to supply
power is exhausted.
With an Internal
UPS
An optional internal UPS will not support external devices during
power failure.