- No category
advertisement
2 Burning the Expansion ROM Image
12
2.1
2.1.1
2.1.2
Burning the Image on ConnectX® Family Devices
Prerequisites
Expansion ROM Image
The expansion ROM images can be compiled using the Mellanox FlexBoot code source available in the FlexBoot webpage on www.mellanox.com
.
For further information on how to compile the code source, please refer to the pxebuild.py file inside the code source.
Firmware Burning Tools
You need to install the Mellanox Firmware Tools (MFT) package (version 4.1.0 or later) in order to burn the PXE ROM image. To download MFT, see Firmware Tools under www.mellanox.com > Products > InfiniBand/VPI Drivers > Firmware Tools.
Burning the Expansion ROM Image
NOTE: On selected platforms when burning the UEFI ROM image on a particular device, the UEFI controls other devices of the same type, if such devices do not have
UEFI burned on them.
To burn the composite image, perform the following steps:
1. Obtain the MST device name. Run:
# mst start
The device name will be of the form:
mt<dev_id>_pci{_cr0|conf0}
.
1
2. Create and burn the composite image. Run: flint -d <mst device name> --allow_rom_change brom <expansion ROM image path>
NOTE: If the following error “-E- Burn ROM failed: Unsupported operation under Controlled/Secure FW, please retry with -no_fw_ctrl” appears during the burning rom process, use the following burn command instead: flint -d <mst device name> --allow_rom_change --no_fw_ctrl brom <expansion ROM image path>
FlexBoot Example on Linux:
flint -d /dev/mst/mt4119_pci_cr0 --allow_rom_change brom FlexBoot-
3.5.110_4119.mrom
FlexBoot Example on Windows:
flint -d mt4119_pci_cr0 --allow_rom_change brom FlexBoot-
3.5.110_4119.mrom
1
Depending on the OS, the device name may be superseded with a prefix.
Mellanox Technologies Rev 3.0
2.2
UEFI Example on Linux:
flint -d /dev/mst/mt4119_pci_cr0 --allow_rom_change brom
14_12_24_RELEASE_0x1017.efirom
UEFI Example on Windows:
flint -d mt4119_pci_cr0 --allow_rom_change brom
14_12_24_RELEASE_0x1017.efirom
Removing the Expansion ROM Image
Remove the expansion ROM image. Run: flint -d <mst device name> drom
NOTE: When removing the expansion ROM image, you also remove PreBoot drivers from the boot device list.
Rev 3.0 Mellanox Technologies 13
advertisement
Related manuals
advertisement
Table of contents
- 11 1 Mellanox PreBoot Drivers (FlexBoot & UEFI)
- 11 1.1 Overview
- 11 1.2 Supported Mellanox Adapter Devices and Firmware
- 12 2 Burning the Expansion ROM Image
- 12 2.1 Burning the Image on ConnectX® Family Devices
- 12 2.1.1 Prerequisites
- 12 2.1.2 Burning the Expansion ROM Image
- 13 2.2 Removing the Expansion ROM Image
- 14 3 Preparing the DHCP Server in Linux
- 14 3.1 Case I: InfiniBand Ports
- 14 3.1.1 Installing DHCP
- 14 3.1.2 Configuring the DHCP Server
- 14 3.1.2.1 For ConnectX Family Devices
- 15 3.1.2.2 Extracting the Port GUID – Method I
- 15 3.1.2.3 Extracting the Port GUID – Method II
- 15 3.1.2.4 Placing Client Identifiers in /etc/dhcpd.conf
- 15 3.1.3 Running the DHCP Server
- 16 3.1.4 Adding Device Driver Support in Linux Kernels/Initrd
- 16 3.2 Case II: Ethernet Ports
- 16 3.2.1 Extracting the MAC Address – Method I
- 16 3.2.2 Extracting the MAC Address – Method II – FlexBoot Only
- 17 3.2.3 Extracting the MAC Address – Method III
- 17 3.2.4 Placing MAC Addresses in /etc/dhcpd.conf
- 18 4 Subnet Manager – OpenSM
- 19 5 BIOS Configuration
- 19 5.1 FlexBoot (Legacy BIOS Mode)
- 19 5.2 UEFI (UEFI BIOS Mode)
- 20 6 Flexboot User Interface
- 20 6.1 Skipping FlexBoot, FlexBoot User Interface and FlexBoot Port
- 20 6.2 Invoking the User Interface
- 20 6.2.1 Browsing the User Interface Menu
- 21 6.2.2 Accessing FlexBoot Sub Menus
- 21 6.3 Configuring System Settings
- 21 6.3.1 Editing the Parameters using Free Text
- 22 6.3.2 Editing the Parameters using Set Values
- 22 6.3.3 Deleting Configurable Settings
- 22 6.3.4 Restoring Default Configurations
- 23 6.4 Exiting FlexBoot User Interface
- 24 7 FlexBoot System Settings Configuration Options
- 24 7.1 System Setup
- 25 7.1.1 Diagnostic
- 25 7.1.1.1 boot_to_shell
- 26 7.1.1.2 panic_behavior
- 26 7.1.2 Bus:Device:Function
- 26 7.1.3 Chip Type
- 26 7.1.4 Device Name
- 26 7.1.5 PCI Device ID
- 26 7.1.6 Banner Menu Timeout
- 27 7.1.7 Virtualization Mode
- 27 7.1.8 Number of Virtual Functions
- 28 7.2 Power Configuration
- 28 7.2.1 Advanced Power Settings
- 28 7.2.2 Disable Slot Power Limiter
- 29 7.3 Firmware Image Properties
- 29 7.3.1 Flexboot Version
- 29 7.3.2 Family Firmware Version
- 30 7.4 Main Configuration
- 30 7.4.1 Blink LEDs
- 31 7.4.2 MAC Address
- 31 7.5 NIC Configuration
- 31 7.5.1 Ethernet NIC Configuration
- 31 7.5.1.1 Legacy Boot Protocol
- 32 7.5.1.2 IPv4/IPv6 support
- 32 7.5.1.3 Boot Retry Count
- 32 7.5.1.4 Undi network wait timeout
- 33 7.5.1.5 Virtual LAN ID
- 33 7.5.1.6 Virtual LAN Mode
- 33 7.5.1.7 VPI link type
- 33 7.5.1.8 Wake on LAN
- 34 7.5.2 InfiniBand NIC Configuration
- 34 7.5.2.1 PKey Value
- 35 7.6 iSCSI General Parameters
- 35 7.6.1 DHCP IP
- 35 7.6.2 DHCP Parameters
- 36 7.6.3 IP Version
- 36 7.6.4 CHAP Authentication
- 36 7.6.5 CHAP Mutual Authentication
- 36 7.6.6 Boot to target
- 37 7.7 iSCSI Initiator Parameters
- 37 7.7.1 CHAP ID
- 38 7.7.2 CHAP Secret
- 38 7.7.3 IPv4 Address
- 38 7.7.4 IPv4 Primary DNS
- 38 7.7.5 IPv4 Default Gateway
- 39 7.7.6 iSCSI Name
- 39 7.7.7 Subnet Mask
- 40 7.8 iSCSI First Target Parameters
- 40 7.8.1 Boot LUN
- 41 7.8.2 Connect
- 41 7.8.3 iSCSI Name
- 41 7.8.4 CHAP ID
- 41 7.8.5 CHAP Secret
- 42 7.8.6 IP Address
- 42 7.8.7 TCP Port
- 43 8 HII System Settings Configuration Options
- 43 8.1 Main Configuration Page
- 43 8.1.1 Blink LEDs
- 44 8.1.2 Device Name
- 44 8.1.3 Chip Type
- 44 8.1.4 PCI Device ID
- 44 8.1.5 PCI Address
- 44 8.1.6 Link Status
- 44 8.1.7 Network Link Type
- 45 8.1.8 MAC Address
- 45 8.1.9 Virtual MAC Address
- 45 8.2 Firmware Image Properties
- 46 8.2.1 Family Firmware Version
- 46 8.2.2 EFI Version
- 46 8.3 NIC Configuration
- 46 8.3.1 Banner Message Timeout
- 47 8.3.2 Legacy Boot Protocol
- 47 8.3.3 Virtual LAN Mode
- 47 8.3.4 Virtual LAN ID
- 47 8.3.5 PKey
- 48 8.3.6 Link Speed
- 48 8.3.7 Boot Retry Count
- 48 8.3.8 Wake on LAN
- 49 8.4 Device Level Configuration
- 49 8.4.1 Virtualization Mode
- 49 8.4.2 PCI Virtual Functions Advertised
- 50 8.5 iSCSI General Parameters
- 50 8.5.1 Boot to Target
- 50 8.5.2 TCP/IP Parameters via DHCP
- 51 8.5.3 iSCSI Parameters via DHCP
- 51 8.5.4 CHAP Authentication
- 51 8.5.5 CHAP Mutual Authentication
- 51 8.5.6 IP Version
- 52 8.6 iSCSI Initiator Parameters
- 52 8.6.1 CHAP ID
- 52 8.6.2 CHAP Secret
- 53 8.6.3 IPv4 Address
- 53 8.6.4 IPv4 Primary DNS
- 53 8.6.5 IPv4 Default Gateway
- 54 8.6.6 iSCSI Name
- 54 8.6.7 Subnet Mask
- 55 8.7 iSCSI First Target Parameters
- 55 8.7.1 Boot LUN
- 56 8.7.2 Connect
- 56 8.7.3 iSCSI Name
- 56 8.7.4 CHAP ID
- 56 8.7.5 CHAP Secret
- 57 8.7.6 IP Address
- 57 8.7.7 TCP Port
- 58 8.8 Power Configuration
- 58 8.8.1 Advanced Power Settings
- 58 8.8.2 Disable Slot Power Limiter
- 59 9 How to Boot
- 59 9.1 PXE Boot
- 59 9.1.1 Prerequisites
- 59 9.1.2 Starting Boot
- 60 9.1.3 How to Boot to ESXi
- 60 9.1.4 How to Boot Using HTTP and iPXE Script
- 60 9.2 iSCSI
- 60 9.2.1 Installing to iSCSI Target
- 61 9.2.2 Configuring an iSCSI Target in Linux Environment
- 61 9.2.2.1 Prerequisites
- 61 9.2.2.2 Configuring the DHCP Server to Boot From an iSCSI Target
- 62 9.3 Booting from FlexBoot via IPv6
- 63 9.4 Legacy Boot Priority Behavior
- 63 9.4.1 Legacy Boot Protocol PXE
- 64 9.4.2 Legacy Boot Protocol iSCSI
- 64 9.4.3 CHAP Authentication and CHAP Mutual Authentication
- 65 10 UEFI PXE Boot
- 66 Appendix A: Diskless Machines
- 66 A.1 Case I: InfiniBand Ports
- 67 A.1.1 Example: Adding an IB Driver to initrd (Linux)
- 67 A.1.1.1 Prerequisites
- 67 A.1.1.2 Adding the IB Driver to the initrd File
- 69 A.2
- 69 A.2.1
- 69 A.2.1.1
- 69 A.2.1.2