Re: [nv-l] Generating Topology Map with MLMs
James i will cut this to short, what
i want to achieve here is to have a single topology MAP having showing
subnet of different customers. NOW i cant just give my NetView access to
all these subnet( these are not just subnet but complete enterprise networks).
Now here i will go with your recommendation that what should i do, use
MLM or install NetView in each of customers network?
I am not sure that NetView can share
Topology map with other NetView servers? and if yes, then how?
forwarding events is not a problem but
i also want to have single console of Topology map of all networks that
are being managed!
|James Shanks <jshanks AT us.ibm DOT com>
Sent by: owner-nv-l AT lists.us.ibm DOT com
06-09-05 07:11 PM
Please respond to
nv-l AT lists.us.ibm DOT com
|nv-l AT lists.us.ibm DOT com
|Re: [nv-l] Generating Topology Map with
MLM is not a substitute for NetView but an adjunct
to it. Whether it is
suitable or not for the purpose you want, only you can decide.
MLM only discovers devices in one subnet; it's own. That's why you
need one for each subnet of the customer's network if you want to use MLM
discovery. it is possible to manually add a few devices in another
to an MLM for monitoring, but there is no way to get it to automatically
monitor or discover more than its own subnet. It is not a tiny NetView.
It's original design purpose was to monitor remote locations connected
the central NetView by slow WAN links which could not sustain the constant
ping or SNMP traffic that Netview monitoring requires.
MLM's communicate with NetView via SNMP sets and gets, and also traps.
have to have both the read and write community names correct in
ovsnmp.conf. You can also configure the trapd destination table in
to threshold on outside traps. Once netmon finds an MLM using an
with the read community string, it send an SNMPset to that MLM telling
to start reporting the discovery and monitoring data it has to the central
location. The nodes the MLM has discovered will get added to NetView
topology provided that netmon can ping them to verify their authenticity.
Combining two distinct customer networks under one NetView will only
well if they have separate and distinct addressing schemes, since
duplicates are not allowed, unless you also deploy CNAT gateways
them to do translations.
You might profitably spend some time reading in the MLM doc before making
your deployment decision. You might also deploy a test one and play
it a little too. That's easy enough to do.
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group