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
Communications Subsystems: Monitoring and
Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
6-3
Local Area Networks (LANs) and Wide Area
Networks (WANs)
•
Physical interfaces (PIFs)
Processes that use the SLSA subsystem to send and receive data on a LAN attached
to an Integrity NonStop server are called LAN service providers. Two service
providers—the NonStop TCP/IP and NonStop TCP/IPv6 subsystems and the Port
Access Method (PAM)—are currently supported. They provide access for these
subsystems:
Processes, user applications, and subsystems that use the SLSA subsystem and
related LAN providers to connect to an FCSA or G4SA attached to an Integrity
NonStop NS-series server are called LAN clients. For example, the WAN subsystem is
a client of the SLSA subsystem because the SLSA subsystem provides the WAN
subsystem access to the ServerNet wide area network (SWAN) concentrator through
the LAN.
The WAN subsystem is used to control access to the SWAN concentrator. Depending
on your configuration, it can be used to configure and manage both WAN and LAN
connectivity for these communication subsystem objects:
You can define these communications subsystem objects as WAN subsystem devices.
LAN Service Provider Subsystems Supported
NonStop TCP/IP subsystem,
NonStop TCP/IPv6 subsystem
The Expand subsystem, which provides Expand-over-
IP connections.
Port Access Method (PAM) Ethernet and token-ring LANs. The OSI/AS, OSI/TS,
SNAX/XF, and SNAX/APN subsystems communicate
with SLSA through the PAM subsystem.
Object Connectivity By
AM3270 Line-handler processes
Asynchronous Terminal Process
6100 (ATP6100)
Line-handler processes
Communications Process
subsystem (CP6100)
Line-handler processes
EnvoyACP/XF Line-handler processes
Envoy subsystem Line-handler processes
Expand Subsystem network control process and line-handler
processes
ServerNet cluster (Expand-over-
ServerNet)
Line-handler processes
SNAX/APN Subsystem service manager process and line-handler
processes
SNAX/XF Subsystem service manager process and line-handler
processes
TR3271 Line-handler processes
X25AM Line-handler processes