From: Chuah Eng Wee (chuahew@xxxxxxxxxxxxxxx)
Date: Mon Nov 15 1999 - 06:02:40 GMT-3
Hi...
[r6]--------[r4]--------------[r5]--------[r3]
link between r6 and r4 is ethernet
link between r4 and r5 is frame relay
link between r3 and r5 is ethernet
r4 must not configure ipx routing
r6 advertise some saps and ipx network
r5 runs IRB
The problem:
When the link between R4 and R5 is hdlc encapsulation. Everything works
fine, r5 can see the saps from r6. So does r3
WHen the link between R4 and R5 is frame relay, r5 will not be able
to see the saps and ipx routes from r6. The bridging between r4
and r5 works fine. I tested this by placing 1 PC in the segment
between r4-r6 and another PC at r3-r5. They are able to find each other.
If u say that my IRB config is wrong, why does it work when the encap is
hdlc ??
I also realised that when configuring IRB, one has to be very careful.
For e.g, if u have ip protocol running in the above set up with routing
ip only and no bridging, at r5 u need to put "no bridge 2 bridge ip"
otherwise, it will not work. I thot when u assign a network layer address
to an interface, that protocol will be routed regardless whether there
is a bridge group command. I personnaly find IRB pretty confusing.
Anyway, the config is as below. Any help greatly appreciated.
[R6]
interface Loopback1
ipx network AA00
!
interface Loopback2
ipx network AA20
!
interface FastEthernet0/0
ipx network 460
bridge-group 2
bridge 2 pro ieee
[R4]
interface Ethernet0
bridge-group 2
!
interface Serial0
encapsulation frame-relay
bridge-group 2
!
interface Serial0.1 multipoint
frame-relay map bridge 405 broadcast
frame-relay interface-dlci 402
frame-relay interface-dlci 405
bridge-group 2
bridge 2 pro ieee
[R5]
interface Serial0
encapsulation frame-relay
frame-relay map bridge 504 broadcast
bridge-group 2
interface BVI2
no ip address
lat enabled
ipx network 460
bridge 2 protocol ieee
bridge 2 route appletalk
bridge 2 route ip
bridge 2 route ipx
no bridge 2 bridge appletalk
no bridge 2 bridge ip
bridge 2 pro ieee
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:55 GMT-3