Seeing Default Gateway on a VAX

[blaked97]

Hello, I was wondering if someone could tell me how to see what the default gateway is assigned to on a VAX?

Thanks.

[blaked97]

VAX/VMS v5.5-2H4

If that's relevant.

[Volker Halle]

Hi,

if you're talking about the defaultTCP/IP gateway, it depends on the TCP/IP stack that's installed.

For the DEC/Compaq/HP UCX/TCPIP product, it's:

$ UCX SHOW ROUTE/PERM

and look at the entry for PN 0.0.0.0

Volker.

[RBrown_1]

Assuming VMS and UCX

$ UCX SHOW ROUTE

On the other hand you could tell us what OS, version, and IP stack and get an exact answer. Try

$ SHOW SYSTEM/NOPROCESS
$ SHOW NETWORK
$ SHOW NETWORK "TCP/IP"/FULL

[RBrown_1]

Obviously I type too slowly. :-(

[blaked97]

Yes I'm talking about the TCP/IP gateway.

The IP next to PN 0.0.0.0 is the IP address of the VAX. (At least, it's the IP address that shows up when I try and ping that VAX from elsewhere in the network).

Maybe I'm asking the wrong question. I'm trying to find the IP address of the router that the VAX communicates through.

Here's what I get:
RMVAX > ucx show route

DYNAMIC database

Type Destination Gateway

AH 127.0.0.1 127.0.0.1
AN 0.0.0.0 170.4.80.10
AN 192.1.11.0 170.4.80.1
AN 170.4.0.0 170.4.80.10

RMVAX > show network
VAX/VMS Network status for local node 5.35 RMVAX on 20-APR-2011 13:51:26.15

The next hop to the nearest area router is node 5.511 RMROUT.


Node Links Cost Hops Next Hop to Node

5.35 RMVAX 0 0 0 (Local) -> 5.35 RMVAX
5.40 STEEL 0 4 1 ISA-0 -> 5.43 CASTER
5.41 BFVAX 1 4 1 ISA-0 -> 5.41 BFVAX
5.42 BOP 0 4 1 ISA-0 -> 5.42 BOP
5.43 CASTER 0 4 1 ISA-0 -> 5.43 CASTER
5.44 BROWNS 0 4 1 ISA-0 -> 5.44 BROWNS
5.45 BMVAX 0 4 1 ISA-0 -> 5.45 BMVAX
5.46 CAVS 0 4 1 ISA-0 -> 5.46 CAVS
5.405 BLMCAS 1 4 1 ISA-0 -> 5.405 BLMCAS
5.511 RMROUT 0 4 1 ISA-0 -> 5.511 RMROUT
5.615 VXRDFC 0 4 1 ISA-0 -> 5.615 VXRDFC

Total of 11 nodes.


Sorry, I know some networking networking, but none really in VMS. I don't really understand what those results mean. Any light you can shed for me would be appreciated.

[Hoff]

This box uses 170.4.80.10 as the IP designated router.

[Steven Schweda]

> VAX/VMS v5.5-2H4

> $ SHOW NETWORK
> $ SHOW NETWORK "TCP/IP"/FULL

At VMS V5.x, SHOW NETWORK provides only
DECnet information.

[Volker Halle]

You can find the IP address of the VAX with:

$ UCX SHOW INTERFACE

And if the IP address shown for AN 0.0.0.0 is the IP address of the VAX, then I guess, that it does NOT have a default gateway defined...

Check with $ UCX SHOW ROUTE/PERM

If there is no default gateway defined, you shouldn't be able to ping that VAX from outside the 170.4.x.x network.

Volker.

[blaked97]

> $ SHOW NETWORK "TCP/IP"/FULL

doesn't work. VMS will take

> $ SHOW NETWORK 'TCPIP'

but not the /FULL and not "TCP/IP". However, SHOW NETWORK 'TCPIP' gives the same thing as SHOW NETWORK.


Also, the 170.4.80.10 is the IP of the box, not any router. I don't know why that comes up next to AN 0.0.0.0 There is a router with the IP 170.4.80.1 and that comes up next to AN 192.1.11.0 when I do a UCX SHOW ROUTE. I suspect 170.4.80.1 is the router it goes through. Why wouldn't this be listed next to AN 0.0.0.0?

[blaked97]

Here's what I get:

RMVAX > ucx show interface
Packets
Interface IP_Addr Network mask Receive Send MTU

ZE0 170.4.80.10 255.255.0.0 7550623 4941312 1500
LO0 127.0.0.1 255.0.0.0 0 0 65535
RMVAX > ucx show route/perm

PERMANENT database

Type Destination Gateway

PN 0.0.0.0 170.4.80.10
PN 170.4.0.0 170.4.80.10
PN 192.1.11.0 170.4.80.1


So the box has IP 170.4.80.10
Apparently it doesn't have a default gateway set then, since it has its own IP next to 0.0.0.0?

What does the line:

PN 192.1.11.0 170.4.80.1

indicate? Like I said, I think 170.4.80.1 is the router it uses, but I don't know what that 192.1.11.0 before it is for.

[RBrown_1 · Accepted solution]

I am guessing that you don't have a gateway outward defined. Can you get out? To google for example?

To define a gateway try something like

UCX SET ROUTE /DEFAULT /GATEWAY=170.4.80.1 /PERMANENT

[Hoff]

Translating those pesky cryptic letter codes...

N --- Network route
H --- Host route
A --- Active
P --- Permanent


The UCX> tool routing-related commands

SHOW ROUTE
SHOW ROUTE /FULL
SHOW ROUTE /FULL /PERMANENT

On those commands that support it, the /FULL qualifier can be key to figuring out what's up.

Establishing routes, or configuring as a router:
CREATE ROUTE ! creates (nukes) routing database
SET ROUTE ! adds a route
SET NOROUTE ! removes a route
START ROUTING ! starts up host-based routing
SET CONFIGURATION -
START [NO]ROUTING ! start routing when UCX starts
STOP ROUTING ! you guessed it...


Setting the gateway

SET ROUTE network_IP_address -
/GATEWAY="gateway" /NETWORK ! network route

SET ROUTE remote_host -
/GATEWAY="gateway" ! host route


The VAX/VMS box can itself (also) be configured as an IP router.


The titles of the two core (V4-vintage manuals are:

"DIGITAL TCP/IP Services for OpenVMS
Management Command Reference"

"DIGITAL TCP/IP Services for OpenVMS
Management"

And yes, if you Google, you can likely find V4.2 versions of these posted, and possibly other versions.

[Steven Schweda]

> > $ SHOW NETWORK "TCP/IP"/FULL
>
> doesn't work. VMS will take
>
> $ SHOW NETWORK 'TCPIP'
>
> but not the /FULL and not "TCP/IP".

Apr 20, 2011 18:59:48 GMT

> At VMS V5.x, SHOW NETWORK provides only
> DECnet information.

I wasn't joking.

> However, SHOW NETWORK 'TCPIP' gives the
> same thing as SHOW NETWORK.

Not amazing, really.

alp $ x := SHOW NETWORK 'TCPIP'
alp $ write sys$output x
SHOW NETWORK


> [...] I'm trying to find the IP address of
> the router that the VAX communicates
> through.

Perhaps the only (useful) gateway/router it
knows is itself.


> What does the line:
>
> PN 192.1.11.0 170.4.80.1
>
> indicate?

Apparently, someone (once) told it to use
170.4.80.1 as the gateway to use to reach
192.1.11.0. (With no apparent netmask, and
with my ignorance of what 192.1.11.0 might
be, I don't know how useful that would be.)

> Like I said, I think 170.4.80.1 is the
> router it uses, but I don't know what that
> 192.1.11.0 before it is for.

That 192.1.11.0 is what it uses 170.4.80.1 as
a gateway to. Whether that makes any sense
is a different question.


Is there some particular gateway/router which
you would like it to use?

If there are useless-looking routes (which
you don't understand), then you might record
them, then delete them, and see what happens.

Is there some actual problem which you are
trying to solve?