nv-l

Re: Problem with refresh

1999-01-20 08:48:26
Subject: Re: Problem with refresh
From: Hernan Dario Villegas <hvillega AT MAIL.BIC.COM DOT CO>
To: nv-l AT lists.tivoli DOT com
Date: Wed, 20 Jan 1999 08:48:26 -0500
Thanks for your answers.   I have configured  the Ovwdb cache in 30000  (
remember that the number of objects is 18079).  The paging space is
configured in
 2 X RAM ( I have 512 M RAM and 1 GB in paging space).
What else can I do ??





John Creasey <creasey AT OZEMAIL.COM DOT AU> con fecha 19/01/99 08:59:12 AM

Por favor, responda a Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L AT UCSBVM.ucsb DOT edu>

Destinatarios: NV-L AT UCSBVM.ucsb DOT edu
CC:      (cci: HVILLEGA/BIC)
Asunto: Re: Problem with refresh




How do you set your ovwdb cache size?


-----Original Message-----
From: Discussion of IBM NetView and POLYCENTER Manager on NetView
[mailto:NV-L AT UCSBVM.UCSB DOT EDU]On Behalf Of James Shanks
Sent: Wednesday, 20 January 1999 00:08
To: NV-L AT UCSBVM.UCSB DOT EDU
Subject: Re: Problem with refresh


At least some of what you are seeing is normal.  netmon will not respond to
your demand poll requests until he has done all his initial work, and this
includes loading the entire topology database and doing all the daily
config checks (SNMP requests) specified in his SNMP configuration.  So in a
large network it might very well take two hours for him to respond to a
demand poll you initiated immediately after start up.  Development is
looking at changing this behavior so that user requests get more priority,
but I can make no promises.

As for the collection, I am not sure what to say.  The collection will be
maintained by nvcold, which will be very active at the start of things,
since he must react to every ovwdb change netmon makes.  Both netmon and
nvcold will be making a lot of ovwdb calls.  The only thing I can think of
which would improve this performance is making sure that you have enough
paging space (between 2 - 2 1/2 X  RAM) and that your ovwdb cache size is
at least 20 per cent larger than the number of objects you have in the
database.  If that is still not enough, I recommend you open a problem with
Support and get someone to look at your situation more closely.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Hernan Dario Villegas <hvillega AT MAIL.BIC.COM DOT CO> on 01/18/99 10:01:05 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks)
Subject:  Problem with refresh





Hi all:

I have installed TME10  NetView 5.1  in a Risc/6000 H50 with 512 Mb RAM  2
microprocessors, 16 Gb DD, always the machine works with 85-95 %   time of
microprocessor free.
The   ovtopodump  reports:

NUMBER OF NETWORKS: 877
NUMBER OF SEGMENTS: 901
NUMBER OF NODES: 7390
NUMBER OF INTERFACES: 8397
NUMBER OF GATEWAYS: 400

And the ovobjprint |head -1  reports:
Number of objects defined in the database: 18079

I have seen that when I start  NetView  the demand poll waits approximately
2 hours to start to function and the collections (p.e.  a collection of
routers down)  do not actualizate the real state of the nodes during this
time.
May somebody tell me if this is normal? if not, what can I do to optimice
this startup time?.

Thanks,


Hernan D. Villegas.
Telecommunications Analyst.
Bancolombia.

<Prev in Thread] Current Thread [Next in Thread>