The NMS station is a known NMS system in the network and building an ACL to drop its packets is not an option. From what i read in Cisco documentation i found that the following command stops the polling :
Your first post mentioned that you were using an access-list so thats why I mentioned it.
The config you mention above is part of an snmp-server view which is used to exclude certain mib objects from being polled. However, you don't know which MIB is causing the CPU to spike, so it will not be useful.
You can enable debugs to determine what is happening (prob not good with 99% CPU) or look through the logs to see if there are any CPUHOG messages.
If you want to bring down the CPU utilization you will need to do one of the following:
1) Disable snmp
2) Add an ACL to block snmp or add an acl to the comm string blocking that NMS from RO access
Ok i have disabled polling from the NMS. I had another problem again with a CPU load. The CPU went high due to an virtual exec proccess. From i found in Cisco's website, this problem is sourced from a telnet connection. Is that the only case? How can i completely stop it when it happens?
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.