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
Determining Your System Configuration
HP Integrity NonStop NS-Series Operations Guide—529869-001
2-2
Modular Hardware Components
Modular Hardware Components
Hardware for Integrity NonStop systems is implemented in modules, or enclosures that
are installed in modular cabinets. The servers include these hardware components:
•
Modular Cabinet with Power Distribution Unit (PDU)
•
NonStop Blade Complex
•
NonStop Blade Element
•
Logical Synchronization Unit (LSU)
•
Processor Switch
•
I/O Adapter Module (IOAM) Enclosure and I/O Adapters
•
Disk Drive Enclosure
•
Maintenance Switch (Ethernet)
•
Optional UPS and ERM
•
System Console
•
Cable Management Devices
•
Enterprise Storage System (ESS)
For descriptions of these components and how they fit within an Integrity NonStop
server cabinet, refer to the Integrity NonStop NS-Series Hardware Installation Manual
and the Integrity NonStop NS-Series Planning Guide.
Many enclosure combinations are possible within the modular cabinets that make up
an Integrity NonStop server. The applications and purpose of any Integrity NonStop
server determine the number and combinations of these enclosures and the cabinets
that house them.
For example, installing three NonStop Blade Elements provides up to four triplex
logical processors per NonStop Blade Element with 12 NonStop Blade Elements
providing a maximum of 16 triplex logical processors.
IOAM enclosures connect via ServerNet links to the processor switch (p-switch). One
IOAM enclosure provides ServerNet connectivity for up to 10 ServerNet I/O adapters
on each of the two ServerNet fabrics. FCSAs and G4SAs can be installed in an IOAM
enclosure in any mixture for communications to storage devices and subsystems as
well as to LANs. Additional IOAM enclosures can be added to increase connectivity
and storage resources.
Integrity NonStop systems connect to NonStop S-series I/O enclosures by using fiber-
optic ServerNet links to connect the p-switches of the Integrity NonStop systems to
IOMF 2 CRUs in the I/O enclosures.