Redstorm:Harness boot

From OSR

Booting Harness Nodes

These are also done on rscsmw2 and should be done for every reboot. You should try to minimize the number of full power cycles that you do on the cage. Some of the nodes don't seem to come up reliabily, so we don't power cycle unless things really get wedged. These steps should be sufficient to get the nodes back into a sane state most of the time. Sometimes it doesn't work, in which case you will need to do the full reboot as described above.

Whole cage boots

• Init the entire cage:

               rs_init cx24y2c0

• Boot all the qk nodes. The new `coldstart` is very verbose and will generate reams of noise that you probably don't care about.

               rs_boot --qk cx24y2c0

• Boot the linux node. Unlike the `--qk` boot, this will give you the console for the Linux node as it boots. Once you see the final startup messages (`Starting SSHD`) it is safe to hit ^C to kill the boot process. If you don't kill it, eventually it will die on its own, but there will be an orphan `bootlinux` process out there that will continue to write the console to this terminal.

               rs_boot --l n0.cx24y2

• Login to the service node:

               ssh root@rsclogin108

Single node boots

If you crash a node it is possible to reboot that one module and have it rejoin th mesh. Each module has four nodes on it, so re-initing the node will take the other three down as well. If you are just doing one node tests then it is not necessary to bring them all back up.

               rs_init n4.cx24y2
               rs_boot --qk n{4,5,6,7}.cx24y2