dzuleta wrote:
I can try to help you if u want, but u will need to provide me for info.
First, which attribute contains the utilization of the port?
Second, when u want to generate an event/alarm?
-You take one value every 5 minutes and if in between those 5 minutes it drops below 50% you generate an alarm?
Or maybe take the maximun value in a period of 5 minutes, and then if it drops below 50% for more than 140 seconds generate an alarm.
U need to be more explicit in the conditions u want to make.
As i can see from your watch expresion u are not referencing the instance.
Almost sure that ifHCInOctets and ifSpeed are tables, this means, you must do 1 watch per instance and call it like: INTEGER ( ( COUNTER_DELTA( ifHCInOctets.x ) * 100 ) / ( INTEGER( ifSpeed.x ) * 300 ) ) where x is the number of the instance (1,2,3,...,x)
or make a watch for all the instance (or a range) and call it like: INTEGER ( ( COUNTER_DELTA( ifHCInOctets.# ) * 100 ) / ( INTEGER( ifSpeed.# ) * 300 ) )
Hi
Thanks for the info
Interestingly I think I have a bug with the Watcheditor - no matter what I do - including following the manuals examples - I get a "there is a syntax error in the watch expression" - so am checkign with CA
Right - on to the questions
As to the generation of the alarm it will be
take one reading (a), 5 minutes later take another reading (b)
if there is a 50% drop from (a) to (b) then generate an event
What I will do then is use EventDisp to create an escalation process
As to the watch expression - so even if the watch is against the port model it needs the instance number? I was going off the manual (which ia a bit vague ) and using some examples of port types to work out the syntax (badly of course)
Adding an instance is fine as its only a subset of ports
Wondering is one could use a variable to pick up the ifindex value by defining a watch to get the index of the port
Anyway its only a small number of ports so I can create a limited specific watch for each port it nescessary
As to the exact syntax to work out load - just working out the best attribute there, trouble is with the watch editor giving me borken values tricky to confirm the exact value.