02-03-2025 06:50 AM
How does the TACACS dead timer work in the Cisco switch? Suppose you have this command
"tacacs-server timeout 5"
Does that mean if the switch doesn't get a reply within 5 seconds from the TACACS server, will that mark that server as "DEAD" and does not send anymore TACACS requests to that particular TACACS server until it realizes the server is responding(may be keepalive packets)? Or will that keep sending TACACS requests to that TACACS server?
02-03-2025 07:23 AM - edited 02-03-2025 07:26 AM
Hello @Paheeradan Nagulan
The tacacs-server timeout 5 command sets the time the switch waits for a response from a TACACS+ server before considering that specific request as failed. However, this does not mean the server is immediately marked as "dead." It only means that if the server does not respond within 5 seconds, the switch will treat that authentication attempt as unsuccessful and move to the next available authentication method or server if configured.
A TACACS+ server is marked as "dead" only after multiple consecutive failures, not just one timeout. This behavior is controlled by the TACACS+ deadtime feature. If a switch is configured with aaa server tacacs+ deadtime <minutes>, it will temporarily stop sending authentication requests to a server after repeated failures and use other available servers instead.
When a TACACS+ server is marked as dead, the switch does not send any further authentication requests to it until the deadtime expires or until the switch detects that the server is responding again. Server monitoring mechanisms periodically check if the server is reachable, and once it starts responding, it is marked as "alive," and authentication requests resume.
Without the deadtime configuration, the switch will keep trying the same TACACS+ server for each authentication attempt, even if it is unresponsive, causing potential delays.
Improve failover behavior ? it is best to configure both tacacs-server timeout and aaa server tacacs+ deadtime to ensure quick switching between available servers...
02-03-2025 12:34 PM
Hi M02@rt37
I have been searching for this elusive TACACS+ dead timer feature, but I can't find it in any IOS/IOS-XE version. Do you have an example of an IOS/IOS-XE in which this exists, and a show run to prove it?
In the RADIUS world, the concept has existed for many years
radius-server deadtime <1-1440min>
radius-server dead-criteria time|tries ...
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide