I think you would have to do what everyone did before there was RFI.
The usual approach was to ignore most of the events, and use rulesets to
handle
classes of events. Operators would only react to events that passed the
filters of the rulesets, and ignore the red areas of the map, focusing on
the device pointed out by the ruleset. A separate events display that
subscribes to that ruleset helps them with that focus.
- Core switches and routers: Interface Down/Up are very important.
- Remote routers: Node Down events - check for corresonding
interface events from core device; if none, then this is the cause
- Ignore as many lower-level remote devices as possible; for significant
remote servers and switches Node Down, check status of corresponding
remote router; if it is up, this is an isolated outage.
Others may have sample rulesets for T/EC and/or Netview that
implement this, but it is not likely that they will help your case
specifically.
They might be useful as a guide, however. Anybody?
Another approach might be to run them both, but let netmon poll the
routers.
This might result in double polling, if you are using more than one
Netview.
The RFI function enables netmon to generate special events - network
unreachable, Router Down, etc. You would still get the flood of down
events for downstream nodes, and you would still take the approach of
ignoring them, but these RFI events would simplify your ruleset processing
and reduce or eliminate the administrative burden of maintaining tables
of dependancies.
Either way, it is important that you not monitor anything that you do not
need to monitor. Specifically, if you do not really need every workstation
in the map, take measures (seedfile) to exclude them from discovery.
If the trap rate is your main concern, rather than notification, then this
is
your first line of attack.
If you are going to do RFI, you should try to get to the lastest code. It
is
always improving.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
Kevin Smith
<c-kevin.smith1@w To: Nv-L
<nv-l@lists.tivoli.com>
com.com> cc:
Subject: [nv-l] RFI
05/10/2002 03:59
PM
Lists,
My servers IBM f50 AIX 4.3.3 Netview 6.02 MLM. I wold like to
implement rfi but the following says it's not possible:
CF Document ID: 1016900 - IBM Tivoli NetView: Can Netview 6.02 monitor
routers using RFI and MLM run at the same time?
Problem Desc: Can Netview 6.02 monitor routers using RFI and MLM run at
the
same time?
Solution: When running 6.02 Netview Unix (this was only tested on Unix
Netview) do not
use MLM's to monitor Routers when using RFI. This is a current limitation
on
the product.
Is there anyone that has an MLM and has the functionality that RFI has
without implementing RFI. The functionality I seek is that when a link
goes
down I dont get traps from netmon for every interface of the node behind
that link reporting down. Instead I would like to see that node be
unreachable and receive an alarm from the source of the failure.
Sincerely
Kevin Smith
System Administrator
410-965-0328
c-kevin.smith1@wcom.com
9-5p.m (est)
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|