[Top] [All Lists]

[nv-l] VPN staue threshold

To: nv-l@lists.tivoli.com
Subject: [nv-l] VPN staue threshold
From: adam.paisley@elekta.com
Date: Tue, 8 Jul 2003 17:39:01 +0100
Delivered-to: mailing list nv-l@lists.tivoli.com
Delivery-date: Tue, 08 Jul 2003 17:41:42 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
List-help: <mailto:nv-l-help@lists.tivoli.com>
List-post: <mailto:nv-l@lists.tivoli.com>
List-subscribe: <mailto:nv-l-subscribe@lists.tivoli.com>
List-unsubscribe: <mailto:nv-l-unsubscribe@lists.tivoli.com>
Mailing-list: contact nv-l-help@lists.tivoli.com; run by ezmlm

Hi list,
I'm a little stuck for an approach to generate events for when a vpn interface goes down.

The mib table contains the vpn status for a number of vpn tunnels.  These are reported as a 1 for up and 0 for down.  

Initially I thought I'd use a simple data collection and threshold, but the trigger is > "a value" and re-arm <= "a value" - this is the opposite to how the device is working.

I'm thinking that this is a fairly standard thing to be able to solve - can anyone offer any pointers on how to do this - I've checked the archive & it only seems to mention calculating positive thresholds.  A thought I've got is that I can set the threshold > 0 and re-arm <=0 which will cause it to trigger all the time, then use a rule to get the mib value (will the trap include that?) and then do something with it in the rule to decide if it should be sent onwards to TEC.

Any thoughts appreciated.


<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web