welcome: please sign in

Diff for "RebootingMireSp"

Differences between revisions 2 and 6 (spanning 4 versions)
Revision 2 as of 2008-02-20 19:37:39
Size: 548
Editor: MichaelOlson
Comment: Mention krunk and minicom
Revision 6 as of 2010-01-21 13:12:06
Size: 508
Editor: dslb-092-074-055-194
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
= Reboot via Service Processor =
Line 4: Line 6:
ssh admin@69.90.123.71}}} ssh admin@mire-sp.hcoop.net}}}
Line 10: Line 12:
 1. Krunk will have halted, because its serial port is connected to mire, and it gets messed up when rebooting. Turn it back on again by logging into mire and doing the following. {{{
minicom -o
boot
<exit minicom>}}}

= Post-boot =

After boot, run '''sudo /etc/init.d/domtool-slave start''', as it seems that domtool-slave does not start up automatially.

This page explains how to reboot mire using the SP interface.

1. Reboot via Service Processor

  1. Log into the SP using ssh.

    ssh admin@mire-sp.hcoop.net
  2. Power off the "platform", which is the normal processor.

    platform set power state -f off
  3. Wait a few minutes.
  4. Power on the platform.

    platform set power state -f on

2. Post-boot

After boot, run sudo /etc/init.d/domtool-slave start, as it seems that domtool-slave does not start up automatially.

RebootingMireSp (last edited 2010-01-21 13:12:06 by dslb-092-074-055-194)