Go it! On Tue, Jul 27, 2010 at 9:05 PM, Marko Milivojevic <[email protected]>wrote:
> It doesn't change. You always need to match DLCIs on both ends of the > link. GRE tunnel is simply tunneling the traffic between serial > interfaces, as if they were directly connected. > > -- > Marko Milivojevic - CCIE #18427 > Senior Technical Instructor - IPexpert > > YES! We include 400 hours of REAL rack > time with our Blended Learning Solution! > > Mailto: [email protected] > Telephone: +1.810.326.1444 > Fax: +1.810.454.0130 > Web: http://www.ipexpert.com/ > > On Tue, Jul 27, 2010 at 19:00, Abel ... <[email protected]> wrote: > > Thanks everyone is working now, I din't realize that the logic in > > frame-relay route change if I use FR Switching over GRE. > > Thanks for help. Now I have my full home lab. > > > > On Tue, Jul 27, 2010 at 8:45 PM, m.lammerse <[email protected]> wrote: > >> > >> Hi Abel, > >> I think this is simply a matter of mismatching dlcis. I quickly labbed > >> this up and it works fine, as you said > >> R1(s1/0)----(s1/0)R2(s1/1)----(s1/0)R3(s1/1)----(s1/0)R4 > >> R2 and R3 are FR switches > >> R2#sh frame route > >> Input Intf Input Dlci Output Intf Output Dlci Status > >> Serial1/0 104 Tunnel23 204 active > >> Tunnel23 204 Serial1/0 104 active > >> R2# > >> R3#sh frame route > >> Input Intf Input Dlci Output Intf Output Dlci Status > >> Serial1/1 104 Tunnel23 204 active > >> Tunnel23 204 Serial1/1 104 active > >> R3# > >> R1#ping 172.16.14.4 repeat 100 > >> Type escape sequence to abort. > >> Sending 100, 100-byte ICMP Echos to 172.16.14.4, timeout is 2 seconds: > >> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > >> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > >> Success rate is 100 percent (100/100), round-trip min/avg/max = 4/38/208 > >> ms > >> R1#sh frame map > >> Serial1/0 (up): ip 172.16.14.4 dlci 104(0x68,0x1880), dynamic, > >> broadcast,, status defined, active > >> R1# > >> R4#sh frame map > >> Serial1/0 (up): ip 172.16.14.1 dlci 104(0x68,0x1880), dynamic, > >> broadcast,, status defined, active > >> R4# > >> My configs are attached. > >> cheers, > >> Marcel > >> On 28 Jul, 2010,at 11:18 AM, "m.lammerse" <[email protected]> wrote: > >> > >> Looking at the Cisco example, the DLCI between the two fr switches is > >> identical, whereas yours seems to be different. I.e. > >> On FR1 > >> Tunnel0 201 Serial0/0/0 102 active > >> Tunnel0 203 Serial0/0/1 302 active > >> Tunnel0 204 Serial0/1/0 402 active > >> Tunnel0 205 Serial0/1/1 502 active > >> Tunnel0 206 Serial0/2/0 602 active > >> Tunnel0 211 Serial0/0/0 112 active > >> On FR2 > >> interface Serial0/2/0 > >> description Connected to R2 > >> no ip address > >> encapsulation frame-relay > >> frame-relay intf-type dce > >> frame-relay route 201 interface Tunnel0 102 <-- > >> frame-relay route 203 interface Tunnel0 302 <-- > >> frame-relay route 204 interface Tunnel0 402 <-- > >> frame-relay route 205 interface Tunnel0 502 <-- > >> frame-relay route 206 interface Tunnel0 602 <-- > >> Don't these DLCIs need to match? > >> On 28 Jul, 2010,at 10:47 AM, "m.lammerse" <[email protected]> wrote: > >> > >> Great, you learn something new everyday :) > >> is your tunnel interface up/up? can you post a show inter tunnel0? > >> > >> On 28 Jul, 2010,at 10:23 AM, "Abel ..." <[email protected]> wrote: > >> > >> I don't is a cli-issue, cisco even have a clear documentation about how > to > >> do it > >> > >> > http://www.cisco.com/en/US/docs/ios/wan/configuration/guide/wan_cfg_frm_rly_ps6441_TSD_Products_Configuration_Guide_Chapter.html#wp1065347 > >> The logic behind of this is a FR header+payload inside an Ethernet | IP > >> with the FRHeader+payload as a payload of the IP data. I configure this > >> stuff a lot of years ago with two 2501 with tunnel interface over > ethernet > >> and work perfectly > >> > >> On Tue, Jul 27, 2010 at 7:11 PM, m.lammerse <[email protected]> wrote: > >>> > >>> Hi, > >>> I don't think this can work. > >>> First of all, GRE and Frame-Relay are completely different protocols > >>> operating at different OSI layers. GRE is IP (layer 3) based, whereas > >>> frame-relay is a layer-2 technology. > >>> Also, traditionally, you would need a corresponding frame-relay route > >>> command under the tunnel interface to connect the DLCIs. This command > is > >>> missing in the configuration below. > >>> I think the fact that you can configure a tunnel interface as a > >>> destination for the frame-relay switching is a cli-issue. Meaning that > ios > >>> simply allows any interface to be configured, but doesn't check that is > >>> actually a supported feature. > >>> regards, > >>> Marcel > >>> > >>> On 28 Jul, 2010,at 09:15 AM, "Abel ..." <[email protected]> wrote: > >>> > >>> > >>> At the moment I'm trying to configure a Frame-relay switch with two > 2811 > >>> connecting each other over a fastethernet. First router have 3 WIC-2T > and > >>> the second 1 WIC-2T. As the output show the frame-relay PVC over the > GRE > >>> tunnels never come up. I read and re-read a few configuration examples > and > >>> everything says that configuring must do the trick but for some reason > my > >>> home lab is against me. Thanks for the help in advanced. > >>> -------------------------------------------------------------------- > >>> hostname FR1 > >>> ! > >>> frame-relay switching > >>> ! > >>> interface Tunnel0 > >>> no ip address > >>> tunnel source FastEthernet0/0 > >>> tunnel destination 1010.10.20 > >>> ! > >>> interface FastEthernet0/0 > >>> ip address 10.10.10.10 255.255.255.0 > >>> duplex auto > >>> speed auto > >>> ! > >>> interface Serial0/0/0 > >>> description Connected to R1 > >>> no ip address > >>> encapsulation frame-relay > >>> clock rate 128000 > >>> frame-relay intf-type dce > >>> frame-relay route 102 interface Tunnel0 201 > >>> frame-relay route 103 interface Serial0/0/1 301 > >>> frame-relay route 104 interface Serial0/1/0 401 > >>> frame-relay route 105 interface Serial0/1/1 501 > >>> frame-relay route 106 interface Serial0/2/0 601 > >>> frame-relay route 112 interface Tunnel0 211 > >>> ! > >>> interface Serial0/0/1 > >>> description Connected to R3 > >>> no ip address > >>> encapsulation frame-relay > >>> frame-relay intf-type dce > >>> frame-relay route 301 interface Serial0/0/0 103 > >>> frame-relay route 302 interface Tunnel0 203 > >>> frame-relay route 304 interface Serial0/1/0 403 > >>> frame-relay route 305 interface Serial0/1/1 503 > >>> frame-relay route 306 interface Serial0/2/0 603 > >>> ! > >>> interface Serial0/1/0 > >>> description Connected to R4 > >>> no ip address > >>> encapsulation frame-relay > >>> frame-relay intf-type dce > >>> frame-relay route 401 interface Serial0/0/0 104 > >>> frame-relay route 402 interface Tunnel0 204 > >>> frame-relay route 403 interface Serial0/0/1 304 > >>> frame-relay route 405 interface Serial0/1/1 504 > >>> frame-relay route 406 interface Serial0/2/0 604 > >>> ! > >>> interface Serial0/1/1 > >>> description Connected to R5 > >>> no ip address > >>> encapsulation frame-relay > >>> clock rate 128000 > >>> frame-relay intf-type dce > >>> frame-relay route 501 interface Serial0/0/0 105 > >>> frame-relay route 502 interface Tunnel0 205 > >>> frame-relay route 503 interface Serial0/0/1 305 > >>> frame-relay route 504 interface Serial0/1/0 405 > >>> frame-relay route 506 interface Serial0/2/0 605 > >>> ! > >>> interface Serial0/2/0 > >>> description Connected to R6 > >>> no ip address > >>> encapsulation frame-relay > >>> clock rate 128000 > >>> frame-relay intf-type dce > >>> frame-relay route 601 interface Serial0/0/0 106 > >>> frame-relay route 602 interface Tunnel0 206 > >>> frame-relay route 603 interface Serial0/0/1 306 > >>> frame-relay route 604 interface Serial0/1/0 406 > >>> frame-relay route 605 interface Serial0/1/1 506 > >>> ! > >>> interface Serial0/2/1 > >>> description Connected to BB1 > >>> no ip address > >>> encapsulation frame-relay > >>> shutdown > >>> frame-relay intf-type dce > >>> ! > >>> end > >>> > >>> FR1#sh version > >>> Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9-M), Version > >>> 12.4(18b), RELEASE SOFTWARE (fc2) > >>> Technical Support: http://www.cisco.com/techsupport > >>> Copyright (c) 1986-2008 by Cisco Systems, Inc. > >>> Compiled Mon 19-May-08 15:43 by prod_rel_team > >>> ROM: System Bootstrap, Version 12.4(13r)T, RELEASE SOFTWARE (fc1) > >>> FR1 uptime is 6 days, 23 hours, 26 minutes > >>> System returned to ROM by reload at 23:57:35 UTC Tue Jul 20 2010 > >>> System image file is "flash:c2800nm-adventerprisek9-mz.124-18b.bin" > >>> > >>> This product contains cryptographic features and is subject to United > >>> States and local country laws governing import, export, transfer and > >>> use. Delivery of Cisco cryptographic products does not imply > >>> third-party authority to import, export, distribute or use encryption. > >>> Importers, exporters, distributors and users are responsible for > >>> compliance with U.S. and local country laws. By using this product you > >>> agree to comply with applicable laws and regulations. If you are unable > >>> to comply with U.S. and local laws, return this product immediately. > >>> A summary of U.S. laws governing Cisco cryptographic products may be > >>> found at: > >>> http://www.ciscocom/wwl/export/crypto/tool/stqrg.html > >>> If you require further assistance please contact us by sending email to > >>> [email protected]. > >>> Cisco 2811 (revision 53.50) with 245760K/16384K bytes of memory. > >>> Processor board ID FHK1101F2MA > >>> 2 FastEthernet interfaces > >>> 6 Serial(sync/async) interfaces > >>> 16 terminal lines > >>> 1 Virtual Private Network (VPN) Module > >>> DRAM configuration is 64 bits wide with parity enabled. > >>> 239K bytes of non-volatile configuration memory. > >>> 62720K bytes of ATA CompactFlash (Read/Write) > >>> Configuration register is 0x2102 > >>> FR1#sh frame-relay route > >>> Input Intf Input Dlci Output Intf Output Dlci Status > >>> Serial0/0/0 102 Tunnel0 201 > inactive > >>> Serial0/0/0 103 Serial0/0/1 301 active > >>> Serial0/0/0 104 Serial0/1/0 401 active > >>> Serial0/0/0 105 Serial0/1/1 501 active > >>> Serial0/0/0 106 Serial0/2/0 601 active > >>> Serial0/0/0 112 Tunnel0 211 > inactive > >>> Serial0/0/1 301 Serial0/0/0 103 active > >>> Serial0/0/1 302 Tunnel0 203 > inactive > >>> Serial0/0/1 304 Serial0/1/0 403 active > >>> Serial0/0/1 305 Serial0/1/1 503 active > >>> Serial0/0/1 306 Serial0/2/0 603 active > >>> Serial0/1/0 401 Serial0/0/0 104 active > >>> Serial0/1/0 402 Tunnel0 204 > inactive > >>> Serial0/1/0 403 Serial0/0/1 304 active > >>> Serial0/1/0 405 Serial0/1/1 504 active > >>> Serial0/1/0 406 Serial0/2/0 604 active > >>> Serial0/1/1 501 Serial0/0/0 105 active > >>> Serial0/1/1 502 Tunnel0 205 > inactive > >>> Serial0/1/1 503 Serial0/0/1 305 active > >>> Serial0/1/1 504 Serial0/1/0 405 active > >>> Serial0/1/1 506 Serial0/2/0 605 active > >>> Serial0/2/0 601 Serial0/0/0 106 active > >>> Serial0/2/0 602 Tunnel0 206 > inactive > >>> Serial0/2/0 603 Serial0/0/1 306 active > >>> Serial0/2/0 604 Serial0/1/0 406 active > >>> Serial0/2/0 605 Serial0/1/1 506 active > >>> Tunnel0 201 Serial0/0/0 102 active > >>> Tunnel0 203 Serial0/0/1 302 active > >>> Tunnel0 204 Serial0/1/0 402 active > >>> Tunnel0 205 Serial0/1/1 502 active > >>> Tunnel0 206 Serial0/2/0 602 active > >>> Tunnel0 211 Serial0/0/0 112 active > >>> > >>> > >>> > >>> > ---------------------------------------------------------------------------------------- > >>> FR2 > >>> interface Tunnel0 > >>> no ip address > >>> tunnel source FastEthernet0/0 > >>> tunnel destination 10.10.10.10 > >>> ! > >>> interface FastEthernet0/0 > >>> ip address 10.1010.20 255.255.255.0 > >>> duplex auto > >>> speed auto > >>> ! > >>> interface Serial0/2/0 > >>> description Connected to R2 > >>> no ip address > >>> encapsulation frame-relay > >>> frame-relay intf-type dce > >>> frame-relay route 201 interface Tunnel0 102 > >>> frame-relay route 203 interface Tunnel0 302 > >>> frame-relay route 204 interface Tunnel0 402 > >>> frame-relay route 205 interface Tunnel0 502 > >>> frame-relay route 206 interface Tunnel0 602 > >>> ! > >>> interface Serial0/2/1 > >>> description Connected to R2 > >>> no ip address > >>> encapsulation frame-relay > >>> frame-relay intf-type dce > >>> frame-relay route 211 interface Tunnel0 112 > >>> ! > >>> end > >>> FR2#sh version > >>> Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9-M), Version > >>> 12.4(18b), RELEASE SOFTWARE (fc2) > >>> Technical Support: http://www.cisco.com/techsupport > >>> Copyright (c) 1986-2008 by Cisco Systems, Inc. > >>> Compiled Mon 19-May-08 15:43 by prod_rel_team > >>> ROM: System Bootstrap, Version 12.4(1r) [hqluong 1r], RELEASE SOFTWARE > >>> (fc1) > >>> FR2 uptime is 12 minutes > >>> System returned to ROM by reload at 20:20:00 UTC Tue Jul 27 2010 > >>> System image file is "flash:c2800nm-adventerprisek9-mz.124-18b.bin" > >>> > >>> This product contains cryptographic features and is subject to United > >>> States and local country laws governing import, export, transfer and > >>> use. Delivery of Cisco cryptographic products does not imply > >>> third-party authority to import, export, distribute or use encryption. > >>> Importers, exporters, distributors and users are responsible for > >>> compliance with U.S. and local country laws. By using this product you > >>> agree to comply with applicable laws and regulations. If you are unable > >>> to comply with U.S. and local laws, return this product immediately. > >>> A summary of U.S. laws governing Cisco cryptographic products may be > >>> found at: > >>> http://www.cisco.com/wwl/export/crypto/tool/stqrg.html > >>> If you require further assistance please contact us by sending email to > >>> [email protected] > >>> Cisco 2811 (revision 53.50) with 247808K/14336K bytes of memory. > >>> Processor board ID FTX1035A30J > >>> 11 FastEthernet interfaces > >>> 2 Serial(sync/async) interfaces > >>> 1 Virtual Private Network (VPN) Module > >>> DRAM configuration is 64 bits wide with parity enabled. > >>> 239K bytes of non-volatile configuration memory. > >>> 62592K bytes of ATA CompactFlash (Read/Write) > >>> Configuration register is 0x2102 > >>> ------------------------------------------------- > >>> R1#sh frame-relay pvc | include DLCI > >>> DLCI = 102, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE = > >>> Serial0/0/0 > >>> DLCI = 103, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = > >>> Serial0/0/0 > >>> DLCI = 104, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = > >>> Serial0/0/0 > >>> DLCI = 105, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = > >>> Serial0/0/0 > >>> DLCI = 106, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = > >>> Serial0/0/0 > >>> DLCI = 112, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE = > >>> Serial0/0/0 > >>> R2#sh frame-relay pvc | include DLCI > >>> DLCI = 201, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE = > >>> Serial0/0 > >>> DLCI = 203, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE = > >>> Serial0/0 > >>> DLCI = 204, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE = > >>> Serial0/0 > >>> DLCI = 205, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE = > >>> Serial0/0 > >>> DLCI = 206, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE = > >>> Serial0/0 > >>> DLCI = 211, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE = > >>> Serial0/1 > >>> R3#sh frame-relay pvc | include DLCI > >>> DLCI = 301, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = > >>> Serial0/0/0 > >>> DLCI = 302, DLCI USAGE = UNUSED, PVC STATUS = INACTIVE, INTERFACE = > >>> Serial0/0/0 > >>> DLCI = 304, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = > >>> Serial0/0/0 > >>> DLCI = 305, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = > >>> Serial0/0/0 > >>> DLCI = 306, DLCI USAGE = UNUSED, PVC STATUS = ACTIVE, INTERFACE = > >>> Serial0/0/0 > >>> > >>> _______________________________________________ > >>> For more information regarding industry leading CCIE Lab training, > please > >>> visit www.ipexpertcom > >> > >> _______________________________________________ > >> For more information regarding industry leading CCIE Lab training, > please > >> visit www.ipexpert.com > > > > > > _______________________________________________ > > For more information regarding industry leading CCIE Lab training, please > > visit www.ipexpert.com > > > > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
