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
Starting and Stopping the System
HP Integrity NonStop NS-Series Operations Guide—529869-001
15-4
Powering On the System From a No Power State
•
You must power on Fibre Channel to SCSI Converter devices connected to
your system before you power on the tape devices attached to it. The
converter must be powered on first to be able to discover the tape devices as
they are powered on.
•
Maintenance switches installed outside of a modular cabinet must be powered
on according to the instructions provided with the switch.
2. Locate the circuit breaker that controls the power cords connected to the system
cabinets. In most case, each modular cabinet in a system powers on as soon as
soon as the power is applied. In addition, these components power on when the
Integrity NonStop NS-server is powered on:
•
NonStop I/O enclosures connected to the system
•
Maintenance switches installed in a modular cabinet power
3. To physically monitor power-on activity:
a. Check fan activity for the processor switches, processor slices, IOAM
enclosures, and disk drive enclosures. Check that the fans are turning and that
you can feel air circulate through the components.
b. After the POSTs finish, check that only green power-on LEDs are lit in the
system components before you start the server. For more information about
status LEDs, see Using the Status LEDs to Monitor the System on page 3-20.
4. After the POSTs finish, check the AC power cords. Perform this test only if you
have connected redundant power cords to separate circuits:
a. If you have a UPS installed, switch off the UPS outputs.
b. If you do not have a UPS installed:
1. Locate the circuit breaker that controls half the power cords.
2. Switch this breaker off.
c. Check that all components are still operating.
d. Switch this breaker back on.
e. Locate the other circuit breaker that controls the other half of the power cords.
f. Switch this breaker off.
g. Check that all components are still operating.
h. Switch this breaker back on.
i. If any components fail during any of the power shutdowns, see Components
Fail When Testing the Power on page 15-19.
j. If you have a UPS installed, switch off the UPS outputs.
Note. The maintenance switch does not have redundant power.