Steffen Weiberle wrote:
Thanks, John. That may be it. Hopefully the fix is not just for DHCP
interfaces, since I
am using a fixed address.
First, netstrategy returned what it's supposed to in this case: "ufs
none none" is the right answer here.
I'd be somewhat surprised if the CR John referenced is the problem; that
CR has entirely to do with the case of interfaces for which the driver
is supplied by an ITU. As you're using e1000g, and the output shows
that it's been found, I don't think that's it. The cause here appears
to be that the properties which should have been populated out of the
GRUB setting weren't, as shown in this excerpt from your output:
+ prtconf -v /devices
+ sed -n /boot-mac/{;n;p;}
bootmac=
+ cut -f 2 -d '
+ prtconf -v /devices
+ sed -n /host-ip/{;n;p;}
hostip=
+ cut -f 2 -d '
+ prtconf -v /devices
+ sed -n /subnet-mask/{;n;p;}
netmask=
+ cut -f 2 -d '
+ prtconf -v /devices
+ sed -n /router-ip/{;n;p;}
def_route=
Each of those properties should have a value, which install-discovery
uses to configure the interface and the default route into Solaris.
They don't, so somewhere between GRUB and the kernel this got dropped.
You aren't using an outdated version of GRUB, are you?
Dave
Thanks
Steffen
John Beck wrote:
Steffen> Recent Nevada builds have caused me to experience a new failure
Steffen> when trying to install x64 systems.
Steffen> I don't 'own' the DHCP server on the network and thus can not
Steffen> set up PXE boot. Instead, I have created GRUB entries that
Steffen> hard code the system network information... This used to work
Steffen> until recently, maybe until the new boot mechanism.
Steffen> I noticed that install-discovery calls netstrategy, which is
Steffen> returning values that don't configure the network, it seems...
This seems somewhat similar to
6490981 netstrategy continues to report empty strings for dhcp'd
interfaces even after a driver is added
which was fixed in build 65.
-- John
http://blogs.sun.com/jbeck
_______________________________________________
networking-discuss mailing list
[email protected]
_______________________________________________
networking-discuss mailing list
[email protected]
_______________________________________________
networking-discuss mailing list
[email protected]
