ACNS 5.x - Tacacs Key not encrypted in startup configuration

Unanswered Question
Apr 23rd, 2009

In a WAE 512 running ACNS 5.5.9.9, the tacacs key is not encrypted in the startup configuration. However, when I view the running configuration, the tacacs key is encrypted via astericks. Is there a way to enable the encryption of the key for the startup configuration as well or is this not working as it should be. The only way I found this is that when Ciscoworks compares the running and startup configurations it finds that they are not in sync because the tacacs key is represented differently between the startup and running configurations.

Thanks,

Tim Schlosser

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
owillins Wed, 04/29/2009 - 06:09

If you configure a key on the Content Engine, it must be the same as the one configured on the TACACS+ servers. The TACACS+ clients and servers use the key to encrypt all TACACS+ packets transmitted. If you do not configure a TACACS+ key, packets are not encrypted. TACACS+ authentication is disabled by default. You can enable TACACS+ authentication and local authentication at the same

Still you are getting problem then

Delete the configuration.

Restart the router and configure again.

Actions

This Discussion