From: Foltz (globalfx@xxxxxxxxxxxxxx)
Date: Wed Feb 07 2001 - 19:07:10 GMT-3
Also, when you do
dlsw remote-peer 0 tcp 150.150.10.3
the '0' specifies all ports
Richard Foltz, CCNP-Voice, CCNP, CCDP, MCSE+I, Network+, A+
----- Original Message -----
From: <jpritcha@csc.com>
To: "Brian Hescock" <bhescock@cisco.com>
Cc: <ccielab@groupstudy.com>
Sent: Tuesday, February 06, 2001 10:08 PM
Subject: Re: where to apply dlsw port-lists (doc's lacking)
> Router-A has two dlsw remote peers (150.150.10.3, 150.150.10.2) and three
> token ring interfaces:
>
> Router-A"
> !
> .
> source-bridge ring-group 100
> dlsw local-peer peer-id 150.150.10.1
> dlsw remote-peer 1 tcp 150.150.10.3 (the '1' references dlsw port-list 1)
> dlsw remote-peer 2 tcp 150.150.10.2 (the '2' references dlsw port-list 2)
> !
> .
> dlsw port-list 1 port tokenring0 tokenring1
> dlsw port-list 2 port tokenring2
>
> Explorers originating on a ring supported by 150.150.10.3 will be
> propagated out tok0 and tok1 by Router-A but not out tok2.
>
> Jim
>
>
>
>
>
> Please respond to Brian Hescock <bhescock@cisco.com>
>
> Sent by: nobody@groupstudy.com
>
>
> To: ccielab@groupstudy.com
> cc:
>
> Subject: where to apply dlsw port-lists (doc's lacking)
>
>
> You guys are probably sick of me by now... ;-)
>
> >From the docs: "You can create a port list of local ports and apply the
> list to remote peer definitions."
>
> I have yet to find where to apply port-lists in the dlsw remote-peer
> command as indicated. The only thing I can think of is in the absence of
> a ring-list it uses the port-list instead (even though the command
> clearly states ring-list, not port-list). Or am I just missing the
> command that's right in front of my eyes? (not the port-list command but
> where to apply the port-list in the dlsw remote-peer command). Thx,
>
> B.
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:41 GMT-3