Possible answers are: 1) we have always been at war with elbonia, so we continue to be at war with elbonia 2) we like 1 central place to manage access / authorization and we desire the collection of accounting type data so we know when Foo did Bar to Baz. (I know you can shovel ~7k users on an arista of current flavor, and a juniper of same flavor... the initial commit time is 'stupendous' though :) - do not try this on a ciscoXR device was my recollection) You can also set some relatively clear authorization config on devices for read-only-ish or read-write account priveleges, on cisco/arista/juniper... anyway, why do you want to use tacacs? (Unless everyone is still running tac_plus on RHEL7) I'm trying to migrate some tac plus instances to a new Linux distro that apparently doesn't support tcp_wrappers and I'm having trouble both compiling it and making an RPM for it.
Published at: 2026-02-17 22:07:21
Still want to read the full version? Full article
