From: Shafagh Zandi (szmetal@gmail.com)
Date: Sat Oct 13 2007 - 10:15:29 ART
I mean,
If you are connected via console to R1, then you should configure
session-timeout on console, then telnet to R2, and it works like a charm, it
depends on where you are - to initiate a session from there.
Regards,
Shafagh Zandi
www.shafagh.com
On 10/13/07, Shafagh Zandi <szmetal@gmail.com> wrote:
>
> Benedict,
>
> What about your connection to R1, is it from console then to R2? I mean,
> try it using telnet to R1 connecting to a vty then make a session to R2 from
> R1.
>
> Regards,
> Shafagh Zandi
>
>
> On 10/13/07, Benedict Munyao <bmunyao@gmail.com> wrote:
> >
> > I labbed it up as follows:
> >
> > R1--------------------------R2
> > 155.6.0.1 155.6.0.2
> >
> >
> > R1
> > lin con 0
> > session-timeout 1
> >
> > telnet 155.6.0.2
> > >R2
> >
> > With this configuration, the session disconnects after 1 minute and I'm
> > returned to idle state on R1.
> >
> > Next I moved the command to vty lines as follows:
> >
> > lin con 0
> > no session-timeout 1
> > lin vty 0 4
> > session-timeout 1
> >
> > telnet 155.6.0.2
> > >R2
> >
> > This time it did not time out, unless I used exec-timeout 1 on vty lines
> > at
> > R2.
> >
> > Perhaps other scenarios produce other results, but this led me to the
> > conclusion that the command affects outgoing sessions only when set on
> > the
> > local console line. I could not make sense of part of the explanation on
> >
> > doccd for this command.
> >
> > Sincerely
> > Benedict Munyao
> >
> >
-- Shafagh Zandi, www.shafagh.com
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:14 ART