For the most part, these can safely be ignored. We see this often and there are a few internal bugs to get these log messages cleaned up. They will most likely be suppressed in 3.3 which is due out in October.
A couple things to remember:
++If this message is seen after a policy is modified through configuration, it is recommended to detach the policy and re-attach it to ensure that the QOS policy works correctly.
++If this message appears due to interface up/down or speed negotiation, it is okay to ignore it.
Is it possible to get anyone to confirm this answer as correct? I have a pretty good understanding of QoS and there were no changes to the policy at all, just interface up/downs that triggered the warning about Modification to policy is unrecommended. Thus, I'm inclined to believe your answer because I can't think of any reason why an interface flap would have a real negative impact on marking policies. Can anyone else concur with this answer?
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.