I have PXE booting clients that exhibit similar behavior. They get their
DHCP information from the right server, but then occasionally someone
puts up a PXE server on campus (usually a Novell ZenWorks imaging
server) and they will PXE boot to that server instead. Anyone have any
suggestions on how I can more closely tie the PXE clients to the right
server all the time?
Thanks.
Anselm Martin Hoffmeister wrote:
It seems you are running more than one dhcpd on that network and clients tend
to get their kernel after dhcp information from server_1 and continue
booting, running dhclient and retrieving info from server_2. This is no
problem if all the servers supply same services and probably makes kind of
load balancing, but it may be bad in a mixed setup.
In your place, I'd set all dhcp servers as "non authoritative" and add one
host section for each host at only _one_ dhcp server. This way, you can move
clients from one server to another at your choice, "emptying" one server for
the moment of upgrading to LTSP4. Afterwards (when everything is a homogenous
landscape of LTSP4 machines), you could reduce your dhcpd setup to only two
dhcp servers, and do loadbalancing e.g. by X -broadcast
which is far more reasonable probably. However this has been discussed before,
and I'm not experienced enough on this topic to recommend a certain strategy.
btw. the kernel messages can be retrieved with the dmesg on the client shell.
No idea though if this is in the LTSP tree regularly, in case it's not, you
can copy it + the needed libs over from the server tree.
Regards,
Anselm
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
--
Brian Payst, MS
Director of Technology & Systems Support
Division of Student Affairs
The University of North Carolina at Chapel Hill
voice: (919) 962-1469 fax: (919) 962-5241
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
