From: Greg Parrish (gparrish@xxxxxxxxx)
Date: Sat Apr 06 2002 - 01:47:49 GMT-3
According to documentation you only need the dynamic keyword on the dial out
side and not the remote side. Also once you connect it will remain connected
for 5 minutes after no activity also but this is tunable. You only need the
promiscuous keyword if you were coming from a border peer right? Since the
other router is configured to talk directly with you he should not need it I
think?
Greg
Ahmed Mamoor Amimi wrote:
> Yes ur right.
> i think the best solution in this case is to use promescus keyword on the
> other router.
>
> -Mamoor
>
> ----- Original Message -----
> From: Narvaez, Pablo <Pablo.Narvaez@getronics.com>
> To: Ahmed Mamoor Amimi <mamoor@ieee.org>; Jonghwan Hyon
> <jerry@datacraft-korea.com>; <ccielab@groupstudy.com>
> Sent: Friday, April 05, 2002 7:04 AM
> Subject: RE: DLSW Dynamic peer question!
>
> > If you use dynamic peers, both ends should give dynamic keyword to the
> remote site correct?
> >
> > -----Original Message-----
> > From: Ahmed Mamoor Amimi [mailto:mamoor@ieee.org]
> > Sent: Jueves, 04 de Abril de 2002 07:20 p.m.
> > To: Jonghwan Hyon; ccielab@groupstudy.com
> > Subject: Re: DLSW Dynamic peer question!
> >
> >
> > why didnt u give dynamic keyword on the routerb. I am getting a feeling
> that
> > is is routerb that is keeping up the link.
> >
> > -Mamoor
> >
> >
> > ----- Original Message -----
> > From: Jonghwan Hyon <jerry@datacraft-korea.com>
> > To: <ccielab@groupstudy.com>
> > Sent: Thursday, April 04, 2002 11:13 PM
> > Subject: DLSW Dynamic peer question!
> >
> >
> > > hi, group!
> > >
> > > i configure dlsw dynamic peer, but the peer connected constantly on
> remote
> > site!
> > >
> > > is it normal operation?
> > >
> > > here is my configuration.
> > >
> > > routera#sh conf
> > >
> > > dlsw local-peer peer-id 135.5.1.1
> > > dlsw remote-peer 0 tcp 135.5.6.6 keepalive 0 timeout 90 dynamic
> > inactivity 3
> > > dlsw bridge-group 1
> > >
> > > routera#sh dlsw peer
> > > Peers: state pkts_rx pkts_tx type drops ckts
> > TCP uptime
> > > TCP 135.5.6.6 DISCONN 0 0 dynam 0
> > 0 - -
> > > Total number of connected peers: 0
> > > Total number of connections: 0
> > >
> > >
> > > routerb#sh conf
> > > dlsw local-peer peer-id 135.5.6.6
> > > dlsw remote-peer 0 tcp 135.5.1.1 keepalive 0 timeout 90
> > > dlsw bridge-group 1
> > >
> > > routerb#sh dlsw peer
> > > Peers: state pkts_rx pkts_tx type drops ckts
> > TCP uptime
> > > TCP 135.5.1.1 CONNECT 2 2 conf 0 0
> 0
> > 00:02:02
> > >
> > >
> > > thanks, regards,
> > >
> > > ***********************************************
> > > Jonghwan Hyon(Jerry), CCNP/CCDP/CCSI
> > > Manager
> > > Technical Service/Taejon Branch Office
> > >
> > > Datacraft Korea, Inc.
> > > 320-150, Room #309 Expotel Bldg
> > > 381 Man-nyun-dong, Seo-Gu, Taejon, Korea
> > >
> > > Tel : 8242-487-4272
> > > Fax : 8242-487-4273
> > > Mobile : 8211-437-8883
> > > e-mail : jerry@datacraft-korea.com
> > > ***********************************************
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:57 GMT-3