RE: 2 dlsw peers. On both you have Ethernet and TR

From: Mas Kato (tealp729@xxxxxxxx)
Date: Tue May 22 2001 - 15:39:57 GMT-3


   
Indeed--port lists, ring lists and bgroups will help you get selected
traffic to the right remote-peer, but in this scenario, everything's
going to the same remote-peer. Hmmm...how to segregate the traffic at
the remote-end...

What about a brute-force treatment of it as an extended four-port
bridge? Is there anything you could do so that frames are only forwarded
out the ports you wanted them to be forwarded out of, based upon their
source MAC address?

Potential list of tools:

-Extended IBM access-list
-Bridge-group output-pattern
-Vendor code access-list
-source-bridge output-address-list
?

Even if this is workable, I would imagine the forwarding performance
would be pathetic.

Regards,

Mas

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Theodore TZEVELEKIS
Sent: Tuesday, May 22, 2001 9:33 AM
To: Padhu (LFG); 'RAMIL'; ccielab@groupstudy.com
Cc: gorrior@yahoo.com
Subject: RE: 2 dlsw peers. On both you have Ethernet and TR

But how will the router know which local peer corresponds to which
remote
peer?
All dlsw config is done in global config.

I have found the following:

http://www.cisco.com/warp/public/cc/pd/ibsw/ibdlsw/prodlit/dlsw3_rg.htm

(Port List section)

But it is not the exact scenario I'm looking for: This is a 1 & 2
scenario.
1 local peer, 2 physically distinct remote peers.

-----Original Message-----
From: Padhu (LFG) [mailto:padhu@steinroe.com]
Sent: Tuesday, May 22, 2001 5:41 PM
To: 'RAMIL'; Theodore TZEVELEKIS; ccielab@groupstudy.com
Cc: gorrior@yahoo.com
Subject: RE: 2 dlsw peers. On both you have Ethernet and TR

Just my 2c

R1--------------R2
ETh ETH
TR TR
On R1 and R2 , assign ip to ETH and TR interfaces and complete the dlsw
configurations
create a bridge group for ETh and Ring list for TR on both R1 and R2
respectively.
Create the remote peers on R1 with bgroup as the local target pointing
to
R2's ethernet as peer
repeat this 3 more times for the 3 other interfaces.

Somone correct me if this wouldn't work.

Cheers,Padhu

-----Original Message-----
From: RAMIL [mailto:ramil@SkiBuff.com]
Sent: Tuesday, May 22, 2001 10:35 AM
To: Theodore TZEVELEKIS; ccielab@groupstudy.com
Cc: gorrior@yahoo.com
Subject: Re:

border peers?

----- Original Message -----
From: "Theodore TZEVELEKIS" <theodore_tzevelekis@yahoo.com>
To: <ccielab@groupstudy.com>
Cc: <gorrior@yahoo.com>
Sent: Tuesday, May 22, 2001 11:28 AM

> Suppose you have 2 dlsw peers. On both you have
> Ethernet and TR.
>
> However, you only want the 2 ethernets to communicate
> with eachother and the two TR with eachother.
>
> In other words, no TR traffic should be seen on either
> ethernet and no ethernet traffic should be seen on
> either TR.
>
> Any ideas about how to do this?
>
> Please reply to all.
>



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:49 GMT-3