On 11/2/07, Sean Clarke <[EMAIL PROTECTED]> wrote: > bash-3.00# /opt/SUNWut/sbin/utadm -l > LAN connections: On > Sun Ray interconnect framework is not configured > > So, nothing configured.... > > bash-3.00# /opt/SUNWut/sbin/utadm -a nge0 > Error: Interface "nge0" already configured; cannot add > > But, something is configured....
Right, it's sort of half-configured. There are no DHCP tables but there are still some fragments of previous configuration in other places; in this case, in /etc/inet/networks. A 'utadm -d nge0' should clear out everything realted to the nge0 interface. A 'utadm -r' should clear out everything. > After a bit of tweaking I manage to get it sorted, however.. when I run > utadm -a nge0 it runs the freezes at: > > ### successfully setup "/etc/hostname.nge0" file > Warning: IP address "172.16.0.4" appears in "/etc/inet/hosts" with > another hostname, fix? ([Y]/N): > ### successfully setup "/etc/inet/hosts" file > ### successfully setup "/etc/inet/netmasks" file > ### successfully setup "/etc/inet/networks" file > ### finished install of "nge0" interface > > and nothing.... so in desperation I reboot, now every time I access > utadm it hangs: > > bash-3.00# /opt/SUNWut/sbin/utadm -l > > <hang> > > bash-3.00# /opt/SUNWut/sbin/utadm -p > > <hang> > > bash-3.00# /opt/SUNWut/sbin/utadm -d nge0 > > So.. what is the best way out of this sorry mess... what can I do to > reset things and start again? 'utadm' does a certain amount of discovery of the existing configuration before it even looks at the command line options. It's probably getting stuck at that point. I've never seen that happen before. My guess is that one of the DHCP queries it runs is hanging, but that's just a guess. There are two things you can do to gather more information. The first is to run 'utadm' with execution tracing turned on, so that you can see what it's done and what it's trying to do next. Do '/bin/ksh -p -x /opt/SUNWut/sbin/utadm -l'. (That won't show you what scripts invoked by 'utadm' are doing, but it will show you how far it gets and some of what it did on its way to hanging.) The second is that, once the 'utadm' has hung, run 'ptree' against the 'utadm' process (that'll tell you which child command process is hanging) and then run 'truss' against the hanging process to see what it's doing, or what it's waiting for. OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
