«

Thank you all for viewing my message. My company is trying to
implement Private IP over a point to point frame relay. We have 2
routers(1 gateway and 1 FR PIP) in local office and 2 routers(same as
local) at the remote office. The PIP routers were just added. Our
situation is that the PIP router in our office can talk to the PIP
router at our remote office, but our network cannot communicate with
each other. I'm sure that it's a routing table issue, I have done
some research into it, but I don't know how to fix it. If any one can
help that would be great. Here is our topology.

local - Cisco RT 1 (gateway) Cisco RT 2 FR PIP
ethernet 192.168.1.254 192.168.1.2
Frame Relay 206.133.11.35 -

remote - Cisco RT1 (Gateway) Cisco RT 2 FR PIP
ethernet 192.168.2.254 192.168.2.20
Frame Relay 65.250.21.65

Routing Table
Local Cisco RT2 FR PIP
2 connected interfaces
192.168.1.2 eth0/0
206.133.11.35 serial0/0.100
65.250.21.64 via 206.133.11.34 through serial0/0.100
RIP is on 206.133.11.0

Remote Cisco RT2 FR PIP
2 connected interfaces
192.168.2.20 eth0/0
65.250.21.65 serial0/0.100
206.133.11.34 via 65.250.21.64 through serial0/0.100
RIP is on 65.250.21.0


I can ping local Eth of RT2, but not the serial IP
I can not ping remote eth or serial
from local RT2 I can ping any local IP, self eth IP, self serial IP,
and Remote serial IP, but not remote LAN or remote RT2 eth IP
telnet into remote RT2 I can ping remote IP, remote self eth IP,
remote serial IP, local serial IP, but not local eth IP or local LAN.

Do I need to add more static routes?
Do I need to change the routing table on the gateway routers also?
And how do I do that?

Thanks for all your help,

Paul

In article <> ,
(pchee373) wrote:

> Thank you all for viewing my message. My company is trying to
> implement Private IP over a point to point frame relay. We have 2
> routers(1 gateway and 1 FR PIP) in local office and 2 routers(same as
> local) at the remote office. The PIP routers were just added. Our
> situation is that the PIP router in our office can talk to the PIP
> router at our remote office, but our network cannot communicate with
> each other. I'm sure that it's a routing table issue, I have done
> some research into it, but I don't know how to fix it. If any one can
> help that would be great. Here is our topology.
>
> local - Cisco RT 1 (gateway) Cisco RT 2 FR PIP
> ethernet 192.168.1.254 192.168.1.2
> Frame Relay 206.133.11.35 -
>
> remote - Cisco RT1 (Gateway) Cisco RT 2 FR PIP
> ethernet 192.168.2.254 192.168.2.20
> Frame Relay 65.250.21.65

The Frame Relay PVC should be a single subnet, so both routers should
have addresses in the same subnet.

>
> Routing Table
> Local Cisco RT2 FR PIP
> 2 connected interfaces
> 192.168.1.2 eth0/0
> 206.133.11.35 serial0/0.100
> 65.250.21.64 via 206.133.11.34 through serial0/0.100
> RIP is on 206.133.11.0
>
> Remote Cisco RT2 FR PIP
> 2 connected interfaces
> 192.168.2.20 eth0/0
> 65.250.21.65 serial0/0.100
> 206.133.11.34 via 65.250.21.64 through serial0/0.100
> RIP is on 65.250.21.0

RIP won't work between the routers if they're not on a common subnet.

--
Barry Margolin,
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***

Barry Margolin <> wrote in message news:<barmar->...
> In article <> ,
> (pchee373) wrote:
>
> > Thank you all for viewing my message. My company is trying to
> > implement Private IP over a point to point frame relay. We have 2
> > routers(1 gateway and 1 FR PIP) in local office and 2 routers(same as
> > local) at the remote office. The PIP routers were just added. Our
> > situation is that the PIP router in our office can talk to the PIP
> > router at our remote office, but our network cannot communicate with
> > each other. I'm sure that it's a routing table issue, I have done
> > some research into it, but I don't know how to fix it. If any one can
> > help that would be great. Here is our topology.
> >
> > local - Cisco RT 1 (gateway) Cisco RT 2 FR PIP
> > ethernet 192.168.1.254 192.168.1.2
> > Frame Relay 206.133.11.35 -
> >
> > remote - Cisco RT1 (Gateway) Cisco RT 2 FR PIP
> > ethernet 192.168.2.254 192.168.2.20
> > Frame Relay 65.250.21.65
>
> The Frame Relay PVC should be a single subnet, so both routers should
> have addresses in the same subnet.
>
> >
> > Routing Table
> > Local Cisco RT2 FR PIP
> > 2 connected interfaces
> > 192.168.1.2 eth0/0
> > 206.133.11.35 serial0/0.100
> > 65.250.21.64 via 206.133.11.34 through serial0/0.100
> > RIP is on 206.133.11.0
> >
> > Remote Cisco RT2 FR PIP
> > 2 connected interfaces
> > 192.168.2.20 eth0/0
> > 65.250.21.65 serial0/0.100
> > 206.133.11.34 via 65.250.21.64 through serial0/0.100
> > RIP is on 65.250.21.0
>
> RIP won't work between the routers if they're not on a common subnet.

both PIP routers are using 255.255.255.252 subnet and they can talk to each other

Why have you got 206.133.11.25 at one end and 62.250.21.65 at the other? If
it's point-point why not have one or the other? Are you using secondary
addresses?

Maybe best posting parts of your config


