Colo Server Setup

From JCWiki
Jump to navigation Jump to search

BIOS

You will want to adjust the following settings (where supported):

  • set the date and time to GMT
  • set the power loss option to last state (this ensures that if the DC loses power, the server will turn on when power is restored, and more importantly the same will happen when the ATS port is power cycled).
  • make sure USB is not disabled (to allow KVM ISO mount/boot)
  • optionally, disable ROM option for NICs so they don't waste time trying to pxe boot
  • adjust the boot order to boot first to HD/RAID. Note: if you're booting to KVM ISO you will have to reboot after the ISO is mounted before you see the Belkin device show up as a bootable device (which you can then move up in the boot order)

Install the OS

Refer to IPKVM for details on how to use it to do the install.

RAID setup (if equipped) After you exit the BIOS screen you will see the RAID (3ware) BIOS screen. To enter the configuration press Alt-3. There you will be able to create a new mirror from the drives provided. To do this, move the cursor to each drive and hit the spacebar to select each drive (should be *'d after selecting) then tab down to the menu at the bottom to Create Array. It should be a RAID1 (mirror) with write cache disabled (unless there is a backup battery). Use default options for all other settings. No need to give it a name. When done setting up the options, press F8 to save and exit.

Do a minimal install of whatever OS the customer has selected. Don't install packages beyond the basics (i.e. openssh)

It'll be a crapshoot which ethernet device (if there are multiple) is the active one. You basically have to guess and assign an IP to one and immediately after configuring it go ping it. If it's pinging, you guessed right. If not, you can either go back and give the IP to the other nic (this may not work since the other nic may still have the same IP) or you can ask the DC to swap the cat5 cable to the other port.

FreeBSD systems will require you to complete the OS load over ftp since the OS won't recognize the IPKVM's ISO as a CD drive (this despite the fact that it clearly booted to it initially). This is why we use "netboot" ISOs.