Do not panic and switch too hastily. Switching workstations makes a mess of the oven data by breaking image files into several pieces. If you make a mistake, the database files could also be damaged.
Pilot should definitely not be running oven on the other workstation (crater or dorado) at the same time. This is not impossible, but it is rather dangerous --- you could destroy the other database if you make a mistake.
Make sure the other workstation is functional before you get too involved in this process.
This is assuming that crater is not already dead. Try to kill the oven daemons if you can; otherwise they may continue to read the error messages.
Kill whatever is running on dorado; then follow the normal instructions in pilot_login or pilot_short. Be careful with the oven parameters because they might be set to "readonly". This login will possibly involve creating shared memory and possibly killing old daemons. Be careful not to load database from disk until step 4.
In the blue window on dorado, "copy database database_save" to make sure you don't lose the old database file when reading database from oven.
This should give you the latest database file with current clocks. Do NOT do this step unless you are sure that the problem was with crater and not with the on-board computers.
Usually we run the oven VxWorks software from EPROM. The EPROM version of the software can reboot without the Sun, and can get oven database information from other on-board computers or from non-volatile RAM. The typical boot setup looks like this:
> bootChange '.' = clear field; '-' = go to previous field; ^D = quit boot device : ln processor number : 0 host name : crater file name : /u/vxworks/oven0v1/vxWorks inet on ethernet (e) : 22.214.171.124:ffffff00 t (g) : user (u) : vwuser ftp password (pw) (blank = use rsh): flags (f) : 0x0 target name (tn) : oven0v1 startup script (s) : /u/vxworks/oven0v1/startup.cmd other (o) : value = 0 = 0x0
But, if you are using VxWorks which boots from disk, you will also need to change the boot parameters of the on-board computers before they can successfully reboot. To change the boot parameters, interrupt the auto-boot sequence and type "c" for change. If you are changing the network address of the VME computer, be sure to reboot it again and verify the name before connecting it to the network.
The typical network boot parameters look like:
-> bootChange '.' = clear field; '-' = go to previous field; ^D = quit boot device : ln processor number : 0 host name : dorado file name : /u/vxworks/oven1v0/vxWorks inet on ethernet (e) : 126.96.36.199:ffffff00 inet on backplane (b): 0 host inet (h) : 188.8.131.52 gateway inet (g) : user (u) : vwuser ftp password (pw) (blank = use rsh): flags (f) : 0x0 target name (tn) : oven1v0 startup script (s) : /u/vxworks/oven1v0/startup.cmd other (o) : value = 0 = 0x0
The relevant network computers are: (from /etc/hosts)
184.108.40.206 dorado.as.arizona.edu dorado 220.127.116.11 libra.as.arizona.edu libra 18.104.22.168 crater.as.arizona.edu crater 22.214.171.124 ncdxta12.as.arizona.edu ncdxta12 126.96.36.199 vw4.as.arizona.edu vw4 188.8.131.52 vw5.as.arizona.edu vw5 184.108.40.206 afone.as.arizona.edu afone 220.127.116.11 aftwo.as.arizona.edu aftwo 18.104.22.168 oven0v0.as.arizona.edu oven0v0 22.214.171.124 oven0v1.as.arizona.edu oven0v1 126.96.36.199 oven0v2.as.ari2.as.arizona.edu oven1v2 188.8.131.52 oven2v0.as.arizona.edu oven2v0 184.108.40.206 oven2v1.as.arizona.edu oven2v1 220.127.116.11 oven2v2.as.arizona.edu oven2v2 18.104.22.168 mlpc10.as.arizona.edu mlpc10 22.214.171.124 mlpc11.as.arizona.edu mlpc11