Configuring DHCP Server with Infiniband

Hal Rosenstock hal.rosenstock at gmail.com
Thu Apr 4 14:52:02 UTC 2013


On Thu, Apr 4, 2013 at 10:07 AM, Malek Musleh <malek.musleh at gmail.com>wrote:

> Hi Hal,
>
> Do you know where I can retrieve those patches?
>

They were sent to dhcp-bugs and dhcp-suggest. It was assigned bug #24249.
Not sure how to find them now. There was also one other subsequent bug fix
for a segfault found.


> It doesn't quite make sense why there IS some Infiniband support code,
> such as for parsing (parse.c) and token (con flax.c) in the code, but not
> all of it.
>
>
I don't have an explanation for that and forget whether that was the case
back 2 years ago.

-- Hal


>
>
>
> Reading the parts of the OFED documentation says this:
>
> >
> ===============================================================================
> > 3. IPoIB Configuration Based on DHCP
> >
> ===============================================================================
> >
> > Setting an IPoIB interface configuration based on DHCP (v3.0.4 which is
> > available via www.isc.org) is performed similarly to the configuration
> of
> > Ethernet interfaces. In other words, you need to make sure that IPoIB
> > configuration files include the following line:
> >    For RedHat:
> >    BOOTPROTO=dhcp
> >    For SLES:
> >    BOOTPROTO=dhcp
> > Note: If IPoIB configuration files are included, ifcfg-ib<n> files will
> be
> > installed under:
> > /etc/sysconfig/network-scripts/ on a RedHat machine
> > /etc/sysconfig/network/ on a SuSE machine
> >
> > Note: Two patches for DHCP are required for supporting IPoIB. The patch
> files
> > for DHCP v3.0.4 are available under the docs/dhcp/ directory.
> >
> > Standard DHCP fields holding MAC addresses are not large enough to
> contain an
> > IPoIB hardware address. To overcome this problem, DHCP over InfiniBand
> messages
> > convey a client identifier field used to identify the DHCP session. 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.
>
>
> I don't see how to download an older version (3.0.4 vs. 4.2.5) nor is
> there a /doc/dhcp/ folder in 4.2.5 that holds patches.
>
> Malek
>
>
>
>
> On Thu, Apr 4, 2013 at 9:25 AM, Hal Rosenstock <hal.rosenstock at gmail.com>wrote:
>
>> Hi,
>>
>> On Thu, Apr 4, 2013 at 9:14 AM, Malek Musleh <malek.musleh at gmail.com>wrote:
>>
>>> Hi,
>>>
>>> I am using the latest dhcp package from ISC (dhcp-4.2.5-P1), and I am
>>> trying to configure my dhcp server for infiniband clients. The server host
>>> machine has infiniband port, as well as several client machines.
>>>
>>> Looking through the source code, it seems that there is infiniband
>>> support (unlike prior dhcp rpms where patches need to be applied, patches
>>> of which in themselves are incomplete).
>>>
>>> I installed the package, and when I try to run the dhcp server to listen
>>> on the infiniband port (ib0) as follows:
>>> # dhcpd ib0 -d
>>>
>>> I get the following error:
>>>
>>> Internet Systems Consortium DHCP Server 4.2.5-P1
>>> Copyright 2004-2013 Internet Systems Consortium.
>>> All rights reserved.
>>> For info, please visit https://www.isc.org/software/dhcp/
>>> Wrote 0 leases to leases file.
>>> Unsupported device type 32 for "ib0"
>>>
>>> If you did not get this software from ftp.isc.org, please
>>> get the latest from ftp.isc.org and install that before
>>> requesting help.
>>>
>>> If you did get this software from ftp.isc.org and have not
>>> yet read the README, please read it before requesting help.
>>> If you intend to request help from the dhcp-server at isc.org
>>> mailing list, please read the section on the README about
>>> submitting bug reports and requests for help.
>>>
>>> Please do not under any circumstances send requests for
>>> help directly to the authors of this software - please
>>> send them to the appropriate mailing list as described in
>>> the README file.
>>>
>>> exiting.
>>>
>>> I thought the error might be on my part due to the configuration file,
>>> but grepping through the source code for that error, in
>>> file: dhcp-4.2/dhcp-4.2.5-P1/common/bpf.c
>>>
>>>                 case IFT_ETHER:
>>>                         hw->hlen = sa->sdl_alen + 1;
>>>                         hw->hbuf[0] = HTYPE_ETHER;
>>>                         memcpy(&hw->hbuf[1], LLADDR(sa), sa->sdl_alen);
>>>                         break;
>>>                 case IFT_ISO88023:
>>>                 case IFT_ISO88024: /* "token ring" */
>>>                 case IFT_ISO88025:
>>>                 case IFT_ISO88026:
>>>                         hw->hlen = sa->sdl_alen + 1;
>>>                         hw->hbuf[0] = HTYPE_IEEE802;
>>>                         memcpy(&hw->hbuf[1], LLADDR(sa), sa->sdl_alen);
>>>                         break;
>>> #ifdef IFT_FDDI
>>>                 case IFT_FDDI:
>>>                         hw->hlen = sa->sdl_alen + 1;
>>>                         hw->hbuf[0] = HTYPE_FDDI;
>>>                         memcpy(&hw->hbuf[1], LLADDR(sa), sa->sdl_alen);
>>>                         break;
>>> #endif /* IFT_FDDI */
>>>                 default:
>>>                         log_fatal("Unsupported device type %d for
>>> \"%s\"",
>>>                                   sa->sdl_type, name);
>>>
>>>
>>> But nothing for Infiniband, even though HTYPE_INFINIBAND is defined in
>>> the includes/ directory. Should I be using a different version of dhcp, or
>>> is there some additional patch I need to apply.
>>>
>>>
>>
>> I sent out patches for this back on 4/23/11 ("Add support for DHCP over
>> IPoIB per IETF RFC 4390") but they have not yet been incorporated into
>> upstream ISC DHCP release. Those 2 patches were done against 4.2.1-P1 which
>> was the latest at that time.
>>
>> -- Hal
>>
>>
>>>
>>>
>>> Thanks,
>>>
>>> Malek
>>>
>>> _______________________________________________
>>> dhcp-users mailing list
>>> dhcp-users at lists.isc.org
>>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20130404/f9107369/attachment.html>


More information about the dhcp-users mailing list