From: Radoslav Vasilev (deckland@gmail.com)
Date: Fri Sep 15 2006 - 12:46:07 ART
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