Re: [nv-l] Error messages in "nvcorrd.alog"

[Leslie Clark <lclark@us.ibm.com>]

When using the Query Smartset function, for traps from devices, use Origin as the comparison element. For Netview events, you can use element 2, or you can also use Origin, which Netview 'falsifies' to be the same as element 2.  I always take James' advice and make sure that the only functions connected to the Event Stream are either Trap Settings (for one or more specific events) or Event Attribute (for whole classes of events.) This drops a lot of unwanted events before getting to anything that is resource-intensive, such as Query Smartet.

Cordially,

Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit

James Shanks/Raleigh/IBM@IBMUS Sent by: owner-nv-l@lists.us.ibm.com 12/09/2003 09:24 AM Please respond to nv-l

To:        nv-l@lists.us.ibm.com         cc:                 Subject:        Re: [nv-l] Error messages in "nvcorrd.alog"

Sure.  You have a ruleset which is doing Query Smartset (collection) using attribute 2 as the source of the object id.  That means that for every trap which reaches this point, nvcorrd tries to resolve whatever is in attribute 2 to an object in the database, in order to see whether it is a member of the collection you specified.     But only NetView events have a hostname in attribute 2.  So this fails for every non-NetView event which gets this far in the ruleset.  The message is trying to tell you that your Query Collection is failing far too often and ruining your performance.  In other words, your ruleset needs to be re-designed. 

You should precede the Query Smartset portion with a Trap Settings or Event Attribute Node so that you only query the database for collection membership on the right kind of traps.  Anything else is terribly inefficient. 


James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

"Georg Gangl" <Georg.Gangl@brz.gv.at> Sent by: owner-nv-l@lists.us.ibm.com 12/09/2003 04:48 AM Please respond to nv-l

To:        <nv-l@lists.us.ibm.com>        cc:                Subject:        [nv-l] Error messages in "nvcorrd.alog"

Hi  Group members,

Our "nvcorrd.alog" file is flooded with error messages of the following
type:

2003/09/12 08:09:07      NVcollDnode.C[127] :   Object not found
2003/09/12 08:09:07      NVcollDnode.C[123] :   NVCollCmpDnode::Resolve
NVCollCmpDnode(Attr: 2 contained in UMS) Failed, no objid for attr 2,
requested object = SNM@BRZ GURU 0@SERVERS, returned obj id = 0

Does anybody know what this error messages want to tell me ?

Thank you very much for any help.

Cordially,

Georg Gangl

_____________________________
Ing. Georg Gangl
Bundesrechenzentrum Ges.m.b.H.
Hintere Zollamtsstrasse 4
A-1033 Wien
Gruppe I-PS-NW Netzwerke
Tel.:  00 43 (1) 711 23 - 3891 DW
Fax.: 00 43 (1) 711 23 - 3897 DW
mailto:Georg.Gangl@brz.gv.at 
--------------------------------------------------