[Info-vax] tcpip gateway question

Anton Shterenlikht mexas at bristol.ac.uk
Tue Sep 8 08:30:14 EDT 2009


On Tue, Sep 08, 2009 at 04:37:25AM -0700, H Vlems wrote:
> On 8 sep, 12:31, Anton Shterenlikht <me... at bristol.ac.uk> wrote:
> > I've a VMS cluster on a local 10.10.10.0/24 network.
> >
> > I'm trying to set up one of the VMS nodes
> > to also sit on the University network 137.222.0.0/16.
> >
> > So I used tcpip$config and configured the two interfaces as:
> >
> >    1  -  WE0 Menu (EWA0: TwistedPair 100mbps)
> >    2  -  137.222.187.238/16  mech-cluster238       Configured,Active          
> >
> >    3  -  WE1 Menu (EWB0: TwistedPair 100mbps)
> >    4  -  10.10.10.1/24       vav                   Configured,Active          
> >
> > I added the default University gateway, 137.222.187.250, and
> > name servers 137.222.10.36 and 137.222.10.39 with tcpip$config
> > options
> >                  3  -  Routing              
> >                  4  -  BIND Resolver        
> >
> > I've ssh server and client enabled on this node.
> >
> > My problem is that I cannot even ping the gateway.
> >
> > Does this look reasonable:
> >
> > $ tcpip show route
> >
> >                              DYNAMIC
> >
> > Type           Destination                           Gateway
> >
> > AN    0.0.0.0                               137.222.187.250
> > AN    10.10.10.0/24                         10.10.10.1
> > AH    10.10.10.1                            10.10.10.1
> > AH    127.0.0.1                             127.0.0.1
> > AN    137.222.0.0/16                        137.222.187.238
> > AH    137.222.187.238                       137.222.187.238
> > $
> >
> > many thanks for any advice or a link to a relevant manual.
> >
> > --
> > Anton Shterenlikht
> > Room 2.6, Queen's Building
> > Mech Eng Dept
> > Bristol University
> > University Walk, Bristol BS8 1TR, UK
> > Tel: +44 (0)117 331 5944
> > Fax: +44 (0)117 331 5924
> 
> Anton,
> the 10.10.10.0 network is reachable with this configuration?
> What is the output of:  traceroute 137.222.187.250?

Hans,

yes, 10.10.10.0 network seems to be completely fine. I can
connect to any node with ssh and ping any local node from any node
on the local network, e.g.:

$ ping 10.10.10.8 
PING 10.10.10.8 (10.10.10.8): 56 data bytes
64 bytes from 10.10.10.8: icmp_seq=0 ttl=64 time=1 ms
64 bytes from 10.10.10.8: icmp_seq=1 ttl=64 time=0 ms
64 bytes from 10.10.10.8: icmp_seq=2 ttl=64 time=0 ms
64 bytes from 10.10.10.8: icmp_seq=3 ttl=64 time=0 ms


----10.10.10.8 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 0/0/1 ms
$ ping 10.10.10.31
PING 10.10.10.31 (10.10.10.31): 56 data bytes
64 bytes from 10.10.10.31: icmp_seq=0 ttl=64 time=0 ms
64 bytes from 10.10.10.31: icmp_seq=1 ttl=64 time=0 ms
64 bytes from 10.10.10.31: icmp_seq=2 ttl=64 time=0 ms
64 bytes from 10.10.10.31: icmp_seq=3 ttl=64 time=0 ms


----10.10.10.31 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 0/0/0 ms
$ 


But trying to reach the gateway I end up with this:


$ tcpip traceroute 137.222.187.250
traceroute to vav (137.222.187.250): 1-30 hops, 38 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14 
 Cancel 

(interrupt)
$ 

the process doesn't seem to end, so I terminated it.


My configuration is actually more complex. Here's an
illustration, explanation below.

-----------UNiversity network-----------------------------
        ^                             ^
        |                             |
   +--------+                    +--------+
   | VMS    |                    | FreeBSD|
   | node A |                    | rx2600 |
   +--------+                    +--------+
        |                             |
        V                             V
------------local network--------------------------------
      ^                        ^               ^
      |                        |               |
   +--------+             +--------+      +---------+
   | VMS    |             | VMS    |      | VMS     |
   | node B |             | node C |      | node D  |
   +--------+             +--------+      +---------+

Nodes A, B, C, D form VMS cluster.

Connections to the cluster nodes B, C, D via FBSD in and out
work fine. But I'm having trouble setting up node A.
 

Until now I've had a 3-node VMS cluster B, C, D
on the local network. I connect to the
cluster via a FreeBSD frontend with port forwarding.
This FreeBSD frontend acts as a gateway for all VMS
nodes to access the University network and beyond.
This works fine. I set gateway to the ip address of 
the local facing interface on FreeBSD box, 10.10.10.31,
and the outgoing and incoming connections to and
from the local network pass fine.

This is a an example, pinging the Univerisity gateway:

$ tcpip ping 137.222.187.250
PING 137.222.187.250 (137.222.187.250): 56 data bytes
64 bytes from 137.222.187.250: icmp_seq=0 ttl=254 time=2 ms
64 bytes from 137.222.187.250: icmp_seq=1 ttl=254 time=8 ms
64 bytes from 137.222.187.250: icmp_seq=2 ttl=254 time=1 ms
64 bytes from 137.222.187.250: icmp_seq=3 ttl=254 time=1 ms


----137.222.187.250 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 1/3/8 ms
$
$ tcpip show route
  
                             DYNAMIC
  
Type           Destination                           Gateway
  
AN    0.0.0.0                               10.10.10.31
AN    0.0.0.0                               10.10.10.31
AN    10.10.10.0/24                         10.10.10.7
AN    10.10.10.0/24                         10.10.10.6
AH    10.10.10.6                            10.10.10.6
AH    10.10.10.7                            10.10.10.7
AH    10.10.10.106                          10.10.10.106
AH    10.10.10.107                          10.10.10.107
AH    127.0.0.1                             127.0.0.1


Now this FreeBSD frontend is, of course, a single point of
failure, so if it's down I cannot reach the local
network. So I wanted to add a second frontend, an alpha
node A, and at the same time use it as a member of my VMS
cluster. And this is where I'm stuck.

It might be important to mention that setting router
or BIND resolve servers on node A via tcpip$config
takes very long time, typically several minutes.
This usually is an indication of some misconfiguration,
but what?

many thanks

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 331 5924




More information about the Info-vax mailing list