I agree with David that the reason you are getting these messages is that some device in your network is configured to use your TACACS server but the server is not configured to talk to the IP address that is in the source address of the TACACS packet. There can be two reasons this happens: the server is not configured for this client device at all, or the server is configured to talk to this client device using a different IP address. If the client device has more than one interface which it can use to send to the TACACS server then the server might receive packets from either interface and each one uses its own address as the source address by default. In this situation it is very useful to configure: ip tacacs source-address
to specify which address the client should use. It is probably best practice to specify a loopback address for this.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.