From: fingham@cox.net
Date: Thu Feb 20 2003 - 22:00:47 GMT-3
Brett: Another post explained the basics. This configuration misses
the point of configuring a border peer.
First, configure the border peer which in this case is R1:
dlsw local peer 172.20.1.1 group 20 border prom
This is the only statement needed on R1. The group number is the group
all three peers will belong to, the border parameter signifies that R1 is a border peer,
and the promiscuous is to form remote peer connections. The problem with the
original configs is that the prom parameter was left off of the border (R1), among
other things.
Then configure the other group peers:
For R3:
dlsw local-peer peer-id 170.20.1.3 group 20 prom
dlsw remote-peer 0 tcp 170.20.1.1
dlsw bridge-group 10
int e 0
bridge-group 10
bridge 10 protocol ieee
For R2:
dlsw local-peer peer-id 170.20.1.2 group 20 prom
dlsw remote-peer 0 tcp 170.20.1.1
dlsw bridge-group 11
int e 0
bridge-group 11
bridge 11 protocol ieee
The dlsw peers will be formed between R2 and R1, and between R3 and R1. There will be
no peering between R2 and R3 until there is traffic passed. When there is traffic, a circuit
will be created and R2 and R3 will be peered as "pod" (peer-on-demand). The pod part
is why R2 and R3 need the prom parameter.
This can be tested with PC's on either end using NetBIOS or with DSPU on routers attached
to R2 and R3, or a spare mainframe.
HTH, Fred
>
> From: "Brett Lewis" <brett_lewis_666@msn.com>
> Date: 2003/02/20 Thu AM 10:38:06 EST
> To: SinghA1@telkom.co.za, ccielab@groupstudy.com
> Subject: Re: need help on DLSW border configuration
>
> Does the following work
>
> R3
>
> dlsw local-peer peer-id 170.20.1.3
> dlsw remote-peer 0 tcp 170.20.1.1
> dlsw bridge-group 10
>
> R2
> dlsw local-peer peer-id 170.20.1.2
> dlsw remote-peer 0 tcp 170.20.1.1
> dlsw bridge-group 10
>
> R1
> dlsw local-peer peer-id 170.20.1.1 promiscuous
> dlsw bridge-group 10
>
> Thanks
>
> Brett
>
>
>
>
>
>
> >From: "Anesh Singh (A)" <SinghA1@telkom.co.za>
> >Reply-To: "Anesh Singh (A)" <SinghA1@telkom.co.za>
> >To: <ccielab@groupstudy.com>
> >Subject: need help on DLSW border configuration
> >Date: Thu, 20 Feb 2003 11:56:04 +0200
> >
> >Team
> >
> >
> > R3------------R1-------R2
> >
> >The three routers are connected on a frame-relay cloud running ospf
> >R3 must peer with R1
> >R2 must peer with R1
> >
> >R3 must peer with R2 without fully meshed dslw
> >
> >Our configs
> >
> >R3
> >
> > dlsw local-peer peer-id 170.20.1.3 group 10 promiscuous
> >dlsw remote-peer 0 tcp 170.20.1.1
> >dlsw bridge-group 10
> >
> >
> >R2
> > dlsw local-peer peer-id 170.20.1.2 group 10 promiscuous
> >dlsw remote-peer 0 tcp 170.20.1.1
> >dlsw bridge-group 10
> >
> >R1
> >dlsw local-peer peer-id 170.20.1.1 group 10 border
> >dlsw bridge-group 10
> >
> >My problem is that R3 and R2 cannot peer (the connection fails with a
> >time out msg)
> >
> >
> >
> >R2 error msg
> >2d00h: DLSw: START-TPFSM (peer 170.20.1.3(2065)): event:TIMER-TIMER
> >EXPIRED state:DISCONN
> >2d00h: DLSw: dtp_action_d() close conn/timer expired for peer
> >170.20.1.3(2065)
> >2d00h: DLSw: END-TPFSM (peer 170.20.1.3(2065)): state:DISCONN->DISCONN
> >
> >DLSw: freeing 170.20.1.3 (0)
> >
> >Pls help!!!!!!!!!!!!
>
>
> _________________________________________________________________
> Stay in touch with absent friends - get MSN Messenger
> http://messenger.msn.co.uk
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:32 GMT-3