Rao Shoaib wrote: > I just installed nwam1-build-RC1 on my Toshiba laptop running latest > open solaris development build. I have not installed the GUI yet. > Here are come comments. > > *) The bfu went fine and the system rebooted fine > > *) The e1000g interface was plumbed correctly > > *) nameservice that was working previously had stopped working. So I > decided to go back to the default. After issuing svcadm to switch back > I thought everything would go back to the old way but it turns out > there was no plumbed interface in the system. Moreover > /etc/hostname.<interface> and /etc/dhcp* files did not exist. So now > even If I reboot I can not get back to my original configuration Did you you /etc/hostname.* and /etc/dhcp* before? NWAM doesn't touch those file at all. > [ ... ] > > *) So I rebooted the system. The system obviously came up without any > networking. I tried to enable nwam without disabling > network/physical:default and the framework correctly put it in > maintenance mode. disabling network/physical:default and bringing in > network/physical:nwam correctly configured my e1000g interface and > guess what name service was working !!!!!!! > > *) I rebooted my laptop again. It came up with nwam enabled but no > interface plumbed. All my manual attempts to get an IP so I could > transfer the log file failed. So I disabled nwam, create > /etc/hostname.e1000g0 and /etc/dhcp.e1000g0, enable > network/physical:default and rebooted. The system came up fine. I > transferred the log file (attached). > > *) Now again I disabled network/physical:default and enabled > network/physical:nwam and rebooted .. I am in the same situation with > a system with no plumbed/configured/working interface. This time > however /etc/hostname.e1000g0 and /etc/dhcp.e1000g0 are still there. the no interfaces after 2nd reboot is bug 11685 (http://defect.opensolaris.org/bz/show_bug.cgi?id=11685) which is because of CR 6888202 in ON. Garrett has pushed the fix for it to ON. I am working on getting that changeset and any related ones to the NWAM gate. We'll spin RC2 with that.
In the mean-time, the workaround is to simply restart nwam. Anurag
