I don't follow. The asterisk portion is the key itself obfuscated by RME to prevent eavesdropping. If the key is deployed back to the device, it should be done in clear text so the device understands it. The literal "********" will not be sent to the device.
Ah. If you go the the RME shadow directory, you should see the key just as it would appear on the router. So, the short answer is RME has archived a config which can be put back on the router, restoring everything that currently appears in the running config.
In my RME, when I view the config for my 3745, I see the following for tacacs-server key:
tacacs-server key ********
If I click the Edit button in the config viewer, then view the Tacacs Global section, I see the following in the credentials box:
tacacs-server key ******
If I click the the hyperlinked "******", I see the following in the popup:
Old Credential : tacacs1
Where "tacacs1" is the configured tacacs-server key on my router.
So, if you lose the key, you can either use RME's Config Editor to see the unencrypted value, or look at the shadow directory on the server which will have the clear text config that was archived from the device.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...