Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Computing > Cisco > Frame Relay Lan routing between sites help needed

Reply
Thread Tools

Frame Relay Lan routing between sites help needed

 
 
kjkearney@gmail.com
Guest
Posts: n/a
 
      05-04-2007
Our company recently purchased 4 frame relay circuits and 4 used cisco
1720 routers. The way the frame relay has been set up is 1 host and 3
remotes. I am curretnly working on the host and 1 remote at this
time. I have been able to connect the 2 sites however I cannot figure
out what to do to get the 2 lan networks to see each other.

Router 1 (main site)
~~~~~~~~~~~~~~~~~~~~~~~~
interface FastEthernet0
description CBB Data Ethernet
ip address 10.0.0.69 255.255.254.0
speed 100
full-duplex
!
interface Serial0
bandwidth 1024
no ip address
encapsulation frame-relay
!
interface Serial0.16 point-to-point
description 84th/Pinelake Frame Relay DLCI 16/16
bandwidth 1024
ip address 192.168.168.14 255.255.255.252
frame-relay interface-dlci 16
!
interface Serial0.17 point-to-point
description 84th/Fletcher Frame Relay DLCI 16/17
bandwidth 1024
ip address 192.168.168.6 255.255.255.252
frame-relay interface-dlci 17
!
interface Serial0.18 point-to-point
description 84th/Downtown Frame Relay DLCI 16/18
bandwidth 1024
ip address 192.168.168.10 255.255.255.252
frame-relay interface-dlci 18
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Router 2 (remote site)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
interface FastEthernet0
description 27th Street Data Ethernet
ip address 10.0.10.69 255.255.255.0
speed 100
full-duplex
!
interface Serial0
bandwidth 1024
ip address 192.168.168.5 255.255.255.252
encapsulation frame-relay
frame-relay interface-dlci 16
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

int ser 0.17 on the main site is UP and UP and ser 0 on the remote
site is UP and UP
I can telnet to and from each site using the serial IP addresses.

what am I missing to allow LAN traffic to travel between the two
sites?

I tried adding routes such as on the main site i added
ip route 10.0.10.0 255.255.255.0 192.168.168.5

and on the remote site i added
ip route 0.0.0.0 0.0.0.0 192.168.168.6

but it did not help. I am sure I am missing something simple here but
I just do not know what. I figured after I get this remote working
the others will be easy to follow.

Thank you
KJ

 
Reply With Quote
 
 
 
 
Trendkill
Guest
Posts: n/a
 
      05-04-2007
On May 4, 10:50 am, (E-Mail Removed) wrote:
> Our company recently purchased 4 frame relay circuits and 4 used cisco
> 1720 routers. The way the frame relay has been set up is 1 host and 3
> remotes. I am curretnly working on the host and 1 remote at this
> time. I have been able to connect the 2 sites however I cannot figure
> out what to do to get the 2 lan networks to see each other.
>
> Router 1 (main site)
> ~~~~~~~~~~~~~~~~~~~~~~~~
> interface FastEthernet0
> description CBB Data Ethernet
> ip address 10.0.0.69 255.255.254.0
> speed 100
> full-duplex
> !
> interface Serial0
> bandwidth 1024
> no ip address
> encapsulation frame-relay
> !
> interface Serial0.16 point-to-point
> description 84th/Pinelake Frame Relay DLCI 16/16
> bandwidth 1024
> ip address 192.168.168.14 255.255.255.252
> frame-relay interface-dlci 16
> !
> interface Serial0.17 point-to-point
> description 84th/Fletcher Frame Relay DLCI 16/17
> bandwidth 1024
> ip address 192.168.168.6 255.255.255.252
> frame-relay interface-dlci 17
> !
> interface Serial0.18 point-to-point
> description 84th/Downtown Frame Relay DLCI 16/18
> bandwidth 1024
> ip address 192.168.168.10 255.255.255.252
> frame-relay interface-dlci 18
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Router 2 (remote site)
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> interface FastEthernet0
> description 27th Street Data Ethernet
> ip address 10.0.10.69 255.255.255.0
> speed 100
> full-duplex
> !
> interface Serial0
> bandwidth 1024
> ip address 192.168.168.5 255.255.255.252
> encapsulation frame-relay
> frame-relay interface-dlci 16
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> int ser 0.17 on the main site is UP and UP and ser 0 on the remote
> site is UP and UP
> I can telnet to and from each site using the serial IP addresses.
>
> what am I missing to allow LAN traffic to travel between the two
> sites?
>
> I tried adding routes such as on the main site i added
> ip route 10.0.10.0 255.255.255.0 192.168.168.5
>
> and on the remote site i added
> ip route 0.0.0.0 0.0.0.0 192.168.168.6
>
> but it did not help. I am sure I am missing something simple here but
> I just do not know what. I figured after I get this remote working
> the others will be easy to follow.
>
> Thank you
> KJ


