Do you have two separate trap settings or just one? If you have just one, with
both traps selected, then it should trigger only once. If you have two, then it
will trigger twice because the match for "3119.1.1" is a match for anything
which follows the last "1", so "3119.1.100" actually matches both.
I just posted an append earlier this week in which I told Ken Freeman that
there was an internal defect open on the fact that the match in a Trap Settings
node was too broad and that the fix would be included in the next round of
maintenance. Until then you will have to live with this or code around it.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Eirik Tysse <eirik.tysse@DNB.NO> on 11/24/99 02:55:38 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Problem with inhouse snmp trap id's/Rulesets
Hi all,
We use snmp traps extensively with inhouse applications , using our own
private enterprise ID (3119)
Today I saw something funny:
In a Netview ruleset, we have an action node after the following trap id's:
3119.1.1 6 4
3119.1.100 6 4.
However, if I send snmp trap id 3119.1.100 6 4, the ruleset triggers the
action node twice, both on "1" and "100".
You see ?
Am I missing some basic mib/snmp knowledge here ?
Mvh/Regards,
Eirik Tysse
Den norske Bank
Networked Systems Management
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that DnB cannot
accept any payment orders or other legally binding correspondence with
customers as a part of an email.
This email message has been virus checked by the virus programs used
in the DnB Group.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
|