RE: IEWB vol1 Lab 20 - Bridging over Frame relay

From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Fri Sep 15 2006 - 13:42:13 ART


R2 and R3 have a L3 to L2 mapping via inverse-ARP directly since you do
not have inverse-ARP disabled. This means the traffic is not going
through the hub router. Shutdown the hub router's interface and you'll
see that you can still ping between R2 and R3.

Also your frame-relay interface-dlci commands on R2 and R3 aren't doing
anything. The DLCI's are already assigned to the physical interface so
applying the command serves no purpose in your case.

HTH,

Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
 
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
 

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Radoslav Vasilev
Sent: Friday, September 15, 2006 8:46 AM
To: ccielab
Subject: IEWB vol1 Lab 20 - Bridging over Frame relay

Hi Group,

In IEWB vol1, lab 20, section 2.2 (bridging over FR), there's a
requirenment for a hub in a hub-and spoke router to provide transit
service, untill an order (new) PVC will be connecting the spokes
directly.

R1 (hub) connects using two P2P interfaces to R2 and R3 (the spokes)
using PVC 102 (to R2) and PVC103 to R3.
The idea is to basically bridge the two PVCs, and R1 will access the IP
subnet that bridge group represents usigng another interface to one of
the spokes.

My solutions (on the hub) :

int se0/0.102
 bridge-group 2

int se 0/0.103
 bridge-group 2

bridge 2 protocol ieee

On the spokes, the interfaces look like:

r2:
interface Serial0/0
 ip address 142.1.23.2 255.255.255.248
 encapsulation frame-relay
 clock rate 64000
 frame-relay interface-dlci 201

r3:
interface Serial1/0
 ip address 142.1.23.3 255.255.255.248
 encapsulation frame-relay
 clock rate 64000
 no fair-queue
 frame-relay interface-dlci 301

Connectivity between the spokes R2 and R3 is ok.

In the IEWB solution, the things are organised differently:

on R1, the hub, they have CRB
while on the spokes they run IRB.

Any idea why this is required and can't we just make the hub "blintly"
bridge them without IRB/CRB configuration?

Thanks,
Rado



This archive was generated by hypermail 2.1.4 : Sun Oct 01 2006 - 16:55:40 ART