| |
Installing the ESI Supervisory Computer | |
The ESI Supervisory computer is a Sun Ultra-1 with 128 MB of RAM, a 17-inch color monitor, and a 2 GB internal SCSI disk. The internal SCSI disk is connected to SCSI controller 0, which is located on the motherboard and which also appears on the back-panel as a narrow SCSI connector. Also located on the motherboard is a 10-Mbs Ethernet interface (le0). In addition, the computer has an Sbus board containing both a fast-wide SCSI interface and a 10/100-Mbs auto-sensing TP ethernet interface (hme0).
The back-panel of the computer has connectors arranged roughly as follows:
RS-232_ttya
Sbus-Board
+-------------------------------+
Monitor_Conn RS-232_ttyb | RJ45(hme0) Wide_SCSI |
+-------------------------------+
AC_Plug Parallel_Port AUI RJ45(le0) Narrow_SCSI Microphone/Speaker_Jacks
The Supervisory computer also has a 3 x 9 GB hot-swappable Andataco disk drive 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
Esupv Esupv Esupv
Mirror Data Disk Boot Disk
Copy of
Boot Disk
The fast-wide SCSI interface on the Andataco disk enclosure connects to the fast-wide SCSI interface connector on the Sbus-board in the computer (i.e., to the connector labeled "Wide_SCSI" in the above drawing).
Currently, no external devices connect to the narrow SCSI interface connector on the back of the motherboard (i.e., to the connector labeled "Narrow_SCSI" in the above drawing).
1. Connect the fast-wide SCSI interface from the Andataco disk enclosure to
the fast-wide SCSI interface connector on the Sbus-board ("Wide_SCSI").
Use the enclosed fast-wide SCSI terminator to terminate the bus at the
disk drive enclosure. Make sure you attaching the external disk drive
enclosure that is labeled "esupv", and NOT the one labeled "esinst".
2. Connect the 17-inch monitor to the connector labeled "Monitor"
3. Connect the keyboard and mouse
4. Insert a TP ethernet "pacifier" into the RJ45 TP 10-Mbs ethernet connector
for the le0 interface located on the motherboard (and NOT into the RJ45
connector for the hme0 interface located on the Sbus board). There is
such a TP ethernet pacifier (a small grey male RJ45 connector that jumpers
the send lines to the receive lines) packed in a small plastic bag inside
the box containing the Supervisory computer CPU chassis.
NOTE: Failure to insert this TP ethernet pacifier will likely cause the
initial bootstrap to hang for a very long time with complaints
about the lack of carrier on the le0 interface.
NOTE: Do NOT connect the ESI Supervisory 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 monitor and the Andataco external disk drive enclosure,
and wait for the Andataco disks to complete their power up sequence.
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)
of the Andataco disk drive enclosure.
NOTE: The narrow SCSI interface found on the motherboard is SCSI
controller 0, while the fast-wide 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 that is
attached to the fast-wide SCSI interface on the Sbus board,
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
esupv.ucolick.org. Log in as root (using the esupv 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)
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 garbage (internal 2 GB data partition)
Please don't mess with these unmounted disk partitions at this time. In
particular, the internal 2 GB disk probably needs a reformat and newfs.
4. Logged in as root, update the following files:
/etc/hostname.le0: Change "esupv.ucolick.org" to
"koki.keck.hawaii.edu"
/etc/nodename: Change "esupv.ucolick.org" to
"koki.keck.hawaii.edu"
/etc/hosts: Confirm that it has the correct IP addresses
defined for koki. However, please do NOT
change any of the hostnames for the ESI
Private Network (192.168.5.x) at this time,
and please don't change the /etc/hostname.hme0
file.
/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 le0 interface. (Keep it handy, since you will need it for the initial bootstrapping of the ESI Instrument Computer.) 2. Connect the Keck-2 subnet (128.171.136.x) to the RJ45 connector for the le0 interface (i.e., the RJ45 connector on the motherboard). 3. Reboot the ESI Supervisory Computer from the default boot device by using the command "boot". 4. Hopefully, the ESI Supervisory Computer will now boot up as koki.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.
| Go To: | ||||
| Instruments Home Page | Keck Home Page | Observer's Reference Shelf | ||
ESI Master
8 February 2000