Once again GREAT idea. However see my original post
We do NOT used command for automatic action we use rulesets. In an action node
I can call the script (which I do) but the trap data is not passed as command
line arguments, it exists as environment variables and I have no way to know
how many environment variables exist.
I'm not adverse to scripting. I have already tackled a number of other issues
this way - the problem I have is determining how many variables are the trap
environment data when I call my script to handle the variable format trap.
> -----Original Message-----
> From: Todd H. [mailto:netview@toddh.net]
> Sent: Thursday, October 03, 2002 1:59 PM
> To: Barr, Scott
> Cc: nv-l@lists.tivoli.com
> Subject: Re: [nv-l] Cursed Cisco Trap Formats
>
>
>
> "Barr, Scott" <Scott_Barr@csgsystems.com> writes:
> >
> > So, let me go back to my original request - how can I handle this
> > with automation?
>
> Use $* in the trap format for that OID/generic/specific that comes in.
> That'll shut trapd up and let it gracefully deal with the variability.
>
> Then script a command (using ksh, Perl, or even C if ya like) for
> automatic action that handles 3 4 or 5 varbinds appropriately as you
> wish. Send an event to TEC then with postemsg.
>
> The scripting is left as an (albeit fairly straightfoward) exercise to
> the user. You have a situation that requires some customization via
> scripting, and I'm afraid no one can shield you from having to do that
> scripting.
>
> Best Regards,
> --
> Todd H.
> http://www.toddh.net/
>
|