Phillip,
Yes the collections you define affect nvcold startup. It will also affect other
things like snmpCollect or assigning of nodes to MLM's using collections.
It is not so much to do to the number of collections than it is the time it
takes
to resolve them. I have found that certain ways of creating collections are
better
than others. For example, it is always better to use a regular expression than
a
list of node names. Specific nodes in a list are really slow in being evaluated
by nvcold. Regular expressions are orders of magnitude faster.
I would recommend the following approach to determining the best rule to use
for a
given collection:
1. Determine the time it takes for nvcold to evaluate the collection. The best
way to do this is with nvUtil. First do:
nvUtil g Collection_Name
This will show you the rule used. Then do this command substituting the
collection rule from above:
time nvUtil e "Collection_Rule_From_above"
The time (or timex) command will show you how long it takes nvcold to evaluate
the
rule. Note that you could just run nvUtil l Collection_name, but I think nvcold
caches the members of a collection in memory, so you won't really get a good
measurement.
2. You can try different rules that evaluate to the same set of nodes, to see
which one is faster. Play with regular expressions rather than a speicified
list. This is really helpful you have a naming convention in your Network.
3. Change the rules to in the collection either on the command line with
nvUtil,
or using the collectioned GUI to the rule that is the fastest for that
collection.
Philip_Guerra@TIVOLI.COM wrote:
> Environment:
> Sun Ultra 250 running Solaris2.7, TME 3.6.2 and NetView 6.0
> 1 gig of RAM
> < 20,000 Objects in the db
>
> I have had to create a number of Collections or SmartSets, as they are now
> called. Some of them are simple and just use a network segment and some are
> lists. Some have boolean components, like and/or and some of these are nested
> in others. With all these collections, it has appeared to me that nvcold
> takes
> forever, ~30 minutes, to start or initialize after an ovstart. I have about
> 30
> SmartSets and planning to add more. The Netview gui also takes a while to
> synchronize after starting. Is this behavior with nvcold due to the number of
> SmartSets? Is the slow synchronization at startup due to netmon, nvcold, or
> some other combination?
>
> Regards,
> Philip
>
> _________________________________________________________________________
>
> NV-L List information (unsubscribing, policies, posting, digest version,
> searchable archives): http://www.tkg.com/nv-l
--
Ray Schafer | schafer@tkg.com
The Kernel Group | Distributed Systems Management
http://www.tkg.com
|