If you are using (bridge irb) than just create an BVI inteface ..use the
command *interface BVI 1 (on both R6 and R9)* ..you need no ip addresss on
it here .. I believe ARP failed as IP  will not work when you are using IRB
unlesss you create an BVI. try it! and dont forget the *bridge x route
ip*command.
Regards



On Tue, Oct 12, 2010 at 8:00 PM, <[email protected]>wrote:

> Send CCIE_RS mailing list submissions to
>        [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://onlinestudylist.com/mailman/listinfo/ccie_rs
> or, via email, send a message with subject or body 'help' to
>        [email protected]
>
> You can reach the person managing the list at
>        [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of CCIE_RS digest..."
>
> Today's Topics:
>
>   1. Re: Vol 1 Lab 7 Task 7.4 Frame Relay: Bridging (Adam Booth)
>
>
> ---------- Forwarded message ----------
> From: Adam Booth <[email protected]>
> To: Winston Lee <[email protected]>
> Date: Tue, 12 Oct 2010 12:11:13 +1000
> Subject: Re: [OSL | CCIE_RS] Vol 1 Lab 7 Task 7.4 Frame Relay: Bridging
> Hmm,
>
> Sorry for pointing you in the wrong direction. Having a look this lab it
> uses point-to-point FR interfaces, so I don't think what I said was of any
> help actually :)
>
> It sounded like ARP wasnt working though - are you able to debug ARP on BB1
> and BB3 and see if that gets through?
>
> Cheers,
> Adam
>
> On Tue, Oct 12, 2010 at 12:00 PM, Adam Booth <[email protected]> wrote:
>
>> Hi Winston,
>>
>> When you did your frame-relay mapping for bridge frames - did you also
>> include the "broadcast" keyword ? This will be required for ARP to work.
>>
>> Cheers,
>> Adam
>>
>>   On Tue, Oct 12, 2010 at 11:32 AM, Winston Lee 
>> <[email protected]>wrote:
>>
>>>    Hello All,
>>>
>>> I'm performing task 7.4 (trying to use bridge-groups so that BB1 can talk
>>> to BB3 across frame-relay), and I'm running into issues not documented in
>>> the solution guide. Specifically, I cannot ping from BB1 to BB3 - or vice
>>> versa. After doing a 'debug ip packet' on BB3, I noticed that encapsulation
>>> was failing and that the arp entry for 100.100.100.100 was incomplete. After
>>> adding in the arp entry manually on both BB1 and BB3, ping functions
>>> correctly. Is there something I'm missing here, or is this expected
>>> behavior? I believe this is supposed to work without manually adding in arp
>>> entries.
>>>
>>> --------------------------
>>>
>>> BB3#debug ip packet
>>> IP packet debugging is on
>>> BB3#p 100.100.100.100 r 1
>>>
>>> Type escape sequence to abort.
>>> Sending 1, 100-byte ICMP Echos to 100.100.100.100, timeout is 2 seconds:
>>>
>>> *Apr 10 11:12:22.563: IP: tableid=0, s=100.100.100.250 (local),
>>> d=100.100.100.100 (FastEthernet0/0), routed via RIB
>>> *Apr 10 11:12:22.563: IP: s=100.100.100.250 (local), d=100.100.100.100
>>> (FastEthernet0/0), len 100, sending
>>> *Apr 10 11:12:22.567: IP: s=100.100.100.250 (local), d=100.100.100.100
>>> (FastEthernet0/0), len 100, encapsulation failed.
>>> Success rate is 0 percent (0/1)
>>> BB3#show arp
>>> Protocol  Address          Age (min)  Hardware Addr   Type   Interface
>>> Internet  100.100.100.100         0   Incomplete      ARPA
>>> Internet  100.100.100.250         -   0004.c18e.2e00  ARPA
>>> FastEthernet0/0
>>>
>>> BB1(config)#arp 100.100.100.250 0004.c18e.2e00 ARPA
>>>
>>> BB3(config)#arp 100.100.100.100 0006.2893.a041 ARPA
>>>
>>> BB3#p 100.100.100.100 r 1
>>>
>>> Type escape sequence to abort.
>>> Sending 1, 100-byte ICMP Echos to 100.100.100.100, timeout is 2 seconds:
>>> !
>>> Success rate is 100 percent (1/1), round-trip min/avg/max = 80/80/80 ms
>>> BB3#
>>> *Apr 10 11:16:31.747: IP: tableid=0, s=100.100.100.250 (local),
>>> d=100.100.100.100 (FastEthernet0/0), routed via FIB
>>> *Apr 10 11:16:31.747: IP: s=100.100.100.250 (local), d=100.100.100.100
>>> (FastEthernet0/0), len 100, sending
>>> *Apr 10 11:16:31.823: IP: tableid=0, s=100.100.100.100 (FastEthernet0/0),
>>> d=100.100.100.250 (FastEthernet0/0), routed via RIB
>>> *Apr 10 11:16:31.827: IP: s=100.100.100.100 (FastEthernet0/0),
>>> d=100.100.100.250 (FastEthernet0/0), len 100, rcvd 3
>>>
>>>
>>>
>>> _______________________________________________
>>> For more information regarding industry leading CCIE Lab training, please
>>> visit www.ipexpert.com
>>>
>>>
>>
>
>


-- 
Best Regards,

Saleh Hassan Batouq
[email protected]
Tel: +968 99365607
Fax: +968 2469690
P.O.Box:1083- Postal Code:112
Muscat-Sultanate Of Oman
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to