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
I/O Adapters and Modules: Monitoring and Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
8-3
Monitoring I/O Adapters and Modules
G4SAs are configured and managed through the Subsystem Control Facility (SCF)
interface to the ServerNet LAN Systems Access (SLSA) subsystem. The SLSA
subsystem is preinstalled and preconfigured and is started during the system-load
sequence.
For information about the SLSA subsystem, refer to the LAN Configuration and
Management Manual.
Monitoring I/O Adapters and Modules
Use the Subsystem Control Facility (SCF) or the OSM Service Connection to monitor
the FCSAs, G4SAs, and ServerNet/DAs.
Monitoring the FCSAs
To monitor the FCSAs using OSM, refer to Using OSM to Monitor the System on
page 3-7.
To monitor the FCSA and its attached devices with SCF, use the SCF INFO and SCF
STATUS commands.
For example, to monitor all FCSAs using SCF:
> SCF STATUS ADAPTER $ZZSTO.#FCSA*, DETAIL
The SCF Reference Manual for the Storage Subsystem provides reference details and
examples for using the SCF INFO and SCF STATUS commands.
When monitoring FCSAs using the OSM Service Connection, the states of the FCSAs
should indicate normal operation. Table 8-1 lists the possible states for the FCSA.
Table 8-1. Service, Flash Firmware, Flash Boot Firmware, Device, and
Enabled States for the FCSA (page 1 of 2)
State Description
Service State: OK The resource is functioning normally and does not require attention or
service.
Service State:
Attention
Required
The resource requires operator attention. This condition sometimes
generates an alarm, and the component that requires attention is
colored yellow in the tree pane and in the Physical and ServerNet
views of the view pane.
Service State:
Service Required
The resource requires service. This condition generates an alarm, and
the component that requires service is colored red in the tree pane and
in the Physical and ServerNet views of the view pane
Flash Compare
State: Same
Current and default versions are the same.
Flash Compare
State: Up-rev
The current version is newer than the default version.