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-12
Tracing a Communications Line
The system displays a listing similar to this output. The NEIGHBOR field displays the
system to which a given line connects, and the STATUS field indicates whether the line
is up:
Tracing a Communications Line
Use the SCF TRACE command to trace the operation of a communications line. The
line continues normal operation while being traced, but it passes all its message traffic
to a trace procedure. Tracing enables you to see the history of a communications line,
including its internal processing.
You can display trace files by using the commands available in the PTrace program.
For information about PTrace, refer to the PTrace Reference Manual. For information
about configuring a trace by using the SCF TRACE command, refer to the
configuration and management manual for the communications subsystem you want to
trace.
1-> INFO PROCESS $NCP, LINESET
EXPAND Info PROCESS $NCP , LINESET
LINESETS AT \COMM (116) #LINESETS=35 TIME: JUL 9,2001 19:28:04
LINESET NEIGHBOR LDEV TF PID LINE LDEV STATUS FileErr#
1 \CYCLONE (206) 363 200K ( 0, 287)
1 363 READY
2 \SNAX (118) 353 200K ( 5, 333)
1 353 READY
3 \TESS (194) 554 200K ( 8, 279)
1 554 READY
4 \TSII (099) 556 200K ( 2, 265)
1 556 READY
5 \ESP (163) 365 200K ( 1, 274)
1 365 READY
6 \SVLDEV (077) 538 200K ( 7, 265)
1 538 READY
.
.
.
27 \SIERRA (012) 183 10K ( 4, 290)
1 183 READY
28 \PRUNE (175) 677 200K ( 5, 334)
1 677 READY
29 \OPMAN (252) 276 790K ( 5, 294) NPT
1 276 READY
30 \SOCIAL (045) 165 790K ( 8, 280)
1 165 READY
31 \NCCORP2 (080) 295 790K ( 8, 264)
1 295 READY
32 \CS8 (152) 323 -- -- -----
1 323 NOT READY (124)
33 \CORE (241) 324 -- -- -----
1 324 NOT READY (124)
34 \SUNTEC (062) 367 790K ( 5, 293) NPT
1 367 READY
35 \CS8 (152) 368 -- -- -----
1 368 NOT READY (124)