This guide describes how to perform routine system hardware operations for HP
Integrity NonStop™ NS-series servers. These tasks include monitoring the system,
performing common operations tasks, and performing routine hardware maintenance.
This guide is written for system operators.
Product Version
N.A.
Supported Release Version Updates (RVUs)
This guide supports H06.08 and all subsequent H-series RVUs until otherwise
indicated by its replacement publication.
Manual Informationxiii
New and Changed Informationxiii
About This Guidexv
Who Should Use This Guidexv
What Is in This Guidexvi
Where to Get More Informationxvii
Notation Conventionsxviii
1. Introduction to Integrity NonStop NS-Series Operations
When to Use This Section1-2
Understanding the Operational Environment1-2
What Are the Operator Tasks?1-2
Monitoring the System and Performing Recovery Operations1-2
Preparing for and Recovering from Power Failures1-3
Stopping and Powering Off the System1-3
Powering On and Starting the System1-3
Creating Startup and Shutdown Files1-3
Performing Preventive Maintenance
Operating Disk Drives and Tape Drives
Responding to Spooler Problems1-4
Updating Firmware1-4
Determining the Cause of a Problem:
A Systematic Approach1-4
A Problem-Solving Worksh eet1-4
Task 1: Get the Facts1-6
Task 2: Find and Eliminate the Cause of the Problem1-7
1-3
1-3
Task 3: Escalate the Problem If Necessary1-8
Task 4: Prevent Future Problems1-9
Hewlett-Packard Company—529869-005
i
Contents
2. Determining Your System Configuration
Logging On to an Integrity NonStop Server1-9
System Consoles1-9
Opening a TACL Window1-10
Overview of OSM Applications1-1 1
Launching OSM Applications1-11
Service Procedures1-12
Support and Service Library1-12
2. Determining Your System Configuration
When to Use This Section2-1
Modular Hardware Components2-2
Differences Between Integrity NonStop NS-Series Systems2-2
Terms Used to Describe System Hardware Components2-4
Recording Your System Configuration2-4
Using SCF to Determine Your System Configuration2-5
SCF System Naming Conventions2-5
SCF Configuration Files2-5
Using SCF to Display Subsystem Configuration Information2-6
Displaying SCF Configuration Information for Subsystems2-9
When to Use This Section3-1
Functions of Monitoring3-2
Monitoring Tasks3-2
Working With a Daily Checklist3-2
Tools for Checking the Status of System Hardware3-3
Additional Monitoring Tasks3-6
Monitoring and Resolving Problems—An Approach3-7
Using OSM to Monitor the System3-7
Using the OSM Service Connection3-7
Recovery Operations for Problems Detected by OSM3-12
Monitoring Problem Incident Reports3-12
Using SCF to Monitor the System3-12
Determining Device States3-13
Automating Routine System Monitoring3-16
Using the Status LEDs to Monitor the System3-20
Related Reading3-22
HP Integrity NonStop NS-Series Operations Guide—529869-005
ii
Contents
4. Monitoring EMS Event Messages
When to Use This Section4-1
What Is the Event Management Service (EMS)?4-1
Tools for Monitoring EMS Event Messages4-1
OSM Event Viewer 4-2
EMSDIST4-2
ViewPoint4-2
Web ViewPoint4-2
Related Reading4-2
5. Processes: Monitoring and Recovery
When to Use This Section5-1
Types of Processes5-1
System Processes5-1
I/O Processes (IOPs)5-2
4. Monitoring EMS Event Messages
Generic Processes5-2
Monitoring Processes5-3
Monitoring System Processes5-3
Monitoring IOPs5-4
Monitoring Generic Processes5-4
Recovery Operations for Processes5-6
Related Reading5-6
6. Communications Sub systems: Mon itoring and Recovery
When to Use This Section6-1
Communications Subsystems6-1
Local Area Networks (LANs) and Wide Area Networks (WANs)
Monitoring Communications Subsystems and Their Objects
Monitoring the SLSA Subsystem6-4
Monitoring the WAN Subsystem6-6
Monitoring the NonStop TCP/IP Subsystem6-9
Monitoring Line-Handler Process Status6-10
Tracing a Communications Line6-12
6-4
6-2
Recovery Operations for Communications Subsystems 6-13
Related Reading6-13
HP Integrity NonStop NS-Series Operations Guide—529869-005
iii
Contents
7. ServerNet Resources: Monitoring and Recovery
7. ServerNet Resources: Monitoring and Recovery
When to Use This Section7-1
ServerNet Communications Network7-1
System I/O ServerNet Connections7-4
Monitoring the Status of the ServerNet Fabrics7-4
Monitoring the ServerNet Fabrics Using OSM7-5
Monitoring the ServerNet Fabrics Using SCF7-6
Related Reading7-8
8. I/O Adapters and Modules: Monitoring and Recovery
When to Use This Section8-1
I/O Adapters and Modules8-2
Fibre Channel ServerNet Adapter (FCSA8-2
Gigabit Ethernet 4-Port Adapter (G4SA)8-2
4-Port ServerNet Extender (4PSE)8-3
Monitoring I/O Adapters and Modules8-3
Monitoring the FCSAs8-4
Monitoring the G4SAs8-5
Monitoring the 4PSEs8-7
Recovery Operations for I/O Adapters and Modules8-7
Related Reading8-8
9. Processors and Components: Monitoring and Recovery
When to Use This Section9-1
Overview of the NonStop Blade Complex9-2
Monitoring and Maintaining Processors9-4
Monitoring Processors Automatically Using TFDS
Monitoring Processor Status Using the OSM Low-Level Link
Monitoring Processor Status Using the OSM Service Connection9-5
Monitoring Processor Performance Using ViewSys9-7
Identifying Processor Problem s9-7
Processor or System Hangs9-7
Processor Halts9-8
9-4
9-5
OSM Alarms and Attribute Values9-8
HP Integrity NonStop NS-Series Operations Guide—529869-005
iv
Contents
10. Disk Drives: Monitoring and Recovery
Recovery Operations for Processors9-9
Recovery Operations for a Processor Halt9-9
Halting One or More Processors9-10
Reloading a Single Processor on a Running Server9-10
Recovery Operations for a System Hang9-14
Enabling/Disabling Processor and System Freeze9-15
Freezing the System and Freeze-Enabled Processors9-15
Dumping a Processor to Disk9-15
Backing Up a Processor Dump to Tape9-19
Replacing Processor Memory9-19
Replacing the Processor Board and Processor Entity9-19
Submitting Information to Your Service Provider9-19
Related Reading9-22
10. Disk Drives: Monitoring and Recovery
When to Use This Section10-1
Overview of Disk Drives10-2
Internal SCSI Disk Drives10-2
M8xxx Fibre Channel Disk Drives10-3
Enterprise Storage System (ESS) Disks10-3
Monitoring Disk Drives10-4
Monitoring Disk Drives With OSM10-4
Monitoring Disk Drives With SCF10-5
Monitoring the State of Disk Drives10-9
Monitoring the Use of Space on a Disk Volume10-9
Monitoring the Size of Database Files10-9
Monitoring Disk Configur ation and Perf orma nce10-10
Identifying Disk Drive Problems10-1 1
Internal SCSI Disk Drives10-11
M8xxx Fibre Channel Disk Drives10-11
Recovery Operations for Disk Drives10-12
Recovery Operations for a Down Disk or Down Disk Path10-14
Recovery Operations for a Nearly Full Database File10-15
Related Reading10-15
HP Integrity NonStop NS-Series Operations Guide—529869-005
v
Contents
11. Tape Dr ives: Monitoring and Recovery
11. Tape Drives: Monitoring and Recovery
When to Use This Section11-1
Overview of Tape Drives11-1
Monitoring Tape Drives11-2
Monitoring Tape Drive Status With OSM11-2
Monitoring Tape Drive Status With SCF11-5
Monitoring Tape Drive Status With MEDIACOM11-6
Monitoring the Status of Labeled-Tape Operations11-7
Identifying Tape Drive Problems11-7
Recovery Operations for Tape Drives 11-8
Recovery Operations Using the OSM Service Connection11-8
Recovery Operations Using SCF11-9
Related Reading11-9
12. Print ers and Termin a ls : Monitoring and R e co v ery
When to Use This Section12-1
Overview of Printers and Terminals12-1
Monitoring Printer and Collector Process Status12-2
Monitoring Prin ter Status12-2
Monitoring Collector Process Status12-2
Recovery Operations for Printers and Terminals12-3
Recovery Operations for a Full Collector Process12-3
Related Reading12-3
13. Applications: Monitoring and Recovery
When to Use This Section13-1
Monitoring TMF
Monitoring the Status of TMF
Monitoring Data Volumes13-2
TMF States13-3
Monitoring the Status of Pathway13-4
PATHMON States13-5
Related Reading13-6
13-1
13-2
HP Integrity NonStop NS-Series Operations Guide—529869-005
vi
Contents
14. Pow er Failures: Preparation and Recovery
14. Power Failures: Preparation and Recovery
When to Use This Section14-2
System Response to Power Failures 14-2
NonStop NS-Series Cabinets (Modular Cabinets)14-2
NonStop S-Series I/O Enclosures14-2
External Devices 14-2
ESS Cabinets14-3
Air Conditioning14-3
Preparing for Power Failure14-3
Set Ride-Through Time14-3
Configure OSM Power Fail Support14-3
Monitor Power Supplies14-4
Monitor Batteries14-4
Maintain Batteries14-4
Power Failure Recovery14-4
Procedure to Recover From a Power Failure14-5
Setting System Time14-5
Related Reading14-5
15. Starting and Stopping the System
When to Use This Section15-2
Powering On a System15-2
Powering On the System From a Low Power State15-3
Powering On the System From a No Power State15-3
Starting a System15-5
Loading the System15-5
Starting Other System Components15-9
Performing a System Load15-9
Performing a System Load From a Specific Processor15-11
Reloading Processors15-12
Minimizing the Frequency of Planned Outages15-14
Anticipating and Planning for Change15-14
Stopping Application, Devices, and Processes15-14
Stopping the System15-16
Alerts15-16
Halting All Processors Using OSM15-16
Powering Off a System15-17
System Power-Off Using OSM15-17
System Power-Off Using SCF15-17
Emergency Power-Off Procedure15-18
HP Integrity NonStop NS-Series Operations Guide—529869-005
vii
Contents
Troubleshooting and Recovery Operations15-18
Fans Are Not Turning15-18
System Does Not Appear to Be Powered On15-19
Green LED Is Not Lit After POSTs Finish15-19
Amber LED on a Component Remains Lit After the POST Finishes15-19
Components Fail When Testing the Power15-19
Recovering From a System Load Failure15-20
Getting a Corrupt System Configuration File Analyzed15-21
Recovering From a Reload Failure15-21
Exiting the OSM Low-Level Link15-22
Opening Startup Event Stream and Startup TACL Windows15-22
Related Reading15-24
16. Creating Startup and Shutdown Files
Automating System Startup and Shutdown16-2
16. Creating Startup and Shutdown Files
Managed Configuration Services (MCS)16-2
Startup16-2
Shutdown16-3
For More Information 16-3
Processes That Represent the System Console16-3
$YMIOP.#CLCI16-3
$YMIOP.#CNSL16-3
$ZHOME16-4
$ZHOME Alternative16-4
Example Command Files16-4
CIIN File16-5
Establishing a CIIN File16-6
Modifying a CIIN File16-6
If a CIIN File Is Not Specified or Enabled in OSM16-7
Example CIIN Files16-8
Writing Efficient Startup and Shutdown Command Files16-9
Command File Syntax16-9
Avoid Manual Intervention16-10
Use Parallel Processing16-10
Investigate Product-Specific Techniques16-11
How Process Persistence Affects Configuration and Startup16-11
Tips for Startup Files16-11
HP Integrity NonStop NS-Series Operations Guide—529869-005
viii
Contents
Startup File Examples16-12
Tips for Shutdown Files16-19
Shutdown File Examples16-19
17. Preventive Maintenance
System Startup File16-12
Spooler Warm-Start File 16-14
TMF Warm-Start File16-14
TCP/IP Stack Configuration and Startup File16-14
CP6100 Lines Startup File16-17
ATP6100 Lines Startup File16-17
X.25 Lines Startup File16-17
Printer Line Startup File16-18
Expand-Over-IP Line Startup File16-18
Expand Direct-Connect Line Startup File16-18
System Shutdown File16-20
CP6100 Lines Shutdown File16-21
ATP6100 Lines Shutdown File16-21
X.25 Lines Shutdown File16-21
Printer Line Shutdown File16-22
Expand-Over-IP Line Shutdown File16-22
Direct-Connect Line Shutdown File16-22
Spooler Shutdown File16-23
TMF Shutdown File16-23
17. Preventive Maintenance
When to Use This Section17-1
Monitoring Physical Facilities17-1
Checking Air Temperature and Humidity17-1
Checking Physical Security17-2
Maintaining Order and Cleanliness17-2
Checking Fire-Protectio n Systems17-2
Cleaning System Components17-2
Cleaning an Enclosure17-2
Cleaning and Maintaining Printers17-2
Cleaning Tape Drives17-3
Handling and Storing Cartridge Tapes17-3
HP Integrity NonStop NS-Series Operations Guide—529869-005
ix
Contents
A. Operational Differences Between Systems
Running G-Series and H-Series RVUs
A. Operational Differences Between Systems Runnin g G-Series
and H-Series RVUs
B. Tools and Utilities for Operations
When to Use This AppendixB-1
BACKCOPYB-2
BACKUPB-2
Disk Compression Program (DCOM)B-2
Disk Space Analysis Program (DSAP)B-2
EMSDISTB-2
Event Management Service Ana lyzer (EM SA)B-2
File Utility Program (FUP)B-3
MeasureB-3
MEDIACOMB-3
NonStop NET/MASTERB-3
NSKCOM and the Kernel-Managed Swap Facility (KMSF)B-3
OSM PackageB-3
PATHCOMB-4
PEEKB-4
RESTOREB-4
SPOOLCOMB-4
Subsystem Control Facility (SCF) B-4
HP Tandem Advanced Command Language (TACL)B-5
TMFCOMB-5
Web ViewPoint B-5
ViewPointB-5
ViewSys
B-6
C. Related Reading
D. Converting Numbers
When to Use This AppendixD-1
Overview of Numbering SystemsD-2
Binary to DecimalD-3
Octal to DecimalD-4
Hexadecimal to DecimalD-5
Decimal to BinaryD-7
Decimal to OctalD-8
Decimal to HexadecimalD-9
HP Integrity NonStop NS-Series Operations Guide—529869-005
x
Contents
Safety and Compliance
Index
Examples
Example 2-1.SCF LISTDEV Command Output2-7
Example 2-2.SCF ADD DISK Command Output2-11
Example 2-3.SCF INFO PROCESS Command Output2-15
Example 2-4.SCF INFO SAC Command Output2-15
Example 2-5.SCF INFO PROCESS $ZZWAN Command Output2-16
Example 2-6.SCF INFO LINE Command Output2-16
Example 3-1.SCF STATUS TAPE Command3-13
Example 3-2.System Monitoring Command File3-16
Example 3-3.System Monitoring Output File3-17
Figures
Safety and Compliance
Figure 3-1.OSM Management: System Icons Indicate Problems Within3-8
Figure 3-2.Expanding the Tree Pane to Locate the Source of Problems3-9
Figure 3-3.Attributes Tab3-10
Figure 3-4.Using System Status Icons to Monitor Multiple Systems3-10
Figure 3-5.Alarm Summary Dialog Box3-11
Figure 3-6.Problem Summary Dialog Box3-11
Figure 7-1.Integrity NonStop NS16000 System7-2
Figure 7-2.Integrity NonStop NS14000 System with IOAM Enclosure7-3
Figure 7-3.I/O Connections to the PICS in a P-Switch7-4
Figure 9-1.Modular NSAA With One NonStop Blade Complex and Four
Processors9-3
Figure 9-2.
Figure 9-3.
Figure 11-1. OSM: Monitoring Tape Drives Connected to an FCSA11-3
Figure 11-2.OSM: Monitoring Tape Drives Connected to an IOMF211-4
Figure 15-1.System Load Dialog Box15-10
Figure 15-2.Logical Processor Reload Parameters15-13
Figure 15-3.Opening a Startup TACL Window15-22
Processor Status Display9-5
OSM Representation of Processor Complex9-6
Figure 15-4.OutsideView Buttons on the Windows Toolbar15-22
Figure D-1.Binary to Decimal ConversionD-3
Figure D-2.Octal to Decimal ConversionD-4
Figure D-3.Hexadecimal to Decimal ConversionD-6
HP Integrity NonStop NS-Series Operations Guide—529869-005
xi
Contents
Tables
Table 1-1.Problem-Solving Worksheet1-5
Table 2-1.Key Subsystems and Their Logical Device Names and Device
Table 2-2.Displaying Information for the TCP/IP Subsystem ($ZTCO)2-9
Table 2-3.Displaying Information for the Kernel Subsystem ($ZZKRN)2-10
Table 2-4.Displaying Information for the Storage Subsystem ($ZZST0)2-10
Table 2-5.Displaying Information for the SLSA Subsystem ($ZZLAN)2-12
Table 2-6.Displaying Information for the WAN Subsystem ($ZZWAN)2-13
Table 2-7.Subsystem Objects Controlled by SCF2-13
Table 3-1.Monitoring System Components3-4
Table 3-2.Daily Tasks Checklist3-6
Table 3-3.SCF Object States3-14
Table 3-4.Status LEDs and Their Functions3-20
Table 3-5.Related Reading for Monitoring3-22
Tables
Types2-8
Table 4-1.Related Reading for Monitoring EMS Event Messages4-2
Table 6-1.Related Reading for Communications Lines and Devices6-13
Table 8-1.Service, Flash Firmware, Flash Boot Firmware, Device, and Enabled
States for the FCSA8-4
Table 8-2.Service, Device, and Enabled States for the G4SA8-6
Table 8-3.Related Reading for I/O Adapters and Modules8-8
Table 9-1.Other Files to Submit to Your Service Provider9-20
Table 9-2.Additional Processor Dump Information for Your Service Provider9-21
Table 9-3.Related Reading for Monitoring and Recovery Operations on
Processors9-22
Table 10-1.Primary and Backup Path States for Disk Drives10-9
Table 10-2.Possible Causes of Common Disk Drive Problems10-11
Table 10-3.
Table 11-1.
Common Recovery Operations for Disk Drives10-12
Common Tape Drive Problems11-7
Table 1 1-2.Related Reading for Tapes and Tape Drives11-9
Table 13-1.TMF States13-3
Table 15-1.System Load Paths in Order of Use15-7
Table 15-2.Related Reading for Starting and Stopping a System15-24
Table C-1.Related Reading for Tools and UtilitiesC-1
Table D-1.Descriptions of Number SystemsD-2
HP Integrity NonStop NS-Series Operations Guide—529869-005
xii
What’s New in This Manual
Manua l In forma tion
HP Integrity NonStop NS-Series Operations Guide
Abstract
This guide describes how to perform routine system hardware operations for HP
Integrity NonStop™ NS-series servers. These tasks include monitoring the system,
performing common operations tasks, and performing routine hardware maintenance.
This guide is written for system operators.
Product Version
N.A.
Supported Release Version Updates (RVUs)
This guide supports H06.08 and all subsequent H-series RVUs until otherwise
indicated by its replacement publication.
This manual has b een up dated to i nclude refer ences t o HP In tegr ity NonStop NS14000
and NS1000 servers containing VIO enclosures (in place of an IOAM enclosure).
HP Integrity NonStop NS-Series Operations Guide—529869-005
xiii
What’s New in This Manual
New and Changed Information
HP Integrity NonStop NS-Series Operations Guide—529869-005
xiv
About This Guide
This guide describes how to perform routine system hardware operations for HP
Integrity NonStop NS-series servers on H-series release version updates.
This guide is primarily geared toward commercial type NonStop NS-series servers
(see Differences Between Integrity NonStop NS-Series Systems on page 2-2 for high-
level architectural and hardware differences between the various commercial models).
While basic monitoring principles, such as Using OSM to Monitor the System on
page 3-7, apply to Telco as well as commercial systems, refer to the NonStop NS-Series Carrier Grade Server Manual for hardware details and service procedures
specific to Telco systems.
Note. NS-series refers to the hardware that makes up the server. H-series refers to the
software that runs on the server.
The term, NonSto p s erv er, refers to both NonStop S-series servers and Integrity NonStop
NS-series servers.
Use this guide along with the Guardian User’s Guide and the written policies and
procedures of your company regarding:
General operations
•
Security
•
System backups
•
Starting and stopping applications
•
Who Should Use This Guide
This guide is written for operators who perform system hardware operations. It
provides an overview of the routine tasks of monitoring the system and guides the
operator through the infrequent tasks of starting and stopping the system and
performing online recovery on the system.
HP Integrity NonStop NS-Series Operations Guide—529869-005
Introduction to Integrity NonStop NS-Series Operations
Determining Your System Configuration
Overview of Monitoring and Recovery
Monitoring EMS Event Messages
Processes: Monitoring and Recovery
Communications Subsystems: Monitoring and Recovery
ServerNet Resources: Monitoring and Recovery
I/O Adapters and Modules: Monitoring and Recovery
Processors and Components: Monitoring and Recovery
Disk Drives: Monitoring and Recovery
Tape Drives: Monitoring and Recovery
Printers and Terminals: Monitoring and Recovery
Applications: Monitoring and Recovery
Power Failures: Preparation and Recovery
Section 1 5
Section 1 6
Section 1 7
Appendix A
Appendix B
Appendix C
Appendix D
Starting and Stopping the System
Creating Startup and Shutdown Files
Preventive Maintenance
Operational Differences Between Systems Running G-Series and
H-Series RVUs
Tools and Utilities for Operations
Related Reading
Converting Numbers
HP Integrity NonStop NS-Series Operations Guide—529869-005
xvi
About This Guide
Where to Get More Information
Operations planning and operations management practices appear in these manuals:
NonStop NSxxxx Planning Guide for your NS16000, NS14000, or NS1000 server
•
Availability Guide for Application Design
•
Availability Guide for Change Management
•
Availability Guide for Problem Management
•
Note. For manuals not available in the H-series collection, please refer to the G-series
collection on NTL.
For comprehensive information about performing operations tasks for an Integrity
NonStop NS-series server, you need both this guide and the Guardian User’s Guide.
The Guardian User’s Guide describes some tasks not covered in this guide, such as
supporting users of the system.
The Guardian User’s Guide describes routine tasks common to system operations on
all NonStop servers. Instructions and examples show how to support users of the
system, how to monitor operator messages, how to control the spooler, and how to
manage disks and tapes. Numerous tools that support these functions are also
documented. Some monitoring procedures in the Guardian User’s Guide have
information about using only the Subsystem Control Facility (SCF). That guide does
not generally describe any monitoring procedures using the OSM packages.
Where to Get More Info rma tion
Information about the use of OSM, such as how to migrate from TSM to OSM, how to
install and configure OSM server and client components, and how to use the OSM
Service Connection, appear in these manuals:
OSM Migration and Configuration Guide
•
NonStop System Console Installer Guide
•
OSM Service Connection User’s Guide (available in NTL and as online help within
•
the OSM Service Connection)
Servers that are connected in ServerNet clusters require special installation and
operating procedures that are not documented in this manual. Such information is
instead provided with the appropriate cluster documentation and the ServerNet Cluster Supplement for Integrity NonStop NS-Series Servers.
In the 6780 ServerNet cluster environment, installation and operating procedures are
documented in these manuals:
ServerNet Cluster 6780 Planning and Installation Guide
•
ServerNet Cluster 6780 Operations Guide
•
Installation and operating procedures for earlier server clusters (those using 6770
switches) are documented in:
ServerNet Cluster Manual
•
HP Integrity NonStop NS-Series Operations Guide—529869-005
xvii
About This Guide
OSM is the required system management tool for servers that use 6780 switches in
ServerNet clusters, but OSM also provides system management for earlier versions of
ServerNet clusters.
For other documentation related to operations tasks, refer to Appendix C, Related
Reading.
Support and Service Library
These NTL Support and Service library categories provide procedures, part numbers,
troubleshooting tips, and tools for servicing NonStop S-series and Integrity NonStop
NS-series systems:
Hardware Service and Maintenance Publications
•
Service Information
•
Service Procedures
•
Tools and Download Files
•
Troubleshooting Tips
•
Support and Service Library
Within these categories, where applicable, content might be further categorized
according to server or enclosure type.
Authorized service providers can also order the NTL Support and Service Library CD:
Channel Partners and Authorized Service Providers: Order the CD from the SDRC
•
at https://scout.nonstop.compaq.com/SDRC/ce.htm.
HP employees: Subscribe at World on a Workbench (WOW). Subscribers
•
automatically receive CD updates. Access the WOW order form at
http://hps.knowledgemanagement.hp.com/wow/order.asp.
Notation Conventions
Hypertext Links
Blue underline is used to indicate a hypertext link within text. By clicking a passage of
text with a blue underline, you are taken to the location described. For example:
This requirement is described under Backup DAM Volumes and Physical Disk
Drives on page 3-2.
General Sy ntax Notation
The following list summarizes the notation conventions for syntax presentation in this
manual.
HP Integrity NonStop NS-Series Operations Guide—529869-005
xviii
About This Guide
General Syntax Notation
UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter
these items exactly as shown. Items not enclosed in brackets are required. For
example:
MAXATTACH
lowercase italic letters. Lowercase italic letters indicate variable items that you supply.
Items not enclosed in brackets are required. For example:
file-name
computer type. Computer type letters within text indicate C and Open System Services
(OSS) keywords and reserved words; enter these items exactly as shown. Items not
enclosed in brackets are required. For example:
myfile.c
italic computer type. Italic computer type letters within text indicate C and Open
System Services (OSS) variable items that you supply. Items not enclosed in brackets
are required. For example:
pathname
[ ] Brackets. Brackets enclose optional syntax items. For example:
TERM [\system-name.]$terminal-name
INT[ERRUPTS]
A group of items enclosed in brackets is a list from which you can choose one item or
none. The items in the list may be arranged either vertically, with aligned brackets on
each side of the list, or horizontally, enclosed in a pair of brackets and separated by
vertical lines. For example:
FC [ num ]
[ -num ]
[ text ]
K [ X | D ] address
{ } Braces. A group of items enclosed in braces is a list from which you are required to
choose one item. The items in the list may be arranged either vertically, with aligned
braces on each side of the list, or horizontally, enclosed in a pair of braces and
separated by vertical lines. For example:
LISTOPENS PROCESS { $appl-mgr-name }
{ $process-name }
ALLOWSU { ON | OFF }
| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in
brackets or braces. For example:
INSPECT { OFF | ON | SAVEABEND }
HP Integrity NonStop NS-Series Operations Guide—529869-005
xix
About This Guide
Notation for Messages
… Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you
can repeat the enclosed sequence of syntax items any number of times. For example:
M address [ , new-value ]…
[ - ] {0|1|2|3|4|5|6|7|8|9}…
An ellipsis imme diately fol lowing a single syntax item indi cates that you can repeat that
syntax item any number of times. For example:
"s-char…"
Punctuation. Parentheses, commas, semicolons, and other symbols not previously
described must be entered as shown. For example:
error := NEXTFILENAME ( file-name ) ;
LISTOPENS SU $process-name.#su-name
Quotation marks around a symbol such as a bracket or brace indicate the symbol is a
required character that you must enter as shown. For example:
"[" repetition-constant-list "]"
Item Spacing. Spaces shown between items are required unless one of the items is a
punctuation symbol such as a parenthesis or a comma. For example:
CALL STEPMOM ( process-id ) ;
If there is no space between two items, spaces are not permitted. In the following
example, there are no spaces permitted between the period and any other items:
$process-name.#su-name
Line Spacing. If the syntax of a command is too long to fit on a single line, each
continuation line is indented three spaces and is separated from the preceding line by
a blank line. This spacing distinguishes items in a continuation line from items in a
vertical list of selections. For example:
ALTER [ / OUT file-spec / ] LINE
[ , attribute-spec ]…
Notation for Messages
The following list summarizes the notation conventions for the presentation of
displayed messages in this manual.
Bold Text. Bold text in an example indicates user input entered at the terminal. For
example:
ENTER RUN CODE
?123
CODE RECEIVED: 123.00
HP Integrity NonStop NS-Series Operations Guide—529869-005
xx
About This Guide
Notation for Messages
The user must press the Return key after typing the input.
Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or
[ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For
example:
Event number = number [ Subject = first-subject-value ]
A group of items enclosed in brackets is a list of all possible items that can be
displayed, of which one or none might actually be displayed. The items in the list might
be arranged either vertically, with aligned brackets on each side of the list, or
horizontally, enclosed in a pair of brackets and separated by vertical lines. For
example:
proc-name trapped [ in SQL | in SQL file system ]
{ } Braces. A group of items enclosed in braces is a list of all possible items that can be
displayed, of which one is actually displayed. The items in the list might be arranged
either vertically, with aligned braces on each side of the list, or horizontally, enclosed in
a pair of braces and separated by vertical lines. For example:
obj-typeobj-name state changed to state, caused by
{ Object | Operator | Service }
process-name State changed from old-objstate to objstate
{ Operator Request. }
{ Unknown. }
| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in
brackets or braces. For example:
Transfer status: { OK | Failed }
% Percent Sign. A percent sign precedes a number that is not in decimal notation. The
% notation precedes an octal number. The %B notation precedes a binary number.
The %H notation precedes a hexadecimal number. For example:
%005400
%B101111
%H2F
P=%p-register E=%e-register
HP Integrity NonStop NS-Series Operations Guide—529869-005
xxi
About This Guide
Change Bar Notation
Change bars are used to indicate substantive differences between this edition of the
manual and the preceding edition. Change bars are vertical rules placed in the right
margin of changed portions of text, figures, tables, examples, and so on. Change bars
highlight new or revised information. For example:
The message types specified in the REPORT clause are different in the COBOL85
environment and the Common Run-Time Environment (CRE).
The CRE has many new message types and some new message type codes for
old message types. In the CR E, the messa ge type S Y STEM incl udes all me ssages
except LOGICAL-CLOSE and LOGICAL-OPEN.
Change Bar Notation
HP Integrity NonStop NS-Series Operations Guide—529869-005
xxii
1
Introduction to Integrity NonStop
NS-Series Operations
When to Use This Section on page 1-2
Understanding the Operational Environment on page 1-2
What Are the Operator Tasks? on page 1-2
Monitoring the System and Performing Recovery Operations on page 1-2
Preparing for and Recovering from Power Failures on page 1-3
Stopping and Powering Off the System on page 1-3
Powering On and Starting the System on page 1-3
Performing Preventive Maintenance on page 1-3
Operating Disk Drives and Tape Drives on page 1-3
Responding to Spooler Problems on page 1-4
Updating Firmware on page 1-4
Determining the Cause of a Problem: A Systematic Approach on page 1-4
A Problem-Solving Worksh eet on page 1-4
Task 1: Get the Facts on page 1-6
Task 2: Find and Eliminate the Cause of the Problem on page 1-7
Task 3: Escalate the Problem If Necessary on page 1-8
Task 4: Prevent Future Problems
Logging On to an Integrity NonStop Server on page 1-9
System Consoles
Opening a TACL Window on page 1-10
Overview of OSM Applications on page 1-11
Launching OSM Applications on page 1-11
Service Procedures on page 1-12
on page 1-9
on page 1-9
Support and Service Library on page1-12
HP Integrity NonStop NS-Series Operations Guide—529869-005
1-1
Introduction to Integrity NonStop NS-Series
Operations
When to Use This Section
When to Use This Section
This section introduces system hardware operations for Integrity NonStop NS-series
servers. It provides an introduction to the other sections in this guide.
Understanding the Operational Environment
To understand the operational environment:
If you are already familiar with other NonStop systems, see Appendix A,
•
Operational Differences Between Systems Running G-Series and H-Series RVUs.
For a brief introduction to the system organization and the location of system
•
components in an Integrity NonStop server, see Section 2, Determining Your
System Configuration.
For information about various software tools and utilities you can use to perform
•
system operations on an Integrity NonStop server, see Appendix B, Tools and
Utilities for Operations.
What Are the Operator Tasks?
The system operations described in this guide include:
Monitoring the system and performing recovery operations
•
Preparing for and recovering from power failures
•
Stopping and powering off the system
•
Powering on and starting the system
•
Performing preventive maintenance
•
Operating disk drives and tape drives
•
Responding to spooler problems
•
Monitoring the System and Performing Recovery Operation s
Checking for indications of potential system problems by monitoring the system is part
of the normal system operations routine. You perform recovery operations to restore a
malfunctioning system component to normal use. Most recovery procedures for
Integrity NonStop servers can be performed online. Monitoring the status of all system
components and performing recovery operations are described in:
Section 3, Overview of Monitoring and Recovery
•
Section 4, Monitoring EMS Event Messages
•
Section 5, Processes: Monitoring and Recovery
•
Section 6, Communications Subsystems: Monitoring and Recovery
•
Section 7, ServerNet Resources: Monitoring and Recovery
•
Section 8, I/O Adapters and Modules: Monitoring and Recovery
•
Section 9, Processors and Components: Monitoring and Recovery
•
HP Integrity NonStop NS-Series Operations Guide—529869-005
1-2
Introduction to Integrity NonStop NS-Series
Operations
Section 10, Disk Drives: Monitoring and Recovery
•
Section 11, Tape Drives: Monitoring and Recovery
•
Section 12, Printers and Terminals: Monitoring and Recovery
•
Section 13, Applications: Monitoring and Recovery
•
Recovery operations for a system conso le are not discu ssed in th is guide. For recove ry
procedures for a system console and the applications installed on the system console,
see the NonStop NSxxxx Hardware Installation Manual for your Integrity NonStop
NS16000, NS14000, or NS1000 server.
Preparing for and Recovering from Power Failures
Preparing for and Recovering from Power Failures
You can minimize unplanned outage time by having procedures to prepare and
recover quickly from power failures, as described in Section 14, Power Failures:
Preparation and Recovery.
Stopping and Powering Off the System
HP recommends a specific set of procedures for stopping and powering off an Integrity
NonStop server or its components, as described in Section 15, Starting and Stopping
the System.
Powering On and Starting the System
HP recommends a specific set of procedures for powering on and starting an Integrity
NonStop server or its components, as described in Section 15, Starting and Stopping
the System.
Creating St a r tup and Shutdown Files
HP recommends a specifi c set of pr ocedur es for creati ng st ar tup and shut down fil es on
an Integrity NonStop server or its components, as described in Section 16, Creating
Startup and Shutdown Files.
Performing Preventive Maintenance
Routine preventive maintenance consists of:
Dusting or cleaning enclosures as needed
•
Cleaning tape drives regularly
•
Evaluating tape condition regularly
•
Cleaning and reverifying tapes as needed
•
Routine hardware maintenance procedures are described in Section 17, Preventive
Maintenance.
Operating Disk Drives and Tape Drives
Refer to the documentation shipped with the drive.
HP Integrity NonStop NS-Series Operations Guide—529869-005
1-3
Introduction to Integrity NonStop NS-Series
Operations
Responding to Spooler Problems
Responding to Spooler Problems
Refer to the Spooler Utilities Reference Manual.
Updating Firmwa r e
Refer to the H06.xx Software Installation and Upgrade Guide
Determining the Cause of a Problem:
A Systematic Approach
Continuous availability of your NonStop system is important to system users, and your
problem-solving processes can help make such availability a reality. To determine the
cause of a problem on your system, start by trying the easiest, least expensive
possibilities. Move to more complex, expensive possibilities only if the easier solutions
fail.
This subsection presents an approach you can use in your operations environment to:
Determine the possible causes of problems
•
Systematically fix or escalate such problems
•
Develop ways of preventing the same problems from recurring
•
The four basic steps in systematic problem solving are:
TaskPage
Task 1: Get the Facts
Task 2: Find and Eliminate th e C ause of the Problem1-7
Task 3: Escalate the Problem If Necessary1-8
Task 4: Prevent Future Problems1-9
A Problem-Solving Worksheet
Table 1-1 is a worksheet that you can use to help you through the problem-solving
process. Use this worksheet to:
Get the facts about a problem
•
Find and eliminate the cause of the problem
•
Make any appropriate escalation decisions
•
Prevent future problems
•
1-6
Make copies of this worksheet and use it to collect and analyze facts regarding a
problem you are experiencing. The results might not tell you exactly what is occurring,
but they will narrow down the number of possible causes.
You are authorized by HP to reproduce this worksheet only for the purpose of
operating your system.
HP Integrity NonStop NS-Series Operations Guide—529869-005
1-4
Introduction to Integrity NonStop NS-Series
Operations
Table 1-1. Problem-Solving Worksheet
Problem FactsPossible Causes
What?
Where?
A Problem-Solving Worksheet
When?
Magnitude?
Situ ation FactsEscalation Decision
Plan to Verify/Fix
Plan to Prevent and Control
Damage
HP Integrity NonStop NS-Series Operations Guide—529869-005
1-5
Introduction to Integrity NonStop NS-Series
Operations
Task 1: Get the Facts
The first step in solving any problem is to get the facts. Although it is tempting to
speculate about causes, your time is better spent in first understanding the symptoms
of the problem.
Task 1a: Determine the Facts About the Problem
To get a clear, complete description of problem symptoms, ask questions to determine
the facts about the problem. For example:
CategoryQuesti ons to Ask
What?What are you having trouble with?
What specifically is wrong?
Where?Where did you first notice the problem?
Where has it occurred since you first noticed it?
Which ap plic ations, components, de v ic es , and people ar e affec t ed?
When?When did the problem occur?
What is the frequency of the problem?
Has this problem occurred before this time?
Task 1: Get the Facts
Magnitude?Is the problem quantifiable in any way? (That is, can it be measured?) For
example , h ow m any people are affected? Is this problem getting wors e?
Task 1b: Determine the Facts About the Situation
Collect facts about the situation in which the problem arose. A clear description of the
situation that led to the problem could indicate a simple solution. Examples of
questions to ask are:
Who reported the problem and how can this person be contacted?
•
How critical is the situation?
•
What events led to the problem?
•
Has anything changed recently that might have caused the problem?
•
What event messages have you received?
•
What is the current configuration of the hardware and software products affected?
•
An example of information you might obtain from asking questions:
QuestionAnswer
What is happening that
indicates a problem?
Where is this problem
occurring?
A terminal is h ung.
In the office of USER.BONNIE. The affected terminal is
named $JT1.#C02.
When is this problem occurring?At 8:30 this morning and also at the same time two days
ago. Both times, this problem occurred after three
unsuccessful attempts to log on.
What is the magnitude of this
problem?
HP Integrity NonStop NS-Series Operations Guide—529869-005
Intermittent; the problem seemed t o disappear on its own
when it first occurred two days ago.
1-6
Loading...
+ 236 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.