Luca -
I cannot answer for your problem #1 with slow performance.
But #2 is not a problem. That is how it works. A read-only map does not get
map changes of this sort without a refresh. This is what distinguishes a
read-only from a read-write map. This means that the owner of the read-write
map has to plan his changes and coordinate them with the read-only map users if
he wants them to get them after the maps are open.
James Shanks
Tivoli (NetView for UNIX) L3 Support
"Smeriglio,Luca,VEVEY,FC-SIL/INF." <Luca.Smeriglio@NESTLE.COM> on 02/11/2000
05:20:31 AM
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/Tivoli Systems)
Subject: Refresh Problem with Read-only ipmap
Dear list,
I'm having some refresh/synchronisation problems between the main
read-write Map (running on the NV6k server) and read-only Maps opened
on other non-AIX boxes through XWindows (telnet on the server, then start
nv6k in read-only).
1/ when there's a status change, it takes sometimes more than 2 minutes for
this change
to be reflected on the read-only maps, compared to the server.
2/ when there's a topology change done on the read-write map (for example,
managing/unmanaging nodes, deleting a node from all submaps, ...), this
change is
only taken into account by the read-only maps after a File/Refresh or a
reload of the GUI.
I can't use Netview Client on those boxes unfortunately.
Any idea how to improve those issues ?
Is this the normal behaviour of a read-only instance ?
Thanks for your help !
Cheers,
Luca
Luca.Smeriglio@nestle.com
Luca Smeriglio
Nestec S.A. / Informatique du Centre
Network Architecture & Tivoli Coordination
Av. Nestl
é 55 CH-1800 Vevey (Switzerland)
*+41(021) 924 2653 7 +41 (021) 924 4589 * A1-320
This message is intended only for the use of the addressee
and may contain information that is privileged and
confidential.
|