Hi Mike
I've never tried this for SpectroWatches but I think you will need to
use the functionality for Copying Event Variables from One Event to
Another (see the 8.1 Event Config Files guide, p42) to do this. Have you
tried that?

The SpectroWatch event variable info you need is in table 3 on page 130
of the 8.1 SpectroWatch Operators guide.

So assuming your current rule looks something as follows:
0x1 R Aprisma.Eventpair, 0x2, 0x3, 1200

Something like the following might do what you need:
0x1 R Aprisma.Eventpair, 0x2, "0x3 7:7", 1200

The one possible problem I see is that you will only be passing the
bitrate value for when the threshold is initially breached. But I guess
that is better than nothing.

Cheers, John

-----Original Message-----
From: Friedman, Mike [mailto:[email protected]] 
Sent: 27 January 2009 21:04
To: spectrum
Subject: [spectrum] Customized alarm for bandwidth usage

Hi,

I am trying to setup alarming on our internet links so that if they
exceed a certain total bitrate we receive an alarm.  Unfortunately the
built in threshold is only for total utilization and we would like to
see the actual bit usage versus just a percentage of the interfaces
usage.  We are using this to monitor how often we exceed our contract
rate with our internet provider.  Also, we only want to alarm when we
exceed our commitment rate for over a certain period of time as our
contract does allow for bursting, just not extended overusage.

So far I have been able to get the alarming working using a watch on the
In_BitRate and Out_BitRate attributes that generates an event(ex. 0x1)
when we exceed our limit and another event(0x2) to reset when we return
below that limit.  Also, I have setup a pairing rule on 0x1 so that if
it doesn't see event 0x2 within 20 minutes it creates an alarm event
(0x3)

The problem I am having is how to get the bitrate information into the
alarm (0x3) when its generated. If I trigger the watch to just generate
the alarm itself then I get the information we would like to see, but
there is no option for the violation to be present for a period of time
before alarming.

Maybe I am going about this in a completely roundabout and incorrect way
and there is something much easier I am missing, but and recommendations
would be appreciated.

Michael R. Friedman
Network Engineer
Network Engineering | Orbitz Worldwide



---
To unsubscribe from spectrum, send email to [email protected] with the
body: unsubscribe spectrum [email protected]

---
To unsubscribe from spectrum, send email to [email protected] with the body: 
unsubscribe spectrum [email protected]

Reply via email to