What do your routing tables look like on both sides? You definitely
need static routes or a routing protocol (I'd go with a routing
protocol), and you'll probably need to consider point to point vs.
point to multipoint and split horizon. Source a traceroute or more
from the remote site, does it have routes all the way out? Does the
central site have routes in its table back? Is IP routing enabled on
th remote router so it is routing between its serial and ethernet
interfaces?

 
Reply With Quote
 
 
 
 
Scooby
Guest
Posts: n/a
 
      05-04-2007
<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Our company recently purchased 4 frame relay circuits and 4 used cisco
> 1720 routers. The way the frame relay has been set up is 1 host and 3
> remotes. I am curretnly working on the host and 1 remote at this
> time. I have been able to connect the 2 sites however I cannot figure
> out what to do to get the 2 lan networks to see each other.
>
> Router 1 (main site)
> ~~~~~~~~~~~~~~~~~~~~~~~~
> interface FastEthernet0
> description CBB Data Ethernet
> ip address 10.0.0.69 255.255.254.0
> speed 100
> full-duplex
> !
> interface Serial0
> bandwidth 1024
> no ip address
> encapsulation frame-relay
> !
> interface Serial0.16 point-to-point
> description 84th/Pinelake Frame Relay DLCI 16/16
> bandwidth 1024
> ip address 192.168.168.14 255.255.255.252
> frame-relay interface-dlci 16
> !
> interface Serial0.17 point-to-point
> description 84th/Fletcher Frame Relay DLCI 16/17
> bandwidth 1024
> ip address 192.168.168.6 255.255.255.252
> frame-relay interface-dlci 17
> !
> interface Serial0.18 point-to-point
> description 84th/Downtown Frame Relay DLCI 16/18
> bandwidth 1024
> ip address 192.168.168.10 255.255.255.252
> frame-relay interface-dlci 18
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Router 2 (remote site)
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> interface FastEthernet0
> description 27th Street Data Ethernet
> ip address 10.0.10.69 255.255.255.0
> speed 100
> full-duplex
> !
> interface Serial0
> bandwidth 1024
> ip address 192.168.168.5 255.255.255.252
> encapsulation frame-relay
> frame-relay interface-dlci 16
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> int ser 0.17 on the main site is UP and UP and ser 0 on the remote
> site is UP and UP
> I can telnet to and from each site using the serial IP addresses.
>
> what am I missing to allow LAN traffic to travel between the two
> sites?
>
> I tried adding routes such as on the main site i added
> ip route 10.0.10.0 255.255.255.0 192.168.168.5
>
> and on the remote site i added
> ip route 0.0.0.0 0.0.0.0 192.168.168.6
>
> but it did not help. I am sure I am missing something simple here but
> I just do not know what. I figured after I get this remote working
> the others will be easy to follow.
>
> Thank you
> KJ
>


KJ,

Sounds like you may not have the correct default gateway setup on the
workstations. At each location, you will need to point this setting to the
LAN interface of the local router. Or, if there is another default gateway
at any particular location (maybe an internet connection), you would need
the route back to the frame relay network.

Before testing end to end, try testing workstation to remote router to make
sure you can get that far, then test to a device on the remote lan.

Hope that helps,

Jim


 
Reply With Quote
 
kjkearney@gmail.com
Guest
Posts: n/a
 
      05-04-2007
On May 4, 10:50 am, "Scooby" <(E-Mail Removed)> wrote:
> <(E-Mail Removed)> wrote in message
>
> news:(E-Mail Removed) ups.com...
>
>
>
>
>
> > Our company recently purchased 4 frame relay circuits and 4 used cisco
> > 1720 routers. The way the frame relay has been set up is 1 host and 3
> > remotes. I am curretnly working on the host and 1 remote at this
> > time. I have been able to connect the 2 sites however I cannot figure
> > out what to do to get the 2 lan networks to see each other.

