[Top] [All Lists]

Re: [nv-l] VPN staue threshold

To: nv-l@lists.tivoli.com
Subject: Re: [nv-l] VPN staue threshold
From: Stephen Hochstetler <shochste@us.ibm.com>
Date: Tue, 8 Jul 2003 14:28:10 -0500
Delivered-to: mailing list nv-l@lists.tivoli.com
Delivery-date: Tue, 08 Jul 2003 20:29:40 +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


Ok, here is potentially an easy one with a bit of work.   The trigger is ">
0"  the rearm is "<= 0".   You should get a trap on either condition.
Then in trapd.conf configuration or in a ruleset you call a script that
takes the information and generates a new trap....VPN interface down  or
VPN interface up based on the snmpcollect threshold traps.  Your script
should receive the MIB instances that relate to the specific tunnel...so
you might walk the MIB and get some more information that you put into your
VPN traps before you regenerate them.

Stephen Hochstetler              shochste@us.ibm.com
International Technical Support Organization at IBM
Office - 512-838-6198 (t/l 678)       FAX - 512-838-6931

                      ta.com                   To:       nv-l@lists.tivoli.com  
                      07/08/2003 11:39         Subject:  [nv-l] VPN staue 

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.


To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)

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

Archive operated by Skills 1st Ltd

See also: The NetView Web