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
Creating Startup and Shutdown Files
HP Integrity NonStop NS-Series Operations Guide—529869-001
16-15
Spooler Warm-Start File
Spooler Warm-Start File
This example command file warm starts the spooler.
After the spooler has been brought up, the printer devices should be in the WAITING
state. This file can be invoked automatically from the STRTSYS file, or you can invoke
it by using the following TACL command:
> OBEY $SYSTEM.STARTUP.SPLWARM
comment -- This is $SYSTEM.STARTUP.SPLWARM
comment -- This file warm starts the spooler, leaving all jobs intact.
SPOOL / IN $SYSTEM.SPL.SPL, OUT $ZHOME, NAME $SPLS, NOWAIT, PRI 149, &
CPU 1/0
SPOOLCOM; SPOOLER, START
comment -- check to see that the spooler started successfully
SPOOLCOM; SPOOLER, STATUS
TMF Warm-Start File
This example command file warm starts the TMF subsystem.
This file can be invoked automatically from the STRTSYS file, or you can invoke it by
using the following TACL command:
> TMFCOM / IN $SYSTEM.STARTUP.TMFSTART, OUT $ZHOME /
-- This is $SYSTEM.STARTUP.TMFSTART
-- This file warm starts the Transaction Management Facility (TMF) subsystem
-- and checks to see if TMF started successfully.
START TMF;ENABLE DATAVOLS *;STATUS TMF;EXIT
TCP/IP Stack Configuration and Startup File
Configuration data for NonStop TCP/IP (conventional TCP/IP) processes is not added
to the configuration database. Therefore, TCP/IP stacks must be both configured and
started for each LAN port that connects to a SWAN concentrator each time you start
the system, unless you are using NonStop TCP/IPv6 over SWAN. (If so, see the
manuals that support those TCP/IP subsystems.)
You can create TACL command files to configure TCP/IP stacks on the other ports by
assigning the appropriate values the following variables in this example file:
The NonStop TCP/IPv6 subsystems participate in the system configuration database
(however, not with the initial configuration database that is shipped with a new system).
•
TCP/IP Configuration and Management Manual
•
TCP/IPv6 Configuration and Management Manual
GW^ADDR LINE^NAME TCP^CPU2
HOST^NAME LST^NAME TCP^NAME
IP^ADDR TCP^CPU1 TEL^NAME