[Info-vax] SOLVED: Re: tcpip gateway question

[Anton Shterenlikht]

On Tue, Sep 15, 2009 at 04:53:45AM -0700, H Vlems wrote:
> On 15 sep, 13:08, Anton Shterenlikht <me... at bristol.ac.uk> wrote:
> > On Wed, Sep 09, 2009 at 12:54:32AM +0000, John Santos wrote:
> > > In article <mailman.12.1252413824.17612.info-vax_rbnsn.... at rbnsn.com>,
> > > me... at bristol.ac.uk says...>
> > > > On Tue, Sep 08, 2009 at 11:36:48AM +0000, John Santos wrote:
> > > > > In article <mailman.10.1252405909.17612.info-vax_rbnsn.... at rbnsn.com>,
> > > > > me... at bristol.ac.uk says...>
> > > > > > 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.
> >
> > > > > Your net mask is almost certainly wrong. ?No one has a class B on an
> > > > > ethernet segment anymore! ?My guess is you can't see the name servers
> > > > > because your VMS system is trying to send directly to them and it
> > > > > needs to go through your router.
> >
> > > > > Can you ping the router (137.222.187.250) by address? ?If not,
> > > > > your LAN might be subnetted to smaller than a /24 and you should
> > > > > have a local router to get to the rest of it. ?But most likely,
> > > > > your netmask should be 255.255.255.0 (/24). ?Ask your network
> > > > > people...
> >
> > > > John, thank you.
> >
> > > > Yes, the netmask should be /24, I just confirmed this with my
> > > > networks administrator. I changed the configuration, but the
> > > > result is still the same.
> >
> > > In another followup, you posted the output of ipconfig and it
> > > looked like the netmask had been fixed, but there was still
> > > something funny about the broadcast addresses.
> >
> > > Both interfaces had a broadcast address of 137.222.255.255,
> > > IIRC. ?You had noticed that this seemed bogus for the 10.10.10.0
> > > network (should be 10.10.10.255, since it's a /24), but
> > > also it is wrong for the 137.222.187.0 network (it should be
> > > 137.222.187.255 since it's also a /24.) ?But I don't know
> > > what effect this would have. ?Anyone know if it could possible
> > > be breaking ARP?
> >
> > > I have noticed in the past that if you muck around trying to
> > > fix IP configuration stuff in UCX (aka "Hewlitt-Packard
> > > Transmission Control Protocol/Internet Protocol Services for
> > > OpenVMS", no wonder everyone calls it by the obsolete "UCX"
> > > name :-) :-) :-)) it doesn't always reset everything correctly,
> > > but if you totally shut down and reboot, it does. ?So you can
> > > think you've got everything set up correctly (and you're right),
> > > but some little difference bites you back. ?I've always found
> > > these things (like the broadcast mask being wrong) can be fixed
> > > without rebooting, but many times the problem isn't obvious!
> >
> > I rebooted this node several times, no change.
> >
> > In addition to my previous MAC change observation, I discovered
> > that all nodes in the cluster have their current MAC addresses
> > for the first interface, either EWA0 (alpha) or EIA0 (i64) changed
> > to a range of incremental MAC numbers from AA-00-04-00-03-08 to
> > -06-08 (4 nodes). However, all MAC addresses for second interfaces,
> > EWB0 or EIB0 are left at default settings.
> >
> > I'm really puzzled by this. Is this an expected behaviour?
> > Is this something to do with VMS cluster or DECnet?
> > Can I insist that the current MAC address for a particular
> > interface is left as default setting?
> >
> > 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- Tekst uit oorspronkelijk bericht niet weergeven -
> >
> > - Tekst uit oorspronkelijk bericht weergeven -
> 
> The MAC address change is a DECnet feature. In fact its behaviour
> changed somewhat.
> A DECnet address is a host property. The MAC address of all ethernet
> (and FDDI or tokenring) interfaces were changed. This didn't work well
> when networks got bigger. So now only one adapter gets changed.
> The algorthm is fairly simple. All DECnet addresses start with
> AA-00-04-00-wx-yz, where AA-00-04 designates the owner organisation
> (once DEC, now HP).
> A DECnet address is 16 bits, so the fourth byte is set to zero. The
> lower two bytes are computed as follows: <area>*1024 + <hostaddress>.
> Convert the result to HEX and swap the bytes.
> The DECnet address is retrieved as follows. Reverse wx and yz: YZWX
> and convert to decimal. MOD 1024 returns the address and DIV 1024
> returns the area.
> example: AA-00-04-00-03-08 -> 0803 (HEX) -> DECnet address 2.3

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=255 time=1 ms
64 bytes from 137.222.187.250: icmp_seq=1 ttl=255 time=1 ms
64 bytes from 137.222.187.250: icmp_seq=2 ttl=255 time=0 ms
64 bytes from 137.222.187.250: icmp_seq=3 ttl=255 time=0 ms


----137.222.187.250 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 0/0/1 ms
TCPIP>

I used the static MAC addressed of the second interface.
All seems fine now.

My error was not reading DECnet plus manuals carefully, and
assuming static MAC for the first interface.

Many thanks to all correspondents

--
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