From: John Neiberger (neiby@ureach.com)
Date: Fri Oct 04 2002 - 11:52:05 GMT-3
The parameter that is set to 0 in your example is for use with
ring lists and port lists, not bridge groups. If you specify a
number other than zero, you restrict traffic to and from that
peer to a set of ports or rings depending on how you configure
it.
Take a look here for details (watch the line wrap):
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/
121cgcr/ibm_c/bcprt2/bcddlsw.htm#12864
Regards,
John
---- On Fri, 4 Oct 2002, chenyan (chenyan@deeptht.com.cn) wrote:
> hi,guys
>
> Using the commands:
> dlsw local-peer peer-id 10.1.1.1
> dlsw remote-peer 0 tcp 10.1.1.2
> I think the 0 means that all the interfaces of the local peer
can be mapped to the remote peer, and
> if the 0 is replaced by non zero like 1, then I must add the
command" dlsw bridge-group 1" to map the
> bridge-group to remote peer. Is it right?
>
> But if the remote peer only use the "dlsw local-peer peer-id
10.1.1.2 promiscious" then how can I
> know which interfaces can be available to the dlsw traffic?
>
> Thanks
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:39 GMT-3