I am not sure what you are actually asking. Yes, it is netmon who
generates all those traps, Node Down, Node Marginal, Node Up, and so on.
And that is why you do not see them. If you ant to see those, then your
script will have to generate those as well.
>From the sound of things, these interfaces and the nodes they are attached
to are already on the map. How are you bypassing netmon from polling them?
Be aware that nothing you do with the 58916871 will affect what is in the
topology database, so if netmon is also monitoring those interfaces, he
will override your status when he sees the need. While I don't want t
stifle your innovation, you should be aware also that what you are doing --
writing your own script to bypass netmon -- is not really supported. The
purpose of the status trap was so that you could change the status of items
you put on the map which were not being monitored by netmon, such as
applications and other non-IP resources.
I'd like to see an MLM on Linux too, but I fail to see how that should
cause you to do this. There are plenty of other MLMs, AIX, Solaris,
Digital, HP, and NT, and they can run on the oldest, cheapest boxes you
can find. Any box you can run Linux on, you can run NT. I have seen an NT
MLM run on an old 486, 83 MHz box, which didn't have enough horsepower to
drive the full NetView for NT GUI. Once it was running, the display was
disconnected.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
Stephen Elliott <selliott@epicrealm.com>@tkg.com on 02/28/2001 09:34:04 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: "'nv-l@tkg.com'" <nv-l@tkg.com>
cc:
Subject: [NV-L] Override status
Hello, All.
NV 6.0.1 on Solaris 2.6.
A question for James Shanks or Leslie Clark.
I have a task to write a status polling script that is to run in each of
our
data centers, thus off-loading status polling from NetView for these
interfaces. Netmon's polling queue is at it's limits and we can't do MLM's
as IBM has not developed a Linux MLM yet.
Down/Up notifications for interface status will be sent by the sript to
NetView via the 58916871 trap. So far, this works fine and the status of
the
interfaces in question get changed properly (the
nvevents.overrideCompundStatus is set to True as per your Override Status
document). Status is propagated upward for the Node as well, reflecting
Marginal or Critical based upon the submap propagation rules. The only fly
in the ointment so far is that there are no Node Down events being
generated
and I'm assuming that this is because netmon typically generates these when
it detects that all interfaces in a given node are down. Since we're
effectively bypassing netmon for interface status on these devices, it
won't
know when to gen a trap. Can you validate this for me? I'm hoping I've
missed something simple, otherwise I've got more code to write.
Regards,
Steve Elliott
Sr. Network Mgmt. Engineer
epicRealm, Inc.
214-570-4560
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|