>
> > Router 1 (main site)
> > ~~~~~~~~~~~~~~~~~~~~~~~~
> > interface FastEthernet0
> > description CBB Data Ethernet
> > ip address 10.0.0.69 255.255.254.0
> > speed 100
> > full-duplex
> > !
> > interface Serial0
> > bandwidth 1024
> > no ip address
> > encapsulation frame-relay
> > !
> > interface Serial0.16 point-to-point
> > description 84th/Pinelake Frame Relay DLCI 16/16
> > bandwidth 1024
> > ip address 192.168.168.14 255.255.255.252
> > frame-relay interface-dlci 16
> > !
> > interface Serial0.17 point-to-point
> > description 84th/Fletcher Frame Relay DLCI 16/17
> > bandwidth 1024
> > ip address 192.168.168.6 255.255.255.252
> > frame-relay interface-dlci 17
> > !
> > interface Serial0.18 point-to-point
> > description 84th/Downtown Frame Relay DLCI 16/18
> > bandwidth 1024
> > ip address 192.168.168.10 255.255.255.252
> > frame-relay interface-dlci 18
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

>
> > Router 2 (remote site)
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > interface FastEthernet0
> > description 27th Street Data Ethernet
> > ip address 10.0.10.69 255.255.255.0
> > speed 100
> > full-duplex
> > !
> > interface Serial0
> > bandwidth 1024
> > ip address 192.168.168.5 255.255.255.252
> > encapsulation frame-relay
> > frame-relay interface-dlci 16
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

>
> > int ser 0.17 on the main site is UP and UP and ser 0 on the remote
> > site is UP and UP
> > I can telnet to and from each site using the serial IP addresses.

>
> > what am I missing to allow LAN traffic to travel between the two
> > sites?

>
> > I tried adding routes such as on the main site i added
> > ip route 10.0.10.0 255.255.255.0 192.168.168.5

>
> > and on the remote site i added
> > ip route 0.0.0.0 0.0.0.0 192.168.168.6

>
> > but it did not help. I am sure I am missing something simple here but
> > I just do not know what. I figured after I get this remote working
> > the others will be easy to follow.

>
> > Thank you
> > KJ

>
> KJ,
>
> Sounds like you may not have the correct default gateway setup on the
> workstations. At each location, you will need to point this setting to the
> LAN interface of the local router. Or, if there is another default gateway
> at any particular location (maybe an internet connection), you would need
> the route back to the frame relay network.
>
> Before testing end to end, try testing workstation to remote router to make
> sure you can get that far, then test to a device on the remote lan.
>
> Hope that helps,
>
> Jim- Hide quoted text -
>
> - Show quoted text -


Well the problem is I cannot even ping the FastEthernet IP address of
the remote router from the main router. Until I can get that to
happen workstations will not work either.

I can up load my full configs if someone would be willing to edit them
and show me where I am going wrong at.

 
Reply With Quote
 
Scooby
Guest
Posts: n/a
 
      05-04-2007
<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> On May 4, 10:50 am, "Scooby" <(E-Mail Removed)> wrote:
>> <(E-Mail Removed)> wrote in message
>>
>> news:(E-Mail Removed) ups.com...
>>
>>
>>
>>
>>
>> > Our company recently purchased 4 frame relay circuits and 4 used cisco
>> > 1720 routers. The way the frame relay has been set up is 1 host and 3
>> > remotes. I am curretnly working on the host and 1 remote at this
>> > time. I have been able to connect the 2 sites however I cannot figure
>> > out what to do to get the 2 lan networks to see each other.

>>
>> > Router 1 (main site)
>> > ~~~~~~~~~~~~~~~~~~~~~~~~
>> > interface FastEthernet0
>> > description CBB Data Ethernet
>> > ip address 10.0.0.69 255.255.254.0
>> > speed 100
>> > full-duplex
>> > !
>> > interface Serial0
>> > bandwidth 1024
>> > no ip address
>> > encapsulation frame-relay
>> > !
>> > interface Serial0.16 point-to-point
>> > description 84th/Pinelake Frame Relay DLCI 16/16
>> > bandwidth 1024
>> > ip address 192.168.168.14 255.255.255.252
>> > frame-relay interface-dlci 16
>> > !
>> > interface Serial0.17 point-to-point
>> > description 84th/Fletcher Frame Relay DLCI 16/17
>> > bandwidth 1024
>> > ip address 192.168.168.6 255.255.255.252
>> > frame-relay interface-dlci 17
>> > !
>> > interface Serial0.18 point-to-point
>> > description 84th/Downtown Frame Relay DLCI 16/18
>> > bandwidth 1024
>> > ip address 192.168.168.10 255.255.255.252
>> > frame-relay interface-dlci 18
>> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

