Yeah, the _how_ is always the tricky part. :)
Anyone know if it is possible to use the IP in an iPXE script? I know I could
use MAC or UUID but I would like to avoid tying the target to a hardware
parameter because clients will eventually need replacement and then you have to
update the targets to match the new hardware. I could use the available IPs as
target names and do something like this _if_ I can fetch the IP address in an
iPXE script:
sanboot --drive 0x80
iscsi:yourtarget.your.domain.name::::iqn.2013-07.name.domain.your:targetname${IP_ADDRESS}
Thanks,
Joe
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Robin Smidsrød
Sent: Thursday, July 25, 2013 12:42 PM
To: [email protected]
Subject: Re: [ipxe-devel] help pushing iscsi targets with DHCP
On 25.07.2013 17:11, Gruher, Joseph R wrote:
> After doing some more reading last night it looks like it might at least be
> possible by using host or subclass statements, each having a unique root-path
> and being tied to a unique MAC, except then I have to capture all the client
> MAC addresses on the server. It would be nice if I could just tell the
> server when it hands out 10.0.0.1 hand out the root path for target01, and
> 10.0.0.2 hand out target02, and so on, so I can just pair targets to IPs.
> All the clients are identical so it doesn't actually matter if they get the
> same target every time and long as they each get a unique target.
The root-path DHCP option uses the same sanboot URL syntax as sanboot/sanhook,
so you can indeed use DHCP host blocks to target it directly to the specific
nodes. Using the assigned IP address as the wildcard for specifying the target
IQN is a viable solution, albeit a but uncommon. But for your use-case it seems
to be a good option.
I'm not sure _how_ to do what you're suggesting in ISC dhcpd, though.
>From what I understand, you can have a generic subnet block, but you'll need
>to be able to pull out the DHCP response variable representing the currently
>assigned IP address for the host (before it's actually sent to the client) and
>use that to dynamically build up the root-path for the same client.
I'd very much like to see the dhcpd config block that actually does that, as I
have no idea how to do that myself.
-- Robin
_______________________________________________
ipxe-devel mailing list
[email protected]
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
_______________________________________________
ipxe-devel mailing list
[email protected]
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
