1. Dynamic mapping means no inverse arp. 2. Static mapping disables inverse arp for that particular protocol/dlci. Others would still be allowed. You can have both a map and an interface-dlci. While most things can be done with a "frame-relay map" command, things like per-PVC mapp-class assignments (traffic shaping, end-to-end keepalive, etc.) or PPPoFR definition cannot be. So the object then is to play around with things and see if you can or cannot accomplish certain tasks without using an interface-dlci command. See what happens (or what doesn't happen) is an excellent method of learning exactly what these things are for, and likely never forgetting it! :) HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE-M #153, JNCIS-ER, CISSP, et al. CCSI/JNCI-M/JNCI-ER VP - Technical Training - IPexpert, Inc. IPexpert Sr. Technical Instructor [EMAIL PROTECTED] Telephone: +1.810.326.1444 Fax: +1.810.454.0130 http://www.ipexpert.com _____ From: Carlos Valero [mailto:[EMAIL PROTECTED] Sent: Monday, May 26, 2008 11:39 AM To: [EMAIL PROTECTED]; 'Suresh Mishra'; [email protected] Subject: Re: [OSL | CCIE_RS] Frame-relay Interface DLCI and MAP Commands - Lab3 I'm working on Lab 3, but frankly this is not making sense to me. So I hope somebody can help me. I have several questions: 1. We are told: do not rely on Dynamic Mappings ==> Of course that means NO frame-relay interface-dlci command allowed But the solution does use frame-relay interface-dlci! R2 is initially configured like this: interface Serial1/0.24 point-to-point ip address 150.50.24.2 255.255.255.0 frame-relay interface-dlci 204 and then this changed to: interface Serial0/1/0.24 point-to-point frame-relay interface-dlci 104 ppp Virtual-Template1 In both cases we ARE using frame-relay interface-dlci! I don't know, but this doesn't make too much sense to me! 2. This is related to the first question. frame-relay map is supposed to "disable Inv-ARP", correct? So if we configured frame-relay map, then we should not use frame-relay interface-dlci However, both statements ARE being used! Frankly, I don't understand why and how That's not supposed to work! 3. This is not directly related to this Lab, but confusing anyway. I know that "normally" frame-relay interface-dlci and frame-relay map should not be used in the Interface. However, both statements may be needed in QoS config cases, because map-class can't be specified on a "frame-relay map" command In cases like these, frame-relay interface-dlci is ALSO needed, and in these cases the frame-relay map must come first. However, in the Instructor's comments section, I read that if I had configured a frame-relay map, and then I configure frame-relay interface-dlci for the same DLCI, then ALL the previous MAP statements will be erased! Frankly, I don't get it. If I put the map first, and then the frame int, and if frame int erases the map, then I won't have a map statement anyway. But what if I'm not allowed to use Inv-ARP, meaning no frame int statements? Sorry, but F/R may be quite simple for most of you, but things like these make it really confusing for me. I hope somebody can help. Thank you! C. Valero. Scott Morris <[EMAIL PROTECTED]> wrote: Yes, as pointed out on the audio CD's, if you use both a map and the interface-dlci command, the MAP must come first. HTH, -----Original Message----- From: Suresh Mishra [mailto:[EMAIL PROTECTED] Sent: Thursday, February 21, 2008 4:43 PM To: [EMAIL PROTECTED]; [email protected] Subject: Frame-relay Interface DLCI and MAP Commands Hello Scott, I was listening to your audio CD. You said it is possible that we can use frame-relay interface-dlci to apply map class for the PVCs which are assigned using the frame-relay map command. Do we need to worry about any kind of order when using both the commands for the same DLCI under the same interface. Thanks Suresh
