Make sure the system disk drives are setup for Windows. Windows 2008 R2 Datacenter, when booted from EFI, should allow you to manage the disks without any external help. Each disk must have a proper GPT label. If the disks have msdos labels, see Chapter 2, “Disk Preparation for Windows”.

If you run into problems, you may have to wipe out the master boot record (MBR), create a new msdos disk label, create a 100 MB system partition and a second boot/system partition (greater than or equal to 46 GB). Then format those targeted to Windows as new technology file system (NTFS). For more information, see “Disk Setup with Linux” in Chapter 2.

Attach a USB keyboard, USB mouse, and VGA monitor to the BaseIO blade (see Figure 1-1 and Figure 1-2).

---

Note: You can also use the display/keyboard and media redirection feature of the BaseIO BMC firmware (BMC firmware versions 1.2.2 or later). See “Enabling a Remote Console”.

---

Figure 1-1. Altix UV 1000 Individual Rack Unit (IRU)

Figure 1-2. Altix UV 1000 BaseIO Riser Enabled Blade Front Panel Example

Figure 1-3. Altix UV 100 Individual Rack Unit (IRU)

Attach USB DVD-ROM drive if needed (see Figure 1-2 ), and insert Windows Server 2008 R2 Datacenter DVD. For the location of the Altix UV 100 DVD drive, see Figure 1-3.

Use the ssh command to connect to the Chassis Management Controller (CMC), similar to the following example:

---

Note: This assumes the system CMC SMN port is connected and an address is assigned. For more information, see Chapter 2 in the SGI Altix UV CMC Controller Software User's Guide.

---

% ssh root@hostname-cmc

SGI Chassis Manager Controller, Firmware Rev. 1.3.11

system-cmc CMC:r001i01c>

Use the hwcfg command on the console to disable NUMAlink, as follows:

system-cmc CMC:r001i01c>hwcfg nl5_enable=no

From the CMC, perform a power reset, as follows:

system-cmc CMC:r001i01c>power reset

When prompted on the console, hit the space bar for the Boot Menu, as shown in Figure 1-4.

Figure 1-4. Console Prompt for Boot Menu Screen

From the boot manager screen, select Device Manager, as shown in Figure 1-5.

Figure 1-5. Device Manager Screen

Navigate the Device Manager, as follows:

From the Device Manager screen, as shown in Figure 1-6, select Advanced.

Figure 1-6. Device Manager Advanced Option Screen

From the Advanced screen, select SGI Custom Configuration, as shown in Figure 1-7.

Figure 1-7. SGI Custom Configuration Option Example

From the Advanced screen, as shown in Figure 1-8, perform the following:

Figure 1-8. Advanced Screen APIC Mode Option

You can either boot to the EFI shell and run \efi\boot\bootx64 or enter the boot menus and use the Boot Manager to select the boot loader. Be sure to navigate into the DVD's file hierarchy to find the Windows boot loader. Do not just boot from the DVD at the top level or you will get a legacy boot and Windows will not be able to use X2APIC mode or access more than eight Nehalem-EX sockets (or four Westmere-EX sockets.) Note that the DVD may not be at fs0, depending on what other bootable partitions are available on other drives.

Once the install completes and Windows has booted (using a VGA monitor and attached keyboard and mouse on the Altix UV system), copy the downloaded hotfixes onto the system. Unzip each one to the desktop.

Reboot the system when prompted. The hotfix install completes after reboot. If the system appears to hang on reboot, after at least two minutes, reset the machine as follows:

system-cmc CMC:r001i01c>power reset

Reboot the system. When prompted on the console, perform the following:

Use the hwcfg command on the console to enable NUMAlink, as follows:

system-cmc CMC:r001i01c>hwcfg nl5_enable=yes

From the CMC perform a power reset, as follows:

system-cmc CMC:r001i01c>power reset

Boot into Windows. This should take about 10 minutes on a 128 processor, one TB memory Altix UV 100 system. A 256 core, 2TB Alitx UV 1000 system takes about 28 minutes to boot Windows. The disk activity LED on the Base I/O, just to the right of the SATA connector, should be flashing. This will be the only indication of activity for most of the wait time.

The SAC> command will show up on the serial console towards the end of the 10 minutes. It will take a few more minutes before the login screen appears on the VGA monitor. Windows will now take another 20 to 30 minutes, depending on the speed of the root filesystem, to discover new hardware and write their configuration to disk. It will prompt for reboot when complete. Reboot once more to complete the install.

Establish a network connection to the SMN, as follows:

# ssh -X sysco@uv-system-smn

From the SMN, launch the Mozilla Firefox web browser, as follows:

sysco@system-smn:~/hw>firefox -no-remote 2>dev/null &

Enter the IP address of the BaseIO node baseboard management controller (BMC), similar to the following:

