Make sure that the installation site meets the operating limits and AC power requirements as explained in Chapters 3 and 4 of the CHALLENGE/Onyx Site Preparation Guide.

Make sure required tools and personnel are on hand for unloading and opening crates and for moving large systems.

Prepare the physical location to allow for space, air flow, and floor-loading requirements for all component systems, as explained in Chapter 3 of the CHALLENGE/Onyx Site Preparation Guide.

Plan to situate the OPS component systems fairly close together. Differential SCSI cables, including cabling inside the chassis, can be no longer than 25 meters (82 feet). Use only the cables included in the shipment.

Make sure the site meets safety and operating considerations, as explained in Chapter 3 of the CHALLENGE/Onyx Site Preparation Guide. Note that the fully loaded Challenge RAID rack weighs 899.4 lb (407.96 kg); make sure flooring is adequate.

Prepare the site for the systems' electrical requirements, as explained in Chapter 4 of the CHALLENGE/Onyx Site Preparation Guide.

Connect your laptop or ASCII terminal and keyboard to the first Challenge server, as explained in the server installation instructions.

Reserve the label sheets that are included with the Challenge vault systems; you need them for labeling SCSI cables for OPS.

Set the SCSI bus selectors on each optional vault to 8 through 15. Figure 2-1 shows the location of the settings.

Figure 2-1. SCSI Bus Selectors on Front of Vault

Connect the power cord for the first OPS host (OPS1). Turn on the main power switch on the back of the unit; turn on the laptop or ASCII terminal. If necessary, see the server installation instructions for details.

On the OPS host, turn the System Controller key switch to the On position. When power-on diagnostics are completed, a message appears.

Type hinv on each OPS host; the screen should display output like the following (some lines omitted for clarity):

6 150 MHZ IP19 Processors

... 
Integral Ethernet controller: et0, Ebus slot 5
FDDI ... : fxp0 
EPC external interrupts
Integral SCSI controller 1: Version WD33C95A, differential, revision 0
Disk drive: unit 1 on SCSI controller 1
Integral SCSI controller 0: Version WD33C95A, single ended, revision 0
Tape drive: unit 6 on SCSI controller 0: DAT
Integral SCSI controller 7: Version SCIP/WD33C95A
Integral SCSI controller 6: Version SCIP/WD33C95A
Integral SCSI controller 5: Version SCIP/WD33C95A
Integral SCSI controller 4: Version SCIP/WD33C95A
Integral SCSI controller 3: Version SCIP/WD33C95A
Integral SCSI controller 2: Version SCIP/WD33C95A
Integral EPC parallel port: Ebus slot 5
VME bus: adapter 0 mapped to adapter 21
VME bus: adapter 21

Set up each system on the network for the site.

Have ready eight of the OPS host-vault cables. Use only these cables for this connection.

On blank labels from the label sheet, create labels OPS1, OPS2, Vault 1, and Vault 2. Attach the labels to the appropriate OPS hosts and vaults.

Power off both servers and vaults.

On the back of vault 1, insert one of the cables into the top SCSI channel A socket, as shown in Figure 2-5.

Label the cable end or connector; follow the scheme in Figure 2-3.

Connect the other end of this cable to an even-numbered SCSI bus port on the first OPS host (OPS1), as shown in Figure 2-5. Label the connector or cable end.

Figure 2-5. Connecting the First Challenge Vault and Server

On the back of vault 1, insert a cable into the top SCSI channel B socket. Label the cable end.

Connect the other end of this cable to an odd-numbered SCSI bus port on the first OPS host (OPS1), as shown in Figure 2-6. Label the cable end or connector.

Figure 2-6. Connecting SCSI Buses A and B from the First Vault to the First Server

Insert a third cable into the lower SCSI channel A port on the back of vault 1. Label the cable end.

Connect the other end of this cable to the same even-numbered SCSI bus port on the second OPS host (OPS2) that you used on OPS1, as shown in Figure 2-7. Label the cable end.

Insert a fourth cable into the lower SCSI channel B port on the back of vault 1 and label it. Connect its other end to same odd-numbered SCSI bus port on the second OPS host (OPS2) that you used on OPS1. Label the cable end. Figure 2-7 shows all cables for the first vault installed.

Figure 2-7. Cabling the First Vault to Both Servers

Connect the four remaining cables to the second vault; follow the pattern in steps 4 through 11. Figure 2-4 earlier in this chapter shows this cabling.

If necessary, reset the SCSI bus selector settings on the front of each Challenge vault if they have been unset accidentally.

If one or more optional Digital Linear Tape drives (DLT) were ordered, install them in the server(s).

