Josh, You could either use the map statements "like you did" or specify the "frame interface-dlci 425" & "frame interface-dlci 524" on the respective routers.
You will be provided the needed information for the DLCI's in the LAB but, if you run into a situation where you need to get the correct dlci without being told and cannot get access to the FRS, you will have to do a process of elimination. Being that you are using GNS3 you will not see the true active DLCI's from the FRS, as typically you would only see those that are receiving packets, if you have all devices connected and running, I would shutdown those interfaces on the other routers facing the the fRS that I'm not using and only leave those up that I'm trying to get the correct DLCI's on, once you have narrowed it down to a few DLCI's that are active you will have an easier way to determine your true DLCI's. In schools that I went to the instructors would do exactly what your describing to see if you could troubleshoot it, this is the method that I used to quickly get the correct DLCI's "thanks Heinz Ulm". Here is an example of the other method to get your scenario to work: R5#sh run int s0/0 ! interface Serial0/0 ip address 1.1.1.5 255.255.255.0 encapsulation frame-relay serial restart-delay 0 frame-relay interface-dlci 524 R4#sh run int s0/0 ! interface Serial0/0 ip address 1.1.1.1 255.255.255.0 encapsulation frame-relay serial restart-delay 0 clock rate 2016000 frame-relay interface-dlci 425 Joe Sanchez On 7/29/12 10:02 AM, "Joshua Wood" <[email protected]> wrote: >Hello all, in order to add some additional information and hopefully >clarification on what is confusing me. If I open up the frame switch >in GNS3 that is connecting these two routers and find the DLCI >mappings and then apply those mappings to the interfaces everything >seems to work fine. The problem that I can't figure is how to find out >what the DLCI mappings would be without looking at the frame switch >since I assume that i won't have access to the frame switch in the >CCIE lab. > >Below I have copied the settings that I am using that work. > > >R4(config-if)#do sh run int s0/0 >interface Serial0/0 > ip address 1.1.1.1 255.255.255.0 > encapsulation frame-relay > clock rate 2000000 > frame-relay map ip 1.1.1.5 425 >R4(config-if)# > >R4#ping 1.1.1.5 > >Type escape sequence to abort. >Sending 5, 100-byte ICMP Echos to 1.1.1.5, timeout is 2 seconds: >!!!!! >Success rate is 100 percent (5/5), round-trip min/avg/max = 20/31/44 ms >R4# > >-------------------------------- > >R5#sh run int s1/0 >interface Serial1/0 > ip address 1.1.1.5 255.255.255.0 > encapsulation frame-relay > serial restart-delay 0 > frame-relay map ip 1.1.1.1 524 > >R5#ping 1.1.1.1 >Type escape sequence to abort. >Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds: >!!!!! >Success rate is 100 percent (5/5), round-trip min/avg/max = 20/33/52 ms >R5# > > > > > >On Sun, Jul 29, 2012 at 9:23 AM, Joshua Wood <[email protected]> wrote: >> Hello all, I am having trouble understanding what I believe should be >> a basic concept of frame relay. I am using the IPExpert provided GNS3 >> layout in order to get 2 routers to ping each other using frame relay. >> The two routers (R5 and R4) connect via frame switch. The two problems >> that I am having are 1) the devices can¹t ping each no matter what I >> try and 2) I can¹t figure out how you would find out the DLCI mappings >> without inverse arp which also doesn¹t seem to be working. >> >> I have put some relevant info below but I assume that information >> would be needed but I am not sure what would be helpful. This seems >> like it should be simple but I can't seem to get it to work at all, >> not even by accident. >> >> >> R5(config)#do sh run int s1/0 >> Building configuration... >> >> Current configuration : 112 bytes >> ! >> interface Serial1/0 >> ip address 1.1.1.5 255.255.255.0 >> encapsulation frame-relay >> serial restart-delay 0 >> end >> >> R5(config)#do sh fram map >> Serial1/0 (up): ip 0.0.0.0 dlci 526(0x20E,0x80E0) >> broadcast, >> CISCO, status defined, active >> Serial1/0 (up): ip 0.0.0.0 dlci 524(0x20C,0x80C0) >> broadcast, >> CISCO, status defined, active >> Serial1/0 (up): ip 0.0.0.0 dlci 522(0x20A,0x80A0) >> broadcast, >> CISCO, status defined, active >> Serial1/0 (up): ip 0.0.0.0 dlci 516(0x204,0x8040) >> broadcast, >> CISCO, status defined, active >> Serial1/0 (up): ip 0.0.0.0 dlci 514(0x202,0x8020) >> broadcast, >> CISCO, status defined, active >> Serial1/0 (up): ip 0.0.0.0 dlci 512(0x200,0x8000) >> broadcast, >> CISCO, status defined, active >> Serial1/0 (up): ip 0.0.0.0 dlci 506(0x1FA,0x7CA0) >> broadcast, >> CISCO, status defined, active >> Serial1/0 (up): ip 0.0.0.0 dlci 504(0x1F8,0x7C80) >> broadcast, >> CISCO, status defined, active >> Serial1/0 (up): ip 0.0.0.0 dlci 502(0x1F6,0x7C60) >> broadcast, >> CISCO, status defined, active >> R5(config)# >> >> ----------------------------------------------- >> >> R4(config)#do sh run int s0/0 >> Building configuration... >> >> Current configuration : 108 bytes >> ! >> interface Serial0/0 >> ip address 1.1.1.1 255.255.255.0 >> encapsulation frame-relay >> clock rate 2000000 >> end >> >> R4(config)#do sh fram map >> Serial0/0 (up): ip 0.0.0.0 dlci 426(0x1AA,0x68A0) >> broadcast, >> CISCO, status defined, active >> Serial0/0 (up): ip 0.0.0.0 dlci 425(0x1A9,0x6890) >> broadcast, >> CISCO, status defined, active >> Serial0/0 (up): ip 0.0.0.0 dlci 422(0x1A6,0x6860) >> broadcast, >> CISCO, status defined, active >> Serial0/0 (up): ip 0.0.0.0 dlci 416(0x1A0,0x6800) >> broadcast, >> CISCO, status defined, active >> Serial0/0 (up): ip 0.0.0.0 dlci 415(0x19F,0x64F0) >> broadcast, >> CISCO, status defined, active >> Serial0/0 (up): ip 0.0.0.0 dlci 412(0x19C,0x64C0) >> broadcast, >> CISCO, status defined, active >> Serial0/0 (up): ip 0.0.0.0 dlci 406(0x196,0x6460) >> broadcast, >> CISCO, status defined, active >> Serial0/0 (up): ip 0.0.0.0 dlci 405(0x195,0x6450) >> broadcast, >> CISCO, status defined, active >> Serial0/0 (up): ip 0.0.0.0 dlci 402(0x192,0x6420) >> broadcast, >> CISCO, status defined, active >> R4(config)# >_______________________________________________ >For more information regarding industry leading CCIE Lab training, please >visit www.ipexpert.com > >Are you a CCNP or CCIE and looking for a job? Check out >www.PlatinumPlacement.com > >http://onlinestudylist.com/mailman/listinfo/ccie_rs _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com http://onlinestudylist.com/mailman/listinfo/ccie_rs
