By default, the DHCP server looks for a configuration file called nf under /etc. In order for the DHCP server to provide configuration records for clients, an appropriate configuration file needs to be created. For the NVIDIA OFED for Linux package, it is recommended to have IPoIB use the same format that FlexBoot uses for this client identifier. The length of the client identifier field is not fixed in the specification. This client identifier field can be used to associate an IP address with a client identifier value, such that the DHCP server will grant the same IP address to any client that conveys this client identifier. To overcome this problem, DHCP over InfiniBand messages convey a client identifier field used to identify the DHCP session. Standard DHCP fields holding MAC addresses are not large enough to contain an IPoIB hardware address.
For further information, please see the REAME file available under the docs/dhcp/ directory. In other words, you need to make sure that IPoIB configuration files include the following line:Ī patch for DHCP may be required for supporting IPoIB. Setting an IPoIB interface configuration based on DHCP is performed similarly to the configuration of Ethernet interfaces. You can also apply a manual configuration that persists only until the next reboot or driver restart (see below). IPoIB configuration can be based on DHCP or on a static configuration that you need to supply (see below). The first port on the first HCA in the host is called interface ib0, the second port is called ib1, and so on. The configuration of IPoIB requires assigning an IP address and a subnet mask to each HCA port, like any other network adapter card (i.e., you need to prepare a file called ifcfg-ib for each port). Unless you have run the installation script mlnxofedinstall with the flag '-n', then IPoIB has not been configured by the installation. "mtu=5" indicates that all IPoIB ports in the fabric are using 4k MTU, ("mtu=4" indi- cates 2k MTU) IPoIB Configuration
0 kommentar(er)
