Thommy M. Malmstr?m writes:
> > Why is my machine called "unknown"
> >
> > Please make sure that the Nevada install process
> > asks for
> > node name even if the person installing is
> > selecting DHCP
> > o provide IP environment.
>
> Lars, it doesn't matter how you set the nodename. Some DHCP server forces a
> name for you and you can't set it otherwise. But 'unknown' should be avoided
> as it causes questions...
As for the next question, this isn't exactly a problem with the DHCP
client. Instead, it's a problem with svc:/system/identity:node which
does this in /lib/svc/method/identity-node:
case "$_INIT_NET_STRATEGY" in
"dhcp") hostname=`/sbin/dhcpinfo Hostname` ;;
[...]
if [ -z "$hostname" ]; then
hostname="`shcat /etc/nodename 2>/dev/null`"
if [ -z "$hostname" ]; then
hostname="unknown"
fi
fi
In other words, it assumes that if the DHCP server supplies a name on
the system's "primary" interface (even if you didn't want that name),
then that should override what the administrator has explicitly set in
/etc/nodename.
This logic was implemented as part of CR 4773326.
Replacing /sbin/netstrategy with a shell script that does something
like this will work around the problem:
echo ufs none none
... at least until the next upgrade wipes out the customized
/sbin/netstrategy.
--
James Carlson, Solaris Networking <james.d.carlson at sun.com>
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