Power on the vaults. Power on the servers.

Do a dummy I/O to test each link. For example, in the numbering scheme used so far, to test SCSI bus 2, send data from OPS1 to disk 8 on SCSI bus 2 (dks2d8) and see if the disk light for disk 8 on the first vault lights up. Send data from OPS2 and see if the same LED is activated. Repeat this process for each bus.

Halt and power off each system.

For the first OPS host, enter the command nvram. The last line of this command's output should contain the line

scsihostid=

This output means that the SCSI host ID for this OPS host is 0, the default.

Repeat step 2 in the second window for the second OPS host. The last line of the output should be scsihostid=2, meaning that the SCSI host ID for the second OPS host is 2.

Reboot and start the System Maintenance menu; choose item 5, the Command Monitor.

In the Command Monitor, set the SCSI ID for this system:

setenv scsihostid 2

---

Caution: No SCSI device on any bus on any server should have SCSI ID 2.

---

To verify that the SCSI ID was set, enter

printenv

The output should include the line scsihostid=2.

Exit the System Maintenance menu and restart the system.

Enter the command hinv; see Section 2.1, "Setting Up the Component Systems," for a sample output.

Enter the command hinv for the second server. Compare the output for each server.

Check the contents of the FDDI board shipment, as explained in Chapter 1 of the FDDIXpress Mezzanine Board Installation Instructions.

Use the versions command to see if the system into which you are installing the FDDIXPress™ mezzanine board is already running FDDIXPress software. If FDDIXPress is not installed, install it following the instructions in the FDDIXpress Release Notes.

Install the FDDIXpress board following instructions in Sections 2.1 and 2.2 in Chapter 2 (Challenge L) or Sections 3.1 and 3.2 in Chapter 3 (Challenge XL) of the FDDIXpress Mezzanine Board for CHALLENGE and Onyx Installation Instructions.

Cable the connections and complete the installation as explained in Chapter 4 of the FDDIXpress Mezzanine Board for CHALLENGE and Onyx Installation Instructions.

Edit /etc/config/netif.options to include network addresses, for example:

 #  To override the name and/or address of the first gateway interface,
 #  change the value part and remove the leading : character.

 : if2name=ipg0
 : if2addr=dlm-$HOSTNAME

 #  If this host has more than 2 interfaces, you must define values for
 #  if3name (and if4name if appropriate). Change if3addr (and if4addr) to
 #  the appropriate names in /etc/hosts if your site has different naming
 #  conventions.

 if3name=
 if3addr=gate2-$HOSTNAME

 if4name=
 if4addr=gate3-$HOSTNAME

Edit /etc/hosts to include IP numbers for OPS1 and OPS2. Use test numbers that are not in use on the customer's network. For example:

 127.0.0.1       localhost
 #
 # This network number, '192.0.2' is the officially blessed 'test' network.
 #      It should be changed immediately to your own official network number.
 
 # start of well known machines--do not remove this line
 # main ethernet network
 192.26.79.38    ops1
 192.26.79.39    ops2
 # for DLM FDDI connection only
 192.0.2.200     dlm-ops1
 192.0.2.201     dlm-ops2
 #

Finish configuring the new FDDI station, as explained in Chapter 2 of the FDDIXpress Administration Guide. If you are familiar with the procedures, follow the section "Quick and Easy Configuration Instructions" in that chapter.

Verify the FDDI connection, as explained in Chapter 2 of the FDDIXpress Administration Guide.

Have ready the two remaining SCSI cables and the two 20-foot SCSI cables included in the Challenge RAID shipment (p/n 9290111).

Using blank labels from a label sheet, create two labels that say DF SCSI n and two labels that say DF SCSI N, where n and N are the numbers of two remaining SCSI controllers on the servers (in the example in Figure 2-3, these are 6 and 7).

Attach the two even-numbered labels below the SCSI A in symbol and SCSI A out symbol silk-screens on the Challenge RAID storage system. Attach the two odd-numbered labels below the SCSI B in symbol and SCSI B out symbol on the Challenge RAID storage system. Figure 2-8 shows the Challenge RAID SCSI ports.

Figure 2-8. SCSI–2 Bus Connectors on Back of Challenge RAID Chassis

On the back of the Challenge RAID storage system, attach a SCSI cable to the Challenge RAID SCSI A in port. Connect the SCSI cable to the SCSI A in connector as shown in Figure 2-9, making sure the connector is inserted securely.

Figure 2-9. Connecting a SCSI Bus Cable to a Challenge RAID SCSI Port

