HP Integrity NonStop NS-Series Operations Guide HP Part Number: 520573-007 Published: December 2007 Edition: H06.
© Copyright 2007 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About This Document.......................................................................................................19 Supported Release Version Updates (RVUs)........................................................................................19 Intended Audience................................................................................................................................19 New and Changed Information in This Edition...............................................
Modular Hardware Components.........................................................................................................35 Differences Between Integrity NonStop NS-Series Systems...........................................................36 NonStop System Architectures..................................................................................................36 Integrity NonStop NS16000 Series Systems...............................................................................
Web ViewPoint................................................................................................................................70 Related Reading....................................................................................................................................70 5 Processes: Monitoring and Recovery.........................................................................71 When to Use This Section.................................................................................
Recovery Operations for a Down Disk Due to a Fabric Failure................................................95 Recovery Operations for a Down Path Between Processors......................................................95 Recovery Operations for a Down Processor .............................................................................95 Recovery Operations for a File-System Error............................................................................95 Related Reading.................................
10 Disk Drives: Monitoring and Recovery..................................................................121 When to Use This Section....................................................................................................................121 Overview of Disk Drives ....................................................................................................................121 Internal SCSI Disk Drives..........................................................................................
When to Use This Section....................................................................................................................145 Monitoring TMF..................................................................................................................................145 Monitoring the Status of TMF.......................................................................................................145 Monitoring Data Volumes..............................................................
Powering Off a System........................................................................................................................166 System Power-Off Using OSM......................................................................................................166 System Power-Off Using SCF........................................................................................................167 Emergency Power-Off Procedure........................................................................
ATP6100 Lines Shutdown File.......................................................................................................188 X.25 Lines Shutdown File..............................................................................................................189 Printer Line Shutdown File............................................................................................................189 Expand-Over-IP Line Shutdown File.....................................................................
D Converting Numbers.................................................................................................205 When to Use This Appendix...............................................................................................................205 Overview of Numbering Systems.......................................................................................................205 Binary to Decimal..................................................................................................
List of Figures 3-1 3-2 3-3 3-4 3-5 3-6 7-1 7-2 7-3 9-1 9-2 9-3 11-1 11-2 15-1 15-2 15-3 D-1 D-2 D-3 OSM Management: System Icons Indicate Problems Within.......................................................54 Expanding the Tree Pane to Locate the Source of Problems.........................................................55 Attributes Tab................................................................................................................................
List of Tables 1-1 2-1 2-2 2-3 2-4 2-5 2-6 2-7 3-1 3-2 3-3 3-4 3-5 4-1 6-1 8-1 8-2 8-3 9-1 9-2 9-3 10-1 10-2 10-3 11-1 11-2 13-1 15-1 15-2 C-1 D-1 Problem-Solving Worksheet..........................................................................................................27 Key Subsystems and Their Logical Device Names and Device Types.........................................41 Displaying Information for the TCP/IP Subsystem ($ZTCO).......................................................
List of Examples 2-1 2-2 2-3 2-4 2-5 2-6 3-1 3-2 3-3 SCF LISTDEV Command Output.................................................................................................40 SCF ADD DISK Command Output...............................................................................................43 SCF INFO PROCESS Command Output......................................................................................47 SCF INFO SAC Command Output............................................................
About This Document This guide describes how to perform routine system hardware operations for HP Integrity NonStop NS-series servers on H-series release version updates. This guide is primarily geared toward commercial type NonStop NS-series servers (see Differences Between Integrity NonStop NS-Series Systems on page 2-2 for high-level architectural and hardware differences between the various commercial models).
• • • • • • • • • • • • • • • • • • • “Monitoring EMS Event Messages” (page 69) “ Processes: Monitoring and Recovery” (page 71) “Communications Subsystems: Monitoring and Recovery” (page 77) “ServerNet Resources: Monitoring and Recovery” (page 89) “ I/O Adapters and Modules: Monitoring and Recovery” (page 97) “Processors and Components: Monitoring and Recovery” (page 103) “Disk Drives: Monitoring and Recovery” (page 121) “Tape Drives: Monitoring and Recovery” (page 135) “Printers and Terminals: Monitoring
?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. [ ] Brackets Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines.
"[" repetition-constant-list "]" Item Spacing Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In this example, no spaces are permitted between the period and any other items: $process-name.
In the 6780 ServerNet cluster environment, installation and operating procedures are documented in these manuals: • • ServerNet Cluster 6780 Planning and Installation Guide ServerNet Cluster 6780 Operations Guide Installation and operating procedures for earlier server clusters (those using 6770 switches) are documented in: • ServerNet Cluster Manual OSM is the required system management tool for servers that use 6780 switches in ServerNet clusters, but OSM also provides system management for earlier ve
1 Introduction to Integrity NonStop NS-Series Operations • • • “When to Use This Section” (page 25) “Understanding the Operational Environment” (page 25) “What Are the Operator Tasks?” (page 25) — “Monitoring the System and Performing Recovery Operations ” (page 26) — “Preparing for and Recovering from Power Failures” (page 26) — “Stopping and Powering Off the System” (page 26) — “Powering On and Starting the System” (page 26) — “Performing Preventive Maintenance” (page 26) — “Operating Disk Drives and Tap
• • • Performing preventive maintenance Operating disk drives and tape drives Responding to spooler problems Monitoring the System and Performing Recovery Operations Checking for indications of potential system problems by monitoring the system is part of the normal system operations routine. You perform recovery operations to restore a malfunctioning system component to normal use. Most recovery procedures for Integrity NonStop servers can be performed online.
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.
Table 1-1 Problem-Solving Worksheet (continued) Problem Facts Possible Causes Magnitude? Situation Facts Escalation Decision Plan to Verify/Fix Plan to Prevent and Control Damage 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 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. The problem-solving worksheet gives you a guide for accomplishing this task.
Task 3: Escalate the Problem If Necessary If the solutions you tried in the previous tasks do not solve the problem, you might consider escalating the problem to get additional help. Task 3a: Determine Whether You Need to Escalate the Problem After you complete each task in the problem-solving process, you must decide whether you can continue by yourself or if you must ask for help.
System Consoles A system console is a personal computer approved by HP to run maintenance and diagnostic software for Integrity NonStop servers. New system consoles are preconfigured with the required HP and third-party software. When upgrading to the latest RVU, software upgrades can be installed from the HP NonStop System Console Installer CD. System consoles communicate with Integrity NonStop servers over a dedicated service LAN (local area network).
Opening a TACL Window Directly From MR-Win6530 Starting with NonStop System Console installer S7X-SWV2/HNSC-SWV2, comForte MR-Win6530 replaces OutsideView as the terminal emulator shipped with the console software. It is launched by the OSM Low-Level Link version T0633AAT and later for Startup TACL and Event Stream windows. To launch a TACL session directly from MR-Win6530, see the MR-Win6530 User's Guide (shipped with the console-based product).
For more information on configuring, accessing, or using OSM applications, see: • • • OSM Migration and Configuration Guide OSM Service Connection User’s Guide Online help within the OSM Service Connection, Low-Level Link, Notification Director, and Event Viewer applications Service Procedures OSM offers a variety of guided procedures, interactive actions, and documented service procedures to automate or assist with system serviceability.
2 Determining Your System Configuration • • “When to Use This Section” (page 35) “Modular Hardware Components” (page 35) — “Differences Between Integrity NonStop NS-Series Systems” (page 36) — “Terms Used to Describe System Hardware Components” (page 37) • • “Recording Your System Configuration” (page 37) “Using SCF to Determine Your System Configuration” (page 37) — “SCF System Naming Conventions” (page 38) — “SCF Configuration Files” (page 38) — “Using SCF to Display Subsystem Configuration Information
Differences Between Integrity NonStop NS-Series Systems NonStop System Architectures Integrity NonStop NS-series systems offer of a variety of architecture and configuration options to suit different customer needs. Integrity NonStop NS16000 series and Integrity NonStop NS14000 systems take advantage of NonStop advanced architecture (NSAA). For more information, see the NonStop NS16000 Series Planning Guide or NonStop NS14000 Planning Guide.
Integrity NonStop NS1000 and NS1200 systems do not support connections to NonStop S-series I/O enclosures. Besides the architectural differences, Integrity NonStop NS1000 and NS1200 systems also utilize different NonStop Blade Elements than Integrity NonStop NS16000 series or NS14000 systems. For more information on Integrity NonStop NS1000 and NS1200 systems, refer to the appropriate Planning Guide or Installation Manual for your Integrity NonStop server.
subsystem running on the Integrity NonStop NS-series server. You also use SCF to display information about subsystems and their objects. SCF accepts commands from a workstation, a disk file, or an application process. It sends display output to a workstation, a file, a process, or a printer. Some SCF commands are available only to some subsystems. An overall SCF reference is the SCF Reference Manual for H-Series RVUs. Subsystem-specific information appears in a separate manual for each subsystem.
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. Then you can use the INFO command with a logical device name or device type to obtain information about a specific device or class of devices.
Example 2-1 SCF LISTDEV Command Output $SYSTEM STARTUP 1> SCF LISTDEV LDev 0 1 3 5 6 7 63 64 65 66 67 68 86 87 91 104 105 106 107 108 104 105 106 107 108 121 122 123 124 126 128 129 131 132 133 134 135 136 137 145 167 168 200 Name $0 $NCP $YMIOP $Z0 $SYSTEM $ZOPR $ZZKRN $ZZWAN $ZZSTO $ZZSMN $ZZSCL $ZZLAN $ZSNET $ZSLM2 $ZNET $ZM03 $ZM02 $ZM01 $ZM00 $ZLOG $ZM03 $ZM02 $ZM01 $ZM00 $ZLOG $ZIM03 $ZIM02 $ZIM01 $ZIM00 $ZEXP $SC26 $SC25 $DATA6 $DATA5 $DATA4 $DATA3 $DATA2 $DATA1 $DATA $ZOLHD $ZTC0 $ZTNT $ZPMON PPI
Pri The priority level of the I/O process Program The fully qualified name of the program file for the process Table 2-1 gives the names of some subsystems that are common to most Integrity NonStop NS-series systems and are routinely monitored by operations. These subsystems appear in the LISTDEV output in Example 2-1 (page 40).
TCP/IP Subsystem These examples are based on a TCP/IP process named $ZTCO.
Table 2-4 Displaying Information for the Storage Subsystem ($ZZST0) (continued) To Display Information About These Configured Objects Enter This Command All disk drives (list) LISTDEV TYPE 3 All disk drives (summary information) INFO DISK $* A specific disk drive (detailed information) INFO DISK $name, DETAIL All tape drives (list) LISTDEV TYPE 4 All tape drives (summary information) INFO TAPE $* A specific tape drive (detailed information) INFO TAPE $name, DETAIL When displaying configuration
To get detailed configuration information in command format for all disks on the system, issue this command: -> INFO DISK $*,OBEYFORM 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
The WAN subsystem has responsibility for all WAN connections.
Table 2-7 Subsystem Objects Controlled by SCF (continued) Subsystem Acronym Description Device Type Device Subtype OSICMIP Open Systems Interconnection/Common Management Information Protocol 55 24 OSIFTAM Open Systems Interconnection/File Transfer, Access, and Management 55 21 or 25 OSIMHS Open Systems Interconnection/Message Handling System 55 11 or 12 OSITS Open Systems Interconnection/Transport Services 55 55, 4 OSS Open System Services 24 0 PAM Port Access Method QIO Queued I/
Example 2-3 SCF INFO PROCESS Command Output 32-> INFO PROCESS $ZZKRN.#* NONSTOP KERNEL - Info PROCESS \DRP09.$ZZKRN Symbolic Name CLCI-TACL OSM-APPSRVR OSM-CIMOM OSM-CONFLH-RD OSM-OEV QATRAK QIOMON ROUT SCP SP-EVENT TFDSHLP ZEXP ZHOME ZLOG ZSLM2 ZZKRN ZZLAN ZZSTO ZZWAN *Name *Autorestart *Program $CLCI 10 $SYSTEM.SYSTEM.TACL $ZOSM 10 $SYSTEM.SYSTEM.APPSRVR $ZCMOM 5 $SYSTEM.SYSTEM.CIMOM $ZOLHI 0 $SYSTEM.SYSTEM.TACL $ZOEV 10 $SYSTEM.SYSTEM.EVTMGR $TRAK 10 $SYSTEM.SYSTOOLS.QATRACK $ZMnn 10 $SYSTEM.SYSTEM.
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.... *IOPOBJECT........ TCPIP Name........ 0 *Type............. ( 0,49) 0 Alternate Cpu..... 1 172.031.145.090 $SYSTEM.SYS00.SNMPTMUX $ZTC02 WAN MANAGER Detailed Info Process \DRP09.$ZZWAN.#0 RecSize........... 0 *Type............. (50,00) Preferred Cpu..... 0 Alternate Cpu..... N/A *IOPOBJECT........ $SYSTEM.SYS00.
3 Overview of Monitoring and Recovery • • • “When to Use This Section” (page 49) “Functions of Monitoring” (page 49) “Monitoring Tasks” (page 49) — “Working With a Daily Checklist” (page 50) — “Tools for Checking the Status of System Hardware ” (page 50) — “Additional Monitoring Tasks” (page 53) • • “Monitoring and Resolving Problems—An Approach” (page 53) “Using OSM to Monitor the System” (page 53) — “Using the OSM Service Connection” (page 54) — “Recovery Operations for Problems Detected by OSM” (page
Working With a Daily Checklist A good method for ensuring that certain areas of your operations environment are monitored is to develop a checklist. Monitor these items on a system frequently.
Table 3-1 Monitoring System Components Resource Monitored Using These Tools See...
Table 3-1 Monitoring System Components (continued) Resource Monitored Using These Tools NonStop Blade Complex components: OSM Service Connection Blade Elements, LSUs, logical processors See...
Table 3-1 Monitoring System Components (continued) Resource Monitored Using These Tools See...
Using the OSM Service Connection The OSM Service Connection can be used in a variety of ways to monitor your system, including: • • • Use of colors and symbols to direct you to the source of any problems Attribute values for system resources, displayed in the Attributes tab and in many dialog boxes. Alarms, displayed in the Alarms tab and Alarm Summary dialog box. The following section presents one model for using the OSM Service Connection to monitor your system, along with a few other options.
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. Directly above the details pane is the view pane, from which you can choose a Physical or Inventory view of your system or ServerNet Cluster.
Figure 3-3 Attributes Tab 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. 2. Establishing an OSM Service Connection session to the system. From the Summary menu on the OSM toolbar, selecting System Status.
Figure 3-5 Alarm Summary Dialog Box Figure 3-6 Problem Summary Dialog Box 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.
Recovery Operations for Problems Detected by OSM Recovery operations depend on the particular problem, of course. Methods of determining the appropriate recovery action include: • • • • Alarm Details, available for each alarm displayed in OSM, provide suggested repair actions. The value displayed by problem attributes in OSM often provide clues to recovery. EMS events, retrieved and viewed in the OSM Event Viewer, include cause, effect, and recovery information in the event details.
Example 3-1 SCF STATUS TAPE Command 1-> STATUS TAPE $* STORAGE - Status TAPE \COMM.$TAPE0 LDev State Primary Backup PID PID 156 STOPPED 2,268 3,288 DeviceStatus STORAGE - Status TAPE \COMM.$DLT20 LDev State Primary Backup PID PID 394 STARTED 2,267 3,295 NOT READY DeviceStatus STORAGE - Status TAPE \COMM.$DLT21 LDev State Primary Backup PID PID 393 STARTED 1,289 0,299 NOT READY DeviceStatus STORAGE - Status TAPE \COMM.
where: subsystem The reporting subsystem name object-type The object, or device, type object-name The fully qualified name of the object State One of the valid object states: ABORTING, DEFINED, DIAGNOSING, INITIALIZED, SERVICING, STARTED, STARTING, STOPPED, STOPPING, SUSPENDED, SUSPENDING, and UNKNOWN PPID The primary processor number and process identification number (PIN) of the object BPID The backup processor number and PIN of the object attrn The name of an attribute of the object valn T
Table 3-3 SCF Object States (continued) State Substate Explanation HARDDOWN The object is in the hard-down state or is physically inaccessible due to a hardware error. INACCESSIBLE The object is inaccessible to user processes. PREMATURE-TAKEOVER The backup input/output (I/O) process was asked to take over for the primary I/O process before it had the proper information. RESOURCE-UNAVAILABLE The input/output (I/O) process could not obtain a necessary resource.
1. To create a command file named SYSCHK that will automate system monitoring, type the text shown in Example 3-2 into an EDIT file.
Example 3-3 System Monitoring Output File 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.$DATA04 LDev Primary Backup Mirror 60 *STARTED STARTED *STARTED STORAGE - Status DISK \SHARK.
SLSA Status ADAPTER Name State $ZZLAN.MIOE0 STARTED $ZZLAN.E4SA0 STARTED $ZZLAN.MIOE1 STARTED $ZZLAN.E4SA2 STARTED COMMENT THIS CHECKS ALL LIFS SCF STATUS LIF $* SLSA Status LIF Name $ZZLAN.LAN0 $ZZLAN.LAN3 State STARTED STARTED Access State UP DOWN COMMENT THIS CHECKS ALL PIFS SCF STATUS PIF $* SLSA Status PIF Name State $ZZLAN.E4SA0.0.A STARTED $ZZLAN.E4SA0.0.B STARTED $ZZLAN.E4SA0.1.A STOPPED $ZZLAN.E4SA0.1.
COMMENT THIS CHECKS THE STATUS OF PATHWAY: PATHCOM $ZVPT;STATUS PATHWAY;STATUS PATHMON PATHWAY -- STATE=RUNNING RUNNING EXTERNALTCPS 0 LINKMONS 0 PATHCOMS 1 SPI 0 SERVERCLASSES RUNNING 17 STOPPED 0 THAWED 17 SERVERPROCESSES TCPS RUNNING 17 1 STOPPED 35 0 PENDING 0 0 FROZEN 0 RUNNING STOPPED PENDING TERMS 0 0 0 PATHMON \COMM.$ZVPT -- STATE=RUNNING PATHCTL (OPEN) $OPER.VIEWPT.
Table 3-4 Status LEDs and Their Functions (continued) Location LED Name Color All EMU 66 Function If all lights are on and none are flashing, the drive is not operational. Perform the following actions: 1. Check FCSA. Replace if defective. 2. Check FC-AL I/O module. Replace if defective. 3. Replace drive. Heartbeat Left Green Flashes when EMU is operational and performing locate. Power might just have been applied to the EMU, or an enclosure fault might exist.
Table 3-4 Status LEDs and Their Functions (continued) Location LED Name Color Function Service Amber Lights to indicate internal failure or service action required. Power-on Green Lights when the adapter is receiving power. Service Amber Lights to indicate internal failure or service action required. 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.
Table 3-5 Related Reading for Monitoring Task Tool For information, see...
4 Monitoring EMS Event Messages • • • “When to Use This Section” (page 69) “What Is the Event Management Service (EMS)?” (page 69) “Tools for Monitoring EMS Event Messages” (page 69) — “OSM Event Viewer ” (page 69) — “ViewPoint” (page 69) — “Web ViewPoint” (page 70) • “Related Reading” (page 70) 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.
and requests for operator actions. The events screens allow operators to monitor significant occurrences or problems in the network as they occur. Critical events or events requiring immediate action are highlighted. Web ViewPoint Web ViewPoint, a browser-based product, accesses the Event Viewer, Object Manager, and Performance Monitor subsystems.
5 Processes: Monitoring and Recovery • • “When to Use This Section” (page 71) “Types of Processes” (page 71) — “System Processes” (page 71) — “I/O Processes (IOPs)” (page 71) — “Generic Processes” (page 71) • “Monitoring Processes” (page 72) — “Monitoring System Processes” — “Monitoring IOPs” — “Monitoring Generic Processes” • • “Recovery Operations for Processes” (page 75) “Related Reading” (page 75) When to Use This Section This section provides basic information about the different types of process
Examples of generic processes: • • The $ZZKRN Kernel subsystem manager process Other generic processes controlled by $ZZKRN; for example: — The $ZZSTO storage subsystem manager process — The $ZZWAN wide area network (WAN) subsystem manager process — QIO processes — OSM server processes — The $ZZLAN ServerNet LAN Systems Access (SLSA) subsystem manager process — The $FCSMON fibre channel storage monitor For more information, refer to the SCF Reference Manual for the Kernel Subsystem.
$ZTXAE $ZWBAF $ZZW00 $DSMSCM $DATA2 $ZLOG $ZTH00 $DSMSCM $Z1RM $ZPP01 0,330 0,333 0,334 0,335 0,336 0,340 0,343 0,344 1,80 1,280 145 179 199 220 220 150 148 220 148 160 015 015 215 317 317 011 005 317 005 015 P P P P P P P 255,255 255,255 255,255 255,255 255,255 255,255 255,255 255,255 255,255 255,255 $SYSTEM.SYS14.SNMPTMUX $SYSTEM.SYS14.WANBOOT $SYSTEM.SYS14.CONMGR $SYSTEM.SYS14.TSYSDP2 $SYSTEM.SYS14.TSYSDP2 $SYSTEM.SYS14.EMSACOLL $SYSTEM.SYS14.TFDSHLP $SYSTEM.SYS14.TSYSDP2 $SYSTEM.SYS14.
MSGMON MSGMON MSGMON MSGMON MSGMON MSGMON MSGMON MSGMON MSGMON MSGMON MSGMON MSGMON MSGMON MSGMON OSM-APPSRVR OSM-CIMOM OSM-CONFLH-RD OSM-OEV QATRAK QIOMON QIOMON QIOMON QIOMON QIOMON QIOMON QIOMON QIOMON QIOMON QIOMON QIOMON QIOMON QIOMON QIOMON QIOMON QIOMON RTACL SCP SP-EVENT TFDSHLP TFDSHLP TFDSHLP TFDSHLP TFDSHLP TFDSHLP TFDSHLP TFDSHLP TFDSHLP TFDSHLP TFDSHLP TFDSHLP TFDSHLP $ZIM02 $ZIM03 $ZIM04 $ZIM05 $ZIM06 $ZIM07 $ZIM08 $ZIM09 $ZIM10 $ZIM11 $ZIM12 $ZIM13 $ZIM14 $ZIM15 $ZOSM $ZCMOM $ZOLHI $ZOEV $TR
Recovery Operations for Processes For recovery operations on generic processes, use the SCF interface to the Kernel subsystem and specify the PROCESS object. These SCF commands are available for controlling generic processes: ABORT Terminates operation of a generic process. This command is not supported for the subsystem manager processes. START Initiates the operation of a generic process. Generic processes that are configured to be persistent usually do not require operator intervention for recovery.
6 Communications Subsystems: Monitoring and Recovery • • “When to Use This Section” (page 77) “Communications Subsystems” (page 77) — “Local Area Networks (LANs) and Wide Area Networks (WANs)” (page 77) “Monitoring Communications Subsystems and Their Objects” (page 79) • • • • • • • “Monitoring the SLSA Subsystem” (page 79) “Monitoring the WAN Subsystem” (page 81) “Monitoring the NonStop TCP/IP Subsystem” (page 84) “Monitoring Line-Handler Process Status” (page 85) “Tracing a Communications Line” (page 8
Adapters supported on NonStop S-series servers that can be accessed through Expand over IP, include: • • • • • • • ATM 3 ServerNet adapter (ATM3SA) Ethernet 4 ServerNet adapter (E4SA) Fast Ethernet ServerNet adapter (FESA) Gigabit Ethernet ServerNet adapter (GESA) Gigabit Ethernet 4-Port ServerNet adapter (G4SA) Multifunction I/O board (MFIOB) in the processor multifunction (PMF) customer-replaceable unit (CRU) and I/O multifunction (IOMF) CRU Token-Ring ServerNet adapter (TRSA) For further information, r
Object Connectivity By ServerNet cluster (Expand-over-ServerNet) Line-handler processes SNAX/APN Subsystem service manager process and line-handler processes SNAX/XF Subsystem service manager process and line-handler processes TR3271 Line-handler processes X25AM Line-handler processes You can define these communications subsystem objects as WAN subsystem devices.
Monitoring the Status of an Adapter and Its Components 1. To monitor the status of an adapter: > SCF STATUS ADAPTER adapter-name A listing similar to this example is sent to your home terminal: ->STATUS ADAPTER $ZZLAN.G11123 SLSA Status ADAPTER Name $ZZLAN.G11123 State STARTED 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.
> SCF STATUS PIF pif-name A listing similar to this example is sent to your home terminal: ->STATUS PIF $ZZLAN.G11123.0 SLSA Status PIF Name $ZZLAN.G11123.0.A State STARTED Trace Status ON 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 4.
Monitoring Status for a SWAN Concentrator To display the current status for a SWAN concentrator: > SCF STATUS ADAPTER $ZZWAN.#concentrator-name 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.
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 \COMM.$ZZWAN.#5 ,264 Process traced.. NO WAN Manager STATUS PROCESS for PROCESS State :......... STARTED LDEV Number..... 67 PPIN............ 4 \COMM.$ZZWAN.
> 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...............
TCPIP Status ROUTE \SYSA.$ZTCO.* Name #ROU11 #ROU9 #ROU12 #ROU8 #ROU3 Status RefCnt STARTED STARTED STARTED STARTED STOPPED 0 0 0 1 0 Monitoring NonStop TCP/IP Subnets To obtain the status of all NonStop TCP/IP subnets: > SCF STATUS SUBNET $ZTC0.* The system displays a listing similar to: 1-> STATUS SUBNET $ZTC0.* TCPIP Status SUBNET \SYSA.$ZTC0.* Name #LOOP0 #EN1 Status STARTED STARTED Monitoring Line-Handler Process Status A line-handler process is a component of a data communications subsystem.
If any state other than STARTED appears, check the meaning of the state in SCF Object States on page 3-14. Depending upon the type of problem, follow your established procedures for problem reporting and escalation. Examples To check the detailed status of line $LHCS6S: > SCF STATUS LINE $LHCS6S, DETAIL A listing such as this output is sent to your home terminal: -> STATUS LINE $LHCS6S, DETAIL PPID.................... ( 3, 24) BPID................ ( 2, 24) State................... STOPPED Path LDEV.......
34 \SUNTEC (062) 367 35 \CS8 (152) 368 1 293) NPT 1 -- ----1 324 NOT READY (124) 790K ( 5, -- 367 READY 368 NOT READY (124) Tracing a Communications Line Use the SCF TRACE command to trace the operation of a communications line. The line continues normal operation while being traced, but it passes all its message traffic to a trace procedure. Tracing enables you to see the history of a communications line, including its internal processing.
Table 6-1 Related Reading for Communications Lines and Devices (continued) For Information About... Refer to...
7 ServerNet Resources: Monitoring and Recovery • • • “ServerNet Communications Network” (page 89) “System I/O ServerNet Connections” (page 91) “Monitoring the Status of the ServerNet Fabrics” (page 92) — “Monitoring the ServerNet Fabrics Using OSM” (page 92) — “Monitoring the ServerNet Fabrics Using SCF” (page 93) • “Related Reading” (page 95) When to Use This Section Use this section to learn about monitoring and performing recovery operations for the internal and external ServerNet fabrics, and to und
Figure 7-1 Integrity NonStop NS16000 Series System Integrity NonStop NS14000 ServerNet Connectivity ServerNet connections between I/O devices and processors depend on whether the Integrity NonStop NS14000 system has an IOAM enclosure or VIO enclosures. Figure 7-2 shows an NS14000 system with an IOAM enclosure.
Figure 7-2 Integrity NonStop NS14000 System with IOAM Enclosure Integrity NonStop NS1200 and NS1000 ServerNet Connectivity ServerNet connections between I/O devices and processors depend on whether the Integrity NonStop NS1000 system has an IOAM enclosure or VIO enclosures. NonStop NS1200 systems have VIO enclosures only. For more information on Integrity NonStop NS1200 and NS1000 systems, see the appropriate Planning Guide or Installation Manual, or the Versatile I/O (VIO) Manual.
ServerNet cables connected to the p-switch PICs in slots 10 through 13 come from the LSUs and processors. Cables connected to the PICs in slots 4 though 9 connect to one or more IOAM enclosures or to NonStop S-series I/O enclosures equipped with IOMF2 CRUs. Figure 7-3 shows the connections to the PICs in a fully populated p-switch. For Integrity NonStop NS14000 systems, see “Integrity NonStop NS14000 ServerNet Connectivity” (page 90).
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. The X and Y external ServerNet fabric objects are located under the ServerNet Cluster object (if your system is part of a ServerNet cluster). 3. Check the fabric objects for: a.
15 <- DOWN Y-FABRIC TO FROM 00 01 02 <03 <04 <05 <06 <07 <08 <09 <10 <11 <12 <13 <14 <15 <- 0 1 UP UP UP UP DOWN DOWN DOWN DOWN DOWN DOWN DOWN DOWN DOWN DOWN DOWN DOWN DOWN DOWN 2 3 4 5 6 7 8 9 10 11 12 13 14 15 UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA UNA In the preceding example of a 2-processor system: • • All ServerNet connections between processors 0 and 1 are up.
The path from the processor in the FROM row to the processor in the TO column is down because the path is failing. The processor in the FROM row cannot send to the processor in the TO column. • <- DOWN (for an entire row) The processor in the FROM row is down or nonexistent. For a processor that does exist on your system, this status is abnormal. • ERROR nnn (for an entire row) The processor in the FROM row unexpectedly returned a file-system error to that ServerNet fabric.
8 I/O Adapters and Modules: Monitoring and Recovery • • “When to Use This Section” (page 97) “I/O Adapters and Modules” (page 97) — “Fibre Channel ServerNet Adapter (FCSA)” (page 97) — “Gigabit Ethernet 4-Port Adapter (G4SA)” (page 98) — “4-Port ServerNet Extender (4PSE)” (page 98) • “Monitoring I/O Adapters and Modules” (page 99) — “Monitoring the FCSAs” (page 99) — “Monitoring the G4SAs” (page 100) — “Monitoring the 4PSEs” (page 101) • • “Recovery Operations for I/O Adapters and Modules” (page 101) “
enclosures, for a total of eight per FCSA. The FCS Manager process assigns a SAC on an FCSA to a particular instance of the FCS Monitor. Up to 10 FCSAs can be housed in an I/O adapter module (IOAM), which is mounted in an IOAM enclosure (except in Integrity NonStop NS14000 and NS1000 systems, where slot 1 is reserved for a “4-Port ServerNet Extender (4PSE)”).
Monitoring I/O Adapters and Modules Use the Subsystem Control Facility (SCF) or the OSM Service Connection to monitor the FCSAs, G4SAs, and ServerNet/DAs. Monitoring the FCSAs For a general, top-down approach for using OSM to monitor system components, refer to Using OSM to Monitor the System on page 3-7. To monitor the FCSA and its attached devices with SCF, use the SCF INFO and SCF STATUS commands. For example, to monitor all FCSAs using SCF: > SCF STATUS ADAPTER $ZZSTO.
Table 8-1 Service, Flash Firmware, Flash Boot Firmware, Device, and Enabled States for the FCSA (continued) State Description Enabled State: Disabled The component is present but not operational, possibly because the Disable action was performed. Enabled State: Enabled The component is operational. Enabled State: Fault A problem was detected. The component might be functioning below standard or not responding. Inspect the component. Enabled State: Off The component is not functional.
Table 8-2 Service, Device, and Enabled States for the G4SA (continued) 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. Enabled State: Disabled The component is present but not operational, possibly because the Disable action was performed.
Table 8-3 Related Reading for I/O Adapters and Modules For Information About Refer to...
9 Processors and Components: Monitoring and Recovery • • • “When to Use This Section” (page 103) “Overview of the NonStop Blade Complex” (page 103) “Monitoring and Maintaining Processors” (page 106) — “Monitoring Processor Status Using the OSM Low-Level Link” (page 106) — “Monitoring Processor Status Using the OSM Service Connection” (page 107) — “Monitoring Processor Performance Using ViewSys” (page 108) • “Identifying Processor Problems” (page 109) — “Processor or System Hangs” (page 109) — “Processor
A processor with two NonStop Blade Elements comprise the dual modular redundant (DMR) NonStop Blade Complex, which is also referred to as a duplex system. This duplex system provides data integrity and system availability that is comparable to NonStop S-series systems, but at considerably faster processing speeds. Three NonStop Blade Elements plus their associated LSUs make up the triple modular redundant (TMR) NonStop Blade Complex, which is referred to as a triplex system.
Figure 9-1 Modular NSAA With One NonStop Blade Complex and Four Processors For Integrity NonStop NS16000 series servers, ServerNet communications are controlled by processor switch (or p-switch) modules; one for each of the ServerNet fabrics (represented by X and Y ServerNet Switching blocks in Figure 9-1). P-switches connect input/output components to the NS-series 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.
3. The status for all processors should be “Executing NonStop OS.” (See Figure 9-2.) If not, refer to “Identifying Processor Problems” (page 109). Figure 9-2 Processor Status Display Monitoring Processor Status Using the OSM Service Connection For Integrity NonStop NS-series systems, the OSM Service Connection displays processor-related components under Processor Complex objects in the tree pane. There can be up to four Processor Complex objects per NS-series system, for a total of 16 processors.
Figure 9-3 OSM Representation of Processor Complex To check processor-related components using the OSM Service Connection: 1. 2. Expand the tree pane to check all Processor Complex objects. If a Processor Complex object icon contains a yellow arrow (as illustrated in Figure 9-3), expand that complex to check its subcomponents. • If any processor subcomponent is displaying a red or yellow triangular symbol over its object icon, check the Attributes tab for degraded attribute values.
NOTE: The Measure utility also collects and displays statistics about system performance and the performance of processors and other system components. Operations management personnel often use this utility to help fine-tune and balance a system. For instructions on using this utility, refer to the Measure User’s Guide and the Measure Reference Manual. After the first ViewSys screen appears, press F1 to view processor busy statistics: To exit ViewSys, press F16.
When the operating system detects a software error that it cannot correct, it can execute a freeze instruction to suspend all application and system processes running in the associated processor. The status of the frozen processor becomes: Freeze code = %nnnnnn If system freeze is enabled, the status for all other freeze-enabled processors becomes: Frozen by other processor The Processor Halt Codes Manual documents processor halt codes.
and perform the type of recovery operation needed (see “Monitoring Processors Automatically Using TFDS” (page 106)). For information on configuring and using TFDS, see the Tandem Failure Data System (TFDS) Manual. If all processors have halted (the system is down), TFDS cannot perform an automatic dump or reload. You must load the system, as described in Performing a System Load From a Specific Processor on page 15-11.
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 Blade Element from the reload operation. This allows you get the processor running for the PEs on the other Blade Elements, take a dump of the PE on the omitted Blade Element, and then reintegrate it back into the running processor.
option is one of these: NOSWITCH [PRIME|NOPRIME] fabric OMITBLADE [A|B|C] $volume [.sysnn.osdir] NOSWITCH specifies that, when a processor is reloaded, there is no default autoswitch of controller ownership to the configured primary processor. Sets up the logical processor for the reload operation. NOPRIME is the default. specifies whether the X fabric or Y fabric is used for the transfer of the operating system image to the processor during the RELOAD operation.
8. 9. Check the TACL 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. If the load fails, check the parameters and reload the processor. If the load fails again, contact your service provider. Using the OSM Service Connection to Perform Reload The OSM Service Connection provides a Reload action on the Logical Processor object.
7. Click OK. Recovery Operations for a System Hang If a system hang occurs on an NS-series server, you no longer have to choose between taking the time to dump the system or quickly loading the system without the benefit of getting the dump information. You can now load processor 0 or 1 while excluding one processor element (PE) in that processor.
Confirm that the action success Processor Freeze State for each processor is now Enabled. In addition to the attribute values described earlier, in the LLL Processor Status dialog box, each processor should now display an “F” appears next to its name Dumping a Processor to Disk Dump options for NonStop NS-series servers are different than for NonStop S-series servers.
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. Verify that a disk is available with enough space to store the dump.
3. Monitor the dump to make sure that it finishes successfully: a. Wait for this message to appear: CPU n has been dumped to dumpfile b. Check the size of dumpfile to verify that the end-of-file pointer (EOF) is not equal to zero. > FUP INFO dumpfile When a processor is dumped to disk, the RCVDUMP utility begins copying the dump in a compressed format from the specified processor into a disk file called dumpfile. If dumpfile does not exist, the RCVDUMP utility creates it.
Submitting Information to Your Service Provider To help with the analysis of a processor dump, submit a backup tape of other system configuration and operations files and some additional information. • • • “Submitting Tapes of Processor Dumps” (page 119) “ViewPoint” (page 69) “Additional Information Required by Your Service Provider ” (page 119) Submitting Tapes of Processor Dumps Use a separate tape for each processor dump.
Table 9-2 Additional Processor Dump Information for Your Service Provider (continued) The processor numbers of the processors that were dumped, along with the letter designation of the PEs dumped.
10 Disk Drives: Monitoring and Recovery • • “When to Use This Section” (page 121) “Overview of Disk Drives ” (page 121) — “Internal SCSI Disk Drives” (page 122) — “M8xxx Fibre Channel Disk Drives” (page 122) — “Enterprise Storage System (ESS) Disks” (page 123) • “Monitoring Disk Drives” (page 123) — “Monitoring Disk Drives With OSM” (page 123) — “Monitoring Disk Drives With SCF ” (page 124) — “Monitoring the State of Disk Drives” (page 127) — “Monitoring the Use of Space on a Disk Volume” (page 128) — “M
Internal SCSI Disk Drives Internal SCSI disk drives are installed in NonStop S-series I/O enclosures. These disk drives are Class-1 CRUs. Any physical action on a CRU, including installing and replacing disks, can be performed by customers. However, depending on the class of CRU, training in replacement techniques might be recommended.
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.
Task See Determine: • Service state • Primary path state • Secondary path state Using OSM to Monitor the System on page 3-7 Learn possible values of primary and backup path state attributes for disk drives and disk paths “Monitoring the State of Disk Drives” (page 127) Monitoring Disk Drives With SCF This subsection explains how to list disk volumes and determine their status. 1.
92 MIRROR-BACKUP INACTIVE STOPPED HARDDOWN 2,266 3,266 General Disk Information: Device Type........... 3 Device Subtype........... 53 Primary Drive Type.... Mirror Drive Type........ Physical Record Size.. 4096 Priority................. 220 Library File.......... Program File.......... $SYSTEM.SYS00.TSYSDP2 Protection............ MIRRORED Hardware Information: Path Location Power (group,module,slot) PRIMARY EXTERNAL DUAL MIRROR EXTERNAL NONE Total Errors = 0 Total Warnings = 0 3.
STORAGE - Status VIRTUAL DISK \COMM.$WEBVPT LDev State Primary Backup Type Subtype PID PID 142 STARTED 9,26 8,47 3 36 STORAGE - Status VIRTUAL DISK \COMM.$WIPRO LDev State Primary Backup Type PID PID 141 STARTED 9,27 8,51 3 Subtype 36 STORAGE - Status VIRTUAL DISK \COMM.$ZERO LDev State Primary Backup Type PID PID 133 STARTED 8,78 9,57 3 Subtype 36 STORAGE - Status VIRTUAL DISK \COMM.$ZIMBU LDev State Primary Backup Type PID PID 115 STARTED 9,28 8,52 3 STORAGE - Status DISK \COMM.
6 6 6 6 PRIMARY BACKUP MIRROR MIRROR-BACKUP ACTIVE INACTIVE ACTIVE INACTIVE STARTED STARTED STARTING STARTING REVIVE REVIVE PID 0,10 0,10 0,10 0,10 PID 1,10 1,10 1,10 1,10 The output from this example indicates that $DATA00: • • Is a mirrored volume (primary and mirror paths) Has a mirror disk that is being revived (SubState REVIVE) LDev Logical device number Path Disk path assignment PathStatus Status of the disk path; whether that path is the current path (ACTIVE) or not (INACTIVE) State Cu
Monitoring the Use of Space on a Disk Volume The Disk Space Analysis Program (DSAP) provides information on disk capacity, free-space fragments, and page allocation. To check for bad sectors, you can use SCF: -> INFO DISK $*, BAD, SEL started, sub magnetic Bad Sectors Information $DATA14 Primary: No bad sectors found.
FILE LABEL: 775 (31.6% USED) EXTENTS ALLOCATED: 10 Monitoring Disk Configuration and Performance For information about See Checking configuration information for disk devices SCF Reference Manual for the Storage Subsystem Monitoring disk block and cache statistics Examining system performance data with Measure Measure User’s Guide Identifying Disk Drive Problems For recovery operations, refer to “Recovery Operations for Disk Drives ” (page 130).
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.
Table 10-3 Common Recovery Operations for Disk Drives (continued) Problem Recovery Unspared defective sectors To check for unspared defective sectors with SCF:-> INFO DISK $*, BAD, SEL started, sub magneticTo check for unspared defective sectors with DSAP at a TACL prompt:> DSAP $* • Recovery for DSAP is not needed. • Recovery for DCOM: use the SCF INFO DISK, BAD command on the affected disk to obtain the bad sector address. Before restarting DCOM, perform the CONTROL DISK, SPARE command.
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. $DATA00-P and $DATA00-B are stopped in the HARDDOWN substate. STORAGE - Status DISK \ALPHA12.
- ALTER MEMOS, MAXEXTENTS 20 - INFO MEMOS, DETAIL A report such as this one is sent to your home terminal: $DATA.DATA1.MEMOS 12 Jul 1993, 14:05 ENSCRIBE TYPE U CODE 101 EXT ( 2 PAGES, 2 PAGES ) ODDUNSTR MAXEXTENTS 20 BUFFERSIZE 4096 OWNER 8,255 SECURITY (RWEP): NUNU DATA MODIF: 12 Jul 1993, 14:04 CREATION DATE: 12 Jan 1993, 14:04 LAST OPEN: 12 Jul 1993, 14:24 EOF 567022 (78.5% USED) FILE LABEL: 649 (22.
11 Tape Drives: Monitoring and Recovery • • • “When to Use This Section” (page 135) “Overview of Tape Drives” (page 135) “Monitoring Tape Drives” (page 135) — “Monitoring Tape Drive Status With OSM” (page 135) — “Monitoring Tape Drive Status With SCF” (page 137) — “Monitoring Tape Drive Status With MEDIACOM” (page 138) — “Monitoring the Status of Labeled-Tape Operations” (page 139) • • “Identifying Tape Drive Problems” (page 139) “Recovery Operations for Tape Drives ” (page 140) — “Recovery Operations Us
3. Expand the Tape Collection object and select the tape drive displaying a red or yellow triangular symbol over the tape drive object or bell-shaped symbol next to the object. For an example of an FCSA-connected tape drive, see Figure 11-1; for an IOMF2-connected tape drive, see the following figure. • If a red or yellow triangular symbol is displayed over the tape drive object, check the Attributes tab for the specific attribute reporting a degraded value.
Figure 11-2 OSM: Monitoring Tape Drives Connected to an IOMF2 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).
Primary PID The primary processor number and process identification number (PIN) of the specified device Backup PID The backup processor number and PIN of the specified device DeviceStatus The status of the device path For more information: • • SCF Object States on page 3-14 describes the possible SCF states of tape drives and other devices. The Guardian User’s Guide provides additional information about tape operations and the tasks you can perform.
A listing such as this one is sent to your home terminal: MEDIACOM - T6028D42 (18DEC98) Tape Drive ----------$TAPE0 Drive Status ----FREE Tape Name ----- Tape Status ------ Label Type ------- Open Mode ------ Process Name ----------------- 1 tape drive returned. 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.
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. From the OSM Service Connection tree pane (the left-hand pane shown in Figure 11-1 (page 136)): a.
The SCF Reference Manual for the Storage Subsystem describes these commands. Related Reading For more information about tapes and tape drives, refer to the documentation listed in Table 11-2. Table 11-2 Related Reading for Tapes and Tape Drives For Information About... Refer to... Tape drives Integrity NonStop NS-Series Supported Hardware BACKUP, RESTORE, and BACKCOPY utilities Guardian Disk and Tape Utilities Reference Manual (for Enscribe and SQL/MP files) BRCOM utility Backup and Restore 2.
12 Printers and Terminals: Monitoring and Recovery • • • “When to Use This Section” (page 143) “Overview of Printers and Terminals ” (page 143) “Monitoring Printer and Collector Process Status” (page 143) — “Monitoring Printer Status” (page 143) — “Monitoring Collector Process Status” (page 144) • “Recovery Operations for Printers and Terminals” (page 144) — “Recovery Operations for a Full Collector Process” (page 144) • “Related Reading” (page 144) When to Use This Section This section provides a bri
The output shows that the printer $LASER is up and available to print user jobs. Monitoring Collector Process Status Check that the collector processes on your spooler subsystem do not become more than about 90 percent full. To check their status: > SPOOLCOM COLLECT A listing similar to this output is sent to your home terminal: COLLECT $S $S1 $S2 STATE ACTIVE ACTIVE ACTIVE FLAGS CPU PRI 0 , 1 149 1 , 2 149 2 , 3 149 UNIT 4 10 8 DATA FILE $SPOOL.SPL.DATA $SPOOL.SPL.DATA1 $SPOOL.SPL.
13 Applications: Monitoring and Recovery • • “When to Use This Section” (page 145) “Monitoring TMF” (page 145) — “Monitoring the Status of TMF” (page 145) — “Monitoring Data Volumes” (page 146) — “TMF States” (page 147) • “Monitoring the Status of Pathway” (page 147) — “PATHMON States” (page 148) • “Related Reading” (page 149) 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.
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. However, information from the other STATUS commands (STATUS DATAVOLS, STATUS OPERATIONS, STATUS SERVER, and STATUS TRANSACTION) does not appear in the STATUS TMF display.
$DATA6 $DATA6 AUX01 AUX01 Online Archive Started Recovering TMF States The TMF subsystem can be in any of the states listed in Table 13-1. Table 13-1 TMF States State Meaning Configuring New Audit Trails The TMF subsystem has not yet been started with this configuration. Deleting The TMF subsystem is purging its current configuration, audit trails, and volume and file recovery information for the database in response to a DELETE TMF command.
> PATHCOM $pathmon-process-name 3.
The other elements of the STATUS PATHMON output are: • • • • • CPUS shows the number of the primary and backup processors in which the PATHMON process is running. If the backup PATHMON process is not running, the second number is blank. PATHCTL, LOG1, and LOG2 contain information about the PATHMON control file and the logging files. The REQNUM column contains the PATHMON internal identifiers of application requesters that are currently running in this environment.
14 Power Failures: Preparation and Recovery • • “When to Use This Section” (page 151) “System Response to Power Failures ” (page 151) — “NonStop NS-Series Cabinets (Modular Cabinets) ” (page 151) — “External Devices ” (page 152) — “ESS Cabinets” (page 152) — “Air Conditioning” (page 152) • “Preparing for Power Failure” (page 152) — “Set Ride-Through Time” (page 152) — “Monitor Power Supplies” (page 153) — “Monitor Batteries” (page 153) — “Maintain Batteries” (page 153) • “Power Failure Recovery” (page
External Devices External (peripheral), devices, such as tape drives, external disk drives, LAN routers, and SWAN concentrators, are not backed up by internal batteries. External devices behave differently than a system during power failure according to the UPS support provided: No UPS Peripheral devices will fail immediately if not supported by a UPS. With a Site UPS A site UPS should support external devices until its capacity to supply power is exhausted.
For more information, see the appropriate Installation Manual for your Integrity NonStop NS16000 series, NS14000, NS1200, or NS1000 system or the OSM Service Connection User’s Guide. Monitor Power Supplies Monitor power-generating equipment and run regular checks on any backup generators to make sure that you can handle extended power outages. Monitor Batteries • • • Monitoring site UPS batteries is the responsibility of the customer. OSM does not interface with a site UPS or batteries.
or by using the TACL command interpreter. Refer to the Guardian Procedure Calls Reference Manual or the TACL Reference Manual. Related Reading For more information about preparing for and recovering from power failures: • • • • • 154 The effect of power failures on NonStop NS-series servers, see the NonStop NS-Series Planning Guide. The ride-through time, see the SCF Reference Manual for the Kernel Subsystem. The TACL SETTIME command, see the TACL Reference Manual.
15 Starting and Stopping the System • • “When to Use This Section” (page 155) “Powering On a System ” (page 156) — “Powering On the System From a Low Power State” (page 156) — “Powering On the System From a No Power State” (page 156) • “Starting a System” (page 158) — “Loading the System” (page 158) — “Starting Other System Components” (page 160) — “Performing a System Load ” (page 161) — “Performing a System Load From a Specific Processor” (page 162) — “Reloading Processors” (page 163) • “Minimizing t
Powering On a System Powering on a system delivers AC power to the system cabinets. Fans on the processor switches, processor Blade Elements, IOAM or VIO enclosures, and disk drive enclosures start turning, and air begins to circulate through the components. After the fans start to operate, most other system components begin to power on. Status light-emitting diodes (LEDs) on the system components light during a series of power-on self-tests (POSTs). Any of the LEDs can become lit briefly during the POSTs.
1. Before you power on any system enclosures, power on the external system devices and any other devices you want started when the system starts. External system devices include tape devices, Enterprise Storage Systems (ESSs), printers, and terminals. Refer to the documentation that accompanies the device for instructions on powering on. For example: • • You must power on Fibre Channel to SCSI Converter devices connected to your system before you power on the tape devices attached to it.
12. 13. 14. 15. For each Group 1nn, check that module 2 and module 3 are displayed. If any of these components are not yet displayed, wait before you start the system. After the system is powered on, you must wait 5 minutes before starting the system. You can now start your system as described in “Starting a System” (page 158). Starting a System Use the OSM Low-Level Link to start a system.
configuration that you want to load. The system disk that you load from starts as $SYSTEM. Any alternate system disks start using their alternate name. After you select a system load disk, the Disk Type box indicates whether you’ve selected a Fibre Channel (FCDM) or SCSI disk. The Path window is populated with information about four load paths. You can double-click on a row to make changes. However, the changes do not persist after the dialog box is closed.
Table 15-1 System Load Paths in Order of Use (continued) Data Travels 6 Mirror $SYSTEM-M 0 Y 7 Mirror backup $SYSTEM-M 0 X 8 Mirror backup $SYSTEM-M 0 Y 9 Primary $SYSTEM-P 1 X 10 Primary $SYSTEM-P 1 Y 11 Backup $SYSTEM-P 1 X 12 Backup $SYSTEM-P 1 Y 13 Mirror $SYSTEM-M 1 X 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.
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” (page 171). • You can include commands in startup command files that you invoke from a TACL prompt or another startup file.
1. 2. 3. 4. 5. 6. 7. 8. 9. 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. 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. In the Configuration File box, select a system configuration file. In most cases, you should select the Current (CONFIG) file.
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. For more information about dumping processor memory, refer to Section 9, Processors and Components: Monitoring and Recovery. 12. If needed, reload any remaining processors.
8. Check that the reload initiated successfully. From the Low-Level Link, the Processor Status dialog box shows the status for the processor as “Executing NonStop OS.
Note the effect on the system when you stop these applications: • • Stopping Pathway applications begins shutdown of all TCP objects (shutting down TERM objects and then themselves) in parallel. New work is disallowed. The PATHMON process logs the start and completion of SHUTDOWN2. It does not log status messages during shutdown.
> SCF CONTROL DISK $*,REFRESH 9. If the system is a member of a ServerNet cluster, HP recommends that you first remove the system from the cluster. To remove the system from the cluster, refer to the ServerNet Cluster 6780 Operations Guide (for 6780 switches) or the ServerNet Cluster Manual (for 6770 switches). Stopping the System Stopping a system halts each processor (terminating all processes running in each processor) on the system in an orderly fashion.
3. 4. Select actions. From the drop-down menu, select System Power Off. System Power-Off Using SCF To power off the system using SCF, log on to an available TACL command interpreter as the super ID (255,255) and issue the SCF power-off command: > SCF CONTROL SUBSYS $ZZKRN, SHUTDOWN 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.
Green LED Is Not Lit After POSTs Finish It can take several minutes for the green LEDs on all system components to light: 1. 2. Wait for the POSTs to finish. It might take as long as 10 minutes for all system components. If the green LEDs still do not light: a. Check that AC power cords and component power cords are properly connected. b. If one green LED still does not light, a system component might have failed its POST. 3.
a. b. c. d. e. Load the system as described in “Starting a System” (page 158). In the Configuration File box, select Base (CONBASE) as the configuration file. Reload the remaining processors. See “Reloading Processors” (page 163). From the Startup TACL window, configure a tape drive. Restore a previously backed-up configuration file. Load the system as described in “Starting a System” (page 158) from the current configuration file (CONFIG). Check that the CIIN file is enabled. 11.
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. To open startup event stream windows and startup TACL windows from OSM: 1. 2. Log on to the OSM Low-Level Link.
2. 3. 4. 5. Select Session > New. The New Session Properties dialog box appears. On the Session tab, in the Session Caption box, type a session caption name such as Startup Events or Startup TACL. Click IO Properties. The TCP/IP Properties dialog box appears. Type the DNS name or IP address of the maintenance entity (ME) or integrated maintenance entity (IME), followed by a space, and the port number of the window type (303 for the startup event stream window, and 301 for the startup TACL window).
Table 15-2 Related Reading for Starting and Stopping a System (continued) For Information About Refer to Informing OSM of the location of an alternate system disk. OSM Service Connection online help See Saving (a disk-level action) or deleting (a system-level action) alternate system load volumes.
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” (page 174) — “Managed Configuration Services (MCS)” (page 174) — “Startup” (page 174) — “Shutdown” (page 174) — “For More Information ” (page 174) • “Processes That Represent the System Console” (page 174) — “$YMIOP.#CLCI” (page 174) — “$YMIOP.
— — “Spooler Shutdown File” (page 190) “TMF Shutdown File” (page 190) 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.
This process: • • Runs on the system console Is preconfigured on your system during system generation TACL processes are started on $YMIOP.#CLCI by commands in the CIIN file. If a read operation is pending, such as a TACL prompt on $YMIOP.#CLCI, write operations are blocked, causing the process attempting the write operation to wait indefinitely. $YMIOP.#CNSL $YMIOP.#CNSL is a write-only device for logging.
applicability of any example or sample program before placing the software into production use. • These examples are for a system whose configuration has been changed from the factory-installed configuration. Your system’s initial configuration will differ from these examples. The startup files in this section assume that the objects they start have already been added to the system configuration database. • • The IP addresses used in this section are examples only.
NOTE: By default, the CIIN file contains commands needed to start the (permanent) TACL process pair and to reload all the processors in the system. Do not place commands to prime the processors in the 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).
CONFTEXT CIIN Entry and CIIN File CIIN Option Results CONFTEXT has CIIN entry. Disabled Initial TACL process is started and left in logged-off state. You must log on to complete the system startup process. CONFTEXT has no CIIN entry. Enabled or disabled Initial TACL process is started and left logged on to the super ID (255,255). You must initiate the remainder of the system startup process manually and then log off.
Comment -- then terminate. Comment -- This file is used to reload the remaining processors and Comment -- start a TACL process pair for the system console. Comment -- Reload the remaining processors. RELOAD /TERM $ZHOME, OUT $ZHOME/ * Comment Comment Comment Comment Comment Comment Comment Comment Comment ---------- Use SCF to start a persistent TACL process pair for the system console TACL window.
NOTE: When using explicit names, you must revise your command files whenever a configuration change occurs. Therefore, you should balance the time it takes to update configuration files against the savings in startup or shutdown time. • Use single-line commands instead of multiple-line commands. Multiple-line commands in a command file increase execution time. Avoid Manual Intervention Write startup and shutdown files so that they execute correctly without requiring manual intervention.
How Process Persistence Affects Configuration and Startup When the system is started, all processes that are configured to be persistent are started automatically by the persistence manager ($ZPM) or by the subsystem manager, which is started by $ZPM. For example, when the system is started, the WAN subsystem manager automatically starts all WAN I/O processes (IOPs) that were started before the system was shut down. However, communications lines and paths must be started manually by the operator.
> OBEY $SYSTEM.STARTUP.STRTSYS Comment -- This is $SYSTEM.STARTUP.STRTSYS comment -- Start the server for labeled tape processing.
SCF / IN $SYSTEM.STARTUP.STRTLP, OUT $ZHOME / comment -- Start the Expand-over-IP line to \Case2 SCF / IN $SYSTEM.STARTUP.IP2CASE2, OUT $ZHOME / comment -- Start the direct-connect line SCF / IN $SYSTEM.STARTUP.STRTLH, OUT $ZHOME / 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.
The NonStop TCP/IPv6 subsystems participate in the system configuration database (however, not with the initial configuration database that is shipped with a new system). • • TCP/IP Configuration and Management Manual TCP/IPv6 Configuration and Management Manual 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.
+ ALTER SUBNET #SN1, SUBNETMASK %%hFFFFFF00 + ALTER SUBNET #LOOP0, IPADDRESS 127.1 + START SUBNET * + ADD ROUTE #GW, DESTINATION 0, GATEWAY [GW^ADDR], DESTTYPE BROADCAST + START ROUTE * + EXIT POP #INLINEPREFIX #OUTPUT #OUTPUT Starting Listner: [LST^NAME] LISTNER /NAME [LST^NAME], CPU [TCP^CPU1], PRI 160, NOWAIT, TERM [CON^NAME], HIGHPIN OFF/ $SYSTEM.ZTCPIP.
> SCF / IN $SYSTEM.STARTUP.STRTX25, OUT $ZHOME / == == == This is $SYSTEM.STARTUP.STRTX25 Starts the X.25 lines associated with the SWAN concentrator $ZZWAN.#S01 ALLOW 20 ERRORS START LINE $X25* 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.
== This is $SYSTEM.STARTUP.STRTLH START LINE $Case2elh 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.
comment -- Shut down the printer lines associated with the SWAN concentrator SCF/ IN $SYSTEM.SHUTDOWN.SDNLP, OUT $ZHOME / comment -- Shut down the Expand-over-IP line to \Case2 SCF/ IN $SYSTEM.SHUTDOWN.IP2CASE2, OUT $ZHOME / comment -- Shut down the Expand manager process, $ZEXP SCF/ IN $SYSTEM.SHUTDOWN.SDNEXP, OUT $ZHOME / comment -- Shut down the direct-connect line SCF/ IN $SYSTEM.SHUTDOWN.STRTLH, OUT $ZHOME / comment -- Drain the spooler subsystem using the SPOOLCOM command file comment -- SPLDRAIN.
X.25 Lines Shutdown File This example shows an SCF command file that stops the X.25 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.SDNX25, OUT $ZHOME / == This is $SYSTEM.SHUTDOWN.SDNX25 == == This shuts down the X.25 lines associated with the SWAN concentrator $ZZWAN.
== This is $SYSTEM.SHUTDOWN.STOPLH == This shuts down the direct-connect line ALLOW 20 ERRORS ABORT LINE $Case2elh 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.
17 Preventive Maintenance • • “When to Use This Section” (page 191) “Monitoring Physical Facilities” (page 191) — “Checking Air Temperature and Humidity” (page 191) — “Checking Physical Security” (page 191) — “Maintaining Order and Cleanliness” (page 191) — “Checking Fire-Protection Systems” (page 191) • “Cleaning System Components” (page 192) — “Cleaning an Enclosure” (page 192) — “Cleaning and Maintaining Printers” (page 192) — “Cleaning Tape Drives” (page 192) • “Handling and Storing Cartridge Tapes
Cleaning System Components This subsection contains basic information about cleaning enclosures, printers, and tape drives. Many companies have service-level agreements with HP that include regular preventive maintenance (PM) of their hardware components. If a Field Service Organization (FSO) representative handles cleaning and other preventive maintenance for your company, you need not be concerned with the cleaning tasks mentioned here.
NOTE: These precautions are extremely important to prevent damage: • Do not use cleaner solutions that contain lubricants. Lubricants deposit a film on the tape head and impair performance. • Do not use aerosol cleaners, even if they contain isopropyl alcohol. The spray is difficult to control and often contains metallic particles that damage the tape head. • Do not use soap and water on a tape path. Soap leaves a thick film, and water can damage electronic parts. • Do not use facial tissues.
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.
B Tools and Utilities for Operations When to Use This Appendix This appendix briefly describes the tools and utilities that might be available on your system to assist you in performing the operations tasks for an Integrity NonStop NS-series server. The use of some of these tools and utilities is discussed throughout this guide. For a list of other documentation that provides detailed information about these tools and utilities, refer to Appendix C, Related Reading.
Measure Use the Measure program to collect and display system performance statistics about processors, processes, communication and network lines, files, disks, and terminals. Operations management personnel often use Measure to help fine-tune and balance a system. MEDIACOM MEDIACOM is the operator interface to the Distributed Systems Management/Tape Catalog (DSM/TC). It allows you to perform routine tape and tape-drive management operations.
You can run SCF from any workstation or terminal on the system after you are logged on. Use SCF to: • Configure and add an object • Remove an object • Begin or restore access to an object • Stop access to an object • Show static configuration information for an object • Show dynamic information for an object • Automate subsystem startup and shutdown procedures • Power off the system HP Tandem Advanced Command Language (TACL) The TACL product is the command interface to the NonStop Kernel operating system.
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 Tool Documentation Description BACKCOPYBACKUPDCOMDSAP 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.
Table C-1 Related Reading for Tools and Utilities (continued) Tool Documentation Description OSM package OSM Service Connection User’s Guide (also available as online help within OSM Service Connection) This guide includes: • An overview of all OSM applications and components • How to use the OSM Service Connection (the primary OSM interface) to monitor and perform actions on system and cluster resources OSM Migration and Configuration Guide This guide includes: • Comparison of OSM and TSM software •
Table C-1 Related Reading for Tools and Utilities (continued) Tool Documentation Description RESTORE Guardian Disk and Tape Utilities Reference Manual This manual describes these disk and tape utilities: BACKCOPY, BACKUP, DCOM, DSAP, and RESTORE. This manual supports both D-series, G-series, and H-series RVUs. SPOOLCOM Spooler Plus Utilities Reference Manual This manual describes the spooler utilities—Peruse, SPOOLCOM, Font, and RPSetup— and presents the complete syntax for these utilities.
Table C-1 Related Reading for Tools and Utilities (continued) 204 Tool Documentation Description TACL TACL Reference Manual This manual provides information on using the TACL interface. TMFCOM TMF Operations and Recovery Guide This manual describes how to operate TMF and recover from error conditions. It is intended for those responsible for TMF system maintenance. TMF Reference Manual This manual describes how to use the TMFCOM command interface to TMF.
D Converting Numbers 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 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.
Figure D-1 Binary to Decimal Conversion 1. 2. 3. Take the rightmost binary digit and multiply it by the rightmost placeholder value. Moving to the left, take the next binary digit and multiply it by the next placeholder value. Continue to do this until the binary number has been exhausted. Add the multiplied values together. The result is: Binary Value Decimal Value %B11011 27 Octal to Decimal To convert an octal number to a decimal number: 1.
Figure D-2 Octal to Decimal Conversion 1. 2. 3. Take the rightmost octal digit and multiply it by the rightmost placeholder value. Moving to the left, take the next octal digit and multiply it by the next placeholder value. Continue to do this until the octal number has been exhausted. Add the multiplied values together. The result is: Octal Value Decimal Value %1375 765 Hexadecimal to Decimal To convert a hexadecimal number to a decimal number: 1.
Example Convert the hexadecimal value BA10 to its decimal equivalent. (In this example, the symbol “*” indicates multiplication.) Refer to Figure D-3 (page 208). Figure D-3 Hexadecimal to Decimal Conversion 1. 2. 3. Take the rightmost hexadecimal digit and multiply it by the rightmost placeholder value. 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.
3. 88/2 = 44 0 4. 44/2 = 22 0 5. 22/2 = 11 0 6. 11/2 = 5 1 7. 5/2 = 2 1 8. 2/2 = 1 0 9. 1/2 = 0 1 remainder = most significant (leftmost) digit The result is: Decimal Value Binary Value 354 %B101100010 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.
1. 2. 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.
Safety and Compliance This section 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.
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.
1M Laser Product in accordance with US FDA regulations and the IEC 60825-1. The product does not emit hazardous laser radiation. WARNING: Use the controls or adjustments or performance of procedures other than those specified herein or in the laser product’s installation guide may result in hazardous radiation exposure. To reduce the risk of exposure to hazardous radiation: • LASER RADIATION - DO NOT VIEW DIRECTLY WITH OPTICAL INSTRUMENTS. CLASS 1M LASER PRODUCT. • Do not try to open the module enclosure.
total combined leakage current should not exceed 5 percent of the rated input current for the device. “HIGH LEAKAGE CURRENT, EARTH CONNECTION ESSENTIAL BEFORE CONNECTING SUPPLY” “HOHER ABLEITSTROM. VOR INBETRIEBNAHME UNBEDINGT ERDUNGSVERBINDUNG HERSTELLEN” “COURANT DE FUITE E’LEVE’. RACCORDEMENT A LA TERRE INDISPENSABLE AVANT LE RACCORDEMENT AU RESEAU” FUSE REPLACEMENT CAUTION – For continued protection against risk of fire, replace fuses only with fuses of the same type and the same rating.
Index Symbols $SYSTEM, recovery operations for, 168 $YMIOP.#CLCI, 174, 176 $YMIOP.
SCF STATUS DISK command, 125 SCF STATUS LIF command, 81 SCF STATUS LINE command, 86 SCF STATUS PIF command, 81 SCF STATUS TAPE command, 138 start-of-shift checklist, 50 Expand-over-IP startup file, 186 F Fast Ethernet ServerNet adapter (FESA), 78 FCDM, 35 FCSA, 77 overview, 97 problems with, 99 states, 99 FESA, 78 Fibre Channel disk module (FCDM), 35 Fibre Channel ServerNet adapter (see FCSA) Fibre Channel ServerNet adapter (FCSA), 77 File Utility Program (FUP) description of, 197 INFO command, 118, 128 Fr
Octal to decimal conversion, 206 OSM CIIN file, 177 description of, 198 documentation, 202 guided procedures, 33 launching, 32 security, 178 using to monitor and resolve problems, 53 OSM Event Viewer, 69 Outages, planned, 164 halt code = %nn message, 109 recovery operations for, 110 Processors dumps (see Dumps) freeze (see Freeze) halt See Processor halts, 109 halting processors, 111 hang, 109 monitoring, 58 recovery operations for , 110 P R PAM, 78 Parallel Library TCP/IP, 42 PATHCOM, 147 PATHMON proce
spooler, 190 system shutdown file, 187 TMF, 190 X.25 lines, 189 SNAX/APN, 79 SPOOLCOM, 198 Spooler, 183, 190 Startup files about, 176 ATP6100 lines, 185 automating, 174 CIIN, 174 configuration database, 181 CP6100, 185 direct-connect, 186 Expand-over-IP, 186 invoking, 174 security, 181 sequence, 181 spooler warm start, 183 system startup file, 181 TCP/IP stacks, 181 TMF warm start, 183 X.
