nv-l

Re: Re: Inline action fails in ruleset

2000-11-17 09:27:46
Subject: Re: Re: Inline action fails in ruleset
From: James_Shanks AT tivoli DOT com
To: nv-l AT lists.tivoli DOT com
Date: Fri, 17 Nov 2000 09:27:46 -0500
The problem with community strings in NVC is addressed by IY11761 whih will
be part of 6.0.2 and 5.1.4.  If you re having a serious poblem as a result
and require an efix for it, please contact Support.

If you want help with your inline action problem then you should also call
Support.  nvcorrd builds those scripts and executes them serially, he is
not multi-tasked, and thus I don't see how one user can interfere with
another.

James Shanks
Team Leader, Level 3 Support
 Tivoli NetView for UNIX and NT



"Gruner Mike" <mike.gruner AT rfv.sfa DOT se> on 11/17/2000 02:58:00 AM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

To:   nv-l AT tkg DOT com
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  [NV-L] Re: Inline action fails in ruleset




We suspect the inline action script which we had running in 2 different
event
workspaces overwrote in the /usr/OV/tmp/@@uactions. Had different users too
+
several workspaces running the inline action at the same time. Now we try
to reduce the workspaces that are running the inline action. We found out
that the syntax error problem wasn't in our script but in the
/usr/OV/tmp/@@uactions
which looked very strange at times ; overwritten or not complete
information in
it.

By the way the NVC variable is set to funny values in the @@uactions.
Our community is : xxxxxx  and strings are appended to it in  the
@@uactions.

Mike Gruner

>The inline action node builds a script called /usr/OV/tmp/@@uactions in
>which it executes you script or command, so yes, the syntax error message
>indicates a script failure that you should investigate.  I don't see that
>the wait interval has anything to do with the failure but that is
something
>you will have to decide.
>Increasing the wait when the script executes correctly will have no
effect.
>But when it doesn't, how long do you want to hold up event processing
>waiting for it to finish?  I would be looking into the failure and also
how
>many on these inline actions you have running at one time.
>
>As for filtering, you could have two event attribute nodes in parallel if
>you want , something like this:
>    rs_node 1 connects to event attribute1 which connects to rs_node 2
>     rs_node 1 connects to event attribute2 which connects to rs_node2
>
>So if event attribute 1 looks for "BRIO/1" while event attribute 2 looks
>for "BRIO/4", those which fail event attribute 1 will pass attribute 2 and
>vice-vera, and those which are neither of these will fail.    I don't
think
>it will help in this case but the Event Attribute node also lets you
>specify a word in a variable using a dotted decimal type notation.  So for
>example, the second word of the third trap variable may be specified as
>"3.2".
>
>James Shanks
>Team Leader, Level 3 Support
> Tivoli NetView for UNIX and NT



"Gruner Mike" <mike.gruner AT rfv.sfa DOT se> on 11/16/2000 07:28:00 AM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

To:   nv-l AT tkg DOT com
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  [NV-L] Inline action fails in ruleset




Hello,
have an inline action which is filtering out Cisco messages containing
BRIO ,
FMT and TX strings on Interface Down / Interface Up .
The problem is that sometimes that those messages get passed  by the inline
action anyway. The inline action takes about 0.6 seconds to execute.
We have a wait interval of 3 seconds in the inline action.We get the
following
error entries in nvcorrd.blog :

2000/11/16 12:01:06    UserExitDnode.C[131] :   Inline command
'/usr/OV/RFV/scripts/stop_bri.sh' failed. error data:
/usr/OV/tmp/@@uactions[12]: 0403-057 Syntax error at line 26 : `'' is not
matched.

Now some questions :

Is the entry in the nvcorrd.blog related to the fact that some messages are
passed by
the inline action when they shouldn't  ?

Should we increase the wait interval from 3 seconds to 3 + ?

Can this filtering be done some other way ? We tried the Event Attribute
decision Node but since our argument strings vary
e g BRIO/1 or BRIO/4 and so on we can't have EXACT match.

Awaiting  eagerly suggestions

Mike Gruner

_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l




[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread
Index]
[Search Page]

_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l


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