"pchee373" <> wrote in message
news: m...
> Thank you all for viewing my message. My company is trying to
> implement Private IP over a point to point frame relay. We have 2
> routers(1 gateway and 1 FR PIP) in local office and 2 routers(same as
> local) at the remote office. The PIP routers were just added. Our
> situation is that the PIP router in our office can talk to the PIP
> router at our remote office, but our network cannot communicate with
> each other. I'm sure that it's a routing table issue, I have done
> some research into it, but I don't know how to fix it. If any one can
> help that would be great. Here is our topology.
>
> local - Cisco RT 1 (gateway) Cisco RT 2 FR PIP
> ethernet 192.168.1.254 192.168.1.2
> Frame Relay 206.133.11.35 -
>
> remote - Cisco RT1 (Gateway) Cisco RT 2 FR PIP
> ethernet 192.168.2.254 192.168.2.20
> Frame Relay 65.250.21.65
>
> Routing Table
> Local Cisco RT2 FR PIP
> 2 connected interfaces
> 192.168.1.2 eth0/0
> 206.133.11.35 serial0/0.100
> 65.250.21.64 via 206.133.11.34 through serial0/0.100
> RIP is on 206.133.11.0
>
> Remote Cisco RT2 FR PIP
> 2 connected interfaces
> 192.168.2.20 eth0/0
> 65.250.21.65 serial0/0.100
> 206.133.11.34 via 65.250.21.64 through serial0/0.100
> RIP is on 65.250.21.0
>
>
> I can ping local Eth of RT2, but not the serial IP
> I can not ping remote eth or serial
> from local RT2 I can ping any local IP, self eth IP, self serial IP,
> and Remote serial IP, but not remote LAN or remote RT2 eth IP
> telnet into remote RT2 I can ping remote IP, remote self eth IP,
> remote serial IP, local serial IP, but not local eth IP or local LAN.
>
> Do I need to add more static routes?
> Do I need to change the routing table on the gateway routers also?
> And how do I do that?
>
> Thanks for all your help,
>
> Paul
>

(pchee373) wrote in message news:< om>...
> Barry Margolin <> wrote in message news:<barmar->...
> > In article <> ,
> > (pchee373) wrote:
> >
> > > Thank you all for viewing my message. My company is trying to
> > > implement Private IP over a point to point frame relay. We have 2
> > > routers(1 gateway and 1 FR PIP) in local office and 2 routers(same as
> > > local) at the remote office. The PIP routers were just added. Our
> > > situation is that the PIP router in our office can talk to the PIP
> > > router at our remote office, but our network cannot communicate with
> > > each other. I'm sure that it's a routing table issue, I have done
> > > some research into it, but I don't know how to fix it. If any one can
> > > help that would be great. Here is our topology.
> > >
> > > local - Cisco RT 1 (gateway) Cisco RT 2 FR PIP
> > > ethernet 192.168.1.254 192.168.1.2
> > > Frame Relay 206.133.11.35 -
> > >
> > > remote - Cisco RT1 (Gateway) Cisco RT 2 FR PIP
> > > ethernet 192.168.2.254 192.168.2.20
> > > Frame Relay 65.250.21.65
> >
> > The Frame Relay PVC should be a single subnet, so both routers should
> > have addresses in the same subnet.
> >
> > >
> > > Routing Table
> > > Local Cisco RT2 FR PIP
> > > 2 connected interfaces
> > > 192.168.1.2 eth0/0
> > > 206.133.11.35 serial0/0.100
> > > 65.250.21.64 via 206.133.11.34 through serial0/0.100
> > > RIP is on 206.133.11.0
> > >
> > > Remote Cisco RT2 FR PIP
> > > 2 connected interfaces
> > > 192.168.2.20 eth0/0
> > > 65.250.21.65 serial0/0.100
> > > 206.133.11.34 via 65.250.21.64 through serial0/0.100
> > > RIP is on 65.250.21.0
> >
> > RIP won't work between the routers if they're not on a common subnet.
>
> both PIP routers are using 255.255.255.252 subnet and they can talk to each other

I assume from the IP addresses of the FR links (and from previous
comments) that the FR network "breaks out" into some intermediate
network somewhere.

The two private networks can't talk because neither appears in the
routing table at the remote end, so you were correct in your
assumption that it is a routing table issue. The first question that I
have is :- are private address ranges allowed across your FR network?

Pete

"Neil" <> wrote in message news:<ce3c0s$27b$>...
> Why have you got 206.133.11.25 at one end and 62.250.21.65 at the other? If
> it's point-point why not have one or the other? Are you using secondary
> addresses?
>
> Maybe best posting parts of your config
>
>
The 206.133.11.25 255.255.255.252 and the 63.250.21.65
255.255.255.252 were IP's given to us by the ISP(MCI). Those 2
routers CAN talk to each other,

I can ping local Eth of RT2 from a LAN computer, but not the serial IP
> > I can not ping remote eth or serial
> > from local RT2 I can ping any local IP, self eth IP, self serial IP,
> > and Remote serial IP, but not remote LAN or remote RT2 eth IP
> > telnet into remote RT2 I can ping remote IP, remote self eth IP,
> > remote serial IP, local serial IP, but not local eth IP or local LAN.

Thanks
Paul

In article <> ,
(pchee373) wrote:

> "Neil" <> wrote in message
> news:<ce3c0s$27b$>...
> > Why have you got 206.133.11.25 at one end and 62.250.21.65 at the other? If
> > it's point-point why not have one or the other? Are you using secondary
> > addresses?
> >
> > Maybe best posting parts of your config
> >
> >
> The 206.133.11.25 255.255.255.252 and the 63.250.21.65
> 255.255.255.252 were IP's given to us by the ISP(MCI). Those 2
> routers CAN talk to each other,

How is an ISP involved? Your original post said that this was a frame
relay connection between your two sites. Are they actually frame relay
connections to the ISP POPs?

--
Barry Margolin,
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***