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

Preventive Maintenance
HP Integrity NonStop NS-Series Operations Guide—529869-001
17-2
Checking Physical Security
Checking Physical Security
Your company’s security policy will guide you in the kind of security monitoring you
perform. You might be asked to check doors and windows at the beginning and end of
your shift and report the presence of unauthorized persons. In some facilities,
operations staff might be responsible for monitoring and maintaining electronic security
systems.
Maintaining Order and Cleanliness
Clutter and debris can cause accidents and fires. Dust, smoke, and spilled liquids can
damage system hardware components. Depending on your company’s policies, you
might be asked to keep the computer room clean; inspect air filters; keep printer dust
under control through periodic vacuuming; and enforce a ban on smoking, eating, and
drinking in the computer room.
Checking Fire-Protection Systems
You might also be asked to check the fire alarms and fire extinguisher systems in your
facility.
Cleaning System Components
This subsection contains basic information about cleaning enclosures, printers, and
tape drives. Many companies have service-level agreements with HP that include
regular preventive maintenance (PM) of their hardware components. If a Field Service
Organization (FSO) representative handles cleaning and other preventive maintenance
for your company, you need not be concerned with the cleaning tasks mentioned here.
Cleaning an Enclosure
Cleaning an enclosure is an infrequent task that you perform as required by conditions
at your site. Many installations require only occasional dusting. To dust an enclosure,
use a lint-free, antistatic dust cloth.
If you need to clean an enclosure, use a cotton cloth and a cleaning product
formulated for computer equipment. Or use a damp cotton cloth and a mild,
nonabrasive soap.
Cleaning and Maintaining Printers
Inspect all printers and replace the ribbons on line printers as needed. Replace the
toner cartridges of laser printers that are shared by the user community when print
quality lessens. To remove paper dust that can affect printer operation, vacuum
printers periodically.
Caution. Do not use solvents or spray products on any part of an enclosure.










