I had a same issue when I did this lab. I was able to learn BB1 mac address up to R6 and after that I was not able to see on R9. and if try from from other direction on BB3, I was able to see BB3 mac address on R9 but not on R6. I tried all commands which are mentioned in DSG but was not able to ping. It's a really nice Lab but doesn't work as per DSG. Any one has complete this Lab ? I would like to know what we are missing ?
On Mon, Oct 11, 2010 at 7:11 PM, Adam Booth <[email protected]> wrote: > 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 >>> >>> >> > > _______________________________________________ > 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
