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.
Document History Part Number Product Version 529869-001 N.A.
HP Integrity NonStop NS-Series Operations Guide Index Examples What’s New in This Manual xiii Manual Information xiii New and Changed Information Figures Tables xiii About This Guide xv Who Should Use This Guide xv What Is in This Guide xvi Where to Get More Information xvii Notation Conventions xviii 1.
1. Introduction to Integrity NonStop NS-Series Operations (continued) Contents 1. Introduction to Integrity NonStop NS-Series Operations (continued) Overview of OSM Applications 1-12 Launching OSM Applications 1-12 Service Procedures 1-13 CSSI Web 1-13 2.
4. Monitoring EMS Event Messages Contents 4. Monitoring EMS Event Messages When to Use This Section 4-1 What Is the Event Management Service (EMS)? Tools for Monitoring EMS Event Messages 4-1 OSM Event Viewer 4-2 EMSDIST 4-2 ViewPoint 4-2 Web ViewPoint 4-2 Related Reading 4-2 4-1 5.
Contents 7. ServerNet Resources: Monitoring and Recovery 7. ServerNet Resources: Monitoring and Recovery When to Use This Section 7-1 ServerNet Communications Network 7-1 System I/O ServerNet Connections 7-3 Monitoring the Status of the ServerNet Fabrics 7-3 Monitoring the ServerNet Fabrics Using OSM 7-4 Monitoring the ServerNet Fabrics Using SCF 7-4 Related Reading 7-8 8.
Contents 9. Processors and Components: Monitoring and Recovery (continued) 9. Processors and Components: Monitoring and Recovery (continued) Dumping a Processor to Disk 9-15 Backing Up a Processor Dump to Tape 9-19 Replacing Processor Memory 9-19 Replacing the Processor Board and Processor Entity 9-19 Submitting Information to Your Service Provider 9-19 Related Reading 9-22 10.
11. Tape Drives: Monitoring and Recovery (continued) Contents 11. Tape Drives: Monitoring and Recovery (continued) Identifying Tape Drive Problems 11-7 Recovery Operations for Tape Drives 11-8 Recovery Operations Using the OSM Service Connection Recovery Operations Using SCF 11-9 Related Reading 11-9 11-8 12.
14. Power Failures: Preparation and Recovery (continued) Contents 14. Power Failures: Preparation and Recovery (continued) Power Failure Recovery 14-4 Procedure to Recover From a Power Failure Setting System Time 14-5 Related Reading 14-5 14-5 15.
Contents 16. Creating Startup and Shutdown Files 16. Creating Startup and Shutdown Files Automating System Startup and Shutdown 16-3 Managed Configuration Services (MCS) 16-3 Startup 16-3 Shutdown 16-3 For More Information 16-3 Processes That Represent the System Console 16-4 $YMIOP.#CLCI 16-4 $YMIOP.
16. Creating Startup and Shutdown Files (continued) Contents 16. Creating Startup and Shutdown Files (continued) ATP6100 Lines Shutdown File 16-22 X.25 Lines Shutdown File 16-22 Printer Line Shutdown File 16-23 Expand-Over-IP Line Shutdown File 16-23 Direct-Connect Line Shutdown File 16-23 Spooler Shutdown File 16-24 TMF Shutdown File 16-24 17.
B. Tools and Utilities for Operations (continued) Contents B. Tools and Utilities for Operations (continued) PATHCOM B-4 PEEK B-4 RESTORE B-4 SPOOLCOM B-4 Subsystem Control Facility (SCF) B-4 HP Tandem Advanced Command Language (TACL) TMFCOM B-5 Web ViewPoint B-5 ViewPoint B-5 ViewSys B-6 B-5 C. Related Reading D.
Figures Contents Figures Figure 3-1. Figure 3-2. Figure 3-3. Figure 3-4. Figure 3-5. Figure 3-6. Figure 7-1. Figure 7-2. Figure 9-1. Figure 9-2. Figure 9-3. Figure 11-1. Figure 11-2. Figure 15-1. Figure 15-2. Figure 15-3. Figure 15-4. Figure D-1. Figure D-2. Figure D-3.
Tables (continued) Contents Tables (continued) Table 6-1. Table 8-1. Table 8-2. Table 8-3. Table 9-1. Table 9-2. Table 9-3. Table 10-1. Table 10-2. Table 10-3. Table 11-1. Table 11-2. Table 13-1. Table 15-1. Table 15-2. Table C-1. Table D-1.
What’s New in This Manual Manual Information 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.
What’s New in This Manual New and Changed Information HP Integrity NonStop NS-Series Operations Guide —529869-001 xiv
About This Guide This guide describes how to perform routine system hardware operations for Integrity NonStop NS-series servers on H-series release version updates. Integrity NonStop NS-series systems employ a unique method for achieving fault tolerance in a clustered processor environment: the modular NonStop advanced architecture (NSAA). NSAA utilizes standard Intel® Itanium® microprocessors, without cycle-by-cycle lock-stepping.
What Is in This Guide About This Guide What Is in This Guide Section or Appendix Section and Appendix Titles Section 1 Introduction to Integrity NonStop NS-Series Operations Section 2 Determining Your System Configuration 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 a
Where to Get More Information About This Guide Where to Get More Information Operations planning and operations management practices appear in these manuals: • • • • Integrity NonStop NS-Series Planning Guide 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.
CSSI Web About This Guide • ServerNet Cluster Manual 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. CSSI Web The CSSI Web provides procedures, part numbers, troubleshooting tips, and tools for servicing NonStop systems.
General Syntax Notation About This Guide 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.
Notation for Messages About This Guide An ellipsis immediately following a single syntax item indicates 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.
Notation for Messages About This Guide lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] 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.
Change Bar Notation 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).
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-4
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.
Introduction to Integrity NonStop NS-Series Operations • • • • • • • • Preparing for and Recovering from Power Failures 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 Section 10, Disk Drives: Monitoring and Recovery Section 11, Tape Drives: Monitoring and Recovery Section 12, Printers and Terminals: Monitoring and
Introduction to Integrity NonStop NS-Series Operations • Operating Disk Drives and Tape Drives 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. Responding to Spooler Problems Refer to the Spooler Utilities Reference Manual. Updating Firmware Refer to the H06.
Introduction to Integrity NonStop NS-Series Operations A Problem-Solving Worksheet 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 Make copies of this worksheet and use it to collect and analyze facts regarding a problem you are experiencing.
Introduction to Integrity NonStop NS-Series Operations A Problem-Solving Worksheet Table 1-1.
Introduction to Integrity NonStop NS-Series Operations Task 1: Get the Facts 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.
Introduction to Integrity NonStop NS-Series Operations Task 2: Find and Eliminate the Cause of the Problem Task 2: Find and Eliminate the Cause of the Problem After you collect the facts, you are ready to begin considering the possible causes of a problem. Using these facts and relying on your knowledge and experience, begin to list possible causes of the problem. Task 2a: Identify the Most Likely Cause To evaluate the possible causes of any problem, you must compare each cause with the problem symptoms.
Introduction to Integrity NonStop NS-Series Operations Task 3: Escalate the Problem If Necessary Task 2b: Fix the Most Probable Cause of the Problem For the example in the worksheet, the most likely cause of the hung terminal is a security problem. Ask yourself what would be the fastest, least expensive, safest, and surest way of verifying that this is the most probable cause of the problem. Once you have determined the most likely cause, try to fix it.
Introduction to Integrity NonStop NS-Series Operations Task 4: Prevent Future Problems Task 4: Prevent Future Problems Solving problems that occur with your system can be exciting because it is active and stimulating. Preventing problems is often less dramatic. But in the end, prevention is more productive than solving problems. The more work you do to prevent problems before they arise, the fewer problems that will arise at potentially critical times.
Introduction to Integrity NonStop NS-Series Operations Opening a TACL Window is established from the console through Internet Explorer browser sessions. For more information, see Launching OSM Applications on page 1-12. Opening a TACL Window On a system console, you must open a TACL window before you can log on to the TACL command interpreter. For information about logging on to a TACL command interpreter, see the Guardian User’s Guide. You can use any of the following methods to open a TACL window.
Introduction to Integrity NonStop NS-Series Operations Overview of OSM Applications Overview of OSM Applications HP NonStop Open System Management (OSM) applications perform a variety of functions, such as: • • • • The OSM Low-Level Link Application is primarily used for down-system support, such as Two startup event stream windows and two startup TACL windows are automatically launched on the system console configured to receive them.
Introduction to Integrity NonStop NS-Series Operations Service Procedures to make accessing these applications easier. You can also simply open a new Internet Explorer browser window and enter the URL of the system you wish to access.
Introduction to Integrity NonStop NS-Series Operations HP Integrity NonStop NS-Series Operations Guide —529869-001 1-14 CSSI Web
2 Determining Your System Configuration When to Use This Section on page 2-1 Modular Hardware Components on page 2-2 Terms Used to Describe System Hardware Components on page 2-3 Recording Your System Configuration on page 2-3 Using SCF to Determine Your System Configuration on page 2-4 SCF System Naming Conventions on page 2-4 SCF Configuration Files on page 2-5 Using SCF to Display Subsystem Configuration Information on page 2-6 Displaying SCF Configuration Information for Subsystems on page 2-9 Additiona
Determining Your System Configuration Modular Hardware Components Modular Hardware Components Hardware for Integrity NonStop systems is implemented in modules, or enclosures that are installed in modular cabinets.
Determining Your System Configuration Terms Used to Describe System Hardware Components Terms Used to Describe System Hardware Components The terms used to describe system-hardware components vary. These terms include: • • Device System resource or object Device A device can be a physical device or a logical device. A physical device is a physical component of a computer system that is used to communicate with the outside world or to acquire or store data.
Determining Your System Configuration • Using SCF to Determine Your System Configuration Using SCF to list objects and devices and to display subsystem configuration information For information on forms available that can help you record your system configuration, refer to the Integrity NonStop NS-Series Planning Guide. Using SCF to Determine Your System Configuration SCF is one of the most important tools available to you as a system operator.
Determining Your System Configuration SCF Configuration Files SCF Configuration Files Your system is delivered with a standard set of configuration files: • • • The $SYSTEM.SYSnn.CONFBASE file contains the minimal configuration required to load the system. The $SYSTEM.ZSYSCONF.CONFIG file contains a standard system configuration created by HP.
Determining Your System Configuration Using SCF to Display Subsystem Configuration Information Using SCF to Display Subsystem Configuration Information SCF enables you to display, in varying levels of detail, the configuration of objects in each subsystem supported by SCF. For example, you can use the LISTDEV command to list all the devices on your system or to list the objects within a given subsystem.
Determining Your System Configuration Using SCF to Display Subsystem Configuration Information SCF LISTDEV: Listing the Devices on Your System To obtain listings for most devices and processes that have a device type known to SCF, at a TACL prompt type: > SCF LISTDEV In the example shown in Example 2-1, the SCF LISTDEV command lists all the physical and logical devices on the system. Example 2-1.
Using SCF to Display Subsystem Configuration Information Determining Your System Configuration The columns in Example 2-1 mean: LDev The logical device number Name The logical device name PPID The primary processor number and process identification number (PIN) of the specified device BPID The backup processor number and PIN of the specified device Type The device type and subtype RSize The record size the device is configured for Pri The priority level of the I/O process Program The fully
Displaying SCF Configuration Information for Subsystems Determining Your System Configuration To display information about a particular device: > SCF LISTDEV TYPE n where n is a number for the device type. For example, if n is 3, the device type is disks. For the \MS9 system, entering LISTDEV TYPE 3 would display information for $DATA6, $DATA5, $DATA4, $DATA3, $DATA2, $DATA1, and $DATA.
Determining Your System Configuration Displaying SCF Configuration Information for Subsystems Kernel Subsystem Before using commands listed in Table 2-3, type this command to make the Kernel subsystem the default object: > SCF ASSUME PROCESS $ZZKRN Generic processes are part of the SCF Kernel subsystem. Generic processes can be created by the operating system or by a user.
Determining Your System Configuration Displaying SCF Configuration Information for Subsystems When displaying configuration files for disk and tape devices in the storage subsystem, you can use the OBEYFORM option with the INFO command to display currently defined attribute values in the format that you would use to set up a configuration file. Each attribute appears as a syntactically correct configuration command.
Displaying SCF Configuration Information for Subsystems Determining Your System Configuration To get detailed configuration information in command format for all tape drives on the system, issue this command: -> INFO TAPE $*,OBEYFORM ServerNet LAN Systems Access (SLSA) Subsystem Before using commands listed in Table 2-5, type this command to make the SLSA subsystem the default object: > SCF ASSUME PROCESS $ZZLAN The SLSA subsystem provides access to parallel LAN and WAN I/O for Integrity NonStop servers.
Additional Subsystems Controlled by SCF Determining Your System Configuration Examples of the INFO command used with the OBEYFORM option are: -> INFO ADAPTER $*, OBEYFORM -> INFO LIF $*, OBEYFORM WAN Subsystem Before using commands listed in Table 2-6, type this command to make the wide area network (WAN) subsystem the default object: > SCF ASSUME PROCESS $ZZWAN The WAN subsystem has responsibility for all WAN connections. Table 2-6.
Determining Your System Configuration Additional Subsystems Controlled by SCF Table 2-7.
Displaying Configuration Information—SCF Examples Determining Your System Configuration Displaying Configuration Information—SCF Examples These examples show SCF commands that display subsystem configuration information, along with the information that is returned. These commands are not preceded by an ASSUME command. To display all the processes running in the Kernel subsystem: -> INFO PROC $ZZKRN.#* The system displays a listing similar to that shown in Example 2-3: Example 2-3.
Displaying Configuration Information—SCF Examples Determining Your System Configuration To display configuration attribute values for all the WAN subsystem configuration managers, TCP/IP processes, and WANBoot processes: -> INFO PROCESS $ZZWAN.* The system displays a listing similar to that shown in Example 2-5: Example 2-5. SCF INFO PROCESS $ZZWAN Command Output -> INFO PROCESS $ZZWAN.* WAN MANAGER Detailed Info Process \DRP09.$ZZWAN.#ZTXAE RecSize........... Preferred Cpu..... HOSTIP Address....
3 Overview of Monitoring and Recovery When to Use This Section on page 3-1 Functions of Monitoring on page 3-2 Monitoring Tasks on page 3-2 Working With a Daily Checklist on page 3-2 Tools for Checking the Status of System Hardware on page 3-3 Additional Monitoring Tasks on page 3-6 Monitoring and Resolving Problems—An Approach on page 3-7 Using OSM to Monitor the System on page 3-7 Using the OSM Service Connection on page 3-7 Recovery Operations for Problems Detected by OSM on page 3-12 Monitoring Problem
Overview of Monitoring and Recovery Functions of Monitoring Functions of Monitoring You must monitor a system to ensure that it is operating properly and to recognize when corrective action is required.
Overview of Monitoring and Recovery Tools for Checking the Status of System Hardware An example of a checklist you might use to standardize your routine daily monitoring tasks is: Task Operator’s name Date & time Notes and questions Check phone messages Check faxes Check e-mail Check shift log Check EMS event messages Check status of terminals Check comm.
Tools for Checking the Status of System Hardware Overview of Monitoring and Recovery Table 3-1. Monitoring System Components (page 1 of 3) Resource Monitored Using These Tools See...
Tools for Checking the Status of System Hardware Overview of Monitoring and Recovery Table 3-1. Monitoring System Components (page 2 of 3) Monitored Using These Tools See...
Additional Monitoring Tasks Overview of Monitoring and Recovery Table 3-1. Monitoring System Components (page 3 of 3) Resource Monitored Using These Tools See...
Overview of Monitoring and Recovery Monitoring and Resolving Problems—An Approach Monitoring and Resolving Problems—An Approach A useful approach to identifying and resolving problems in your system is to first use OSM to locate the focal point of a hardware problem and then use SCF to gather all the related data from the subsystems that control or act on the hardware.
Overview of Monitoring and Recovery Using the OSM Service Connection Figure 3-1. OSM Management: System Icons Indicate Problems Within VST310.vsd Note. In the OSM Service Connection Management window, the tree pane is located on the far left. In the lower right is the Overview pane. Located between them is the details pane, from which you can choose to view the Attributes or Alarms tab.
Overview of Monitoring and Recovery Using the OSM Service Connection 3. Click to select the alarm, then right-click and select Details. Figure 3-2. Expanding the Tree Pane to Locate the Source of Problems VST311.vsd Check the Attributes tab (Figure 3-3) also, as a yellow or red triangular symbol indicates problem attribute values exist. In this case, the degraded Service State attribute was caused by an alarm.
Overview of Monitoring and Recovery Using the OSM Service Connection Figure 3-3. Attributes Tab VST312.vsd Using System Status Icons to Monitor Multiple Systems When you are monitoring multiple systems, you can create a System Status Icon for each system, allowing you to keep a high-level eye on each system while saving screen space. Figure 3-4 shows three separate System Status icons, each created by: 1. Establishing an OSM Service Connection session to the system. 2.
Overview of Monitoring and Recovery Using the OSM Service Connection Using Alarm and Problem Summaries Other options for monitoring your system with the OSM Service Connection include using the Alarm Summary (Figure 3-5) or Problem Summary (Figure 3-6) dialog boxes to quickly view all alarms and problem conditions that exist on your system. Figure 3-5. Alarm Summary Dialog Box VST314.vsd Figure 3-6. Problem Summary Dialog Box VST315.
Overview of Monitoring and Recovery Recovery Operations for Problems Detected by OSM Suppressing Problems and Alarms In certain cases, you might want to acknowledge or suppress a particular problem, to stop it from propagating a known problem all the way up to the system level. That way, it will be easier to identify other problems that might occur.
Determining Device States Overview of Monitoring and Recovery Determining Device States This subsection explains how to determine the state of devices on your system. For example, to monitor the current state of all tape devices on your system, at an SCF prompt: -> STATUS TAPE $* Example 3-1 shows the results of the SCF STATUS TAPE $* command: Example 3-1. SCF STATUS TAPE Command 1-> STATUS TAPE $* STORAGE - Status TAPE \COMM.
Determining Device States Overview of Monitoring and Recovery The general format of the STATUS display follows. However, the format varies depending on the subsystem.
Determining Device States Overview of Monitoring and Recovery Table 3-3. SCF Object States (page 2 of 2) State Substate Explanation SERVICING SPECIAL The object is being serviced or used by a privileged process and is inaccessible to user processes. TEST The object is reserved for exclusive testing. STARTED The object is logically accessible to user processes. STARTING The object is being initialized and is in transition to the STARTED state.
Overview of Monitoring and Recovery Automating Routine System Monitoring Automating Routine System Monitoring You can automate many of the monitoring procedures. Automation saves you time and helps you to perform many routine tasks more efficiently. Your operations environment might be using TACL macros, TACL routines, or command files to perform routine system monitoring and other tasks.
Automating Routine System Monitoring Overview of Monitoring and Recovery Example 3-3. System Monitoring Output File (page 1 of 3) COMMENT THIS IS THE FILE SYSCHK COMMENT THIS CHECKS ALL DISKS: SCF STATUS DISK $* STORAGE - Status DISK \SHARK.$DATA12 LDev Primary Backup Mirror 52 *STARTED STARTED *STARTED STORAGE - Status DISK \SHARK.$DATA01 LDev Primary Backup Mirror 63 *STARTED STARTED *STARTED STORAGE - Status DISK \SHARK.
Automating Routine System Monitoring Overview of Monitoring and Recovery Example 3-3. System Monitoring Output File (page 2 of 3) COMMENT THIS CHECKS ALL SACS: SCF STATUS SAC $* SLSA Status SAC Name $ZZLAN.E4SA1.0 $ZZLAN.E4SA1.1 $ZZLAN.E4SA1.2 $ZZLAN.E4SA1.3 Owner 1 0 0 1 State STARTED STARTED STARTED STARTED COMMENT THIS CHECKS ALL ADAPTERS SCF STATUS ADAPTER $* SLSA Status ADAPTER Name $ZZLAN.MIOE0 $ZZLAN.E4SA0 $ZZLAN.MIOE1 $ZZLAN.
Automating Routine System Monitoring Overview of Monitoring and Recovery Example 3-3.
Using the Status LEDs to Monitor the System Overview of Monitoring and Recovery Using the Status LEDs to Monitor the System Status LEDs on the various enclosures and system components light during certain operations, such as when the system performs a series of power-on self-tests (POSTs) when a server is first powered on. Table 3-4 lists some of the status light-emitting diodes (LEDs) and their functions. Table 3-4.
Using the Status LEDs to Monitor the System Overview of Monitoring and Recovery Table 3-4. Status LEDs and Their Functions (page 2 of 3) Location LED Name Color Function Power Middle Green Flashes when EMU is operational and performing locate. On when EMU is operational. An EMU or an enclosure fault might still exist. Off when power has just been applied to an enclosure, or when an enclosure fault exists. Enclosure Status Amber Flashes when EMU is operational and performing locate.
Related Reading Overview of Monitoring and Recovery Table 3-4. Status LEDs and Their Functions (page 3 of 3) Location LED Name Color Function LSU logic board Power-on Green Lights when power is on and adapter is available for normal operation. Service Amber Lights when a POST is in progress, board is being reset, or a fault exists. Power-on Flashing Green Lights when power is on and Blade Element is available for normal operation.
4 Monitoring EMS Event Messages When to Use This Section on page 4-1 What Is the Event Management Service (EMS)? on page 4-1 Tools for Monitoring EMS Event Messages on page 4-1 OSM Event Viewer on page 4-2 OSM Event Viewer on page 4-2 ViewPoint on page 4-2 Web ViewPoint on page 4-2 Related Reading on page 4-2 When to Use This Section Use this section for a brief description of the Event Management Service (EMS) and the tools used to monitor EMS event messages.
OSM Event Viewer Monitoring EMS Event Messages OSM Event Viewer The OSM Event Viewer is a browser-based event viewer. The OSM Event Viewer allows you to retrieve and view events from any EMS formatted log files ($0, $ZLOG, or an alternate collector) for rapid assessment of operating system problems. To access the OSM Event Viewer, refer to Launching OSM Applications on page 1-12. For details on how to use the OSM Event Viewer, refer to the online help.
5 Processes: Monitoring and Recovery When to Use This Section on page 5-1 Types of Processes on page 5-1 System Processes on page 5-1 I/O Processes (IOPs) on page 5-2 Generic Processes on page 5-2 Monitoring Processes on page 5-3 Monitoring System Processes on page 3 Monitoring IOPs on page 4 Monitoring Generic Processes on page 4 Recovery Operations for Processes on page 5-6 Related Reading on page 5-7 When to Use This Section This section provides basic information about the different types of processes
Processes: Monitoring and Recovery I/O Processes (IOPs) I/O Processes (IOPs) An I/O process (IOP) is a system process that manages communications between a processor and I/O devices. IOPs are often configured as fault-tolerant process pairs, and they typically control one or more I/O devices or communications lines. Each IOP is configured in a maximum of two processors, typically a primary processor and a backup processor.
Monitoring Processes Processes: Monitoring and Recovery Monitoring Processes This subsection briefly provides examples of some of the tools available to monitor processes. For some processes, such as IOPs, monitoring is more fully discussed in other manuals. In general, use this method to monitor processes: 1. Develop a list of processes that are crucial to the operation of your system. 2. Determine how each of these processes is configured. 3. Use the appropriate tool to monitor the process.
Monitoring IOPs Processes: Monitoring and Recovery $ZLM01 $ZTC0 $ZTNT $ZPORT $KLA9E $ZTM02 $GRD2 $ZP02A $ZCMOM B B B B B 1,342 1,352 1,355 1,357 1,424 2,5 2,243 2,300 2,303 200 200 149 149 147 200 147 195 150 P P P P 015 011 001 001 001 017 001 001 001 255,255 255,255 255,255 255,255 255,255 255,255 255,255 255,255 255,255 $SYSTEM.SYS14.LANMON $SYSTEM.SYS14.TCPIP $SYSTEM.SYS14.TELSERV $SYSTEM.SYS14.LISTNER $DATA2.KMZTT.LOGGER $SYSTEM.SYS14.TMFMON2 $DATA2.QA9050.RUNNER $SYSTEM.ZRPC.
Monitoring Generic Processes Processes: Monitoring and Recovery This example shows the output produced by this command: 1-> STATUS PROCESS $ZZKRN.#* NONSTOP KERNEL - Status PROCESS \DRP25.$ZZKRN.
Recovery Operations for Processes Processes: Monitoring and Recovery TFDSHLP TFDSHLP TFDSHLP ZEXP ZHOME ZLOG ZZKRN ZZLAN ZZSCL ZZSMN ZZSTO ZZWAN $ZTH13 $ZTH14 $ZTH15 $ZEXP $ZHOME $ZLOG $ZZKRN $ZZLAN $ZZSCL $ZZSMN $ZZSTO $ZZWAN STOPPED STOPPED STOPPED STARTED STARTED STARTED STARTED STARTED STARTED STARTED STARTED STARTED None None None 0 ,13 0 ,289 0 ,308 0 ,293 0 ,292 1 ,290 1 ,289 0 ,291 2 ,296 None None None 1 ,15 1 ,295 1 ,329 1 ,319 1 ,297 2 ,279 2 ,282 1 ,320 3 ,289 255,255 255,255 255,255 255,
Processes: Monitoring and Recovery Related Reading Related Reading For more information about generic processes and the SCF interface to the Kernel subsystem, refer to the SCF Reference Manual for the Kernel Subsystem. For more information about IOPs, refer to the WAN Subsystem Configuration and Management Manual, the SWAN Concentrator and WAN Subsystem Troubleshooting Guide, and the Expand Configuration and Management Manual.
Processes: Monitoring and Recovery HP Integrity NonStop NS-Series Operations Guide —529869-001 5 -8 Related Reading
6 Communications Subsystems: Monitoring and Recovery When to Use This Section on page 6-1 Communications Subsystems on page 6-1 Local Area Networks (LANs) and Wide Area Networks (WANs) on page 6-2 Monitoring Communications Subsystems and Their Objects on page 6-4 Monitoring the SLSA Subsystem on page 6-4 Monitoring the WAN Subsystem on page 6-6 Monitoring the NonStop TCP/IP Subsystem on page 6-9 Monitoring Line-Handler Process Status on page 6-10 Tracing a Communications Line on page 6-12 Recovery Operation
Communications Subsystems: Monitoring and Recovery Local Area Networks (LANs) and Wide Area Networks (WANs) or other communication interface options to provide data transmissions over local area networks (LANs) or wide area networks (WANs), respectively. Similarly, multiple higher-level components can use the services of a single lower-level component.
Communications Subsystems: Monitoring and Recovery • Local Area Networks (LANs) and Wide Area Networks (WANs) Physical interfaces (PIFs) Processes that use the SLSA subsystem to send and receive data on a LAN attached to an Integrity NonStop server are called LAN service providers. Two service providers—the NonStop TCP/IP and NonStop TCP/IPv6 subsystems and the Port Access Method (PAM)—are currently supported.
Communications Subsystems: Monitoring and Recovery Monitoring Communications Subsystems and Their Objects Monitoring Communications Subsystems and Their Objects Monitoring and recovery operations for communications subsystems can be complex. An error in any of the components—service providers, clients, objects, adapters, processes, and so on—can generate multiple error messages from many interdependent subsystems and processes.
Communications Subsystems: Monitoring and Recovery Monitoring the SLSA Subsystem This example shows the listing displayed when checking all adapters on $ZZLAN: > SCF STATUS ADAPTER $ZZLAN.* 1->STATUS ADAPTER $ZZLAN.* SLSA Status ADAPTER Name $ZZLAN.G11121 $ZZLAN.G11122 $ZZLAN.G11123 $ZZLAN.G11124 $ZZLAN.G11125 $ZZLAN.MIOE0 $ZZLAN.MIOE1 State STARTED STARTED STARTED STARTED STARTED STARTED STARTED 2. The SAC object corresponds directly to the hardware on an adapter.
Communications Subsystems: Monitoring and Recovery Monitoring the WAN Subsystem This example shows a listing of the status of all PIFs on $ZZLAN.G11123: > SCF STATUS PIF $ZZLAN.G11123.* ->STATUS PIF $ZZLAN.G11123.* SLSA Status PIF Name $ZZLAN.G11123.0.A $ZZLAN.G11123.0.B $ZZLAN.G11123.0.C $ZZLAN.G11123.0.D State STARTED STARTED STOPPED STARTED Trace Status ON ON OFF ON 4. The LIF provides an interface to the PIF.
Communications Subsystems: Monitoring and Recovery Monitoring the WAN Subsystem The system displays a listing similar to: -> status adapter $zzwan.#s01 WAN Manager STATUS ADAPTER for ADAPTER State........... STARTED \TAHITI.$ZZWAN.#S01 Number of clips. 3 Clip 1 status : CONFIGURED Clip 2 status : CONFIGURED Clip 3 status : CONFIGURED To display the status for all SWAN concentrators configured for your system: > SCF STATUS ADAPTER $ZZWAN.
Communications Subsystems: Monitoring and Recovery Monitoring the WAN Subsystem Monitoring WAN Processes To display the status of all WAN subsystem processes—configuration managers, TCP/IP processes, WANBoot processes: > SCF STATUS PROCESS $ZZWAN.* The system displays a listing similar to: -> STATUS PROCESS $ZZWAN.* WAN Manager STATUS PROCESS for PROCESS State :......... STARTED LDEV Number..... 66 PPIN............ 5 ,264 WAN Manager STATUS PROCESS for PROCESS State :......... STARTED LDEV Number.....
Communications Subsystems: Monitoring and Recovery 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: -> 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 Line...
Communications Subsystems: Monitoring and Recovery Monitoring Line-Handler Process Status Monitoring NonStop TCP/IP Routes To display status information for all NonStop TCP/IP routes: > SCF STATUS ROUTE $ZTCO.* The system displays a listing similar to: 1-> Status Route $ZTCO.* TCPIP Status ROUTE \SYSA.$ZTCO.
Communications Subsystems: Monitoring and Recovery Monitoring Line-Handler Process Status This listing shows that the Expand line-handler process being monitored is up and functioning normally.
Communications Subsystems: Monitoring and Recovery Tracing a Communications Line The system displays a listing similar to this output.
Communications Subsystems: Monitoring and Recovery Recovery Operations for Communications Subsystems Recovery Operations for Communications Subsystems Some general troubleshooting guidelines are: • • Examine the contents of the event message log for the subsystem. For example, the WAN subsystem or Kernel subsystem might have issued an event message that provides information about the process failure.
Communications Subsystems: Monitoring and Recovery Related Reading Table 6-1. Related Reading for Communications Lines and Devices (page 2 of 2) For Information About... Refer to...
7 ServerNet Resources: Monitoring and Recovery When to Use This Section on page 7-1 ServerNet Communications Network on page 7-1 System I/O ServerNet Connections on page 7-3 Monitoring the Status of the ServerNet Fabrics on page 7-3 Monitoring the ServerNet Fabrics Using OSM on page 7-4 Monitoring the ServerNet Fabrics Using SCF on page 7-4 Related Reading on page 7-8 When to Use This Section Use this section to learn about monitoring and performing recovery operations for the internal and external ServerN
ServerNet Resources: Monitoring and Recovery ServerNet Communications Network simultaneously to improve performance, and to ensure that no single failure disrupts communications among the remaining system components. A ServerNet adapter provides the interface between a ServerNet fabric and the Fibre Channel and Ethernet links. A ServerNet adapter contains a ServerNet bus interface (SBI) and one or more ServerNet addressable controllers (SACs).
ServerNet Resources: Monitoring and Recovery System I/O ServerNet Connections System I/O ServerNet Connections ServerNet connections to the system I/O devices (storage disk and tape drive as well as Ethernet communication to networks) radiate out from the p-switches for both the X and Y ServerNet fabrics. ServerNet cables connected to the p-switch PICs in slots 10 through 13 come from the LSUs and processors.
ServerNet Resources: Monitoring and Recovery 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.
Monitoring the ServerNet Fabrics Using SCF ServerNet Resources: Monitoring and Recovery Use the SCF STATUS SERVERNET command to display current information about the ServerNet fabric.
ServerNet Resources: Monitoring and Recovery Monitoring the ServerNet Fabrics Using SCF Normal ServerNet Fabric States Normal states for a path on the ServerNet fabrics can be one of: • UP The path from the processor in the FROM row to the processor in the TO column is up. The status for all ServerNet connections between existing processors in a system should be UP. • <-DOWN (for an entire row) The processor in the FROM row is down or nonexistent.
ServerNet Resources: Monitoring and Recovery Monitoring the ServerNet Fabrics Using SCF The path from the processor in the FROM row to the processor in the TO column is down because the processor in the TO column is down. For a processor that does exist on your system, this status is abnormal. UNA overrides all other states. Recovery Operations for the ServerNet Fabrics For most recovery operations, refer to the SCF Reference Manual for the Kernel Subsystem.
ServerNet Resources: Monitoring and Recovery Related Reading Related Reading For more information about the interconnections between Integrity NonStop systems and S-series systems, see the Integrity NonStop NS-Series Planning Guide. For more information about the ServerNet fabrics, see the SCF Reference Manual for the Kernel Subsystem.
8 I/O Adapters and Modules: Monitoring and Recovery When to Use This Section on page 8-1 I/O Adapters and Modules on page 8-1 Fibre Channel ServerNet Adapter (FCSA on page 8-2 Gigabit Ethernet 4-Port Adapter (G4SA) on page 8-2 Monitoring I/O Adapters and Modules on page 8-3 Monitoring the FCSAs on page 8-3 Monitoring the G4SAs on page 8-5 Recovery Operations for I/O Adapters and Modules on page 8-6 Related Reading on page 8-7 When to Use This Section Use this section for monitoring and recovery information
I/O Adapters and Modules: Monitoring and Recovery Fibre Channel ServerNet Adapter (FCSA Fibre Channel ServerNet Adapter (FCSA The FCSA provides Fibre Channel connectivity to certain external devices such as disk drives contained in a disk drive enclosure that supports fibre-channel disks and an Enterprise Storage System (ESS).
I/O Adapters and Modules: Monitoring and Recovery Monitoring I/O Adapters and Modules G4SAs are configured and managed through the Subsystem Control Facility (SCF) interface to the ServerNet LAN Systems Access (SLSA) subsystem. The SLSA subsystem is preinstalled and preconfigured and is started during the system-load sequence. For information about the SLSA subsystem, refer to the LAN Configuration and Management Manual.
I/O Adapters and Modules: Monitoring and Recovery Monitoring the FCSAs Table 8-1. Service, Flash Firmware, Flash Boot Firmware, Device, and Enabled States for the FCSA (page 2 of 2) State Description Flash Compare State: Down-rev The default version is newer than the current version. Flash Compare State: Unknown Unable to compare files. Device State: Aborting Processing is terminating. Device State: Defined State is defined by the NonStop OS. Device State: Degraded Performance is degraded.
I/O Adapters and Modules: Monitoring and Recovery Monitoring the G4SAs Monitoring the G4SAs Use the Subsystem Control Facility (SCF) or the OSM Service Connection to monitor the G4SAs. To monitor the G4SAs using OSM, refer to Using OSM to Monitor the System on page 3-7. To monitor the G4SA and its attached devices with SCF, use the SCF INFO and SCF STATUS commands. For example, to monitor G4SAs using SCF: > SCF STATUS ADAPTER $ZZLAN.
I/O Adapters and Modules: Monitoring and Recovery Recovery Operations for I/O Adapters and Modules Table 8-2. Service, Device, and Enabled States for the G4SA (page 2 of 2) State Description Device State: Starting Processing is starting up. Device State: Stopped Processing has been terminated. Device State: Stopping Processing is being terminated. Device State: Unknown Component is not responding. Device State: OK Component is accessible.
I/O Adapters and Modules: Monitoring and Recovery Related Reading Related Reading For more information about monitoring and performing recovery operations for the I/O adapters and the SLSA and Storage subsystems, see the manuals listed in Table 8-3. The appropriate manual to use depends on how your system is configured. Table 8-3. Related Reading for I/O Adapters and Modules For Information About Refer to...
I/O Adapters and Modules: Monitoring and Recovery HP Integrity NonStop NS-Series Operations Guide —529869-001 8 -8 Related Reading
9 Processors and Components: Monitoring and Recovery When to Use This Section on page 9-2 Overview of the NonStop Blade Complex on page 9-2 Monitoring and Maintaining Processors on page 9-4 Monitoring Processor Status Using the OSM Low-Level Link on page 9-5 Monitoring Processor Status Using the OSM Service Connection on page 9-5 Monitoring Processor Performance Using ViewSys on page 9-7 Identifying Processor Problems on page 9-7 Processor or System Hangs on page 9-7 Processor Halts on page 9-8 OSM Alarms a
Processors and Components: Monitoring and Recovery When to Use This Section When to Use This Section Use this section to monitor processors and to perform recovery operations such as processor dumps. Overview of the NonStop Blade Complex The basic building block of the modular NonStop advanced architecture (NSAA) compute engine is the NonStop Blade Complex, which consists of two or three processor modules called NonStop Blade Elements.
Processors and Components: Monitoring and Recovery Overview of the NonStop Blade Complex Figure 9-1.
Processors and Components: Monitoring and Recovery Monitoring and Maintaining Processors In summary, these terms describe the NSAA processor: Term Description Blade Complex Consists of two Blade Elements (in a duplex system) or three Blade Elements (in a triplex system) and up to four logical processors and their associated LSUs. An Integrity NonStop system includes up to four Blade Complexes.
Processors and Components: Monitoring and Recovery Monitoring Processor Status Using the OSM LowLevel Link Monitoring Processor Status Using the OSM Low-Level Link From the OSM Low-Level Link, use the Processor Status dialog box to determine if the processors are running: 1. Log on to the OSM Low-Level Link. 2. On the toolbar, click the Processor Status button. 3. The status for all processors should be “Executing NonStop OS.” (See Figure 9-2.) If not, refer to Identifying Processor Problems on page 9-7.
Processors and Components: Monitoring and Recovery Monitoring Processor Status Using the OSM Service Connection Figure 9-3. OSM Representation of Processor Complex To check processor-related components using the OSM Service Connection: 1. Expand the tree pane to check all Processor Complex objects. 2. If a Processor Complex object icon contains a yellow arrow (as illustrated in Figure 9-3), expand that complex to check its subcomponents.
Processors and Components: Monitoring and Recovery Monitoring Processor Performance Using ViewSys Monitoring Processor Performance Using ViewSys Use the ViewSys product to view system resources online and to see information on system performance. ViewSys provides information about processor activity. Using ViewSys, you can list the processors on your system and determine their status. For more information, refer to ViewSys on page B-6.
Processors and Components: Monitoring and Recovery Processor Halts Processor Halts When certain errors occur (such as when data integrity is at risk), the operating system cannot correct the problem and must halt all application and system processes running in the associated processor. The remaining running processors in the system each send a message, reporting the halted processor as down.
Processors and Components: Monitoring and Recovery Recovery Operations for Processors Recovery Operations for Processors The architecture of Integrity NonStop NS-series servers offers recovery options not available in NonStop S-series.
Processors and Components: Monitoring and Recovery Halting One or More Processors Processor Problems on page 9-7), and contact your service provider to help you determine the appropriate course of action. This section describes the various options for Dumping a Processor to Disk and Reloading a Single Processor on a Running Server that you might be directed to use.
Processors and Components: Monitoring and Recovery Reloading a Single Processor on a Running Server Using TACL RELOAD to Perform Reload Run the RELOAD utility to reload the remaining processors after the first processor in a system has been brought up, or to recover a processor that has failed. The H-series RELOAD utility allows you to omit (or exclude) a slice from the reload operation.
Processors and Components: Monitoring and Recovery Reloading a Single Processor on a Running Server cpu is the processor number, an integer from 0 through 15. cpu-cpu is two processor numbers separated by a hyphen, specifying a range of processors. In a range specification, the first processor number must be less than the second. option is one of these: NOSWITCH [PRIME|NOPRIME] fabric OMITSLICE [A|B|C] $volume [.sysnn.
Processors and Components: Monitoring and Recovery Reloading a Single Processor on a Running Server 8. Check the OutsideView window for status messages, which will report successes or errors during the load. Monitor the state of the processor you are loading until it is executing the NonStop Kernel operating system. 9. If the load fails, check the parameters and reload the processor. If the load fails again, contact your service provider.
Processors and Components: Monitoring and Recovery Recovery Operations for a System Hang 2. Select Reload from the Action list under Selection Criteria. 3. From the list of Logical Processors, select the ones you want to reload and click Add to move them to the lower list (you can select and add one at a time, or Ctrl-click to select more than one). 4. Once all the processors you want to reload (and only those you want to reload) are in the lower list, click Perform Action. 5.
Processors and Components: Monitoring and Recovery Enabling/Disabling Processor and System Freeze Enabling/Disabling Processor and System Freeze Caution. Enabling Processor Freeze and System Freeze should only be done by, or under the direction of, your service provider. When System Freeze is enabled and one freeze-enabled processor halts, all other freeze-enabled processors in the system also halt.
Processors and Components: Monitoring and Recovery Dumping a Processor to Disk For automatic dumping and reloading of halted processors, use the HP Tandem Failure Data System (TFDS). To dump automatically, TFDS must be configured on the system before the halt occurs. However, you can also bring up TFDS following a halt and use the TFDSCOM command ANALYZE CPU to obtain information about the failure.
Processors and Components: Monitoring and Recovery Dumping a Processor to Disk Before You Begin • • • You must have a second processor connected to a terminal or workstation with a running command interpreter. The processor in which the TACL command interpreter is running performs the dump. If dumpfile already exists, it must be empty. (Its end-of-file pointer, or EOF, must be zero.) You must not prime or reset the processor before performing a processor dump. To prepare for a disk dump: 1.
Processors and Components: Monitoring and Recovery Dumping a Processor to Disk SLICE sliceId is the identification of the slice from which the processor element is to be dumped. Valid values are A or B or C or ALL. Note that ALL may not be used with the parallel method of dumping. START n... is the byte address where the dump will start. The default value is 0. END n... is the byte address where the dump will stop. Using a value of -1 is the same as specifying the end of memory. The default value is -1.
Processors and Components: Monitoring and Recovery Backing Up a Processor Dump to Tape Troubleshooting and Recovery Operations for Disk Dumps If a message indicates that the dump was not successful, repeat Dumping a Processor to Disk on page 9-13 using the other ServerNet fabric.
Processors and Components: Monitoring and Recovery Submitting Information to Your Service Provider Submitting Tapes of Processor Dumps Use a separate tape for each processor dump. For each tape you submit, record: • • The notation BACKUP to indicate a disk dump that has been backed up to tape.
Processors and Components: Monitoring and Recovery Submitting Information to Your Service Provider Additional Information Required by Your Service Provider In addition to the tapes previously discussed, submit the information listed in Table 9-2 to your service provider. Table 9-2.
Processors and Components: Monitoring and Recovery Related Reading Related Reading For more information about tools used to monitor and perform recovery operations on processors, refer to the documentation listed in Table 9-3. . Table 9-3.
10 Disk Drives: Monitoring and Recovery When to Use This Section on page 10-1 Overview of Disk Drives on page 10-2 Internal SCSI Disk Drives on page 10-2 M8xxx Fibre Channel Disk Drives on page 10-3 Enterprise Storage System (ESS) Disks on page 10-3 Monitoring Disk Drives on page 10-4 Monitoring Disk Drives With OSM on page 10-4 Monitoring Disk Drives With SCF on page 10-5 Monitoring the State of Disk Drives on page 10-9 Monitoring the Use of Space on a Disk Volume on page 10-9 Monitoring the Size of Databa
Overview of Disk Drives Disk Drives: Monitoring and Recovery Overview of Disk Drives The Integrity NonStop NS-series server supports three types of disk drives: • • • Internal SCSI Disk Drives M8xxx Fibre Channel Disk Drives Enterprise Storage System (ESS) Disks Internal SCSI Disk Drives Internal SCSI disk drives are installed in NonStop S-series I/O enclosures. Part Number/ Bar Code Label Write-On Label Green Power-On LED Yellow or Amber Activity LED CDT 106.CDD These disk drives are Class-1 CRUs.
M8xxx Fibre Channel Disk Drives Disk Drives: Monitoring and Recovery M8xxx Fibre Channel Disk Drives M8xxx Fibre Channel disk drives are installed in disk drive enclosures. A single disk drive is shown: VST601.vsd Fibre Channel disk drives are field-replaceable units (FRUs). Any physical action on a FRU, including installation and replacement, must be performed only by a qualified HP service provider.
Monitoring Disk Drives Disk Drives: Monitoring and Recovery Monitoring Disk Drives For information about See Tools for monitoring status, space use, configuration, and performance of disk drives Appendix B, Tools and Utilities for Operations Displaying EMS events generated by storage devices and subsystems Section 4, Monitoring EMS Event Messages Monitoring with OSM Monitoring Disk Drives With OSM on page 10-4 Monitoring with SCF Monitoring Disk Drives With SCF on page 10-5 Monitoring Disk Drive
Monitoring Disk Drives With SCF Disk Drives: Monitoring and Recovery Monitoring Disk Drives With SCF This subsection explains how to list disk volumes and determine their status. 1. List the status of all the disk volumes on your system, issue this command from SCF: > STATUS DISK $*, SUB MAGNETIC 1-> STATUS DISK $*, SUB MAGNETIC STORAGE - Status DISK \COMM.$SYSTEM LDev Primary Backup Mirror 6 *STARTED STARTED *STARTED STORAGE - Status DISK \COMM.
Monitoring Disk Drives With SCF Disk Drives: Monitoring and Recovery 2. Get information about a disk with SCF STATUS DISK, DETAIL. For example: -> STATUS DISK $DATA09, DETAIL The output from this example shows that $DATA09 is in the STOPPED state, HARDDOWN substate. STORAGE - Detailed Status DISK \SHARK.
Monitoring Disk Drives With SCF Disk Drives: Monitoring and Recovery To display the status of all disks: -> STATUS DISK $* 1-> STATUS DISK $* STORAGE - Status DISK \COMM.$SYSTEM LDev Primary Backup Mirror 6 *STARTED STARTED *STARTED MirrorBackup STARTED Primary PID 0,257 Backup PID 1,257 Primary PID 2,288 Backup PID 3,267 STORAGE - Status VIRTUAL DISK \COMM.$VIEWPT LDev State Primary Backup Type Subtype PID PID 147 STARTED 9,22 8,53 3 36 STORAGE - Status VIRTUAL DISK \COMM.
Monitoring Disk Drives With SCF Disk Drives: Monitoring and Recovery To display the detailed status of the disk $DATA01: -> STATUS $DATA01, DETAIL STORAGE - Detailed Status DISK \SHARK.$DATA01 Disk Path Information: LDev Path PathStatus 63 63 63 63 PRIMARY BACKUP MIRROR MIRROR-BACKUP ACTIVE INACTIVE ACTIVE INACTIVE State SubState STARTED STARTED STARTED STARTED Primary PID 0,267 0,267 0,267 0,267 Backup PID 1,266 1,266 1,266 1,266 General Disk Information: Device Type........... 3 Device Subtype..
Disk Drives: Monitoring and Recovery Monitoring the State of Disk Drives Monitoring the State of Disk Drives Each disk drive can have two paths, the primary and the backup. (Each M8xxx disk drive is forced to have two paths.) The two path states are represented separately. Table 10-1. Primary and Backup Path States for Disk Drives Path State Description Degraded This path of this disk drive has a state other than Up. Down The disk volume or disk path is not logically accessible.
Disk Drives: Monitoring and Recovery Monitoring Disk Configuration and Performance $DATA.FILES.FILEA 10 Jul 1993, 14:05 ENSCRIBE TYPE U CODE 100 EXT ( 224 PAGES, 14 PAGES ) ODDUNSTR MAXEXTENTS 370 BUFFERSIZE 4096 OWNER 8,255 SECURITY (RWEP): NUNU, LICENSED DATA MODIF: 10 Jul 1994, 14:04 CREATION DATE: 10 Jan 1994, 14:04 LAST OPEN: 10 Jul 1994, 14:04 EOF 267022 (58.2% USED) FILE LABEL: 822 (20.2% USED) EXTENTS ALLOCATED: 10 This report shows that FILEA is 58.2% full.
Identifying Disk Drive Problems Disk Drives: Monitoring and Recovery Identifying Disk Drive Problems For recovery operations, refer to Recovery Operations for Disk Drives on page 10-12. Table 10-2. Possible Causes of Common Disk Drive Problems Problems Possible Symptoms Disk is full or does not have enough space. Error 43 (unable to obtain disk space for file extent) occurs. Disk free space is fragmented. If the disk is full, an application might go down. One disk in a mirrored pair is down.
Disk Drives: Monitoring and Recovery Recovery Operations for Disk Drives Recovery Operations for Disk Drives These SCF commands control DISK objects: Command Description ABORT Terminates the operation of a disk drive immediately, leaving it in the STOPPED state, HARDDOWN substate. ALTER Changes attribute values for a storage device. BYPASS Bypasses one or more disks in a Fibre Channel disk-drive enclosure. CONTROL Issues disk-specific commands.
Disk Drives: Monitoring and Recovery Recovery Operations for Disk Drives Table 10-3. Common Recovery Operations for Disk Drives (page 2 of 2) Problem Recovery Unspared defective sectors To check for unspared defective sectors with SCF: -> INFO DISK $*, BAD, SEL started, sub magnetic To check for unspared defective sectors with DSAP at a TACL prompt: > DSAP $* • • Recovery for DSAP is not needed.
Recovery Operations for a Down Disk or Down Disk Path Disk Drives: Monitoring and Recovery Recovery Operations for a Down Disk or Down Disk Path To restart a disk or disk path: 1. If a path is down due to a ServerNet fabric failure, determine the affected paths. From an SCF prompt: -> STATUS DISK $*-*, SUB MAGNETIC The output indicates: • • • $DATA06-M and $DATA06-MB are stopped in the DOWN substate. $WD8-M and $WD8-MB are stopped in the HARDOWN substate.
Disk Drives: Monitoring and Recovery Recovery Operations for a Nearly Full Database File Recovery Operations for a Nearly Full Database File When a database file is 90 percent full or more, you can modify the file extents dynamically with FUP or perform other procedures according to your system policies. Note. Allocating additional extents to any file causes that file to take up more disk space.
Disk Drives: Monitoring and Recovery HP Integrity NonStop NS-Series Operations Guide —529869-001 10 -16 Related Reading
11 Tape Drives: Monitoring and Recovery When to Use This Section on page 11-1 Overview of Tape Drives on page 11-1 Monitoring Tape Drives on page 11-2 Monitoring Tape Drive Status With OSM on page 11-2 Monitoring Tape Drive Status With SCF on page 11-5 Monitoring Tape Drive Status With MEDIACOM on page 11-6 Monitoring the Status of Labeled-Tape Operations on page 11-7 Identifying Tape Drive Problems on page 11-7 Recovery Operations for Tape Drives on page 11-8 Recovery Operations Using the OSM Service Conne
Tape Drives: Monitoring and Recovery Monitoring Tape Drives For further information, refer to the document on Integrity NonStop NS-Series Supported Hardware and the Integrity NonStop NS-Series Hardware Installation Manual. Monitoring Tape Drives This section describes the various methods of tape drives, which include: • • • OSM Service Connection SCF Use MEDIACOM to monitor the use of tape drives and to write tape labels.
Tape Drives: Monitoring and Recovery Monitoring Tape Drive Status With OSM Figure 11-1. OSM: Monitoring Tape Drives Connected to an FCSA VST316.vsd 4. If an alarm or degraded conditions exist, the tape drive probably requires either: • Operator intervention. For more information, see Recovery Operations for Tape Drives on page 11-8. • Service or replacement. Contact your service provider and refer to the CSSI Web for the replacement procedure.
Tape Drives: Monitoring and Recovery Monitoring Tape Drive Status With OSM Figure 11-2. OSM: Monitoring Tape Drives Connected to an IOMF2 VST317.vsd Note. All tape drives connected to a system appear under the Tape Collection object. When a IOMF2-connected tape drive uses storage routers, those objects appear under that tape drive object in the OSM tree pane hierarchy; however, fibre channel routers appear under the Monitored Service LAN Devices object (after being configured in OSM).
Monitoring Tape Drive Status With SCF Tape Drives: Monitoring and Recovery Monitoring Tape Drive Status With SCF To check the status of all tape drives on your system with SCF: > SCF STATUS TAPE $* A listing similar to this one is sent to your home terminal: STORAGE - Status TAPE \MINDEN.$XTAPE LDev State Primary Backup PID PID 93 STOPPED 1,287 0,279 STORAGE - Status TAPE \MINDEN.
Monitoring Tape Drive Status With MEDIACOM Tape Drives: Monitoring and Recovery Monitoring Tape Drive Status With MEDIACOM The MEDIACOM command STATUS TAPEDRIVE displays the current status of a tape drive. Among other things, this command tells you whether a tape is mounted on the drive, the name of the DEFINE associated with the tape, and which volume catalog and pool owns it. Note. Manual unloading of a tape is not detected by a tape drive, so information from STATUS TAPEDRIVE can be out of date.
Tape Drives: Monitoring and Recovery Monitoring the Status of Labeled-Tape Operations Monitoring the Status of Labeled-Tape Operations Use the MEDIACOM STATUS TAPEDRIVE and STATUS TAPEMOUNT commands to determine the current status of labeled-tape operations on your system.
Tape Drives: Monitoring and Recovery Recovery Operations for Tape Drives Recovery Operations for Tape Drives You can perform recovery operations on tape drives using either the SCF interface to the storage subsystem or the OSM Service Connection. Recovery Operations Using the OSM Service Connection If the recovery operation calls for an OSM Service Connection action, you can perform an action on one or more tape drive objects. Performing an OSM Action on a Tape Drive 1.
Recovery Operations Using SCF Tape Drives: Monitoring and Recovery Recovery Operations Using SCF These SCF commands are available for controlling TAPE objects: SCF Command Description PRIMARY Causes the backup processor of a tape drive to become the primary processor and the primary processor of the drive to become the backup processor. RESET Puts a tape drive in a state from which it can be restarted. START Initiates the operation of a tape drive.
Related Reading Tape Drives: Monitoring and Recovery Table 11-2. Related Reading for Tapes and Tape Drives (page 2 of 2) For Information About... Refer to...
12 Printers and Terminals: Monitoring and Recovery When to Use This Section on page 12-1 Overview of Printers and Terminals on page 12-1 Monitoring Printer and Collector Process Status on page 12-2 Monitoring Printer Status on page 12-2 Monitoring Collector Process Status on page 12-2 Recovery Operations for Printers and Terminals on page 12-3 Recovery Operations for a Full Collector Process on page 12-3 Related Reading on page 12-3 When to Use This Section This section provides a brief overview about moni
Monitoring Printer and Collector Process Status Printers and Terminals: Monitoring and Recovery Monitoring Printer and Collector Process Status This subsection explains how to list the printers on your system and determine their status. It also explains how to check the status of the spooler subsystem collector processes, which accept output from applications and store the output on a disk.
Printers and Terminals: Monitoring and Recovery Recovery Operations for Printers and Terminals This listing shows that the three collector processes, $S, $S1, and $S2, are active and none is approaching a full state.
Printers and Terminals: Monitoring and Recovery HP Integrity NonStop NS-Series Operations Guide —529869-001 12- 4 Related Reading
13 Applications: Monitoring and Recovery When to Use This Section on page 13-1 Monitoring TMF on page 13-1 Monitoring the Status of TMF on page 13-2 Monitoring Data Volumes on page 13-2 TMF States on page 13-3 Monitoring the Status of Pathway on page 13-4 PATHMON States on page 13-5 Related Reading on page 13-6 When to Use This Section This section explains how to monitor the status of the HP NonStop Transaction Management Facility (TMF) and Pathway transaction processing applications.
Applications: Monitoring and Recovery Monitoring the Status of TMF Monitoring the Status of TMF To monitor TMF using TMFCOM: 1. At a TACL prompt: > TMFCOM 2. At the TMFCOM prompt: ~ STATUS TMF Note. The STATUS TMF command presents status information about the audit dump, audit trail, and catalog processes. Thus, in addition to the general TMF information, the STATUS TMF command combines information from the STATUS AUDITDUMP, STATUS AUDITTRAIL, and STATUS BEGINTRANS commands.
TMF States Applications: Monitoring and Recovery For example, to check the status of all data volumes, at a TMFCOM prompt, type: ~ STATUS DATAVOLS TMFCOM responds with output similar to: Audit Recovery Volume Trail Mode State --------------------------------------------------$DATA1 MAT Online Started $DATA2 MAT Online Started $DATA3 MAT Online Recovering $DATA4 MAT Archive Recovering $DATA5 AUX01 Online Started $DATA6 AUX01 Online Started $DATA6 AUX01 Archive Recovering TMF States The TMF subsystem can b
Monitoring the Status of Pathway Applications: Monitoring and Recovery Table 13-1. TMF States (page 2 of 2) State Meaning Stopped The TMF subsystem is stopped. Stopping The TMF subsystem is stopping and is in one of these conditions: Waiting for Transactions to Finish The subsystem is waiting for all transactions to be finished. Data Volumes The subsystem is stopping data volumes. Waiting for RDF The subsystem is waiting for the Remote Duplicate Database Facility (RDF) to shut down.
PATHMON States Applications: Monitoring and Recovery PATHCOM responds with output such as: EXTERNALTCPS LINKMONS PATHCOMS SPI RUNNING 0 0 1 1 SERVERCLASSES RUNNING 13 STOPPED 5 THAWED 18 SERVERPROCESSES TCPS RUNNING 13 1 STOPPED 40 0 PENDING 0 0 TERMS RUNNING 1 STOPPED 0 PENDING 0 FROZEN 0 FREEZE PENDING 0 SUSPENDED 0 This output provides information about the number of Pathway processes and servers that are running, stopped, and so forth. 4.
Applications: Monitoring and Recovery • The WAIT column indicates whether the process is waiting, which can be caused by one of these conditions: IO The request is waiting for an I/O operation to finish. LOCK The request is waiting for an object that has been locked by another requester. PROG-DONE The request is waiting for a RUN PROGRAM to finish.
14 Power Failures: Preparation and Recovery When to Use This Section on page 14-2 System Response to Power Failures on page 14-2 NonStop NS-Series Cabinets (Modular Cabinets) on page 14-2 External Devices on page 14-2 ESS Cabinets on page 14-3 Air Conditioning on page 14-3 Preparing for Power Failure on page 14-3 Set Ride-Through Time on page 14-3 Monitor Power Supplies on page 14-3 Monitor Batteries on page 14-4 Maintain Batteries on page 14-4 Power Failure Recovery on page 14-4 Procedure to Recover From a
Power Failures: Preparation and Recovery When to Use This Section When to Use This Section Use this section for information about how to prepare for power failures and how to recover if a power failure occurs. System Response to Power Failures NonStop NS-Series Cabinets (Modular Cabinets) NonStop NS-series servers are designed to operate in a computer-room environment containing a site UPS. Without a UPS, a system will stop uncontrollably when the power is lost.
Power Failures: Preparation and Recovery ESS Cabinets During a power failure, a ServerNet/DA remains operational during the power-fail delay time, but the external modular disk and tape subsystems attached to it do not. This type of situation could result in data-integrity problems if the system software continues processing data from an external disk drive or tape drive during a short power outage.
Power Failures: Preparation and Recovery Monitor Batteries Monitor Batteries • • • Monitoring site UPS batteries is the responsibility of the customer. OSM does not interface with a site UPS or batteries. Monitoring batteries in an internal UPS and ERM is performed using OSM. Monitor batteries in I/O enclosures using OSM. For more information on battery attributes and actions, see the OSM Service Connection online help.
Power Failures: Preparation and Recovery Procedure to Recover From a Power Failure Procedure to Recover From a Power Failure After power is restored: 1. Power on the system using OSM LLL described in Powering On a System on page 15-2. 2. Log on to the OSM Service Connection and check the status of all system components to make sure they are started. 3. Use SCF commands to check the status of external devices and, if necessary, to restart any external devices to bring them back online.
Power Failures: Preparation and Recovery HP Integrity NonStop NS-Series Operations Guide —529869-001 14- 6 Related Reading
15 Starting and Stopping the System When to Use This Section on page 15-2 Powering On a System on page 15-2 Powering On the System From a Low Power State on page 15-3 Powering On the System From a No Power State on page 15-3 Starting a System on page 15-5 Loading the System on page 15-5 Starting Other System Components on page 15-8 Performing a System Load on page 15-9 Performing a System Load From a Specific Processor on page 15-11 Reloading Processors on page 15-12 Minimizing the Frequency of Planned Outa
Starting and Stopping the System When to Use This Section Recovering From a Reload Failure on page 15-21 Exiting the OSM Low-Level Link on page 15-22 Opening Startup Event Stream and Startup TACL Windows on page 15-22 Related Reading on page 15-24 When to Use This Section Normally, you leave a system running. However, some procedures or recovery actions require you to start the system (perform a system load) or stop or power off the system.
Starting and Stopping the System Powering On the System From a Low Power State Powering On the System From a Low Power State 1. Log on to the OSM Low-Level Link. 2. From the tree pane, right click the system and select actions. 3. Select Power On System. 4. If your maintenance LAN is not configured with the dynamic name service (DNS) or does not have reverse look-up, you must perform a hard reset of the maintenance entities (MEs) in each p-switch and IOAM enclosure: a.
Starting and Stopping the System • • Powering On the System From a No Power State You must power on Fibre Channel to SCSI Converter devices connected to your system before you power on the tape devices attached to it. The converter must be powered on first to be able to discover the tape devices as they are powered on. Maintenance switches installed outside of a modular cabinet must be powered on according to the instructions provided with the switch. 2.
Starting and Stopping the System Starting a System 5. If you have a UPS installed, check that the UPS is fully charged. Then, test the UPS by turning off both circuit breakers. 6. Log on to the OSM Low-Level Link. 7. Select System Discovery. 8. Double-click the System. 9. Double-click each Group 40n; for example, Group 400. 10. Check that the logical processors are displayed. 11. Double-click each Group 1nn; for example, Group 100. 12. For each Group 1nn, check that module 2 and module 3 are displayed.
Starting and Stopping the System • • Loading the System Two startup event stream windows and two startup TACL windows are automatically launched on the system console configured to receive them. The CIIN function is enabled by default. See CIIN File on page 16-6. System Load to a Specific Processor Alternately, you can perform a system load from a specified processor. When you load the system from a specified logical processor: • • • • The other logical processors are not primed automatically.
Loading the System Starting and Stopping the System IOAM • • • FCSA Disk Drive Enclosure Path Group Module Slot SAC Shelf Bay Primary 110 2 1 1 1 1 Backup 110 3 1 1 1 1 Mirror 110 3 1 2 1 1 Mirror Backup 110 2 1 2 1 1 A SCSI-Load attempts to load the system from a disk in group, module, slot 11.1.11 of a NonStop S-series I/O enclosure. A load from $SYSTEM attempts to load the system from a disk in group, module, slot 11.1.
Starting Other System Components Starting and Stopping the System Table 15-1. System Load Paths in Order of Use Data Travels 14 Mirror $SYSTEM-M 1 Y 15 Mirror backup $SYSTEM-M 1 X 16 Mirror backup $SYSTEM-M 1 Y Configuration File Normally, you select Current (CONFIG), the default system configuration file. For the system disk volume you select to load the system, CONFIG represents the system configuration database that is currently running or was last running.
Starting and Stopping the System Performing a System Load For example, you can use the SCF interface to the Kernel subsystem to add these processes to the system configuration database: ° ° $ZEXP, the Expand manager process $ZPMON, the OSS monitor process For more information about configuring generic processes to start automatically, refer to the documentation in Related Reading on page 15-24.
Starting and Stopping the System Performing a System Load Figure 15-1. System Load Dialog Box 5. From the Configuration drop-down menu under System Load Configuration, select a system load volume. You can select the $SYSTEM, FCDM-Load, SCSI-Load, or an alternate system volume. 6. In the SYSnn field, enter the number of the SYSnn subvolume. The value nn must be a two-digit octal number in the range 00 through 77. 7. In the Configuration File box, select a system configuration file.
Starting and Stopping the System Performing a System Load From a Specific Processor 11. Check for messages in these windows and dialog boxes: • • System Load dialog box The primary startup event stream window (startup event stream messages) and the primary startup TACL window (startup messages) 12. After the System Load dialog box displays the “System Startup Complete” message, close the dialog box. 13. From the Processor Status dialog box, check the status of all processors.
Starting and Stopping the System Reloading Processors 8. Click Load. 9. Check for messages in the System Load dialog box. After the “System Startup Complete” message, close the dialog box. 10. In the Processor Status dialog box, check the status of all processors. At least one processor must be running. Determine whether you need to reload any remaining processors. 11. Dump processor memory, if needed.
Starting and Stopping the System Reloading Processors To reload a multiple processors, use the Multi-Resource Actions dialog box (available from the Display menu of the OSM Service Connection): 1. In the Multi-Resource Actions dialog box, select Logical Processor from the Resource Types list. All Logical Processors in the system will be displayed in the right-hand pane. 2. Select Reload from the Action list under Selection Criteria. 3.
Starting and Stopping the System Minimizing the Frequency of Planned Outages Minimizing the Frequency of Planned Outages To minimize the frequency of planned outages: • • Anticipate and plan for change Perform changes online Anticipating and Planning for Change Anticipating and planning for change is a key requirement for maintaining an enterprise-level, 24 x 7 operation.
Starting and Stopping the System • Stopping Application, Devices, and Processes Stopping DSM/SCM stops the CNFGINFO server process, the Pathway environment for DSM/SCM, the alternate EMS collector $ZPHI, and TCP/IP processes for DSM/SCM, as this example shows: STOP CNFGINFO server process $ZPHC STOP DSM/SCM Pathway system $YPHI PATHCOM $YPHI;SHUTDOWN !,WAIT $Z02H: TCP TCP-H, STOPPED $Z02H: TCP TCP-T, STOPPED STOP DSM/SCM Alternate EMS Collector $ZPHI • • Following the SPOOLER DRAIN command, the colle
Starting and Stopping the System Stopping the System 6. Drain the spooler. The SPOOLCOM SPOOLER DRAIN command stops the spooler in an orderly manner. It is the only recommended way to stop the spooler. At a TACL prompt: > SPOOLCOM supervisor-name, SPOOLER, DRAIN 7. Stop the TMF subsystem. At the TACL prompt: > TMFCOM STOP TMF 8. Refresh the disks to put them in an orderly state before shutdown. Use the SCF CONTROL DISK, REFRESH command: > SCF CONTROL DISK $*,REFRESH 9.
Starting and Stopping the System Powering Off a System 5. From the Processors Actions menu, select Halt. 6. Click Perform action. 7. A message box asks whether you are sure you want to perform a halt on the selected processors. Click OK. Powering Off a System Use OMS or SCF to place most system components in a low-power state before you remove power to all system components. Any attached I/O enclosures power off completely.
Starting and Stopping the System Emergency Power-Off Procedure Emergency Power-Off Procedure If possible, HP recommends that the system be in a low power state before you remove power to the system. However, in emergency situations, you might need to quickly remove AC power from a system. Sites equipped with an emergency power-off (EPO) switch can use it to remove AC power from your entire system. For more information on the EPO system, see the NonStop NS-Series Planning Guide.
Starting and Stopping the System System Does Not Appear to Be Powered On System Does Not Appear to Be Powered On If AC power is being supplied to the server and the fans are turning but the server still does not appear to be powered, the server might be running internal tests. Wait several minutes (at least 10 minutes for large configurations). If the server is still not powered on after this time and you cannot determine the cause of the problem: • • Check your site’s circuit breakers.
Starting and Stopping the System Recovering From a System Load Failure Recovering From a System Load Failure If a system load is not successful or if the system halts: 1. Check for messages in the System Load dialog box of the OSM Low-Level Link. 2. Check the Processor Status dialog box of the OSM Low-Level Link for halt codes. Look up the halt codes in the Processor Halt Codes Manual for further information about the cause of failure and the appropriate recovery procedure. 3.
Starting and Stopping the System Getting a Corrupt System Configuration File Analyzed Pending changes can appear (but are misleading) if the earlier configuration has different system name, number, or time attributes than the configuration you replaced. For example, if you load the \EAST system from the CONFBASE file (which specifies \NONAME as the system name), an INFO SUBSYS $ZZKRN command displays \EAST as the current system and \NONAME as a pending change.
Exiting the OSM Low-Level Link Starting and Stopping the System Exiting the OSM Low-Level Link If all processors in the system have been halted and you are unable to log off, press Alt-F4 to exit the OSM Low-Level Link. Opening Startup Event Stream and Startup TACL Windows When you perform a normal system load, these windows open automatically. If the windows do not open or if you close them, you can reopen them using either OSM or Outside View.
Starting and Stopping the System Opening Startup Event Stream and Startup TACL Windows 1. Select Start > OutsideView > OutsideView. The OutsideView dialog box appears. 2. Select Session > New. The New Session Properties dialog box appears. 3. On the Session tab, in the Session Caption box, type a session caption name such as Startup Events or Startup TACL. 4. Click IO Properties. The TCP/IP Properties dialog box appears. 5.
Related Reading Starting and Stopping the System Related Reading For more information, refer to the documentation listed in Table 15-2. Table 15-2. Related Reading for Starting and Stopping a System For Information About Refer to Using SCF to customize your configuration SCF Reference Manual for H-Series RVUs provides an overall reference for SCF, as well as information on customizing your configuration using command files.
16 Creating Startup and Shutdown Files This section describes command files that automatically start and shut down an Integrity NonStop NS-series server. Automating System Startup and Shutdown on page 16-3 Managed Configuration Services (MCS) on page 16-3 Startup on page 16-3 Shutdown on page 16-3 For More Information on page 16-3 Processes That Represent the System Console on page 16-4 $YMIOP.#CLCI on page 16-4 $YMIOP.
Creating Startup and Shutdown Files Expand-Over-IP Line Startup File on page 16-19 Expand Direct-Connect Line Startup File on page 16-19 Tips for Shutdown Files on page 16-20 Shutdown File Examples on page 16-20 System Shutdown File on page 16-21 CP6100 Lines Shutdown File on page 16-22 ATP6100 Lines Shutdown File on page 16-22 X.
Automating System Startup and Shutdown Creating Startup and Shutdown Files Automating System Startup and Shutdown Managed Configuration Services (MCS) Integrity NonStop NS-Series servers are being configured with Managed Configuration Services (MCS) when they are installed. Functions performed by MCS include configuring the Spooler, Pathway, and Expand lines, and creating startup and shutdown files. This section is about creating startup and shutdown files without the use of MCS.
Creating Startup and Shutdown Files Processes That Represent the System Console Processes That Represent the System Console On Integrity NonStop NS-series servers, the system console is a pair of windows on a LAN-connected system console. It is represented by the processes $YMIOP.#CLCI and $YMIOP.#CNSL, and the home terminal is represented by the $ZHOME process pair. $YMIOP.#CLCI $YMIOP.#CLCI is the primary interactive terminal for the operator interface to the system.
Creating Startup and Shutdown Files ° • $ZHOME Alternative Never specify $ZHOME for the INFILE for a process. The $ZHOME process returns the FEINVALOP error (file-system error 2) in response to any read operation. Generic processes started by the $ZPM persistence manager inherit $YMIOP.#CLCI as the HOMETERM, INFILE, and OUTFILE unless these attributes are changed in the configuration record for the generic process.
Creating Startup and Shutdown Files CIIN File CIIN File The CIIN file is a TACL command (OBEY) file that contains a limited set of commands that usually: • Start a TACL process pair on the system console for the system console TACL window ($YMIOP.#CLCI) When the startup TACL executes the commands in the CIIN file and terminates, the $YMIOP.#CLCI process pair lets you log on to the system and complete the system startup. Note.
Creating Startup and Shutdown Files Establishing a CIIN File Establishing a CIIN File The CIIN file is configured at the factory as $DSMSCM.SYS.CIIN. You do not need to establish this file. DSM/SCM automatically copies the CIIN file from the initial location into each SYSnn you create. Note. The CIIN file must be owned by a member of the super-group (255,n).
If a CIIN File Is Not Specified or Enabled in OSM Creating Startup and Shutdown Files If a CIIN File Is Not Specified or Enabled in OSM The results of the startup TACL process varies depending on whether a CIIN file is specified in the CONFTEXT file and whether the CIIN option is enabled. CONFTEXT CIIN Entry and CIIN File CIIN Option 1. CONFTEXT has CIIN entry, and file is available in specified location. Enabled CIIN is executed by initial (startup) TACL process.
Creating Startup and Shutdown Files Example CIIN Files Example CIIN Files This example CIIN file does not include a persistent CLCI TACL process. Comment Comment Comment Comment ----- This is the initial command input (CIIN) file for the system. If CIIN is enabled in OSM and configured in your CONFTEXT file, the initial TACL process will read this file and then terminate. Comment -- This file is used to reload the remaining processors and Comment -- start a TACL process pair for the system console.
Creating Startup and Shutdown Files Writing Efficient Startup and Shutdown Command Files Writing Efficient Startup and Shutdown Command Files TACL and by many subsystems support command files. Command files for startup or shutdown contain a series of commands that automatically execute when the file is executed.
Creating Startup and Shutdown Files Avoid Manual Intervention Avoid Manual Intervention Write startup and shutdown files so that they execute correctly without requiring manual intervention. Any time an operator must intervene, startup and shutdown time increase and the possibility of human error increases.
Creating Startup and Shutdown Files Investigate Product-Specific Techniques Investigate Product-Specific Techniques Some products provide commands that reduce the time required to start up or shut down their services. Familiarize yourself with the products and applications that run on your system to identify time-saving techniques for speeding startup and shutdown operations. Refer to the relevant documentation for each product.
Creating Startup and Shutdown Files Startup File Examples Startup File Examples You can implement the system startup sequence with a collection of startup files, each with a specific purpose. HP recommends that you invoke the startup files in this order: 1. Startup file for the system, to be invoked after the CIIN file is invoked 2. Startup files for the system software 3. Startup files for the subsystems 4. Startup files for the communications lines 5.
Creating Startup and Shutdown Files System Startup File Comment Comment Comment Comment ----- If you have used SCF to start a persistent $ZEXP Expand manager process pair, you do not need an explicit SCP command to start $ZEXP, unless you load the system from a different CONFIG file. Comment Comment Comment Comment ----- If you have not configured $ZEXP as a persistent generic process,remove the commenting from the following SCP command and start $ZEXP as a nonpersistent process pair.
Spooler Warm-Start File Creating Startup and Shutdown Files 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.
Creating Startup and Shutdown Files TCP/IP Stack Configuration and Startup File This example shows a TACL command file that configures the TCP/IP stack on $ZZLAN.L018. ?TACL MACRO == == This file is $SYSTEM.STARTUP.IPSTK1 Adds TCPIP and related processes to $ZZLAN.L018 #FRAME #PUSH CON^NAME, LINE^NAME, TCP^NAME, LST^NAME, TEL^NAME #PUSH HOST^NAME, IP^ADDR, GW^ADDR, TCP^CPU1, TCP^CPU2 #SET IP^ADDR #SET GW^ADDR 192.231.36.099 192.231.36.
Creating Startup and Shutdown Files TCP/IP Stack Configuration and Startup File + EXIT #POP #INLINEPREFIX ] #OUTPUT #OUTPUT Starting TCP/IP: [TCP^NAME] TCPIP /NAME [TCP^NAME], TERM [CON^NAME], NOWAIT, CPU [TCP^CPU1] / [TCP^CPU2] DELETE DEFINE =TCPIP^PROCESS^NAME ADD DEFINE =TCPIP^PROCESS^NAME, FILE [TCP^NAME] PARAM TCPIP^PROCESS^NAME [TCP^NAME] PARAM ZTNT^TRANSPORT^PROCESS^NAME [TCP^NAME] #OUTPUT #OUTPUT Configuring TCP/IP...
Creating Startup and Shutdown Files CP6100 Lines Startup File CP6100 Lines Startup File This example shows an SCF command file that starts the CP6100 lines associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX). This file can be invoked automatically from the STRTSYS file, or you can invoke it by using the following TACL command: > SCF / IN $SYSTEM.STARTUP.STRTCP6, OUT $ZHOME / == This is $SYSTEM.STARTUP.
Creating Startup and Shutdown Files Printer Line Startup File Printer Line Startup File This example shows an SCF command file that starts a printer line associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX). This file can be invoked automatically from the STRTSYS file, or you can invoke it by using the following TACL command: > SCF / IN $SYSTEM.STARTUP.STRTLP, OUT $ZHOME / == This is $SYSTEM.STARTUP.
Creating Startup and Shutdown Files Tips for Shutdown Files Tips for Shutdown Files HP recommends that you specify “N” for the read access portion of the file security attribute (RWEP) for your shutdown files to allow the files to be read by any user on the network. For example, you might secure these files “NCCC.” The sequence in which you invoke shutdown files can be important. Some processes require other processes to be stopped before they can be stopped.
Creating Startup and Shutdown Files System Shutdown File System Shutdown File This example shows a TACL command file that shuts down the system software and invokes other shutdown files. The local operator invokes this file by entering the following TACL command: > OBEY $SYSTEM.SHUTDOWN.STOPSYS Note. Shutting down the system in an orderly fashion does not require that you shut down every process. Some processes that have startup files might not need shutdown files. comment -- This is $SYSTEM.SHUTDOWN.
Creating Startup and Shutdown Files CP6100 Lines Shutdown File CP6100 Lines Shutdown File This example shows an SCF command file that stops the ATP6100 lines associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX). This file can be invoked automatically from the STOPSYS file, or you can invoke it by using the following TACL command: > SCF/ IN $SYSTEM.SHUTDOWN.SDNCP6, OUT $ZHOME / == This is $SYSTEM.SHUTDOWN.
Creating Startup and Shutdown Files Printer Line Shutdown File Printer Line Shutdown File This example shows an SCF command file that stops the printer line associated with the SWAN concentrator $ZZWAN.#S01 (configuration track-ID X001XX). This file can be invoked automatically from the STOPSYS file, or you can invoke it by using the following TACL command: > SCF/ IN $SYSTEM.SHUTDOWN.SDNLP, OUT $ZHOME / == This is $SYSTEM.SHUTDOWN.
Creating Startup and Shutdown Files Spooler Shutdown File Spooler Shutdown File This example shows a TACL command file that drains the spooler. This file can be invoked automatically from the STOPSYS file, or you can invoke it by using the following TACL command: > OBEY $SYSTEM.SHUTDOWN.SPLDRAIN To maintain the integrity of the spooler environment, HP recommends that you wait until the spooler has finished draining rather than stop any spooler processes by using the TACL STOP command.
17 Preventive Maintenance When to Use This Section on page 17-1 Monitoring Physical Facilities on page 17-1 Checking Air Temperature and Humidity on page 17-1 Checking Physical Security on page 17-2 Maintaining Order and Cleanliness on page 17-2 Checking Fire-Protection Systems on page 17-2 Cleaning System Components on page 17-2 Cleaning an Enclosure on page 17-2 Cleaning and Maintaining Printers on page 17-2 Cleaning Tape Drives on page 17-3 Handling and Storing Cartridge Tapes on page 17-3 When to Use
Preventive Maintenance Checking Physical Security Checking Physical Security Your company’s security policy will guide you in the kind of security monitoring you perform. You might be asked to check doors and windows at the beginning and end of your shift and report the presence of unauthorized persons. In some facilities, operations staff might be responsible for monitoring and maintaining electronic security systems. Maintaining Order and Cleanliness Clutter and debris can cause accidents and fires.
Preventive Maintenance Cleaning Tape Drives Cleaning Tape Drives Clean tape drive heads and sensors frequently. For detailed information on cleaning tape drives, refer to the documentation shipped with your tape drive. How often you clean a tape drive or the tape path depends on use, operating environment, and tape quality. Cleaning supplies are available from HP.
Preventive Maintenance • • • Handling and Storing Cartridge Tapes Do not remove the leader block, pull out the tape, or press the reel lock. If the leader block is detached from the tape, contact the tape supplier for a leader block repair kit. When transporting cartridge tapes, do not stack the cartridges more than six high. Pack them carefully with the reel sides upright. The leader block edges can crack if they engage with each other.
A Operational Differences Between Systems Running G-Series and H-Series RVUs Users familiar with systems running G-series RVUs will find several major differences in the operational environment of systems running H-series RVUs. Although many of the operations to be performed remain the same, the tools you use to execute these operations might differ significantly. For H-series RVUs, these changes have been made: • • • • • • • • • • • TSM is not supported in H-series. You must use OSM.
Operational Differences Between Systems Running G-Series and H-Series RVUs HP Integrity NonStop NS-Series Operations Guide —529869-001 A- 2
B Tools and Utilities for Operations When to Use This Appendix on page B-1 BACKCOPY on page B-2 BACKUP on page B-2 Disk Compression Program (DCOM) on page B-2 Disk Space Analysis Program (DSAP) on page B-2 EMSDIST on page B-2 Event Management Service Analyzer (EMSA) on page B-2 File Utility Program (FUP) on page B-3 Measure on page B-3 MEDIACOM on page B-3 NonStop NET/MASTER on page B-3 NSKCOM and the Kernel-Managed Swap Facility (KMSF) on page B-3 OSM Package on page B-3 PATHCOM on page B-4 PEEK on page B-
Tools and Utilities for Operations BACKCOPY BACKCOPY Use the BACKCOPY utility to create one or two duplicate tapes for archive storage, distribution, or disaster recovery. You can also create one or two labeled (or unlabeled) tape sets from a labeled or unlabeled tape set. The BACKCOPY utility duplicates tapes that are made from a BACKUP utility file-mode operation, but it cannot duplicate tapes that are made from a BACKUP utility volume-mode operation.
Tools and Utilities for Operations File Utility Program (FUP) File Utility Program (FUP) The File Utility Program (FUP) is a component of the standard software package for the NonStop Kernel operating system. FUP software is designed to help you manage disk files, nondisk devices (printers, terminals, and tape drives), and processes (running programs) on the Integrity NonStop system. You can use FUP to create, display, and duplicate files; load data into files; alter file characteristics; and purge files.
Tools and Utilities for Operations PATHCOM For more information on the OSM package, including a description of the individual applications and how they differ from their TSM counterparts, see the OSM Migration Guide and the OSM User's Guide. PATHCOM PATHCOM is the interactive interface to the PATHMON process, through which users enter commands to configure and manage Pathway applications.
Tools and Utilities for Operations HP Tandem Advanced Command Language (TACL) HP Tandem Advanced Command Language (TACL) The TACL product is the command interface to the NonStop Kernel operating system. In addition to providing full command-interpreter facilities, you can program the TACL interface to help you manage your system in these ways: • • • Automate subsystem startup and shutdown procedures.
Tools and Utilities for Operations ViewSys ViewSys ViewSys is a system resource monitor that displays processor performance statistics and resource consumption for a set polling period. It updates the numbers automatically at the end of each polling period, which allows you to evaluate the effects of changes as those changes are made. ViewSys indicates the current allocation of a given resource and the percentage of that resource used.
C Related Reading For more information about tools and utilities used for system operations, refer to the documentation listed in Table C-1. Table C-1. Related Reading for Tools and Utilities (page 1 of 5) Tool Documentation Description BACKCOPY Guardian Disk and Tape Utilities Manual This manual describes these disk and tape utilities: BACKCOPY, BACKUP, DCOM, DSAP, and RESTORE. This manual supports D-Series, G-series, and H-series RVUs.
Related Reading Table C-1. Related Reading for Tools and Utilities (page 2 of 5) Tool Documentation Description NonStop NET/MASTER NonStop NET/MASTER MS System Management Guide Describes how to integrate system and network management services. It serves as an alternative to the ViewPoint console application. NSKCOM Kernel-Managed Swap Facility (KMSF) Manual This manual describes the operation of and command syntax for NSKCOM, the command interface to KMSF.
Related Reading Table C-1. Related Reading for Tools and Utilities (page 3 of 5) Tool Documentation Description PATHCOM TS/MP System Management Manual This manual describes the interactive management interface to the NonStop TS/MP product. It is intended for system managers and operators.
Related Reading Table C-1. Related Reading for Tools and Utilities (page 4 of 5) Tool Documentation Description Subsystem Control Facility (SCF) SCF Reference Manual for H-Series RVUs This manual describes the operation of SCF on H-series RVUs and how it is used to configure, control, and monitor subsystems supported by an SCF interface.
Related Reading Table C-1. Related Reading for Tools and Utilities (page 5 of 5) Tool Documentation Description Web ViewPoint Web ViewPoint Version 5.2 User Guide This guide describes Web ViewPoint, a browser-based automated operation and management product that provides access to the Event Viewer, Object Manager, and Performance Monitor subsystems.
Related Reading HP Integrity NonStop NS-Series Operations Guide —529869-001 C- 6
D Converting Numbers When to Use This Appendix D-1 Overview of Numbering Systems D-2 Binary to Decimal D-3 Octal to Decimal D-4 Hexadecimal to Decimal D-5 Decimal to Binary D-7 Decimal to Octal D-8 Decimal to Hexadecimal D-9 When to Use This Appendix Refer to this appendix if you need to convert numbers from one numbering system to another.
Overview of Numbering Systems Converting Numbers Overview of Numbering Systems Internally, a computer stores data as a series of off and on values represented symbolically by the binary digits, or bits, 0 and 1, respectively. Because numbers represented as strings of binary 0s and 1s are difficult to read, binary numbers are generally converted into octal, decimal, or hexadecimal form. Table D-1 describes the binary, octal, decimal, and hexadecimal number systems. Table D-1.
Binary to Decimal Converting Numbers Binary to Decimal To convert a binary number to a decimal number: 1. Starting from the right, multiply the least significant (rightmost) binary digit by the first placeholder value. Moving towards the left, multiply each new binary digit by its corresponding placeholder value until the binary number is exhausted. To establish placeholder values, the first placeholder value (on the far right) is 1.
Converting Numbers Octal to Decimal Octal to Decimal To convert an octal number to a decimal number: 1. Starting from the right, multiply the least significant (rightmost) octal digit by the first placeholder value. Moving towards the left, multiply each new octal digit by its corresponding placeholder value until the octal number is exhausted. To establish placeholder values, the first placeholder value on the far right is 1.
Converting Numbers Hexadecimal to Decimal Hexadecimal to Decimal To convert a hexadecimal number to a decimal number: 1. Starting from the right, multiply the least significant (rightmost) hexadecimal digit by the first placeholder value. Moving towards the left, multiply each new hexadecimal digit by its corresponding placeholder value until the hexadecimal number is exhausted. To establish placeholder values, the first placeholder value (on the far right) is 1.
Converting Numbers Hexadecimal to Decimal Figure D-3. Hexadecimal to Decimal Conversion Placeholder values ... 4096 256 16 1 ... B A 1 0 Hexadecimal number 0 * 1 1 * 16 10 * 256 11 * 4096 = 0 = 16 = 2560 = 45056 47632 CDT 609.CDD 1. Take the rightmost hexadecimal digit and multiply it by the rightmost placeholder value. 2. Moving to the left, take the next hexadecimal digit and multiply it by the next placeholder value. Continue to do this until the hexadecimal number has been exhausted.
Converting Numbers Decimal to Binary Decimal to Binary To convert a decimal number to a binary number: 1. Divide the decimal number by 2. The remainder of this first division becomes the least significant (rightmost) digit of the binary value. 2. Divide the quotient from Step 1 by 2, and use the remainder of the next division as the next digit (to the left) of the binary value. Continue to divide the quotients by 2 until the decimal number is exhausted.
Converting Numbers Decimal to Octal Decimal to Octal To convert a decimal number to an octal number: 1. Divide the decimal number by 8. The remainder of this first division becomes the least significant (rightmost) digit of the octal value. 2. Divide the quotient from Step 1 by 8, and use the remainder of the next division as the next digit (to the left) of the octal value. Continue to divide the quotients by 8 until the decimal number is exhausted.
Converting Numbers Decimal to Hexadecimal Decimal to Hexadecimal To convert a decimal number to a hexadecimal number: 1. Divide the decimal number by 16. The remainder of this first division becomes the least significant (rightmost) digit of the hexadecimal value. If the remainder exceeds 9, convert the 2-digit remainder to its hexadecimal letter equivalent. Use this table for conversion. Decimal Hexadecimal 10 A 11 B 12 C 13 D 14 E 15 F 2.
Converting Numbers Decimal to Hexadecimal HP Integrity NonStop NS-Series Operations Guide —529869-001 D -10
Safety and Compliance This sections contains three types of required safety and compliance statements: • • • Regulatory compliance Waste Electrical and Electronic Equipment (WEEE) Safety Regulatory Compliance Statements The following regulatory compliance statements apply to the products documented by this manual. FCC Compliance This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules.
Safety and Compliance Regulatory Compliance Statements Korea MIC Compliance Taiwan (BSMI) Compliance Japan (VCCI) Compliance This is a Class A product based on the standard or the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may occur, in which case the user may be required to take corrective actions.
Safety and Compliance Regulatory Compliance Statements European Union Notice Products with the CE Marking comply with both the EMC Directive (89/336/EEC) and the Low Voltage Directive (73/23/EEC) issued by the Commission of the European Community.
Safety and Compliance SAFETY CAUTION SAFETY CAUTION The following icon or caution statements may be placed on equipment to indicate the presence of potentially hazardous conditions: DUAL POWER CORDS CAUTION: “THIS UNIT HAS MORE THAN ONE POWER SUPPLY CORD. DISCONNECT ALL POWER SUPPLY CORDS TO COMPLETELY REMOVE POWER FROM THIS UNIT." "ATTENTION: CET APPAREIL COMPORTE PLUS D'UN CORDON D'ALIMENTATION. DÉBRANCHER TOUS LES CORDONS D'ALIMENTATION AFIN DE COUPER COMPLÈTEMENT L'ALIMENTATION DE CET ÉQUIPEMENT".
Safety and Compliance Waste Electrical and Electronic Equipment (WEEE) HIGH LEAKAGE CURRENT To reduce the risk of electric shock due to high leakage currents, a reliable grounded (earthed) connection should be checked before servicing the power distribution unit (PDU).
Safety and Compliance Important Safety Information Statements -6
Index A Asynchronous Terminal Process 6100 (ATP6100) 6-3 ATM 3 ServerNet adapter (ATM3SA) 6-2 ATM3SA 6-2 ATP6100 6-3, 16-22 Automating system shutdown 16-3 system startup 16-3 B BACKCOPY utility B-2 BACKUP utility backing up configuration and operations files 9-20 description of B-2 Batteries charging 14-4 maintaining 14-4 Battery ride-through 15-22 Binary number system D-2 Binary to decimal conversion D-3 Bus dumps See Dumps Cleaning enclosures 17-2 Collector (spooler), checking status of 12-2 Command fi
Index E Disk drives (continued) LEDs 3-20 monitoring 10-4 recovery operations for 10-12, 10-13 Disk Space Analysis Program (DSAP) B-2 Distributed Systems Management/Tape Catalog (DSM/TC) B-3 DSAP B-2 DSM/TC B-3 Dumps completed message 9-18 dump file checking with FUP 9-18 submitting to service provider 9-21 processor to disk 9-19 E E4SA 6-2 EMS Analyzer (EMSA) B-2 EMS event messages, monitoring 4-1/4-2 EMSA B-2 EMSDIST description of B-2 using to monitor EMS event messages 4-2 EMSLOG file 9-20 Enclosures
Index G G K G4SA 6-2 monitoring 8-5 overview 8-2 states 8-5 GESA 6-2 Gigabit Ethernet 4-port adapter (G4SA) 6-2 Gigabit Ethernet ServerNet adapter 6-2 Guided procedures, OSM 1-13 G-series -xv Kernel-Managed Swap Facility (KMSF) B-3 KMSF B-3 H M Halting processors 9-10 See also Processor halts Hang of processor 9-7 of system, recovery operations for 9-10 Hexadecimal number system D-2 Hexadecimal to decimal conversion D-5 Home terminal, using $ZHOME 16-4 Hometerm See VHS HP NonStop Open System Managem
Index O NSKCOM B-3 Number conversion binary to decimal D-3 decimal to binary D-7 decimal to hexadecimal D-9 decimal to octal D-8 hexadecimal to decimal D-5 octal to decimal D-4 overview D-1 O Octal number system D-2 Octal to decimal conversion D-4 OSM CIIN file 16-8 description of B-3 documentation C-2 guided procedures 1-13 launching 1-12 security 16-8 using to monitor and resolve problems 3-7 OSM Event Viewer 4-2 Outages, planned 15-14 P PAM 6-3 Parallel Library TCP/IP 2-9 PATHCOM 13-4 PATHMON process
Index R Processors (continued) See Freeze halt See Processor halts halting processors 9-10 hang 9-7 monitoring 3-12 recovery operations for 9-9/9-21 R RCVDUMP utility 9-18 Recovery operations for disk drives 10-12, 10-13 for printers 12-2 for processor halt 9-9 for processors 9-7/9-20 for ServerNet fabrics 7-7 for system console 1-3 for tape drives 11-8 for $SYSTEM 15-20 Reloading single processor on running server 9-19 RESTORE utility B-4 S SACs 6-2 SCF B-4 commands HELP 3-7 LISTDEV 2-7 STATUS ADAPTER
Index T TMF warm start 16-15 X.
