When you utswitch by hostname, it's going to try go public IP, no?

What happens when you run utswitch -h 192.168.132.3 from a Sun Ray connected to ndssr01.



Bemis, Suzanna K wrote:
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?

        CORRECT.  134.222.187.0 is the public network, 192.168.132.0 is
the private Sunray Network.  I ran utadm -a <interface> on each computer
and configured it with it's 192.168.132.x address.
So, does this mean you have connected all three systems to the
Interconnect, even though they are not part of the same FOG?
        
        YES.  But I had not run 'utadm -L on' on any computer until last
night.  Now here's the output from utgstatus on one linux and the
solaris 9.

        AFTER running utadm -L on on all computers

        NDSSR01
host flags interface flags interface flags 134.253.223.0/24 192.168.132.0/24 ------------ ------------------- ------------------- ndssr01 TN 134.222.187.208 UA- 192.168.132.1 UA-

        skb-linux -N    134.222.187.182 UA-    192.168.132.3   -AM

pablo -N 134.222.187.81 UA- 192.168.132.2 -AM
        SKB-LINUX
host flags interface flags interface flags 134.253.223.0/24 192.168.132.0/24 ------------ ------------------- ------------------- skb-linux TN 134.222.187.182 UA- 192.168.132.3 UAM

pablo -N 134.222.187.81 UA- 192.168.132.2 UAM ndssr01 -N 134.222.187.208 UA- 192.168.132.1 -A-
        Now when I run 'utswitch -h skb-linux' from ndssr01 it gets to a
25D, but it's trying it on the 134.222.187.182 address, not the
192.168.132.2.          Then it times out and goes back to my ndssr01
session.  When I run 'utswitch -h ndssr01' from skb-linux, I get no
response, no errors, just returns       to the command line.


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.

        I CAN PING each 192.168.132.x host from each other 192.168.132.x
host.

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

OUTPUT of 'utadm -l' from NDSSR01 LAN connections: 0n
        Subnetwork: 192.168.132.0
                Interface=              hme0 (192.168.132.1)
                Netmask=                255.255.255.0
                Broadcast=              192.168.132.255
                Router=         192.168.132.1
                AuthSrvr=               192.168.132.1
                FirmwareSrvr=   192.168.132.1
                NewTver=
2.0_37.b_114880-07,REV=2004.10.19.12.53
                IP assignment=  124/238 (192.168.132.100)

        OUTPUT from 'utadm -l' on skb-linux:
        LAN connections: 0n
        Subnetwork: 192.168.132.0
                Interface=              eth2 (192.168.132.3)
                Netmask=                255.255.255.0
                Broadcast=              192.168.132.255
                Router=         192.168.132.3
                AuthSrvr=               192.168.132.3
                FirmwareSrvr=   192.168.132.3
                NewTver=                3.1_120879-05_2006.09.20.12.31
                IP assignment=  0/1 (192.168.132.252)
        
        OUTPUT from 'telnet localhost 7010;gstatus' on NDSSR01

        # telnet localhost 7010
        Trying 127.0.0.1...
        Connected to localhost.
        Escape character is '^]'.
        gstatus
        numhosts 5
        host ndssr01 lastseen 5 timeoff 0 addr 86debbd0 numifs 2 period
20 starttime 1172070004 LAN_OK TRUSTED
        interface eri0 ip 86debbd0 mask ffffff00 bcast 86debbff lastpkt
5 LAN
        interface hme0 ip c0a88401 mask ffffff00 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 ffffff00 bcast c0a884ff lastpkt
-1
        interface eth0 ip 86debb51 mask ffffff00 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 ffffff00 bcast 86debbff lastpkt
0 LAN
        interface eth2 ip c0a88403 mask ffffff00 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 ffffff00 bcast 86debbff lastpkt
18 LAN
        interface eth2 ip c0a88403 mask ffffff00 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 ffffff00 bcast c0a884ff lastpkt
2
        interface eth0 ip 86debb51 mask ffffff00 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 ffffff00 bcast 86debbff lastpkt
3 LAN
        interface hme0 ip c0a88401 mask ffffff00 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 flags interface flags interface flags 134.222.187.0/24 192.168.132.0/24 ------------ ------------------- ------------------- ndssr01 TN 134.222.187.208 U-- 192.168.132.1 U--

skb-linux -N    134.222.187.182 U--    192.168.132.3   -AM

pablo -N 134.222.187.81 U-- 192.168.132.2 -AM
'utgstatus' on linux (skb-linux):

host flags interface flags interface flags 134.222.187.0/24 192.168.132.0/24 ------------ ------------------- ------------------- skb-linux TN 134.222.187.182 U-- 192.168.132.3 UAM

pablo     -N    134.222.187.81  U--    192.168.132.2   UAM

ndssr01 -N 134.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 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

Reply via email to