>>
>> > Router 2 (remote site)
>> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> > interface FastEthernet0
>> > description 27th Street Data Ethernet
>> > ip address 10.0.10.69 255.255.255.0
>> > speed 100
>> > full-duplex
>> > !
>> > interface Serial0
>> > bandwidth 1024
>> > ip address 192.168.168.5 255.255.255.252
>> > encapsulation frame-relay
>> > frame-relay interface-dlci 16
>> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

>>
>> > int ser 0.17 on the main site is UP and UP and ser 0 on the remote
>> > site is UP and UP
>> > I can telnet to and from each site using the serial IP addresses.

>>
>> > what am I missing to allow LAN traffic to travel between the two
>> > sites?

>>
>> > I tried adding routes such as on the main site i added
>> > ip route 10.0.10.0 255.255.255.0 192.168.168.5

>>
>> > and on the remote site i added
>> > ip route 0.0.0.0 0.0.0.0 192.168.168.6

>>
>> > but it did not help. I am sure I am missing something simple here but
>> > I just do not know what. I figured after I get this remote working
>> > the others will be easy to follow.

>>
>> > Thank you
>> > KJ

>>
>> KJ,
>>
>> Sounds like you may not have the correct default gateway setup on the
>> workstations. At each location, you will need to point this setting to
>> the
>> LAN interface of the local router. Or, if there is another default
>> gateway
>> at any particular location (maybe an internet connection), you would need
>> the route back to the frame relay network.
>>
>> Before testing end to end, try testing workstation to remote router to
>> make
>> sure you can get that far, then test to a device on the remote lan.
>>
>> Hope that helps,
>>
>> Jim- Hide quoted text -
>>
>> - Show quoted text -

>
> Well the problem is I cannot even ping the FastEthernet IP address of
> the remote router from the main router. Until I can get that to
> happen workstations will not work either.
>
> I can up load my full configs if someone would be willing to edit them
> and show me where I am going wrong at.
>


Odd, indeed. And, you are correct, that if you can't get that far, then
workstations are a moot point. I do understand that you can connect serial
to serial okay, so that says connectivity is there. Routing would be my
next guess. From each device you should try 'show ip route' to make sure
that your entries are in the routing table. Also, checking the obvious,
make sure the LAN interfaces are up and that you can ping them from the
local routers.

Please do upload the full configs and also include the following outputs
from each router.

show ip route
show ip int brief
ping 192.168.168.5
ping 192.168.168.6
ping 10.0.0.69
ping 10.0.10.69

Jim




 
Reply With Quote
 
Doug McIntyre
Guest
Posts: n/a
 
      05-04-2007
http://www.velocityreviews.com/forums/(E-Mail Removed) writes:
>Well the problem is I cannot even ping the FastEthernet IP address of
>the remote router from the main router. Until I can get that to
>happen workstations will not work either.


Check to make sure the line protocol is up on your fastethernet on
that side. If line protocol is down, you won't be able to ping.

Otherwise, seeing the 'show route' for each router would be more
helpful than seeing configs at this point.

Doing the static routes that you had listed should work fine.

You seem to have connectivity across the Frame-Relay.



 
Reply With Quote
 
kjkearney@gmail.com
Guest
Posts: n/a
 
      05-05-2007
On May 4, 5:04 pm, Doug McIntyre <(E-Mail Removed)> wrote:
> (E-Mail Removed) writes:
> >Well the problem is I cannot even ping the FastEthernet IP address of
> >the remote router from the main router. Until I can get that to
> >happen workstations will not work either.

>
> Check to make sure the line protocol is up on your fastethernet on
> that side. If line protocol is down, you won't be able to ping.
>
> Otherwise, seeing the 'show route' for each router would be more
> helpful than seeing configs at this point.
>
> Doing the static routes that you had listed should work fine.
>
> You seem to have connectivity across theFrame-Relay.


I think the main thing I am missing is something along the lines of
router rip.

I am not exactly sure ho this works but after adding it to the 2
routers I was able to ping each others router fast ethernet port but
nothing past it.

so in otherwords from router b (remote) i could ping router a's serial
IP, and fast ethernet port but I could not ping anything past it that
was on router a's lan and vise versa.

Anyway here are my full configs.

Router A (main)
---------------------------------
sho run
Building configuration...

