timeout login response and exec-timeout

[raffski]

I had exec-timeout configured on my vty interfaces, then for grins I added the command 'timeout login response 15' since this now logs me off after 15 seconds of inactivity, i tried to back out by using no timeout login response 15, but the command timeout login response 0 now applies to this vty. i can't remove it, and the exec-timeout commands do now 'take' any more. well they get accepted, but the show run never displays them. IOS 12.2.(17a) is running.

So what's happening?, is there any way to remove the timeout login response 0 entry and get exec-timeout back in there?

[vincent-n]

Your post made me confused a bit but have you tried:

line vty 0 4

exec-timeout 10 0

10 is the minutes and 0 is the seconds. This is the default Cisco value. I'm guessing here that the command "timeout login response 0" might be the default value so try the exec-timeout command with response 0 and see how things go. Good luck.

[raffski]

Hmmm, what I think was happening is: when I set exec-timeout 10 0, the router would take the command, but the line would not appear in the running config. But if I set the exec-timeout to a different value, it does appear. So I think since 10 0 is the default, it doesn't appear in the config.

Also if you use the timeout login response command, then it seems to appear for ever, doing no timeout login response sets the value to 0, the entry stating 'timeout login response 0' remains. I would have expected the entry to be removed form the config in normal circumstances.

Bit wierd, but I have both commands in use now.

exec-timeout 9 30

timeout login response 15

[milan.kulik]

Hi,

why do you think it's wierd to have both commands in use?

Each of them is playing a different role:

timeout login response

defines how long the router waits for your username and password (see http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/secur_r/sec_s1g.htm#1073079)

while

exec-timeout

closes the established session after defined time of inactivity (see http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/fun_r/cfr_1g03.htm#1029531)

The URLs above also explain how to remove the commands form config (i.e. set the timers back to default values).

If no timeout login response sets the value to 0 (as you describe) I would consider it as a bug. Try to set timeout login response to 30 sec (default) to remove it from the config.

Regards,

Milan

[thisisshanky]

As Milan suggested, it could be a bug, but i just tried this command on a 12.2(8) code and when you give a no form of the command, the timeout login response 0 command comes under the line mode.

I tried setting the defaults for the line interface by using the command,

Router(config)#default line vty 0

%cant delete last 5 lines.

I guess the only other way to remove this is to backup your configs, wipe out the configs, reload the configs back, without the timeout command on it.

[rjackson]

It sound like the 0 value is how it tells you that it is not going to timeout login responses.

[raffski]

I thought the behaviour of the commands was wierd, not their combined use.

timeout login response 30 does remove it from the config.

Wierd.

[thisisshanky]

Usually default configuration commands does not appear on the running configs. So probably it got itself removed because, 30 seconds would be the default value for this command.

[namso2]

I think 0 in this case means infinity.