[EMAIL PROTECTED] wrote:
Hi, We are setting up a new remote office and are testing Sunray DTU connection. We managed to get the remote DTU to connect to our central SRSS i.e. I can see the Insert Card OSD. However, the DTU is not pulling the new firmware. I have used "./utadm -A <new VLAN> " to register the new subnet. And ./utadm -l shows: bash-3.00# ./utadm -l LAN connections: On
Unless you do BOOTP forwarding from the remote subnet, the DHCP settings are irrelevant. The thing that's important is the setting up of .parms files and firmware in /tftpboot on the server. Verify that those exist. If they don't, then you may need to run utfwadm to install the patch firmware and create the .parms files.
And we have added the following settings to our router (acting as DHCP servers): option 49 ip 192.168.16.21 192.168.16.22 192.168.16.23 option 35 ip 192.168.16.21 192.168.16.22 192.168.16.23 option 23 ascii "4.0_127553-01_2007.11.09.17.41" option 31 ip 192.168.16.21 option 66 ip 192.168.16.21
Option 66 should work to provide a hook whereby the Sun Ray can read its .parms file and firmware. Options 35, 23, and 31 do nothing. You've set the generic options here, and you need to set specific vendor options in the SUNW.NewT.SUNW vendor class.
When the DTU starts up, it will cycle through 192.168.16.21 to 23, and eventually connects to one of them. But it is not downloading the new firmware 4.0_127553-01_2007.11.09.17.41
Look at the utquery output for the Sun Ray and see if it's reading the .parms information. You could also snoop the TFTP traffic to see if the Sun Ray is trying to read from the server.
Kent _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
