From: fwells12 (fwells12@xxxxxxxxxxx)
Date: Sun Dec 31 2000 - 19:57:17 GMT-3
Thank You. I just needed the additional frame map statements. I had tried
a few but was using the wrong DLCI numbers to reference them. I have been
looking at so many frame scenarios over the last few days I guess I am
getting confused by the mulitude of ways there are to configure the same
outcome.
----- Original Message -----
From: Michael King <kingmi1@yahoo.com>
To: fwells12 <fwells12@hotmail.com>
Sent: Sunday, December 31, 2000 2:10 PM
Subject: Re: More frame relay trouble...
> The way you have it, you should be able to ping from
> hub to every spoke, but not from spoke to spoke. If
> you want to ping from spoke to spoke then you need
> additional frame-relay map statements on each spoke.
> Right now, you only have 1 map statement on each spoke
> mapping to the hub. Here is what it should look like
> to have spoke-to-spoke connectivity. You will notice
> I did a couple of things different. First, on the
> hub, I used frame-relay interface-dlci commands where
> you used frame-relay map statements. Your way is
> fine. I just chose inverse arp (frame-relay
> interface-dlci command) as opposed to static mappings
> (frame-relay map statements). Second, under each
> spoke I used a frame-relay map statement for that
> spokes own IP address. You don't have to put that in
> there but if you don't you will not be able to ping
> yourself.
>
> HUB
> int serial0
> encap frame
> no shut
> int serial0.1 point-to-multipoint
> ip address 10.10.1.1 255.0.0.0
> frame-relay interface-dlci 102
> frame-relay interface-dlci 103
> frame-relay interface-dlci 105
> no shut
>
> SPOKE1
> int serial0
> ip address 10.10.1.2 255.0.0.0
> encap frame
> frame-relay map ip 10.10.1.1 201 broadcast
> frame-relay map ip 10.10.1.2 201 broadcast
> frame-relay map ip 10.10.1.3 201 broadcast
> frame-relay map ip 10.10.1.5 201 broadcast
>
> SPOKE2
> int serial0
> ip address 10.10.1.3 255.0.0.0
> encap frame
> frame-relay map ip 10.10.1.1 301 broadcast
> frame-relay map ip 10.10.1.2 301 broadcast
> frame-relay map ip 10.10.1.3 301 broadcast
> frame-relay map ip 10.10.1.5 301 broadcast
>
> SPOKE3
> int serial0
> ip address 10.10.10.5 255.0.0.0
> encap frame
> frame-relay map ip 10.10.1.1 501 broadcast
> frame-relay map ip 10.10.1.2 501 broadcast
> frame-relay map ip 10.10.1.3 501 broadcast
> frame-relay map ip 10.10.1.5 501 broadcast
>
>
>
>
> --- fwells12 <fwells12@hotmail.com> wrote:
> > Why can't I simply add additional frame relay
> > statements to the spoke =
> > routers to give them spoke-to-spoke reachability? I
> > have tried adding =
> > statements but they do not work. I thought that
> > because router1 knows =
> > how to get to all other routers, you would not have
> > to do anything =
> > additional to the spoke routers except adding the
> > appropriate =
> > frame-relay map statements etc. This is driving me
> > nuts.
> >
> > For example I tried the following statements on
> > router2 and router3:
> > Router2
> > frame-r map ip 10.10.1.3 301 broad =20
> > Router3
> > frame-r map ip 10.10.1.2 201 broad
> >
> > I should now be able to ping each other
> > right?...they do not work!
> >
> >
> >
> > FRAME SWITCH
> > interface Serial0
> > no ip address
> > no ip directed-broadcast
> > encapsulation frame-relay
> > no ip route-cache
> > no ip mroute-cache
> > clockrate 64000
> > frame-relay lmi-type ansi
> > frame-relay intf-type dce
> > frame-relay route 102 interface Serial1 201
> > frame-relay route 103 interface Serial2 301
> > frame-relay route 105 interface Serial3 501
> > !
> > interface Serial1
> > no ip address
> > no ip directed-broadcast
> > encapsulation frame-relay
> > no ip route-cache
> > no ip mroute-cache
> > clockrate 64000
> > frame-relay lmi-type ansi
> > frame-relay intf-type dce
> > frame-relay route 201 interface Serial0 102
> > !
> > interface Serial2
> > no ip address
> > no ip directed-broadcast
> > encapsulation frame-relay
> > no ip route-cache
> > no ip mroute-cache
> > clockrate 64000
> > frame-relay lmi-type ansi
> > frame-relay intf-type dce
> > frame-relay route 301 interface Serial0 103 =20
> > !
> > interface Serial3
> > no ip address
> > no ip directed-broadcast
> > encapsulation frame-relay
> > no ip route-cache
> > no ip mroute-cache
> > clockrate 64000
> > frame-relay lmi-type ansi
> > frame-relay intf-type dce
> > frame-relay route 501 interface Serial0 105 =20
> >
> > ROUTER1 -on serial 0 of frame switch
> > interface Serial0
> > no ip address
> > no ip directed-broadcast
> > encapsulation frame-relay
> > no ip mroute-cache
> > bandwidth 2000
> > no fair-queue
> > frame-relay lmi-type ansi
> > !
> > interface Serial0.1 multipoint
> > ip address 10.10.1.1 255.0.0.0
> > bandwidth 2000
> > frame-relay map ip 10.10.1.2 102 broadcast
> > frame-relay map ip 10.10.1.3 103 broadcast
> > frame-relay map ip 10.10.1.5 105 broadcast
> >
> > ROUTER2 -on serial 1 of frame switch
> > interface Serial0
> > ip address 10.10.1.2 255.0.0.0
> > no ip directed-broadcast
> > encapsulation frame-relay
> > no ip mroute-cache
> > bandwidth 2000
> > frame-relay map ip 10.10.1.1 201 broadcast=20
> > frame-relay lmi-type ansi
> >
> > ROUTER3 -on serial 2 of frame switch
> > interface Serial0
> > ip address 10.10.1.3 255.0.0.0
> > encapsulation frame-relay
> > no ip mroute-cache
> > bandwidth 2000
> > no fair-queue
> > frame-relay map ip 10.10.1.1 301 broadcast
> > frame-relay lmi-type ansi
> >
> > ROUTER5 -on serial 3 of frame switch
> > interface Serial0
> > ip address 10.10.1.5 255.0.0.0
> > no ip directed-broadcast
> > encapsulation frame-relay
> > no ip mroute-cache
> > bandwidth 2000
> > no fair-queue
> > frame-relay map ip 10.10.1.1 501 broadcast=20
> > frame-relay lmi-type ansi
> >
> >
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:26:14 GMT-3