This is not OpenSolaris specific, but relates to Solaris 10 10/09 JumpStart over the network. We are not using a traditional environment. We are installing Solaris from a Linux OS. The end result is that the client's are installed via the JumpStart mechanism. However, the PXE modules and boot loaders are written in-house
We have found recently that when we attempt to boot and install the Solaris 10 x86 OS onto a client, that the client exits install-discovery citing the inability to configure the interfaces. Through poking around, I have found that bootmac, hostip, netmask, and def_route are not set in the /devices tree and this is why install-discovery quits. If I run /sbin/netstrategy, it returns "ufs none none" after install-discovery has errored out. Executing the same from a working environment after ctrl-C'ing install-discovery returns "ufs $int dhcp" (where $int is the primary interface in the chassis). In analysing packet captures in a working and non-working environment, we have found that in the working environment, the observed behavior is 2 DHCP discovers (one from PXE; the second from Solaris when loading the Solaris environment) while in our non-working environment we observe only the first DHCP discover from PXE. I am trying to identify at what point our failure is occurring, but am unsure how the variables identified above are populated in the /devices tree. I am hoping that someone here might be able to guide me in the right direction to identify the point and cause of failure. -- This message posted from opensolaris.org
