Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[nv\-l\]\s+\[NV\-L\]\s+Ruleset\s+trace\s+\-\s+Query\s+Database\s+Field\s+not\s+working\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [nv-l] [NV-L] Ruleset trace - Query Database Field not working (score: 1)
Author: James Shanks <jshanks AT us.ibm DOT com>
Date: Fri, 10 Jan 2003 09:31:07 -0500
Two answers to your two questions. (1) The command to trace ruleset operation is nvcdebug. You can see the various options in the man page. But the best thing to do wen debugging ruleset is to issue
/usr/local/webapp/mharc-adsm.org/html/nv-l/2003-01/msg00011.html (15,700 bytes)

2. [nv-l] [NV-L] Ruleset trace - Query Database Field not working (score: 1)
Author: Bocock Leonard <Leonard.Bocock AT siemens.com DOT au>
Date: Fri, 10 Jan 2003 12:46:54 +1100
List NV7.13, Solaris 2.8. I have a simple ruleset not working: An 'interface down' trap sets a Database Field CorrStat1, Origin, to a value of "1", and forwards the trap. If I send an 'interface down
/usr/local/webapp/mharc-adsm.org/html/nv-l/2003-01/msg00162.html (11,933 bytes)


This search system is powered by Namazu