That might explain it. We have four. And the collections I'm defining are
rather large. Its probably trying to update the wrong ones first, getting
rejected by those MLM's, and getting onto the appropriate one when my back is
turned.
Any ETA (even rough) on that release?
Thanks
Art DeBuigny
debuigny@dallas.net
James Shanks wrote:
> Art -
> Could it be that what you are seeing is described in APAR IX79362?
> Currently, when you update the collection for any MLM, it gets
> re-distributed to all MLMs, so the more you have the longer it takes. The
> fix for this APAR will change that, so that only the appropriate MLM gets
> updated. The fix will be included in V5.1.1 and U459387 for V4 as soon
> as they are available.
>
> James Shanks
> Tivoli (NetView for UNIX) L3 Support
>
> Art DeBuigny <debuigny@DALLAS.NET> on 12/10/98 06:55:34 PM
>
> Please respond to Discussion of IBM NetView and POLYCENTER Manager on
> NetView <NV-L@UCSBVM.UCSB.EDU>
>
> To: NV-L@UCSBVM.UCSB.EDU
> cc: (bcc: James Shanks)
> Subject: Mid Level Managers
>
> Hello;
>
> I have a question concerning the Mid Level Managers under NetView 5.1 on
> AIX 4.1.5.
>
> We have several Mid Level Managers. When I go to change the collection
> to add more nodes to its polling list, it seems to take forever for that
> change to make it to the alias tables on the MIB. I assume that there
> is some internal process NetView is running, maybe once a day, to update
> its MLM's. Is there a way to 'kick' NetView, making it update the MLM's
> right away? Its difficult to test when you have to wait so long to get
> the collection moved over to the MLM.
>
> Art DeBuigny
> debuigny@dallas.net
|