From: Jay Hennigan (jay@xxxxxxxx)
Date: Sun Jan 21 2001 - 18:16:04 GMT-3
On Sun, 21 Jan 2001, Vikas Gupta wrote:
> Fred,
>
> How would R4 and R5 initiate first session when they
> don't have any explicit remote-peer statements, they
> will only accept connections (not initiate) and then
> dlsw traffic can pass thru once the connection is
> made. In this case the very first session has to be
> from R2. Let's say any SNA device on R5 or R4 is
> trying to connect to a SNA host anywhere in the
> network and let us assume that there is nothing in the
> Dlsw cache, the first thing Dlsw will do is send
> explorers to all remote-peers but in this case there
> are no remote-peer statements configured and hence
> explorers will not be sent anywhere. If the SNA device
> would have been on R2 side , explorers will be sent to
> R4 and R5 as they are defined in remote-peer
> statements.
>
> Atleast this is my understanding. Any comments??
The DLSW peering will occur as long as there is TCP/IP connectivity
between the routers, originated by the configured peers toward the
promiscuous peers. So, you'll have a DLSW TCP connection between
R2 and R4, and another between R2 and R5. Both of these will originate
with R2.
Once this DLSW peering is established (regardless of which side originated
it) traffic can flow over it in either direction. So, devices on R4 or
R5 should be able to send explorers to R2.
I haven't thought it through or set it up in the lab as to whether R4
and R5 can "bounce" traffic through R2 to each other. Because it's a
form of bridging I would tend to think so. Does DLSW have an attribute
similar to split-horizon that would prevent this?
[snippage]
> > Scenario: Configure R2, R4, and R5 for DLSW.
> Configure filter so that the
> > only protocol that is transported via dlsw is
> netbios and apply this filter
> > to R2 remote peer statements.
> >
> > R5:
> > dlsw local-peer peer-id 150.100.5.5 group 100
> promiscuous
> > dlsw bridge-group 1
> > int loopback 0
> > ip address 150.100.5.5 255.255.255.0
> > int e0
> > bridge-group 1
> > bridge 1 protocol ieee
> >
> > R2:
> > source-bridge ring-group 200
> > dlsw local-peer peer-id 150.100.2.2 group 100
> border
> > dlsw remote-peer 0 tcp 150.100.4.4
> lsap-output-list 200
> > dlsw remote-peer 0 tcp 150.100.5.5
> lsap-output-list 200
> > dlsw remote-peer 0 tcp 150.100.5.5
> lsap-output-list 200
> > int loopback 0
> > ip address 150.100.2.2 255.255.255.0
> > int token0
> > source-bridge 25 1 200
> > source-bridge spanning
> > access-list 200 permit 0xF0F0 0x0101
> >
> > R4:
> > source-bridge ring-group 400
> > dlsw local-peer peer-id 150.100.4.4 group 100
> promiscuous
> > int loopback 0
> > ip address 150.100.4.4 255.255.255.0
> > int token0
> > source-bridge 26 1 400
> > source-bridge spanning
-- Jay Hennigan - Network Administration - jay@west.net NetLojix Communications, Inc. NASDAQ: NETX - http://www.netlojix.com/ WestNet: Connecting you to the planet. 805 884-6323
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:38 GMT-3