Hi all,
We ran into a little problem. This is the situation:
In the past (untill now) we never used tacacs on our switches. We have a main system who creates seed files for different network management systems. The input file for rme contained a telnet password. Because this was in the file it errored on it and did not go on checking the other passwords and usernames.
I created a file myself where I put !{[NOVALUE]}! in the colums that needed to be empty and only left the ip-address, community strings and the tacacs information.
The result after importing the file was that it gave an INCORRECT on the tacacs login. Weird since I am able to do a login using that tacacs account from the same machine. I checked if the right information was in the right column and it is right..
After searching the internet I found some info on checking the TacacsPrompt.ini file. This file was ok too.
Did anyone experience this problem too and would you like to share this solution with us?
Thanks
InDenial
InDenial
We ran into a little problem. This is the situation:
In the past (untill now) we never used tacacs on our switches. We have a main system who creates seed files for different network management systems. The input file for rme contained a telnet password. Because this was in the file it errored on it and did not go on checking the other passwords and usernames.
I created a file myself where I put !{[NOVALUE]}! in the colums that needed to be empty and only left the ip-address, community strings and the tacacs information.
The result after importing the file was that it gave an INCORRECT on the tacacs login. Weird since I am able to do a login using that tacacs account from the same machine. I checked if the right information was in the right column and it is right..
After searching the internet I found some info on checking the TacacsPrompt.ini file. This file was ok too.
Did anyone experience this problem too and would you like to share this solution with us?
Thanks
InDenial
InDenial