UNIX admin writes: > > 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?
It means the entry is not valid. Most often, this is because some client has returned a DHCP DECLINE message when offered that address -- which in turn means that the address is a duplicate, and thus must not be used on this network. The flag can be set manually as well to prevent the server from assigning that address, or even to prevent the server from assigning _any_ address to a given client. > 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. Click on the "Lease" tab and set the Client ID there. The Address tab just has (I think) the Client Name as known to name services. Surprisingly, the "Help" button also works. ;-} The Client ID is, by default, a hex string, starting with "01" for an Ethernet MAC address. > > 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. One modifies configuration parameters (boot server and the like), the other manages network address (lease) tables. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list [email protected]
