AN!Wiki :: How To :: Configuring Network Boot on Fujitsu Primergy |
Note: This mini-tutorial was written as a compendium to the Anvil! m2 Tutorial. |
This tutorial will show you how to boot a Fujitsu server off of a PXE server, as is often done when using a Striker dashboard as an install target.
Note: to ensure your product has the latest security updates and operates at optimal performance, it is recommended you update your product to the latest firmware after installation and to periodically check for new firmware releases. Updates can be found by searching your model name at or though the mydlink mobile applications for mydlink registered devices.
Contents
|
- Realtek driver for RTL8168E/8111E and Windows 7 64bit. A complete list of available network device drivers for Realtek RTL8168E/8111E. On this page, you will find all available drivers listed by release date for the Windows 7 64bit operating system. From the following list, select any driver and try it on your device.
- Download Nvidia Network Card drivers, firmware, bios, tools, utilities. Latest downloads from Nvidia in Network Card. Sort by: last update. NVIDIA nForce Networking Controller Driver 67.6.2.0 for Vista/Windows 7 64-bit 3,421 downloads. Network Card Nvidia.
Note: There may be slight variations in the appearance and layout of your BIOS, though you should have no trouble finding what you need. |
When you first power on a Fujitsu Primergy server, it will take a minute or so for anything to show on the screen. This is normal, particularly after AC was disconnected.
When it does show the first screen, you will see a prompt to press <F2> to enter the BIOS.
Press <F2> and then wait.
The machine will continue to boot, scanning the RAID controller in the process. Once done, it will enter the BIOS scree.
The first page you will see is the Main BIOS page.
Enabling 'PXE' (Network) Booting
Most Anvil! systems use three separate dual-port network cards. The first two ports are usually built into the server and the other two are add-in cards.
If you aren't sure which is which, you can simply enable all of them as bootable cards.
The goal of this tutorial is to make life easy, if not efficient, so we will cover how to enable all interfaces as bootable devices.
Enabling Booting from onboard NICs
Note: To navigate the BIOS pages, use your left and right arrow keys. One you are on the page you want, press the up and down keys to moved between the items. Press '<enter>' to edit an item's value. |
Press the 'right' arrow key to switch to the 'Advanced' page.
Press the 'down' key to highlight 'Onboard Devices Configuration' and press '<enter>'.
You will an option to enable or disable the onboard LAN (network) interfaces followed by an option to set if each is bootable and, if so, using what protocol.
Select each 'LAN X Oprom' that is not set to 'PXE', press '<enter>' and select the 'PXE' option. Press '<enter>' again to make the change.
Some trivia;
- Oprom is short for 'Option ROM' (itself an acronym for 'Read Only Memory) and is used by the hardware to determine where to look for bootable devices.
- iSCSI is a way to use raw storage from a device on the network as if it was a local hard drive. Setting a NIC to 'iSCSI' boot mode tells the system to reach out over the network to find its 'hard drive' to boot from.
Now we can select either onboard interface to boot off of!
Note: It's outside the scope of this tutorial, but if you have hardware RAID and no optical drive, you can disable the onboard SATA to reduce boot times. |
Now to save and exit.
Press the '<esc>' key to return to the 'Advanced' page and then use the right arrow key to navigate to the 'Save and Edit' page. Select 'Save changes and Reset' and press '<enter>'.
Enabling booting from add-in NICs
Note: Most Anvil! systems use one of the onboard NICs for the connection to the Back-Channel Network, which is what we will use to boot the node off of the Striker dashboard. So for most people, this section is not needed. |
If you want to enable booting off of add-in network cards, you will need to tell the BIOS to look at them during boot.
To do this, you need to know which PCIe slot the add-in card is plugged into. Depending on your hardware server model, this should either be stamped into the metal near each expansion slot and/or shown on a label inside the server itself.
Once you know which PCIe slots your add-in network cards are in, you're ready to enable them!
Boot the computer and press <F2> to go back into the BIOS as before.
Navigate to the 'Advanced' menu and go down to the 'Option ROM Configuration' item and press '<enter>'.
Change the 'Launch Slot X OpROM' to 'Enabled' for the slots with NICs installed in them.
Once done, as above, press '<esc>' to return to the 'Advanced' menu, then use the arrow keys to go to the 'Save and Exit' page and then choose the 'Save changes and Reset' option.
Booting from the network
Note: The screen prompting for you to press '<F12>' to select boot might pass quickly. You can start pressing '<F12>' before seeing the prompt and it will still provide the boot selection menu. |
Download foxcon driver. During the boot of the machine, you will see a prompt to press '<F12>' to 'enter Boot Menu'.
Drivers Fsc Network & Wireless Cards Login
Press '<F12>' and then wait. The machine needs to scan a few things, like the RAID controller, before the boot device selection window appears.
And there you have it!
In some cases, the add-in Intel-based cards have their PXE booting disabled. In these cases, simply enabling the OpROM in the BIOS is not enough to enable PXE booting.
If, after following the earlier steps. you still don't see your Add-In cards as bootable options when you press <F12>, you will need to enable the controller's boot firmware.
Note: This next process requires RHEL or CentOS be installed. If you do not have an OS yet, please use a USB DVD drive to install EL6 64-bit traditionally. |
Downloading the Intel BootUtil
We are going to need to use a tool from Intel called BootUtil to change the controller's firmware.
Visit the Intel Boot Agent download page and then click on 'Download Intel Ethernet Flash Firmware Utility' and then click on 'Preboot.tar.gz'. Agree to the EULA and then save the file.
Copy the Preboot.tar.gz file to your node.
Go to the directory you saved it to on the node and extract it:
Now change into the APPS/BootUtil/Linux_x64/ directory.
By default, the utility is not executable, so the last step is to fix that. As the root user, run:
Done!
Using bootutil64e
First, let's look at the current installed adapters:
In this case, the first four interfaces on our two dual-port 10Gbps adapters. Note that the 'Flash Firmware' is listed as 'Disabled'? This tells up we need to update their configuration.
We want all to be PXE bootable, so we're going to run:
Note: Ignore the errors on ports 5 and 6, these are the onboard adapters and the command wasn't needed on them. |
Now reboot.
That's it!
When the node reboots, you should be able to see all adapters as PXE bootable when you press <F12> during the boot process.
From here, you can pick up what to do next back at the main tutorial:
Any questions, feedback, advice, complaints or meanderings are welcome. | ||||
Us: Alteeve's Niche! | Support: Mailing List | IRC: #clusterlabs on Freenode | © Alteeve's Niche! Inc. 1997-2019 | |
legal stuff: All info is provided 'As-Is'. Do not use anything here unless you are willing and able to take responsibility for your own actions. |
Drivers Fsc Network & Wireless Cards Printing
- Realtek PCIe GBE Family Controller (RTL8168)
- Realtek Gaming GBE Family Controller (RTL8118)
- Realtek PCIe FE Family Controller (RTL8136)
- Realtek PCIe 2.5GbE Family Controller (RTL8125)
- D-Link DGE-528T Gigabit Ethernet Adapter
- D-Link DGE-660TD Gigabit CardBus PC Card
- I-O DATA ETG-CB Gigabit Ethernet Adapter
- I-O DATA ETG-PCI Gigabit Ethernet Adapter
- LG System Interface(TV)
- Sitecom Gigabit-Ethernet PCI Adapter LN-027
- SMC EZ Card 10/100/1000(SMC9452TX-1)
- TP-Link Gigabit PCI Express Adapter
- ZyXEL GN680-T Gigabit PCI Adapter
- The driver is also designed for Abit, Acer, Acorp, Albatron, AMOI, Amtek, AOpen, Arima, Asrock, Asus, BENQ, BioStar, Buffalo, Chaintech, Channel, Clevo, Compal, DELL, DFI, ECS, EPoX, FIC, Foxconn, FSC, Gateway, Gigabyte, HP, Intel, Inventec, Jetway, Lenovo, LG, LiteOn, Mitac, MSI, NEC, Panasonic, Pegatron, Samsung, Sharp, TopStar, Toshiba, Twinhead, Uniwill, Wistron.
- Recomended for: RTL8101, RTL8101E, RTL8101HP, RTL8102E, RTL8103E, RTL8103EL, RTL8103EVL, RTL8105E, RTL8106E, RTL8106EUS, RTL8107E, RTL8112, RTL8112L, RTL8118, RTL8118AS, RTL8119, RTL8119i, RTL8125, RTL8131, RTL8136, RTL8136HP, RTL8167, RTL8168, RTL8168B, RTL8168C, RTL8168CP, RTL8168D, RTL8168DP, RTL8168E, RTL8168EP, RTL8168ES, RTL8168F, RTL8168FB, RTL8168FP, RTL8168FR, RTL8168G, RTL8168GA, RTL8168GR, RTL8168GU, RTL8168GUA, RTL8168H, RTL8169, RTL8401, RTL8402, RTL8411, RTL8411AAR, RTL8411B and RTL8411BA.