This chapter provides the prepatory steps that must be performed before you can begin actual installation. It is extremely important to read and perform these steps.
It is recommended that two SSEs perform the array installation. One of the SSEs should be the designated "driver," who operates the IRISconsole station and installs and configures the software and then sets up the network. For example, a second SSE can help verify and check off steps during the procedures, install hardware, and cable HIPPI.
 | Note: It is highly recommended that at least one of the SSEs be familiar with network configuration and HIPPI configuration. |
The installation of the array will go much more smoothly if a set of preinstallation information is obtained in advance of hardware bring-up, as described in Table 3-1. Much of this information can be obtained days or weeks in advance of customer hardware rollout.
The array site should have already been selected and prepared as described in the Chapter 2, "Installation Planning and Site Preparation."
In addition, be sure to perform and check off the following technical, administrative, and bureaucratic tasks prior to installation, to help ensure a successful array setup.
Table 3-1. Preinstallation Checklist
Activity | Date Completed | Notes |
|---|---|---|
Read supporting manuals, array Web pages, release notes and reference pages (man pages). | __/__/__ |
|
Gather the supporting documentation. See "Related Documents". | __/__/__ |
|
Look at the two array World-Wide Web (WWW) sources for latest information: http://www-hpc.asd.sgi.com/Projects/Array (viewable only within the Silicon Graphics firewall) http://www.sgi.com/Products/PowerChallengeArray (viewable by anyone with web access) http://www-nsd.engr.sgi.com/nsd/htmls/prodmkt/DataArra y/index.html (viewable only by Silicon Graphics employees inside the Silicon Graphics firewall) | __/__/__ |
|
Read the related release notes and man pages. These documents contain important information not covered in the array manuals such as diagnostics testing and array command definition. |
|
|
Establish clear lines of communication with the customer. | __/__/__ |
|
Ensure that you have strategic points of contact with the fieldand with the customer (see Section 3.2). The customer contacts should represent the customer's needs and have authority to make decisions. | __/__/__ |
|
Verify that all the required hardware and software have been received and inventoried (see Section 3.3). | __/__/__ |
|
Obtain the inventory list and the system serial numbers from the customer. | __/__/__ |
|
Verify that floor space and local area networking, and environmental preparations have been properly completed (see Section 3.5). | __/__/__ |
|
Assign each array node a node number from 1 to N, where N is the number of nodes (see Section 3.4). | __/__/__ |
|
Determine the array name (see Section 3.9). | __/__/__ |
|
Plan the local area network and HIPPI setup with the customer. | __/__/__ |
|
Draw a HIPPI connectivity diagram. For arrays with HIPPI switches, identify the HIPPI switch ports for each HIPPI interface connection (Section 3.7). | __/__/__ |
|
Determine if logical or source routing is to be used for HIPPI network routing, and determine HIPPI I-fields for each array node (see Section 3.8). | __/__/__ |
|
Determine the local area network (typically Ethernet) IP addresses and hostnames for the IRISconsole and array nodes, and be sure they've been properly allocated and registered at the site (see Section 3.10). | __/__/__ |
|
Determine the HIPPI IP addresses and hostnames for the array nodes, and be sure they've been properly allocated and registered at the site (see Section 3.11). | __/__/__ |
|
Assign IRISconsole multiplexer ports for each array node (see Section 3.6). | __/__/__ |
|
Label the networking cables (see Section 3.7.2). | __/__/__ |
|
Because arrays are commonly placed in large organizations, it is important to configure the array with respect to the administrative structure in place at the site. More organizational coordination may be required for array installations than for workstation and single server installations. Be sure that your contacts have the ability and authority to make the required decisions.
The array consists of many layered hardware and software components, which if absent prevent the complete and proper operation of the system. Carefully ensure that all inventory has arrived at the site, and has cleared the customer's local inventory control procedures. Collect and record the system serial numbers. Table 3-2 lists some of the major hardware and software components of the array.
Description | Part Number |
|---|---|
Multi-Port HIPPI switch (Note: The switch is optional for 2 array nodes) | 9110124 |
HIPPI board | 030-0522-007 (Note: The HIPPI board must be at revision 7 or later, if released to properly support the HIPPI bypass function and the new version of MPI). |
HIPPI cables (2 pairs per HIPPI interface if using switch, 1 pair per HIPPI interface if switchless) | 9290123 |
HIPPI Software | 813-0306-00x |
Serial port cable per HIPPI Switch (Indy to control port) | 018-0527-00x |
IRISConsole software (on two CDs) | 813-0384-00x and 8130-0385-00x |
Serial Port Multiplexer | 933210 |
Serial port cables for each array node (2) | 018-0527-00x |
Array software package (1.0 release) | SC4-PCAS-1.0 (POWER CHALLENGEarray only) |
Array software package(2.0 release) | SC4-CAS-2.0 (for POWER CHALLENGEarray or CHALLEGE DataArray). Note: This version requires IRIX 6.2 |
Because the array may consist of a large number of servers, it is useful to assign each server an increasing number starting at 1. These node numbers will be used to assist in proper network wiring and to compute configuration table entries.
Be sure the proper physical, electrical, and environmental preparations have been completed in advance of the array installation, as discussed in Chapter 2.
Be sure proper floor space has been allocated to permit connectivity of the IRISconsole to the array nodes, connectivity of the HIPPI components, and connectivity of optional graphics displays to array nodes. Be sure networking plans have been constructed to place the array on a local Ethernet and to support the HIPPI network. Be sure proper power and cooling have been arranged.
The IRISconsole multiplexer connects to an Indy workstation through a SCSI cable, and to each array node through two special IRISconsole serial cables (p/n 018-0527-001), one for the array node system console port, and one cable for the array node diagnostic port. Prepare a console connectivity diagram in advance of the installation. Refer to the IRISconsole Administrator's Guide (p/n 007-2872-xxx) for more information.
The HIPPI interfaces, cables, and switch (optional for two-node arrays) form a high-speed network connecting the array nodes. Careful, well-organized planning up front can dramatically ease the subsequent HIPPI network wiring and configuration as described in this section.
First, it is important for you to be familiar with the installation of HIPPI interfaces, and some of the basic administration. Refer to the IRIS HIPPI Installation Instructions (p/n 108-0106-xxx) and the IRIS HIPPI Administrator's Guide (p/n 007-2229-xxx) for detailed information about the theory and practice of HIPPI networking.
Once you are familiar with the basics of HIPPI, draw a diagram showing the cabling connections between HIPPI interfaces, and between the switch if present. Note that each HIPPI interface requires two cables, one for outgoing data (the source), and one for incoming data (the destination).
| Note: The source on one interface (or switch port) must be connected to the destination on another interface or switch port. |
If there are only two array nodes, no switch is required. An interface on one system can be directly connected to the corresponding interface on the other.
If there is a switch, the interface on a system must be connected to a port on the switch. It is important to record which port number each array node and each interface connect to. A good systematic scheme for port assignment is:
For single HIPPI interface arrays, it is suggested that you connect the HIPPI interface of the first node to HIPPI switch port 0 (the first available HIPPI port).
For double HIPPI interface arrays, it is suggested that you connect the first HIPPI interface of node 1 to HIPPI switch port 0, the second HIPPI interface of node 1 to HIPPI switch port 1, the first HIPPI interface of node 2 to HIPPI switch port 2, and the second HIPPI interface of node 2 to HIPPI switch port 3.
Be sure the HIPPI networking diagram is complete before continuing.
Before you can configure the HIPPI network, you need to decide the routing method to use. HIPPI supports two methods of routing data between the sending and receiving interfaces; these are called source routing and logical routing. I-Fields in source routing describe the exact path a connection makes through switch ports. I-Fields in logical routing indicate a node number, and the switches internally decide the appropriate path to take to get to another node's interface. It is recommended that you to use source routing unless the customer specifically requests otherwise, because less configuration is required.
HIPPI I-Fields are values that describe how to route data from a transmitting interface to a particular receiving interface through a HIPPI network. The I-Fields are required because a HIPPI network may consist of multiple switches and numerous HIPPI interfaces. The I-Fields indicate the path and connection attributes the network should use when forming connections. Each array node has a file, /usr/etc/hippi.imap, that contains I-Fields describing how to connect to the other HIPPI interfaces. The array node consults this file when connecting to other HIPPI interfaces.
Determine and record the I-Fields for every array node, as described in IRIS HIPPI Installation Instructions (p/n 108-0106-xxx).
The array requires a name. The name is used by various array facilities. Ask the customer to determine a convenient, descriptive name (for example, sgi_array or hotbox). The name may contain alphanumeric characters beginning with a letter. Keep the array name sensibly short, so it does not become unwieldy.
The nodes of an array are connected to the IRISconsole and two other computer systems via a local area network (LAN). This local area network is separate from the HIPPI network described earlier. The most commonly used local area network is Ethernet.
You must have the following information to configure the LAN:
a network number
IP addresses and hostnames on this network for each array node, and for the IRISconsole Indy
These addresses and hostnames must be allocated and registered at the customer's site. Be sure to have the network address, host IP addresses and hostnames before continuing.
| Note: It is recommended that the primary hostname of each array node be a simple name followed by the node number. This will ease configuration. For example, a four-node array called "hotbox", in the domain engr.sgi.com might have nodes named hotbox1.engr.sgi.com through hotbox4.engr.sgi.com. |
Similarly, you must have a network address for the HIPPI network, and host addresses and names for each array node on the HIPPI network. The IRISconsole is not on the HIPPI network, so no HIPPI IP addresses need to be created for the Indy workstation.
| Note: It is recommended that you select the names of the array nodes on the HIPPI network to be a prefixed version of the local area network hostnames. If available, it is recommended that you use "gate2-"as the prefix for the HIPPI interface "hip0-", and "gate3-" as the prefix for the interface "hip1-". For example, the HIPPI interfaces for host hotbox3.engr.sgi.com might be called gate2-hotbox3.engr.sgi.com and gate3-hotbox3.engr.sgi.com. |
At this point, the preparatory steps should be complete. Verify that the preconfiguration checklist in Table 3-1 is complete before you begin the actual installation.