Trouble Again with "set statements =" in Dynamic Groups

[Randall C Grimshaw]

My approach is to use class definitions - so using your data it would look like this:

class "PXECLIENT" {
  match concat(pick-first-value(option vendor-class-identifier,"no-identifier"),"=",binary-to-ascii(10, 8, "-", option dhcp-parameter-request-list));
}
subclass "PXECLIENT" "PXEClient=1-3-6-12-15-60-66-67" {
    next-server = "192.168.9.7";
    filename = "x1970.0";
}

you can aim these devices at specific pools with logic such as:
allow members of "PXECLIENT";

Randall Grimshaw rgrimsha at syr.edu
________________________________________
From: dhcp-users-bounces+rgrimsha=syr.edu at lists.isc.org [dhcp-users-bounces+rgrimsha=syr.edu at lists.isc.org] on behalf of Martin McCormick [martin at dc.cis.okstate.edu]
Sent: Tuesday, February 28, 2012 3:42 PM
To: Users of ISC DHCP
Subject: Trouble Again with "set statements =" in Dynamic Groups

        I just discovered that the syntax I have used in the
past to create bootP groups dynamically seems to have broken
somewhere along the way. We now use

Internet Systems Consortium DHCP Server 4.1-ESV-R4

and I am not sure when things stopped working because many of
our clients who were using specific groups in bootP moved on to
other technology over the years. The bootP groups have raised
their darling little heads again, however, as one department
wants to use PXECLIENT and that's when I discovered something
was wrong.

        The group in question has several set statements such as

{
option vendor-class-identifier "PXEClient";
option dhcp-parameter-request-list 1,3,6,12,15,60,66,67;
next-server "192.168.9.7";
             filename "x1970.0";
}

        That is basically how one would hard-code the statements
in dhcpd.conf. When turning all this in to omshell statements, I
had needed to concatenate those lines in to one long one with
;'s at the end of each statement.

        Now, my group starts out okay but no more information
appears to be collected after the end of the first statement so
if you put the PXECLIENT statement first, you get it but none of
the others. The omshell output makes you think it all got in,
quoting the entire "set statements" line, etc. Later, when you
watch a dhcpddump of a host trying to use the group and when you
go in to /var/db/dhcpd.leases, one sees only part of the group
information which squares with the incomplete dump the client
gets.

        When searching for information on this problem, I came
across archives of my postings in 2007 about this same problem
and the solution so it looks like something has changed to break
the syntax that had been working.
_______________________________________________
dhcp-users mailing list
dhcp-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users