Comments below...
I can't catch your idea very well.
Is that mean the map in the mlm node will refresh after the change of the
mlm domain collections ?
>> Yes. It is just a Collection, and that's how Collections work.
MLM domain will make use of its subnet as the default. How can I control the
node discovery in the mlm ?
>> You can turn OFF node discovery on the MLM and leave that job to Netview.
>> Check in smconfig in the Node Discovery Settings and disable discovery.
>> MLM is only capable of discovery on its own subnet - but it is capable
>> of status monitoring of anything you define in the domain collection.
How can I erase the node which have been discovered by default setting that
I don't want to be monitored ?
>> If the node is in the domain submap and you don't want it anywhere in the
>> IP map at all, then delete it. To keep it from coming back, you will need
>> to prevent netmon from discovering it. That is done with the netmon
>> seedfile (not the MLM seedfile mentioned in the netmon config dialog). See
>> the man page for netmon, the online help for netmon configuration, and the
>> Admin Guide for more info on the netmon seedfile. This is probably your case.
>> If you want it on the IP map, but not in the MLM submap, then modify the
>> domain Collection (that is, you want netmon to monitor it, not the
>> MLM, then to to Tools...Collection Editor and modify the domain Collection
>> to exclude those nodes.
>>
>> Understand that discovery and status monitoring are two different things.
>> In most cases you would use netmon to control discovery, and use the MLMs
>> for offloading status monitoring. When I use a netmon seedfile to prevent
>> the discovery of unwanted nodes, for example PCs, and use MLM for status
>> monitoring, I have never had to do anything to the MLM to prevent the
>> discovery of those PCs. Netmon handles it. So if unwanted nodes are in your
>> MLM domain collection, I suspect that it is because they are already in your
>> IP map, discovered by netmon, not by the MLM. So it is netmon you need to
>> learn more about.
Would you mind to explain more ?
-----Original Message-----
From: Leslie Clark [mailto:lclark AT US.IBM DOT COM]
Sent: Tuesday, October 05, 1999 8:23 AM
To: NV-L AT UCSBVM.UCSB DOT EDU
Subject: Re: Question about mlm_domain
Don't erase anything!
The membership in the mlm domain collections, although it starts
out with the members of the local subnet of the MLM, is configured
using the Collection Editor (under Tools..) just like any other
Collection. This means NO cut/paste, add/delete. Use the editor.
You can define the membership based on Attributes, Subnets,
Object Lists, or combinations of other Collections. When you
change the definition you will automatically see the membership
change in the grouping for that domain. In your case you might
modify the rule so that one clause is for the subnet, as it is, and
an additional clause excludes non-snmp things, and another
clause excludes printers by OID. (If you are on NT, the Collections
are SmartSets.)
More basically, though, if there are things in your database
that you do not want to monitor, I would encourage you to
exclude them from discovery as well.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
When a new mlm has been setup, our netview will automatically configure the
mlm_domain_newnode of its sub-network. But not all nodes in this subnet will
need to be monitoring.
1. Can I specify the exact ip address instead ?
2. How can I erase the map in the MLM submap only ( which do not affect my
IP map ) ?
Welcome for any comment
Thanks
|
