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-9
Monitoring the NonStop TCP/IP Subsystem
Monitoring CLIPs
To display the current status for a CLIP:
> SCF STATUS SERVER $ZZWAN.#concentrator-name.clip-num
Values for the CLIP number are 1, 2, or 3.
The system displays a listing similar to:
Monitoring the NonStop TCP/IP Subsystem
This subsection describes how to obtain the status for NonStop TCP/IP processes,
routes, and subnets. For additional information, refer to the TCP/IP Configuration and
Management Manual. For NonStop TCP/IPv6, refer to the TCP/IPv6 Configuration and
Management Manual.
Monitoring the NonStop TCP/IP Process
To display the dynamic state of a NonStop TCP/IP process, first list the names of all
NonStop TCP/IP processes:
-> SCF LISTDEV TCPIP
Then type:
> SCF STATUS PROCESS tcp/ip-process-name
where tcp/ip-process-name is the name of the process you want information
about.
The system displays a listing similar to this output, which is for process $ZTCO:
-> status server $zzwan.#s01.1
WAN Manager STATUS SERVER for CLIP \COWBOY.$ZZWAN.#S01.1
STATE :..........STARTED
PATH A...........: CONFIUGRED
PATH B...........: CONFIGURED
NUMBER of lines. 2
Line...............0 : $SAT23A
Line...............1 : $SAT23B
-> Status Process $ZTCO
TCPIP Status PROCESS \SYSA.$ZTCO
Status: STARTED
PPID.................( 0,107) BPID.............. ( 1. 98)
Proto State Laddr Lport Faddr Fport SendQ RecvQ
TCP TIME-WAIT 130.252.12.3 ftp-data 130.252.12.152 11089 0 0
TCP TIME-WAIT 130.252.12.3 ftp-data 130.252.12.152 63105 0 0
TCP ESTAB 130.252.12.3 ftp 130.252.12.152 57441 0 0
TCP TIME-WAIT 130.252.12.3 smtp 130.252.12.8 3309 0 0