Forum Discussion
teemo_13
Cirrus
CirrusTACACS+ Timeout on BIG-IP v12
I know that v12 is no longer supported. We still have a device that is being used and cannot be upgraded to v13 anywore. We need to comply with the security requirement of adjusting the tacacs timeou...
Paulius
MVP
MVPteemo_13 If you cannot modify this timeout in the GUI for this auth group then the CLI will not work for it. What does the F5 say when you try to configure this via CLI?
teemo_13it does not output any error, nothing happens basically
- Paulius
teemo_13 Typically if a command is not valid when entering it through the CLI it will error stating such and if you use the "load sys config from-terminal merge" and drop the configuration in place it will error as well stating what piece of the configuration is causing the issue. If you did not receive any errors and when you run the command "list auth tacacs" and you see the timeout it should absolutely have taken that and applied it to the active configuration. How have you verified that the timeout is not working?
- teemo_13
See screenshot, no timeout under system-auth, whereas in v13, it is under that config