# Intel® Ethernet FCoE Boot

Intel® Ethernet FCoE Boot allows the user to install FCoE to boot an operating system from a remote target. The following information refers specifically to FCoE Boot. To then configure the OS go to: Windows or Linux.

Upgrading an FCoE-Booted System

Intel® Ethernet FCoE Boot Option Rom Setup

Microsoft* Windows* Setup for Intel® FCoE Boot

Installing Windows 2008 With Local Disk

Crash Dump Support

BootUtility

### Upgrading an FCoE-booted System

| NOTE: Upgrading from older versions of FCoE Boot is not supported.

### Intel® Ethernet FCoE Boot Option ROM Setup

#### FCoE Port Selection Menu

To configure Intel® Ethernet FCoE Boot, power-on or reset the system and press the Ctrl-D key combinationwhen the message "`Press <Ctrl-D> to run setup...`" is displayed. After pressing the Ctrl-D key combination, you will be taken to the Intel® Ethernet FCoE Boot Port Selection Setup Menu.

The first screen of the Intel® Ethernet FCoE Boot Setup Menu displays a list of Intel® FCoE Boot-capable adapters. For each adapter port, the associated SAN MAC address, PCI device ID, PCI bus/device/function location, and a field indicating FCoE Boot status is displayed. Up to 10 FCoE Boot-capable ports can be displayed within the Port Selection Menu. If there are more Intel® FCoE Boot-capable adapters, these are not listed in the setup menu.

Highlight the desired port and press Enter.

#### FCoE Boot Targets Configuration Menu

FCoE Boot Targets Configuration: Discover Targets is highlighted by default. If the Discover VLAN value displayed is not what you want, enter the correct value. H ighlight Discover Targets and then press Enter to show targets associated with the Discover VLAN value. Under Target WWPN, if you know the desired WWPN you can manually enter it or press Enter to display a list of previously discovered targets.

#### FCoE Target Selection Menu

Highlight the desired Target from the list and press Enter.

Manually fill in the LUN and Boot Order values.

> Boot Order valid values are 0-4, where 0 means no boot order or ignore the target. A 0 value also indicates that this port should not be used to connect to the target. Boot order values of 1-4 can only be assigned once to target(s) across all FCoE boot-enabled ports.

> VLAN value is 0 by default. You may do a Discover Targets which will display a VLAN. If the VLAN displayed is not the one you require, enter the VLAN manually and then perform Discover Targets on that VLAN.

Hit Save.

| NOTE: After the Discover Targets function is executed, the Option ROM will attempt to remain logged into the fabric until the FCoE Boot Targets Configuration Menu is exited.

- Keyboard Shortcuts: Up/Down, TAB and SHIFT-TAB to move between the controls. Left/Right/Home/End/Del/Backspace in the edit boxes.

- Press the Esc key to leave the screen.

### Intel® PROSet for Windows* Device Manager

Many of the functions of the Intel® FCoE Boot Port Selection Setup Menu can also be configured or revised using Intel® PROSet for Windows Device Manager. Click here for instructions on installing and using Intel® PROSet for Windows Device Manager.

- FCoE boot version is displayed on the Boot Options tab if the combo image supports FCoE boot.
- FCoE Boot is an Active Image option if FCoE boot is supported by the combo image.
- The Active Image setting enables/disables FCoE boot in the EEPROM.
- FCoE boot settings are displayed if FCoE Boot is the active image.

## Microsoft* Windows* Setup for Intel® FCoE Boot

| Warning: Upgrading base driver via Intel® Windows Device Manager will fail on Windows Server 2008 R2 or Windows Server 2008 R2 SP1 and a blue screen will result.

### Requirements

1. Follow installation steps to install the Intel® Ethernet FCoE Boot-capable adapters with Intel® Ethernet FCoE Boot firmware support.

2. Create a disk target (LUN) on an available Fibre Channel target. Configure this LUN to be accessible to the WWPN address of the initiator of the host being booted.

3. Make sure the FCoE initiator of the host system starts the Intel® Ethernet FCoE Boot firmware. The firmware should be configured properly, be able to connect to Fibre Channel target, and detect the boot disk.

4. To setup Windows Server* 2008 boot system when a local disk is available, follow the steps in installing Windows 2008 with Local Disk.

5. Obtain information on Crash Dump Support.

## Installing Windows 2008 with Local Disk

| Warning: Upgrading or uninstalling driver will cause blue screen Upgrading or uninstalling the network adapter driver via Windows Device Manager on the boot port will result in a lost connection to the SAN. The lost connection will result in a Windows blue screen on the next boot and will require the OS to be reinstalled.

After the Option Rom is installed, if you wish to install Windows 2008 with local disk, do the following:

1. Follow the instructions for installing Windows 2008 and the FCoE stack.

2. Verify that the FCoE boot disk is available in the Fabric View tab of Intel® PROSet for Windows Device Manager, and verify that you are online using Windows Disk Manager.

3. Open a command prompt, run the fcoeprep.bat batch file. To find the batch file, navigate to your architecture's directory within the \APPS\FCOEBOOT directory.

4. Shut Windows down and capture the OS image to a local disk partition.

5. Transfer the image from the local hard drive to the FCoE target. This may be done from within the local Windows installation.

6. For Windows 2008 R2 SP1 only: Run bcdboot.exe from the local Windows installation to make the FCoE disk bootable.

   - If a System Reserved partition exists on the FCoE disk, type: `bcdboot F:\Windows /s E:`
     where E: is the FCoE System Reserved partition and F: is the FCoE partition with the Windows directory.

   - If a System Reserved partition does not exist, type: `bcdboot E:\Windows /s E:`
     where E: is the FCoE partition with the Windows directory.

7. Shut down and remove the local disk.
8. Configure the system BIOS to boot from the FCoE disk and boot.

## Crash Dump Support

Crash dump file generation is supported in this release.

`Last modified on 4/06/11 10:31a Revision 39`