On This Page
Make sure that your client is connected physically and logically to the server(s)
The PreBoot drivers' images are already programmed on the adapter card
For InfiniBand ports only: Start the Subnet Manager
Configure and start the DHCP server
Configure and start at least one of the services such as: iSCSI, tftp, http
Boot the client machine and enter BIOS setup to configure "MLNX FlexBoot" to be the first on the boot device priority list.
On dual-port ConnectX-3 network adapters, the client first attempts to boot from Port 1. If this fails, it switches to boot from Port 2. Note also that the driver waits up to 10 seconds for port come up and up to 90 seconds to assign an IP from the DHCP server.
If a PreBoot driver was selected through BIOS setup, the client will boot from FlexBoot. The client will display FlexBoot attributes, sense the port protocol (In ConnectX-3 cards only) – Ethernet or InfiniBand. The port sensing occurs only when the port is connected to a QSFP connector. In case of an InfiniBand port, the client will also wait for port configuration by the Subnet Manager. If auto-sensing protocol fails, the port will be configured as an InfiniBand port.
After configuring the IB/ETH port, the client attempts to connect to the DHCP server to obtain an IP address and the source location of the kernel/OS to boot from. Next, FlexBoot attempts to boot as directed by the DHCP server.
For instructions on booting to ESXi, refer to the ESXi Installation Guide on VMWare site: http://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.upgrade.doc/GUID-B9DB94CA-4857-458B-B6F1-6A688726AED0.html
After performing basic HTTP configuration, add the following lines to the dhcp server configuration file:
hardware ethernet F4:
kernel -n vmlinuz http: