RE: [SunRay-Users] Utselect between solaris and linux not working
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Doolittle Sent: Thursday, February 22, 2007 3:05 PM To: SunRay-Users mailing list Subject: Re: [SunRay-Users] Utselect between solaris and linux not working It certainly looks to me like your network is flaky. Hopefully it's an artifact tickled by the multicast functionality, which will resolve itself once you change to broadcast... -Bob I unconfigured the sunray services on ndssr01 'utadm -r' and 'utconfig -u' and reran the 'utconfig' and 'utadm -a hme0' and still no 'U' between ndssr01 and pablo/skb-linux. I went ahead and upgraded to SRSS 3.1 on ndssr01 and it still wouldn't see skb-linux or pablo on the 192.1681.32.0 network with utgstatus. I physically moved pablo into the same room where ndssr01 is located, physically connected ndssr01 and pablo (192.168.132.0) via a crossover cable and got the 'U' between the two. Then I connected both to a 5-port linksys switch and used the 192.168.132.0 network to uplink it to the rest of the network. I was able to switch between the ndssr01 and pablo on the sunray's after that. Still couldn't see 'U' for skb-linux which is still in another room. Definitely a network issue. I assumed because the auth.props has enableMulticast=true commented out, that that implies enableMulticast=false. But not the case. I explicitly set enableMulticast=false on all three and now ALL computers see and switch between each other. Thanks for all your help Bob, OttoM, and Craig!! On to the next issue in another email to come. Suzie ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://node1.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] Utselect between solaris and linux not working
Bemis, Suzanna K wrote: I assumed because the auth.props has enableMulticast=true commented out, that that implies enableMulticast=false. But not the case. I explicitly set enableMulticast=false on all three and now ALL computers see and switch between each other. For the record - the commented out lines in auth.props are intended to document the default behavior. It's probably not the best communications method for this purpose. -Bob ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://node1.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] Utselect between solaris and linux not working
Bemis, Suzanna K wrote: I think so too. But I don't see a problem with using -A, what problem do you see? Craig is right that she'll have to use the 192.* addresses instead of the public IP addresses, however. Is this what you were referring to? That's the one advantage to using the Interconnect - it will translate the public IP to the appropriate private one internally. I strongly suspect that Suzanna never restarted SRSS after utadm -L on, otherwise we'd see U for all interfaces on all networks. I ran 'utadm -L on' followed by 'utrestart' on all computers. Last one was on ndssr01 and in fact users this morning were asking who's pablo? So when the utrestart on ndssr01 happened the sunray users lost the connection to 'ndssr01', and 'pablo' appeared on their sunray's. I had to disconnect the 192.168.132.0 network cable from pablo and skb-linux so ndssr01 would be the default. It's good to know that we could run the linux sunray servers, but the point is I need some users to know about the linux servers and use them, but I don't want ALL users to. We're still testing the linux environment in general. This is going to be a problem, once you get things working smoothly. Unless you take special measures it'll be a roll of the dice as to what server you'll connect to. I recommend you follow OttoM's suggestion to revert to an Interconnect config (although I disagree with several of his statements, cockroaches notwithstanding, regarding the severity of using '-A' - it'll work fine for redirecting *between* FOGs, which is what I believe you care about and I verified this both by re-reading the code and trying it myself). An Interconnect config will work if you want to be able to redirect within a FOG also, and it allows you to use the primary hostname/IP when redirecting, so it's preferable. Get this working first. To avoid the die-roll sending you to the Linux boxes, you have a few options. - Just disable/shutdown DHCP on the Linux boxes after getting utadm set up the way you want it. Since the solaris box will offer DHCP the DTUs will be told to connect to it initially. This is your simplest option. - Use AMGH. This would allow you to configure your systems to send specific users where you want them. If you have some folks you want to be using Linux, and some not, this will make things seamless for you. You can specify the behavior per-Sun Ray, per-smartcard, per-user, or whatever works best for you. - Configure DHCP individually for each MAC, on both servers, to specify where you want each Sun Ray to go. Sounds painful, not your first option but I mention it for completeness. Your first step is to just get things working to a point where utswitch redirects work, without introducing any new variables. Then you can experiment with the options above to get more control over where the DTUs are connecting. -Bob Craig asked earilier to try 'utswitch -h 192.168.132.3' on ndssr01 - same result as 'utswitch -h skb-linux' - it went to a 25D and showed 134.222.187.182. And, in answer to OttoM about the private network - 192.168.132.0 is only used for the sunray's. Administration, Internet, etc is done on the 134.222.187.0 network. So what might the 'utadm -A' option do that the 'utadm -a' didn't? All we have on the 192.168.132.0 network are sunray's and these three sunray servers. If you have questions about how the network is set up and routed from a physical perspective I can't answer any of those questions myself but if you tell me what to ask the Networking group I can do that much. All I can say is that I don't want to get an entire new LAN for the linux sunray servers because the infrastructure costs would be more than it's worth. Thanks again and still - Suzie -Bob Craig -- why do you think it isn't an isolated interconnect? Suzanna -- is this 192.168.132.0 supposed to be reachable from the rest of your network, or is it supposed to be a private isolated subnet? OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
RE: [SunRay-Users] Utselect between solaris and linux not working
This is going to be a problem, once you get things working smoothly. Unless you take special measures it'll be a roll of the dice as to what server you'll connect to. I recommend you follow OttoM's suggestion to revert to an Interconnect config (although I disagree with several of his statements, cockroaches notwithstanding, regarding the severity of using '-A' - it'll work fine for redirecting *between* FOGs, which is what I believe you care about and I verified this both by re-reading the code and trying it myself). An Interconnect config will work if you want to be able to redirect within a FOG also, and it allows you to use the primary hostname/IP when redirecting, so it's preferable. Get this working first. To avoid the die-roll sending you to the Linux boxes, you have a few options. - Just disable/shutdown DHCP on the Linux boxes after getting utadm set up the way you want it. Since the solaris box will offer DHCP the DTUs will be told to connect to it initially. This is your simplest option. - Use AMGH. This would allow you to configure your systems to send specific users where you want them. If you have some folks you want to be using Linux, and some not, this will make things seamless for you. You can specify the behavior per-Sun Ray, per-smartcard, per-user, or whatever works best for you. - Configure DHCP individually for each MAC, on both servers, to specify where you want each Sun Ray to go. Sounds painful, not your first option but I mention it for completeness. Your first step is to just get things working to a point where utswitch redirects work, without introducing any new variables. Then you can experiment with the options above to get more control over where the DTUs are connecting. -Bob I'll hopefully get some time to take ndssr01 down this weekend and reconfigure as per Bob's and OttoM's emails. In the meantime, and I wasn't making changes to anything, but I ran utgstatus on ndssr01 and got this (notice pablo's status on the 192.168.132.0 interface): bash-2.05# /opt/SUNWut/sbin/utgstatus host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ ndssr01 TN134.222.187.208 UA-192.168.132.1 UA- pablo -N134.222.187.81 UA-192.168.132.2 UAM skb-linux -N134.222.187.182 UA-192.168.132.3 -AM So I ran into the other office where there's a sunray connected to ndssr01, signed on thinking I'd try the utswitch to pablo, but ran utgstatus first and got this: bash-2.05# /opt/SUNWut/sbin/utgstatus host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ ndssr01 TN134.222.187.208 UA-192.168.132.1 UA- pablo -N134.222.187.81 UA-192.168.132.2 -AM skb-linux -N134.222.187.182 UA-192.168.132.3 -AM I don't know what happened in those few moments, but ndssr01 saw pablo as 'U' and then not. Suzie ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] Utselect between solaris and linux not working
It certainly looks to me like your network is flaky. Hopefully it's an artifact tickled by the multicast functionality, which will resolve itself once you change to broadcast... -Bob Bemis, Suzanna K wrote: This is going to be a problem, once you get things working smoothly. Unless you take special measures it'll be a roll of the dice as to what server you'll connect to. I recommend you follow OttoM's suggestion to revert to an Interconnect config (although I disagree with several of his statements, cockroaches notwithstanding, regarding the severity of using '-A' - it'll work fine for redirecting *between* FOGs, which is what I believe you care about and I verified this both by re-reading the code and trying it myself). An Interconnect config will work if you want to be able to redirect within a FOG also, and it allows you to use the primary hostname/IP when redirecting, so it's preferable. Get this working first. To avoid the die-roll sending you to the Linux boxes, you have a few options. - Just disable/shutdown DHCP on the Linux boxes after getting utadm set up the way you want it. Since the solaris box will offer DHCP the DTUs will be told to connect to it initially. This is your simplest option. - Use AMGH. This would allow you to configure your systems to send specific users where you want them. If you have some folks you want to be using Linux, and some not, this will make things seamless for you. You can specify the behavior per-Sun Ray, per-smartcard, per-user, or whatever works best for you. - Configure DHCP individually for each MAC, on both servers, to specify where you want each Sun Ray to go. Sounds painful, not your first option but I mention it for completeness. Your first step is to just get things working to a point where utswitch redirects work, without introducing any new variables. Then you can experiment with the options above to get more control over where the DTUs are connecting. -Bob I'll hopefully get some time to take ndssr01 down this weekend and reconfigure as per Bob's and OttoM's emails. In the meantime, and I wasn't making changes to anything, but I ran utgstatus on ndssr01 and got this (notice pablo's status on the 192.168.132.0 interface): bash-2.05# /opt/SUNWut/sbin/utgstatus host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ ndssr01 TN134.222.187.208 UA-192.168.132.1 UA- pablo -N134.222.187.81 UA-192.168.132.2 UAM skb-linux -N134.222.187.182 UA-192.168.132.3 -AM So I ran into the other office where there's a sunray connected to ndssr01, signed on thinking I'd try the utswitch to pablo, but ran utgstatus first and got this: bash-2.05# /opt/SUNWut/sbin/utgstatus host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ ndssr01 TN134.222.187.208 UA-192.168.132.1 UA- pablo -N134.222.187.81 UA-192.168.132.2 -AM skb-linux -N134.222.187.182 UA-192.168.132.3 -AM I don't know what happened in those few moments, but ndssr01 saw pablo as 'U' and then not. Suzie ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
RE: [SunRay-Users] Utselect between solaris and linux not working
mask ff00 bcast c0a884ff lastpkt 600 sessions 0 idles 0 load 0.0 endhosts Connection to localhost closed by foreign host. OUTPUT of 'telnet localhost 7010;gstatus' from SKB-LINUX [EMAIL PROTECTED] sunray]# telnet localhost 7010 Trying 127.0.0.1... Connected to localhost (127.0.0.1). Escape character is '^]'. gstatus numhosts 5 host skb-linux lastseen 18 timeoff 0 addr 86debbb6 numifs 2 period 20 starttime 1172071839 ROUTER LAN_OK TRUSTED interface eth0 ip 86debbb6 mask ff00 bcast 86debbff lastpkt 18 LAN interface eth2 ip c0a88403 mask ff00 bcast c0a884ff lastpkt 18 sessions 1 idles 0 load 0.0 host pablo lastseen 2 timeoff -131 addr 86debb51 numifs 2 period 20 starttime 1172072364 ROUTER LAN_OK interface eth1 ip c0a88402 mask ff00 bcast c0a884ff lastpkt 2 interface eth0 ip 86debb51 mask ff00 bcast 86debbff lastpkt 2 LAN sessions 1 idles 0 load 0.0 host ndssr01 lastseen 3 timeoff 291 addr 86debbd0 numifs 2 period 20 starttime 1172070004 LAN_OK interface eri0 ip 86debbd0 mask ff00 bcast 86debbff lastpkt 3 LAN interface hme0 ip c0a88401 mask ff00 bcast c0a884ff lastpkt 723 LAN sessions 155 idles 62 load 0.4 endhosts Connection closed by foreign host. Thanks, - Suzanna Bemis, Suzanna K wrote: When I bring up 'utselect' gui on the solaris 9 machine I don't expect to see the names of the linux servers. I enter the name of either linux server in the Enter server field and nothing happens at all. No error messages no switching. When I type in 'utswitch -h linuxhost' again nothing happens. No error messages it just returns to the command line. I have all network interfaces in the /etc/hosts files of all three computers and again I don't get any error messages so name resolution is not an issue. The same symptoms, nothing, when I try the the utselect and utswitch from the linux to the solaris 9. 'utgstatus' on Solaris 9 (ndssr01): host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ ndssr01 TN134.222.187.208 U--192.168.132.1 U-- skb-linux -N134.222.187.182 U--192.168.132.3 -AM pablo -N134.222.187.81 U--192.168.132.2 -AM 'utgstatus' on linux (skb-linux): host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ skb-linux TN134.222.187.182 U--192.168.132.3 UAM pablo -N134.222.187.81 U--192.168.132.2 UAM ndssr01 -N134.222.187.208 U--192.168.132.1 --- Pablo is the other linux box. Utswitch and utselect work between linux boxes. Thanks, Suzie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Doolittle Sent: Tuesday, February 20, 2007 6:30 AM To: SunRay-Users mailing list Subject: Re: [SunRay-Users] Utselect between solaris and linux not working Note that utselect will *never* display hosts outside of the local FOG, is this perhaps what you are seeing? You can run it with the -R option to get a text-input field where you can type a server name, but that's the most you can do to deal with extra-FOG hosts - you can't get a chooser that lists hosts outside of your local FOG. It works fine between any OS platforms. I do this almost daily (although I use utswitch directly, which utselect also uses). -Bob ottomeister wrote: On 2/19/07, Bemis, Suzanna K [EMAIL PROTECTED] wrote: I have SRSS 3.1.1 on 2 Linux sunray servers (pablo and skb-linux) and SRSS 2.0 on Solaris 9 (ndssr01). 'utselect' won't work between a Linux SR server and the solaris 9 server ... In what way doesn't it work? (What do you see when you run it, how do you interact with it, what happens then?) Does it not work in both directions or only in one? What does 'utgstatus' show on these machines? On which of the networks that show in 'utgstatus' is the Sun Ray unit located? Does 'utswitch -h servername' work? OttoM. __ ottomeister Disclaimer: These are my opnions. I do not speak for my employer. ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users
Re: [SunRay-Users] Utselect between solaris and linux not working
interface eth0 ip 86debbb6 mask ff00 bcast 86debbff lastpkt 0 LAN interface eth2 ip c0a88403 mask ff00 bcast c0a884ff lastpkt 600 sessions 0 idles 0 load 0.0 endhosts Connection to localhost closed by foreign host. OUTPUT of 'telnet localhost 7010;gstatus' from SKB-LINUX [EMAIL PROTECTED] sunray]# telnet localhost 7010 Trying 127.0.0.1... Connected to localhost (127.0.0.1). Escape character is '^]'. gstatus numhosts 5 host skb-linux lastseen 18 timeoff 0 addr 86debbb6 numifs 2 period 20 starttime 1172071839 ROUTER LAN_OK TRUSTED interface eth0 ip 86debbb6 mask ff00 bcast 86debbff lastpkt 18 LAN interface eth2 ip c0a88403 mask ff00 bcast c0a884ff lastpkt 18 sessions 1 idles 0 load 0.0 host pablo lastseen 2 timeoff -131 addr 86debb51 numifs 2 period 20 starttime 1172072364 ROUTER LAN_OK interface eth1 ip c0a88402 mask ff00 bcast c0a884ff lastpkt 2 interface eth0 ip 86debb51 mask ff00 bcast 86debbff lastpkt 2 LAN sessions 1 idles 0 load 0.0 host ndssr01 lastseen 3 timeoff 291 addr 86debbd0 numifs 2 period 20 starttime 1172070004 LAN_OK interface eri0 ip 86debbd0 mask ff00 bcast 86debbff lastpkt 3 LAN interface hme0 ip c0a88401 mask ff00 bcast c0a884ff lastpkt 723 LAN sessions 155 idles 62 load 0.4 endhosts Connection closed by foreign host. Thanks, - Suzanna Bemis, Suzanna K wrote: When I bring up 'utselect' gui on the solaris 9 machine I don't expect to see the names of the linux servers. I enter the name of either linux server in the Enter server field and nothing happens at all. No error messages no switching. When I type in 'utswitch -h linuxhost' again nothing happens. No error messages it just returns to the command line. I have all network interfaces in the /etc/hosts files of all three computers and again I don't get any error messages so name resolution is not an issue. The same symptoms, nothing, when I try the the utselect and utswitch from the linux to the solaris 9. 'utgstatus' on Solaris 9 (ndssr01): host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ ndssr01 TN134.222.187.208 U--192.168.132.1 U-- skb-linux -N134.222.187.182 U--192.168.132.3 -AM pablo -N134.222.187.81 U--192.168.132.2 -AM 'utgstatus' on linux (skb-linux): host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ skb-linux TN134.222.187.182 U--192.168.132.3 UAM pablo -N134.222.187.81 U--192.168.132.2 UAM ndssr01 -N134.222.187.208 U--192.168.132.1 --- Pablo is the other linux box. Utswitch and utselect work between linux boxes. Thanks, Suzie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Doolittle Sent: Tuesday, February 20, 2007 6:30 AM To: SunRay-Users mailing list Subject: Re: [SunRay-Users] Utselect between solaris and linux not working Note that utselect will *never* display hosts outside of the local FOG, is this perhaps what you are seeing? You can run it with the -R option to get a text-input field where you can type a server name, but that's the most you can do to deal with extra-FOG hosts - you can't get a chooser that lists hosts outside of your local FOG. It works fine between any OS platforms. I do this almost daily (although I use utswitch directly, which utselect also uses). -Bob ottomeister wrote: On 2/19/07, Bemis, Suzanna K [EMAIL PROTECTED] wrote: I have SRSS 3.1.1 on 2 Linux sunray servers (pablo and skb-linux) and SRSS 2.0 on Solaris 9 (ndssr01). 'utselect' won't work between a Linux SR server and the solaris 9 server ... In what way doesn't it work? (What do you see when you run it, how do you interact with it, what happens then?) Does it not work in both directions or only in one? What does 'utgstatus' show on these machines? On which of the networks that show in 'utgstatus' is the Sun Ray unit located? Does 'utswitch -h servername' work? OttoM. __ ottomeister Disclaimer: These are my opnions. I do not speak for my employer. ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] Utselect between solaris and linux not working
mask ff00 bcast c0a884ff lastpkt 600 sessions 0 idles 0 load 0.0 endhosts Connection to localhost closed by foreign host. OUTPUT of 'telnet localhost 7010;gstatus' from SKB-LINUX [EMAIL PROTECTED] sunray]# telnet localhost 7010 Trying 127.0.0.1... Connected to localhost (127.0.0.1). Escape character is '^]'. gstatus numhosts 5 host skb-linux lastseen 18 timeoff 0 addr 86debbb6 numifs 2 period 20 starttime 1172071839 ROUTER LAN_OK TRUSTED interface eth0 ip 86debbb6 mask ff00 bcast 86debbff lastpkt 18 LAN interface eth2 ip c0a88403 mask ff00 bcast c0a884ff lastpkt 18 sessions 1 idles 0 load 0.0 host pablo lastseen 2 timeoff -131 addr 86debb51 numifs 2 period 20 starttime 1172072364 ROUTER LAN_OK interface eth1 ip c0a88402 mask ff00 bcast c0a884ff lastpkt 2 interface eth0 ip 86debb51 mask ff00 bcast 86debbff lastpkt 2 LAN sessions 1 idles 0 load 0.0 host ndssr01 lastseen 3 timeoff 291 addr 86debbd0 numifs 2 period 20 starttime 1172070004 LAN_OK interface eri0 ip 86debbd0 mask ff00 bcast 86debbff lastpkt 3 LAN interface hme0 ip c0a88401 mask ff00 bcast c0a884ff lastpkt 723 LAN sessions 155 idles 62 load 0.4 endhosts Connection closed by foreign host. Thanks, - Suzanna Bemis, Suzanna K wrote: When I bring up 'utselect' gui on the solaris 9 machine I don't expect to see the names of the linux servers. I enter the name of either linux server in the Enter server field and nothing happens at all. No error messages no switching. When I type in 'utswitch -h linuxhost' again nothing happens. No error messages it just returns to the command line. I have all network interfaces in the /etc/hosts files of all three computers and again I don't get any error messages so name resolution is not an issue. The same symptoms, nothing, when I try the the utselect and utswitch from the linux to the solaris 9. 'utgstatus' on Solaris 9 (ndssr01): host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ ndssr01 TN134.222.187.208 U--192.168.132.1 U-- skb-linux -N134.222.187.182 U--192.168.132.3 -AM pablo -N134.222.187.81 U--192.168.132.2 -AM 'utgstatus' on linux (skb-linux): host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ skb-linux TN134.222.187.182 U--192.168.132.3 UAM pablo -N134.222.187.81 U--192.168.132.2 UAM ndssr01 -N134.222.187.208 U--192.168.132.1 --- Pablo is the other linux box. Utswitch and utselect work between linux boxes. Thanks, Suzie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Doolittle Sent: Tuesday, February 20, 2007 6:30 AM To: SunRay-Users mailing list Subject: Re: [SunRay-Users] Utselect between solaris and linux not working Note that utselect will *never* display hosts outside of the local FOG, is this perhaps what you are seeing? You can run it with the -R option to get a text-input field where you can type a server name, but that's the most you can do to deal with extra-FOG hosts - you can't get a chooser that lists hosts outside of your local FOG. It works fine between any OS platforms. I do this almost daily (although I use utswitch directly, which utselect also uses). -Bob ottomeister wrote: On 2/19/07, Bemis, Suzanna K [EMAIL PROTECTED] wrote: I have SRSS 3.1.1 on 2 Linux sunray servers (pablo and skb-linux) and SRSS 2.0 on Solaris 9 (ndssr01). 'utselect' won't work between a Linux SR server and the solaris 9 server ... In what way doesn't it work? (What do you see when you run it, how do you interact with it, what happens then?) Does it not work in both directions or only in one? What does 'utgstatus' show on these machines? On which of the networks that show in 'utgstatus' is the Sun Ray unit located? Does 'utswitch -h servername' work? OttoM. __ ottomeister Disclaimer: These are my opnions. I do not speak for my employer. ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users
Re: [SunRay-Users] Utselect between solaris and linux not working
period 20 starttime 1172070004 LAN_OK TRUSTED interface eri0 ip 86debbd0 mask ff00 bcast 86debbff lastpkt 5 LAN interface hme0 ip c0a88401 mask ff00 bcast c0a884ff lastpkt 5 LAN sessions 155 idles 61 load 0.4 host pablo lastseen 5 timeoff -421 addr 86debb51 numifs 2 period 20 starttime 1172072364 ROUTER LAN_OK interface eth1 ip c0a88402 mask ff00 bcast c0a884ff lastpkt -1 interface eth0 ip 86debb51 mask ff00 bcast 86debbff lastpkt 5 LAN sessions 1 idles 0 load 0.0 host skb-linux lastseen 0 timeoff -291 addr 86debbb6 numifs 2 period 20 starttime 1172071839 ROUTER LAN_OK interface eth0 ip 86debbb6 mask ff00 bcast 86debbff lastpkt 0 LAN interface eth2 ip c0a88403 mask ff00 bcast c0a884ff lastpkt 600 sessions 0 idles 0 load 0.0 endhosts Connection to localhost closed by foreign host. OUTPUT of 'telnet localhost 7010;gstatus' from SKB-LINUX [EMAIL PROTECTED] sunray]# telnet localhost 7010 Trying 127.0.0.1... Connected to localhost (127.0.0.1). Escape character is '^]'. gstatus numhosts 5 host skb-linux lastseen 18 timeoff 0 addr 86debbb6 numifs 2 period 20 starttime 1172071839 ROUTER LAN_OK TRUSTED interface eth0 ip 86debbb6 mask ff00 bcast 86debbff lastpkt 18 LAN interface eth2 ip c0a88403 mask ff00 bcast c0a884ff lastpkt 18 sessions 1 idles 0 load 0.0 host pablo lastseen 2 timeoff -131 addr 86debb51 numifs 2 period 20 starttime 1172072364 ROUTER LAN_OK interface eth1 ip c0a88402 mask ff00 bcast c0a884ff lastpkt 2 interface eth0 ip 86debb51 mask ff00 bcast 86debbff lastpkt 2 LAN sessions 1 idles 0 load 0.0 host ndssr01 lastseen 3 timeoff 291 addr 86debbd0 numifs 2 period 20 starttime 1172070004 LAN_OK interface eri0 ip 86debbd0 mask ff00 bcast 86debbff lastpkt 3 LAN interface hme0 ip c0a88401 mask ff00 bcast c0a884ff lastpkt 723 LAN sessions 155 idles 62 load 0.4 endhosts Connection closed by foreign host. Thanks, - Suzanna Bemis, Suzanna K wrote: When I bring up 'utselect' gui on the solaris 9 machine I don't expect to see the names of the linux servers. I enter the name of either linux server in the Enter server field and nothing happens at all. No error messages no switching. When I type in 'utswitch -h linuxhost' again nothing happens. No error messages it just returns to the command line. I have all network interfaces in the /etc/hosts files of all three computers and again I don't get any error messages so name resolution is not an issue. The same symptoms, nothing, when I try the the utselect and utswitch from the linux to the solaris 9. 'utgstatus' on Solaris 9 (ndssr01): host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ ndssr01 TN134.222.187.208 U--192.168.132.1 U-- skb-linux -N134.222.187.182 U--192.168.132.3 -AM pablo -N134.222.187.81 U--192.168.132.2 -AM 'utgstatus' on linux (skb-linux): host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ skb-linux TN134.222.187.182 U--192.168.132.3 UAM pablo -N134.222.187.81 U--192.168.132.2 UAM ndssr01 -N134.222.187.208 U--192.168.132.1 --- Pablo is the other linux box. Utswitch and utselect work between linux boxes. Thanks, Suzie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Doolittle Sent: Tuesday, February 20, 2007 6:30 AM To: SunRay-Users mailing list Subject: Re: [SunRay-Users] Utselect between solaris and linux not working Note that utselect will *never* display hosts outside of the local FOG, is this perhaps what you are seeing? You can run it with the -R option to get a text-input field where you can type a server name, but that's the most you can do to deal with extra-FOG hosts - you can't get a chooser that lists hosts outside of your local FOG. It works fine between any OS platforms. I do this almost daily (although I use utswitch directly, which utselect also uses). -Bob ottomeister wrote: On 2/19/07, Bemis, Suzanna K [EMAIL PROTECTED] wrote: I have SRSS 3.1.1 on 2 Linux sunray servers (pablo and skb-linux) and SRSS 2.0 on Solaris 9 (ndssr01). 'utselect' won't work between a Linux SR server and the solaris 9 server ... In what way doesn't it work? (What do you see when you run it, how do you interact with it, what happens then?) Does it not work in both directions or only in one? What does 'utgstatus' show on these machines? On which of the networks that show in 'utgstatus' is the Sun Ray unit located? Does 'utswitch -h servername' work? OttoM. __ ottomeister Disclaimer: These are my opnions. I
Re: [SunRay-Users] Utselect between solaris and linux not working
5 LAN sessions 1 idles 0 load 0.0 host skb-linux lastseen 0 timeoff -291 addr 86debbb6 numifs 2 period 20 starttime 1172071839 ROUTER LAN_OK interface eth0 ip 86debbb6 mask ff00 bcast 86debbff lastpkt 0 LAN interface eth2 ip c0a88403 mask ff00 bcast c0a884ff lastpkt 600 sessions 0 idles 0 load 0.0 endhosts Connection to localhost closed by foreign host. OUTPUT of 'telnet localhost 7010;gstatus' from SKB-LINUX [EMAIL PROTECTED] sunray]# telnet localhost 7010 Trying 127.0.0.1... Connected to localhost (127.0.0.1). Escape character is '^]'. gstatus numhosts 5 host skb-linux lastseen 18 timeoff 0 addr 86debbb6 numifs 2 period 20 starttime 1172071839 ROUTER LAN_OK TRUSTED interface eth0 ip 86debbb6 mask ff00 bcast 86debbff lastpkt 18 LAN interface eth2 ip c0a88403 mask ff00 bcast c0a884ff lastpkt 18 sessions 1 idles 0 load 0.0 host pablo lastseen 2 timeoff -131 addr 86debb51 numifs 2 period 20 starttime 1172072364 ROUTER LAN_OK interface eth1 ip c0a88402 mask ff00 bcast c0a884ff lastpkt 2 interface eth0 ip 86debb51 mask ff00 bcast 86debbff lastpkt 2 LAN sessions 1 idles 0 load 0.0 host ndssr01 lastseen 3 timeoff 291 addr 86debbd0 numifs 2 period 20 starttime 1172070004 LAN_OK interface eri0 ip 86debbd0 mask ff00 bcast 86debbff lastpkt 3 LAN interface hme0 ip c0a88401 mask ff00 bcast c0a884ff lastpkt 723 LAN sessions 155 idles 62 load 0.4 endhosts Connection closed by foreign host. Thanks, - Suzanna Bemis, Suzanna K wrote: When I bring up 'utselect' gui on the solaris 9 machine I don't expect to see the names of the linux servers. I enter the name of either linux server in the Enter server field and nothing happens at all. No error messages no switching. When I type in 'utswitch -h linuxhost' again nothing happens. No error messages it just returns to the command line. I have all network interfaces in the /etc/hosts files of all three computers and again I don't get any error messages so name resolution is not an issue. The same symptoms, nothing, when I try the the utselect and utswitch from the linux to the solaris 9. 'utgstatus' on Solaris 9 (ndssr01): host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ ndssr01 TN134.222.187.208 U--192.168.132.1 U-- skb-linux -N134.222.187.182 U--192.168.132.3 -AM pablo -N134.222.187.81 U--192.168.132.2 -AM 'utgstatus' on linux (skb-linux): host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ skb-linux TN134.222.187.182 U--192.168.132.3 UAM pablo -N134.222.187.81 U--192.168.132.2 UAM ndssr01 -N134.222.187.208 U--192.168.132.1 --- Pablo is the other linux box. Utswitch and utselect work between linux boxes. Thanks, Suzie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Doolittle Sent: Tuesday, February 20, 2007 6:30 AM To: SunRay-Users mailing list Subject: Re: [SunRay-Users] Utselect between solaris and linux not working Note that utselect will *never* display hosts outside of the local FOG, is this perhaps what you are seeing? You can run it with the -R option to get a text-input field where you can type a server name, but that's the most you can do to deal with extra-FOG hosts - you can't get a chooser that lists hosts outside of your local FOG. It works fine between any OS platforms. I do this almost daily (although I use utswitch directly, which utselect also uses). -Bob ottomeister wrote: On 2/19/07, Bemis, Suzanna K [EMAIL PROTECTED] wrote: I have SRSS 3.1.1 on 2 Linux sunray servers (pablo and skb-linux) and SRSS 2.0 on Solaris 9 (ndssr01). 'utselect' won't work between a Linux SR server and the solaris 9 server ... In what way doesn't it work? (What do you see when you run it, how do you interact with it, what happens then?) Does it not work in both directions or only in one? What does 'utgstatus' show on these machines? On which of the networks that show in 'utgstatus' is the Sun Ray unit located? Does 'utswitch -h servername' work? OttoM. __ ottomeister Disclaimer: These are my opnions. I do not speak for my employer. ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org
Re: [SunRay-Users] Utselect between solaris and linux not working
ottomeister wrote: On 2/21/07, Bob Doolittle [EMAIL PROTECTED] wrote: utadm -l should report everything. Typically there's no point in mixing LAN and Interconnect, however. A cleaner config would be utadm -A 192.168.132.0, as I suggested earlier. That's the right thing to do *IFF* 192.168.132.0 is a properly routed part of the intranet. If 192.168.132.0 truly is an isolated interconnect then telling SRSS otherwise will break everything. Surely not everything. What are you envisioning? From Suzanna's experience with '-L on' and then trying to 'utswitch -h skb-linux' from ndssr01 I'd have to believe that 192.168.132.0 really is an isolated interconnect. I think so too. But I don't see a problem with using -A, what problem do you see? Craig is right that she'll have to use the 192.* addresses instead of the public IP addresses, however. Is this what you were referring to? That's the one advantage to using the Interconnect - it will translate the public IP to the appropriate private one internally. I strongly suspect that Suzanna never restarted SRSS after utadm -L on, otherwise we'd see U for all interfaces on all networks. -Bob Craig -- why do you think it isn't an isolated interconnect? Suzanna -- is this 192.168.132.0 supposed to be reachable from the rest of your network, or is it supposed to be a private isolated subnet? OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
RE: [SunRay-Users] Utselect between solaris and linux not working
I think so too. But I don't see a problem with using -A, what problem do you see? Craig is right that she'll have to use the 192.* addresses instead of the public IP addresses, however. Is this what you were referring to? That's the one advantage to using the Interconnect - it will translate the public IP to the appropriate private one internally. I strongly suspect that Suzanna never restarted SRSS after utadm -L on, otherwise we'd see U for all interfaces on all networks. I ran 'utadm -L on' followed by 'utrestart' on all computers. Last one was on ndssr01 and in fact users this morning were asking who's pablo? So when the utrestart on ndssr01 happened the sunray users lost the connection to 'ndssr01', and 'pablo' appeared on their sunray's. I had to disconnect the 192.168.132.0 network cable from pablo and skb-linux so ndssr01 would be the default. It's good to know that we could run the linux sunray servers, but the point is I need some users to know about the linux servers and use them, but I don't want ALL users to. We're still testing the linux environment in general. Craig asked earilier to try 'utswitch -h 192.168.132.3' on ndssr01 - same result as 'utswitch -h skb-linux' - it went to a 25D and showed 134.222.187.182. And, in answer to OttoM about the private network - 192.168.132.0 is only used for the sunray's. Administration, Internet, etc is done on the 134.222.187.0 network. So what might the 'utadm -A' option do that the 'utadm -a' didn't? All we have on the 192.168.132.0 network are sunray's and these three sunray servers. If you have questions about how the network is set up and routed from a physical perspective I can't answer any of those questions myself but if you tell me what to ask the Networking group I can do that much. All I can say is that I don't want to get an entire new LAN for the linux sunray servers because the infrastructure costs would be more than it's worth. Thanks again and still - Suzie -Bob Craig -- why do you think it isn't an isolated interconnect? Suzanna -- is this 192.168.132.0 supposed to be reachable from the rest of your network, or is it supposed to be a private isolated subnet? OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] Utselect between solaris and linux not working
Note that utselect will *never* display hosts outside of the local FOG, is this perhaps what you are seeing? You can run it with the -R option to get a text-input field where you can type a server name, but that's the most you can do to deal with extra-FOG hosts - you can't get a chooser that lists hosts outside of your local FOG. It works fine between any OS platforms. I do this almost daily (although I use utswitch directly, which utselect also uses). -Bob ottomeister wrote: On 2/19/07, Bemis, Suzanna K [EMAIL PROTECTED] wrote: I have SRSS 3.1.1 on 2 Linux sunray servers (pablo and skb-linux) and SRSS 2.0 on Solaris 9 (ndssr01). 'utselect' won't work between a Linux SR server and the solaris 9 server ... In what way doesn't it work? (What do you see when you run it, how do you interact with it, what happens then?) Does it not work in both directions or only in one? What does 'utgstatus' show on these machines? On which of the networks that show in 'utgstatus' is the Sun Ray unit located? Does 'utswitch -h servername' work? OttoM. __ ottomeister Disclaimer: These are my opnions. I do not speak for my employer. ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] Utselect between solaris and linux not working
First of all, to be sure I'm reading this right, you appear to have *not* configured 134.222.187.0 for Sun Ray (via utadm), and you have configured 192.168.132.0 as an Interconnect (utadm -a interface). You have not enabled LAN (utadm -L on or utadm -A subnet). Is this correct? So, does this mean you have connected all three systems to the Interconnect, even though they are not part of the same FOG? The fact that you don't have the U flag for all interfaces on the 192.168.132.0 subnet is indicative of your problem. It implies that you have a network problem on that subnet which is not forwarding traffic. The fact that you see -AM for the Linux hosts from ndssr01 implies that it *used* to see the Linux hosts on that interface, but no longer does. Try ping'ing the 192.168.132.0 IP addresses from each of your hosts. If you can reach all the hosts, something else is going on. Please send 'utadm -l' output, and also the following: - telnet localhost 7010 (you won't get any response, it will wait for you to issue a command) - type gstatus - cut/paste the output into an e-mail and we'll get a closer look at what's going on -Bob Bemis, Suzanna K wrote: When I bring up 'utselect' gui on the solaris 9 machine I don't expect to see the names of the linux servers. I enter the name of either linux server in the Enter server field and nothing happens at all. No error messages no switching. When I type in 'utswitch -h linuxhost' again nothing happens. No error messages it just returns to the command line. I have all network interfaces in the /etc/hosts files of all three computers and again I don't get any error messages so name resolution is not an issue. The same symptoms, nothing, when I try the the utselect and utswitch from the linux to the solaris 9. 'utgstatus' on Solaris 9 (ndssr01): host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ ndssr01 TN134.222.187.208 U--192.168.132.1 U-- skb-linux -N134.222.187.182 U--192.168.132.3 -AM pablo -N134.222.187.81 U--192.168.132.2 -AM 'utgstatus' on linux (skb-linux): host flagsinterface flagsinterface flags 134.222.187.0/24 192.168.132.0/24 ------ skb-linux TN134.222.187.182 U--192.168.132.3 UAM pablo -N134.222.187.81 U--192.168.132.2 UAM ndssr01 -N134.222.187.208 U--192.168.132.1 --- Pablo is the other linux box. Utswitch and utselect work between linux boxes. Thanks, Suzie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Doolittle Sent: Tuesday, February 20, 2007 6:30 AM To: SunRay-Users mailing list Subject: Re: [SunRay-Users] Utselect between solaris and linux not working Note that utselect will *never* display hosts outside of the local FOG, is this perhaps what you are seeing? You can run it with the -R option to get a text-input field where you can type a server name, but that's the most you can do to deal with extra-FOG hosts - you can't get a chooser that lists hosts outside of your local FOG. It works fine between any OS platforms. I do this almost daily (although I use utswitch directly, which utselect also uses). -Bob ottomeister wrote: On 2/19/07, Bemis, Suzanna K [EMAIL PROTECTED] wrote: I have SRSS 3.1.1 on 2 Linux sunray servers (pablo and skb-linux) and SRSS 2.0 on Solaris 9 (ndssr01). 'utselect' won't work between a Linux SR server and the solaris 9 server ... In what way doesn't it work? (What do you see when you run it, how do you interact with it, what happens then?) Does it not work in both directions or only in one? What does 'utgstatus' show on these machines? On which of the networks that show in 'utgstatus' is the Sun Ray unit located? Does 'utswitch -h servername' work? OttoM. __ ottomeister Disclaimer: These are my opnions. I do not speak for my employer. ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] Utselect between solaris and linux not working
On 2/19/07, Bemis, Suzanna K [EMAIL PROTECTED] wrote: I have SRSS 3.1.1 on 2 Linux sunray servers (pablo and skb-linux) and SRSS 2.0 on Solaris 9 (ndssr01). 'utselect' won't work between a Linux SR server and the solaris 9 server ... In what way doesn't it work? (What do you see when you run it, how do you interact with it, what happens then?) Does it not work in both directions or only in one? What does 'utgstatus' show on these machines? On which of the networks that show in 'utgstatus' is the Sun Ray unit located? Does 'utswitch -h servername' work? OttoM. __ ottomeister Disclaimer: These are my opnions. I do not speak for my employer. ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