http://192.168.1.200

To determine the IP address of the BaseIO node BMC, see “Determining the IP Address of the BaseIO BMC”.

The BaseIO node BMC login screen appears, as shown in Figure 1-10. Login as root with the password superuser.

Figure 1-10. BMC Login Screen

The System Information screen appears, as shown in Figure 1-11. Click on the Remote Control tab.

Figure 1-11. BMC System Information Screen

The Remote Control screen appears, as shown in Figure 1-12. Click on the Console Redirection button.

Figure 1-12. BMC Remote Control Screen

The Console Redirection screen appears, as shown in Figure 1-13. Click on the Launch Console button.

Figure 1-13. BMC Remote Control Console Redirection Screen

You may need to enable pop-ups for this address for the Firefox browser first. From the Preferences dialog box, allow access from the IP address of the BaseIO.

A Java application under Firefox will open. Select Execute Java Web Start file (default) from the pop-up menu, as shown in Figure 1-14. You can also click the checkbox to keep it from showing up later.

Figure 1-14. Select Execute Java Web Start file (default) Pop-up Menu

You will then get a screen about The web site's certificate cannot be verified. Do you want to continue? , as shown in Figure 1-15. Click the Yes button to continue. You can also click the checkbox to keep it from showing up later.

Figure 1-15. Web site Warning-Security Screen

You will then get a screen about The application's digital signature cannot be verified. Do you want to run the application?, as shown in Figure 1-16. Click the Run button to continue. You can also click the checkbox to keep it from showing up later.

Figure 1-16. Application Warning-Security Screen

The JViewer KVM redirection window appears with a Shell> prompt, as shown in Figure 1-17.

Figure 1-17. KVM JViewer Shell Prompt Screen

---

Note: You may need to expand the JViewer window in order to see the entire desktop of the system in the following steps.

---

From the Shell> prompt issue the following command, as shown in Figure 1-18:

Shell>fs0:\efi\boot\bootx64

Figure 1-18. Booting the Operating System from the JViewer Shell> Prompt Screen

Login to the CMC, as follows:

ssh root@hostname-cmc
SGI Chassis Manager Controller, Firmware Rev. 1.1.11

CMC:r1i1c>  

Run the iodcon command on the CMC to get to the BaseIO BMC' ibmc0, as follows:

uv14-cmc CMC:r001i01c> iodcon

The iodcon tool brings up an internal serial connection to the BaseIO BMC (it is serial, which is why you need to hit ENTER to see the prompt in the next step).

Press the Enter key to get the r001i01b00i> prompt

Run the ifconfig eth1 command to obtain the inet addr, as follows:

r001i01b00i> ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 08:00:69:15:C0:57
          inet addr:172.20.255.254  Bcast:172.20.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1508779 errors:204 dropped:28 overruns:0 frame:204
          TX packets:2262923 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:924130317 (881.3 MiB)  TX bytes:3017177156 (2.8 GiB)
          Interrupt:1

Enter CTRL-X to exit the console.

The output also displays the MAC address as the HWaddr. You can use this information to configure a known MAC to IP address/host name mapping in your DHCP server.

Establish a network connection to the SMN, as follows:

# ssh -X sysco@uv-system-smn

Perform the following command to find the IP address of the BaseIO BMC, as follows:

sysco@uv14-smn:~/hw> cmclist -a
sysco@uv14-smn:~/hw> cmclist -a
# File: /var/lib/dhcp/db/dhcpd.leases
# UID              IP Address
d \001\010\000i\025\300W 172.20.255.254
sysco@uv14-smn:~/hw>   

From the CMC, perform a power reset, as follows:

system-cmc CMC:r001i01c>power reset

When prompted on the console, hit the space bar for the Boot Menu, as shown in Figure 1-19.

Figure 1-19. Console Prompt for Boot Menu Screen

From the boot manager screen, select Device Manager, as shown in Figure 1-23.

Figure 1-20. Device Manager Screen

Navigate the Device Manager, as follows:

From the Device Manager screen, select Security, as shown in Figure 1-21.

Figure 1-21. Device Manager Screen Security Option

From the Security screen, select the Admin Password option, as shown in Figure 1-22.

Figure 1-22. Security Screen Admin Password Option

From the Security Admin Password screen, enter the new administrative password, as shown in Figure 1-23.

Figure 1-23. Security Screen for Setting Administrative Password

When you reboot the system, the console will be locked and you will be prompted for a password before the system finishes booting and the Shell> prompt appears, as shown in Figure 1-24.

Figure 1-24. Console Administrative Password Prompt

The console password can be deleted by clearing the EFI variables, as follows:

# power -c reset

You can change the console password in the same manner you originally set it. If you delete the password with the power -c reset command, you need to go back through the setup screens to set it again.