Michael,
Another alternative is to configure the router to use the same source
address in all of the traps that it sends. I don't know what type of
routers you are using. The format of the command for Cisco routers is:
snmp-server trap-souce <interface-name>
Use an interface name that has the DNS reverse entry defined for it's IP
address. This may vary slightly depending on your IOS level. Other router
vendors may provide a similar feature.
Karin
-----Original Message-----
From: owner-nv-l@tkg.com [mailto:owner-nv-l@tkg.com]On Behalf Of
sylvia.koch@emprise.de
Sent: Thursday, December 14, 2000 10:19 AM
To: IBM NetView Discussion
Subject: Antwort: Re: [NV-L] SNMP Configuration
Michael,
if you resolve all interface addresses of a router to the same name, you
can correlate the Interface Down and Interface Up traps in your ruleset as
follows:
The list of comparisons in your Reset on Match template should contain two
entries:
2 Equal to 2
3.2 Equal to 3.2
The first entry ensures, that the two traps come from the same router.
The second entry ensures, that the same interface goes down and up. It
compares the second token in the third variable. The third variable
contains the trap text "Interface xxx Down" or "Interface xxx Up",
therefore the second token is the name of the interface.
Hope this helps
Sylvia
michael.hamm@
tudor.lu An: IBM NetView Discussion
<nv-l@tkg.com>
Gesendet von: Kopie: (Blindkopie: Sylvia
Koch/Emprise)
owner-nv-l@tk Thema: Re: [NV-L] SNMP
Configuration
g.com
14.12.00
16:11
Bitte
antworten an
IBM NetView
Discussion
yes, this was also my first idea, to use /etc/hosts to solve the problem,
BUT...
the an other RuleSet did not work anymore.
The ruleset check for down going interfaces. after a interface down, it
waits for 5 minutes to recieve an interface up. if no interface up
aproache, it send a mail to me. (I use varbind 2)
finally after making somw tests, this ruleset can not differ anymore,
when for example interface 3 goes down by error and interface 4
comes up by admin. Know all interfaces get resolve to the routername.
By the way,
Is there a Lekture, like "Rulesets for Dummies" or some equal????
"Leslie
Clark" To: IBM NetView Discussion
<nv-l@tkg.com>
<lclark@us.ib cc:
m.com> Subject: Re: [NV-L] SNMP
Configuration
Sent by:
owner-nv-l@tk
g.com
12/14/00
03:45 PM
Please
respond to
IBM NetView
Discussion
One solution is to add name resolution for the addresses that the
traps come from. Make it the same name as the Selection Name for
the node. If your DNS does not allow two addresses to resolve to
the same name, then put them in /etc/hosts.
Another solution is to make sure the nodes are discovered by the
address that sends the traps. You can do this by putting the name
(or the address) in a seedfile, and deleting and rediscovering the
node.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
michael.hamm@tudor.lu@tkg.com on 12/13/2000 04:48:46 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: nv-l@tkg.com
cc:
Subject: [NV-L] SNMP Configuration
hi,
the map application figure out the routers and it's
interfaces in the network. But with DNS maybe just
one single name is asigned to one of the planty
router interfaces.
It seems that NetView SNMP applications are
not clever enought to check back to its database,
to find out, that all this interfaces fit to one and the
same router.
my problem:
My filter don't work on authentication failure traps,
because the trap came in with an ip-adresse, which
is not asigned to the routers name....
maybe there is an other solution than set up a filter
with more than 20 event attribute nodes, one for every
router interface???
thanks in advance
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
|