The source-bridge transparent command is only needed if 
you are bridging between the token-ring and ethernet on 
the same router.  It is not needed if you are using 
dlsw to peer between, for instance, R1 token and R2 
ether AND R1 ether and R3 ether/token.

The virtual ring is not required on the EN router.  
Some configs had this on CCO but it doesn't do anything.
If there is no token-ring interface on the router, a 
virtual ring is not needed, but the dlsw bridge-group 
is.


Your understanding is correct.
> two questions...thx in advance!
> 
> 1. is the "source-bridge transparent" command required on the token ring
> router when one dlsw peer is ethernet only & the other dlsw peer is token
> ring only (i.e., bet/ r1-e1 & r2-to1)?
> 
> 2. why is the virtual ring (500) required on the ethernet router in the
> config below?
> 
> finally, i understand that in the following config, the "source-bridge
> transparent" command is required bec/ ethernet & token ring is off the same
> router
> 
> !ethernet router:
> 
> source-bridge ring-group 500
> dlsw local-peer peer-id 1.1.1.1
> dlsw remote-peer 0 tcp 2.2.2.2 lf 1500
> dlsw bridge-group 5
> bridge-group 5 protocol ieee
> !
> int e0
> ip address 1.1.1.1 255.255.255.0
> bridge-group 5
> 
> !ethernet/token ring router:
> 
> source-bridge ring-group 500
> source-bridge transparent 500 1000 1 5
> dlsw local-peer peer-id 2.2.2.2
> dlsw remote-peer 0 tcp 1.1.1.1 lf 1500
> dlsw bridge-group 5
> bridge-group 5 protocol ieee
> !
> int e1/2
> ip address 2.2.2.2 255.255.255.0
> bridge-group 5
> !
> int to0
> ring-speed 16
> source-bridge 7 1 500
> source-bridge spanning
> 
> Timur Mirza
> Principal Network Engineer
> Network Planning & Engineering, West Region
> 15505-B Sand Canyon Avenue
> Irvine, California 92618
> Verizon Wireless
> 949.286.6623 (o)
> 949.697.7964 (c)




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=46909&t=46896
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to