[Info-vax] tcpip gateway question

[jbriggs444]

On Sep 8, 8:30 am, Anton Shterenlikht <me... at bristol.ac.uk> wrote:
> 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.

Which is a big problem.

>
> > > 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
> > > $
>
[snip]
> > 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.

As indicated on the first line, that's a 30 hop traceroute.  It would
have gone another 16 hops if you had not interrupted it.

The key observation is that the very first hop timed out.  You have no
connectivity to the default gateway on the University side.

Your IP is 137.222.187.238
gateway IP is 137.222.187.250

That means that the netmask is unlikely to be the culprit.  With two
IP addresses that close to one another, the netmask on the default
gateway would have to be 255.255.255.240 or narrower to cause
problems.

http://h71000.www7.hp.com/doc/732final/6631/6631pro_001.html

Check interface status with tcpip> ifconfig -a

Check ARP with $ tcpip show arp

If you don't see any ARP entries on the University side, that's a clue
that you're not receiving from it.
Have someone log onto the gateway and see if they see your ARP.  If
not, that's a clue that it's not receiving from you.

You don't have a duplicate IP address (137.222.187.238) do you?  You
didn't steal it from the FreeBSD box by any chance?