Connect the other end of this cable to the even-numbered SCSI bus on OPS1, as shown in Figure 2-10.

Figure 2-10. Connecting a Challenge RAID SCSI Bus Cable to a Challenge SCSI Port

Continue cabling as diagrammed in Figure 2-11.

Figure 2-11. Challenge RAID OPS Connection Schemes

Figure 2-12 shows a typical hookup for an OPS configuration with one Challenge RAID storage system.

Figure 2-12. Connecting SCSI Cables to a Challenge RAID and Both OPS Hosts

Have ready the contents of the IRISconsole multiplexer kit and the pair of cables included in the cable kit, so that you have four 2-ft DB25-DB9 serial cables (p/n018-0527-001).

Connect one end of the SCSI cable (018-0526-001) included in the multiplexer kit to the workstation's SCSI port, as shown in Figure 2-13, Figure 2-14, and Figure 2-15.

Figure 2-13. Cabling the Multiplexer to an Indy Workstation

Figure 2-14. Connecting the Multiplexer's SCSI Cable to an Indigo Workstation

Figure 2-15. Connecting the Multiplexer's SCSI Cable to an Indigo² Workstation

Attach the other end of the cable to the leftmost socket on the back of the multiplexer, as shown in Figure 2-13.

If the customer has purchased two multiplexers, attach the cable of the second multiplexer to the middle socket on the first multiplexer.

Cable the power supply to the rightmost port on the multiplexer, as shown in Figure 2-13.

Select an appropriate SCSI ID number by inserting a small screwdriver or other tool and rotating the arrow, as shown in Figure 2-16. Using SCSI ID 7 on early models of the multiplexer causes the power indication LED to blink. Select another ID and the LED glows steadily with no blink.

---

Note: The system disk in the Indigo workstation is always SCSI target ID 1 (on the Indy and Indigo2, ID 1 is the default). Never select SCSI ID 1 for a multiplexer.

---

Figure 2-16. Setting the Multiplexer SCSI ID

If the multiplexer is the last SCSI device on the workstation's standard external SCSI port, terminate it properly by attaching the external SCSI terminator included in the multiplexer shipment. See Figure 2-13.

Reboot the workstation.

Attach a 25-pin end of a serial cable to serial port 1 (or another port, as the customer wishes) on the top of the multiplexer.

Connect the 9-pin connector from serial port 1 on the multiplexer to the connector labeled System Console tty_1 on the I/O panel of the first OPS host (OPS1), as shown in Figure 2-17.

Figure 2-17. Cabling the OPS Host Remote System Control Connector

Attach a 25-pin end of a serial cable to serial port 2 (or another port, as the customer wishes) on the top of the multiplexer. Connect the other end of this cable to the Remote Sys Control SSE Use Only connector, which is to the right of the I/O panel on the first OPS host, as shown in Figure 2-18.

Figure 2-18. Cabling the OPS Host System Console Connector

Figure 2-19 shows cabling for a Challenge XL.

Figure 2-19. Multiplexer Cabling for Challenge XL

Repeat steps 1 through 3 for the second OPS host: attach serial cables from ports 3 and 4 on the multiplexer to the OPS2's System Console tty_1 and Remote Sys Control SSE Use Only ports, respectively.

Figure 2-20 diagrams IRISconsole multiplexer cables.

Figure 2-20. IRISconsole Cabling for OPS

---

Note: Do not use the 8-pin powered serial connector in systems that have the IRISconsole multiplexer installed.

---

Make sure that the Challenge RAID power switch is off.

Connect the power cord to the storage system. Plug the other end of the power cord into an AC power outlet. See Figure 2-21.

Figure 2-21. Connecting the Power Cord (Back of Challenge RAID Storage System)

Turn on the storage system's power. The green power light on the front of the Challenge RAID storage system comes on, and the fans rotate. See Figure 2-22.

Figure 2-22. Turning On the Storage System Power

If the busy light on none of the drive modules lights up, make sure that the power for each storage-control processor is enabled. Move the fan module's latch to the UNLOCK position, as indicated in Figure 2-23.

Figure 2-23. Unlocking the Fan Module

Swing open the fan module and move the power switch for each disabled storage-control processor to the enable position, as shown in Figure 2-24.

Figure 2-24. Enabling a Storage-Control Processor's Power

Swing the fan module closed, and then move the latch to the LOCK position.

---

Caution: Do not leave the fan module open for more than two minutes at any time. The Challenge RAID storage system shuts down if the fan module is disabled for more than two minutes.

---

If necessary, connect the power cables and power on the OPS hosts, the Challenge RAID, the workstation, and the multiplexer.