| |
Installing the ESI Instrument Computer | |
The ESI Instrument computer is a Sun Ultra-2 with 640 MB of RAM, two 20-inch color monitors, and two 4-GB internal SCSI disks. The internal SCSI disks are connected to SCSI controller 0, which is located on the motherboard and which also appears on the back-panel as the SCSI connector located directly underneath the connector for the first monitor (Monitor_1). Also located on the motherboard is a 10/100-Mbs auto-sensing TP Ethernet interface (hme0).
In addition, the computer has an Sbus board which contains both a fast-wide SCSI interface (which is SCSI controller 1) and a 10/100-Mbs auto-sensing TP ethernet interface (hme1) that will be used for the ESI Private Network. There is also a second Sbus board with a frame buffer for the second color monitor.
The back-panel of the computer has connectors arranged roughly as follows:
RS-232_ttya
FAN AC-
Plug RS-232_ttyb Sbus-Board
+-------------------------------+
Monitor_1 | RJ45 SCSI_Controller_1 |
| (hme1) |
+-------------------------------+
On/Off SCSI_Controller_0 <...> RJ45 KBD Parallel_Port Audio_Jacks
(hme0)
I forgot to record which Sbus slot contains the second frame buffer for the second color monitor, but it should be obvious since it will be the only Sbus board that has a Sun monitor connector on it.
The Instrument computer also has a 3 x 9-GB hot-swappable Andataco disk enclosure with a fast-wide SCSI interface. As viewed from the front of the enclosure, the three disks are as follows:
Target 0 Target 1 Target 2
Esinst Esinst Esinst
Mirror Data Disk Boot Disk
Copy of
Boot Disk
The fast-wide SCSI interface on the Andataco disk enclosure connects to the SCSI_Controller_1 interface connector on the Sbus-board in the computer. (Don't confuse the SCSI_Controller_1 connector, which is on the Sbus-board, with the SCSI_Controller_0 connector, which is on the motherboard and located under the connector for the first monitor, Monitor_1)
The Instrument computer also has an Exabyte tape drive which attaches to the connector for SCSI_Controller_0 (i.e., the connector located under the connector for Monitor_1). Thus, the Exabyte is on the same SCSI controller (SCSI_Controller_0) as the two 4-GB internal disk drives, while the external Andataco disk drive enclosure is on its own separate SCSI controller (SCSI_Controller_1).
1. Connect the fast-wide SCSI interface from the Andataco disk enclosure to the
fast-wide SCSI interface connector on the Sbus-board (SCSI_Controller_1).
Use the enclosed fast-wide SCSI terminator to terminate the bus at the
disk drive enclosure. Make sure you are attaching the external disk drive
enclosure that is labeled "esinst", and NOT the one labeled "esupv".
2. Connect the SCSI interface from the Exabyte tape drive to the SCSI interface
connector on the motherboard (SCSI_Controller_0). That connector is located
directly under the connector for Monitor_1. Use the enclosed SCSI
terminator to terminate the bus at the Exabyte.
3. Connect the first 20-inch monitor to the connector labeled "Monitor_1",
which is located directly under the RS-232 connector for terminal
/dev/ttyb. Then connect the second 20-inch monitor to the other monitor
connector located on the second Sbus board.
4. Connect the keyboard and mouse
5. Insert a TP ethernet "pacifier" into the RJ45 TP 10/100 Mbs ethernet
connector (for interface hme0) located on the motherboard and appearing
on the back-panel just to the left of the connector for the keyboard.
There is such a pacifier (a small grey male RJ45 connector that jumpers
the send lines to the receive lines) packed in a small plastic bag inside
the shipping box containing the ESI Supervisory computer CPU chassis.
Failure to insert this pacifier will likely cause the initial bootstrap
to hang for a very long time, complaining about the lack of carrier on
the hme0 interface.
NOTE: do not connect the ESI Instrument computer to the Keck Observatory
ethernet at this time, since the computer still has its Santa Cruz
IP address and hostname.
1. Power up the monitors, the Exabyte tape drive, and the Andataco external
disk drive enclosure. Then wait for the Exabyte and the Andataco disks to
complete their power up sequence (the Exabyte can take a minute or two).
2. Power up the CPU. The system should now boot from the target 2 boot
disk (the rightmost disk as viewed from the front of the enclosure)
in the Andataco disk drive enclosure.
NOTE: The SCSI interface found on the motherboard is SCSI controller 0,
while the SCSI interface provided by the Sbus board is SCSI
controller 1. Thus, since we boot from the target 2 disk of the
external disk drive enclosure which is connected to SCSI controller 1,
the default boot partition when the system is powered up is
controller 1, target 2, disk 0, partition 0
(i.e., /dev/rdsk/c1t2d0s0).
3. Once the system finishes booting, the computer should come up as
esinst.ucolick.org. Log in as root (using the esinst root password that
Kibrick supplied to Jon Chock via telephone on July 26) and verify that
the following disk partitions have successfully mounted:
/dev/rdsk/c1t2d0s0 / (external root partition)
/dev/rdsk/c1t2d0s6 /u (external user files)
/dev/rdsk/c1t1d0s2 /data1 (external 9 GB data partition)
/dev/rdsk/c0t1d0s2 /data2 (internal 4 GB data partition)
Note that the following disk partitions are NOT currently mounted, and
in general should not be mounted at this time:
/dev/rdsk/c1t0d0s0 /mirror (mirror copy of root partition)
/dev/rdsk/c1t0d0s6 /umirror (mirror copy of /u partition)
/dev/rdsk/c0t0d0s0 /old-root (obsolete Solaris 2.5 boot)
Please don't mess with these unmounted disk partitions at this time.
4. Logged in as root, update the following files:
/etc/hostname.hme0: Change "esinst.ucolick.org" to
"kanaha.keck.hawaii.edu"
/etc/nodename: Change "esinst.ucolick.org" to
"kanaha.keck.hawaii.edu"
/etc/hosts: Confirm that it has the correct IP addresses
defined for kanaha. However, please do NOT
change any of the hostnames for the ESI
Private Network (192.168.5.x) at this time.
/etc/resolv.conf: Update to reference the appropriate name
servers for keck
/etc/defaultdomain: Update with appropriate domain for Keck
/etc/nsswitch.conf: Update as necessary to enable Keck NIS service.
However, please insure that items that are
currently resolved first using "files"
continue to be resolved first using "files".
5. After verifying that the above listed files have been correctly updated,
shutdown the system.
1. Remove the TP ethernet pacifier from the RJ45 connector for the hme0 interface. Keep it handy, in case you need it for any further stand-alone booting. 2. Connect the Keck-2 subnet (128.171.136.x) to the RJ45 connector for the hme0 interface (i.e., the RJ45 connector on the motherboard from which you just removed the pacifier). 3. Reboot the ESI Instrument Computer from the default boot device by using the command "boot". 4. Hopefully, the ESI Instrument Computer will now boot up as kanaha.keck.hawaii.edu on the Keck-2 subnet. 5. Once you reach this point, please give Kibrick a call in Santa Cruz so that he can log in remotely and check that everything looks in order.