CiscoWorks - Device fault manager HighUtilization Event every time
I've got an issue with the device fault manager on CiscoWorks.
Basically, what i wanted to do was to stop the ExceededMaximumUptime reported to many times on all my routers (ADSL interface). I tried to do some tweaking but even if I don't have ExceededMaximumUptime anymore, a HighUtilization alert replaced it (with many more alert :-( ).
What you are seeing with the bogus highutilization could be a bug either on the device or in DFM. Start a sniffer trace filtering on udp/161 traffic to this router. When you get the bogus HighUtilization event, stop the trace. The last two polls should be interesting. Manually calculating the utilization on the interface (both in and out) will indicate whether the problem is with the device or with DFM.
The same bug could be affecting all of your devices. Based on what you said you did, I think your config is good. Modifying a custom group is the way to go in this case. The fact that you see bogus utilization is never a good thing, even if the config was totally wrong.
I tried to use a new group (4) with exactly the same rule to capture the packets because I remove all the stuff on the old one (2) to stop those alerts for the night, and putted the group on the top of settings priority and it works fine... no more HighUtilization Alert, I don't understand...
And now when I try to use the old group (2), There is no more device on it, even if I recreate exactly the same rule ...
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.