Paul,
AAA is what I do, so I would recommend that. Unless you've got a small
handful of routers and the configs rarely change, AAA makes your life
much easier.
TACACS+ would have let you get much more specific on what commands the
outside company could run - command authorization.
If you have
I would setup a TACACS+ server. You can get a free one from Cisco, but you
have to compile it. You can then create user names, passwords and priv
levels. That way it's easier to change the passwords for those who know
them. If you can swing something like ACS, even better.
We are moving that
The best practice is, if you know Perl or some other scripting language (and
I don't BTW, at least not well enough) is to put together a script that will
take as input the existing enterprise-wide router password and a new
password and the script can telnet to each router, login and change the
pas
Hi ...
I am just about to change all the router/switch passwords in my company
(about
40) ... I have only been there several weeks and I have only worked in a very
small routing/switching environment before
I have had to give access to an outside company so they can monitor certain
WA
N lin
4 matches
Mail list logo
