nv-l

FW: [nv-l] Netmon initialization - how to speed it up?

2002-08-26 15:10:58
Subject: FW: [nv-l] Netmon initialization - how to speed it up?
From: "Binder, Karin" <karin.binder AT nwa DOT com>
To: "Nv-L (E-mail)" <nv-l AT lists.tivoli DOT com>
Date: Mon, 26 Aug 2002 14:10:58 -0500
Hi all, 

Homework complete, but with no improvement.  Summary:

Tried nvTurboDatabase space and speed:  no change.
Ran Best/1 - confirmed hardware is adequate, no I/O delays, etc.
Also added -Y option to netmon.lrf:  no change.

Anything else I can try?  7.1.x is looking mighty good right now....

Karin

-----Original Message-----
From: Binder, Karin 
Sent: Monday, July 01, 2002 4:15 PM
To: Nv-L (E-mail)
Subject: FW: [nv-l] Netmon initialization - how to speed it up?



Thank you Stephen for all of the suggestions.  I've been doing some homework:

1. I've run nvTurboDatabase on both systems.  BUT, it was quite a while ago 
with the space option for a different problem.  We have not run the speed 
option.  Further,  I found that production is not running that way now. Most 
likely missed re-running nvTurbodatabase the last time we rediscovered the 
database.  Not good.  This will be corrected as soon as we're out of our 
holiday freeze period, and I'll try the speed option at the same time.  I have 
hopes this will make a significant difference for us.  

2. ovwdb cache is huge.  more than adequate.

3. The system has 3G memory and 3G paging.  We do have a performance tool, but 
my associate who has access to it is in Europe on vacation.  Good for him, not 
so good for me.  We were going to schedule some time to watch it during startup 
on the next planned outage.  Unfortunately, there have been some unplanned 
outages instead.

4. Both test and production use the same three DNS servers in the same order in 
their resolv.conf files.   I know this is frequently a problem area, but does 
not appear to be the bottleneck here.

5. /etc/nsv.conf contains "hosts = local,bind4"  on both systems

6. There are 41 host entries in /etc/hosts on production.

7. /usr/OV/databases is part of /usr/OV file system.  Not ideal, but better 
than as part of /usr.  The disk is part of a storage array.  It is striped.  

I will follow up with nvTurbodatabase and running Best/1 and see where it leads.

Thanks again,
Karin 

-----Original Message-----
From: Stephen Hochstetler [mailto:shochste AT us.ibm DOT com]
Sent: Friday, June 28, 2002 4:04 PM
To: nv-l AT lists.tivoli DOT com
Subject: Re: [nv-l] Netmon initialization - how to speed it up?


Karin,

Some of these things are in Redbook
http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246019.pdf


Over the years I have experienced slow netmon startup at times.    You say
that you are on NetView 6.0.3.    Here are some things that has helped me.

1.  Have you ever run nvTurboDatabase on both systems?    How large is your
overflow file in production?
      this will impact performance on databases larger than 30K in a very
positive way.
2.  What is the size of your ovwdb cache?
      is it big enough?
3.  How much paging space does your system have?
      do you have a performance tool that can monitor your system
performance while it comes up?
4.  Does both your test system and production system use the same DNS
configuration?    Do you have more than one DNS in your resolv.conf?
      This can make a HUGH difference.
5.  What does your /etc/netsvc.conf look like on both systems?
      name resolution can really slow down netmon initialization
6.  How many entries do you have in your /etc/hosts in your production
system?
      is it large enough, and is netmon looking at this for every name?
7.  where do you have your /usr/OV/databases ?   Is it on its own
filesystem?   Is it stripped across multiple disk drives if more than
100MB?
      this is another general NetView performance item for large production
systems.    For good performance on fast systems, I have used the number of
100MB of database per disk drive for striping.

If all the above looks good...the last thing I did was to make the NetView
server a DNS, by running named.   Then we created some scripts that read
the NetView database and generated the DNS configuration files for all the
hosts in the NetView database.   While a DNS usually has just one interface
for each device, these files had ALL interfaces in the DNS config files.
This made netmon very happy because he checks every interface as he
initializes.  (at least I think so).   So for 32K objects in the database,
the initialization went back to a few minutes instead of over an hour.
There may have been changes made in V7 of NetView that helps with this, but
this is what we did a while back.



Kind regards,
Stephen Hochstetler              shochste AT us.ibm DOT com
International Technical Support Organization  - Austin
Office - 512-436-8564                      FAX - 512-436-8701

ITSO redbooks at  http://www.redbooks.ibm.com


---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe AT lists.tivoli DOT com
For additional commands, e-mail: nv-l-help AT lists.tivoli DOT 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 AT lists.tivoli DOT com
For additional commands, e-mail: nv-l-help AT lists.tivoli DOT 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)


<Prev in Thread] Current Thread [Next in Thread>
  • FW: [nv-l] Netmon initialization - how to speed it up?, Binder, Karin <=