From: Derek Fage (DerekF@xxxxxxxxxxx)
Date: Tue Jul 20 1999 - 15:27:44 GMT-3
OK - I understand now.
Thanks for the info.
Derek...
> -----Original Message-----
> From: Fred Ingham [SMTP:fningham@worldnet.att.net]
> Sent: 20 July 1999 19:29
> To: Derek Fage
> Cc: ccielab@groupstudy.com
> Subject: Re: DLSW+ Border Peer Configuration
>
> On your non-border routers I would configure the promiscuous parameter.
> The peering between groups can be established directly after the
> resource is identified thru the border peers. The border peers
> establish peering with all peers in their group but are used only to
> forward explorers to other groups. For instance, in your configuration,
> a group 1 peer wanting to establish a session with a group 2 peer would
> send an explorer to the border peer which would forward it to the other
> border peer which would then forward it to the group 2 peers. A reply
> would be sent the same route. Then the peers in group 1 and group 2
> would establish the connection as peer-on-demand. This can be between
> two peers in the same group or peers in different groups.
>
> Some excerpts from the Configuration Guide are included below:
>
> Configuration for Peer A1
> dlsw local-peer peer-id 10.2.17.1 group 40 promiscuous
> dlsw remote-peer 0 tcp 10.2.24.1
> dlsw peer-on-demand-defaults tcp
>
> Configuration for Border Peer A
> dlsw local-peer peer-id 10.2.24.1 group 40
> border promiscuous
> dlsw remote-peer 0 tcp 10.2.18.2
>
> Configuration for Peer B1
> dlsw local-peer peer-id 10.2.24.3 group 50 promiscuous
> dlsw remote-peer 0 tcp 10.2.18.2
> dlsw peer-on-demand-defaults tcp
>
> Configuration for Border Peer B
> dlsw local-peer peer-id 10.2.18.2 group 50
> border promiscuous
> dlsw remote-peer 0 tcp 10.2.24.1
>
> After configuring border peers and peer groups, the same fully meshed
> connectivity is possible
> without the overhead. In the "after" network, two peer groups are
> defined (Group 40 and Group 50).
> Within each group, one or more peers are configured as border peers.
> Every peer within Group 40
> establishes a peer connection with border peer A (BPA). Every peer
> within Group 50 establishes a
> peer connection with border peer B (BPB). The border peers establish a
> peer connection with each
> other. When a peer in Group 40 wants to find a resource, it sends a
> single explorer to its border peer.
> The border peer forwards this explorer to every peer in its group and to
> every other border peer. BPB,
> after receiving this explorer, forwards it to every peer in its group.
> When the resource is found (in
> this case at B1), a positive reply flows back to the origin (A1) via the
> two border peers. At this point
> A1 establishes a direct peer connection to B1. Peer connections that are
> established via border peers
> without the benefit of preconfiguration are called peer-on-demand
> connections. The rules for
> establishing on-demand peers are defined in the dlsw
> peer-on-demand-defaults tcp command in each router.
>
> And:
>
> With border peers in place, it is possible for two peers to communicate
> with each other even though
> neither has a configuration for the other. This is because they learn
> about each other via their
> respective border peers. For that reason, there is a statement that
> defines how to connect with peers
> when no dlsw remote-peer commands are used. That statement is the dlsw
> peer-on-demand-defaults
> tcp command, and it can be used to specify the encapsulation, filters,
> and timers.
> On-demand peer connections can be made between two peers in the same
> group or two peers in
> different groups.
>
> Derek Fage wrote:
> >
> > I'm running through some final configuration scenarios, and need a bit
> of
> > advice about this.
> >
> > I'm trying to setup a DLSW+ configuration using border peers.
> >
> > In group 1 I have 3 peers and a border peer, and in group 2 I have 3
> peers
> > and a border peer.
> >
> > Border peers are configured as follows:
> >
> > dlsw local-peer peer-id nnn.nnn.nnn.nnn group 1 border promiscous
> > dlsw remote-peer 0 tcp nnn.nnn.nnn.nnn (address of group 2 border
> peer)
> >
> > Group peers are configured as follows:
> >
> > dlsw local-peer peer-id nnn.nnn.nnn.nnn group 1 (or 2)
> > dlsw remote-peer 0 tcp nnn.nnn.nnn.nnn (address of border peer for
> this
> > group).
> >
> > All appears fine, and the capabilities for the peers look correct - I
> just
> > want to understand a bit more how this works.
> >
> > Let's look at the situation where a SRB client attached to the ring of a
> > peer client in group 1 wants to connect to an SRB server attached to the
> > ring of a peer client in group 2.
> >
> > Am I correct in assuming that the individual peers will send all of the
> > traffic via the border peer router to the remote site (once the ARE has
> > established the route) ? Is this also the case between peers in the same
> > group ?
> >
> > Derek...
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:42 GMT-3