HP NonStop S-Series Planning and Configuration Guide Abstract This guide explains how to plan for and configure HP NonStop™ S-series servers and how to plan and prepare your site, operational environment, and hardware and software configurations. In addition, the guide describes the ServerNet system area network (ServerNet SAN) and the available hardware and system configurations. It also provides a glossary, a parts list, and a guide to other NonStop S-series manuals. Product Version N.A.
Document History Part Number Product Version Published 523303-010 N.A. April 2004 523303-011 N.A. April 2004 523303-012 N.A. June 2004 523303-014 N.A. September 2004 523303-015 N.A.
HP NonStop S-Series Planning and Configuration Guide Glossary Index What’s New in This Guide xv Manual Information xv New and Changed Information xvi About This Guide xvii Who Should Use This Guide xvii What’s in This Guide xvii Where to Get More Information xvii Notation Conventions xviii Part I. Reference Information 1.
Terms and Concepts (continued) Contents Terms and Concepts (continued) Components 1-7 Components, Processor Enclosure Without Power Shelf, Appearance Side 1-7 Components, Processor Enclosure Without Power Shelf, Service Side 1-8 Components, I/O Enclosure Without Power Shelf, Appearance Side 1-9 Components, I/O Enclosure Without Power Shelf, Service Side 1-10 Components, Processor Enclosure With Power Shelf, Appearance Side 1-11 Components, Processor Enclosure With Power Shelf, Service Side 1-12 Components
Terms and Concepts (continued) Contents Terms and Concepts (continued) Subsystem Control Facility (SCF) 1-37 HP Tandem Failure Data System (TFDS) 1-38 Hardware Tools 1-38 ServerNet Architecture 1-39 ServerNet Adapter 1-40 ServerNet Addressable Controller (SAC) 1-40 ServerNet Link 1-41 ServerNet Node 1-41 ServerNet Packet 1-41 ServerNet Router 1-41 Wormhole Routing 1-42 ServerNet Fabric 1-43 Networking 1-43 Ethernet 1-43 Protocols 1-44 IP Addresses 1-45 2.
4. System Components Contents Tetra 16 Topology Features 3-13 ServerNet Topology Configuration 3-14 Where the ServerNet Topology Configuration Value Is Stored 3-14 The ServerNet Topology Configuration Value and CRU Replacement 4.
5. ServerNet Cabling Contents Plug-in Cards 4-62 Typical PIC Installations 4-63 System Console 4-66 Tape Drives 4-68 SWAN Concentrators 4-69 External Disk Drives 4-69 ServerNet Clusters 4-69 IOAM Enclosures 4-69 Components 4-70 Group, Module, and Slot Hierarchy for IOAM Enclosures 4-72 5.
6. ServerNet Communication Pathways Contents 6.
9.
Contents 10.
11. Planning for LAN Communications Contents Configuring the Maximum Power-Fail Delay Time Battery Considerations 10-7 10-7 11.
13. Completing the Installation Plan Contents 13.
A. Part Numbers Contents TSM Package 15-9 Creating an Alternate System Disk 15-10 Startup and Shutdown Files 15-10 Automating System Startup 15-10 Automating System Shutdown 15-11 Processes That Represent the System Console CIIN File 15-11 Process Persistence 15-11 Adding Super-Group User IDs 15-12 15-11 Part III. Appendixes A.
B. Specifications Contents Ethernet Switches and Hubs A-20 Modems and Modem Cable A-20 Universal Modem and Its AC Power Cords A-22 IOAM Products A-24 Cables and Cable Assemblies A-26 AC Power Cords, Enclosures Without Power Shelves A-29 AC Power Cords, Enclosures With Power Shelves A-30 B.
C. Blank Forms Contents C. Blank Forms D. Case Study: ServerNet Cable Lengths Hardware Configuration D-1 Choosing Cable Lengths D-2 Installation Document D-4 E.
G. Modular Power Information Contents G.
What’s New in This Guide Manual Information HP NonStop S-Series Planning and Configuration Guide Abstract This guide explains how to plan for and configure HP NonStop™ S-series servers and how to plan and prepare your site, operational environment, and hardware and software configurations. In addition, the guide describes the ServerNet system area network (ServerNet SAN) and the available hardware and system configurations.
New and Changed Information What’s New in This Guide New and Changed Information This manual includes the following new and changed information: Section Changed Contents To be updated. What’s New in This Guide This section. Section 1, Terms and Concepts Corrected illustration of IOAM enclosure in a rack and added the ERM to the list of FRUs. Added virtual tape drives to the list of FRUs. Section 3, Topologies Clarified information about IOAM configurations in a system.
About This Guide This section offers a general overview of this guide, describes this guide’s intended audience, and explains the contents of each section of this guide. Who Should Use This Guide This guide is written for those who are responsible for planning the installation, configuration, and maintenance of the server and the software environment at a particular site.
Notation Conventions About This Guide Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
General Syntax Notation About This Guide { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line.
Notation for Messages About This Guide Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [ , attribute-spec ]… !i and !o.
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.
Notation for Management Programming Interfaces About This Guide Notation for Management Programming Interfaces This list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual. UPPERCASE LETTERS. Uppercase letters indicate names from definition files. Type these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters.
Part I. Reference Information This part provides information about the organization, physical arrangement, and configurations that are possible with the NonStop S-series servers. The information is descriptive rather than task oriented. Section Title Abstract 1 Terms and Concepts This section defines basic terms and concepts associated with NonStop S-series servers, the ServerNet architecture, and networking.
Part I.
1 Terms and Concepts NonStop S-Series Servers 1-1 Enclosures 1-2 Components 1-7 Cluster Switch Enclosure 1-16 IOAM Enclosure Components 1-17 CRU Identification, System Enclosures 1-21 FRU Identification, IOAM Enclosures 1-23 CRUs and FRUs 1-26 CRU/FRU Replacement Tools 1-30 ServerNet Architecture 1-39 Networking 1-43 NonStop S-Series Servers Server Description S74 Limited to two processors S76 Limited to two processors S700 Limited to two processors S740 Limited to two proce
Enclosures Terms and Concepts Enclosures Enclosure 1-2 System Enclosure 1-2 Base Enclosure 1-3 Stackable Enclosure 1-3 Processor Enclosure 1-3 I/O Enclosure 1-3 Modified I/O Enclosure 1-3 IOAM Enclosure 1-3 Peripheral Enclosure 1-4 Cluster Switch Enclosure 1-4 Visual Image Package 1-4 Power Shelf 1-4 Appearance Side and Service Side 1-5 Enclosure Arrangements 1-5 Enclosures and Power Shelf 1-6 Note.
Terms and Concepts Base Enclosure Base Enclosure A base enclosure is an enclosure that is mounted on a frame base with casters and is installed directly on the floor. It can have another enclosure stacked on top of it. Stackable Enclosure A stackable enclosure is an enclosure that is installed on top of a base enclosure and is not mounted on a frame base. Processor Enclosure A processor enclosure is a system enclosure that contains processor multifunction (PMF) CRUs.
Terms and Concepts Peripheral Enclosure IOAM enclosures connect to an MSEB of S76000 and later NonStop S-series systems and can be installed in place of I/O enclosure in groups 11, 12, 13, 14, or 15. I/O enclosures and IOAM enclosures can coexist in the same system. For more information, see IOAM Enclosures on page 4-69 or the Modular I/O Installation and Configuration Guide. Peripheral Enclosure A peripheral enclosure is an enclosure that contains components related to peripheral devices.
Terms and Concepts Appearance Side and Service Side Appearance Side and Service Side All system enclosures have an appearance side and a service side: • • The appearance side of an enclosure contains disk drives. System enclosures are usually arranged so that the appearance side is the most visible side. The appearance side is covered with a door, which must remain closed during normal operation to ensure proper cooling.
Enclosures and Power Shelf Terms and Concepts Enclosures and Power Shelf The type of PMF CRU or IOMF CRU determines whether a power shelf is required: CRU Type Does Not Require Power Shelf Requires Power Shelf S74 PMF X S76 PMF X S700 PMF X (with NSR-W) X (with NSR-G or NSR-T) S740 PMF X S760 PMF X S7000 PMF X S7400 PMF X S7600 PMF X S7800 PMF X S70000 PMF X S72000 PMF X S74000 PMF X S76000 PMF X S78000 PMF X S86000 PMF X S88000 PMF X IOMF IOMF 2 X X HP NonStop S-Seri
Components Terms and Concepts Components Components, Processor Enclosure Without Power Shelf, Appearance Side Group Service LED 01 02 03 04 05 06 07 08 11 12 13 14 15 16 17 18 09 19 10 20 21 22 23 28 24 25 26 27 VST950.
Components, Processor Enclosure Without Power Shelf, Service Side Terms and Concepts Components, Processor Enclosure Without Power Shelf, Service Side 50 55 Even-Numbered Processor Odd-Numbered Processor 51 52 53 54 56 Group ID Label Group Service LED Module ID Label VST621.
Components, I/O Enclosure Without Power Shelf, Appearance Side Terms and Concepts Components, I/O Enclosure Without Power Shelf, Appearance Side The appearance side of an I/O enclosure without a power shelf is identical to that of a processor enclosure without a power shelf. Group Service LED 01 02 03 04 05 06 07 08 11 12 13 14 15 16 17 18 09 19 10 20 21 22 23 28 24 25 26 27 VST950.
Components, I/O Enclosure Without Power Shelf, Service Side Terms and Concepts Components, I/O Enclosure Without Power Shelf, Service Side 50 55 51 52 53 54 Connects to X Fabric Connects to Y Fabric 56 Group ID Label Group Service LED Module ID Label VST971.
Components, Processor Enclosure With Power Shelf, Appearance Side Terms and Concepts Components, Processor Enclosure With Power Shelf, Appearance Side Group Service LED 01 02 03 04 05 06 07 08 11 12 14 15 17 18 13 16 09 19 10 20 21 22 23 28 24 25 26 27 29 30 31 32 VST622.
Components, Processor Enclosure With Power Shelf, Service Side Terms and Concepts Components, Processor Enclosure With Power Shelf, Service Side The PMF CRUs on your NonStop server might appear slightly different from those shown here. 50 55 51 52 53 54 Group Service LED 56 Module ID Label Group ID Label VST623.
Components, I/O Enclosure With Power Shelf, Appearance Side Terms and Concepts Components, I/O Enclosure With Power Shelf, Appearance Side The appearance side of an I/O enclosure with a power shelf is identical to that of a processor enclosure with a power shelf. Group Service LED 01 02 03 04 05 06 07 08 11 12 14 15 17 18 13 16 09 19 10 20 21 22 23 28 24 25 26 27 29 30 31 32 VST622.
Components, I/O Enclosure With Power Shelf, Service Side Terms and Concepts Components, I/O Enclosure With Power Shelf, Service Side 50 Connects to X Fabric 55 51 52 53 54 Connects to Y Fabric 56 Group ID Label Module ID Label Power Shelf Group Service LED VST402.
Terms and Concepts Components in NonStop S76000, S86000, and Later Configurations Components in NonStop S76000, S86000, and Later Configurations NonStop S76000 and S86000 servers use the G06.16 RVU and later. The NonStop S88000 uses the G06.24 RVU and later. These conditions apply to the NonStop S7800, S76000, S86000, and later servers: • • • • MSEBs are required in slots 51 and 52 of all processor enclosures, 01 through 08.
Cluster Switch Enclosure Terms and Concepts Cluster Switch Enclosure In addition to system enclosures, a NonStop cluster switch enclosure houses the ServerNet cluster components: The cluster switch enclosure is half the height of a standard NonStop S-series system enclosure. VST 012 .vsd For information about ServerNet clusters, see the ServerNet Cluster Manual.
Terms and Concepts IOAM Enclosure Components IOAM Enclosure Components An IOAM enclosure provides you with access to other storage options. It is mounted in a modular cabinet and connects to the MSEB of S76000 and later NonStop S-series systems. Up to three IOAM enclosures, a maintenance switch, a power distribution unit (PDU), and a UPS can be installed inside one cabinet. An IOAM enclosure is 10 rack units (U) high.
Terms and Concepts Related Components Related Components These components are used in conjuction with IOAM enclosures: • • • • Maintenance switch Modular cabinet Power distribution unit (PDU) UPS For additional information, see IOAM Enclosures on page 4-69.
IOAM Enclosure in a Standard 19-Inch Rack (Front) Terms and Concepts IOAM Enclosure in a Standard 19-Inch Rack (Front) IOAM Enclosure 42 42 41 41 40 40 39 39 38 38 37 37 36 36 35 35 34 34 33 33 32 32 31 31 30 30 29 29 28 28 27 27 26 26 25 25 24 24 23 23 22 22 21 21 20 20 19 19 18 18 17 17 16 16 15 15 14 14 13 13 12 12 11 11 10 10 09 09 08 08 07 07 06 06 05 05 04 04 03 03 02 02 01 01 Fans Power Suppl ies Extended Run-Ti
IOAM Enclosure in a Standard 19-Inch Rack (Rear) Terms and Concepts IOAM Enclosure in a Standard 19-Inch Rack (Rear) This figure shows an optional UPS installed.
CRU Identification, System Enclosures Terms and Concepts CRU Identification, System Enclosures Customer-replaceable units (CRUs) are hardware components that can be serviced and replaced by customers. Not all components in a system enclosure are CRUs. CRUs are identified by their physical location in a processor enclosure or I/O enclosure: their group, module, and slot numbers. Group A group consists of all components accessible to a pair of service processors (SPs) in a system enclosure.
CRU Identification Terms and Concepts This figure shows the complete CRU identification of a disk drive located in slot 03 of group 02. 02 MODULE 01 01 Group 02, Module 01, Slot 03 SLOT 01 02 03 04 05 06 03 VST602.
Terms and Concepts FRU Identification, IOAM Enclosures FRU Identification, IOAM Enclosures Field-replaceable units (FRUs) are hardware components that can be serviced only by service providers trained by HP. All components in an IOAM enclosure are FRUs. FRUs are identified by their physical location in an enclosure by their group, module, and slot numbers. Group A group consists of all components in an IOAM enclosure and derives its number from the processor enclosure to which it is cabled.
Terms and Concepts Group, Module, and Slot Numbers; Front of Modular Cabinet Group, Module, and Slot Numbers; Front of Modular Cabinet 42 42 41 41 40 40 39 39 38 38 37 36 35 37 Fans (Module 3) Fans (Module 2) 34 IOAM Enclosure (Group 12) 33 Slot 17 Slot 17 32 31 31 30 30 29 28 29 Sl ot 16 Slot 16 27 25 24 28 27 26 26 Power Supplies Modules 2 and 3 25 24 23 23 22 22 21 21 20 20 19 18 Fans (Modul e 3) Fans (Module 2) 17 16 15 IOAM Enclosure (Group 11) 35 34 33 3
Terms and Concepts Group, Module, and Slot Numbers; Rear of Modular Cabinet Group, Module, and Slot Numbers; Rear of Modular Cabinet 42 42 41 41 40 40 39 39 38 38 37 37 36 36 35 35 34 34 33 33 32 32 31 Slot 5 Slot 4 Slot 3 Slot 2 Slot 5 Slot 1 Slot 4 Slot 3 Slot 2 29 Slot 1 28 27 28 27 26 26 25 25 24 24 23 Slot15 Slot 18 Slot15 Slot18 23 22 Module 2 Module 3 22 Power Suppli es 21 21 20 20 19 19 18 18 17 17 ServerNet Swi tch Board (Module 2, Slot 14
Terms and Concepts CRUs and FRUs CRUs and FRUs NonStop S-series system hardware components are divided into two categories: CRUs and field-replaceable units (FRUs). CRUs CRUs are divided into three service classes: Class-1, Class-2, and Class-3 CRUs. Class-1 CRUs A Class-1 CRU probably will not cause a partial or total system outage if the documented replacement procedure is not followed correctly. Customers replacing a Class-1 CRU are not required to have previous experience with replacing CRUs.
Terms and Concepts Class-2 CRUs A Class-2 CRU might cause a partial or total system outage if the documented replacement procedure is not followed correctly. Customers replacing a Class-2 CRU should have either three or more months’ experience with replacing CRUs or the equivalent training.
Terms and Concepts CRUs Class-3 CRUs A Class-3 CRU can cause a partial or total system outage if the documented replacement procedure is not followed correctly. Customers replacing Class-3 CRUs should have either six or more months of experience with replacing CRUs or equivalent training.
Terms and Concepts FRUs FRUs These system hardware components are field-replaceable units (FRUs), which must be serviced only by HP authorized service providers.
Terms and Concepts CRU/FRU Replacement Tools Power monitor and control units (PMCUs) Power shelves 6740 ServerNet/FX adapters 6742 ServerNet/FX 2 adapters Tape drives: 5159 5257 5259 9490 CT9841FC-x VT5xxx virtual tape Tape libraries: 4400 9310 9710 L700 Uninterruptible power supply (UPS) Extended run-time module (ERM) CRU/FRU Replacement Tools You use the following software and hardware tools to diagnose and replace failed CRUs/FRUs: CSSI Web 1-30 Service Management Packages 1-31 OSM Guided Procedur
Terms and Concepts • • Service Management Packages Channel Partners and Authorized Service Providers: Order the CD from the SDRC at https://scout.nonstop.compaq.com/SDRC/ce.htm. HP employees: Subscribe at World on a Workbench (WOW). Subscribers automatically receive CD updates. Access the WOW order form at http://hiimpact.americas.cpqcorp.net/wow/order.asp. Note. After G06.23, a snapshot of the CSSI Web is no longer included on the system console installer CD.
Terms and Concepts TSM Guided Procedures Add Node to ServerNet Cluster The OSM equivalent to the Configure ServerNet Node is to use the Add Node to ServerNet Cluster action from the System object within the OSM Service Connection. CRU/FRU Replacement To replace a PMF CRU, IOMF CRU, SEB or MSEB, power supply, ServerNet device adapter (ServerNet/DA), FCSA, IOAM enclosure, ServerNet switch board, or cluster switch, perform an action from the OSM Service Connection: 1.
Terms and Concepts TSM Guided Procedures The guided procedures automate many of the repetitive subtasks and verifications involved in CRU replacement. They also assist you in performing manual subtasks required to replace a CRU online while maintaining the system availability.
Terms and Concepts TSM Guided Procedures Access the Add Switch guided procedure from the taskbar on your system console: Start > Programs > Compaq TSM > Guided Configuration Tools > Add Switch Configure ServerNet Node This guided procedure helps you prepare a server to become a node in a ServerNet cluster. For more information about ServerNet clusters, refer to the ServerNet Cluster Manual.
Terms and Concepts TSM Guided Procedures Start > Programs > Compaq TSM > Guided Replacement Tools > Replace PMF Replace Power Supply Replace Power Supply is the supported method for replacing a power supply in a power shelf on systems running G06.13 and later RVUs.
Terms and Concepts WAN Wizard Pro SWAN Fast Firmware Update SWAN Fast Firmware Update guides you through the process of updating the firmware on the communication line interface processors (CLIPs) residing in a ServerNet wide area network (SWAN or SWAN 2) concentrator box. The SWAN Fast Firmware Update procedure can be launched only from within the TSM Service Application. No Start menu entry is available.
Terms and Concepts • • Subsystem Control Facility (SCF) TR3271 X25AM input/output processes (IOPs) LAN adapters, including • • • • • • ATM 3 ServerNet adapters (ATM3SAs) Common Communication ServerNet adapters (CCSAs) Ethernet 4 ServerNet adapters (E4SAs) Fast Ethernet ServerNet adapters (FESAs) Token-Ring ServerNet adapters (TRSAs) Gigabit Ethernet ServerNet adapters (GESAs) Access WAN Wizard Pro from the taskbar on your system console. For G06.
Terms and Concepts HP Tandem Failure Data System (TFDS) HP Tandem Failure Data System (TFDS) The HP Tandem Failure Data System (TFDS) isolates software problems and provides automatic processor-failure data collection, diagnosis, and recovery services. For more information on TFDS, refer to the Tandem Failure Data System (TFDS) Manual.
Terms and Concepts ServerNet Architecture ServerNet Architecture ServerNet Adapter 1-40 ServerNet Addressable Controller (SAC) 1-40 ServerNet Link 1-41 ServerNet Node 1-41 ServerNet Packet 1-41 ServerNet Router 1-41 Wormhole Routing 1-42 ServerNet Fabric 1-43 HP NonStop S-Series Planning and Configuration Guide —523303-015 1- 39
Terms and Concepts ServerNet Adapter ServerNet Adapter A ServerNet adapter provides the interface between a ServerNet fabric and an I/O bus such as a SCSI bus. A ServerNet adapter contains a ServerNet bus interface (SBI) and one or more ServerNet addressable controllers (SACs).
Terms and Concepts ServerNet Link ServerNet Link A ServerNet link consists of two unidirectional point-to-point communication paths, one in each direction. A ServerNet link connects a ServerNet router to: • • A ServerNet node Another ServerNet router ServerNet Node A ServerNet node is a system in a ServerNet cluster. ServerNet nodes send and receive ServerNet packets. ServerNet Packet ServerNet packets are sent and received by ServerNet nodes.
Terms and Concepts Wormhole Routing Wormhole Routing Wormhole routing is a technique for routing ServerNet packets through ServerNet routers. Packets are immediately switched to the appropriate output ports as soon as they arrive at the router.
Terms and Concepts ServerNet Fabric ServerNet Fabric A ServerNet fabric is a collection of connected routers and ServerNet links that form an internal or external network. Two separate, identically configured fabrics, called the X fabric and the Y fabric, together provide a fault-tolerant interconnection for the ServerNet network. Each processor connects to both fabrics. Typically, ServerNet adapters also connect to both fabrics.
Terms and Concepts Protocols Protocols Transmission Control Protocol (TCP) Transmission Control Protocol (TCP) is a connection-oriented protocol that provides for the reliable exchange of data between a sending and a receiving system, no matter how many intermediate nodes the data traverses. TCP regards the data as a stream of bytes (it is not record-oriented) and guarantees that all data sent is received by the destination system and arrives in the order in which it was sent.
Terms and Concepts IP Addresses Point-to-Point Protocol (PPP) Point-to-Point Protocol (PPP) provides a standard method for encapsulating information over point-to-point links. Remote Procedure Call (RPC) Remote Procedure Call (RPC) is a protocol that extends a procedure-call form of process-to-process communication to a network environment. RPC is a way for programs running on client computers to invoke the services of a program running on a server computer.
Terms and Concepts IP Addresses IP Address Syntax An IP address is a 32-bit numeric value. IP addresses are typically represented by converting the bits to decimal values an octet (8 bits) at a time and separating each octet’s decimal value by a period (.). This is referred to as dot notation, or dotted decimal format. IP addresses are typically of the following form: n.n.n.n where n is a number in the range 0 through 255.
Terms and Concepts IP Addresses For example, to determine the network address and local address from the IP address 192.6.1.1: Indicates Class C 11000000.00000110.00000001.00000001 Network Address = 192.6.1 Local Address = 1 VST915.vsd The number of networks and hosts and the address ranges for each IP address class are: Address Class Number of Networks Number of Hosts/Network Address Range A 127 16,777,215 0.0.0.0-127.255.255.255 B 16,383 65,535 128.0.0.0-191.255.255.
Terms and Concepts IP Addresses Domain Name Servers Every domain is served by a domain name server. A domain name server takes host names and converts them into IP addresses (name-to-IP-address mapping). You are not required to use a domain name server unless your network connects to the Internet. In that case you must use a domain name server. Host Tables If your system is on a small, isolated network, it is possible to map host names to IP addresses using a host table.
Terms and Concepts IP Addresses identify the host number. The subnet mask consists of thirteen 1s (corresponding to 8 bits of network address and 5 bits of subnet address) followed by nineteen 0s. Class A IP Address Bit 8 0 Network Address 0 12 16 24 31 Local Address Subnet Address Host Number Subnet Mask Bit 0 8 11111111 12 16 24 31 111110000000000000000000 Dotted Decimal Equivalent of Subnet Mask 255 248 0 0 VST914.
Terms and Concepts IP Addresses This figure shows the effect of applying the subnet mask 255.248.0.0 to the Class A IP address 73.18.11.135: Dotted Decimal Format IP Address 73 18 11 135 IP Address in Binary Bit 8 0 01001001 12 00010 010 16 00001011 24 31 10000111 Subnet Mask Bit 8 0 11111111 12 11111 000 Full Subnet Address = 73.2 16 00000000 24 31 00000000 Host Number = 2.11.135 VST916.
2 The ServerNet Communications Network The ServerNet communications network is a low-cost, high-speed network within a NonStop S-series system that connects processors to each other and to peripheral controllers. This network offers the interconnectivity of a standard network, but does not depend on shared resources such as interprocessor buses or I/O channels.
The ServerNet Communications Network Flexibility of the ServerNet Architecture Flexibility of the ServerNet Architecture Concurrent Messages The ServerNet communications network allows many messages to be sent concurrently. Processors and I/O devices communicate over point-to-point ServerNet links connected by ServerNet routers, which are crossbar switches that can simultaneously connect any input with any output.
The ServerNet Communications Network Diagramming the ServerNet Communications Network Diagramming the ServerNet Communications Network You can represent the ServerNet communications network in simplified and detailed logical diagrams (also called ServerNet diagrams). Simplified Logical Diagrams Use simplified logical diagrams when it is not important to show the exact paths between endpoints on the ServerNet communications network, such as when diagramming the ServerNet architecture of an entire system.
The ServerNet Communications Network Detailed Logical Diagrams Detailed Logical Diagrams Use detailed logical diagrams when it is important to show the details of the ServerNet links and routers. The X or Y fabric is represented by a collection of circles and lines that represent individual routers and ServerNet links. This figure is a detailed logical diagram of typical two-processor systems, one using ServerNet router 1s, the other using ServerNet router 2s.
The ServerNet Communications Network Detailed Logical Diagrams This figure is a detailed logical diagram of a four-processor system. Processor X Processor Y X 2 Processor Y X 2 2 Y X ServerNet Adapter ServerNet Adapter ServerNet Adapter MSEB Disks ServerNet Adapter 2 2 MSEB MSEB Y 2 ServerNet Adapter MSEB ServerNet Adapter Processor 2 2 ServerNet Adapter Disks ServerNet Adapter VST111.
The ServerNet Communications Network Detailed Logical Diagrams This figure is a detailed logical diagram of a two-processor system connected to an I/O adapter module (IOAM) enclosure. Processor X Y Processor X 2 Y 2 PMF 2 CRU MSEB ServerNet Switch Board X F C S A F C S A F C S A F C S A IOAM F C S A MSEB ServerNet Switch Board Y F C S A F C S A F C S A F C S A F C S A IOAM VST299.
The ServerNet Communications Network How Logical Diagrams Relate to Server Hardware How Logical Diagrams Relate to Server Hardware This illustration of a processor enclosure shows the location of the hardware components that support the ServerNet communications network. These hardware components are described in detail in Section 4, System Components. PMF CRU SEB Disk Drive ServerNet Adapter Service Side Appearance Side VST503.
The ServerNet Communications Network How Logical Diagrams Relate to Server Hardware This figure shows these individual hardware components and how they are symbolized in a logical diagram. Processor X Y Processor X Y SEB X ServerNet Adapter Y ServerNet Adapter SEB ServerNet Adapter SEB SCSI SACs PMF CRU Disks SCSI SACs PMF CRU Disk Drive PMF CRU Notes: The logical symbols illustrate only the hardware components of the ServerNet communications network, not an entire enclosure.
The ServerNet Communications Network How Logical Diagrams Relate to Server Hardware This figure shows the individual hardware components in an IOAM enclosure and how they are symbolized in a logical diagram.The IOAM enclosure hardware components are described in detail in Section 4, System Components.
The ServerNet Communications Network Comparison to NonStop K-Series Systems Comparison to NonStop K-Series Systems On both NonStop K-series systems and systems that use the ServerNet architecture: • • • The disk drives are connected with a SCSI bus. Each processor maintains two independent paths to other processors. No single failure disrupts communications among the remaining system components.
3 Topologies This section introduces the concept of the tetrahedral topology and describes the ServerNet topologies available on NonStop S-series servers. Note. I/O adapter module (IOAM) enclosures are supported by NonStop S76000 and later NonStop S-series systems in Tetra 8 and Tetra 16 topologies.
Topologies Tetrahedral Topology The disadvantage of the tetrahedral topology is an increase in the number of cabling paths. Four enclosures in a tetrahedral topology require six instead of a minimal three paths for an inline topology. Note. The figures in this section are symbolic; they do not represent the actual wiring or enclosure placement for a server. 01 03 02 04 Inline Topology 02 01 02 04 03 03 01 Square Topology 01 04 02 Wye Topology 04 03 Tetrahedral Topology VST960.
Topologies ServerNet Topologies ServerNet Topologies The ServerNet topologies are based on the tetrahedral topology. The connections between the first four processor enclosures of a system form a tetrahedron. Tetrahedron VST949.vsd If a system has more than four processor enclosures, each additional enclosure is connected to one of the first four enclosures, at a vertex or corner of the tetrahedron. See page 3-5. I/O enclosures and IOAM enclosures are connected to processor enclosures.
Topologies Tetra 8 Topology Tetra 8 Topology The Tetra 8 topology supports a maximum of four processor enclosures (eight processors). Each processor enclosure can have up to two I/O enclosures connected to it, for a maximum of eight I/O enclosures. One or both I/O enclosures connected to group 01 can be replaced by IOAM enclosures. I/O Enclosures ServerNet Cables Processor Enclosures VST951.
Topologies Tetra 16 Topology Tetra 16 Topology The Tetra 16 topology builds on the Tetra 8 topology to a maximum of eight processor enclosures (16 processors). Each of the four processor enclosures that make up the Tetra 8 tetrahedron can have one processor enclosure connected to it. Processor Enclosures ServerNet Cables VST952.vsd In the Tetra 16 topology, the maximum number of I/O enclosures supported varies with the server model. A maximum of five IOAM enclosures are supported.
Topologies Tetra 16 Topology The first four processor enclosures form the inner tetrahedron. The rest of the processor enclosures form the outer tetrahedron. Outer tetrahedron Inner tetrahedron VST956.vsd The inner tetrahedrons are made up of groups 01, 02, 03, and 04, and the outer tetrahedrons of groups 05, 06, 07, and 08.
Topologies Tetra 16 Topology In the NonStop S7000, S7400, S7600, and S7800 servers, each processor enclosure in both the inner and outer tetrahedrons can have at most two I/O enclosures connected to it, for a maximum of 16 I/O enclosures. I/O Enclosure Processor Enclosure ServerNet Cables VST953.
Topologies Tetra 16 Topology In a NonStop Sxx000 system, each processor enclosure in the inner tetrahedron can have up to five I/O enclosures connected to it, and each processor enclosure in the outer tetrahedron can have up to four I/O enclosures connected to it. Therefore, the Tetra 16 topology allows a maximum of 36 I/O enclosures. NonStop systems populated by S76000 processors or higher, any or all of the I/O enclosures attached to group 01 can be replaced by IOAM enclosures.
Topologies Topology Configuration Considerations Topology Configuration Considerations Considerations for planning or changing the size or topology of your system: • • • • • • • • • • • • • Processors are always installed in pairs, two processors in each processor enclosure. A Tetra 8 system can have one through four processor enclosures (two through eight processors). You can add processor enclosures to a Tetra 8 system until the maximum of four processor enclosures (eight processors) is reached.
Topologies Topology Configuration Considerations IOAM Enclosure Group I/O Enclosure Groups Not Allowed 11 21, 31, 41 12 22, 32, 42 13 23, 33, 43 14 24, 34, 44 15 25, 35, 45 Caution. IOAM enclosures must be installed and cabled by HP trained service providers. Information is available to your HP trained service provider in the Modular I/O Installation and Configuration Guide.
Topologies Comparing the Tetra 8 and Tetra 16 Topologies Comparing the Tetra 8 and Tetra 16 Topologies A system that contains more than eight processors must be configured as a Tetra 16 topology. However, a system that contains eight processors or fewer can be configured as either a Tetra 8 topology or a Tetra 16 topology. Depending on how you use your system, one topology is likely to be more efficient than the other for your needs.
Topologies Tetra 16 Topology Configurations Tetra 16 Topology Configurations All tetra-16 systems have a maximum of 8 processor enclosures with 16 processors. S7x00 systems have a maximum of 16 I/O enclosures and S7x000 systems have a maximum of 36 I/O enclosures.
Topologies Tetra 8 Topology Features Tetra 8 Topology Features Feature Implications Up to four processor enclosures are supported. Expansion beyond four processor enclosures requires a topology change. Each processor enclosure can support up to two I/O enclosures. Expansion beyond eight I/O enclosures requires a topology change. Processor enclosure slots 51 and 52 can contain SEBs or MSEBs. These SEBs or MSEBs support I/O enclosures. I/O enclosures multiply the number of available adapter slots.
Topologies ServerNet Topology Configuration Feature Implications (page 2 of 2) In the outer tetrahedron, groups 05 through 08: Processor enclosure slots 51 and 52 always contain SEBs or MSEBs. These SEBs or MSEBs maintain ServerNet connections between the processor enclosure on the outer tetrahedron and its associated processor enclosure on the inner tetrahedron. Only one ServerNet connector on each SEBs or MSEBs is used for this purpose.
Topologies The ServerNet Topology Configuration Value and CRU Replacement The ServerNet Topology Configuration Value and CRU Replacement When power is first applied to a PMF CRU, IOMF CRU, SEB, or MSEB, its ServerNet router is initialized. This can occur when the entire enclosure is first powered on or when one of these CRUs is inserted into a powered enclosure, such as during online CRU replacement.
Topologies The ServerNet Topology Configuration Value and CRU Replacement HP NonStop S-Series Planning and Configuration Guide—523303-015 3- 16
4 System Components This section describes the components of a NonStop S-series system. Appearance Side of System Enclosures 4-1 Service Side of System Enclosures 4-16 System Console 4-66 Tape Drives 4-68 SWAN Concentrators 4-69 External Disk Drives 4-69 ServerNet Clusters 4-69 IOAM Enclosures 4-69 Appearance Side of System Enclosures The appearance side of a system enclosure contains slots for these components: Note. For information about IOAM enclosures, see IOAM Enclosures on page 4-69.
System Components Appearance Side of System Enclosures Slot Numbers on Appearance Side of a System Enclosure 01 02 03 04 05 06 07 08 11 12 14 15 17 18 13 16 09 19 10 20 21 22 23 28 24 25 26 27 29 30 31 32 VST622.
System Components Group ID Label Group ID Label On the appearance side, the group ID label is visible through the enclosure door faceplate. This label identifies the group number associated with this system enclosure. For more information, see Group ID Switches on page 4-10. Group ID Label 02 VST706.
System Components Group Service LED Group Service LED On the appearance side, a group service light-emitting diode (LED) is located at the top of the enclosure. The group service LED, when lit, indicates one of the following: • • A command to light the group service LED was issued using the OSM Service Connection or the TSM Service Application. The group ID for this group either could not be determined or conflicts with the group ID of another group in the system.
System Components Disk Management The faceplate of a disk drive includes: • • • A write-on label and a part number/barcode label A green LED at the top that, when lit, indicates that the disk drive is operational. A yellow or amber LED on the lower half that indicates disk activity. Disk drive slots are divided between two SCSI buses.
System Components Disk Management SCSI ID Primary Slot Mirror Slot (page 2 of 2) 5 3 4 8 5 6 9 7 8 Ensure That Alternate Volume Names Are Unique If two disks share the same volume name and alternate volume name, you cannot access both of those disks at the same time. This restriction also applies to $SYSTEM. To ensure that both $SYSTEM volumes are always accessible, verify that every disk in the system has a unique alternate volume name.
System Components 36-GB Disk Drive Requirement 36-GB Disk Drive Requirement A minimum of a 36-GB disk drive is required in 16-GB NonStop S76000 and S86000 servers to receive memory dumps. 20 GB is reserved for memory dump. The remaining storage space can be used for anything. This disk does not have to be $SYSTEM. SCSI Terminators Four SCSI terminators are located in slots 09, 10, 19, and 20. Each SCSI bus requires two terminators for proper operation.
System Components Power Monitor and Control Units (PMCUs) Power Monitor and Control Units (PMCUs) Two power monitor and control units (PMCUs) are located in slots 21 and 22 behind the battery retainer. PMCU VST104.
System Components Batteries Batteries Two rechargeable battery packs are located in slots 23 and 28 behind the battery retainer. The batteries installed in all system enclosures are identical. A battery pack contains: • • 24 sealed, cylindrical, lead-acid cells A nonreplaceable fuse for short-circuit protection These batteries automatically power the system when AC power fails.
System Components Group ID Switches Group ID Switches Two group ID switches are located in slots 24 and 27. 0 1 Group ID Switch VST603.vsd The settings of the group ID switches define the group number of that enclosure: • • Both group ID switches within an enclosure must show the same group number. The group number of each enclosure in your system must be unique. Changing the Group Number • • • The group number of an enclosure cannot be changed online.
System Components Group ID Switches Group ID Switches and Stored Group Numbers Both group ID switches within an enclosure must be set to the same number. When the enclosure is powered on, the service processor (SP) reads the group ID switches and stores that group number. If you power the enclosure off and then power it back on, the SP retains that stored group number of the enclosure.
System Components Fans Processor Numbers and Group Numbers The processor numbers associated with the group numbers in a system are: Processor Group Slot Processor Group Slot 0 01 50 8 05 50 1 01 55 9 05 55 2 02 50 10 06 50 3 02 55 11 06 55 4 03 50 12 07 50 5 03 55 13 07 55 6 04 50 14 08 50 7 04 55 15 08 55 Fans Fans are located in slots 25 and 26 on the appearance side of a system enclosure, and they provide cooling for components inside the enclosure.
System Components Maximum Time That an Appearance-Side Door Can Be Open This figure shows the cooling fans: Cooling Fan Battery Retainer 32 3 2 3 2 Appearance Side VST641.
System Components Power Shelf Power Shelf The type of CRU installed in slots 50 and 55 determines whether that enclosure requires a power shelf. Enclosures without power shelves have power supplies internal to the CRUs in slots 50 and 55. Enclosures with power shelves have external power supplies.
System Components Power Supplies Power Supplies Two power supplies provide redundant power to the components in the enclosure. With two power supplies, loss of one power supply or one AC power cord does not result in a loss of system resources. Each PMF CRU or IOMF 2 CRU in an enclosure with a power shelf receives its power from the power supplies in the power shelf as well as from the batteries. The relationships between power supplies and CRUs in a system enclosure are: The power supply in slot...
System Components Service Side of System Enclosures Service Side of System Enclosures The service side of a system enclosure contains slots for: Note. For information about IOAM enclosures, see IOAM Enclosures on page 4-69.
System Components Service Side of System Enclosures Slot Numbers on Service Side of a System Enclosure 50 55 51 52 53 54 Group Service LED Group ID Label Module ID Label 56 GROUP MODULE 02 01 VST623.vsd Slot Component 50, 55 PMF CRU or IOMF CRU 51–54 SEB, MSEB, or ServerNet adapter 56 EPO connector Note. The appearance of a PMF CRU or IOMF CRU in your system might differ from that shown in the figure.
System Components Group ID Label Group ID Label On the service side, the group ID label is located on the leftmost cable support, illustrated in the figure on page 4-17. The label consists of changeable numbers in a holder. A group ID label is also on the service-side enclosure door, if present. The group ID label displays the group number associated with this system enclosure. For more information, see Group ID Switches on page 4-10.
System Components SEBs and MSEBs SEBs or MSEBs and Fabric Connections For fault tolerance, SEBs are installed in an enclosure in pairs: one for the X fabric and one for the Y fabric. Each SEB provides access to either the X fabric or the Y fabric, but not both. The relationships between SEB slots and ServerNet fabrics are: SEB Slot Number ServerNet Fabric 51 X 52 Y 53 X 54 Y SEBs and MSEBs can be installed in slots 51, 52, 53, and 54. The slot assignments depend upon the topology of the system.
System Components SEBs and MSEBs Six-Connector SEB Faceplate Fault LED (amber) Ejector Power-On LED (green) Faceplate Service LED (yellow) SERVERNET 5 SERVERNET 6 SERVERNET 3 SERVERNET 4 SERVERNET 1 SERVERNET 2 ServerNet Connector VST114.
System Components SEBs and MSEBs MSEB Description MSEBs are supported only on the G06.09 and later RVUs. The MSEB has four fixed ports using a serial-copper interface and six slots that can contain replaceable plug-in cards (PICs). An MSEB provides all the functions of a six-connector SEB. MSEBs can communicate with SEBs as well as other MSEBs. The PICs allow for a variety of interfaces.
System Components SEBs and MSEBs MSEB Faceplate Ejector Fault LED (Amber) Power-On LED (Green) Link Alive LED (Green) PIC, ServerNet 6 (NNA Fiber-Optic PIC Only) 10 6 PIC, ServerNet 9 ServerNet Serial Copper Port 5 4 8 3 7 2 1 Link Alive LED (Green) VST122.
System Components SEBs and MSEBs Selecting MSEB PICs ECL The six-connector SEBs use the ECL interface. To connect MSEBs to sixconnector SEBs, select ECL PICs. Serial copper For new systems or extensive upgrading, select serial-copper PICs and use the slimmer, more flexible serial-copper cables. MMF If enclosures are not arranged in conventional rows, select MMF PICs for distances of 200 meters (650 feet) between processor enclosures and between processor and I/O enclosures.
System Components Associated Fabrics Associated Fabrics • A PMF CRU in slot 50 communicates directly with the X fabric. This PMF CRU can also communicate indirectly with the Y fabric through the PMF CRU in slot 55 of the same enclosure. • A PMF CRU in slot 55 communicates directly with the Y fabric. This PMF CRU can also communicate indirectly with the X fabric through the PMF CRU in slot 50 of the same enclosure.
System Components ServerNet Adapters MSEBS in S7800, S76000, S86000, and later Servers In enclosures containing model 1962, 1971, 1972, or later PMF CRUs: • • • • • MSEBs, not SEBs, occupy slots 51 and 52 of all processor enclosures, 01 through 08 and must not be configured for ECL cables between processor enclosures. Either SEBs or MSEBs can occupy slots 53 and 54 of processor enclosures 01 through 04.
System Components Filler Panels A Typical ServerNet Adapter The Ethernet 4 ServerNet adapter (E4SA) is a typical ServerNet adapter that has four ports for Ethernet connections. Power-On LED (green) Ejector Fault LED (amber) RJ 45 Connector Receive Data (green) Collision Detect (green) RX Transmit Data (green) COL LNK TX ENET 1B Link Integrity (green) SAC 1 RX TX COL LNK ENET 1A RX COL TX LNK ENET 0B SAC 0 RX COL TX LNK ENET 0A VST116.
System Components Slot Assignments for Slots 51 Through 54 Slot Assignments for Slots 51 Through 54 Slot assignments for slots 51, 52, 53, and 54 depend on the type of PMF or IOMF CRU installed in slots 50 and 55 of a system enclosure. HP recommends that you reserve slots 51 and 52 for SEBs or MSEBs in processor enclosures. Single-Ported Slots Slots 51 and 52 are single ported in system enclosures containing models 1950, 1951, 1954, and 1960 PMF CRUs.
System Components Slot Assignments for Slots 51 Through 54 Slot Assignments for SEBs and MSEBs Each SEB or MSEB is single-ported and accesses only the X fabric or the Y fabric, depending on its slot location.
System Components Slot Assignments for Slots 51 Through 54 Slot Assignments for NonStop S-Series Servers Topology Enclosure Hardware Slots Notes Tetra 8 Processor SEBs or MSEBs 51, 52 You form an inner tetrahedron using these SEBs or MSEBs. You can attach two I/O enclosures to these SEBs or MSEBs. ServerNet adapters 53, 54 I/O ServerNet adapters 51, 52, 53, 54 IOAM FCSA G4SA 21, 22, 23, 23, 25 31, 32, 33, 34, 35 Slots are numbered according to their module numbers.
System Components Slot Assignments for Slots 51 Through 54 Slots 51 and 52 Processor enclosure slot 51 is single ported to the X fabric and slot 52 to the Y fabric on all systems using ServerNet router 1 (NonStop S7000, S7400, S70000, and S72000 servers). Slots are dual ported to both the X and Y fabrics on all systems using ServerNet router 2 (NonStop S7600, S7800, S74000, S76000, and S86000 servers).
System Components Emergency Power-Off (EPO) Connector Emergency Power-Off (EPO) Connector The emergency power-off (EPO) connector is located in slot 56. The EPO connector connects a system enclosure to the emergency power-off (EPO) circuitry at your site. When the EPO system is activated, building AC power is removed from the system and an EPO signal is activated, which causes the batteries to disconnect after four minutes.
System Components Processor Multifunction (PMF) CRUs PMF 2 CRUs contain a ServerNet router 2 instead of the ServerNet router 1 found in the earlier models of PMF CRUs. Note. All models are referred to as PMF CRUs unless it is necessary to distinguish a PMF 2 CRU from the others.
System Components Processor Multifunction (PMF) CRUs PMF CRU Faceplates The types of PMF CRU faceplates are: PMF CRU Model Server Faceplate Figure 1950 S7000 page 4-34 1951, 1954, 1960, S7400, S70000, S72000 page 4-35 1961, 1962, 1970, 1971, 1972, 1973, 1974 (PMF 2 CRU) S7600, S7800, S74000, S76000, S78000, S86000, S88000 page 4-36 The faceplates of PMF CRUs for the various models of NonStop S-series servers contain these listed features.
System Components Processor Multifunction (PMF) CRUs Model 1950 PMF CRU (S7000 Servers) Ejector Fault LED (Amber) Power-On LED (Green) Power-On Push Button Differential SCSI Port With External SCSI Passthrough Terminator Handle Serial Console Port (Unused) Ethernet Port Modem Port (Unused) AUX Port (Unused) AC Power Cord Receptacle Power-On Cable Receptacle Power Interlock Ejector VST105.
System Components Processor Multifunction (PMF) CRUs Model 1951, 1954, and 1960 PMF CRUs (S7400, S70000, and S72000 Servers) Ejector Fault LED (Amber) Power-On LED (Green) Power-On Push Button Differential SCSI Port With External SCSI Passthrough Terminator Handle Serial Console Port (Unused) Ethernet Port Modem Port (Unused) AUX Port (Unused) DC Power Cable Receptacle Power-On Cable Receptacle Power Interlock Ejector VST907.
System Components Processor Multifunction (PMF) CRUs Model 1961, 1962, 1970, 1971, 1972, 1973, 1974 PMF 2 CRUs (S7600, S7800, S74000, S76000, S78000, S86000, and S88000 Servers) Ejector ServerNet PIC (Unused) ServerNet PIC (Unused) ServerNet PIC (Unused) Fault LED (Amber) Power-On LED (Green) Power-On Push Button Differential SCSI Port Handle Serial Cable Port AUX Port (Unused) DC Power Cable Receptacle Ethernet Port Power-On Cable Receptacle Power Interlock Ejector VST964.
System Components Processor Multifunction (PMF) CRUs Ports • Differential SCSI port The differential SCSI port is on SCSI bus 3 and can be used to attach a supported tape drive or an Open SCSI device to the system. On PMF CRUs that are not PMF 2 CRUs, an external SCSI passthrough terminator is permanently installed in the differential SCSI port. On PMF 2 CRUs, the SCSI terminator is internal to the differential SCSI port.
System Components • Processor Multifunction (PMF) CRUs DC power cable In S7400, S7600, S7800, and Sxx000 processor enclosures, the DC power cable supplies DC power and other signals to the PMF CRU from the power supply in the power shelf. The DC power cable extends from the power interface board (PIB), located on the power shelf bulkhead, to the DC power cable receptacle on the PMF CRU.
System Components Processor Multifunction (PMF) CRUs The processor numbers and fabric connections: Slot Number of PMF CRU Processor Number Fabric Connection Through MFIOB 50 Even (0 if in group 01) X fabric only 55 Odd (1 if in group 01) Y fabric only The even-numbered processor in slot 50 can also communicate with the Y fabric through its router and the processor in the other PMF CRU in the same enclosure.
System Components Processor Multifunction (PMF) CRUs PMF CRU Memory Size (page 2 of 2) 1951-A 512 MB * 1951 640 MB * 1951-B 1 GB * 1954-X 256 MB 1954-A 512 MB 1954-B 1 GB 1954-C 2 GB 1960-A 512 MB 1961-B 1 GB 1961-D 4 GB 1962-C 2 GB 1962-D 4 GB 1970-A 512 MB 1970-C 2 GB 1970-D 4 GB 1971-B 1 GB 1971-C 2 GB 1971-D 4 GB 1971-F 16 GB 1972-B 1 GB 1972-C 2 GB 1972-D 4 GB 1972-F 16 GB 1973-C 2 GB 1973-D 4 GB 1973-E 8 GB 1974-C 2 GB 1974-D 4 GB 1974-E 8 G
System Components Configurations of Memory Units Configurations of Memory Units The total amount of memory in a PMF CRU depends on the number and size of the memory units installed in the PMF CRU.
System Components Configurations of Memory Units PMB in a 1950 PMF CRU MS8 MS2 MS1 MS4 MS3 MS7 MS6 MS5 Memory Slot Numbers Memory Unit Outer Memory Retainer Screw Memory Slot Inner Memory Retainer Screw Memory Retainer (Closed) Antistatic Mat VST687.
System Components Configurations of Memory Units PMB in a 1951 PMF CRU Memory Retainer Screw MS1 MS2 MS3 MS4 MS5 MS6 MS7 MS8 Memory Slot Numbers Memory Slot Memory Unit Memory Retainer (Closed) Antistatic Mat VST071.
System Components Configurations of Memory Units Compatibility of PMF CRUs Permanent Coexistence of Enclosures in a System The NonStop S-series model number of an enclosure is determined by the pair of PMF CRUs installed in the enclosure.
System Components Configurations of Memory Units PMF CRU Compatibility in an Enclosure During Online Replacement or Upgrade All models of PMF CRUs can be replaced online. Some models of PMF CRUs cannot be upgraded online. This table shows which PMF CRUs can be upgraded from one model to another online. .
System Components Configurations of Memory Units Multifunction I/O Board (MFIOB) The multifunction I/O board (MFIOB) is a ServerNet adapter integrated into PMF CRUs and IOMF CRUs that contains: Two SCSI ServerNet addressable controllers (SACs) These SACs control SCSI buses 1 and 2 and the disk drives on the appearance side of the system enclosure. One differential SCSI SAC This SAC is connected to the differential SCSI port on the PMF CRU or IOMF CRU and controls SCSI bus 3.
System Components Configurations of Memory Units Service Processor (SP) The service processor (SP) on the MFIOB monitors and controls the operation of the system. The SPs: • • • • • • • • Initialize hardware Configure ServerNet routers Perform startup services Perform down system services Perform environmental sense and control (ESC) functions Control power Test hardware Configure hardware Each SP has its own operating system that runs independently of other SPs and of the rest of the system.
System Components Configurations of Memory Units Service processor communication Service processor communication takes place along routes that depend on the destination of the message: • • • The MSPs communicate with the OSM or TSM Low-Level Link running on the system console through the Ethernet ports on the PMF CRUs in group 01 and using the Remote Procedure Call (RPC) protocol. The pair of SPs in one enclosure communicate with each other through the dualported SMB within that enclosure.
System Components Configurations of Memory Units ServerNet Router 2 The PMF 2 CRU contains a ServerNet router 2, which has connections to: • • • • • • • The processor in the same PMF CRU The processor in the other PMF CRU in this enclosure Both SEB or adapter slots 51 and 52 Both SEB or adapter slots 53 and 54 Three ServerNet ports, through plug-in cards (PICs) The peripheral component interconnect (PCI) bus on the MFIOB to two SCSI controllers for the internal disk drive buses The native I/O bus (NIOBu
System Components I/O Multifunction (IOMF) CRUs I/O Multifunction (IOMF) CRUs IOMF CRUs occupy slots 50 and 55 of I/O enclosures. They: • • • • Connect to ServerNet fabrics Connect enclosures Supply power Provide power-on connections IOMF CRUs come in the following models: IOMF CRU Model Product Number IOMF CRU 1952 IOMF 2 CRU 1980 IOMF 2 CRUs are supported on the G06.10 and later RVUs. Note.
System Components I/O Multifunction (IOMF) CRUs Associated Fabrics IOMF CRU in Slot … Connects to … 50 X fabric 55 Y fabric Differences Between IOMF CRUs (Model 1952) and IOMF 2 CRUs The IOMF 2 CRU has all the functions of the IOMF CRU (model 1952) except that the unused modem port is removed from the IOMF 2 CRU (model 1980). In addition, the IOMF 2 CRU: • • • • • • • Has three configurable ServerNet ports, two of which are unused at this time Is supported on G06.11 and later RVUs and on G06.
System Components I/O Multifunction (IOMF) CRUs IOMF CRU Faceplates The IOMF CRU faceplates are shown in these figures: IOMF CRU Model Faceplate Figure 1952 IOMF CRU page 4-53 1980 IOMF 2 CRU page 4-54 The faceplates of the different models of the IOMF CRU contain the following features.
System Components I/O Multifunction (IOMF) CRUs 1952 IOMF CRU Faceplate Ejector Fault LED (Amber) Power-On LED (Green) Power-On Push Button ServerNet Port Service LED (Yellow) ServerNet Port Handle Differential SCSI Port Serial Console Port (Unused) Ethernet Port Modem Port (Unused) AUX Port (Unused) AC Power Cord Receptacle Power-On Cable Receptacle Power Interlock Ejector VST117.
System Components I/O Multifunction (IOMF) CRUs 1980 IOMF 2 CRU Faceplate Ejector ServerNet Port 3 (Unused) ServerNet Port 2 (Unused) ServerNet Port 1 Status LED (Amber) Power LED (Green) Power-On Push Button Differential SCSI Port Handle Serial Console Port (Unused) (Behind Handle) AUX Port (Unused) Ethernet Port DC Power Cable Receptacle Power-On Cable Receptacle Power Interlock Ejector VST 300 .
System Components I/O Multifunction (IOMF) CRUs Ports • ServerNet port (on 1952 IOMF CRU) You connect an I/O enclosure to a processor enclosure by connection a ServerNet cable between as SEB or MSEB in the processor enclosure and the ServerNet port on an IOMF CRU in the I/O enclosure.
System Components I/O Multifunction (IOMF) CRUs Power Cords, Power Cables, and Receptacles • 1952 IOMF CRUs: ° AC power cord The AC power cord supplies AC power to power supplies in the IOMF CRU. Removing the AC power cord from an IOMF CRU results in loss of power to the IOMF CRU and its associated PMCU and loss of the capability to charge the associated battery. However, the other components in the enclosure are powered by the other power supply and the batteries.
System Components I/O Multifunction (IOMF) CRUs The 1980 IOMF 2 CRU contains: • • • An amber status LED, that when lit, indicates that the IOMF 2 CRU is in an error condition. A green power LED, that when lit, indicates that the IOMF CRU is operational. Two service LEDs that are currently unused. Multifunction I/O Board (MFIOB) The MFIOBs in IOMF CRUs are identical to those in PMF CRUs.
System Components I/O Multifunction (IOMF) CRUs ServerNet Router 1 The 1952 IOMF CRU contains one ServerNet router 1, which has connections to: • • • • The backplane The ServerNet bus interface (SBI) on the MFIOB ServerNet adapter slots 51, 52, 53, and 54 The serial maintenance bus (SMB), which provides communication between the SP and the other components within the enclosure ServerNet Router 2 The 1980 IOMF 2 CRU contains one ServerNet router 2, which has connections to: • • • • The backplane The S
System Components Enclosure Doors Enclosure Doors System enclosures have a short enclosure door on the appearance side. When closed, it reduces electromagnetic interference (EMI) and ensures maximum cooling for components inside the enclosure. You must keep the appearance-side enclosure door closed during normal operation of the server. Starting with the NonStop S76000 and S86000, servers are equipped with tall doors on the appearance side and service side as part of the visual image package.
System Components Enclosure Doors This figure shows a short enclosure door installed on the service side of an enclosure. Enclosure Frame Post Cable Channel Adapter Frame Service-Side Door Faceplate Group ID Label VST020.
System Components Tall Enclosure Door Visual Image Package Starting with the NonStop S76000 and S86000, servers are equipped with a different visual image package.
System Components Enclosure Side Panel Enclosure Side Panel VST701.vsd Plug-in Cards A plug-in card (PIC) is a replaceable component in ServerNet adapters, MSEBs, and IOMF 2 CRUs. It provides a choice of connection media for ServerNet cables.
System Components Typical PIC Installations Typical PIC Installations This figure shows four PICs installed in a ServerNet/DA: Common Base Board (CBB) PIC Rear SA C4 SA PIC Front Panel C3 Front SA C2 SA C- 1 ServerNet/DA Faceplate VST835.
System Components Typical PIC Installations The PICs in ServerNet adapters are secured from the bottom of the adapter. 1/2-inch T-9 Torx Screws Bottom 3/16-inch T-9 Torx Screws Rear SA CSA SA C SA C- 2 -3 Front C4 VST834.
System Components Typical PIC Installations This figure shows four ServerNet PICs, one NNA PIC, and an empty PIC slot in an MSEB. PICs in an MSEB are secured from above. NNA PIC Plastic Nut on Threaded Stud No Nut on This Stud Rear T-10 Torx Screws Common Base Board (CBB) Front ServerNet PIC VST838.
System Components System Console System Console A system console is a personal computer, approved by HP, used to run maintenance and diagnostic software for NonStop S-series servers. New system consoles are preconfigured with the required HP and third-party software. Existing system consoles can be upgraded to latest software versions from the HP NonStop System Console Installer CD.
System Components System Console The primary system console is connected to group 01 through a local area network (LAN) and the Ethernet ports on PMF CRUs. (HP recommends that you also configure a backup system console on the same LAN.) OSM or TSM running on the system console communicates with the system at two levels: OSM or TSM Communicates With ... Through the ...
System Components Tape Drives Tape Drives An external tape drive is connected to a server through a SCSI cable to the differential SCSI port on a PMF CRU, IOMF CRU, or plug-in card (PIC) on a 6760 ServerNet device adapter (ServerNet/DA). Processor Enclosure (Service Side) 50 55 PMF CRU 51 52 53 54 Differential SCSI Port External SCSI Passthrough Terminator (internal on PMF 2 CRUs and IOMF 2 CRUs) 56 Cable From the Tape Subsystem VST550.vsd Note.
System Components SWAN Concentrators SWAN Concentrators ServerNet wide area network (SWAN) concentrators are communications devices that connect to a NonStop S-series server through dual Ethernet ports and provide connections that support bit-synchronous, byte-synchronous, and asynchronous protocols over a variety of electrical interfaces.
System Components Components Components These components are associated with or reside in an IOAM enclosure.
System Components Components Power Supplies Four power supplies with universal AC input provide power to the components in an IOAM enclosure.The power supplies are installed in slots 15 and 18 on the rear side of an IOAM enclosure. Bezel The bezel is a hinged cover on the front on the IOAM enclosure.
System Components Group, Module, and Slot Hierarchy for IOAM Enclosures For power and environmental requirements, planning, installation, and emergency power-off (EPO) instructions for the R5500 UPS, refer to the documentation shipped with the UPS. For information about planning for a site UPS, contact your HP trained service provider.
System Components Group, Module, and Slot Hierarchy for IOAM Enclosures IOAM Enclosure (Front) Group, Module, and Slot Hierarchy 42 42 41 41 40 40 39 39 38 38 37 36 35 37 Fans (Module 3) Fans (Module 2) 34 IOAM Enclosure (Group 12) 33 Slot 17 Slot 17 32 31 31 30 30 29 28 29 Slot 16 Slot 16 28 27 27 26 26 25 Power Supplies Modules 2 and 3 25 24 24 23 23 22 22 21 21 20 20 19 Fans (Module 3) 18 Fans (Module 2) 17 15 19 18 17 16 IOAM Enclosure (Group 11) 35 3
System Components Group, Module, and Slot Hierarchy for IOAM Enclosures IOAM Enclosure (Rear) Group, Module, and Slot Hierarchy 42 42 41 41 40 40 39 39 38 38 37 37 36 36 35 35 34 34 ServerNet Switch Board (Module 2) 33 33 ServerNet Switch Board (Module 3) 32 32 31 30 31 IOAM (Module 3) 30 Slot 5 Slot 4 Slot 3 Slot 2 Slot 5 Slot 1 27 Slot 4 28 29 Slot 3 29 Slot 1 Slot 2 IOAM Enclosure (Group 12) IOAM (Module 2) 27 26 26 25 25 24 24 23 23 Module 2 22 Modul
System Components Group, Module, and Slot Hierarchy for IOAM Enclosures IOAM Configuration Requirements Configuring IOAM enclosures on a NonStop S-series system includes the following requirements: • • • • An IOAM enclosure can be group 11, 12, 13, 14, or 15. Each one takes the place of up to four I/O enclosures. IOAM enclosures can be installed in any order. MSEB slots corresponding to the group 01 slot in which the IOAM is installed must be empty.
System Components Group, Module, and Slot Hierarchy for IOAM Enclosures Cabling IOAM Enclosures This shows two IOAM enclosures connected to an HP S-series processor enclosure.
5 ServerNet Cabling This section describes ServerNet cables, how to interpret ServerNet cabling diagrams, and how to connect cables between enclosures.
ServerNet Cabling ServerNet Cables ServerNet Cables These types of ServerNet cables are available: • • • • • • SEB-to-SEB ECL SEB-to-MSEB ECL MSEB-to-MSEB ECL Serial-copper Multimode fiber-optic Single-mode fiber-optic The use of the ECL cable adapter to connect an SEB-to-SEB cable to an MSEB has been discontinued. Part numbers for ServerNet cables are listed in Cables and Cable Assemblies on page A-26. System enclosures are connected by ServerNet cables as follows: SEB/MSEB in Processor Enclosure to..
ServerNet Cabling ECL Cables SEB-to-MSEB ECL Cable One end of this cable has a 50-pin connector for a six-connector SEB or IOMF CRU; the other end has a smaller connector for an ECL PIC on an MSEB or IOMF 2 CRU. VST966.vsd MSEB-to-MSEB ECL Cable Both ends of this cable have the smaller connectors for the ECL PICs on MSEBs and IOMF 2 CRUs. VST965.vsd ECL Cable Adapter An SEB-to-SEB ECL cable adapter was used to connect a six-connector SEB to an MSEB. The ECL cable adapter is no longer available.
ServerNet Cabling Serial-Copper Cables Serial-Copper Cables You can connect a serial-copper cable to a serial-copper PICs installed in an MSEB or IOMF 2 CRU. Serial-copper cables are lighter than ECL cables and do not require an adapter cable. Therefore, serial-copper cables are preferred over ECL cables. VST103.vsd Caution. Do not force the cable connector when disconnecting a serial-copper connector. Press the retainer fully, and the connector should release easily.
ServerNet Cabling Fiber-Optic Cables With LC-SC Connectors Fiber-Optic Cables With LC-SC Connectors For the ServerNet Cluster product and IOAM enclosures, fiber-optic cables with LC-SC connectors are used to connect to the MSEBs in processor enclosures. Caution. IOAM enclosures must be installed by service providers trained by HP. All cabling connections must be performed by your service provider.
ServerNet Cabling How Cabling Diagrams Represent Server Hardware How Cabling Diagrams Represent Server Hardware PMF CRU SEB SEB SEB slot 50 slot 51 slot 52 slot 53 SEB slot 54 PMF 5 4 50 6 SEB 1 51 SEB 2 53 3 6 5 4 3 2 1 Group 02 This subsection introduces cabling diagrams and shows how they represent the hardware components of a server. This figure shows a cabling diagram for the hardware components of a processor enclosure. PMF CRU slot 55 Port 6 Port 5 Port 4 Port 3 Port 2 Port 1 VST504.
ServerNet Cabling How Cabling Diagrams Represent Server Hardware This figure shows a cabling diagram for two enclosures connected by a cable. 5 4 6 1 2 3 PMF 50 SEB 51 Group 02 SEB 53 6 5 4 3 2 1 SEB 53 Port 5 Port 5 55 50 IOMF CRU slot 50 Group 25 IOMF Processor Enclosure, Service Side I/O Enclosure, Service Side VST505.
ServerNet Cabling ServerNet Cabling: Tetra 8 Topology ServerNet Cabling: Tetra 8 Topology This subsection describes the ServerNet cable connections for the Tetra 8 topology, which is supported by all models of NonStop S-series servers, and supports a maximum of: • • Four processor enclosures Eight I/O enclosures (two for each processor enclosure) Tetra 8 Cabling Diagram, X Fabric on page 5-9 Tetra 8 Cabling Diagram, Y Fabric on page 5-9 Tetra 8 Cabling Table, Processor Enclosures on page 5-10 Tetra 8 Ca
ServerNet Cabling Tetra 8 Cabling Diagram, X Fabric Tetra 8 Cabling Diagram, X Fabric This diagram shows the ServerNet cable connections for the X fabric in the maximum Tetra 8 topology. Group 11 IOMF Group 12 IOMF Group 22 IOMF Group 21 IOMF 50 50 50 50 Group 01 5 4 SEB 6 51 1 2 3 5 PMF 50 4 6 SEB 1 51 2 3 Group 02 Group 04 3 2 SEB 1 51 6 4 PMF 50 5 3 2 1 SEB 6 51 4 PMF 50 5 Group 03 PMF 50 50 50 50 50 Group 41 IOMF Group 42 IOMF Group 32 IOMF Group 31 IOMF VST247.
ServerNet Cabling Tetra 8 Cabling Table, Processor Enclosures Tetra 8 Cabling Table, Processor Enclosures This table describes the ServerNet cable connections among the processor enclosures in the maximum Tetra 8 topology. Each cable appears twice in this table, once for the connection at each end.
ServerNet Cabling Tetra 8 Cabling Table, I/O Enclosures Tetra 8 Cabling Table, I/O Enclosures This table describes the ServerNet cable connections between I/O enclosures and processor enclosures in the maximum Tetra 8 topology.
ServerNet Cabling ServerNet Cabling: Tetra 16 Topology ServerNet Cabling: Tetra 16 Topology This subsection describes the ServerNet cable connections for the Tetra 16 topology, which is supported by the following models of NonStop S-series servers: Note. IOAM enclosures can replace I/O enclosures in cabling diagrams. For information about what is supported, contact your HP representative. Note.
ServerNet Cabling Tetra 16 Cabling Diagram, X Fabric Tetra 16 Cabling Diagram, X Fabric G-series RVUs do not support I/O enclosures connected to SEBs in slot 53 of Groups 05, 06, 07, and 08.
ServerNet Cabling Tetra 16 Cabling Diagram, Y Fabric Tetra 16 Cabling Diagram, Y Fabric G-series RVUs do not support I/O enclosures connected to SEBs in slot 54 of Groups 05, 06, 07, and 089.
ServerNet Cabling Tetra 16 Cabling Table, Processor Enclosures Tetra 16 Cabling Table, Processor Enclosures This table describes the ServerNet cable connections among the processor enclosures in the maximum supported Tetra 16 topology. Each cable appears twice in this table, once for the connection at each end.
ServerNet Cabling Tetra 16 Cabling Table, I/O Enclosures From To (page 2 of 2) Group Slot ServerNet Connector Group Slot ServerNet Connector 04 52 2 02 52 2 04 51 1 03 51 1 04 52 1 03 52 1 04 51 5 08 51 5 04 52 5 08 52 5 05 51 5 01 51 5 05 52 5 01 52 5 06 51 5 02 51 5 06 52 5 02 52 5 07 51 5 03 51 5 07 52 5 03 52 5 08 51 5 04 51 5 08 52 5 04 52 5 Tetra 16 Cabling Table, I/O Enclosures This table describes the ServerNet c
ServerNet Cabling Tetra 16 Cabling Table, I/O Enclosures From To (page 2 of 3) Group Slot Group Slot ServerNet Connector 24 50 02 53 4 24 55 02 54 4 25 50 02 53 5 25 55 02 54 5 31 50 03 53 1 31 55 03 54 1 32 50 03 53 2 32 55 03 54 2 33 50 03 53 3 33 55 03 54 3 34 50 03 53 4 34 55 03 54 4 35 50 03 53 5 35 55 03 54 5 41 50 04 53 1 41 55 04 54 1 42 50 04 53 2 42 55 04 54 2 43 50 04 53 3 43 55 04 54 3 44
ServerNet Cabling Cabling IOAM Enclosures From To (page 3 of 3) Group Slot Group Slot ServerNet Connector 62 55 06 52 2 63 50 06 51 3 63 55 06 52 3 64 50 06 51 4 64 55 06 52 4 71 50 07 51 1 71 55 07 52 1 72 50 07 51 2 72 55 07 52 2 73 50 07 51 3 73 55 07 52 3 74 50 07 51 4 74 55 07 52 4 81 50 08 51 1 81 55 08 52 1 82 50 08 51 2 82 55 08 52 2 83 50 08 51 3 83 55 08 52 3 84 50 08 51 4 84 55 08 52 4
ServerNet Cabling Cabling Diagram, IOAM Enclosure, X Fabric Cabling Diagram, IOAM Enclosure, X Fabric This figure shows an IOAM enclosure group 15 and the other groups that must not be occupied. See Cabling IOAM Enclosures on page 4-76.
ServerNet Cabling NonStop S7800, S76000, S78000, S86000, and S88000 Servers With 1952 IOMF CRUs NonStop S7800, S76000, S78000, S86000, and S88000 Servers With 1952 IOMF CRUs NonStop S7800, S76000, S78000, S86000, or S88000 processor enclosures must be cabled together using either serial-copper or fiber-optic ServerNet cables. ECL cables are not allowed. However, you can use model 1952 IOMF CRUs in these systems with ECL cables and MSEBs.
ServerNet Cabling Cabling Diagram, Model 1962, 1971, 1972, 1973, or 1974 PMF CRUs With 1952 IOMF CRUs, X Fabric Cabling Diagram, Model 1962, 1971, 1972, 1973, or 1974 PMF CRUs With 1952 IOMF CRUs, X Fabric In this diagram, the broken lines represent serial-copper or fiber-optic cables. Solid lines represent ECL cables.
ServerNet Cabling Cabling Diagram, Model 1962, 1971, 1972, 1973, or 1974 PMF CRUs With 1952 IOMF CRUs, Y Fabric Cabling Diagram, Model 1962, 1971, 1972, 1973, or 1974 PMF CRUs With 1952 IOMF CRUs, Y Fabric Group 51 IOMF Group 52 IOMF Group 53 IOMF Group 54 IOMF Group 64 IOMF Group 63 IOMF Group 62 IOMF Group 61 IOMF 55 55 55 55 55 55 55 55 1 2 3 MSEB 52 4 5 6 1 PMF 2 2 55 3 MSEB 4 52 5 6 PMF 2 55 Group 05 6 5 4 Group MSEB 01 52 1 SEB 2 54 3 1 2 3 4 5 6 6 PMF 2 55 5 4 Group MSEB 1 52 02
6 ServerNet Communication Pathways This section describes the structure and operations of the communication pathways provided by each PMF CRU, IOMF CRU or IOAM, and SEB in your NonStop S-series system. Note. In this section, unless otherwise indicated: • • • • Information about PMF CRUs also applies PMF 2 CRUs. Information about IOMF CRUs also applies to IOMF 2 CRUs. Information about SEBs also applies to MSEBs.
ServerNet Communication Pathways PMF CRUs and Communication Pathways For Information About ... Refer to ...
ServerNet Communication Pathways ServerNet Router Inside a PMF CRU ServerNet Router Connections in an Enclosure Each PMF CRU in an enclosure provides a connection to its associated fabric for the other PMF CRU in that enclosure. In this figure, the PMF CRU in slot 50 provides access to the X fabric for the PMF CRU in slot 55.
ServerNet Communication Pathways ServerNet Router Inside a PMF CRU ServerNet Router Connection in an Enclosure, One PMF CRU Removed In this figure, the PMF CRU in slot 50 has been removed from the enclosure. The PMF CRU in slot 55 can still access the Y fabric, but it can no longer access the X fabric through the PMF CRU in slot 50. PMF CRU, slot 55 (Y fabric) Processor X Y SEB Slot 52 (Y fabric) Router ServerNet Adapter ServerNet Adapter Disks ServerNet Adapter VST507.
ServerNet Communication Pathways PMF CRU Pathways Within One Enclosure PMF CRU Pathways Within One Enclosure The router in a PMF CRU provides pathways to slots 51 and 53 (X fabric) or slots 52 and 54 (Y fabric). It also provides a pathway to the PMF CRU in the opposite fabric as well as other destinations of no concern to this discussion. The examples in this section are of the X fabric. The SEB router (not shown) in slot 51 connects the PMF CRU to all ports on the SEB.
ServerNet Communication Pathways PMF CRU Pathways Between Enclosures PMF CRU Pathways Between Enclosures The heavy lines in this figure show typical pathways: • • • In Group 05, from slot 53, through the PMF CRU in slot 50, to the SEB in slot 51 From the SEB in slot 51 in Group 05 to the SEB in slot 51 in Group 01 In Group 01, from the SEB in slot 51 through the PMF CRU in slot 50, to the I/O enclosures connected to the SEB in slot 53.
ServerNet Communication Pathways PMF CRU Pathways With a PMF CRU Removed From the Outer Tetrahedron PMF CRU Pathways With a PMF CRU Removed From the Outer Tetrahedron In this figure, the PMF CRU in group 05, slot 50, has been removed. As a result, any device attached to Group 05 slot 53 is isolated from the rest of the system over the X fabric.
ServerNet Communication Pathways PMF CRU Pathways With a PMF CRU Removed From the Inner Tetrahedron PMF CRU Pathways With a PMF CRU Removed From the Inner Tetrahedron In this figure, the PMF CRU in group 01, slot 50, has been removed. The pathway between SEB 51 and SEB 53 of group 01 is gone. Therefore, the Group 01 I/O enclosures are isolated from the system over the X fabric.
ServerNet Communication Pathways SEBs, MSEBs, and Communication Pathways SEBs, MSEBs, and Communication Pathways SEB Pathways Within One Enclosure 6-9 SEB Pathways Within One Enclosure: One SEB Removed 6-10 SEB Pathways Between Enclosures 6-11 SEB Pathways Between Enclosures: One SEB Removed 6-12 Communication pathways between enclosures are provided by SEBs (or MSEBs). Each SEB in an enclosure connects to one fabric.
ServerNet Communication Pathways SEB Pathways Within One Enclosure: One SEB Removed SEB Pathways Within One Enclosure: One SEB Removed When the SEB is removed from group 05, slot 51, the PMF CRU in slot 50 is isolated from the system over the X fabric and from groups 51 through 54. X Fabric Group 51 IOMF Group 52 IOMF Group 53 IOMF Group 54 IOMF Group 05 50 50 50 50 1 2 SEB 3 51 4 6 Slot 5 53 PMF 50 To Group 01 VST925.
ServerNet Communication Pathways SEB Pathways Between Enclosures SEB Pathways Between Enclosures When one processor enclosure communicates with another processor enclosure, the communication must pass through SEBs or MSEBs. The group number of each enclosure is determined by the ports to which the ServerNet cables are connected. In this figure, group 01 communicates over the X fabric with group 05 and group 52 along paths shown in heavy lines.
ServerNet Communication Pathways SEB Pathways Between Enclosures: One SEB Removed SEB Pathways Between Enclosures: One SEB Removed Removing SEB 53 From the Inner Tetrahedron 6-12 Removing SEB 51 From the Outer Tetrahedron 6-13 Removing SEB 51 From the Inner Tetrahedron 6-14 Removing SEB 53 From the Inner Tetrahedron In this figure, SEB 53 has been removed from group 01. Groups 11 through 15, represented with pale lines, are isolated from the rest of the system over the X fabric.
ServerNet Communication Pathways SEB Pathways Between Enclosures: One SEB Removed Removing SEB 51 From the Outer Tetrahedron In this figure, SEB 51 has been removed from group 05. The PMF CRU in Group 05 slot 50, Groups 51 through 54, and slot 53, represented by pale lines, are not accessible over the X fabric to the rest of the system.
ServerNet Communication Pathways SEB Pathways Between Enclosures: One SEB Removed Removing SEB 51 From the Inner Tetrahedron With the SEB removed from group 01 slot 51, groups 01 and 05, and all their associated I/O enclosures, are not accessible over the X fabric to the rest of the system. The heavy line shows a pathway that is interrupted by the missing SEB in Group 01.
ServerNet Communication Pathways Communication Pathways in Different Topologies Communication Pathways in Different Topologies Tetra 8 Topology Tetra 16 Topology For the X fabric, a system can have an SEB only in slot 51. For the X fabric, a system can have SEBs in slots 51 and 53 of the inner tetrahedron. Each processor enclosure supports one SEB for each ServerNet fabric. Each inner tetrahedron processor enclosure can support up to two SEBs for each ServerNet fabric.
ServerNet Communication Pathways Pathway Between Groups 01 and 31, Tetra 8 Topology Pathway Between Groups 01 and 31, Tetra 8 Topology The heavy line in this figure shows the pathway between group 01 and group 31 over the X fabric on a Tetra 8 topology. All communication between I/O enclosures and processor enclosures is routed through one SEB in each processor enclosure.
ServerNet Communication Pathways Pathway Between Groups 01 and 31, Tetra 16 Topology Pathway Between Groups 01 and 31, Tetra 16 Topology This cabling diagram shows the pathway, over the X fabric, between group 01 and group 31. The communication is routed through one SEB in one processor enclosure, and two SEBs in another processor enclosure.
ServerNet Communication Pathways Determining the Communication Pathways in Your System Determining the Communication Pathways in Your System You can determine the communication pathways in your particular system by using: For ... Refer to ...
7 Enclosure Arrangements and Cable Connections This section discusses arrangements and cable connections for NonStop S-series system enclosures. Considerations for Enclosure Arrangements 7-1 Choosing ServerNet Cable Lengths 7-4 Power-On Cables 7-10 Requirements for Grounding 7-12 Considerations for Expanding a System 7-13 Note. IOAM enclosures can replace I/O enclosures in group 01 of cabling diagrams. For important configuration restrictions, refer to IOAM Enclosures on page 4-69. Note.
Enclosure Arrangements and Cable Connections Example Enclosure Arrangements: Tetra 8 Topology Examples of Enclosure Arrangements Example Enclosure Arrangements: Tetra 8 Topology on page 7-2 Example Enclosure Arrangements: Tetra 16 Topology on page 7-3 Note. The arrangement of system enclosures does not change the requirements for how they are cabled together. ServerNet cables must always be connected according to the requirements of the topology you have chosen.
Enclosure Arrangements and Cable Connections Example Enclosure Arrangements: Tetra 16 Topology Example Enclosure Arrangements: Tetra 16 Topology This figure shows a recommended arrangement of system enclosures for a configuration using the Tetra 16 topology. Smaller and larger Tetra 16 configurations can also use this arrangement. This arrangement minimizes the number of times ServerNet cables cross over each other.
Enclosure Arrangements and Cable Connections Choosing ServerNet Cable Lengths Choosing ServerNet Cable Lengths The following information about ServerNet cable lengths applies to ECL and serialcopper ServerNet cables. The lengths of fiber-optic ServerNet cables available from HP is limited; refer to Cables and Cable Assemblies on page A-26. The lengths of the ServerNet cables you need depends on the arrangement of the enclosures you want to connect. For Information About ... Refer to ...
Enclosure Arrangements and Cable Connections Same-Row Connections Cable slack is 6 inches (15.25 cm) for a single cable in any enclosure. Extra cable length allows cable to bend to attach to connector. If you are tying together a large group of cables, you will need extra slack in each cable in that group. How much slack you need depends on the size of that group of cables. For more information, contact your service provider.
Enclosure Arrangements and Cable Connections Same-Row Connections ServerNet Connections Between Adjacent Enclosures These illustrations show ServerNet cable connections between two system enclosures that are horizontally, vertically, and diagonally adjacent. Horizontally Adjacent Diagonally Adjacent Vertically Adjacent VST958.
Enclosure Arrangements and Cable Connections Same-Row Connections Horizontal ServerNet Connections With Intervening Enclosures These illustrations show ServerNet cable connections between nonadjacent system enclosures that are in the same row at the same level. Horizontal with 1 intervening enclosure Horizontal with 2 intervening enclosures Horizontal with 3 intervening enclosures VST957.
Enclosure Arrangements and Cable Connections Same-Row Connections Diagonal ServerNet Connections With Intervening Enclosures These illustrations show ServerNet cable connections between nonadjacent system enclosures that are in the same row bur at different levels. Diagonal with 1 intervening enclosure Diagonal with 2 intervening enclosures VST959.
Enclosure Arrangements and Cable Connections Different-Row Connections Different-Row Connections If you are connecting two enclosures that are in different rows, you must calculate the length of the ServerNet cable you need.
Enclosure Arrangements and Cable Connections Power-On Cables Use the following worksheets to calculate the length of the ServerNet cable you need: For ... Refer to ... Worksheets to help you determine which cables to order Appendix C, Blank Forms Cross-Row Cabling Worksheet Appendix C, Blank Forms An example of a completed worksheet Appendix D, Case Study: ServerNet Cable Lengths Select a part number from the appropriate table in Cables and Cable Assemblies on page A-26.
Enclosure Arrangements and Cable Connections Power-On Cables These illustrations show typical power-on cable routing. VST807.
Enclosure Arrangements and Cable Connections Powering On Powering On A system can be powered on from a single power-on push button. To power on an entire system, press the power-on push button on either of the PMF CRUs in group 01. Powering Off There are several ways to power off a system: • • For nonemergency power-offs, issue a software command. In an emergency, power off the system in one of these ways.
Enclosure Arrangements and Cable Connections Considerations for Expanding a System Considerations for Expanding a System • • NonStop S7xx servers are limited to two processors. NonStop S-series servers can grow from two to 16 processors, in pairs. The more processors a system has, the more I/O enclosures it can have. For more information about which systems support which topologies, and how many enclosures are supported by each system, refer to Section 3, Topologies.
Enclosure Arrangements and Cable Connections Considerations for Expanding a System HP NonStop S-Series Planning and Configuration Guide—523303-015 7- 14
8 Initial Configurations This section discusses the initial configurations for NonStop S-series servers. For more information, see the G.nn Release Version Update Compendium. Note. Not all the products, configurations, features, and functions described in this guide are available with the current RVU. Ask your service provider about the availability dates for these products, configurations, features, and functions.
Initial Configurations Processor Numbers and Locations Processor Numbers and Locations This table lists each processor by processor number and gives the physical location of the processor multifunction (PMF) CRU that contains that processor.
Initial Configurations Processor Types and Memory Sizes Processor Types and Memory Sizes This table lists the memory sizes available for each processor type. The processors within a system are not required to have the same amount of memory.
Initial Configurations Minimum Disk-Drive Configuration Minimum Disk-Drive Configuration A system must include a minimum of four internal disk drives, all having the same product number. This table lists the factory-default device name, location, and purpose of each of these four internal disk drives.
Initial Configurations External Disk Drives External Disk Drives The external disk drives supported in all NonStop S-series systems for the current RVU are listed in External Disk Drives on page F-5. Tape Drives The external tape drives supported in NonStop S-series systems for the current RVU are listed in Tape Drives on page F-5. Each PMF CRU and IOMF CRU in a system has a SCSI port to which you can connect an external tape drive.
Initial Configurations Initial Default Values for System Attributes Initial Default Values for System Attributes To Change This Attribute (page 1 of 2) System Attribute Default Value BREAKPOINT_CONTROL_ BLOCKS Automatically set to 50 You cannot change an automatically configured system attribute. BUILD_Z0_PROCESS Automatically built during system generation You cannot change an automatically configured system attribute. DAYLIGHT_SAVINGS_TIME NONE Use SCF for the Kernel subsystem.
Initial Configurations Initial Default Values for System Attributes System Attribute Default Value To Change This Attribute (page 2 of 2) SYSTEM_LIBRARY_ CODE_FILES TANDEM^LIBRARY^ CODE^FILES Change in the CONFTEXT file. SYSTEM_NAME \NONAME Use SCF for the Kernel subsystem. See Changing System Name and Number on page 8-8. SYSTEM _NUMBER 254 Use SCF for the Kernel subsystem. See Changing System Name and Number on page 8-8.
Initial Configurations Changing System Name and Number After you install and start a system, you can use SCF to determine the system configuration. Refer to the SCF Reference Manual for G-Series RVUs for more information about this task. Changing System Name and Number Changing the system name and Expand node number (system number) involves more than using SCF to change the system name and system number attributes.
Initial Configurations Objects Configured in the Initial CONFIG File Objects Configured in the Initial CONFIG File When a system is delivered, the file $SYSTEM.ZSYSCONF.CONFIG contains a standard system configuration created by HP. This initial CONFIG file is also saved on your system as the ZSYSCONF.CONF0000 file.
Initial Configurations Objects That Must Not Be Renamed Objects That Must Not Be Renamed After you verify that your system is in working order, you can rename most configured SCF objects. The exceptions are: • • Do not rename the following processes and devices that are used by OSM or TSM: ° ° ° ° ° ° MIOE0 and MIOE1 LANX and LANY $ZCVP0 and $ZCVP1 $ZTCP0 and $ZTCP1 $ZTNP0 and $ZTNP1 $ZPRP0 and $ZPRP1 Do not rename the generic processes configured in the initial current configuration database.
Initial Configurations Command Files for Objects Not Configured in the Initial CONFIG File Command Files for Objects Not Configured in the Initial CONFIG File The following command files that configure and start objects that are not configured in the initial CONFIG file. These files can serve as examples for you to modify as necessary. They also provide the basic files for recovery from system failure. Note. Objects that are not configured in the CONFIG file must be reconfigured after a system load.
Initial Configurations CONFBASE File CONFBASE File The CONFBASE file is placed on the target SYSnn subvolume specified in DSM/SCM. The CONFBASE file for a new system is on $SYSTEM.SYS00. It is unlikely you will ever need to load the system from the CONFBASE file. However, if the current configuration file has become corrupted and there is no other configuration file from which you can load the system, use the CONFBASE procedure in SCF Reference Manual for G-Series RVUs.
Initial Configurations Naming Conventions Used in the SCF0000 File for SCF Objects Naming Conventions Used in the SCF0000 File for SCF Objects This table describes the SCF0000 file-naming conventions for many SCF objects. This information is also contained in the $SYSTEM.ZSYSCONF.SCF0000 file. Refer to Objects That Must Not Be Renamed on page 8-10 before renaming any SCF objects.
Initial Configurations SCF Commands to Automate Disk Configuration is the slot number and port number mapped in the following way: Slot Number Router Port Number Slot Number Router Port Number 51 0 0 53 0 8 51 1 1 53 1 9 51 2 2 53 2 A 51 3 3 53 3 B 52 0 4 54 0 C 52 1 5 54 1 D 52 2 6 54 2 E 52 3 7 54 3 F is a number in the range 00 through 99.
Initial Configurations SWAN Concentrator Configurations SWAN Concentrator Configurations ServerNet wide area network (SWAN and SWAN 2) concentrators are connected to Ethernet switches or hubs that are connected to ports on Ethernet 4 ServerNet adapters (E4SAs). Each SWAN concentrator is uniquely identified by a case-sensitive configuration track-ID. This track-ID, which is case sensitive, is an important part of the system configuration for the SWAN concentrator.
Initial Configurations ServerNet Adapter Configurations ServerNet Adapter Configurations Any ServerNet adapters that are ordered with a system are configured at the factory and named using default names that include the adapter type. Subordinate objects associated with the ServerNet adapters, such as logical interface (LIF) names, are also given default names.
Initial Configurations Initial IP Addresses for System and System Consoles Initial IP Addresses for System and System Consoles New systems are shipped with Internet protocol (IP) addresses preconfigured for communication between the primary system console and your system (including those needed by OSM or TSM). After you install a new system, you must reconfigure these IP addresses to the addresses that are appropriate for your LAN environment: Note.
Initial Configurations IOAM Enclosures This figure shows the physical connections between the system and a system console, their initial IP addresses, and their functions. This configuration is called the setup configuration. Group 01 Processor 1 Processor 0 MSP0: 192.231.36.2 MSP1: 192.231.36.3 Operating System Access Using $ZTCP0: 192.231.36.10 Operating System Access Using $ZTCP1: 192.231.36.11 Dedicated LAN Ethernet Switch or Hub Primary System Console 192.231.36.1 VST905.
Part II. Planning Tasks This part provides information about planning and preparing your site for the installation of NonStop S-series system hardware. Section Title Abstract 9 The Planning and Configuration Process This section provides overviews of the process of installing a new system and the process of making hardware or software changes to an existing system.
Part II.
9 The Planning and Configuration Process This section provides overviews of the process of installing a new system and the process of making hardware or software changes to an existing system.
The Planning and Configuration Process People and Functions People and Functions The people involved in the planning, installation, and configuration of a NonStop S-series system are: Person* Function System planner Plans for the hardware and software installation of a new system or for changes to a system already installed. Arranges for site preparation, schedules the installation, and completes the Installation Document Packet.
The Planning and Configuration Process Advantages of Using the Installation Forms For the installer, the forms provide the following information: • • • A list of the equipment that was ordered A floor plan to indicate the arrangement of equipment in the chosen rooms Diagrams of the hardware connections to be made, including the connections between the external equipment and the ServerNet adapters Most of the blank installation forms are in Appendix C, Blank Forms.
The Planning and Configuration Process Installing a New System Installing a New System Installing a new system involves: Plan the System on page 9-4 Install the System on page 9-6 Test the Customized Operating System on page 9-7 Perform Final Tasks on page 9-7 Plan the System 1. Decide what size system to order. 2.
The Planning and Configuration Process Plan the System 8. Complete an Installation Document Packet containing all the installation forms for the new system. You need to complete the following forms: • • • • • • • • • • • • • • Installation Document Checklist. System Equipment Inventory Form. List only the equipment that you expect to receive with this order. Enclosure Arrangement Diagram. Floor Plan.
The Planning and Configuration Process Install the System Install the System 1. Install and cable the new system according to the instructions provided in the NonStop S-Series Hardware Installation and FastPath Guide. (This step does not include installing SWAN concentrators.) 2. Your HP trained service provider must install, cable, power-on, and configure IOAM enclosures in the new system. 3.
The Planning and Configuration Process Test the Customized Operating System 14. Decide whether you want or need to make any other configuration changes, such as adding other devices connected to Ethernet LANs to the system configuration or changing configuration attributes of disk or tape drives. 15. If you want to change the system configuration, follow the instructions in the NonStop S-Series Hardware Installation and FastPath Guide.
The Planning and Configuration Process Changing an Existing System Changing an Existing System Changing the System Name or System Number The system name and Expand system (node) number can be changed through the SCF Kernel subsystem. Because the attributes that change the system name and system number are stored in a SEEPROM in the enclosure backplane, changes to them require a system reset and reload to take effect.
The Planning and Configuration Process Enclosure Interleaving for Storage Devices Enclosure Interleaving for Storage Devices Within a topology branch (a processor enclosure and all the I/O enclosures connected directly to it), you can configure paths to disk, tape, and Open SCSI devices through adapters in different enclosures. This feature is called enclosure interleaving.
The Planning and Configuration Process Enclosure Interleaving for Storage Devices Recommendations These recommendations are not required, except where they conform to the preceding limitations. For all disk, tape, and Open SCSI Devices • • Configure the -P and -B paths to a device through different adapters, one on the X fabric and the other on the Y fabric. Configure a device to use the two processors that are in the same topology branch as the adapter used for the -P path to the device.
The Planning and Configuration Process Configuring $SYSTEM Disk Slots For All Internal Disk Drives • • Configure the primary half of a mirrored internal disk volume in an odd-numbered slot and the mirror half in the next higher even-numbered slot. Follow this recommendation even when the two halves are in different enclosures.
The Planning and Configuration Process Adding an Internal Disk Drive Adding an Internal Disk Drive 1. Complete or modify the following forms for the installer: • • • Installation Document Checklist. System Equipment Inventory Form. List only the disk drive that is being added to the system. System Enclosure Checklist. Show where in the enclosure the disk drive is to be installed. 2. Install the disk drive as described in the installation part of the replacement procedures on the CSSI Web.
The Planning and Configuration Process Adding a Tape Drive Adding a Tape Drive 1. Complete or modify the following forms for the installer: • • • • • Installation Document Checklist. System Equipment Inventory Form. List only the tape drive that is being added to the system. If you plan to connect the added tape drive to a PMF CRU or IOMF CRU, modify the appropriate configuration form for that PMF CRU or IOMF CRU.
The Planning and Configuration Process Adding a ServerNet Adapter Adding a ServerNet Adapter The supported ServerNet adapters are listed in ServerNet Adapters and Communication Devices on page F-3. 1. Complete or modify the following forms for the installer: • • • • • Installation Document Checklist. System Equipment Inventory Form. List only the ServerNet adapter that is being added to the system. System Enclosure Checklist. Show where in the enclosure the adapter is to be installed.
The Planning and Configuration Process Adding a SWAN or SWAN 2 Concentrator Adding a SWAN or SWAN 2 Concentrator Information about a SWAN concentrator also applies to a SWAN 2 concentrator unless otherwise noted. 1. Perform any site planning tasks needed for the SWAN concentrator, such as planning cable routing and determining where the SWAN concentrator should be installed. General site planning is described in Section 12, Site Planning and Preparation.
The Planning and Configuration Process Adding an AWAN Server Adding an AWAN Server You can add an asynchronous wide area network (AWAN) server to your system online. For information about adding an AWAN 3883, 3884, or 3885 server, refer to the AWAN 3883/4/5 Access Server Installation and Support Guide. (These models are now obsolete.) For information about the AWAN 3886 access server, refer to the AWAN 3886 Server Installation and Configuration Guide.
The Planning and Configuration Process Adding an Open SCSI Device The WAN subsystem software components consist of: • • • • • • One WAN manager process One or more concentrator manager (ConMgr) processes One or more SNMP trap multiplexer processes One or more Trivial File Transfer Protocol (TFTP) server processes One or more WANBoot processes WAN shared driver WAN hardware requires two E4SAs (Ethernet controllers) for fault tolerance, 10megabit switches or hubs, cables, interface converter cables, and
The Planning and Configuration Process Adding or Changing the Configuration of Other Peripheral Devices Adding or Changing the Configuration of Other Peripheral Devices The procedure for adding or changing the configuration of a peripheral device depends on the device being added or changed. Configuration changes to peripheral devices can be performed online. In G06.12 and previous RVUs, the system manager must explicitly configure the WANBoot, TFTP, and SNMPTMUX processes. In G06.
10 Planning for System Availability and Support This section describes advance planning required for minimizing the total number of minutes that an application or system is unavailable.
Planning for System Availability and Support How Availability Is Measured How Availability Is Measured HP believes that the measurement of availability should be from the end user’s perspective. Simply recording that a certain hardware or software component is not operating is not enough; you must also take into consideration the user’s ability to access the service, the quality of the service provided, and the acceptability of the response time to the user.
Planning for System Availability and Support Evaluating System Performance and Growth Evaluating System Performance and Growth Evaluating system performance and growth involves tracking and anticipating growth and then establishing plans to accommodate that growth.
Planning for System Availability and Support Implementing a Formal Change-Control Process to Manage Change Implementing a Formal Change-Control Process to Manage Change Change control is the process for proposing, planning, implementing, and testing change and is a key requirement for minimizing the duration of planned outages.
Planning for System Availability and Support Preventing Unplanned Outages Preventing Unplanned Outages In addition to minimizing the number and duration of planned outages, preventing unplanned outages is an important component of minimizing outage minutes. Causes of Unplanned Outages Studies have identified four common causes of unplanned outages (in order of greatest frequency): 1. Operations management errors 2. Non-fault-tolerant hardware configuration 3. Non-fault-tolerant application design 4.
Planning for System Availability and Support • • • Minimizing Unplanned Outage Minutes Monitoring critical objects in your system environment. Automating operations, intervention, recovery, and performance-monitoring tasks and auditing your system and applications for fault tolerance. Creating an alternate system disk so that it is possible to recover from unexpected difficulties in any of these problem-management procedures.
Planning for System Availability and Support Calculating the Maximum Power-Fail Delay Time Calculating the Maximum Power-Fail Delay Time 1. Software in each processor calculates a power-fail delay time using the following information from the service processor: • • The battery charge. The hardware configuration of that group. The more components in the group, the shorter the amount of time the batteries can power all the components.
Planning for System Availability and Support • Battery Considerations In case of an AC power failure, all equipment in all the system enclosures continues to operate for the shorter of these two times: ° ° The configured maximum power-fail delay time The shortest calculated maximum power-fail delay time of any group in the entire system The operating system continues to process data until that shortest calculated maximum power-fail delay time expires.
11 Planning for LAN Communications This section describes requirements and considerations for configuring local area networks (LANs) for NonStop S-series servers.
Planning for LAN Communications Dedicated LAN for SWAN Concentrators Dedicated LAN for SWAN Concentrators The dedicated LAN for SWAN concentrators can connect only to SWAN or SWAN 2 concentrators, the Ethernet ports on E4SAs and FESAs that connect to the SWAN concentrators, and Ethernet switches or hubs provided by HP. Caution. If your system contains IOAM enclosures, you must have a dedicated LAN for SWAN concentrators that is separated from the LAN for the rest of the system.
Planning for LAN Communications Public LANs This shows a processor enclosure connected to several LANs. Public LAN G Dedicated Service LAN Dedicated LAN for SWAN Concentrators Group 01 HP NonStop S-Series Planning and Configuration Guide—523303-015 11- 3 VST912.
Planning for LAN Communications Multiple IP Addresses Needed Multiple IP Addresses Needed Servers require Internet protocol (IP) addresses for some of the system components that are connected to LANs: System Component Number of IP Addresses Required MSP0. Ethernet port on the PMF CRU in group 01, module 01, slot 50. Used for a low-level link. 1 MSP1. Ethernet port on the PMF CRU in group 01, module 01, slot 55. Used for a low-level link.
Planning for LAN Communications Planning for a Dedicated Service LAN Planning for a Dedicated Service LAN System consoles for OSM and TSM connect to a server through a dedicated Ethernet LAN. Ethernet cables are connected from the Ethernet ports on the PMF CRUs in group 01 to Ethernet switches or hubs, and system consoles then connect to the Ethernet switches or hubs.
Planning for LAN Communications Operating Configurations of Dedicated Service LANs Operating Configurations of Dedicated Service LANs You can configure the dedicated service LAN in several different ways, as described in the OSM Migration Guide or TSM Configuration Guide. HP recommends that you use a fault-tolerant LAN configuration. For a faster configuration option for the OSM Service Connection only, see the OSM Migration Guide. Fault-Tolerant Dedicated Service LAN Configuration Group 01 MSP0: xxx.
Planning for LAN Communications Operating Configurations of Dedicated Service LANs You can use these basic types of operating configurations: • • • • One System Console Managing One System (Setup Configuration) on page 11-7 One System Console Managing Multiple Systems on page 11-8 Multiple System Consoles Managing One System on page 11-9 Multiple System Consoles Managing Multiple Systems on page 11-12 Note. The figures in this section are not intended as wiring diagrams.
Planning for LAN Communications Operating Configurations of Dedicated Service LANs One System Console Managing Multiple Systems Server Primary System Console Modem Remote Service Provider (GCSC) Ethernet Switch or Hub Server VST082.vsd The one OSM or TSM system console on the LAN must be configured as the primary system console.
Planning for LAN Communications Operating Configurations of Dedicated Service LANs Multiple System Consoles Managing One System This subsection contains three variations of this configuration: • • • Primary and Backup System Consoles Managing One System (Recommended Operating Configuration) on page 11-9 Multiple System Consoles Managing One System on page 11-10 Cascading Ethernet Switch or Hub Configuration on page 11-11 Primary and Backup System Consoles Managing One System (Recommended Operating Conf
Planning for LAN Communications Operating Configurations of Dedicated Service LANs Multiple System Consoles Managing One System Remote Service Provider (GCSC) Remote Service Provider (GCSC) Server Primary System Console Backup System Console Dial-Out Modem Dial-In Modem Ethernet Switch or Hub 1 G System Console Ethernet Switch or Hub 2 System Console System Console System Console VST063.vsd Two Ethernet switches or hubs provide fault tolerance and extra ports for adding system consoles.
Planning for LAN Communications Operating Configurations of Dedicated Service LANs Cascading Ethernet Switch or Hub Configuration Remote Service Provider (GCSC) Remote Service Provider (GCSC) Server Primary System Console Backup System Console Dial-Out Modem Dial-In Modem Ethernet Switch or Hub 1 Ethernet Switch or Hub 2 Ethernet Switch or Hub 3 Ethernet Switch or Hub 4 System Console System Console VST999.
Planning for LAN Communications Operating Configurations of Dedicated Service LANs Multiple System Consoles Managing Multiple Systems Remote Service Provider (GCSC) Remote Service Provider (GCSC) \A Primary System Console Backup System Console Dial-Out Modem Dial-In Modem Ethernet Switch or Hub 2 Ethernet Switch or Hub 1 System Console \B \C \D VST062.vsd The servers must have fault-tolerant connections to the Ethernet switches or hubs.
Planning for LAN Communications Planning for Remote Dial-In and Dial-Out Support Planning for Remote Dial-In and Dial-Out Support If you plan to configure a system for both dial-in and dial-out remote support, HP recommends that you configure two system consoles and two modems. One system console and modem is used for dial-in access to the system, and the other system console and modem is used for dial-out access from the system.
Planning for LAN Communications Planning for Remote Dial-In and Dial-Out Support HP NonStop S-Series Planning and Configuration Guide—523303-015 11-14
12 Site Planning and Preparation This section provides information you need to plan and prepare the site for a NonStop S-series system. Related Sources 12-1 Selecting the Rooms and Assigning Floor Space 12-2 Planning for Data Communications 12-3 Planning for System Consoles 12-5 Planning for System Power 12-6 Meeting the Environmental Requirements 12-10 Preparing the Delivery Route 12-13 Site planning is a crucial step in ensuring the smooth installation of new equipment.
Site Planning and Preparation Selecting the Rooms and Assigning Floor Space Selecting the Rooms and Assigning Floor Space By carefully selecting the one room or several rooms that will contain the system equipment, you can making a lot of adjustments to make the rooms you select suitable for the equipment, and you can avoid moving your equipment if you later decide to expand the system.
Site Planning and Preparation • • Planning for Data Communications To ensure the security of your system, you might want to isolate parts of the system into different rooms and control access to those rooms. Depending on your needs, you might want to plan a tape library, which is a separate area or room that contains system image tapes (SITs), site update tapes (SUTs), backup tapes, RVU tapes, TMF online dumps and audit dumps, and any tapes required to run applications.
Site Planning and Preparation Requirements Requirements If you plan to allow access to your system by a remote service provider, you must have at least one telephone line available in the room where the system is installed. It must be a direct line that does not go through a switchboard.
Site Planning and Preparation SWAN Concentrators 04 53 5 0 0 1 11 B F SEIOM SE IO MB 01 53 F 11 04 50 SEB 015304 IOMF 1150 SEB 015304 IOMF 1150 VDT 823 VSD SWAN Concentrators ServerNet wide area network (SWAN) concentrators can support modem connections. When planning for data communications, be sure to consider data communications lines that are to be connected to SWAN concentrators. For more information about SWAN concentrators, refer to the SWAN Concentrator Installation and Support Guide.
Site Planning and Preparation Planning for System Power Planning for System Power Considerations 12-6 Branch Circuits 12-8 Uninterruptible Power Supplies (UPSs) 12-8 Ethernet Switches or Hubs 12-9 System Enclosures 12-9 Peripheral Devices 12-9 AC Power Cords 12-9 Considerations For detailed information about planning for system power, contact your HP trained service provider.
Site Planning and Preparation • • • • • • • • • Considerations Contact your HP trained service provider for information about establishing a signal grounding reference grid. A reference grid is highly recommended for systems consisting of more than four enclosures. For information about IOAM power requirements, refer to Appendix G, Modular Power Information. For systems that include more than two system enclosures, HP strongly recommends using a three-phase AC power source.
Site Planning and Preparation Branch Circuits Branch Circuits Branch circuit requirements are: • • • • • • • All dedicated branch circuits supplying the system enclosures and tape drives must originate from the same branch circuit breaker panel. HP highly recommends that branch circuits for other peripheral equipment, such as system consoles, also originate from the same branch circuit breaker panel as that for system enclosures.
Site Planning and Preparation Ethernet Switches or Hubs Ethernet Switches or Hubs Each Ethernet switch or hub you plan to install requires an AC power source. For information about the use of Ethernet switches or hubs, refer to Section 11, Planning for LAN Communications. System Enclosures Auto-ranging power supplies in the PMF CRUs and IOMF CRUs automatically configure themselves for either 100-120 V AC or 200-240 V AC operation upon application of AC power.
Site Planning and Preparation Meeting the Environmental Requirements Meeting the Environmental Requirements In addition to system power, these environmental factors affect the performance of your system: Computer-Room Construction 12-10 Temperature and Humidity 12-10 Fire and Safety Precautions 12-11 Emergency Power-Off (EPO) Equipment 12-11 Electrostatic Discharge (ESD) Control and Protection 12-12 Other Factors 12-13 These environmental factors are briefly discussed here.
Site Planning and Preparation Fire and Safety Precautions Fire and Safety Precautions Proper precautions for fire prevention and safety in a computer room include: • • • • • Use noncombustible materials and supplies Install smoke detectors and fire-extinguishing equipment Install emergency power-off (EPO) equipment Follow proper power and grounding guidelines Develop proper emergency procedures Emergency Power-Off (EPO) Equipment An emergency power-off (EPO) disconnect is required in the United States
Site Planning and Preparation Electrostatic Discharge (ESD) Control and Protection When the EPO contacts are open, there is 56 V DC across them. The contacts should be rated at a minimum of 75 V. When the EPO switch closes (the switch shorts out the pins on the EPO connector on the system enclosure) there is a 5 mA current for each enclosure connected to the switch. A single pair of contacts rated at 200 mA can support a 16-enclosure system.
Site Planning and Preparation Other Factors Other Factors Other environmental factors to consider include: • • • • • Site cleaning and maintenance Ergonomics and human factors Acoustic noise control Computer-room lighting Computer-room security Preparing the Delivery Route Before your system arrives, you must prepare the delivery route to the computer rooms.
Site Planning and Preparation Preparing the Delivery Route HP NonStop S-Series Planning and Configuration Guide—523303-015 12-14
13 Completing the Installation Plan This section describes how to finish the planning tasks described in this guide, including preparing an Installation Document Packet containing forms and worksheets that describe how to arrange the enclosures, what hardware is present, and what cables are required to build your system: Create the Installation Schedule 13-1 Assemble the Installation Document Packet 13-2 Installation Document Checklist 13-3 System Equipment Inventory Form 13-5 Enclosure Arrangement
Completing the Installation Plan Assemble the Installation Document Packet Assemble the Installation Document Packet This subsection contains instructions for completing and assembling the installation forms into a Installation Document Packet. If you are adding to or reconfiguring an existing system, you might not use all these forms. If you are making a large addition or reconfiguration, make sure you also have forms that show the system before the addition or reconfiguration.
Completing the Installation Plan Installation Document Checklist Installation Document Checklist The Installation Document Checklist tells the installer and the configuration planner which forms, and how many of each form, are present in the Installation Document Packet. Complete the Installation Document Checklist as follows, after you have completed all the installation forms for your system. Task Comments Be sure that you have completed all the other installation forms for your system.
Completing the Installation Plan Installation Document Checklist Example of a Completed Installation Document Checklist Installation Document Checklist Form, Diagram, or Checklist # Pages x System Equipment Inventory Form 1 x Preinstalled I/O Device Cable Checklist 1 x Enclosure Arrangement Diagram 1 x Floor Plan 1 x System Enclosure Checklist 2 x PMF CRU Configuration Form and PMF 2 CRU Configuration Form 4 System Name \Case1 Date 07 / 22 / 96 1 Page 1 of Form, Diagram, or Checklist
Completing the Installation Plan System Equipment Inventory Form System Equipment Inventory Form The System Equipment Inventory Form lists system enclosures and equipment that is not installed in a system enclosure that you expect to receive from HP. The installer uses this list to verify that all equipment ordered is received. (Equipment installed in a system enclosure, such as ServerNet adapters and disk drives, appears on the System Enclosure Checklist.
Completing the Installation Plan System Equipment Inventory Form Example of a Completed System Equipment Inventory Form System Equipment Inventory Form Part or Product Number 7194 System Name \Case1 Date 07 / 22 / 96 Page 1 of 1 Description Quantity Ordered Processor enclosure, double-high 2 S-series system console 2 S-series EPO cable 2 675-004 ServerNet cable, 4.5 feet (1.
Completing the Installation Plan Enclosure Arrangement Diagram Enclosure Arrangement Diagram The Enclosure Arrangement Diagram tells the installer how the system enclosures are to be arranged. Complete the Enclosure Arrangement Diagram as follows. Task Comments Enter the name of the system in the System Name field and date in the date field. This system name must match the system name on all other forms in this packet. Enter the Building name or number and room number in the Building and Room fields.
Completing the Installation Plan Enclosure Arrangement Diagram Example of a Completed Enclosure Arrangement Diagram System Name \Case1 Date 07 / 21 / 96 2239 5 Building __________________ Room__________________ System Number Scale: 1/4 inch = 1 foot 10 (In Expand Network) 1 Number of Rows Enclosure Arrangement Diagram Processor Enclosure Group 02 Processor Enclosure Group 01 Note which enclosures are base enclosures and which are stacked enclosures.
Completing the Installation Plan Floor Plan Floor Plan The Floor Plan allows you to plan and indicate where the system components and furniture should be placed in your computer rooms relative to preinstalled cables, power outlets, and communications lines. With this form and the templates for furniture and system components from Appendix C, Blank Forms, you can represent each computer room and its contents to scale. (These templates are drawn to the scale 1/4 inch = 1 foot—0.64 centimeter = 30.
Completing the Installation Plan Floor Plan Example of a Completed Floor Plan System Name \Case1 Date 07 / 22 / 96 Floor Plan Building 5 2239 Room Scale: 1/4 inch = 1 foot Cabinet 5190 7159 $Tape1 Pedestal RECEPTACLES SWAN Chair Group 1 System Enclosure System Enclosure Service Service Group 2 modem (Primary) POWER 5170 7159 $Tape0 Pedestal Appearance Appearance File System Console Hubs Chair Desk (A) Cabinet TAPES Shelves (A) SUPPLIES Hub Group 2 power Group 1 power Power fo
Completing the Installation Plan Preinstalled I/O Device Cable Checklist Preinstalled I/O Device Cable Checklist If you have already installed I/O device cables for use with this system, use the Preinstalled I/O Device Cable Checklist to tell the installer which cables are to be connected to the system equipment being installed. (This information also included in the Floor Plan.) Complete a Preinstalled I/O Device Cable Checklist as follows.
Completing the Installation Plan Preinstalled I/O Device Cable Checklist Example of a Completed Preinstalled I/O Device Cable Checklist Preinstalled I/O Device Cable Checklist Cable ID Tag 10Base-T to Building Hub System Name \Case1 Date 07 / 21 / 96 1 of 1 Page Floor Plan Room 2239 East wall VST314.vsd VST231.
Completing the Installation Plan System Enclosure Checklist System Enclosure Checklist The System Enclosure Checklist tells the installer what configurable items were ordered and are installed in each processor enclosure and I/O enclosure. Make a copy of this form for each system enclosure in the configuration you are documenting. Complete the System Enclosure Checklist as follows. Task Comments (page 1 of 2) Enter the name of the system in the System Name field.
Completing the Installation Plan Task System Enclosure Checklist Comments (page 2 of 2) Complete the Service Side area of the form: For I/O enclosures: In slots 50 and 55: enter “IOMF.” In slots 51 through 54: If the slot will contain a ServerNet adapter, enter the name and type of the ServerNet adapter. If the slot will not contain a ServerNet adapter, enter “filler panel.” When you have completed this form, enter the date in the Date field.
Completing the Installation Plan System Enclosure Checklist Example of a Completed System Enclosure Checklist System Name \Case1 01 Group Number System Enclosure Checklist 01 Module Number Shaded areas indicate nonconfigurable components Date 07 /21 / 96 Appearance Side: $DATA01-P 4608 $DATA01-M 4608 $DATA02-P 4608 $DATA02-M 4608 $DATA03-P 4608 $DATA03-M 4608 $DATA04-P 4608 $DATA04-M 4608 01 02 03 04 05 06 07 08 $SYSTEM-P 4608 $SYSTEM-M 4608 $DSMSCM-P 4608 $AUDIT-M 4608 $DATA0
Completing the Installation Plan PMF CRU Configuration Forms PMF CRU Configuration Forms The PMF CRU Configuration Form and PMF 2 CRU Configuration Form tell the installer about each PMF CRU in the system and the configurable items associated with it. These completion instructions apply to both forms. Task Comments (page 1 of 2) Enter the name of the system in the System Name field. This system name must match the system name on all other forms in this packet.
Completing the Installation Plan PMF CRU Configuration Forms Task Comments (page 2 of 2) If this PMF CRU is in group 01, complete the Ethernet Port block. If this PMF CRU is not in group 01, leave this Ethernet Port block empty. If this PMF CRU is in group 01, slot 50: 1. In the IP Address field, enter the initial IP address assigned to this port. You might want to indicate the IP address that will replace the initial IP address. 2. In the Adapter Name field, enter $ZZLAN.MIOE0. 3.
Completing the Installation Plan PMF CRU Configuration Forms Example of a Completed PMF CRU Configuration Form System Name \Case1 Date 07 / 21 / 96 PMF CRU Configuration Form Shaded areas indicate nonconfigurable components Group 01 Module 01 Slot 55 SCSI Port Product Number: 5175 SCF Name: $TAPE0 POWER ON SCSI Cable: PN 131369 SCSI SERIAL CONSOLE ETHERNET Ethernet Port IP Address: Initially 192.231.36.
Completing the Installation Plan PMF CRU Configuration Forms Example of a Completed PMF 2 CRU Configuration Form System Name \Case1 Date 07 / 21 / 96 PMF 2 CRU Configuration Form Shaded areas indicate nonconfigurable components Group 01 Module 01 Slot 50 SCSI Port Product Number: 5794 SCF Name: $TAPE0 POWER ON SCSI SERIAL CONSOLE AUX DC POWER ETHERNET POWER-ON CABLE SCSI Cable: PN 131369 Ethernet Port IP Address: Initially 192.231.36.10 Get new address from LAN department Adapter Name: $ZZLAN.
Completing the Installation Plan IOMF CRU Configuration Forms IOMF CRU Configuration Forms The IOMF CRU Configuration Form and IOMF 2 CRU Configuration Form tell the installer about each IOMF CRU in the system and the configurable items associated with it. These instructions apply to both forms. Task Comments Enter the name of the system in the System Name field. This system name must match the system name on all other forms in this packet.
Completing the Installation Plan IOMF CRU Configuration Forms Example of a Completed IOMF CRU Configuration Form System Name \Case 1 Date 07 / 21 / 96 IOMF CRU Configuration Form Shaded areas indicate nonconfigurable components Group 11 Module 01 Slot 50 ServerNet Connection ServerNetCable: 126027 ServerNet Connector: Group 01 Module 01 5 Slot 51 SCSI Port Product Number: Available for future use.
Completing the Installation Plan ServerNet Adapter Configuration Forms ServerNet Adapter Configuration Forms A variety of ServerNet adapters are available for use in NonStop S-series servers. Configuration forms for each adapter are located in the installation and support guide for that adapter. To add ServerNet adapter configuration forms to your Installation Document Packet, copy the necessary forms from the adapter manuals. Follow any planning instructions in the adapter manuals.
Completing the Installation Plan ServerNet Cabling Forms ServerNet Cabling Forms The ServerNet cabling forms are provided to help you determine the number and type of ServerNet cables that you need to cable a system in one row. If you are cabling a system with enclosures arranged in multiple rows, you also use the Cross-Row Cabling Worksheets described on page 13-25.
Completing the Installation Plan ServerNet Cabling Forms Example of a Completed ServerNet Cabling Form System Name Date ServerNet Cabling: Tetra 16 Topology, Processor Enclosures From Group Slot a 01 To Group Slot 51 02 51 01 52 02 52 01 51 03 51 01 52 03 52 01 51 04 51 01 52 04 52 01 51 05 51 01 52 05 52 02 51 04 51 02 52 04 52 02 51 03 51 02 52 03 52 02 51 06 51 02 52 06 52 03 51 04 51 03 52 04 52 03 51 07 51 03 52 07 52 04 51 08 51 04 52 08 52 Page \Case 1 0
Completing the Installation Plan Cross-Row Cabling Worksheets Cross-Row Cabling Worksheets The cross-row cabling worksheets are provided to help you determine the number and type of ServerNet cables that you need to cable a system with enclosures arranged in multiple rows. These worksheets are used with the ServerNet Cabling Forms described on page 13-23.
Completing the Installation Plan IOAM Worksheets Example of a Completed Cross-Row Cabling Worksheet System Name /Case 1 Date 07 / 21 / 97 Page 01 of 01 From group 01 to group 12 Standard Measurements 31 inches (cabinet depth) 6 inches of slack (3 inches per cable end) + 37 + 60 in Variable Measurements Width of service aisle (48 inches minimum) x If cable is installed under a raised floor + 12 in Amount of slack for cable, based on depth of raised floor If cable runs down from a x single enclos
Completing the Installation Plan Final Planning Checklist Final Planning Checklist Use the Final Planning Checklist to determine whether you have done all planning that must be done before you are ready to install or upgrade your system. Check off each item as you complete it and enter the date when you are done.
Completing the Installation Plan Finish Planning Finish Planning After you complete the Installation Document Packet: 1. If you completed this Installation Document Packet while planning for an upgrade, update all copies of the original Installation Document Packet. 2. File a copy of the Installation Document Packet for future reference. 3. Distribute copies of the Installation Document Packet as needed. This person ...
14 Planning for CRU Replacement When you replace a CRU online, you must prepare all elements in the system that are affected by the removal of that CRU, such as other CRUs and processes. Use the procedure in this section and worksheets to determine which components of a system are affected by removal of a PMF CRU, SEB, or MSEB. To replace a PMF CRU, SEB, or MSEB, you must use a guided replacement tool which automatically detects the affected components and prepares the system for CRU replacement.
Planning for CRU Replacement ServerNet Communication Pathways Worksheets This figure shows the worksheets for the X and Y fabrics for a system configured as a Tetra 16 topology. ServerNet Communication Pathways: Tetra 16 Topology, Y Fabric With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the CRU you plan to remove. If you are removing a PMF CRU, check this box.
Planning for CRU Replacement Completing the Worksheets Completing the Worksheets An example illustrates the steps for completing the ServerNet communication pathways worksheets. The example system is a Tetra 16 system containing the following enclosures: 01, 11, 12, 13, 14, 15 02, 21, 22, 23, 24, 25 03, 31, 32, 33, 34, 35 04, 41, 42, 43, 44, 45 05, 51, 52, 53, 54 06, 61, 62, 63, 64 In this example, the SEB will be removed from group 02, slot 51 (the X fabric).
Planning for CRU Replacement 1. Highlight All System Enclosures 1. Highlight All System Enclosures Using a highlighter, highlight all the enclosures your system currently contains. Put a check mark in the first box. ServerNet Communication Pathways: Tetra 16 Topology, X Fabric With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the CRU you plan to remove. If you are removing a PMF CRU, check this box.
Planning for CRU Replacement 2. Black Out the CRU to Be Removed 2. Black Out the CRU to Be Removed Black out the CRU you plan to remove. Put a check mark in the second box. If you are removing a PMF CRU, put a check mark in the third box and black out the PMF CRU shown in the same enclosure on the worksheet for the other fabric. The other PMF CRU in the same enclosure will also lose access to this fabric.
Planning for CRU Replacement 3. Trace Unaffected Pathways 3. Trace Unaffected Pathways Darken the pathways of communication that remain on your system with a heavy line. ServerNet Communication Pathways: Tetra 16 Topology, X Fabric With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the CRU you plan to remove. If you are removing a PMF CRU, check this box.
Planning for CRU Replacement 4. Draw a Line Around Affected Groups 4. Draw a Line Around Affected Groups Draw a line around the groups that cannot be reached when the CRU is removed, indicated by the pathways that are not darkened. Put a check mark in the last box. ServerNet Communication Pathways: Tetra 16 Topology, X Fabric With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the CRU you plan to remove.
Planning for CRU Replacement 4.
15 Planning for System Configuration When you install a new system or change the configuration of a system, you must plan configuration tasks in advance. This section provides an overview of configuration tasks. Detailed instructions for performing the configuration tasks are located in the NonStop S-Series Hardware Installation and FastPath Guide or other manuals referred to here for related configuration needs. Caution.
Planning for System Configuration Installing a Product Revision Installing a Product Revision A product revision, such as an SPR, might include one or more fixes to programs supplied by HP, or it might contain code that adds new function to an HP software product. Installing a product revision might or might not require that the system be shut down. Follow the installation instructions provided with the product revision. The DSM/SCM User’s Guide describes installing product revisions in detail.
Planning for System Configuration Online Configuration Tasks The modified CONFTEXT file is used by DSM/SCM when generating a new operating system image. Refer to the DSM/SCM User’s Guide. Online Configuration Tasks Subsystem Control Facility (SCF) The Subsystem Control Facility (SCF) configures, controls, and collects information about subsystems and the objects (devices, subdevices, processes, and so forth) belonging to each subsystem.
Planning for System Configuration Subsystem Control Facility (SCF) Subsystems Running a G-Series RVU A system running a G-series RVU has multiple subsystems that handle the configuration and management of subsystem-specific generic processes, I/O processes, and system hardware. This illustration provides an overview of the configuration components in these systems: $ZPM $ZCNF CONFIG $SYSTEM.ZSYSCONF.CONFIG $ZZSTO $ZZLAN $ZZKRN $ZZWAN VST115.
Planning for System Configuration Subsystem Control Facility (SCF) Each subsystem manager or monitor process is started by the $ZPM persistence manager process at system load and has the following functions: • • • • Creates I/O processes and other manager processes within the subsystem Configures subsystem objects such as adapter hardware and the ServerNet addressable controllers (SACs) supported by those adapters Identifies the names of processes that must be reserved at system load Monitors its proces
Planning for System Configuration Subsystem Control Facility (SCF) The system configuration files used on systems running G-series RVUs are: On the $SYSTEM.SYSnn subvolume: File Type File Name Description Base CONFIG CONFBASE Contains the minimal configuration to load the system. You use this file when you want to rebuild the system configuration from the absolute minimum configuration. On the $SYSTEM.
Planning for System Configuration Subsystem Control Facility (SCF) This figure illustrates the differences between the types of system configuration files: Initial System Load CONFBASE + Base CONFIG = CONFIG Initial CONFIG SCF0000 File Normal System Load CONFIG Current CONFIG Saved Configuration CONFIG Current CONFIG Automatically Saved Configuration + = -> SCF SAVE CONFxxyy Saved CONFIG CONFIG CONFSAVE Current CONFIG Autosaved CONFIG CONFxxyy CONFIG System Load From Another CONFIG
Planning for System Configuration Kernel-Managed Swap Facility (KMSF) Kernel-Managed Swap Facility (KMSF) Kernel-managed swap space manages virtual memory using swap files controlled by the operating system. Pages of memory not currently in use are swapped, or copied, to disk during a shortage of available physical memory. These memory pages are swapped back or overwritten to physical memory when the code or data are needed. When swapped to disk, the data are stored in swap files.
Planning for System Configuration OSM Package KMSF and the Operations Environment KMSF affects routine operations. Operations staff must monitor KMSF and operator messages to spot potential problems and dynamically add swap space as needed. Event Management Service (EMS) messages are generated to alert staff to swap files that have reached a configured threshold and to changes in KMSF configuration.
Planning for System Configuration Creating an Alternate System Disk For information about performing these configuration changes using TSM, refer to: • TSM Configuration Guide • • • TSM Low-Level Link Application online help TSM Notification Director Application online help TSM Online User Guide Creating an Alternate System Disk Reasons to create an alternate system disk include: • • • You can minimize unplanned outage minutes by having an alternate system disk configured as a backup.
Planning for System Configuration Automating System Shutdown Automating System Shutdown Automating system shutdown with a collection of shutdown files helps the operator bring the system to an orderly halt. The shutdown file sequence reverses the order of commands in the startup file sequence: applications are shut down first, followed by the spooler and other system software.
Planning for System Configuration Adding Super-Group User IDs persistent, create them as generic processes in the system configuration database as described in the NonStop S-Series Hardware Installation and FastPath Guide. For more information about persistence and the $ZPM persistence manager, refer to the SCF Reference Manual for G-Series RVUs.
Part III. Appendixes These appendixes provide part numbers for all CRUs; system specifications; blank system installation forms; examples of how to plan, cable, and configure systems; lists of manuals and online help for NonStop S-series servers; and information about supported hardware and configurations. Appendix Title Abstract A Part Numbers This appendix lists the part numbers for all CRUs used on NonStop S-series servers. B Specifications This appendix describes system specifications.
Part III.
A Part Numbers This appendix lists the part numbers for all the customer-replaceable units (CRUs) used on NonStop S-series servers. Some FRUs are included, but they are identified.
Part Numbers NonStop S-Series Enclosures Cables and Cable Assemblies A-26 AC Power Cords, Enclosures Without Power Shelves A-29 AC Power Cords, Enclosures With Power Shelves A-30 Note. Each part number follows one of two numbering systems: • • Old Tandem part numbers start with 0 or 1. HP part numbers start with T or U. All part numbers contain nine digits. (Only the first six digits are shown in these tables.) Any of these types of part numbers might appear on a part number label.
Part Numbers PMF CRUs Description Part Number (page 2 of 2) Memory See page A-4 Modems See page A-20 Modular SEB (MSEB) and PICs See page A-5 Panel (for power shelf) U27325 PMF CRU See page A-3 Power supply U24597 SCSI passthrough terminator U31491 SCSI terminator U22030 ServerNet expansion board (SEB) See page A-5 ServerNet adapters See page A-13 SWAN concentrators See page A-19 System console See page A-6 Tape drives, 5190 tape subsystem, or 5258 tabletop tape drive See page A
Part Numbers Memory Server Memory Size Part Number (page 2 of 2) 1970-C 2 GB 425692 1970-D 4 GB 425693 1 GB 429955 1971-C 2 GB 424403 1971-D 4 GB 429956 1971-E 8 GB 527446 1971-F 16 GB 429957 2 GB 526490 1973-D 3 GB 526491 1973-E 4 GB 526492 1 GB 523621 1972-C 2 GB 524397 1972-D 4 GB 523622 1972-E 8 GB 527445 1972-F 16 GB 523623 2 GB 526493 1974-D 4 GB 526494 1974-E 8GB 526495 1974-F 16 GB 526496 PMF CRU S76000 1971-B S78000 1973-C S86000 1972-
Part Numbers IOMF CRUs and Related Components IOMF CRUs and Related Components Description Product Number Part Number IOMF CRU 1952 U29574 IOMF 2 CRU 1980 426924 Emitter-coupled logic (ECL) PIC 6750M-E 425640 Multimode fiber-optic (MMF) PIC 6750M-S 427497 Serial-copper PIC 6750M-C 420302 Single-mode fiber-optic (SMF) PIC 6750M-L 420304 Description Product Number Part Number ServerNet expansion board (SEB) 6750 U19566 Modular ServerNet expansion board (MSEB) 6750M 424991 Emitt
Part Numbers Visual Image Package Part Number (page 2 of 2) Description Phillips screws, M5 PNHD (6 each) U07469 Read-Me instructions U41618 Wrench, hex key, short door, 4-mm U28240 Visual Image Package Product Number Description Part Number Appearance-side tall door 523366 Service-side tall door 523379 Side panel, enclosure 523363 Locking wrench (hex wrench) U22855 Visual image package instructions 524411 Full visual image upgrade kit (two doors with side panel) 7285 423634 Appeara
Part Numbers Internal Disk Drives Description Product Number Mouse, PS2 compatible Part Number (page 2 of 2) 420237 System HSSC/IPAQ 2.2 US S7X-IPAQM 522597 System HSSC/IPAQ 2.2 UK S7X-IPAQM 522596 PC HSSC EVO Slim Desktop US S7X-NSC1 526248 PC HSSC EVO Slim Desktop UK S7X-NSC1 526251 System HSSC Slim Desktop US S7X-PC1000 526223 PC accessory box for system console U37588 Internal Disk Drives Description Part Number 4604 disk drive (4.2 gigabyte) U21814 4608 disk drive (8.
Part Numbers Tape Drives Description Part Number (page 2 of 2) Extender (for connecting 6760 adapter to tape drive over fiber-optic cable) 422655 3.3 feet (1.0 meter), with K-series coupler U42296 3.3 feet (1.0 meter) U33688 6.6 feet (2.0 meters) U33689 32.8 feet (10.0 meters) U33690 82.0 feet (25.0 meters) U33691 64.1 feet (50.0 meters) U33692 328.1 feet (100.0 meters) U33693 820.3 feet (250.0 meters) U33694 1640.5 feet (500.
Part Numbers Tape Libraries Description Part Number (page 2 of 2) 5257 SuperDLT drive with ACL for a tape enclosure 522209 5258 ACL tabletop tape drive See page A-11.
Part Numbers 5190/94 Tape Drive and Related Components 5190/94 Tape Drive and Related Components Description Part Number (page 1 of 2) 5190 cartridge tape drive T97673 5190 ACL cartridge tape drive* T97671 5190 tape drive user’s kit U01011 5194 36-track tape drive U13644 5194 ACL cartridge tape drive* U13643 5194 tape drive user’s kit U13858 519x tape cartridge magazine (for ACL) U00188 6760 ServerNet/DA (ServerNet device adapter) U23201 6761 ServerNet/DA fiber-optic plug-in card (F-PIC)
Part Numbers 5258 ACL Tabletop Tape Drive and Related Components Description Part Number (page 2 of 2) SCSI passthrough terminator U31491 SCSI terminator for tape drive CRU T13601 * FRU 5258 ACL Tabletop Tape Drive and Related Components Part Number Description 5258 ACL tabletop tape drive with ACL 522211 Cables, StorageTek (STK), SCSI, 68-pin external: 1 meter (3.3 feet) 424360 3 meters (9.
Part Numbers Linear Tape Open (LTO) Tape Drive and Related Components Description Part Number (page 2 of 2) ruggedized, 328 feet (100 meters) 427280 ruggedized, 656 feet (200 meters) 427281 62.5/125 multimode fiber-optic cables (F9x or F12x) FDDI to SC adapter cable set (contains 1-meter cable and U36322 coupler) U42296 FDDI coupler U36332 F9x cables with FDDI connectors 32.
Part Numbers Loopback Test Equipment Loopback Test Equipment Description Used With Part Number Loopback connector Fiber-optic ServerNet, MSEB, SMF and MMF 427365 Loopback plug Serial-copper ServerNet, MSEB, IOMF2 421586 Loopback plug, 80-pin 6763 CCSA U40757 Loopback test connector ECL ServerNet, SEB, SWAN, IOMF2, MSEB U11674 ServerNet Adapters and Related Components Description Part Number 3710 Ethernet ServerNet adapter U09013 3860 ATM 3 ServerNet adapter (ATM3SA) U08502 3861 Ethern
Part Numbers CCSA and Related Components Part Number (page 2 of 2) Description 820.3 feet (250.0 meters) U33694 1640.5 feet (500.0 meters) U33695 Plug-in cards (PICs) for ServerNet/DA: 6761 fiber-optic PIC (F-PIC) U31967 6762 SCSI PIC (S-PIC) U23218 StorageTek (STK) cables, SCSI, 68-pin external: 1 meter (3.
Part Numbers 6780 Switch and Related Components Part Number (page 2 of 2) Description right fixed rail 425801 rail brackets 426784 Cable management tray 426089 Slide rail bracket, ServerNet II switch 425933 Slide rails, ServerNet II switch 426104 Cable management assembly arm 426016 Cable management assembly bracket 425940 Torx screws, M5 427219 Cage nuts, M5 U22978 Nuts, 8-32 x 0.375 T10011 Flat-head Phillips screws, 8-32 x 0.
Part Numbers 6780 Switch and Related Components Part Number (page 2 of 3) Description Area Power Distribution Unit (PDU), HV, 24 A, attached NEMA L6-30P power cord North America Asia 527135 Power Distribution Unit (PDU), HV, 32 A, attached IEC 309 power cord International 527296 Rack, HP 10642 527136 Rack-mount kit, includes 4 rails, 10 M6 Torx screws, 4 nylon ties 526272 Switch Components: Fan 523793 Logic board 523978 PIC, dual SMF 524984 PIC, Filler 524986 PIC, maintenance 523811
Part Numbers AWAN Servers and Related Components Area Part Number (page 3 of 3) C13 receptacle, 125 V, 10 A, 2.77 meter (9 foot) America, North T24242 L5-15P connector, C13 receptacle, 125 V, 15 A, 2.5 meter (8 foot) America, North 522835 L5-15P connector, C13 receptacle, 250 V, 15 A, 2.5 meter (8 foot) America, North 522836 18 AWG, C13 receptacle, 250 V, 10 A, 2.77 meter, (9 foot) America, North T21747 18 AWG, SPCL, C13 receptacle, 125 V, 10 A, 2.
Part Numbers AWAN Servers and Related Components Description Part Number (page 2 of 2) 3884 AWAN server 8-32p U33742 3884R AWAN server (obsolete) U33661 Modules for 3883/3884R AWAN servers: Current loop (only) 420280 Dual Mode RS-232/CL (obsolete) U38087 IDSN BRI port U33738 RS-232 asynchronous port U33745 V.
Part Numbers SWAN Concentrator and Related Components SWAN Concentrator and Related Components Description Part Number SWAN concentrator, model 3880 U14645 Adapter cables: RS-232 adapter cable DB-25 U11670 RS-449 adapter cable DB-37 U11671 V.35 adapter cable ISO 2593-1973 (34-pin) U11672 X.
Part Numbers Ethernet Switches and Hubs Ethernet Switches and Hubs Description Part Number ProCurve 2524 (J4813A), 24-port, Ethernet switch (product ID M8200-24) for IOAME LAN 528121 ProCurve 2524 (J4813A), 24-port, Ethernet switch (product ID 3870-24) not for IOAME LAN 526423 ProCurve 408 (J4097B), 8-port, Ethenet switch (replaces the following hubs) 528223 Cables, Ethernet: LAN patch cord, black, 3 feet U39929 UTP 10Base-T cable, 25 feet U23150 Ethernet hub: U.S.
Part Numbers Modems and Modem Cable Description Part Number (page 2 of 2) Austria 422043 Belgium U41697 Canada, Mexico, and U.S.
Part Numbers Universal Modem and Its AC Power Cords Universal Modem and Its AC Power Cords Description Part Number (page 1 of 2) Modem, universal 425961 AC power cord for modem: Argentina 425977 Australia 425963 Austria 425962 Belgium 425964 Brazil 425977 Canada 425977 China 425966 Denmark 425968 Finland 425969 France 425970 Germany 425967 Greece 425978 Hong Kong 425971 Iceland 425976 India 425972 Ireland 425971 Israel 425978 Italy 425973 Japan 425977 Korea 42597
Part Numbers Universal Modem and Its AC Power Cords Description Part Number (page 2 of 2) Spain 425978 Sweden 425976 Switzerland 425965 Taiwan 425977 Turkey 425978 U.K. 425971 U.S.
Part Numbers IOAM Products IOAM Products Note. The IOAM enclosure and all related components are field-replaceable units (FRUs.
Part Numbers IOAM Products Uninterruptible Power Supply (UPS) UPS Product Number Part number R5500XR, 6 KVA 3 U (North America, Japan) M8330-6 528116 R5500XR, 6 KVA 3 U (international) M8330-61 528117 ERM: (R5500WR) (world wide) M8330-ERM 528120 SNMP/Web card 526193 IOAM Cables Product Number Part number 2 meters (7 feet) M8900-02 522745 5 meters (16 feet) M8900-05 526016 15 meters (49 feet M8900-15 526017 40 meters (131 feet) M8900-40 525518 80 meters (262 feet) M8900-80 525
Part Numbers Cables and Cable Assemblies Cables and Cable Assemblies Description Part Number (page 1 of 4) 6763 CCSA splitter cables (4-to-1): 4-port V.35 cable: 26.2 feet (8.0 meters) U36657 4-port EIA-449 cable: 26.2 feet (8.0 meters) U36658 4-port RS-232 cable: 26.2 feet (8.0 meters) U36659 4-port X.21 cable: 26.2 feet (8.0 meters) U36660 Adapter cables for SWAN concentrator: RS-232 adapter cable DB-25 U11670 RS-449 adapter cable DB-37 U11671 V.
Part Numbers Cables and Cable Assemblies Description 23 meters (75.5 feet) Part Number (page 2 of 4) U31369 SCSI to fiber extender (CTSFE) 429902 ServerNet ECL cable adapter, SEB-to-MSEB (not used) 425847 ServerNet ECL cables, MSEB-to-MSEB: 1.0 meter (3.3 feet) 427026 1.6 meters (5.3 feet) 427027 2.0 meters (6.5 feet) 427028 2.5 meters (8.2 feet) 427029 3 meters (9.8 feet) 427030 4 meters (13.1 feet) 427031 5 meters (16.4 feet) 427032 6 meters (19.7 feet) 427033 7 meters (23.
Part Numbers Cables and Cable Assemblies Description Part Number (page 3 of 4) 2.5 meters (8.2 feet) U26027 3 meters (9.8 feet) U24316 4 meters (13.1 feet) U24317 5 meters (16.4 feet) U24319 6 meters (19.7 feet) U30033 7 meters (23.0 feet) U30034 8 meters (26.2 feet) U30035 9 meters (29.5 feet) U30036 10 meters (32.8 feet) U30037 25 meters (82.0 feet) U24320 ServerNet MMF cables: 3 meters, (9.8 feet) unsheathed 427275 5 meters, (16.4 feet) unsheathed 427276 10 meters, (32.
Part Numbers AC Power Cords, Enclosures Without Power Shelves Part Number (page 4 of 4) Description ServerNet SMF cables (MSEBs and ServerNet clusters): 10 meters (32.8 feet) 421752 40 meters (131.2 feet) 421755 80 meters (262.4 feet) 426101 80 meters (262.4 feet) plenum rated 427246 AC Power Cords, Enclosures Without Power Shelves All these power cords are 8.2 feet (2.
Part Numbers AC Power Cords, Enclosures With Power Shelves Country Plug Type Part Number (page 2 of 2) United Kingdom BS 1363 T29492 United States (only if specifically ordered for 200-240 V AC) NEMA 6-15P (NEMA 6-15R receptacle) T21747* *Cables U39146 and T21747 are 9.8 feet (3.0 meters) long. AC Power Cords, Enclosures With Power Shelves All these AC power cords are 2.5-meters (8.2-feet) long. Note.
Part Numbers AC Power Cords, Enclosures With Power Shelves Note. In system enclosures with power shelves, some AC power cords contain connectors that, when touched, vibrated, or flexed, can interrupt power intermittently to the enclosure. If a power shelf was shipped between mid-December 1998 and February 1999 and contains Mega power cords, part number 064583 (T64583), replace these cords with part number 421575-001.
Part Numbers AC Power Cords, Enclosures With Power Shelves HP NonStop S-Series Planning and Configuration Guide—523303-015 A-32
B Specifications This appendix describes system specifications.
Specifications Batteries Batteries The batteries in NonStop S-series processor enclosures and I/O enclosures are identical. A battery contains: • • Nonreplaceable fuses for short-circuit protection 24 sealed, cylindrical, lead-acid cells Battery Voltage and Amperage • • • Each cell is rated at 2.5 ampere-hours. The 24 cells in each battery are partitioned into two groups of 12 cells each (24 volts in each group).
Specifications Cables Cables ServerNet Cables for Same-Row Connections This subsection lists which ServerNet cables you need for connections between two enclosures that are in the same row in your system. For Information About ... Refer to ...
Specifications ServerNet Cables for Same-Row Connections SEB-to-SEB Connections in Same Row You need these ServerNet cables for each SEB-to-SEB connection within a row of enclosures. Arrangement of Enclosures Distance Between Connections Cable Length Required Part Number ECL SEB to MSEB ECL MSEB to MSEB Serial Copper Feet Meters Feet Meters ECL SEB to SEB 8.2 2.5 8.2 2.5 U26027 427047 427029 U26027 0 5.2 1.6 5.2 1.6 U26026 427045 427027 427224 1 7.5 2.3 8.2 2.
Specifications ServerNet Cables for Same-Row Connections SEB-to-IOMF CRU Connections in Same Row You need these ServerNet cables for each SEB-to-IOMF-CRU or MSEB-to-IOMF CRU connection within a row of enclosures. Arrangement of Enclosures Distance Between Connections Cable Length Required Part Number ECL SEB to MSEB ECL MSEB to MSEB Serial Copper Feet Meters Feet Meters ECL SEB to SEB 8.2 2.5 8.2 2.5 U26027 427047 427029 U26027 0 6.2 1.9 8.2 2.
Specifications Fiber-Optic Cables Fiber-Optic Cables The minimum bend radius for SMF and MMF fiber-optic cables is: • • Unsheathed: 1.7 inch (4.3 cm) Sheathed (ruggedized): 4.2 inch (10.7 cm) You can use fiber-optic cables available from HP or you can provide your own fiberoptic cables. If you provide your own fiber-optic cables, the attenuation specification is: • • • 3.5 db/km of length 0.5 db/connector insertion 10.
Specifications Enclosure Dimensions Enclosure Dimensions Dimensions of System Components Measurement Dimension Description Inches cm Height 1 base enclosure (includes casters) 37.6 95.5 1 base enclosure and 1 stackable enclosure (casters on base enclosure) 71.7 182.1 Stackable enclosure (no casters) 32.25 81.9 Caster 1.75 4.5 Bottom connector to top of enclosure 20 50.8 Bottom connector on base enclosure to top of stackable enclosure (in a doublehigh stack) 54 137.
Specifications Dimensions of Enclosures and Service Aisles Dimensions of Enclosures and Service Aisles Width of enclosure with 2 cable channels 23 inches (58 cm): Width of cable channel: 2 inches (5 cm) Depth of cable channel: 5 inches (12.7 cm) Depth of enclosure with cable channels: 30.75 inches (74 cm) Height of stackable enclosure without casters: 32.25 inches (82 cm) Service clearance: 48 inches (122 cm) Height of base enclosure with casters: 34 inches (95.5 cm) VST939.
Specifications Dimensions Within an Enclosure (Service Side) Dimensions Within an Enclosure (Service Side) Bottom connector to top of enclosure: 20 inches (51 cm) Far connector to side of enclosure: 13 inches (33 cm) Top connector to floor: in a single-high stack: 25 inches (63.5 cm) in a double-high stack: 59 inches (150 cm) VST948.
Specifications Enclosure Specifications Enclosure Specifications This subsection contains these specifications for system enclosures: Weights for System Enclosures on page B-10 AC Power Requirements for One System Enclosure on page B-11 Environmental Specifications for One System Enclosure on page B-11 Note the following about these specifications: • • • • • All weights are approximate.
Specifications AC Power Requirements for One System Enclosure AC Power Requirements for One System Enclosure Factor 100-120 Volts AC Operation 200-240 Volts AC Operation Nominal voltage 100-120 V AC 200-240 V AC Line frequency 50/60 Hz nominal 50/60 Hz nominal Voltage tolerance 85-132 V AC 170-264 V AC Frequency tolerance 47-63 Hz 47-63 Hz Branch circuits 2 for each enclosure 2 for each enclosure Amperage 20 A 10 A Branch circuit rating Without power shelf: 15 A 10 A With power she
Specifications Processor Types Processor Types The processor type is specified in the CONFTEXT configuration file before the system is shipped from the factory.
Specifications Internal Disk Drives Internal Disk Drives Each NonStop S-series system enclosure can contain up to 16 disk drives. These are the disk drive models that system enclosures can contain. Product Number Capacity 4604 4.2 gigabytes (7,200 rpm) 4608 8.8 gigabytes (7,200 rpm)* 4609 8.
Specifications IOAM Enclosure IOAM Enclosure This subsection contains these specifications: IOAM Enclosure Configuration Rules on page B-14 Environmental Specifications for an IOAM Enclosure on page B-14 Dimensions for an IOAM Enclosure on page B-15 Weights for an IOAM Enclosure and Selected Components on page B-15 IOAM Enclosure Configuration Rules IOAM enclosures can be attached only to group 01.
Specifications Dimensions for an IOAM Enclosure Dimensions for an IOAM Enclosure Component Measurement Inches WxHxD cm Bezel door 17.5 x 19 x 1.5 44.5 x 48.3 x 3.8 Chassis 19 x 19 x 26.75 48.3 x 48.3 x 68.0 Fan 6x6x4 15.2 x 15.2 x 10.2 Power supply 4 x 1.5 x 15 10.2 x 3.8 x 38 I/O midplane 17.3 x 7.2 x 0.12 44 x 18.1 x 0.3 Power midplane 15.5 x 0.087 x 4 39 x 0.22 x 10 ServerNet switch board 16.2 x 1.5 x 17.5 41.1 x 3.8 x 44.5 ServerNet adapter 1.5 x 8.5 x 15.4 3.8 x 21.6 x 39.
Specifications Modular Cabinet Modular Cabinet This subsection contains these specifications: Dimensions for a Modular Cabinet on page B-16 AC Power Requirements for a Modular Cabinet on page B-17 In these specifications, all weights are approximate and include cable management hardware and doors. Dimensions for a Modular Cabinet English inches Metric cm Width 23.5 60 Depth without doors 41 104 Depth with doors 43.25 110 height (42 u) 78.75 200 Weight, empty with PDUs 253 115 Width 35.
Specifications AC Power Requirements for a Modular Cabinet AC Power Requirements for a Modular Cabinet This subsections contains: PDU Power Configurations on page B-17 Modular Cabinet AC Power on page B-17 Modular Cabinet Modules AC Power on page B-18 PDU Power Configurations Geography Configuration USA, Japan 208 VAC, three phase delta, 60 A RMS, 4 wire EMEA 230/400 VAC, three phase wye, 63 A RMS, 5 wire EMEA 230/400 VAC, three phase wye, 63 A RMS, 5 wire, harmonized WW 200 to 250 VAC, single p
Specifications Modular Cabinet Modules AC Power R5500XR UPS (North America, Japan) R5500XR UPS (International) 208/230/240 VAC 208/230/240 VAC 208/230/240 VAC 50/60 Hz 50/60 Hz 50/60 Hz 50/60 Hz Voltage tolerance 200-264 VAC 200-264 VAC 200-264 VAC 200-264 VAC Frequency tolerance 47-63 Hz 47-63 Hz 47-63 Hz 47-63 Hz Amperage 2.5 A @ 200 VAC per side 1.2 A @ 200 VAC per side 22.5 A @ 200 VAC per side 22.
C Blank Forms This appendix contains blank system installation forms in alphabetic order by title. HP recommends that you make copies of these forms because you need several copies of each form when planning to install or add to a system. You are authorized to photocopy these forms only for the purpose of installing and configuring your system.
If you need forms other than those included in this appendix, consult the manuals that describe the subsystem or adapter for which you need the form.
System Name Date / / of Page Cross-Row Cabling Worksheet, SEB to IOMF CRU From group to group Standard Measurements 31inches (cabinet depth) 6 inches of slack (3 inches per cable end) + 37 Variable Measurements + Width of service aisle (48 inches minimum) If cable is installed under a raised floor Amount of slack for cable, based on depth of raised floor + If cable runs down from a single enclosure, or base enclosure in a double-high stack, add 25 inches + stacked enclosure in a double-high
System Name Date Cross-Row Cabling Worksheet, SEB to SEB From group / / of Page to group Standard Measurements + 31 inches (cabinet depth) 6 inches of slack (3 inches per cable end) 37 Variable Measurements + Width of service aisle (48 inches minimum) If cable is installed under a raised floor: Amount of slack for cable, based on depth of raised floor + If cable runs down from a single enclosure, or base enclosure in a double-high stack, add 25 inches stacked enclosure in a double-high stack,
Enclosure Arrangement Diagram Building __________________ Scale: 1/4 inch = 1 foot System Name Date Room__________________ / / System Number (In Expand Network) Number of Rows Note which enclosures are base enclosures and which are stacked enclosures. You can indicate a base enclosure by drawing casters on it. VST316.
System Name Final Planning Checklist Date / / Raised floor, if necessary, including cable cutouts Air conditioning Adequate lighting Fire and safety provisions Electrical outlets for system enclosures Electrical outlets for subsystems or peripheral devices Electrical utility outlets Direct communication line for the system console modem Communications lines for other modems Data communications lines and local area network wiring Work area available near the installation site for unpacking equipment Ins
Floor Plan Building __________________ Room System Name __________________ Date / / Scale: 1/4 inch = 1 foot VST315.
System Name Installation Document Checklist Form, Diagram, or Checklist System Equipment Inventory Form # Pages Date Page Form, Diagram, or Checklist / / of # Pages Other forms, notes, or checklists: Preinstalled I/O Device Cable Checklist Enclosure Arrangement Diagram Floor Plan System Enclosure Checklist PMF CRU Configuration Form and PMF 2 CRU Configuration Form IOMF CRU Configuration Form and IOMF 2 CRU Configuration Form Adapter Configuration Form ServerNet Communication Pathways Worksheet
System Name IOMF CRU Configuration Form Shaded areas indicate nonconfigurable components Group Date / 01 Slot Module / ServerNet Connection ServerNet Cable: ServerNet Connector: Module SCSI Port Group 01 Slot SCSI Port Product Number: SCF Name: SCSI Cable: POWER ON SERVERNET SCSI SERIAL CONSOLE Ethernet Port IP Address: ETHERNET MODEM AUX Adapter Name: SAC Name: AC Power POWER-ON CABLE SAC Access List: PIF Name: LIF Name: VST307.
System Name IOMF 2 CRU Configuration Form Shaded areas indicate nonconfigurable components Group Date / 01 Slot Module / ServerNet Connection ServerNet Cable: ServerNet Connector : Group Module SCSI Port 01 Slot SERVERNET SERVERNET SERVERNET PIC 3 PIC 2 PIC 1 SCSI Port Product Number: SCF Name: POWER ON SCSI Cable: SCSI Ethernet Port SERIAL CONSOLE AUX POWER-ON CABLE DC Power ETHERNET IP Address: Adapter Name: SAC Name: SAC Access List: PIF Name: LIF Name: VST 309 .
System Name PMF CRU Configuration Form Shaded areas indicate nonconfigurable components Group Module Date / 01 Slot / SCSI Port Product Number: SCF Name: POWER ON SCSI Cable: SCSI Ethernet Port SERIAL CONSOLE ETHERNET IP Address: MODEM Adapter Name: AC Power or DC Power AUX POWER-ON SAC Name: CABLE SAC Access List: PIF Name: LIF Name: VST 304 .
System Name PMF 2 CRU Configuration Form Shaded areas indicate nonconfigurable components Group Module Date / 01 Slot / SERVERNET SERVERNET SERVERNET PIC (unused) PIC (unused) PIC (unused) SCSI Port Product Number: SCF Name: POWER ON SCSI Cable: SCSI Ethernet Port SERIAL CONSOLE IP Address: AUX Adapter Name: DC Power ETHERNET SAC Name: POWER-ON CABLE SAC Access List: PIF Name: LIF Name: VST 308 .
System Name Preinstalled I/O Device Cable Checklist Cable ID Tag Date Page / / of Floor Plan VST314.
System Name Date Page / / of ServerNet Cabling: Tetra 8 Topology, I/O Enclosures From Group Slot To Group Slot 11 50 01 51 11 55 01 52 12 50 01 51 12 55 01 52 21 50 02 51 21 55 02 52 22 50 02 51 22 55 02 52 31 50 03 51 31 55 03 52 32 50 03 51 32 55 03 52 41 50 04 51 41 55 04 52 42 50 04 51 42 55 04 52 Length Needed Part Number VST382.
System Name Date Page / / of ServerNet Cabling: Tetra 8 Topology, Processor Enclosures From Group Slot To Group Slot 01 51 02 51 01 52 02 52 01 51 03 51 01 52 03 52 01 51 04 51 01 52 04 52 02 51 04 51 02 52 04 52 02 51 03 51 02 52 03 52 03 51 04 51 03 51 04 51 Length Needed Part Number VST381.
System Name Date Page / / of ServerNet Cabling: Tetra 16 Topology, I/O Enclosures 11-25 From Group Slot To Group Slot 11 50 01 53 11 55 01 54 12 50 01 53 12 55 01 54 13 50 01 53 13 55 01 54 14 50 01 53 14 55 01 54 15 50 01 53 15 55 01 54 21 50 02 53 21 55 02 54 22 50 02 53 22 55 02 54 23 50 02 53 23 55 02 54 24 50 02 53 24 55 02 54 25 50 02 53 25 55 02 54 Length Needed Part Number VST384.
System Name Date Page / / of ServerNet Cabling: Tetra 16 Topology, I/O Enclosures 31-45 From Group Slot To Group Slot 31 50 03 53 31 55 03 54 32 50 03 53 32 55 03 54 33 50 03 53 33 55 03 54 34 50 03 53 34 55 03 54 35 50 03 53 35 55 03 54 41 50 04 53 41 55 04 54 42 50 04 53 42 55 04 54 43 50 04 53 43 55 04 54 44 50 04 53 44 55 04 54 45 50 04 53 45 55 04 54 Length Needed Part Number VST389.
System Name Date Page / / of ServerNet Cabling: Tetra 16 Topology, I/O Enclosures 51-64 From Group Slot To Group Slot 51 50 05 53 51 55 05 54 52 50 05 53 52 55 05 54 53 50 05 53 53 55 05 54 54 50 05 53 54 55 05 54 61 50 06 53 61 55 06 54 62 50 06 53 62 55 06 54 63 50 06 53 63 55 06 54 64 50 06 53 64 55 06 54 Length Needed Part Number VST385.
System Name Date Page / / of ServerNet Cabling: Tetra 16 Topology, I/O Enclosures 71-84 From Group To Group Slot 71 50 07 53 71 55 07 54 72 50 07 53 72 55 07 54 73 50 07 53 73 55 07 54 74 50 07 53 74 55 07 54 81 50 08 53 81 55 08 54 82 50 08 53 82 55 08 54 83 50 08 53 83 55 08 54 84 50 08 53 84 55 08 53 Length Needed Part Number Slot VST390
System Name Date Page / / of ServerNet Cabling: Tetra 16 Topology, Processor Enclosures From Group Slot To Group Slot 01 51 02 51 01 52 02 52 01 51 03 51 01 52 03 52 01 51 04 51 01 52 04 52 01 51 05 51 01 52 05 52 02 51 04 51 02 52 04 52 02 51 03 51 02 52 03 52 02 51 06 51 02 52 06 52 03 51 04 51 03 52 04 52 03 51 07 51 03 52 07 52 04 51 08 51 04 52 08 52 Length Needed Part Number VST383.
ServerNet Communication Pathways: Tetra 8 Topology With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the CRU you plan to remove. If you are removing a PMF CRU, check this box. Then, on the other fabric, black out the PMF CRU in slot 55 or 50 in the corresponding enclosure to indicate that this PMF CRU will lose access to the other fabric as well.
ServerNet Communication Pathways: Tetra 16 Topology, X Fabric With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the CRU you plan to remove. If you are removing a PMF CRU, check this box. Then, on the worksheet for the Y fabric, black out the PMF CRU in slot 55 in the corresponding enclosure to indicate that this PMF CRU will lose access to the X fabric as well.
ServerNet Communication Pathways: Tetra 16 Topology, Y Fabric With a highlighter, shade the enclosures, ports, and slot numbers that are in use in your current configuration. With a pen, black out the CRU you plan to remove. If you are removing a PMF CRU, check this box. Then, on the worksheet for the Y fabric, black out the PMF CRU in slot 55 in the corresponding enclosure to indicate that this PMF CRU will lose access to the X fabric as well.
System Name Group Number 01 Module Number System Enclosure Checklist Date Shaded areas indicate nonconfigurable components / / Appearance Side: 01 02 03 04 05 06 07 08 11 12 13 14 15 16 17 18 Service Side: 50 55 51 52 53 54 VST303.
System Name System Equipment Inventory Form Part or Product Number Description Date Page Quantity Ordered / / of Quantity Received VST306.
Template, Furniture Scale 1/4 inch = 1 foot Equipment Desk (A) Desk (B) Shelves (A) Shelves (B) Cabinet File Chair Table Dimensions: Inches (cm) 66 (168) 54 (137) 45 (114) 33 (84) 33 (84) 33 (84) 24 (61) 45 (114) x x x x x x x x 33 (84) 30 (76) 18 (46) 18 (46) 24 (61) 18 (46) 18 (46) 21 (53) Desk (A) Desk (B) Chair Chair Chair Chair Chair Chair Chair Chair Shelves (B) Shelves (B) Shelves (B) Shelves (B) Shelves (B) Shelves (B) Shelves (B) Shelves (B) File File File File File File
. Template, System Components Scale: 1/4 inch = 1 foot Page 1 of 2 Equipment Dimensions Service Clearance System Enclosure 22 inches (56 cm) W 24 inches (61.0 cm) appearance side 30 inches (76.2 cm) service side 32 inches (81.5 cm) D 22 inches (56 cm) W 39 inches (99.1 cm) D Same ServerNet II Switch Enclosure 22 inches (56 cm) W 37.6 inches (95.5 cm) D 24 inches (61.0 cm) appearance side 30 inches (76.2 cm) service side 7159 Pedestal 23 inches (58.4 cm) W 35 inches (90 cm) D 36 inches (91.
Template, System Components Scale: 1/4 inch = 1 foot Page 2 of 2 Equipment Dimensions: Inches (cm) 5512 Desktop or with Stand 5515-1 Line Printer 5515-2 Line Printer 24.0 (61.0) x 16.0 (41.0) 23.4 (59.5) x 17.7 (45.0) 23.4 (59.5) x 32.7 (83.0) 5516 Line Printer 5524 Serial Matrix Printer 5575 Desktop Laser Printer 23.4 (59.5) x 32.7 (83.0) 24.5 (62.0) x 12.5 (30.5) 16.4 (41.6) x 15.9 (40.3) 5577 Desktop Laser Printer Terminal, generic 21.5 (55.0) x 23.5 (60.0) 18.0 (46.0) x 20.0 (51.
D Case Study: ServerNet Cable Lengths This case study documents the planning and installation of ServerNet cables in a NonStop S70000 system for a fictitious company. Note. Examples and sample cable routes are for illustration only and might not be suited for your particular purpose. HP does not warrant, guarantee, or make any representations regarding the use, or the results of the use, of any examples or cable routes in any documentation.
Case Study: ServerNet Cable Lengths Choosing Cable Lengths Choosing Cable Lengths The planner begins to choose the cable lengths for the system starting with processor enclosure group 01. Group 01 must be connected to I/O enclosure group 12. Because the processor enclosures and I/O enclosures are in different rows, the cables between them must cross the service aisle. The planner knows that the computer room at Developers Inc. is equipped with a raised floor.
Case Study: ServerNet Cable Lengths Choosing Cable Lengths 7. Repeats Step 2 through Step 6 for each ServerNet connection that goes across rows.
Case Study: ServerNet Cable Lengths Installation Document Installation Document The following example is a completed cross-row cabling worksheet for an SEB-toIOMF CRU connection.
E Guide to Server Manuals This appendix provides information about selected manuals and OSM or TSM documentation available for NonStop S-series servers. Manual Sets Manuals grouped by topic Page E-1 Titles and Abstracts Manuals with abstracts in alphabetic order Page E-10 Manual Sets Manual Set Explains how to ...
Guide to Server Manuals NonStop S-Series Server Manuals NonStop S-Series Server Manuals Category Purpose Title Reference Contain information about the manuals, the RVUs, and hardware that support NonStop S-series servers NonStop S-Series Server Description Manual Describe how to prepare for changes to software or hardware configurations Interactive Upgrade Guide 2 Change planning and control Introduction to Tandem NonStop S-Series Servers G06.
Guide to Server Manuals Adapter Manuals Adapter Manuals Purpose Title Provide references for installing, configuring, operating, managing, and supporting adapters 6760 ServerNet/DA Manual 6763 Common Communication ServerNet Adapter Installation and Support Guide ATM Adapter Installation and Support Guide ATM Configuration and Management Manual Ethernet Adapter Installation and Support Guide Fast Ethernet Adapter Installation and Support Guide Fibre Channel ServerNet Adapter Installation and Support Gui
Guide to Server Manuals Configuration and Management Manuals Configuration and Management Manuals The configuration and management manuals describe how to configure entire servers or individual hardware and software components such as peripheral devices and communications software. The stem manual contains the overall description of the server, and the configuration manuals contain specialized information for the individual components not located in the stem manual.
Guide to Server Manuals Generic Process Manuals Generic Process Manuals Manuals about configuring generic processes for G-series RVUs: Subsystem Manager or Monitor Process Name Manual ATM $ZZATM ATM Configuration and Management Manual Expand $ZEXP * Expand Configuration and Management Manual Kernel $ZZKRN SCF Reference Manual for the Kernel Subsystem OSS $ZPMON* Open System Services Installation Guide PAM $ZZPAM * PAM Configuration and Management Manual QIO $ZMnn QIO Configuration and
Guide to Server Manuals Network Manuals Network Manuals Purpose Title Provide references for installing, configuring, operating, managing, and supporting network processes Asynchronous Terminals and Printer Processes Configuration and Management Manual AWAN 3883/4/5 Access Server Configuration and Management Manual AWAN 3883/4/5 Server Installation and Support Guide AWAN 3886 Server Installation and Configuration Guide CP6100 Configuration and Management Manual EnvoyACP/XF Configuration and Management
Guide to Server Manuals SCF Manuals SCF Manuals Purpose Title Provide references about the SCF interface to these subsystems 45xx Modular Disk Subsystem Manual for G-Series Releases 5190/5194 Modular Tape Subsystem Manual AWAN 3886 Server Installation and Configuration Guide LAN Configuration and Management Manual SCF Reference Manual for G-Series RVUs SCF Reference Manual for the Kernel Subsystem SCF Reference Manual for the Storage Subsystem WAN Subsystem Configuration and Management Manual ServerNe
Guide to Server Manuals Tape Manuals Tape Manuals Purpose Title Provide references for installing, configuring, operating, managing, and supporting tape drives and tape libraries 5142 xSE Rackmount Tape Subsystem User Guide 5157/5157ACL S-Series Digital Linear Tape Subsystem Installation Users Guide 5158 ACL Digital Linear Tape Subsystem Installation/Users Guide 5190/5191 ACL Installation Guide 5190/5194 Modular Tape Subsystem Manual 5257/5257 ACL User’s Guide for NonStop S-Series Tape Enclosures 5258A
Guide to Server Manuals Purpose OSM, TSM, System Console Manuals and Online Help Title Virtual Tape Manager Installation and User’s Guide (Tributary Systems) Virtual TapeServer Operations and Administration Guide (Tape Labs) Virtual Tape Solution Installation Guide (Tributary Systems) OSM, TSM, System Console Manuals and Online Help Category Purpose Title Manuals Provide information in CDROM and hypertext format about using the OSM or TSM package to bring up and maintain NonStop S-series servers OS
Guide to Server Manuals Titles and Abstracts Titles and Abstracts Title Abstract (page 1 of 14) 45xx Modular Disk Subsystem Manual for G-Series Releases Describes the installation and operation of the 45xx modular disk subsystem when connected to a 6760 ServerNet device adapter in a NonStop S-series server. 5142 xSE Rackmount Tape Subsystem User Guide Describes the installation and operation of the 5142 xSE rackmount tape subsystem.
Guide to Server Manuals Titles and Abstracts Title Abstract (page 2 of 14) 9800 (CT9800FC) Fibre Channel Converter Installation and User’s Guide Describes how to install and operate the Fibre Channel converter. 9840FC (CT9800FC-3) Installation and User’s Guide for NonStop S-Series Tape Enclosure Describes how to install and configure the 9840 Fiber Channel tape drive in a NonStop S-series tape enclosure.
Guide to Server Manuals Titles and Abstracts Title Abstract (page 3 of 14) Availability Guide for Problem Management Defines problem management and explains how it relates to the operations management framework. It describes unplanned outages and how to predict, prevent, prepare for, and recover from them. It also lists and describes the HP tools available to help you manage your operations environment.
Guide to Server Manuals Titles and Abstracts Title Abstract (page 4 of 14) DSM/SCM Messages Manual Provides cause, effect, and recovery information for messages and errors that may be encountered while using the Distributed Systems Management/Software Configuration Manager (DSM/SCM).
Guide to Server Manuals Titles and Abstracts Title Abstract (page 5 of 14) G06.25 Software Installation and Upgrade Guide Provides detailed procedures for upgrading to the G06.25 RVU of the HP NonStop operating system on a single NonStop S-series server from any G03.00 or later G-series RVU. G06.25 Release Version Update Compendium Provides a summary for the products that have major changes in the G06.
Guide to Server Manuals Titles and Abstracts Title Abstract (page 6 of 14) Introduction to NonStop Operations Management Introduces operations managers to NonStop operations management.
Guide to Server Manuals Titles and Abstracts Title Abstract (page 7 of 14) LAN Configuration and Management Manual Describes how to configure, operate, and manage the ServerNet LAN Systems Access (SLSA) subsystem on a NonStop S-series server. Included are detailed descriptions of the Subsystem Control Facility (SCF) commands used with the SLSA subsystem and a quickreference section showing the command syntax.
Guide to Server Manuals Titles and Abstracts Title Abstract (page 8 of 14) NonStop S-Series Operations Guide Describes how to perform routine system hardware operations for NonStop S-series servers. These tasks include monitoring the system, performing recovery operations, operating disk and tape subsystems, performing routine hardware maintenance, and starting and stopping the system. This guide is written for system operators.
Guide to Server Manuals Titles and Abstracts Title Abstract (page 9 of 14) NonStop System Console Installer Guide Describes how to upgrade a system console (formerly known as TSM workstation) running the Microsoft Windows 2000 Professional or the Microsoft Windows XP Professional operating system to the latest versions of the system console applications delivered on the HP NonStop System Console CD.
Guide to Server Manuals Titles and Abstracts Title Abstract (page 10 of 14) PAM Configuration and Management Manual Describes the Port Access Method (PAM) subsystem, which allows applications running on NonStop S-series servers access to Ethernet and token-ring LANs. This manual is written for systems managers, operators, and others who configure and manage network subsystems on NonStop S-series servers.
Guide to Server Manuals Titles and Abstracts Title Abstract (page 11 of 14) ServerNet Cluster Manual Describes the installation, configuration, and management of ServerNet Cluster hardware and software. ServerNet Cluster 6770 Supplement Describes the use of G06.21, and later, software to manage ServerNet clusters that use the HP NonStop Cluster Switch (6770). The 6770 switch is only used for the star topologies.
Guide to Server Manuals Titles and Abstracts Title Abstract (page 12 of 14) SWAN 2 Concentrator Installation and Support Guide Describes how to install and maintain the next-generation ServerNet wide area network (SWAN 2) concentrator on a NonStop S-series server. It is written for anyone who installs or maintains the SWAN 2 concentrator and its CRUs.
Guide to Server Manuals Titles and Abstracts Title Abstract (page 13 of 14) TSM Event Viewer online help Describes how to use the TSM Event Management Service (EMS) Event Viewer Application, which is software that allows you to view EMS log files using multiple display modes. These various display modes help permit rapid assessment of system problems. This help system is provided for operations and support personnel who are responsible for managing system operations.
Guide to Server Manuals Titles and Abstracts Title Abstract (page 14 of 14) Virtual Tape Manager Installation and User’s Guide (Tributary Systems) Provides a conceptual overview of the Tributary Systems, INC. (TSI) Virtual Tape Solution (VTS), its components, and the operations of the VTS GUI system interface. This guide is intended for use after installation and does not describe installation procedures or how to set up the initial system parameters.
Guide to Server Manuals HP NonStop S-Series Planning and Configuration Guide—523303-015 E -24 Titles and Abstracts
F Supported Hardware and Configurations This appendix list the devices and peripherals currently supported by NonStop S-series servers for this RVU. This information is subject to change. For updated information about the supported hardware for every G-series RVU, refer to the Interactive Upgrade Guide 2. For detailed information about each of these products, refer to the individual manuals for the products.
Supported Hardware and Configurations $SYSTEM Disk Slots $SYSTEM Disk Slots The mirrored $SYSTEM volume is configured in slots 11 and 12 of group 01. Beginning on the G06.06 RVU (and beginning on the G06.04 RVU using SPR T6586AAH), you can place two halves of the $SYSTEM volume in any two slots of the group 01 processor enclosure as long as the two slots have the same SCSI ID. These slot pairs are the following.
Supported Hardware and Configurations ServerNet Adapters and Communication Devices ServerNet Adapters and Communication Devices 3860 ATM 3 ServerNet adapter (ATM3SA)** 3861 Ethernet 4 ServerNet adapter (E4SA)** 3862 Token-Ring ServerNet adapter (TRSA)** 3863 Fast Ethernet ServerNet adapter (FESA)** 3865 Gigabit Ethernet ServerNet adapter (GESA-C) (copper)** 3865 Gigabit Ethernet ServerNet adapter (GESA-F) (fiber)** 3880 ServerNet wide area network (SWAN) concentrator 3881 ServerNet wide area network 2 (SW
Supported Hardware and Configurations Plug-In Cards (PICs) Plug-In Cards (PICs) PICs and Components Used In 6761 fiber-optic PIC (F-PIC) ServerNet/DA 6762 SCSI PIC (S-PIC) ServerNet/DA Emitter-coupled logic (ECL) PIC MSEB, IOMF 2 CRU Multimode fiber-optic (MMF) PIC MSEB, IOMF 2 CRU Node-numbering agent (NNA) PIC MSEB, ServerNet cluster Serial-copper (SCu) PICS MSEB, IOMF 2 CRU Single-mode fiber-optic (SMF) PIC MSEB, IOMF 2 CRU SS7TE PIC CCSA SS7TE2 PIC CCSA SS7TE3 PIC CCSA Filler pan
Supported Hardware and Configurations External Disk Drives External Disk Drives Product Number Capacity 4560 2 gigabytes 4570 4 gigabytes 4580 8 gigabytes 4590 18 gigabytes Tape Libraries Tape Library Supported Tape Drives 4400 9490 9310 9490, 9840 and CT9841F-4 9710 5155, 5159, and 9840 L700 9840 and CT9841F-1 Tape Drives 5142 digital audio tape (DAT) drive 515x digital linear tape (DLT) drive 517x open-reel tape subsystem 5190 cartridge tape drive 5190 ACL cartridge tape drive 5194 c
Supported Hardware and Configurations Printers Tape Drives (Cont’d) VT5801 Virtual Tape Solution: Tributary Systems Inc. 2U VT5901 Virtual Tape Solution: Tape Labs Inc. 2U VT5902 Virtual Tape Solution: Tape Labs Inc. 7U VT5900-A Virtual Tape Solution: Tape Labs Inc. 7U. (Replaces VT5902) VT5900-B Virtual Tape Solution: Tape Labs Inc. 2U (3.5-inch chassis) VT5900-C Virtual Tape Solution: Tape Labs Inc. 2U (3.
Supported Hardware and Configurations Maximum Number of Enclosures for Each RVU Maximum Number of Enclosures for Each RVU These are the maximum numbers of processor and I/O enclosures supported for each Nonstop S-series server and RVU: Tetra 8 Enclosures RVU Server Processor I/O G02.00 S7000 2 S70000 G03.00 to IOAM Tetra 16 Enclosures Processor I/O IOAM 0 2 0 4 4 4 4 S7000 4 8 8 16 S70000 4 8 8 24 S7000 4 8 8 16 S70000 4 8 8 36 G06.
Supported Hardware and Configurations Maximum Number of Enclosures for Each RVU HP NonStop S-Series Planning and Configuration Guide—523303-015 F-8
G Modular Power Information This appendix provides information about topics: Modular Cabinet Input Power IOAM Enclosure Power Requirements UPS Power Requirements Power Distribution Unit Wiring Caution. The information in this section is for your guidance in planning the total power and cooling requirements for your site. For complete information, consult the appropriate site preparation or hardware manuals from HP or the original equipment manufacturer site.
Modular Power Information • IOAM Enclosure Power Requirements International - 200 to 250 V AC Cabinet Input Power ° ° ° Single phase, three-wire with insulated ground conductor, 63A RMS AC power cord (two supplied with cabinet): length: 7 ft.
Modular Power Information UPS Power Requirements UPS Power Requirements Specifications in the following tables assume the UPS is integrated in the modular cabinet. UPS Power Specifications Modular Unit UPS, R5500 XR, 0-1 cycle (operates at 95% efficiency) Plugs per Modular Unit Total Power Consumption (Watts) 2 230 Maximum Total AC Current (Amps) per PDU @ 208 V AC Maximum Total AC Current (Amps) per PDU @ 230 V AC 1.1 (estimated maximum) 1.
Modular Power Information Power Distribution Unit Wiring The following wiring diagrams are provided for the installer to balance the load between the phases. It is possible to inadvertently plug modules into a single phase rather than distribute the load across all three phases. PDU, Unstrapped This view shows the inner wiring of a PDU without strapping. PDU, Three Phase, Delta, (North American) The delta configuration is typical of North American usage.
Modular Power Information PDU, Unstrapped PDU, Unstrapped N L 1 G N L 2 G N L 3 G N L 4 G N L 5 G N L 6 G N L 7 G N L 8 G N L 9 G N L 10 G N L 11 G N L 12 G N L 13 G N L 14 PDU Chassis G Neutral GROUND PDU Unstrapped HP NonStop S-Series Planning and Configuration Guide— 523303-015 G- 5
Modular Power Information PDU, Three Phase, Delta, (North American) PDU, Three Phase, Delta, (North American) Input, three phase, 120 VAC, outlet single phase 208 VAC, with ground, no neutral. This configuration provides 208 VAC by using a delta connection.
Modular Power Information PDU, Three Phase, Wye PDU, Three Phase, Wye Input, three phase, 250VAC, outlet single phase 250 VAC, with ground and neutral. This configuration provides 250 VAC by using a wye connection.
Modular Power Information PDU, Single Phase PDU, Single Phase Input, single phase, 250VAC, outlet single phase 250 VAC, with ground and neutral.
Safety and Compliance Regulatory Compliance Statements The following warning and 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. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
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 DECLARATION OF CONFORMITY Supplier Name: HP COMPUTER CORPORATION Supplier Address: HP Computer Corporation, NonStop Enterprise Division 10333 Vallco Parkway Cupertino, CA 95014 USA Represented in the EU By: Hewlett Packard EMEA GmbH P.O.
Safety and Compliance Regulatory Compliance Statements DECLARATION OF CONFORMITY Supplier Name: HP COMPUTER CORPORATION Supplier Address: HP Computer Corporation, NonStop Enterprise Division 10333 Vallco Parkway Cupertino, CA 95014 USA Represented in the EU By: Hewlett Packard EMEA GmbH P.O.
Safety and Compliance Important Safety Information For PDU (Power Distribution Unit) Important Safety Information For PDU (Power Distribution Unit) Retain and follow all product safety and operating instructions. Observe all warnings on the product and in the operating instructions. To reduce the risk of bodily injury, electric shock, fire, and damage to the equipment, observe all precautions included in this guide.
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 SAFETY CAUTION 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 power distribution unit. Observe the following limits when connecting the product to AC power distribution devices: For PDU that have attached AC power cords or are directly wired to the building power, the total combined leakage current should not exceed 5 percent of the rated input current for the device.
Safety and Compliance Consumer Safety Statements Consumer Safety Statements Customer Installation and Servicing of Equipment The following statements pertain to safety issues regarding customer installation and servicing of equipment described in this manual. • • • Keep door closed for normal operation. The equipment must be installed near the receptacles for the power cords, and the receptacles must be easily accessible to the user. Batteries must be disposed of in compliance with local ordinances.
Safety and Compliance Declaraciones sobre la seguridad del consumidor Declaraciones sobre la seguridad del consumidor Instalación y servicio al equipo por el consumidor Las siguientes declaraciones tienen que ver con aspectos de seguridad relacionados con la instalación y servicio al equipo por el consumidor, y que se describen en este manual. • • • Mantenga la puerta cerrada durante la operación normal del equipo.
Safety and Compliance Käyttöturvaa koskevia huomautuksia Käyttöturvaa koskevia huomautuksia Asiakkaan suorittama laiteasennus ja huolto Seuraavat huomautukset koskevat turvallisuusnäkökohtia, jotka asiakkaan täytyy ottaa huomioon tässä käsikirjassa kuvattuja laiteasennuksia ja huoltotoimenpiteitä suoritettaessa. • • • Kansi täytyy pitää suljettuna normaalin käytön aikana. Laitteisto täytyy asentaa lähelle virtapistokkeita, ja pistokkeiden tulee olla helposti käytettävissä.
Safety and Compliance Meddelanden beträffande konsumentsäkerhet Meddelanden beträffande konsumentsäkerhet Kundutförd installation och service De följande meddelandena beskriver säkerhetsföreskrifter för kundutförd installation och service av utrustning som beskrivs i denna manual: • • • Dörren skall vara stängd under normal drift. Batterier måste kasseras i enlighet med lokala förordningar. Utrustningen bör monters nära eluttag för nätsladdar. Nätsladdarna måste vara lättillgängliga.
Safety and Compliance Meddelanden beträffande konsumentsäkerhet HP NonStop S-Series Planning and Configuration Guide—523303-015 Statements-12
Glossary 3-phase. Describes a single power source with three output phases (A, B, and C). The phase difference between any two of the three phases or currents is 120 degrees. 3860 ATM 3 ServerNet adapter (ATM3SA). See ATM 3 ServerNet adapter (ATM3SA). 3861 Ethernet 4 ServerNet adapter (E4SA). See Ethernet 4 ServerNet adapter (E4SA). 3862 Token-Ring ServerNet adapter (TRSA). See Token-Ring ServerNet adapter (TRSA). 3863 Fast Ethernet ServerNet adapter (FESA). See Fast Ethernet ServerNet adapter (FESA).
Glossary absolute pathname absolute pathname. An Open System Services (OSS) pathname that begins with a slash (/) character and is resolved beginning with the root directory. Contrast with relative pathname. AC. See alternating current (AC). accelerated mode. The operational environment in which Accelerator-generated RISC instructions execute. See also TNS mode and TNS/R native mode. accelerated object code. The RISC instructions that result from processing a TNS object file with the Accelerator program.
Glossary ADAPTER object type types of cable that can connect any of the six 50-pin WAN ports to one of the supported electrical interfaces (RS-232, RS-449, X.21, or V.35). ADAPTER object type. The Subsystem Control Facility (SCF) object type for all adapters attached to your system. address space. The memory locations to which a process has access. ADE. See application development environment (ADE). adjacent SP.
Glossary application binary interface (ABI) The appearance side is opposite the service side. System enclosures are typically arranged so that the appearance side is the most visible side. See also service side. application binary interface (ABI). The conventions used to call functions and access global or external data. application development environment (ADE). A set of methods and tools that are used throughout the lifecycle of an application project to design, code, and manage that project.
Glossary ASSIGN ASSIGN. An HP Tandem Advanced Command Language (TACL) command you can use to associate a file name with a logical file of a program or to assign a physical device to logical entities that an application uses. assign message. Within Subsystem Control Facility (SCF), a message created by SCF for each ASSIGN command. A new process must request its assign message following receipt of the startup message.
Glossary authentication attributes authentication attributes. Security attributes of a process that do not change unless a successful reauthentication occurs or the super ID changes them. For Open System Services (OSS) processes, the authentication attributes include the login name, real user ID, real group ID, authentication system (node name), and group list. authorization attributes.
Glossary backout backout. The Distributed Systems Management/Software Configuration Manager (DSM/SCM) action of making the last configuration applied to the target system inaccessible and replacing it with the previous configuration. backplane. A board that has connectors, on one or both sides of the board, into which circuit board assemblies plug. Backplanes are located behind card cages. BACKUP. A utility for the HP NonStop™ servers that creates a backup copy of one or more disk files on magnetic tape.
Glossary block block. A grouping of one or more system enclosures that an HP NonStop™ S-series system recognizes and supports as one unit. A block can consist of either one processor enclosure, one I/O enclosure, or one processor enclosure with one or more I/O enclosures attached. blocked signal. A programmatic signal that is currently in the pending signal mask of a process and, when generated, is not delivered to the process because of the signal mask setting. Some signals cannot be blocked.
Glossary branch circuit branch circuit. The circuit conductors located between the equipment receptacles and the final overcurrent device in a power distribution panel (PDP) that protect the circuits. branded product. A software product that is licensed by X/Open to carry the X/Open or UNIX trademark. branding process. The activities that lead to the acceptance of a product by X/Open in accordance with its Trade Mark Licence Agreement. break condition.
Glossary cache (cache memory) support. The cable support also contains the group and module ID labels and the rear group service light-emitting diode (LED). cache (cache memory). A small, fast memory holding recently accessed data designed to speed up subsequent access to the same data. Cache memory is built from faster memory chips than main memory, and it is most often used with process or main memory but also used in network data transfer to maintain a local copy of data. cached bindings.
Glossary CE CE. Customer engineer. See service provider. cell. See storage pool. central processing unit (CPU). Historically, the main data processing unit of a computer. The HP NonStop™ servers have multiple cooperating processors rather than a single CPU. See also processor. Challenge Handshake Authentication Protocol (CHAP). An Internet-standard protocol for verifying encrypted passwords. CHAP is a security protocol that is implemented using Point-to-Point Protocol (PPP).
Glossary CIIN CIIN. A command file in the SYSnn subvolume that is read and executed by the startup HP Tandem Advanced Command Language (TACL) process after system load if the CIIN file is specified in the CONFTEXT file and enabled in the OSM or TSM Low-Level Link. circuit breaker. A device designed to open and close a circuit by nonautomatic means and to open the circuit automatically on a predetermined overcurrent without damage to itself. CISC. See complex instruction-set computing (CISC).
Glossary CLIP CLIP. See communications line interface processor (CLIP). cluster. (1) A collection of servers, or nodes, that can function either independently or collectively as a processing unit. See also ServerNet cluster. (2) A term used to describe a system in a Fiber Optic Extension (FOX) ring. More specifically, a FOX cluster is a collection of processors and I/O devices functioning as a logical group. In FOX nomenclature, the term is synonymous with system or node. cluster number.
Glossary CMI CMI. See Communications Management Interface (CMI). code segment. A segment that contains executable instructions of a program or library to be executed plus related information. Code segments can be executed and also accessed as read-only data but not written to by an application program. These readonly and execute-only segments are efficiently shared among simultaneous executions of that program or library. Therefore, they are read from disk but are never written back to disk.
Glossary communications line communications line. A two-way link consisting of processing equipment, I/O devices, protocol conventions, and cables that connect a computer to other computers. communications line interface processor (CLIP). The major programmable device within the ServerNet wide area network (SWAN) concentrator, providing link-level protocol and a software interface to the host. The CLIP stores and implements specific communications protocols. Communications Management Interface (CMI).
Glossary Compaq TSM Service Application Compaq TSM Service Application. A component of the Compaq TSM client software. The TSM Service Application enables you to communicate with an HP NonStop™ S-series server when the HP NonStop operating system is running. When the operating system is not running, communication must take place using the TSM Low-Level Link. See also Compaq TSM Low-Level Link. compiler extended-data segment.
Glossary CONFIG file CONFIG file. In G-series release version updates (RVUs), the current system configuration database file, which is stored on the $SYSTEM. ZSYSCONF subvolume. See also configuration file. configuration. (1) The arrangement of enclosures, system components, and peripheral devices into a working unit. (2) The definition or alteration of characteristics of an object. configuration file.
Glossary conformance document conformance document. An implementor’s document that must accompany software claiming conformance with a POSIX standard. The document specifies the behavior or other aspect of the software when the standard describes a behavior or aspect as implementation-defined. conformance statement questionnaire (CSQ). A document that identifies how a product implements X/Open Specifications as defined in XPG Component/Profile Definitions. A CSQ exists for each branded product.
Glossary connectivity representation of the connectivity among components within an enclosure. See also Physical view. connectivity. The ability of a system to transfer information between itself and a system from another vendor. Other vendors use the term connectivity to mean hardware compatibility. See also interoperability. connector. See port. console message. See operator message. contiguous ground.
Glossary core file core file. See saveabend file. correctable memory error (CME). An error caused by incorrect data at a particular memory location. The cause of the error is such that the error is automatically corrected by the system. Contrast with uncorrectable memory error (UCME). COUP. See Configuration Utility Program (COUP). CPU. See central processing unit (CPU). cpu, pin.
Glossary customer-installable system customer-installable system. A system that does not require specially trained service providers to install. customer-replaceable unit (CRU). A unit that can be replaced in the field either by customers or by qualified personnel trained by HP.
Glossary dBm dBm. Decibels as referenced to a milliwatt. A unit of measure that establishes 0 dBm equal to 1 milliwatt. A negative value represents a decrease in power, and a positive value represents an increase in power. See also decibel (dB). DC. See direct current (DC). DCE. See data communications equipment (DCE). DCF. See dynamic configuration file (DCF). DCT. See destination control table (DCT). DC power cable.
Glossary destination ServerNet ID (DID) destination ServerNet ID (DID). A field in the ServerNet packet header indicating the intended destination for the packet. detailed report. A complete listing of status or configuration information provided by the Subsystem Control Facility (SCF) STATUS or INFO command when you use the DETAIL option. Contrast with summary report. device. A computer peripheral or an object that appears to an application as such. See also terminal. DHCP.
Glossary directory tree directory tree. A hierarchy of directories. In the Open System Services (OSS) environment, directories are connected to each other in a branching hierarchical fashion such that only one path exists between any two directories (if no backtracking occurs). disconnecting means. A device, group of devices, or other means by which the conductors of a circuit can be disconnected from their source of supply. discovery.
Glossary DLC DLC. See data link control (DLC). DNS. See Domain Name System (DNS). DNS server. A server that resolves hostnames to Internet protocol (IP) address mapping queries. These queries originate from either client computers, which are known as resolvers, or other Domain Name System (DNS) servers, which accounts for the distributed nature of DNS. See also Network Information Service (NIS). domain. (1) In the Internet, a part of the naming hierarchy.
Glossary downward compatibility downward compatibility. The ability of a requester to operate with a server of an earlier revision level. In this case, the requester is downward-compatible with the server, and the server is upward-compatible with the requester. Contrast with upward compatibility. drive. See disk drive or tape drive. dropout. A voltage loss of very short duration (that is, milliseconds). DSC. See Dynamic System Configuration (DSC). DSM. See Distributed Systems Management (DSM). DSM/SCM.
Glossary dynamic-link library (DLL) gathered from a server through the process of discovery. Contrast with static information. dynamic-link library (DLL). A collection of procedures whose code and data can be loaded and executed at any virtual memory address, with run-time resolution of links to and from the main program and other independent libraries. The same DLL can be used by more than one process. Each process gets its own copy of DLL static data. Contrast with shared run-time library (SRL).
Glossary effective group ID effective group ID. An attribute of an Open System Services (OSS) process that is used to determine permissions such as the file access allowed for the process. The effective group ID of a process is a group ID that contributes to the group access privileges of that process. The effective group ID of a process might be used to set the group ID of files created by that process. The effective group ID can be changed while the process runs. effective user ID.
Glossary EMI removes power from all computer equipment in the room. The EPO connectors prevent the batteries from powering the server after power is removed. EPO capabilities are required in the United States when a server is installed in a computer room designed to comply with the special construction and fire protection provisions of the United States’ national electrical code (or at other sites as required by local regulations.) EMI. See electromagnetic interference (EMI). emitter-coupled logic (ECL).
Glossary endian endian. Denotes the significance of byte 0 in a multibyte structure such as a word. NonStop servers are big-endian, where the most significant bit is contained in byte 0. Intel systems and HP AlphaServer OpenVMS and HP AlphaServer Tru64 UNIX systems are little-endian, where the least significant bit is contained in byte 0. environmental parameters. Subsystem Control Facility (SCF) session parameters set by default or by using various SCF commands.
Glossary Ethernet Ethernet. A local area network (LAN) that uses the carrier sense multiple access with collision detection (CSMA/CD) access method on a bus topology and is the basis for the IEEE 802.3 standard. Ethernet 4 ServerNet adapter (E4SA). A ServerNet adapter for Ethernet local area networks (LANs) that contains four Ethernet ports. Ethernet hub. A multiport repeater typically supporting 10Base-T cabling. Most hubs are connectors for 8 or 12 cables. Also referred to as a concentrator.
Glossary Expand-over-ServerNet line-handler process device number as its Expand-over-ServerNet line-handler process. However, the line does not have the same states as the line-handler process. Expand-over-ServerNet line-handler process. An Expand line-handler process that uses the NETNAM protocol to access the Network Access Method (NAM) interface provided by the ServerNet cluster monitor process, $ZZSCL. The Expand-over-ServerNet linehandler process handles incoming and outgoing Expand messages.
Glossary external routing external routing. The routing of packets over the external ServerNet fabrics; that is, between systems (or nodes) in a ServerNet cluster. See also internal routing. external ServerNet fabrics. The fabrics that link systems in a ServerNet cluster. See also internal ServerNet fabrics. external ServerNet X or Y fabric. The X or Y fabric that links systems in a ServerNet cluster. See also internal ServerNet X or Y fabric. external system area network manager process (SANMAN).
Glossary FCSA FCSA. See Fibre Channel ServerNet adapter (FCSA). FC switch. See Fibre Channel switch (FC switch). FDC. See flexible disk configuration (FDC). feature-test macro. In C and C++ programs, a symbol that, if defined in a program’s source code, includes specific other symbols from a header within that program’s source code and makes those symbols visible. feeder circuit.
Glossary field field. In a structured programming language, an addressable entry within a data structure. The term field is sometimes used to mean member. field-programmable gate array (FPGA). A programmable integrated circuit that can be customized to perform specific functions. field-replaceable unit (FRU). A unit that can be replaced in the field only by qualified personnel trained by HP and cannot be replaced by customers.
Glossary file mode file mode. For an Open System Services (OSS) process, a field in the stat structure for a specific file that describes the type and characteristics of the file and contains the access permission bits for the file. file mode creation mask. A mask associated with an Open System Services (OSS) process and used when the process creates a file. Bits set in this mask are cleared in the access permission bits for the file. filename.
Glossary file system file system. In the Open System Services (OSS) environment, a collection of files and file attributes. A file system provides the namespace for the file serial numbers that uniquely identify its files. Open System Services provides a file system (see also ISO/IEC IS 9945-1:1990 [ANSI/IEEE Std. 1003.1-1990], Clause 2.2.2.38); the Guardian application program interface (API) provides a file system; and OSS Network File System (NFS) provides a file system.
Glossary FIRINIT FIRINIT. A diagnostic task used to update the communications line interface processor (CLIP) FRU information record (FIR) that is kept in the ServerNet wide area network (SWAN) concentrator CLIP flash memory. FIRMUP. A diagnostic task used to update the copy of the Portable Silicon Operating System (pSOS) system product embedded kernel that is kept in the ServerNet wide area network (SWAN) concentrator communications line interface processor (CLIP) flash memory. firmware.
Glossary four-lane link four-lane link. The four single-mode fiber-optic (SMF) ServerNet cables that connect the two HP NonStop™ Cluster Switches on the same external fabric (for example, X1 and X2) in a split-star topology. FOX. See Fiber Optic Extension (FOX). FOXMON. See FOX monitor process. FOX monitor process. The Fiber Optic Extension (FOX) monitor process for the ServerNet/FX adapter subsystem. The process name is $ZZFOX. FOX ring.
Glossary GB GB. See gigabyte (GB). GCSC. See Global Customer Support Center (GCSC). general-purpose register (GPR). One of a small number of undedicated high-speed memory locations in a processor. generic process. A process created and managed by the Kernel subsystem; also known as a system-managed process. A common characteristic of a generic process is persistence. GESA. See Gigabit Ethernet ServerNet adapter (GESA). G4SA. See Gigabit Ethernet 4-Port ServerNet adapter (G4SA).
Glossary globalized globalized. The import-control characteristic of a loadfile that allows it to import symbols from any loadfile in the loadList of the program with which it is loaded. When those loadfiles offer multiple definitions of the same symbol, those loadfiles are searched in loadList sequence and the first definition found takes precedence. See also searchList. globally unique ID (GUID).
Glossary group ID group ID. The nonnegative integer used to identify a group of users of an HP NonStop™ network node. Each user of a node is a member of at least one group. When the identity of a group is associated with an Open System Services (OSS) process, a group ID value is referred to as one of: • • • • Real group ID Effective group ID Supplementary group ID Saved-set group ID group list.
Glossary hard link server version T7945AAX (shipped with G06.13) or later, use the appropriate guided procedure. hard link. In the Open System Services (OSS) file system, the relationship between two directory entries for the same file. A hard link acts as an additional pointer to a file. A hard link cannot be used to point to a file in another fileset. Contrast with symbolic link. hard reset.
Glossary HP NonStop™ Cluster Switch (model 6770) HP NonStop™ Cluster Switch (model 6770). An assembly that routes ServerNet messages across an external fabric of a ServerNet cluster. The cluster switch consists of a ServerNet II Switch, an uninterruptible power supply (UPS), and AC transfer switch, and it can be packaged in a switch enclosure or in a 19-inch rack. The cluster switch is used with star, split-star, and tri-star topologies. See also HP NonStop™ ServerNet Switch (model 6780).
Glossary HP NonStop™ S7800 server HP NonStop™ S7800 server. A mid-range HP NonStop S-series server that is based on the NonStop S76000 technology and supports all NonStop S-series hardware products that are compatible with the NonStop S76000 servers. HP NonStop™ S70000 server. The first high-performance server in a product line of HP NonStop S-series servers that implements the ServerNet architecture and runs the HP NonStop operating system. HP NonStop™ S72000 server.
Glossary HP NonStop™ System RISC Model D processor (NSR-D processor) HP NonStop™ System RISC Model D processor (NSR-D processor). The model designation for the TNS/R processor used in the HP NonStop S7400 server. HP NonStop™ System RISC Model E processor (NSR-E processor). The model designation for the TNS/R processor used in the HP NonStop S7600 server. HP NonStop™ System RISC Model G processor (NSR-G processor). The model designation for the TNS/R processor used in the HP NonStop S70000 server.
Glossary HP NonStop™ TCP/IPv6 HP NonStop™ TCP/IPv6. An HP product that adds IP version 6 (IPv6) functionality to the parallel library TCP/IP product. IPv6 is a TCP/IP protocol that extends the IP version 4 (IPv4) of 32 bits to 128 bits. NonStop TCP/IPv6 can be run in three modes: INET (only IPv4 and is a direct replacement for parallel library TCP/IP), INET 6 (only IPv6), and Dual (both IPv4 and IPv6 communications). HP NonStop™ Technical Library (NTL).
Glossary ideogram ideogram. See ideograph. ideograph. A character or symbol representing a word or idea. Some writing systems, such as Japanese and Chinese, use thousands of ideographs. An ideograph is sometimes called an ideogram. IEC. International Electrotechnical Committee. IEC is a professional organization that creates or adopts standards for computer hardware, environments, and physical interconnections. IEEE. Institute of Electrical and Electronics Engineers.
Glossary import library import library. A file that represents a dynamic-link library (DLL) and can substitute for it as input to the linker. Import libraries facilitate linking on auxiliary platforms (that is, PCs) where it is inconvenient to store the actual DLLs. in-band control (IBC). A symbol-based communications protocol for communicating management information across a ServerNet link without interfering with any application traffic in the network.
Glossary inode number inode number. A unique identifier within the Open System Services (OSS) file system of an instance of an OSS file. The inode number identifies the instance within the file system catalogs. input/output process (IOP). A running program (part of the HP NonStop™ Kernel operating system) that manages the I/O functions for one or more ServerNet addressable controllers (SACs) of the same type. input source. The resource from which Subsystem Control Facility (SCF) accepts command input.
Glossary internal ServerNet fabrics internal ServerNet fabrics. The fabrics that link ServerNet devices within an HP NonStop™ S-series server. See also external ServerNet fabrics. internal ServerNet X or Y fabric. The X or Y fabric that links ServerNet devices within an HP NonStop™ S-series server. See also fabric. internationalization.
Glossary instance data instance data. For each process using a dynamic-link library, a data segment area containing the global variables used by the library. I/O adapter module (IOAM). A collection of modular components that provides I/O connectivity and can include ServerNet switch boards, Fibre Channel ServerNet adapters (FCSAs), fans, and power supplies. In the IOAM, each module is a logical entity that represents a single service domain. I/O adapter module enclosure (IOAM enclosure).
Glossary IOP three SCSI ServerNet addressable controllers (S-SACs) in a single unit. IOMF 2 CRUs are supported on G06.10 and later release version updates (RVUs). IOP. See input/output process (IOP). IP. See Internet protocol (IP). IP address. An address that uniquely identifies a specific host system within a network to the Internet protocol (IP). An IP address consists of two parts: a network address, which identifies the network, and a local address, which identifies the host within the network.
Glossary ISO/IEC-conforming POSIX.1 application ISO/IEC-conforming POSIX.1 application. An application that both: • • Uses only the facilities described in ISO/IEC IS 9945-1:1990 and approved conforming language bindings for any ISO or IEC standard Is documented as using only those facilities and approved conforming language bindings isolated ground.
Glossary LANMAN LANMAN. See LAN manager (LANMAN) process. LAN manager (LANMAN) process. The process provided as part of the ServerNet local area network (LAN) Systems Access (SLSA) subsystem that starts and manages the SLSA subsystem objects and the LAN monitor (LANMON) process and assigns ownership of Ethernet adapters to the LANMON processes in the system.
Glossary libList libList. The list of libraries to be loaded along with a loadfile. When linking the loadfile, the linker constructs the libList from the names of libraries specified in the linker’s command stream. It stores the libList within the loadfile. library. A generic term for a collection of routines useful in many programs.
Glossary link count link count. In the Open System Services (OSS) file system, the number of directory entries that refer to a particular file. linker. (1) The process or server that invokes the message system to deliver a message to some other process or server. (2) A programming utility, which combines one or more compilation units’ linkfiles to create an executable loadfile for a native program or library. linkfile.
Glossary loadfile loadfile. An executable object code file that is ready for loading into memory and executing on the computer. Loadfiles are further classified as executable programs (containing a main routine at which to begin execution of that program) or executable libraries (supplying routines or variables to multiple programs or separately loaded libraries). A TNS code file might be both a loadfile and a linkfile. Native code files are never both. Contrast with linkfile. loadList.
Glossary local system local system. (1) An on-site system or a system that is geographically near the user or operator. (2) From the perspective of a particular SNETMON, the system or node on which that SNETMON is running. (3) From the perspective of a system console operator, the system to which the operator is logged on. Contrast with remote system. logical device name. The name assigned to an I/O process during its configuration.
Glossary logon sequence logon sequence. The process through which the HP NonStop™ S-series server to be managed is determined, the security constraints to interact with that server are met, and a connection with that server is established. low-level link. A connection between the OSM or TSM client software running on a system console and the master service processors (MSPs) on an HP NonStop™ S-series server.
Glossary master service processor (MSP) master service processor (MSP). A service processor (SP) that provides the basic service processor functions as well as centralized system functions such as a console port, a modem port for remote support functions, and system-load control. The enclosure containing processors 0 and 1 (group 01) also contains a pair of MSPs. See also expansion service processor (ESP). MB. See megabyte (MB). Measure.
Glossary message monitor process (MSGMON) message monitor process (MSGMON). A helper process for the ServerNet cluster monitor process (SNETMON) that runs in each processor on every node of a ServerNet cluster. MSGMON is started by the persistence manager process, $ZPM. It performs duties for SNETMON in those instances where SNETMON needs an agent in each system processor. In addition, MSGMON monitors the connections within the processor and reports changes back to SNETMON when required. MFIOB.
Glossary mount mount. To make a fileset accessible to the users of a node. mount point. In the Open System Services (OSS) file system, a directory that contains a mounted fileset. The mounted fileset can be in a different file system. MRouter. A field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC) that is part of the serial maintenance bus (SMB) architecture. The MRouter distributes the SMB throughout a group. MSEB. See modular ServerNet expansion board (MSEB). MSEB CBB.
Glossary NAM NAM. See Network Access Method (NAM). named resource list (NRL). A table that contains one entry for each device and named process in the system. A logical device number (ldev) is an NRL index. national-standards-body conforming POSIX.1 application.
Glossary network routing table (NRT) network routing table (NRT). A table that resides in each processor in each system in a network. The NRT associates each destination system with the logical device (LDEV) number of the best-path route Expand line-handler process to use to send messages to that system. See also network control process. network topology. The physical layout of components that define a system, a local area network (LAN), or a wide area network (WAN). neutral.
Glossary nonconfigured object nonconfigured object. An object that comes into existence after Subsystem Control Facility (SCF) is running and that was created in response to activity outside the SCF environment. An SCF STATUS command can display the name of a nonconfigured object, but its state is UNKNOWN. nondedicated (public) LAN.
Glossary NonStop™ TCP/IP subsystem NonStop™ TCP/IP subsystem. See HP NonStop™ TCP/IP subsystem. NonStop™ TCP/IPv6. See HP NonStop™ TCP/IPv6. NonStop Technical Library. See HP NonStop™ Technical Library (NTL). normal mode. Electromagnetic interference that occurs between current-carrying conductors (for example, line to neutral). normal mode notification. Another name for an incident report created by the OSM and TSM Notification Director.
Glossary null object type null object type. A placeholder object type for the Subsystem Control Facility (SCF) NAMES and VERSION commands, which do not require explicit specification of a particular object type. null string. In C and C++ programs, a character string that begins with a null character. This term is synonymous with empty string. OBEY file. See command file. object.
Glossary ohm Distributed Systems Management/Software Configuration Manager (DSM/SCM) (which in turn runs SYSGENR) to generate a system image for the new configuration. ohm. The standard unit for measuring resistance. online. Used to describe tasks that can be performed while the HP NonStop™ Kernel operating system and system utilities are operational. Contrast with offline. online change. Any change that can be performed while an application or its system resources are operational.
Glossary Open System Services (OSS) environment users of the OSS environment usually use the OSS shell for their command interpreter. Synonymous with Open System Services (OSS) environment. Contrast with Guardian. Open System Services (OSS) environment. The HP NonStop™ Kernel Open System Services (OSS) application program interface (API), tools, and utilities. Open System Services (OSS) Monitor.
Glossary option option. In a UNIX or Open System Services (OSS) command, a flag and its parameters or a flag without parameters. ordinary library. A dynamic-link library (DLL) or shared run-time library (SRL) that is not public. See ordinary dynamic-link library (ordinary DLL). ordinary dynamic-link library (ordinary DLL). A dynamic-link library (DLL) or shared run-time library (SRL) that is not public. The code file is found at run time and can be provided by the user.
Glossary OSS process ID OSS process ID. In the Open System Services (OSS) environment, the unique identifier that identifies a process during the lifetime of the process and during the lifetime of the process group of that process. See also PID. OSS signal. See Open System Services (OSS) signal. OSS user ID. See HP NonStop™ Kernel user ID. outage. Time during which a computer system is not capable of doing useful work. Outages can be planned or unplanned.
Glossary parent directory parent directory. A particular directory in the hierarchy of directories within a file system. The parent directory for a directory contains an entry for that specific directory and is identified in that directory as the directory immediately above it in the hierarchy. The parent directory for a file contains an entry for that file. parent process. The process that created a given process or (if the creating process has stopped) a process that has inherited a given process.
Glossary peer service processors peer service processors. A pair of service processors (X and Y) in a service processor (SP) domain. Peer service processors function similarly to a fault-tolerant process pair in an HP NonStop™ K-series system. See also service processor (SP). pending incident report.
Glossary physical interface (PIF) physical interface (PIF). The hardware components that connect a system node to a network. physical link interfaces. Communications standards defined by standards organizations. The following physical link interfaces are supported for the ServerNet wide area network (SWAN) concentrator: RS-232, RS-442, RS-449, V.35, and X.21. Physical view.
Glossary Planner Interface revisions. The planner uses the DSM/SCM Planner Interface to carry out these functions. Planner Interface. A graphical user interface (GUI) to the Distributed Systems Management/Software Configuration Manager (DSM/SCM) that runs on the host system. It provides an interface to all the host DSM/SCM planner functions. plug-in card (PIC). A replaceable component that provides a unique function when installed in a customer-replaceable unit (CRU) or field-replaceable unit (FRU).
Glossary portable filename character set portable filename character set. The set of characters that includes the Roman uppercase and lowercase letters, the Arabic numerals, the period, the underscore, and the hyphen. The hyphen cannot be the first character of a portable filename. portable pathname character set. The set of characters that includes the Roman uppercase and lowercase letters, the Arabic numerals, the period, the underscore, the slash (/), and the hyphen.
Glossary power factor correction voltage waveform with respect to the current drawn by the load. When voltage and current are in phase with each other, the power factor is unity, and the power for the load is equal to the product of the applied voltage and load current (P=EI). When the current waveform lags the voltage waveform, the load is inductive. Conversely, when the current waveform leads the voltage waveform, the load is capacitive.
Glossary PPP PPP. See Point-to-Point Protocol (PPP). preemption. A form of late binding in which a symbolic reference to a symbol defined in the same dynamic-link library is instead bound to a definition in another loadfile. preferences file. A file that contains configuration information for the graphical user interface (GUI) portion of the OSM and TSM client software. The preferences file is used by the OSM and TSM client software at system startup. preferred path. See primary path.
Glossary process group ID process group ID. In the Open System Services (OSS) environment, the unique identifier representing a process group during its lifetime. process group leader. In the Open System Services (OSS) environment, the process that has the process group ID of its process group as its OSS process ID. process group lifetime.
Glossary processor dump chips than main memory. It is most often used with process or main memory but is also used in network data transfer (to maintain a local copy of data) and so forth. processor dump. A copy of the memory of a processor. A dump can be to disk or to tape. See also ServerNet dump and tape dump. processor enclosure.
Glossary public LAN library registry, supplied by HP or, optionally, a user. Contrast with ordinary dynamic-link library (ordinary DLL). public LAN. See nondedicated (public) LAN. public library. A dynamic-link library (DLL) or shared run-time library (SRL) that is known to the operating system, available for execution by any process or user, and is not an implicit library. public shared run-time library (public SRL). A TNS/R library supplied by HP. PUP. See Peripheral Utility Program (PUP).
Glossary read/write head read/write head. An electromagnet that can pick up (read) electronic pulses and record (write) electronic pulses on a magnetic disk or tape. The electronic pulses are interpreted by the processor as binary data. See also disk drive and tape drive. real group ID. An attribute of an Open System Services (OSS) process. When an OSS process is created, the real group ID identifies the group of the user or parent process that created the process.
Glossary • regular file All accelerator code optimizations are ended. Register-exact points are a small subset of all memory-exact points. Procedure entry and exit locations and call-return sites are usually register-exact points. All places where the program might switch into or from TNS mode or TNS interpreted mode are register-exact points. Contrast with memory-exact point and nonexact point. regular file.
Glossary remote procedure remote procedure. A procedure or function packaged to be called within a server process indirectly by a client process. remote procedure call. A remote procedure or the action of calling a remote procedure. Remote Procedure Call (RPC). A protocol that extends a procedure-call form of processto-process communication to a network environment. RPC is a way for programs running on client computers to invoke the services of a program running on a server computer.
Glossary response response. The information or confirmation supplied by a subsystem in reaction to a command. A response is typically conveyed as one or more interprocess messages from a subsystem to an application. response packet. A ServerNet packet returned from one ServerNet device to another, responding to an earlier received read request or write request. In the case of responding to a read request, the response packet contains the data that the requesting device wanted to have read.
Glossary root user root of the samples. In general, rms-sensing devices are more accurate than averaging meters. Measurements from averaging meters can be as low as 30 percent of the actual current for loads with high crest factors. root user. See super ID. router. See ServerNet router. router 1. See ServerNet router 1. router 2. See ServerNet router 2. RPC. See Remote Procedure Call (RPC). RS-232. An industry standard for serial data transmission.
Glossary S78000 server S78000 server. See HP NonStop™ Sxx000 server. S86000 server. See HP NonStop™ Sxx000 server. S88000 server. See HP NonStop™ Sxx000 server. Sxx000 server. See HP NonStop™ Sxx000 server. S-series servers. See HP NonStop™ S-series servers. SAC. See ServerNet addressable controller (SAC). sag. A reduction in voltage, usually lasting from one cycle to a few seconds. Sags are typically caused by fault clearing or by heavy load startups. SAN. System area network.
Glossary SCF SCF. See Subsystem Control Facility (SCF). SCL. The mnemonic subsystem name for the ServerNet cluster subsystem. SCP. See Subsystem Control Point (SCP). SCSI. See small computer system interface (SCSI). SCSI object type. The Subsystem Control Facility (SCF) object type for an Open SCSI device. SCSI passthrough terminator. A bus-terminating plug connected between a cable and the external connector of a customer-replaceable unit (CRU).
Glossary selectable segment one unit into virtual memory as the file is loaded. See also code segment and data segment. selectable segment. A type of logical segment formerly known as an extended data segment. The data area for a selectable segment always begins with relative segment 4, and this area can be dynamically switched among several selectable segments by calls to the Guardian SEGMENT_USE_ procedure. The effect is similar to a rapid overlaying of one large data area.
Glossary serial maintenance bus (SMB) domain serial maintenance bus (SMB) domain. The set of enclosures, modules, field-replaceable units (FRUs), and customer-replaceable units (CRUs) connected by a common serial maintenance bus (SMB). server. (1) An implementation of a system used as a stand-alone system or as a node in an Expand network. (2) A combination of hardware and software designed to provide services in response to requests received from clients across a network.
Glossary ServerNet buffer board (SBB) ServerNet buffer board (SBB). The board that provides the ServerNet connection to and from the I/O multifunction (IOMF) customer-replaceable unit (CRU). This board replaces the processor and memory board (PMB) in the IOMF CRU. ServerNet bus interface (SBI). The I/O control and expansion packetizer applicationspecific integrated circuit (ASIC). ServerNet cable. A cable that provides ServerNet links between system enclosures. ServerNet cluster.
Glossary ServerNet dump ServerNet dump. To copy the memory of a processor to disk by using the ServerNet fabrics. ServerNet end device. See ServerNet device. ServerNet expansion board (SEB). (1) A connector board that plugs in to the backplane to allow one or more ServerNet cables to exit the rear of the enclosure. The SEBs and ServerNet cables allow processors in one group to communicate with processors in another group.
Glossary ServerNet node routing ID number is assigned based on the port to which the node is connected on the cluster switch. The ServerNet node number, which can be viewed using the Subsystem Control Facility (SCF), the OSM Service Connection, or the TSM Service Application, is unique for each node in a ServerNet cluster. ServerNet node routing ID. A bit field used to route ServerNet packets across the external ServerNet X and Y fabrics.
Glossary ServerNet II Switch ServerNet II Switch. A 12-port network switch that provides the physical junction point to enable an HP NonStop™ S-series server to connect to a ServerNet cluster. The ServerNet II Switch is a component of the HP NonStop™ Cluster Switch (model 6770). ServerNet switch board. Component in an IOAM. The ServerNet switch board provides ServerNet connections to the I/O adapters in the IOAM. It also provides maintenance functions for the modules in which they are installed.
Glossary service side TSM allow you to use the help of a service provider by configuring client software to support remote notification and remote access. service side. The side of a system enclosure that contains, behind an optional door, processor multifunction (PMF) customer-replaceable units (CRUs) or I/O multifunction (IOMF) CRUs, ServerNet expansion boards (SEBs), modular SEBs (MSEBs), and ServerNet adapters. The service side is opposite the appearance side.
Glossary shell shell. In the Open System Services (OSS) environment, a program that interprets sequences of text input as commands. A shell can operate on an input stream, or it can interactively prompt and read commands from a terminal. shielded twisted pair (STP). A transmission medium consisting of two twisted conductors with a foil or braid shield. Contrast with unshielded twisted pair (UTP). shutdown file.
Glossary single-mode fiber-optic (SMF) plug-in card (PIC) single-mode fiber-optic (SMF) plug-in card (PIC). A plug-in card (PIC) for the modular ServerNet expansion board (MSEB) and I/O multifunction (IOMF) 2 customerreplaceable unit (CRU) that supports the single-mode fiber-optic (SMF) interface. single-mode fiber-optic (SMF) ServerNet cable. A fiber-optic cable that allows only one mode to propagate. SMF ServerNet cable has a small-diameter core for optimized long-distance transmission.
Glossary SMF PIC SMF PIC. See single-mode fiber-optic (SMF) plug-in card (PIC). SMF ServerNet cable. See single-mode fiber-optic (SMF) ServerNet cable. SMI. See ServerNet memory interface (SMI). SMN. The mnemonic name for the external system area network manager process (SANMAN). SMP. See Security Manager Process (SMP). SMT. See SWAN manager task (SMT). snapshot.
Glossary software product revision (SPR) software product revision (SPR). The method of releasing incremental software updates on HP NonStop™ S-series systems. An SPR can include one or more corrections to code, or it can contain code that adds new function to a software product. source ServerNet ID (SID). A field in the ServerNet packet header indicating the source of the packet. SP. See service processor (SP). special character.
Glossary SS7TE plug-in card (PIC) SS7TE plug-in card (PIC). A plug-in card (PIC) used in the 6763 Common Communication ServerNet adapter (CCSA) that supports the EIA-232, EIA-449, V.35, and X.21 interfaces. SS7TE2 plug-in card (PIC). A plug-in card (PIC) used in the 6763 Common Communication ServerNet adapter (CCSA) that supports the E1, J1, and T1 interfaces. S-SAC. See SCSI ServerNet addressable controller (S-SAC). SSI log. See System Service Information (SSI) log. stackable enclosure.
Glossary STFs STFs. See super time factors (STFs). storage pool. A set of physical disk volumes administered as a set of logical disk volumes. A logical disk volume can span multiple physical disk volumes. When a logical disk volume becomes full, more physical disk volumes can be added. storage-pool file. A file containing a list of disk volumes to be used by an Open System Services (OSS) fileset. As these volumes are filled, more volumes can be added to the storage-pool file. storage subsystem.
Glossary SUB option SUB option. In some Subsystem Control Facility (SCF) subsystems, the designation that the object name given in a command stands not just for itself but for the names of all objects at the next-lower level in the hierarchy. The given object name can stand both for itself and for the subordinate objects, or it can stand only for the subordinate objects, depending on the value of the SUB option. subordinate objects.
Glossary subvolume interface procedures; and definition files in Data Definition Language (DDL) for programmers writing their own subsystems. subvolume. A group of related files stored on a disk. All the files have the same volume and subvolume name, but each file has a unique file identifier. summary report. A brief informational listing of status or configuration information provided by the Subsystem Control Facility (SCF) STATUS or INFO command. Contrast with detailed report. superblock.
Glossary SVR4 SVR4. System V Release 4, a specific implementation of UNIX. See also System V. SWAN concentrator. See ServerNet wide area network (SWAN) concentrator. SWAN 2 concentrator. See ServerNet wide area network (SWAN) 2 concentrator. SWAN manager task (SMT). A manager task that is provided as part of the wide area network (WAN) subsystem.
Glossary symbols region definition of that symbol. The symbol value is normally the address of a function or variable named by the symbol. In position-independent code (PIC) loadfiles, symbolic references occur only in data. symbols region. See Inspect region. SYSGENR. The system generation program that generates a customized version of the HP NonStop™ Kernel operating system. SYSnn subvolume.
Glossary system entry point table (SEP table) system entry point table (SEP table). A table used on TNS systems that stores the XEP entry value for each TNS operating system procedure entry point. system expansion. The process of making a target system larger by adding enclosures to it. The enclosures being added can be either new enclosures or enclosures from a donor system. Contrast with system reduction. system generation.
Glossary system process system process. (1) A privileged process that comes into existence at system-load time and exists continuously for a given configuration for as long as the processor remains operable. (2) An HP NonStop™ Kernel operating system process, such as the memory manager, the monitor, and the input/output (I/O) control processes. The files containing system processes are invoked by ALLPROCESSORS paragraph entries.
Glossary tape load and unloading them from the drives, and a means for an operator to load cartridges into or remove cartridges from the tape library. tape load. A system load. A tape load is the process of reading a system image tape (SIT) and writing it to the system disk. Performing a tape load from a SIT to restore the system image files to the $SYSTEM disk is generally not recommended. Perform a tape load only with the advice of the Global Customer Support Center (GCSC) or your service provider.
Glossary tetrahedron tetrahedron. A solid bounded by four triangular faces. In ServerNet context, a tetrahedron is four processors interconnected by ServerNet links so as to form a conceptual tetrahedron. Each processor therefore has a direct connection to the other three processors. See tetrahedral topology. text string. A variable-length sequence of ASCII characters, defined in the CONFTEXT file, that an identifier represents.
Glossary TNS library TNS/R systems, TNS instructions are implemented by millicode routines or by translation to an equivalent sequence of RISC instructions. TNS library. A single, optional, TNS-compiled loadfile associated with one or more application loadfiles. If a user library has its own global or static variables, it is called a TNS shared run-time library (TNS SRL). Otherwise it is called a User Library (UL). TNS loading. A task performed at process startup time when executing a TNS object file.
Glossary TNS/R library system-level architecture. Systems with these processors include most of the HP NonStop™ servers. Contrast with TNS. TNS/R library. A TNS/R native-mode library. For a PIC-compiled application, TNS/R libraries can be dynamic-link libraries (DLLs) or hybridized native shared runtime libraries (SRLs). For an application that is not PIC compiled, TNS/R libraries can only be native SRLs. TNS/R native mode. The operational environment in which native-compiled RISC instructions execute.
Glossary Transmission Control Protocol (TCP) rapid translation is accomplished by remembering and reusing the translations of recently referenced pages. Transmission Control Protocol (TCP). A connection-oriented protocol that provides for the reliable exchange of data between a sending and a receiving system. TCP implements functions corresponding to the Open Systems Interconnection (OSI) reference model Layer 4, the transport layer. Transmission Control Protocol/Internet Protocol (TCP/IP).
Glossary UCME UCME. See uncorrectable memory error (UCME). UID. A nonnegative integer that uniquely identifies a user within a node. In the Open System Services (OSS) environment, the UID is the scalar view of the HP NonStop™ Kernel user ID. The UID is used in the OSS environment for functions normally associated with a UNIX user ID. unattended site. A computer environment where no operator resides on site and the only access is from a central monitoring station. uncorrectable memory error (UCME).
Glossary UPS UPS. See uninterruptible power supply (UPS). upward compatibility. The ability of a requester to operate with a server of a later revision level. In this case, the requester is upward-compatible with the server, and the server is downward-compatible with the requester. Contrast with downward compatibility. User Code (UC). See TNS code space. user code. A logically distinct part of the HP NonStop™ Kernel operating system that consists of the code for user processes. user database.
Glossary volt (V) volt (V). The standard unit of measure of the potential difference that is required to move an electric charge. volume. A logical disk, which can be one or two magnetic disk drives. In HP NonStop™ S-series systems, volumes have names that begin with a dollar sign ($), such as $DATA. See also mirrored disk or volume. WAN. See wide area network (WAN). WANBoot process.
Glossary Windows Internet Name Service (WINS) Windows Internet Name Service (WINS). A name resolution service that resolves Windows NT networking computer names to Internet protocol (IP) addresses in a routed environment. A WINS server handles name registration, queries, and release version updates (RVUs). See also IP address. WINS. See Windows Internet Name Service (WINS). work files. Temporary files created during system generation that serve as storage areas.
Glossary XIO XIO. See extensible input/output (XIO). XLLINK. The linker program invoked during system generation to link accelerated (file code 100) TNS object files to create system code and system library files. XO bond. The bond connection on an isolation transformer, installed between the transformer’s neutral XO terminal and ground.
Glossary $ZTC0 $ZTC0. The default transport-provider process that provides Transmission Control Protocol/Internet Protocol (TCP/IP) services to Open System Services (OSS) AF_INET sockets programs. $ZZATM. The name of the Asynchronous Transfer Mode (ATM) monitor process. $ZZFOX. The name of the Fiber Optic Extension (FOX) monitor process in the ServerNet/FX adapter subsystem. $ZZKRN. The name of the Kernel subsystem manager process. $ZZLAN.
Glossary $ZZWAN HP NonStop S-Series Planning and Configuration Guide—523303-015 Glossary- 120
Index Numbers 3860 ATM 3 ServerNet adapter (ATM3SA) See also ServerNet adapters See ATM3SA ServerNet adapter 3861 Ethernet 4 ServerNet adapter (E4SA) See Ethernet 4 ServerNet adapter (E4SA) 3862 Token-Ring ServerNet adapter (TRSA) See Token-Ring ServerNet adapter (TRSA) 3863 Fast Ethernet ServerNet adapter (FESA) See Fast Ethernet ServerNet adapter (FESA) 3865 Gigabit Ethernet ServerNet adapter (GESA) See Gigabit Ethernet ServerNet adapter (GESA) 3865 Gigabit Ethernet ServerNet adapter (GESA-C) See Gigabit
Index A 6780 ServerNet Switch See Cluster switch See HP NonStop ServerNet Switch (model 6780) 9490 tape drive See Tape drives 9710 Automatic Cartridge Subsystem (ACS) tape library See Tape libraries 9841 Cartridge tape drive See Tape drives A AC power enclosures with power shelves 4-14 PMF CRUs 4-37, 4-56 system enclosures 4-14, 4-37, 4-56 three-phase recommended 12-7 AC power components 4-14 AC power cords IOMF CRUs 4-56 part numbers A-30 PMF CRUs 4-37 service class 1-26 AC power cords, characteristics
Index C Batteries (continued) memory backup 10-8 operation during power loss 4-9, 10-6 power failure 10-7 recharging 4-9, 10-8 recycling B-2 slots 4-9, B-2 spare batteries 4-9, 10-8 Battery retainer 1-26 Bezel 4-71 Branch circuits labeling 12-7 requirements for 12-8 C Cable management system 4-71 Cables AC power See AC power cords adapter A-19 DC power 1-29 EPO cable assembly 1-29 labeling 12-4 lengths choosing 7-4/7-9 example of choosing D-1/D-4 part numbers A-26 SCSI A-26 ServerNet See ServerNet cables
Index D Configuration files (continued) CONFSAVE 15-6 CONFxxyy 15-6 types of 8-9/8-12, 15-5/15-6 Configuration management, creating policies for 9-5 Configuration planner, functions of 9-2 Configuration tools KMSF See KMSF OSM package See OSM SCF See SCF TSM package See TSM Configuration utility process ($ZCNF) 15-4 CONFSAVE file, autosaved CONFIG file 15-6 CONFTEXT file changing 15-3 location of 8-4 processor types specified in B-12 CONFxxyy file, saved CONFIG file 15-6 Convenience receptacles, requireme
Index E Domain name servers 1-48 Domain names 1-47 Door See Enclosure door Dotted decimal format of IP addresses 1-46 E E4SA See Ethernet 4 ServerNet adapter (E4SA) E4SA adapters F-3 ECL cables 5-2 See also ServerNet cables ECL PIC 4-21, A-5, F-4 in an IOMF 2 CRU 4-55 part number A-5 Electrostatic discharge (ESD) See ESD Emergency power-off (EPO) See EPO Emergency power-off (EPO) cable assembly 1-29 Emitter-coupled logic (ECL) See ECL cables See ECL PIC Enclosure 1-29 Enclosure Arrangement Diagram comple
Index F Ethernet 4 ServerNet adapter (E4SA) part number A-13 See also ServerNet adapters See E4SA adapters service class 1-27 Ethernet hubs A-20 for system consoles 12-5 Expand manager process ($ZEXP) E-5 Expansion service processors (ESPs) See Service processors (SPs) Expansion, system 7-13 External disk drives See Disk drives F Fabrics associated adapter slots 4-24 connections to SEBs 4-18 connections to ServerNet adapters 1-43 definition 1-43 X fabric connections to MFIOB SACs 4-39 connectors 4-23 Y f
Index G Floor Plan completing 12-2 purpose of 12-3 Frame 1-29 FRUs emergency power-off (EPO) interface cable assembly 1-30 identifying 1-23 listed 1-29 power shelf See Power shelf ServerNet/FX 2 adapter See ServerNet/FX 2 adapter ServerNet/FX adapter See ServerNet/FX adapter tape drives See Tape drives FTP 1-44 Future system expansion, room selection 12-2 F-PIC description F-4 service class 1-28 G Generic processes 15-5 GESA See Gigabit Ethernet ServerNet adapter (GESA) Gigabit Ethernet 4-port ServerNet
Index I I Inner tetrahedron 3-6 Installation new system, overview of tasks 9-6 planning the schedule 13-1 Installation Document Checklist, completing 13-3 Installation Document Packet assembling 13-2 See Document packet 9-8 Installation forms blank C-1 purpose of 9-2 Installer, functions of 9-2 Internet Protocol (IP) 1-45 See also TCP/IP IOAM enclosure bezel 4-71 cable management system 4-71 cabling 5-12, 7-1 chassis 4-70 components 1-17 fans 4-70 fiber-optic cables with LC-SC connectors 5-5 front side 1-
Index K I/O enclosures See also System enclosures adding 7-13 balancing 7-13 cabling 5-16 contents 1-3 description 1-3 group numbers 3-11, 3-12 illustrations 1-9, 1-10, 1-13, 1-14 modified 1-3 I/O multifunction 2 (IOMF 2) CRU See IOMF 2 CRUs I/O multifunction (IOMF) CRU See IOMF CRUs Light-emitting diodes (LEDs) See LEDs Linear tape open (LTO) tape drive A-12 LMUs contents of 4-39 on PMBs 4-39 Local address 1-45 Logical memory units (LMUs) See LMUs Loopback test connector 1-26 Low Power Mode 10-6 LTO See
Index N Memory units LMUs 4-39 location of 4-39 part numbers A-4 replaceability 1-28 Metric rack mount kit CRU type 1-26 part number A-5 MFIOB functions of 4-46, 4-57 SACs Ethernet 4-46 SCSI 4-46 SACs, SCSI 4-57 service processor 4-46 SMB connections 4-46 MFIOB 2 See MFIOB MMF PIC 4-21, F-4 in an IOMF 2 CRU 4-55 part number A-5 service class 1-28 Modem cables A-20 optional for system consoles 12-5 part numbers A-20 requirement for system consoles 12-5 universal A-22 Modified I/O enclosure 1-3 Modular cabi
Index O NonStop S76000 and S86000 servers 4-25, 5-20 NonStop Virtual Hometerm Subsystem (VHS) 15-11 O ODR See Online disk remirroring (ODR) Offline configuration changes application reconfiguration 15-1 installing a new software release 15-1 installing a product revision 15-2 system name, number, time 15-2 tasks 15-1 Online disk remirroring (ODR) 9-12 Open-reel tape drive See Tape drives Operator, responsibilities of 9-2 OSIMAGE file on D-series RVUs 15-5 OSM online configuration using 15-9 recommended o
Index P PMB LMUs 4-39 memory slots 4-39 physical description 4-38 PMCU appearance side 4-8 fan connections 4-12 FRU type 1-29 functions 4-8 service processors 4-8 slots 4-8 PMF 2 CRU See also PMF CRU faceplate 4-36 part numbers A-3 ports 4-37 ServerNet Router 2 4-49 PMF CRU 16 GB processor configuration requirements 4-25 AC power 4-37, 4-56 communication pathways 6-2 configuration form, completing 13-16 faceplate 4-33, 4-34, 4-35 functions 4-49 LEDs 4-33 memory units See Memory units part numbers A-3 port
Index Q Power-fail ride-through time See Power-fail delay time Power-on cables 7-1, 7-10 PPP 1-45 Preinstalled I/O Device Cable Checklist completing, procedure 13-11 purpose of 13-11 Primary system console See System consoles Problem reporting and tracking, creating policies for 9-5 Processor and memory board (PMB) See PMB Processor enclosures See also System enclosures contents 1-3 group numbers 3-12 illustrations 1-7, 1-8, 1-11, 1-12 Processor multifunction 2 (PMF 2) CRUs See PMF 2 CRUs Processor multif
Index S SCF (continued) subsystems in systems running the Gseries 15-4 topic 15-3 SCF0000 command file configuration file 15-6 naming conventions 8-13 SCSI buses bus 1 slots 4-7 bus 2 slots 4-7 configuring mirrored volumes on 4-5 SACs for 4-46 terminators See SCSI terminators SCSI SAC for external differential SCSI port 4-57 SCSI terminators passthrough terminators 4-37, 4-55 SCSI bus 4-7 service class 1-28 SCu PIC 4-21 SEB fabric connections for 4-19 relationship to processors and ServerNet fabrics 4-19
Index S ServerNet cabling (continued) diagonal connections with intervening enclosures 7-8 different-row connections 7-9 forms 13-23, 13-25 horizontal connections with intervening enclosures 7-7 same-row connections 7-5 tables Tetra 16 topology 5-15 Tetra 8 topology 5-10 Tetra 16 topology 5-12/5-16 Tetra 8 topology 5-8/5-11 worksheets 13-25 ServerNet Cluster 4-69, 13-2, 13-22, 15-9 ServerNet device adapter (ServerNet/DA) part number A-13, A-14 supported configurations F-3 ServerNet ECL cables See ECL cabl
Index S Service side See also specific components group ID label 4-3 group service LED 4-18 IOMF CRUs 4-50 module ID label 4-18 PMF CRU 4-32 SEBs 4-18 ServerNet adapters 4-25 slots in 4-16 Setup configuration cable connections 11-7 security 11-7 to system console 8-18 Shutdown files automating 15-11 sequence of 15-11 Side panel, enclosure 4-62 Signal reference grid 7-1, 7-12, 12-7 Simple Network Management Protocol (SNMP) 1-44, 4-67 Single-mode fiber-optic (SMF) PIC 4-21 Site planning additional resources
Index S SWAN concentrators (continued) LAN planning for 11-2 manuals 4-69 part numbers A-19 service class 1-27 supported F-3 Swap files See also KMSF configuration default values 15-8 when to change 15-8 description 15-8 System area network (SAN) See ServerNet SAN System consoles 4-66/4-67 backup 4-67 connecting to system 12-5 branch circuits for 12-8 configuration of multiple workstations, multiple systems 11-12 multiple workstations, one system 11-9 one workstation, multiple systems 11-8 one workstation
Index T T TACL CIIN file 15-11 startup processes 15-11 system console window 15-11 Tall enclosure door 4-61 Tape drives adding 8-5, 9-13 branch circuits for 12-8 changing the configuration of 9-13 description 4-68 for 16 GB processors 8-5 in systems having 16-GB memory 1-15 power requirements for 12-9 SCSI cables for 12-9 service class 1-27, 1-30 Tape libraries 1-30, 12-3 TCP 1-44 See also TCP/IP TCP/IP defined 1-44 TSM communication 4-67 TCP/IPv6 1-44 Telephone lines for remote access to system 12-4 Term
Index U Transmission Control Protocol over Internet Protocol (TCP/IP) See TCP/IP Transmission Control Protocol (TCP) 1-44 See also TCP/IP TRSA See Token-Ring ServerNet adapter (TRSA) TSM online configuration using 15-9 recommended operating configuration 11-9 setup configuration 8-18, 11-7 updating firmware 15-9 TSM package See TSM U Ultra SCSI PIC 4-51 Unattended sites, monitoring and maintaining 15-9 Uninterruptible power supply (UPS) See UPS Unplanned outages causes 10-5 defined 10-1 minimizing durati
Index Special Characters Special Characters $AUDIT, files in 8-4 $DSMSCM, files in 8-4 $SYSTEM 8-4, 9-11, F-2 $SYSTEM.ZSYSCONF.CONFIG 15-4 $YMIOP.
