From: kym blair (kymblair@hotmail.com)
Date: Tue Dec 24 2002 - 02:05:36 GMT-3
Jennifer,
The following will work:
R1
!
frame sw
int s0
shut
!
int s2
desc (DTE CABLE) -- CONNECTED TO R2 (DCE)
ip add 100.100.200.1 255.255.0.0
encap frame
frame lmi-type ansi
frame intf-type dce
frame map ip 100.100.200.1 200 bro
frame map ip 100.100.200.2 200 bro
no frame inverse-arp
no shut
!
r2
!
int s0
encap frame
frame lmi-type ansi
clock rate 56000
ip add 100.100.200.2 255.255.0.0
frame map ip 100.100.200.1 200 bro
frame map ip 100.100.200.2 200 bro
no frame inverse-arp
no shut
You can also turn the cable around so the DCE end is on the switch. If you
do that, only move the clock rate from R2 to R1 but do not change any other
command.
R2 can only use DLCI 200 to connect to the frame switch; it cannot connect
via DLCI 200 on through the switch to another router since the switch is
mapping the DLCI, not routing the DLCI.
This config is useful for using your switch as a Backbone router to inject
routes into your network. You could also use the ethernet port to do this.
I haven't tried the following, but I think you could use R1's physical S2
interface to route DLCIs from R2 through to other routers, and use a
subinterface (S2.1 point-to-multipoint) to connect to R2 via DLCI 200. R2
would also use physical S0 to map ip addresses to the DLCIs going to other
routers and would use it's S0.1 point-to-multipoint subinterface to map it's
connection to DLCI 200 to the switch. Should be easy to try.
In other words, R1's S0 would be programmed like a normal switch (frame
route statements) and S0.1 point-to-multipoint would be programmed like the
example above (frame map statements). R2 would use frame map statements on
S0 to establish paths to other routers; R2's S0.1 point-to-multipoint would
be programmed like the example above (also using frame map statements).
You could use point-to-point subinterfaces, but then you couldn't map the ip
addresses to DLCI 200 and would have to rely on inverse-arp.
HTH, Kym
>From: "Jennifer Bellucci" <Jennifer_bellucci@hotmail.com>
>Reply-To: "Jennifer Bellucci" <Jennifer_bellucci@hotmail.com>
>To: <ccielab@groupstudy.com>
>Subject: Frame Relay lost idea
>Date: Tue, 24 Dec 2002 03:39:38 -0000
>
>Hi All...try this
>
>I have the following:
>
>R1-----R2
>
>R1 is the FR Switch and also wants to take part in the FR network like R2.
>I have configured R1 like so
>
>!
>frame sw
>int s0
>clock rate 56000
>encap frame
>frame lmi-type ansi
>frame intf-type dce
>frame route 100 int s2 200
>ip add 100.100.200.1 255.255.0.0
>no shut
>!
>int s2
>desc CONNECTED TO R2
>encap frame
>frame lmi-type ansi
>frame intf-type dce
>frame route 200 int s0 100
>no shut
>!
>
>r2
>!
>int s0
>encap frame
>frame lmi-type ansi
>clock rate 56000
>ip add 100.100.200.2 255.255.0.0
>frame map ip 100.100.200.1 200 bro
>no shut
>!
>
>The ping obviously fails. I know I am doing something fundamentally wrong.
>Is
>the config even possible? I was thinking that as the subnet was attached to
>S0
>on R1-FR then any ping packet would be sent out this interface, in which
>case
>how do I get my config to work? I want to send the ping/all packets on R1
>S0
>to int s2 on the same router.
>*Also, I entered the command "frame map ip 100.100.200.2 100 bro" on R1 S0
>before inserting the frame route statements, made no difference.
>
>Please do not hurl abuse at me ( I've already done that).
>
>Would a possible solution be possible with another serial interface? would
>it
>matter if the interface was connected to a device?
>
>Thanks alot
>
>Jennifer Bellucci
>
>Jennifer_bellucci@hotmail.com
>.
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:52 GMT-3