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-6
Loading the System
•
Two startup event stream windows and two startup TACL windows are
automatically launched on the system console configured to receive them.
•
The CIIN function is enabled by default. See CIIN File on page 16-6.
System Load to a Specific Processor
Alternately, you can perform a system load from a specified processor. When you load
the system from a specified logical processor:
•
The other logical processors are not primed automatically.
•
Because the processors not being loaded are not primed, you can perform
processor dumps, if necessary. If you need to dump processors, refer to Section 9,
Processors and Components: Monitoring and Recovery.
°
Do not prime or reset all the processor elements in a logical processor until
after the memory dump.
°
Disable the CIIN file to prevent any processors configured to reload in that file
from being reloaded. The startup event stream windows and Startup TACL
windows are not launched automatically when the CIIN file is disabled. See
CIIN File on page 16-6.
•
The Processor Element Dump Setting option becomes available in the System
Load dialog box. For more information about this option, see Section 9, Processors
and Components: Monitoring and Recovery.
•
You must initiate the load action as described in Performing a System Load From a
Specific Processor on page 15-11.
System Load Disks
An Integrity NonStop NS-series system can contain multiple system disk pairs in
different locations. Use the System Load dialog box to select which system disk to load
from. You select the system disk from the Configuration drop-down menu. The system
load disk you choose must be in the configured location, properly configured as a
system disk, and contain the software configuration that you want to load. The system
disk that you load from starts as $SYSTEM. Any alternate system disks start using
their alternate name.
After you select a system load disk, the Disk Type box indicates whether you’ve
selected a Fibre Channel (FCDM) or SCSI disk. The Path window is populated with
information about four load paths. You can double-click on a row to make changes.
However, the changes do not persist after the dialog box is closed.
You can choose these system load disks:
•
An FCDM-Load attempts to load the system from a system disk in the disk drive
enclosure connected to IOAM enclosure group 110:










