Re: Where doe PXEWorx get "transaction server"
This turns out to be supplied by the undocumented DHCP Options 180, 181, and 182. We added the Zen Imaging server IP to Options 180 and 181, and added 0.0.0.0 to Option 182 and this seems to allow our PCs to boot off a "remote" Zen Imaging server on another subnet, using the router as the initial DHCP server on the local subnet. We arrived at this fix after snooping the booting process with Wireshark.
For those of you fortunate enough to be running JunOS, the configuration is as follows:
{master:0}[edit system services dhcp]
wms2@ccf4200stack# show
domain-name mydomain.edu;
name-server {
[etc]
}
wins-server {
[etc]
}
boot-file dinic.sys;
next-server 10.0.1.99;
option 180 ip-address 10.0.1.99;
option 181 ip-address 10.0.1.99;
option 182 ip-address 0.0.0.0;
pool 10.3.0.0/24 {
address-range low 10.3.0.100 high 10.3.0.249;
router {
10.3.0.254;
[etc]
Where 10.0.1.99 is the address of the Zen Image server.
|
Threaded Mode
