From: Nigel Taylor (nigel_taylor@xxxxxxxxxxx)
Date: Sun Dec 31 2000 - 19:18:31 GMT-3
I think what you're missing is that you HUB already knows how to get to each
of the spokes. In using the
"frame-relay map" command this is normally done to achieve static
connectivity between spokes. So there's no need for this command on the
hub. At the hub or whenever sub-interfaces are used the use of the
"frame-relay interface-dlci" command is required because Inverse ARP will
only resolve to physical interfaces.
This should get things going....
On router1, make these changes...
interface Serial0.1 multipoint
> ip address 10.10.1.1 255.0.0.0
> bandwidth 2000
> frame-relay interface-dlci 102 broadcast
> frame-relay interface-dlci 103 broadcast
> frame-relay interface-dlci 105 broadcast
add these as well... to each of the spoke devices...... 201 for R2,
301 for R3, 501 for R5.
frame-relay map ip 10.10.1.1 <assigned DLCI for this pvc> broadcast
frame-relay map ip 10.10.1.2 <assigned DLCI for this pvc> broadcast
frame-relay map ip 10.10.1.3 <assigned DLCI for this pvc> broadcast
frame-relay map ip 10.10.1.5 <assigned DLCI for this pvc> broadcast
And you would place the required frame map statements in order to achieve
full mesh
connectivity. Also know what happens when using Inverse ARP and the map
commands..
HTH, Folks did I miss anything..?
Nigel...
----- Original Message -----
From: fwells12 <fwells12@hotmail.com>
To: <ccielab@groupstudy.com>
Sent: Sunday, December 31, 2000 4:41 PM
Subject: More frame relay trouble...
> 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