One way iv got this to work is by creating a BVI2 instance +bridge irb in
the same 100.100.100.x subnet on each r1/r2/r6/r9

Would this satisfy the requirement?

Seems by merely bridging from r1 to r9 bb1 & bb3 can't talk, the config
below was the same as Joe's detailed solution guide



On 13 October 2012 14:36, Tony Singh <[email protected]> wrote:

>
> Hi
>
> This is from V1 lab 7.4
>
> *Topology*
> BB1 > VLAN100 > R1 VLAN12 > R2 > FR P2P > R6 bridged to R9 > VLAN300 > BB3
>
> Goal is to ping from BB1 100.100.100.100/24 to BB3 100.100.100.250/24
>
> I can see arp on R1 & R9 for both BB1 & BB3 f0/0 interfaces but I cant get
> ping to run from either end...
>
> Because this task bridges 3 vlan domains iv checked the relevant
> switchport configs are ok hence would not be getting the mac addresses for
> each end of the bb's on r1/r9 (although they do time out a bit)
>
> Debug shows the ar coming in at either r1 r r9 ends
>
> r1
> *Oct 13 10:17:59.847: IP ARP: rcvd req src 100.100.100.100 000d.bd31.0460,
> dst 100.100.100.250 FastEthernet0/1
>
> r9
> *Oct 13 12:41:07.002: IP ARP: rcvd req src 100.100.100.250 000f.8fdd.5740,
> dst 100.100.100.100 FastEthernet0/0
>
> Spanning tree bridge instance 2 is running and agree on R6 as root....
>
> configs below
>
> r1
> bridge irb
> bridge 2 protocol ieee
> bridge 2 route ip
> int f0/0
>  bridge-group 2
> int f0/1
>  bridge-group 2
>
>
> r2
> bridge 2 protocol ieee
> int f0/0
>  bridge-group 2
> int s0/2/1.206
>  bridge-group 2
>
> r6
> bridge 2 protocol ieee
> int s0/1/0.602
>  bridge-group 2
> int s0/2/0
>  bridge-group 2
>
> r9
> bridge irb
> bridge 2 protocol ieee
> bridge 2 route ip
> int s0/2/0
>  bridge-group 2
> int f0/0
>  bridge-group 2
>
>
> can you see what's wrong?
>
>
>
>
>
_______________________________________________
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

Reply via email to