UNIX admin wrote:
Which DHCP server are you using? In a previous message on this
thread, you hinted that you were using some other DHCP server --
not the one in Solaris.
I did? No, it's in.dhcpd that comes with Solaris.
If you're using the Solaris DHCP server, the easiest way (by far)
to administer it is using the dhcpmgr GUI. It's hidden over in
/usr/sadm/admin/bin/dhcpmgr. (Note: you likely want a DHCP/BOOTP
server, not a relay.)
Yes, but that GUI is weird. For example, the address for the PXE boot
client is marked "unusable". Well, what does that mean?
There should be pretty ample documentation on what that means, but it
will mean one of 3 things:
1. Somebody marked it unusable using pntadm or dhcpmgr
2. The DHCP server attempted to offer the address, but some system
answered the ICMP Echo that is sent out to verify that it's unused
before offering.
3. The client responded to the server's offer of the address with a
DHCP Decline message, which is usually because some other system
responded to the ARP request that clients send to double-check the
address is free before accepting it.
Either of the latter two sometimes happen because of buggy clients.
And then when I define the Octane, it won't let me really enter
anything in the "client" field, it's greyed out. And there are some
Java exceptions showing up.
Without exact text of those exceptions I won't attempt to speculate on
the problem.
Note that I haven't modified Java-anything on the system.
If you want to use the command line instead, then you need to use
pntadm to set the flags on a static client entry to 08 (BOOTP) to
let in.dhcpd know that this is an old-school BOOTP client.
I still haven't figured out what the difference between `dhtadm` and
`pntadm` is.
The simple answer is that pntadm manages the addresses available for
DHCP management; dhtadm manages the parameters that are supplied to DHCP
clients in addition to the addresses.
Dave
_______________________________________________
opensolaris-discuss mailing list
[email protected]
