Understanding exec-timeout values You run show running-config and see: Line console 0 Exec-timeout 1 35 Password CURIOUSTABPASSWD Login What do the two numbers following exec-timeout indicate for the console line?

Difficulty: Easy

Correct Answer: If no commands are typed in 1 minute and 35 seconds, the console connection will be closed.

Explanation:


Introduction / Context:
The exec-timeout setting on Cisco IOS line configurations determines how long an EXEC session can remain idle before the device disconnects it. This helps enforce security hygiene and frees resources on busy devices. The command uses a two-parameter format that frequently confuses newcomers.


Given Data / Assumptions:

  • The configuration shows exec-timeout 1 35 on the console line.
  • The numbers represent minutes and seconds, respectively.
  • We focus on local console behavior, not vty-specific differences.


Concept / Approach:

The syntax is exec-timeout . Therefore, exec-timeout 1 35 means 1 minute and 35 seconds of inactivity (no keystrokes entered) will cause the console session to terminate. A value of 0 0 disables the timeout (no automatic disconnect). The setting applies to the specific line context where it is configured (console, aux, or vty).



Step-by-Step Solution:

Parse the two numbers as minutes and seconds.Map 1 and 35 to 1 minute and 35 seconds.Conclude that idle console sessions will be disconnected after that period with no input.Recognize that output activity alone does not reset the timer; user input is required.


Verification / Alternative check:

Testing by leaving the console idle for 95 seconds (1 minute 35 seconds) results in IOS closing the session and returning to the password prompt on the next key press, confirming the configuration behavior.



Why Other Options Are Wrong:

  • 35 seconds only: ignores the minutes parameter.
  • 1 hour and 35 minutes: misreads units; the first number is minutes, not hours.
  • Telnet-only behavior: exec-timeout applies to whichever line it is set on; here it is the console.
  • 96 seconds claim: mathematically off (1*60 + 35 = 95 seconds), and the definition requires user input inactivity.


Common Pitfalls:

  • Assuming device output resets the timer; typically only user input does.
  • Forgetting to set an appropriate timeout on vty lines, leaving remote sessions open indefinitely.


Final Answer:

If no commands are typed in 1 minute and 35 seconds, the console connection will be closed.

Discussion & Comments

No comments yet. Be the first to comment!
Join Discussion