Youre absolutely right. I actually meant to set it up on 172.16.5.x but
somehow i got 172 and 127 mixed up and managed to overlook my mistake for
days. Now i've changed the IP to 172 and things suddenly got a lot more fun.
Thanks a lot
Truls Asheim
On Tue, 27 May 2008, Jim Klimov wrote:
Hello Truls,
You report using a 127.16.x.x network.
Correct me if I am wrong, but aren't all 127.x.x.x addresses
reserved for loopback within a machine? They can also be routed,
blocked, etc. for these reasons (not expected to come on a NIC).
Can any other network entities (beside sun rays) connect to
your server with these addresses?
Possibly the DTUs try to find a TFTP server on themselves?
In short: try to repeate your steps with another private net,
10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16?
Monday, May 26, 2008, 3:19:22 PM, you wrote:
TA> Hi
TA> I'm working on setting up a sunray server, I have only limited
TA> expirience with Solaris and none whatsoever with the Sunray system.
TA> I have installed SRSS 4 on a Sun Fire v440 server with a fresh
TA> installation of Solaris 10. I have configured everything as described in
TA> the SRSS manual and it should be working. However, when i turn on a
TA> connected Sunray 270 terminal (connected directly to the server via a
TA> crossed cable) I get two errors:
TA> First it tries to download firmware from the server but it fails after a
TA> while with the FW Load: Bad read (code 4 G) error. It then apparently
TA> tries to connect to SRSS but fails after a while with the 27 D error
TA> code. 27 means "The Sun Ray DTU is broadcasting to locate a Sun Ray
TA> server since either it was not provided with Sun Ray specific DHCP
TA> parameters or all of the specified servers are not responding." and D
TA> means "DHCP provided all expected parameters."
TA> The TFTP server (from which the firmware is downloaded) is working
TA> perfectly when i try to download its content with a TFTP client on my
TA> local machine.
TA> In regard to the second error SRSS appears to be listening to the right
TA> port (at least according to netstat (see below)) and the DHCP server
TA> appears to provide the correct information to the DTU:
TA> [EMAIL PROTECTED] sbin # ./utadm -l
TA> LAN connections: On
TA> Subnetwork: 127.16.5.0
TA> Interface= ce1 (127.16.5.1)
TA> Netmask= 255.255.255.0
TA> Broadcast= 127.16.5.255
TA> Router= 127.16.5.1
TA> AuthSrvr= 127.16.5.1
TA> AltAuth= 127.16.5.1 255.255.255.255
TA> FirmwareSrvr= 127.16.5.1
TA> NewTver= 4.0_48_2007.08.01.15.48
TA> IP assignment= 0/253 (127.16.5.2)
TA> utquery doesn't return anything and i am also unable to ping the DTU (I
TA> don't know if I should be able to do that):
TA> [EMAIL PROTECTED] SUNWut # ./sbin/utquery -d 127.16.5.233
TA> [EMAIL PROTECTED] SUNWut # ping 127.16.5.233
TA> no answer from 127.16.5.233
TA> netstat output:
TA> TCP: IPv4
TA> Local Address Remote Address Swind Send-Q Rwind Recv-Q State
TA> -------------------- -------------------- ----- ------ ----- ------
TA> -----------
TA> *.* *.* 0 0 49152 0 IDLE
TA> 127.0.0.1.7010 127.0.0.1.40970 49152 0 49160 0
TA> TIME_WAIT
TA> *.111 *.* 0 0 49152 0 LISTEN
TA> *.* *.* 0 0 49152 0 IDLE
TA> *.32771 *.* 0 0 49152 0 LISTEN
TA> *.32772 *.* 0 0 49152 0 LISTEN
TA> *.4045 *.* 0 0 49152 0 LISTEN
TA> *.5987 *.* 0 0 49152 0 LISTEN
TA> *.32773 *.* 0 0 49152 0 LISTEN
TA> *.7100 *.* 0 0 49152 0 LISTEN
TA> *.32774 *.* 0 0 49152 0 LISTEN
TA> *.32775 *.* 0 0 49152 0 LISTEN
TA> *.32776 *.* 0 0 49152 0 LISTEN
TA> *.32777 *.* 0 0 49152 0 LISTEN
TA> *.32778 *.* 0 0 49152 0 LISTEN
TA> *.6112 *.* 0 0 49152 0 LISTEN
TA> *.23 *.* 0 0 49152 0 LISTEN
TA> *.21 *.* 0 0 49152 0 LISTEN
TA> *.79 *.* 0 0 49152 0 LISTEN
TA> *.513 *.* 0 0 49152 0 LISTEN
TA> *.514 *.* 0 0 49152 0 LISTEN
TA> *.6481 *.* 0 0 49152 0 LISTEN
TA> *.7008 *.* 0 0 49152 0 LISTEN
TA> *.22 *.* 0 0 49152 0 LISTEN
TA> *.25 *.* 0 0 49152 0 LISTEN
TA> *.25 *.* 0 0 49152 0 LISTEN
TA> *.587 *.* 0 0 49152 0 LISTEN
TA> *.32779 *.* 0 0 49152 0 LISTEN
TA> *.32780 *.* 0 0 49152 0 LISTEN
TA> *.7012 *.* 0 0 49152 0 LISTEN
TA> *.32792 *.* 0 0 49152 0 BOUND
TA> *.6788 *.* 0 0 49152 0 LISTEN
TA> *.6789 *.* 0 0 49152 0 LISTEN
TA> *.32798 *.* 0 0 49152 0 BOUND
TA> *.1660 *.* 0 0 49152 0 LISTEN
TA> *.1661 *.* 0 0 49152 0 LISTEN
TA> *.32799 *.* 0 0 49152 0 LISTEN
TA> 127.0.0.1.32788 *.* 0 0 49152 0 LISTEN
TA> 127.0.0.1.50505 *.* 0 0 49152 0 LISTEN
TA> *.7011 *.* 0 0 49152 0 LISTEN
TA> *.7007 *.* 0 0 49152 0 LISTEN
TA> 130.225.96.177.32808 130.225.96.177.7012 49152 0 49152 0
TA> ESTABLISHED
TA> 130.225.96.177.7012 130.225.96.177.32808 49152 0 49152 0
TA> ESTABLISHED
TA> *.32810 *.* 0 0 49152 0 BOUND
TA> *.7010 *.* 0 0 49152 0 LISTEN
TA> *.7009 *.* 0 0 49152 0 LISTEN
TA> 127.0.0.1.40885 127.0.0.1.7010 49152 0 49152 0
TA> ESTABLISHED
TA> 127.0.0.1.7010 127.0.0.1.40885 49152 0 49152 0
TA> ESTABLISHED
TA> 130.225.96.177.22 130.225.97.14.53591 47232 0 49232 0
TA> ESTABLISHED
TA> The manual recommends that one uses a 32-bit version of the JVM with
TA> SRSS even when using a 64-bit OS. I couldn't figure out how to check if
TA> I am using a 64- or a 32-bit JVM so right now, I'm just using the one
TA> installed with Solaris. Could that have something to do with my problem?
TA> Please ask if you need any more information.
TA> As an additional question, I would like to know which logs are relevant
TA> when debugging a problem like this, i have not been able to find a log
TA> which shows exactly what happens when a DTU is connected neither have i
TA> been able to get anything useful out of the DHCP server.
TA> Thanks in advance
TA> Truls Asheim
TA> _______________________________________________
TA> SunRay-Users mailing list
TA> [email protected]
TA> http://www.filibeto.org/mailman/listinfo/sunray-users
--
Best regards,
Jim Klimov mailto:[EMAIL PROTECTED]
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
