i have mentioned LAB-6 task 6.2.


On Thu, Sep 2, 2010 at 2:04 AM, Jason Maynard <[email protected]>wrote:

>  I did not look at the lab – I will have a look, which volume?
>
>
>
> *From:* Amer Mustafa [mailto:[email protected]]
> *Sent:* September-01-10 7:01 PM
>
> *To:* Jason Maynard
> *Cc:* [email protected]
> *Subject:* Re: [OSL | CCIE_RS] Workbook 1 , LAB6 (Frame-Relay).
>
>
>
> I need to work on this more until i am confident.
>
>
>
> now see this, on task 6.2 (LAB6-Frame-Relay) :
>
>
>
> The only configuration the workbook recommends is :
>
>
>
> =================
>
> on R6 :
>
> inter ser 0/1/0
>
> encap fram
>
> ip add 150.100.100.6 255.255.255.0
>
> ==================
>
> and then workbook does : show fram map and it finds 150.100.100.2 with DLCI
> 612.
>
>
>
> *I didnt find 150.100.100.2 in my show fram map command, i only found
> 150.100.24.4 ( why , and from where 150.100.24.4 is coming?).*
>
>
>
> i had to map ip 150.100.100.2 602 to make it run:
>
>
>
> *R6(config)#do show run | s Serial0/1/0**
> interface Serial0/1/0
>  ip address 150.100.100.6 255.255.255.0
>  encapsulation frame-relay
>  frame-relay map ip 150.100.100.2 602 broadcast*
>
>
>
> R6#ping 150.100.100.2
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 150.100.100.2, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 16/16/20 ms
>
> On Thu, Sep 2, 2010 at 1:51 AM, Jason Maynard <[email protected]>
> wrote:
>
> You can always use inverse-arp to determine what DLCIs are available. Then
> do your configurations
>
>
>
>
>
>
>
> *From:* Amer Mustafa [mailto:[email protected]]
> *Sent:* September-01-10 6:42 PM
>
>
> *To:* Jason Maynard
> *Cc:* [email protected]
> *Subject:* Re: [OSL | CCIE_RS] Workbook 1 , LAB6 (Frame-Relay).
>
>
>
> Good. but why we have assigned " frame interface-dlci 214"
>
>
>
> from where we get this "214" since we are not running any inve arp and our
> show fram mapp commands doesnt show 214.
>
> On Thu, Sep 2, 2010 at 1:38 AM, Jason Maynard <[email protected]>
> wrote:
>
> Your problem was that you learned all the DLCI by inverse arp which
> assigned them to the physical interface.
>
>
>
> Most likely you configured the interface while it was up and before you
> could turn off inverse arp and therefore learned all the DLCI’s that were
> available.
>
>
>
> If you would have shut the physical interface then configured encapsulation
> and no frame-relay inverse-arp plus all other configuration and then brought
> up the interface you would not have a problem.
>
>
>
>
>
> *From:* Amer Mustafa [mailto:[email protected]]
> *Sent:* September-01-10 6:33 PM
>
>
> *To:* Jason Maynard
> *Cc:* [email protected]
> *Subject:* Re: [OSL | CCIE_RS] Workbook 1 , LAB6 (Frame-Relay).
>
>
>
> jason,
>
>
>
> Thanks alot, its working, but can you explain one point to me !?
>
>
>
> how and why we have decided to 214 on R2 !?
>
>
>
> if you remove the config to the default, and then configure one by one, you
> will endup having the same error, and when do show fram map you will not
> find any mappings for Serial0/1/0.1.
>
>
>
> the only mapping avilable is 150.100.24.4 !
>
>
>
> Please advise.
>
> On Thu, Sep 2, 2010 at 1:23 AM, Amer Mustafa <[email protected]>
> wrote:
>
> Yup, its working but kinda confusing :
>
>
>
>
>
> on R2 :
>
>
>
> R2(config)#do show fram map
>
>
> Serial0/1/0 (up): ip 150.100.100.5 dlci 205(0xCD,0x30D0), static,
>               broadcast,
>               CISCO, status defined, inactive
> Serial0/1/0 (up): ip 150.100.100.2 dlci 205(0xCD,0x30D0), static,
>               CISCO, status defined, inactive
> Serial0/1/0 (up): ip 150.100.100.6 dlci 206(0xCE,0x30E0), static,
>               broadcast,
>               CISCO, status defined, inactive
>
> Serial0/1/0.1 (up): point-to-point dlci, dlci 214(0xD6,0x3460), broadcast
>           status defined, active
> Serial0/1/0 (up): ip 150.100.24.4 dlci *224** *(0xE0,0x3800), dynamic,
>               broadcast,, status defined, active
> R2(config)#
>
>
>
> *R2#sh run | s Serial0/1/0 *
>
> *
> interface Serial0/1/0
>  description Frame Relay Links
>  ip address 150.100.100.2 255.255.255.0
>  encapsulation frame-relay*
>
> * frame-relay map ip 150.100.100.5 205 broadcast *
>
> *
>  frame-relay map ip 150.100.100.6 206 broadcast*
>
> * frame-relay map ip 150.100.100.2 205 *
>
> *
>  no frame-relay inverse-arp
> interface Serial0/1/0.1 point-to-point
>  ip address 150.100.24.2 255.255.255.0*
>
> * frame-relay interface-dlci 214   **
> R2#*
>
>
>
> *on R4 : *
>
> *R4#show run | s Serial0/0/0
> interface Serial0/0/0
>  ip address 150.100.24.4 255.255.255.0
>  encapsulation frame-relay*
>
> * frame-relay interface-dlci 412*
>
> *R4#show fram map**
> Serial0/0/0 (up): ip 150.100.100.2 dlci 402(0x192,0x6420), dynamic,
>               broadcast,, status defined, active
> Serial0/0/0 (up): ip 150.100.24.2 dlci 412(0x19C,0x64C0), dynamic,
>               broadcast,, status defined, active
> R4#*
>
>
>
> ---
>
>
>
> R4#ping 150.100.24.2
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 150.100.24.2, timeout is 2 seconds:
> !!!!!
>
> Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
> R4#
>
> On Thu, Sep 2, 2010 at 1:10 AM, Jason Maynard <[email protected]>
> wrote:
>
> You have your answer, the dlci is assigned to the wrong interface
>
>
>
> Copy and paste this – I know others shut the interface then make changes
> but I find it quicker to copy then default then paster
>
>
>
> *default inter serial 0/1/0*
>
> *interface Serial0/1/0**
>  description Frame Relay Links
>  ip address 150.100.100.2 255.255.255.0
>  encapsulation frame-relay
>  frame-relay map ip 150.100.100.2 205
>  frame-relay map ip 150.100.100.6 206 broadcast
>  frame-relay map ip 150.100.100.5 205 broadcast
>  no frame-relay inverse-arp
> interface Serial0/1/0.1 point-to-point
>  ip address 150.100.24.2 255.255.255.0*
>
> * no frame-relay inverse-arp*
>
> * frame-relay interface-dlci 214*
>
>
>
>
>
> *From:* Amer Mustafa [mailto:[email protected]]
> *Sent:* September-01-10 6:06 PM
>
>
> *To:* Jason Maynard
> *Cc:* [email protected]
> *Subject:* Re: [OSL | CCIE_RS] Workbook 1 , LAB6 (Frame-Relay).
>
>
>
> i have tried this even before i send to you :
>
>
>
> R2(config-subif)#do show fram map
> Serial0/1/0 (up): ip 150.100.100.2 dlci 205(0xCD,0x30D0), static,
>               CISCO, status defined, inactive
> Serial0/1/0 (up): ip 150.100.100.5 dlci 205(0xCD,0x30D0), static,
>               broadcast,
>               CISCO, status defined, inactive
> Serial0/1/0 (up): ip 150.100.100.6 dlci 206(0xCE,0x30E0), static,
>               broadcast,
>               CISCO, status defined, inactive
> Serial0/1/0 (up): ip 150.100.24.4 dlci 214(0xD6,0x3460), dynamic,
>               broadcast,, status defined, active
> R2(config-subif)#fram
> R2(config-subif)#frame-relay inter
> R2(config-subif)#frame-relay interface-dlci 214 ?
>   cisco     Use CISCO Encapsulation
>   ietf      Use RFC1490/RFC2427 Encapsulation
>   ppp       Use RFC1973 Encapsulation to support PPP over FR
>   protocol  Optional protocol information for remote end
>   <cr>
>
> R2(config-subif)#frame-relay interface-dlci 214
> *%PVC already assigned to interface Serial0/1/0*
> R2(config-subif)#
>
> On Thu, Sep 2, 2010 at 12:59 AM, Jason Maynard <[email protected]>
> wrote:
>
> *R2(config)#do sh run | s Serial0/1/0**
> interface Serial0/1/0
>  description Frame Relay Links
>  ip address 150.100.100.2 255.255.255.0
>  encapsulation frame-relay
>  frame-relay map ip 150.100.100.2 205
>  frame-relay map ip 150.100.100.6 206 broadcast
>  frame-relay map ip 150.100.100.5 205 broadcast
>  no frame-relay inverse-arp
> interface Serial0/1/0.1 point-to-point
>  ip address 150.100.24.2 255.255.255.0*
>
> * frame-relay interface-dlci #*
>
>
>
> *From:* Amer Mustafa [mailto:[email protected]]
> *Sent:* September-01-10 5:52 PM
> *To:* Jason Maynard
> *Cc:* [email protected]
> *Subject:* Re: [OSL | CCIE_RS] Workbook 1 , LAB6 (Frame-Relay).
>
>
>
> *Nope, its not working.*
>
>
>
> *R4(config-if)#do show fram map**
> Serial0/0/0 (up): ip 150.100.100.2 dlci 412 (0x19C,0x64C0), dynamic,
>               broadcast,, status defined, active
> R4(config-if)#do sh run | s Serial0/0/0
> interface Serial0/0/0
>  ip address 150.100.24.4 255.255.255.0
>  encapsulation frame-relay
>  frame-relay interface-dlci 412
> R4(config-if)#do ping 150.100.24.2*
>
> *Type escape sequence to abort.**
> Sending 5, 100-byte ICMP Echos to 150.100.24.2, timeout is 2 seconds:
> .....
> Success rate is 0 percent (0/5)
> R4(config-if)#*
>
> On Thu, Sep 2, 2010 at 12:44 AM, Jason Maynard <[email protected]>
> wrote:
>
>
>
>
>
> Do sh “show frame map” to see that you are missing IP to DLCI mappings
>
>
>
> Add “frame-relay interface-dlci #” command
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Amer Mustafa
> *Sent:* September-01-10 5:41 PM
> *To:* [email protected]
> *Subject:* [OSL | CCIE_RS] Workbook 1 , LAB6 (Frame-Relay).
>
>
>
> I am on task 6.4 for LAB 6 WB1.
>
>
>
> on R4 :
>
>
>
> *R4#show run | s Serial0/0/0**
> interface Serial0/0/0
>  ip address 150.100.24.4 255.255.255.0
>  encapsulation frame-relay
> R4#ping 150.100.24.4*
>
> *Type escape sequence to abort.**
> Sending 5, 100-byte ICMP Echos to 150.100.24.4, timeout is 2 seconds:
> .....
> Success rate is 0 percent (0/5)*
>
>
>
> on R2 :
>
>
>
> *R2(config)#do sh run | s Serial0/1/0**
> interface Serial0/1/0
>  description Frame Relay Links
>  ip address 150.100.100.2 255.255.255.0
>  encapsulation frame-relay
>  frame-relay map ip 150.100.100.2 205
>  frame-relay map ip 150.100.100.6 206 broadcast
>  frame-relay map ip 150.100.100.5 205 broadcast
>  no frame-relay inverse-arp
> interface Serial0/1/0.1 point-to-point
>  ip address 150.100.24.2 255.255.255.0
> R2(config)#do ping 150.100.24.2*
>
> *Type escape sequence to abort.**
> Sending 5, 100-byte ICMP Echos to 150.100.24.2, timeout is 2 seconds:
> .....
> Success rate is 0 percent (0/5)
> R2(config)#*
>
>
>
> *what could be the reason ?*
>
>
>
> *======================*
>
>
>
> *regards ... *
>
> *Amer*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to