Howdy, I am an undergrad CS student with a big problem!. Our snazzy student-run SunRay setup has been working great until we moved it out to the fairgrounds for our Tech Expo. I don't normally bug people like this, but we're in a bind and I hope you might have a few minutes to read our problem and see if you might know a solution. We had been using Solaris 10 + SRSS 3.1 on a shared LAN, DHCP handled by the main campus DHCP server. All was dandy until this morning. What we did was reconfigure our server (280R + dual ethernet/dual scsi pci card) for the new IP address (primary eri0) at the Tech Expo, then hung a 24 port ethernet switch off of the PCI card (ce0). The idea is to have the SunRays on their own private LAN with the 280R handling DHCP, etc. I did a "utadm -r" followed by a "utadm -a ce0" thinking that should do the trick. It didn't. We've tried reinstalling Solaris 9 + SRSS 3.1 as more of us have more Solaris 9 experience (we originally ran this setup on Solaris 9 + SRSS 2 when it was new).
Here is the current situation, fresh Solaris 9 + latest patch cluster + SRSS 3.1. Fresh utconfig + utadm -a ce0 + utrestart. When a new SunRay is plugged into the private lan, it gets an IP address from the DHCP pool, connects to get updated firmware (yellow/black arrow animation), but then goes into a reset-every-2-seconds cycle. Gets IP address, connects to server (black arrow), power cycles.... about once every two seconds. This can be seen on the flickering monitor, SunRay amber LED (for half a second), green LED (about a full second).... and by the clicking SunRay speaker about once every 2 seconds or so. Does this ring any bells? I've been over the manual and manpages all morning and am still at a loss. Thank you in advance for any help you may have to offer! Colin _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