Current configuration : 2351 bytes
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname 84RTR01
!
boot-start-marker
boot-end-marker
!
enable password ******
!
memory-size iomem 25
no aaa new-model
ip subnet-zero
!
!
ip domain name domain.com
ip name-server 10.0.0.41
!
ip cef
!
!
!
!
interface FastEthernet0
description CBB Data Ethernet
ip address 10.0.0.69 255.255.254.0
speed 100
full-duplex
!
interface Serial0
bandwidth 1024
no ip address
encapsulation frame-relay
!
interface Serial0.16 point-to-point
description 84th/Pinelake Frame Relay DLCI 16/16
bandwidth 1024
ip address 192.168.168.14 255.255.255.252
frame-relay interface-dlci 16
!
interface Serial0.17 point-to-point
description 84th/Fletcher Frame Relay DLCI 16/17
bandwidth 1024
ip address 192.168.168.6 255.255.255.252
frame-relay interface-dlci 17
!
interface Serial0.18 point-to-point
description 84th/Downtown Frame Relay DLCI 16/18
bandwidth 1024
ip address 192.168.168.10 255.255.255.252
frame-relay interface-dlci 18
!
router rip
network 10.0.0.0
network 192.168.0.0
no auto-summary
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.0.0.1
ip route 10.0.3.0 255.255.255.0 10.0.0.13
ip route 10.0.10.0 255.255.255.0 192.168.168.5
no ip http server
!
snmp-server community public RO
snmp-server community private RW
!
line con 0
line aux 0
line vty 0 4
exec-timeout 0 0
password cbbnet
login
!
end

84RTR01#ping 10.0.0.41

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.41, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
84RTR01#exit

84RTR01#telnet 10.0.10.69
Trying 10.0.10.69 ... Open
---------------------------------

Router B (remote)
---------------------------------
User Access Verification

Password:
27RTR01>en
Password:
27RTR01#sho run
Building configuration...

Current configuration : 1973 bytes
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname 27RTR01
!
boot-start-marker
boot-end-marker
!
enable password *******
!
memory-size iomem 25
no aaa new-model
ip subnet-zero
!
!
ip domain name domain.com
ip name-server 10.0.0.41
!
ip cef
!
!
!
!
interface Loopback0
ip address 192.168.169.6 255.255.255.252
!
interface FastEthernet0
description 27th Street Data Ethernet
ip address 10.0.10.69 255.255.255.0
speed 100
full-duplex
!
interface Serial0
bandwidth 1024
ip address 192.168.168.5 255.255.255.252
encapsulation frame-relay
frame-relay interface-dlci 16
!
router rip
passive-interface FastEthernet0
passive-interface Serial0
--More--   network 10.0.0.0
network 192.168.0.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.168.6
ip route 10.0.0.0 255.255.254.0 192.168.168.6
no ip http server
!
snmp-server community public RO
snmp-server community private RW
snmp-server enable traps tty
!
line con 0
line aux 0
line vty 0 4
exec-timeout 0 0
password cbbnet
login
!
end

27RTR01#ping 10.0.0.69

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.69, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/8 ms
27RTR01#ping 10.0.0.69

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.0.0.41, timeout is 2 seconds:
......
Success rate is 0 percent (0/5)
27RTR01#exit

---------------------------------

Thank you all for your help on this.
KJ

 
Reply With Quote
 
Doug McIntyre
Guest
Posts: n/a
 
      05-06-2007
(E-Mail Removed) writes:
>I think the main thing I am missing is something along the lines of
>router rip.


>I am not exactly sure ho this works but after adding it to the 2
>routers I was able to ping each others router fast ethernet port but
>nothing past it.


The use of a dynamic routing protocol (ie. RIP, EIGRP, OSPF, etc) is
only an aid when you want to not make mistakes doing static routing
across a number of routers out in the field for a network setup like this.
For a 4 note network, I'd prefer to have static routing, a dynamic
routing protocol is overkill for something like that.

If doing RIP makes something work more than before, then you must have
had some static route statements incorrect. I'd still prefer to see a
'show ip route' on each router involved.

*everything* you get with RIP you can do with static routing.

Typically, for this setup, you'd have a default route back to the main
hub on each leaf site. On the hub site, you'd have a static route out
for each leaf LAN network.

The symptoms of being able to ping the remote FastE interface would
point me to looking at the default route out of the leaf site, and/or
the default route setup on a workstation at that leaf site.

 
Reply With Quote
 
