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-13
Additional Subsystems Controlled by SCF
Examples of the INFO command used with the OBEYFORM option are:
-> INFO ADAPTER $*, OBEYFORM
-> INFO LIF $*, OBEYFORM
WAN Subsystem
Before using commands listed in Table 2-6, type this command to make the wide area
network (WAN) subsystem the default object:
> SCF ASSUME PROCESS $ZZWAN
The WAN subsystem has responsibility for all WAN connections.
Additional Subsystems Controlled by SCF
Table 2-7 lists the names associated with additional subsystems that can be controlled
by SCF, along with its device types. You can use SCF commands to display the
current attribute values for these objects.
Some SCF commands are available only to some subsystems. The objects that each
command affects and the attributes of those objects are subsystem specific. This
subsystem-specific information is presented in a separate manual for each subsystem.
A partial list of these manuals appears in Table 6-1 on page 6-13.
Refer to the SCF Reference Manual for H-Series RVUs for further information.
Table 2-6. Displaying Information for the WAN Subsystem ($ZZWAN)
To Display Information About These
Configured Objects Enter This Command
The WAN subsystem manager LISTDEV WAN
All WAN configuration managers, TCP/IP
processes, and WANBoot processes
INFO *
All PATH names INFO PATH *
The WAN adapters INFO ADAPTER *
All DEVICE objects INFO DEVICE *
All PROFILE objects INFO PROFILE *
Table 2-7. Subsystem Objects Controlled by SCF (page 1 of 2)
Subsystem
Acronym Description
Device
Type
Device
Subtype
AM3270 AM3270 Access Method 60 0 or 10
ATM Asynchronous Transfer Mode (ATM)
protocol
42 0 or 1
ATP6100 Asynchronous Terminal Process 6100 53 0










