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-4
Using SCF to Determine Your System Configuration
•
Using SCF to list objects and devices and to display subsystem configuration
information
For information on forms available that can help you record your system configuration,
refer to the Integrity NonStop NS-Series Planning Guide.
Using SCF to Determine Your System
Configuration
SCF is one of the most important tools available to you as a system operator. SCF
commands configure and control the objects (lines, controllers, processes, and so on)
belonging to each subsystem running on the Integrity NonStop NS-series server. You
also use SCF to display information about subsystems and their objects.
SCF accepts commands from a workstation, a disk file, or an application process. It
sends display output to a workstation, a file, a process, or a printer. Some SCF
commands are available only to some subsystems. An overall SCF reference is the
SCF Reference Manual for H-Series RVUs. Subsystem-specific information appears in
a separate manual for each subsystem. For a partial list of these manuals, refer to
Appendix C, Related Reading.
More details about the functions of SCF appear in Subsystem Control Facility (SCF) on
page B-4.
SCF System Naming Conventions
SCF object names usually follow a consistent set of naming conventions defined for
each installation. HP preconfigures some of the naming conventions to create the
logical device names for many SCF objects.
System planning and configuration staff at your site likely will change or expand on the
preconfigured file-naming conventions that HP provides, typically by establishing
naming conventions for configuring such objects as storage devices, communication
processes, and adapters. These conventions should simplify your monitoring tasks by
making process or object functions intuitively obvious to someone looking at the object
name. For example, in your environment, tape drives might be named $TAPEn, where
n is a sequential number.
The SCF Reference Manual for H-Series RVUs lists naming conventions for SCF
objects, as well as HP reserved names that cannot be changed or used for other
objects or processes in your environment.