kjkearney@gmail.com
Guest
Posts: n/a
 
      05-06-2007
On May 6, 12:28 am, Doug McIntyre <(E-Mail Removed)> wrote:
> (E-Mail Removed) writes:
> >I think the main thing I am missing is something along the lines of
> >router rip.
> >I am not exactly sure ho this works but after adding it to the 2
> >routers I was able to ping each others router fast ethernet port but
> >nothing past it.

>
> The use of a dynamicroutingprotocol (ie. RIP, EIGRP, OSPF, etc) is
> only an aid when you want to not make mistakes doing staticrouting
> across a number of routers out in the field for a network setup like this.
> For a 4 note network, I'd prefer to have staticrouting, a dynamicroutingprotocol is overkill for something like that.
>
> If doing RIP makes something work more than before, then you must have
> had some static route statements incorrect. I'd still prefer to see a
> 'show ip route' on each router involved.
>
> *everything* you get with RIP you can do with staticrouting.
>
> Typically, for this setup, you'd have a default route back to the main
> hub on each leaf site. On the hub site, you'd have a static route out
> for each leaf LAN network.
>
> The symptoms of being able to ping the remote FastE interface would
> point me to looking at the default route out of the leaf site, and/or
> the default route setup on a workstation at that leaf site.


Ok that makes more sense. In that case here is the sho ip route
results from the main router.
84RTR01#sho ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS
level-2
ia - IS-IS inter area, * - candidate default, U - per-user
static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is 10.0.0.1 to network 0.0.0.0

10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks
S 10.0.10.0/24 [1/0] via 192.168.168.5
S 10.0.3.0/24 [1/0] via 10.0.0.13
C 10.0.0.0/23 is directly connected, FastEthernet0
192.168.168.0/30 is subnetted, 1 subnets
C 192.168.168.4 is directly connected, Serial0.17
S* 0.0.0.0/0 [1/0] via 10.0.0.1

and here is the ip route from the remote router
27RTR01#sho ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS
level-2
ia - IS-IS inter area, * - candidate default, U - per-user
static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is 192.168.168.6 to network 0.0.0.0

10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 10.0.10.0/24 is directly connected, FastEthernet0
S 10.0.0.0/23 [1/0] via 192.168.168.6
192.168.168.0/30 is subnetted, 1 subnets
C 192.168.168.4 is directly connected, Serial0
192.168.169.0/30 is subnetted, 1 subnets
C 192.168.169.4 is directly connected, Loopback0
S* 0.0.0.0/0 [1/0] via 192.168.168.6

I hope this is more useful.

KJ

 
Reply With Quote
 
kjkearney@gmail.com
Guest
Posts: n/a
 
      05-07-2007
Just a update.

I have been able to successfully route between the main site and 1
remote site now but when hooking up a 2nd remote site and setting
everything up the same I have a routing loop on the 2nd site and I am
unsure how to fix this.

Any suggestions.

main site
ip route 0.0.0.0 0.0.0.0 10.0.0.1
ip route 10.0.3.0 255.255.255.0 10.0.0.13
ip route 10.0.7.0 255.255.255.0 192.168.168.9
ip route 10.0.10.0 255.255.255.0 192.168.168.5

1st remote site (WORKING)
ip route 0.0.0.0 0.0.0.0 192.168.168.6
ip route 10.0.0.0 255.255.255.0 192.168.168.6

2nd remote site (routing loop)
ip route 0.0.0.0 0.0.0.0 192.168.168.10
ip route 10.0.0.0 255.255.255.0 192.168.168.10

any suggestions on how to fix this considering I will be running into
this same issue once i bring up my 3rd and final one?

KJ



 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
2522 Frame Relay Switch config - 2511 Term Server help needed Jake Peters Cisco 2 08-12-2009 07:28 PM
Dhcp Relay Agent And Acl On Sw 3750, DHCP Relay Agent and ACL on Sw 3750 Vimokh Cisco 3 09-06-2006 02:16 AM
Scenario 5: IS-IS routing on Frame Relay Multi-point and Point-to-Point David Sudjiman Cisco 0 06-08-2006 09:11 AM
Provider MPLS IP-Enabled Frame Relay Cloud Routing Conundrum Scott Cisco 0 12-23-2004 02:13 AM
FRAME-RELAY to PLAIN ENGLISH translation needed !!!.... please :( volatileacid Cisco 1 09-22-2004 01:19 AM



Advertisments