User Manual

Rev 2.0-3.0.0
Mellanox Technologies
208
Placing Client Identifiers in /etc/dhcpd.conf
The following is an excerpt of a
/etc/dhcpd.conf example file showing the format of represent-
ing a client machine for the DHCP server.
A.4 Subnet Manager – OpenSM
FlexBoot requires a Subnet Manager to be running on one of the machines in the IB network.
OpenSM is part of the Mellanox OFED for Linux software package and can be used to accom-
plish this. Note that OpenSM may be run on the same host running the DHCP server but it is not
mandatory. For details on OpenSM, see “OpenSM – Subnet Manager” on page 121.
A.5 TFTP Server
When you set the ‘filename’ parameter in your DHCP configuration file to a non-empty file-
name, the client will ask for this file to be passed through TFTP. For this reason you need to
install a TFTP server.
A.6 BIOS Configuration
The expansion ROM image presents itself to the BIOS as a boot device. As a result, the BIOS
will add to the list of boot devices “MLNX FlexBoot <ver>” for a ConnectX device. The priority
of this list can be modified through BIOS setup.
host host1 {
next-server 11.4.3.7;
filename "pxelinux.0";
fixed-address 11.4.3.130;
option dhcp-client-identifier =
ff:00:00:00:00:00:02:00:00:02:c9:00:00:02:c9:03:00:00:10:39;
}
This section applies to ports configured as InfiniBand only.
To use OpenSM caching for large InfiniBand clusters (> 100 nodes), it is recommended
to use the OpenSM options described in
Section 8.2.1, “opensm Syntax”, on
page 121
.