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
ServerNet Resources: Monitoring and Recovery
HP Integrity NonStop NS-Series Operations Guide—529869-001
7-4
Monitoring the ServerNet Fabrics Using OSM
Monitoring the ServerNet Fabrics Using OSM
To check the ServerNet fabrics:
1. Log on to the OSM Service Connection.
2. Expand the tree pane to locate and select the internal or external ServerNet fabric
objects:
a. The X and Y internal ServerNet fabric objects are located under the System
and Fabric Group objects.
b. The X and Y external ServerNet fabric objects are located under the ServerNet
Cluster object (if your system is part of a ServerNet cluster).
3. Check the fabric objects for:
a. If a fabric object icon is covered by a red or yellow triangular symbol, check the
Attributes tab in the details pane for degraded attribute values. The Service
State attribute is only displayed in the Attributes tab if it has a value of other
than OK. If a degraded Service State is indicated, there will be an associated
alarm to provide more information about the cause of the problem.
b. If a bell-shaped symbol is displayed next to a fabric icon in the tree pane,
select the Alarms tab from the details pane. To get more information on an
individual alarm, click to select the alarm, then right-click and select Details.
c. If a fabric object icon is covered by a yellow arrow, there is a problem on a
subcomponent of that fabric. Expand the fabric object to locate the
subcomponent object reporting the alarm or problem attribute.
Under each internal fabric object, you’ll find its associated processor switch
(P-switch) module and subcomponents.
For more information on monitoring and recovery for external fabrics, see the
appropriate ServerNet cluster manual for your particular ServerNet cluster
configuration and hardware.
Monitoring the ServerNet Fabrics Using SCF
The SCF STATUS SERVERNET command displays a matrix for the ServerNet X
fabric and a matrix for the ServerNet Y fabric. Each matrix shows the status of the
paths between all pairs of processors.