From: Fanglo MA (fangloma@xxxxxxxxxxxxxx)
Date: Fri Aug 02 2002 - 08:49:50 GMT-3
Wow! How you reach it!!? You are really best on how to apply tunnel. Any
source/reference would you recommend?
Regards,
Fanglo
On Fri, 2 Aug 2002, kym blair wrote:
> Harbir, try this method of building a frame-relay switch from two 2501
> routers (assuming FRS1 and FRS2 are connected S0-to-S0 as in your first
> attempt, and routers are connected to S1 on each FRS):
>
> FRS1
> _____
>
> frame-relay switching
> !
> interface Tunnel12
> no ip address
> tunnel source Serial0
> tunnel destination 12.12.12.2
> !
> interface Serial0
> ip address 12.12.12.1 255.255.255.0
> !
> interface Serial1
> no ip address
> encapsulation frame-relay
> clockrate 2000000
> frame-relay intf-type dce
> frame-relay route 104 interface Tunnel12 401
>
>
>
> FRS2
> ---------
> frame-relay switching
> !
> interface Tunnel12
> no ip address
> tunnel source Serial0
> tunnel destination 12.12.12.1
> !
> interface Serial0
> ip address 12.12.12.2 255.255.255.0
> !
> interface Serial1
> no ip address
> encapsulation frame-relay
> clockrate 2000000
> frame-relay intf-type dce
> frame-relay route 104 interface Tunnel12 401
>
> --------------------------------------------------------------
> --------------------------------------------------------------
> Or E0-E0 back-to-back with full-mesh DLCIs would allow you to connect up to
> 4 routers with any combination of point-to-point or multipoint:
>
> FRS1
> _____
>
> frame-relay switching
> !
> Ethernet 0
> ip address 192.168.1.1 255.255.255.0
> !
> ip classless
> ip subnet-zero
> ip route 0.0.0.0 0.0.0.0 192.168.1.2
> !
> interface Loopback13
> ip address 132.173.13.1 255.255.255.0
> !
> interface Tunnel13
> no ip address
> tunnel source Loopback13
> tunnel destination 132.173.13.2
> !
> interface Loopback14
> ip address 132.173.14.1 255.255.255.0
> !
> interface Tunnel14
> no ip address
> tunnel source Loopback14
> tunnel destination 132.173.14.2
> !
> interface Loopback23
> ip address 132.173.23.1 255.255.255.0
> !
> interface Tunnel23
> no ip address
> tunnel source Loopback23
> tunnel destination 132.173.23.2
> !
> interface Loopback24
> ip address 132.173.24.1 255.255.255.0
> !
> interface Tunnel24
> no ip address
> tunnel source Loopback24
> tunnel destination 132.173.24.2
> !
> !
> interface Serial0
> no ip address
> encapsulation frame-relay
> clockrate 2000000
> frame-relay intf-type dce
> frame-relay route 102 interface serial1 201
> frame-relay route 103 interface Tunnel13 111
> frame-relay route 104 interface Tunnel14 444
> !
> interface Serial1
> no ip address
> encapsulation frame-relay
> clockrate 2000000
> frame-relay intf-type dce
> frame-relay route 201 interface Serial0 102
> frame-relay route 203 interface Tunnel23 333
> frame-relay route 204 interface Tunnel24 222
>
>
> FRS2
> ---------
> frame-relay switching
> !
> Ethernet 0
> ip address 192.168.1.2 255.255.255.0
> !
> ip classless
> ip subnet-zero
> ip route 0.0.0.0 0.0.0.0 192.168.1.1
> !
> interface Loopback13
> ip address 132.173.13.2 255.255.255.0
> !
> interface Tunnel13
> no ip address
> tunnel source Loopback13
> tunnel destination 132.173.13.1
> !
> interface Loopback14
> ip address 132.173.14.2 255.255.255.0
> !
> interface Tunnel14
> no ip address
> tunnel source Loopback14
> tunnel destination 132.173.14.1
> !
> interface Loopback23
> ip address 132.173.23.2 255.255.255.0
> !
> interface Tunnel23
> no ip address
> tunnel source Loopback23
> tunnel destination 132.173.23.1
> !
> interface Loopback24
> ip address 132.173.24.2 255.255.255.0
> !
> interface Tunnel24
> no ip address
> tunnel source Loopback24
> tunnel destination 132.173.24.1
> !
> interface Serial0
> no ip address
> encapsulation frame-relay
> clockrate 2000000
> frame-relay intf-type dce
> frame-relay route 401 interface Tunnel14 444
> frame-relay route 402 interface Tunnel24 222
> frame-relay route 403 interface Serial1 304
> !
> interface Serial1
> no ip address
> encapsulation frame-relay
> clockrate 2000000
> frame-relay intf-type dce
> frame-relay route 301 interface Tunnel13 111
> frame-relay route 302 interface Tunnel23 333
> frame-relay route 304 interface Serial0 403
>
>
> That's it for the frame-relay switch. Now you have to config the routers.
> This is a good drill, but really recommend you buy a router with 4 or more
> serial ports to be your frame-relay switch.
>
> HTH, Kym
>
>
>
>
> >From: "Fanglo MA \(E-mail\)" <fangloma@pacific.net.hk>
> >Reply-To: "Fanglo MA \(E-mail\)" <fangloma@pacific.net.hk>
> >To: "'Kohli, Harbir'" <harbir.kohli@bellnexxia.com>,
> ><ccielab@groupstudy.com>
> >Subject: RE: Frame-relay switching
> >Date: Fri, 2 Aug 2002 08:53:29 +0800
> >
> >Try no keepalive. May be it can be help.
> >
> >http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120
> >t/120t5/frkeep.htm
> >
> >Regards,
> >Fanglo
> >
> >-----Original Message-----
> >From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> >Kohli, Harbir
> >Sent: Thursday, August 01, 2002 9:16 PM
> >To: 'ccielab@groupstudy.com'
> >Subject: RE: Frame-relay switching
> >
> >
> >Hi,
> >
> >I am trying to create a frame-relay cloud by using 2 routers (FRS1 and
> >FRS2)
> >
> >
> >I am not able to get frame-relay switching to work over the cloud.
> >
> >I have 2 routers connected one to FRS1 and another to FRS2).
> >FRS1
> >_____
> >
> >...
> >frame-relay switching
> >!
> >interface Tunnel12
> >no ip address
> >tunnel source Serial0
> >tunnel destination 12.12.12.2
> >!
> >interface Serial0
> >ip address 12.12.12.1 255.255.255.0
> >!
> >interface Serial1
> >no ip address
> >encapsulation frame-relay
> >frame-relay intf-type dce
> >frame-relay route 104 interface Tunnel12 401
> >!
> >FRS2
> >---------
> >
> >..
> >frame-relay switching
> >interface Serial0
> >ip address 23.23.23.2 255.255.255.0
> >interface Serial1
> >no ip address
> >encapsulation frame-relay
> >clockrate 2000000
> >frame-relay intf-type dce
> >frame-relay route 401 interface Tunnel12 104
> >
> >FRS2#sh frame pvc
> >
> >PVC Statistics for interface Serial1 (Frame Relay DCE)
> >
> >DLCI = 401, DLCI USAGE = SWITCHED, PVC STATUS = INACTIVE, INTERFACE =
> >Serial1
> >
> >What is it that I am missing?
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:14 GMT-3