If you use xnmtrap and set the trap to "Log Only" It will not be sent to TEC nor display in your event windows but it will be kept in trapd.log so that you can gauge how many you are getting. You can
Thanks James, So to use "Log Only" I will have to load or build the trap entries in the trapd.conf? The <> was meant to imply the "not equal to" option. Sean Lawrence Systems Automation Ext 5728 Jame
Ok I ran the "nvcdebug -n" command. The output is as follows 2006/24/10 09:46:38 CorrelationDef.C[562] : Current running correlation: CorrelationDefinition(0x30033b08) + RootDnode + + RuleSet forward
Hello, The forwardall.rs ruleset is used be default in the Event Display, so this is where it is probably getting loaded. There is no relationship between the rulesets that are used by ESE.automation
I am trying to set up some rules to filter out traps coming for Ciscoworks. We are getting way to many now that the network guys have turned it on. Is there a way to simply drop traps that have not b
The answer to your first question is yes. In order to make a trap have the category "Log Only", you have to build a trap definition for it in trapd.conf. If you have MIBs which define these traps, th
Author: "Erdey, Raymond M" <Raymond.M.Erdey AT erac DOT com>
Date: Tue, 24 Oct 2006 10:05:35 -0500
To see if/what events are forward to TEC (1) run serversetup (2) Choose "Configure" (3) Choose "Configure event forwarding to IBM Tivoli Enterprise Console" Hello, The forwardall.rs ruleset is used b
Ok maybe someone can explain what I am seeing here. Why am I still getting a 1.3.6.1.4.1.9.1.400 trap forwarded to TEC? 2006/24/10 09:46:38 CorrelationDef.C[562] : Current running correlation: Correl
I fixed the leading . on the OID. That was an experiment. Sean Lawrence Systems Automation Ext 5728 James Shanks <jshanks AT us.ibm DOT com> Sent by: nv-l-bounces AT lists.ca.ibm DOT com 10/24/2006 1
My config is correct in the rules editor. But the output of nvcdebug -n is different. Looks like the Cisco guys might have solved our flooding problem. I still want to get this working for my own san
Sean, This may seem like a silly question, but did you remember to do a 'nvtecia -reload' after you updated the Enterprise ID in the ruleset? Sorry, I had meant to ask this last time since it's easy
I'm resending this because the last one was too large with all the appends in it or so said the list bouncer. == No way. cat your ruleset again. If the nvcorrd.alog trace shows a leading dot, then th
Yes I have been doing that. It looks like we are going a different direction with the solution for this. I will revisit NV rules as I want to learn this. Thanks for everyone's help. Sean Lawrence Sys
I saw in another response from you that you removed the leading '.' from the enterprise ID in your ruleset... This output shows that it's still there. Has there been any change since you removed it?
No way. cat your ruleset again. If the nvcorrd.alog trace shows a leading dot, then that's what is in the ruleset he loaded. And that's what the nvcorrd trace you posted shows Note that if you change
Well, I got this working. I am not seeing this behaviour. "Note that if you change your TEC ruleset after nvserverd is started, then you must restart him or reload with nvtecia." I was using nvtecia