ITTC Machines Setup on 245E Rack machinesΒΆ

Note

You must use the terminal on the 245E rack to complete these instructions. Also, we currently have an a mano KVM setup so you will have to connect the terminal monitor, keyboard and mouse by hand to the machine you wish to configure.

  • Ensure that the network (PXE) boot option is first in your BIOS. If not, consult ITTC Help. This should be apparent as the ITTC Network Boot Menu should appear with the following boot options:

    +-----------------------------------------------+
    |            ITTC Network Boot Menu             |
    +-----------------------------------------------+
    | Main Menu                                     |
    | Memory Test                                   |
    | Memory Test 86+                               |
    | System Tools (restricted)                     |
    | Normal Boot (default)                         |
    |                                               |
    +-----------------------------------------------+
  • There is about a 10 second timeout, during which if you do not press any key on the keyboard the Normal Boot (default) option will boot the computer from the local disk. Make sure to type an arrow key or hit the space bar to stop the timeout.

  • From the ITTC Network Boot Menu choose the System Tools (restricted) boot option and press Enter.

  • There should now be a red password prompt in the middle of the screen labeled Password Required. Type the password that is taped to the bottom of the monitor for the rack terminal and press Enter.

  • This will unlock the new ITTC Sysadmin Menu which will give the following options:

    +-----------------------------------------------+
    |            ITTC Sysadmin Menu                 |
    +-----------------------------------------------+
    | Main Menu                                     |
    | Automatic (Destructive) Linux Installs        |
    | Manual Linux Installs                         |
    | Windows Install                               |
    | Diagnostic Tools                              |
    |                                               |
    +-----------------------------------------------+
  • From this menu choose the Automatic (Destructive) Linux Install and Enter.

  • Now you should have access to the Linux Installation Methods menu:

    +---------------------------------------------------+
    |            Linux Installation Methods             |
    +---------------------------------------------------+
    | Main Menu                                         |
    | Fedora 12 - Automatic Install - i386 (Testing)    |
    | Fedora 12 - Automatic Install - x86_64 (Testing)  |
    | Fedora 11 - Automatic Install - i386              |
    | Fedora 11 - Automatic Install - x86_64            |
    | Fedora 10 - Automatic Install - i386              |
    | Fedora 10 - Automatic Install - x86_64            |
    | Fedora 9 - Automatic Install - i386               |
    | Fedora 9 - Automatic Install - x86_64             |
    | Fedora 8 - Automatic Install - i386               |
    | Fedora 8 - Automatic Install - x86_64             |
    +---------------------------------------------------+
  • Generally you will want to install the most recent Fedora i386 OS. The most recent release is the highest numbered (in this case Fedora 12), as well as has the (Testing) tag to the right of the menu option.

  • Toggle/highlight the correct option (i.e. Fedora 12 - Automatic Install - i386 (Testing)) with the arrow keys and then press Tab so that you can modify the GRUB boot options.

  • Again, there will be a password prompt labeled Password Required. The password is the same as the password for the previous prompt, so type the password taped to the bottom of the 245E rack terminal monitor and press Enter.

  • This time you will not be taken to a new menu, instead there will be a place to edit the GRUB boot command for installation you chose at the bootom of the screen.:

         +---------------------------------------------------+
         |            ITTC Sysadmin Menu                     |
         +---------------------------------------------------+
         | Main Menu                                         |
         | Fedora 12 - Automatic Install - i386 (Testing)    |
         | Fedora 12 - Automatic Install - x86_64 (Testing)  |
         | Fedora 11 - Automatic Install - i386              |
         | Fedora 11 - Automatic Install - x86_64            |
         | Fedora 10 - Automatic Install - i386              |
         | Fedora 10 - Automatic Install - x86_64            |
         | Fedora 9 - Automatic Install - i386               |
         | Fedora 9 - Automatic Install - x86_64             |
         | Fedora 8 - Automatic Install - i386               |
         | Fedora 8 - Automatic Install - x86_64             |
         +---------------------------------------------------+
    
    > kickstart/fedora/12/i386/vmlinuz initrd=kickstart/fedora/12/i386/initrd.img
    noivp6 ks=http://kickstart.ittc.ku.edu/kickstart/base.ks method=http://kicksta
    rt.ittc.ku.edu/mirror/fedora/linux/releases/12/Fedora/i386/os console=tty0 loa
    d_ramdisk=1 ksdevice=link PROFILE=F12
  • You can ignore most of this, but you will need to change the ksdevice=link to ksdevice=eth1 this is required for historical reasons since Will Dinkle used to use most of the rack machines for networking experiments. Changing the ksdevice (Kick Start Device) changes the network interface through which the installation will happen. Without this change, the installation will promptly fail.

  • You can now press Enter and the installation will start. This will take approximately one hour to complete. This varies largely on both the machine and the current network traffic load at ITTC.

  • After the installation is complete the computer should reboot to a login console, no X display. At this time you will need to email help@ittc.ku.edu asking them to configure Puppet on the machine.

    Note

    Remember to give them the name of the machine in the email.

Previous topic

Remote Testbed Access

Next topic

General Net Console Instructions

This Page