There are several different philosophies on this. I personally am of the "If it ain't broke, don't fix it" philosophy.
Major revisions (12.1, 12.2, etc) always add support for new features and hardware. Unless you need support for such new features or hardware, staying within a given point revision is advisable in my opinion. New features bring the possibility of new bugs, so if the need isn't there, the risk isn't worth it.
When there is a bug, security advisory, or other need to upgrade, I tend to advise upgrading to the latest rebuild of a version. So if I'm running 12.2(17d)SXB5, and I encounter a bug that is fixed in 12.2(17d)SXB7, I would upgrade to 12.2(17d)SXB11 (which is the latest rebuild), as it will have all bug fixes currently available for the 12.2(17d) train, even though I may not have run into those specific bugs.
Again, these are all personal philosophies from my own experiences rather than any type of official guideline.
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.