If you are forwarding such events to T/EC, these extras are not a problem
since it is common in tec rules processing to discard duplicates. If you
are
using a simple Netview rule to send your page, I guess you will have to
make it fancier to account for the duplicate. If you have just customized
the
event directly to do the paging, it is time to get fancier and switch to
using
the netview ruleset editor to pre-process the events. I know I have a
little
learning curve ahead of me, too. Makes me glad I saved all of those
appends from James about traps and rules.
Isn't it nice to know that customer requests are heeded?
Sample rulesets, anybody?
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
I followed up with Tivoli Tech Support since they hadn't volunteered the
information that this was a new feature in 5.1.2 (thank you, Leslie.) I was
told that 'this was a modification due to a request from a major customer.
The customer wanted pinging a node to guarantee to update the nodes
status.'
I looked and couldn't find any difference between the normal traps and the
unwanted traps - Tech Support also says there is no difference. They
didn't
have any suggestions for a workaround and said I should send an enhancement
(or un-enhancement, as the case may be) request to netview AT tivoli DOT com.
Kristi Smith
Mentor Graphics Corporation
(503) 685-1971
kristi_smith AT mentorg DOT com
-----Original Message-----
From: Leslie Clark [mailto:lclark AT US.IBM DOT COM]
Sent: Tuesday, October 26, 1999 6:51 PM
To: NV-L AT UCSBVM.ucsb DOT edu
Subject: Re: Demand Poll Question
New feature in 5.1.2. Lots of up and down traps generated when you do a
demandpoll, or when you do a test..ping. Pagers are going off all over the
world, I know. Take a close look and see if there is any difference
between
them - maybe a different source character (something other than N)? I
thought I saw something today. I'll look again tomorrow.
The thing to ask yourself is "What customer problem were they trying to
solve
when they added this function?" and then figure out how to take advantage
of it.
Lot's of people on this list are processing these events in rulesets. I'm
very
confident that they will share with the rest of us what the impact of this
change
is for them and what new customers need to do about it. Right???
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
We installed NetView fairly recently and are having a problem related to
demand polls. If we initate a demand poll on a device that is up and has a
green status to prod discovery or get a current interface status, we get
interface up traps and node up traps in the event window. Since we plan to
page our on-call person on interface and node up/down traps, this will be a
problem for us.
I used NetView while at a former job and don't remember this type of
behavior on a demand poll. I verfied with one of my former co-workers that
they don't get those events on a user-initiated demand poll. I asked
Tivoli
Technical Support about this and they said it is working as designed.
Can anyone shed some light on this?
Environment: NetView 5.1.2, Tivoli 3.6.1, Solaris 2.6
Regards,
Kristi Smith
Mentor Graphics Corporation
(503) 685-1971
kristi_smith AT mentorg DOT com
|
