Re: [xcat-user] From where next-server is fetched from?

2021-05-21 Thread Vinícius Ferrão via xCAT-user
LOL. I feel like an idiot right now.

Hmmm thanks Kilian, you're indeed correct. I need to understand now why it 
wasn't working and started working when I manually override the next-server 
variable.

> On 21 May 2021, at 21:22, Kilian Cavalotti  
> wrote:
> 
> I don't think it needs to be expanded by xCAT in the DHCP lease file.
> dhcpd will literally send the
> "http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43; string in
> the DHCP reply, and the TFTP/PXE client will interpret this using the
> "next-server" value that is defined at the subnet level in dhcpd.conf.
> 
> Some examples here: https://wiki.alpinelinux.org/wiki/PXE_boot#HOWTO
> 
> Cheers,
> --
> Kilian
> 
> On Fri, May 21, 2021 at 4:51 PM Vinícius Ferrão via xCAT-user
>  wrote:
>> 
>> Hello, I'm running xCAT development build and makedhcp is falling to proper 
>> populate next-server on /var/lib/dhcpd/dhcpd.leases:
>> 
>> As an example:
>> 
>> host adano43 {
>>  dynamic;
>>  hardware ethernet 00:11:22:33:44:55;
>>  uid 00:11:22:33:44:55;
>>  fixed-address 172.26.0.43;
>>supersede server.ddns-hostname = "adano43";
>>supersede host-name = "adano43";
>>if option user-class-identifier = "xNBA" and option 
>> client-architecture
>> = 00:00 {
>>  supersede server.always-broadcast = 01;
>>  supersede server.filename =
>>  "http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43;;
>>} elsif option user-class-identifier = "xNBA" and option
>>client-architecture = 00:09 {
>>  supersede server.filename =
>>  
>> "http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43.uefi;;
>>} elsif option client-architecture = 00:07 {
>>  supersede server.filename = "xcat/xnba.efi";
>>} elsif option client-architecture = 00:00 {
>>  supersede server.filename = "xcat/xnba.kpxe";
>>} else {
>>  supersede server.filename = "";
>>}
>> }
>> 
>> So to figure it out, someone knows from where xCAT grabs the variable to 
>> replace with the next-server? I know that this should be the management node 
>> or maybe a service node, if I was using one.
>> 
>> Thanks,
>> V.
>> 
>> ___
>> xCAT-user mailing list
>> xCAT-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/xcat-user
> 
> 
> 
> -- 
> Kilian
> 
> 
> ___
> xCAT-user mailing list
> xCAT-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xcat-user


___
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user


Re: [xcat-user] From where next-server is fetched from?

2021-05-21 Thread Kilian Cavalotti
I don't think it needs to be expanded by xCAT in the DHCP lease file.
dhcpd will literally send the
"http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43; string in
the DHCP reply, and the TFTP/PXE client will interpret this using the
"next-server" value that is defined at the subnet level in dhcpd.conf.

Some examples here: https://wiki.alpinelinux.org/wiki/PXE_boot#HOWTO

Cheers,
--
Kilian

On Fri, May 21, 2021 at 4:51 PM Vinícius Ferrão via xCAT-user
 wrote:
>
> Hello, I'm running xCAT development build and makedhcp is falling to proper 
> populate next-server on /var/lib/dhcpd/dhcpd.leases:
>
> As an example:
>
> host adano43 {
>   dynamic;
>   hardware ethernet 00:11:22:33:44:55;
>   uid 00:11:22:33:44:55;
>   fixed-address 172.26.0.43;
> supersede server.ddns-hostname = "adano43";
> supersede host-name = "adano43";
> if option user-class-identifier = "xNBA" and option 
> client-architecture
>  = 00:00 {
>   supersede server.always-broadcast = 01;
>   supersede server.filename =
>   "http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43;;
> } elsif option user-class-identifier = "xNBA" and option
> client-architecture = 00:09 {
>   supersede server.filename =
>   
> "http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43.uefi;;
> } elsif option client-architecture = 00:07 {
>   supersede server.filename = "xcat/xnba.efi";
> } elsif option client-architecture = 00:00 {
>   supersede server.filename = "xcat/xnba.kpxe";
> } else {
>   supersede server.filename = "";
> }
> }
>
> So to figure it out, someone knows from where xCAT grabs the variable to 
> replace with the next-server? I know that this should be the management node 
> or maybe a service node, if I was using one.
>
> Thanks,
> V.
>
> ___
> xCAT-user mailing list
> xCAT-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xcat-user



-- 
Kilian


___
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user


[xcat-user] From where next-server is fetched from?

2021-05-21 Thread Vinícius Ferrão via xCAT-user
Hello, I'm running xCAT development build and makedhcp is falling to proper 
populate next-server on /var/lib/dhcpd/dhcpd.leases:

As an example:

host adano43 {
  dynamic;
  hardware ethernet 00:11:22:33:44:55;
  uid 00:11:22:33:44:55;
  fixed-address 172.26.0.43;
supersede server.ddns-hostname = "adano43";
supersede host-name = "adano43";
if option user-class-identifier = "xNBA" and option client-architecture
 = 00:00 {
  supersede server.always-broadcast = 01;
  supersede server.filename =
  "http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43;;
} elsif option user-class-identifier = "xNBA" and option
client-architecture = 00:09 {
  supersede server.filename =
  
"http://${next-server}:80/tftpboot/xcat/xnba/nodes/adano43.uefi;;
} elsif option client-architecture = 00:07 {
  supersede server.filename = "xcat/xnba.efi";
} elsif option client-architecture = 00:00 {
  supersede server.filename = "xcat/xnba.kpxe";
} else {
  supersede server.filename = "";
}
}

So to figure it out, someone knows from where xCAT grabs the variable to 
replace with the next-server? I know that this should be the management node or 
maybe a service node, if I was using one.

Thanks,
V.

___
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user