HP3000-L Archives

January 1999, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Simpkins, Terry" <[log in to unmask]>
Reply To:
Simpkins, Terry
Date:
Fri, 29 Jan 1999 15:46:29 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (46 lines)
We are attempting to add a second gateway to our 3000.

Each of our remote sites has it's own unique (legal) class C address.
Somce of these are part of the class B address our parent company has, and some
are individually registered class C addresses.

The new gateway will be used to access one site, which has one of the
class B addresses assigned to it.
Here is how we have the gateways defined:  (addresses are ficticious)

Gateway:  Local1     address  222.333.444.017   (this is the one we have always had)
Configured Reachable Networks
IP NETWORK ADDRESS      IP MASK         Hops
-----------------------------------             ------------------------------  -------
B 111.222.333.000               255.255.255.0           4
B 111.222.334.000               255.255.255.0           4
C 222.333.445.000               255.255.255.0           4
B 111.222.088.000               255.255.255.0           4
B 111.222.123.000               255.255.255.0           4

This configuration has been working fine for a couple of years.  Access to all of the remote
sites was across a single router connected to our Frame Relay network.

Now we are adding another router to another location, and have added the new gateway.
Gateway:  threecom    address  222.333.444.008
Configured Reachable Networks
IP NETWORK ADDRESS      IP MASK         Hops
-----------------------------------             ------------------------------  -------
B 111.222.444.000               255.255.255.0           4

We can't PING the remote router.  NETTOOL says the 3000 is trying to reach the node
using the "local1" gateway instead of the "threecom" gateway.  I thought the MASK
of 255.255.255.0 would force the match to the "C" address, but apparantly is doesn't.
We have been unable to get the "B" in front of the address to change to a "C" (I assume this
is because of the defined ranges for "B" addresses).
As a short-term fix, we have changed the remote address from 111.222.444 to 222.222.444
and we are able to get to it.

Any ideas how to fix this since we really want to give the remote site the correct address.
*******************************
Terry W. Simpkins
Director ISIT
Lucas Control Systems
[log in to unmask]
*******************************

ATOM RSS1 RSS2