I recently migrated a customer from V4 to V5.1.2 including their database
and found that on the old system as well as the new one, unmanaging a node
with a single interface did NOT unmanage the interface as well. I attribute
this
to some sort of database corruption introduced early in V4, since they had
been using the same database for years without rediscovery. I did a test
rediscovery to verify that it worked properly on a new database (unmanage
the node and the interface gets unmanaged too), and restored their old
database with the recommendation that they rediscover before calling
support about any map or topology problems. An interesting side effect of
this 'corruption' was that they were able to delete a node from one map
and have it disappear from a second map automatically when it was next
opened. They like that feature and may never rediscover on account of it!
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
==============================================================
Hallo Dietmar,
I think is is normal that the Interfaces are not acknowledge if you ack.
the
Device. You must each and every one Interface ack. But if you are a Device
set to unmanaged all Interfaces are unmanaged.
Gruus Dirk
-----Ursprüngliche Nachricht-----
Von: Dietmar Gaulhofer [mailto:dietmar_gaulhofer@AT.IBM.COM]
Gesendet am: Mittwoch, 9. Februar 2000 11:26
An: NV-L@UCSBVM.UCSB.EDU
Betreff: working with Collections
Hi,
I have an situation which i would like to clear - i hope someone could help
me
on that. Env. is AIX 4.3.2 and Netview 5.1.2.
If i unmanage or ack. an Node in an Collection - is then this change also
happening on the Interface level ? A Customer
has a problem that very often the Interface keeps managed. I have the same
behavior on an Testinstallation of V 6 that
if i ack. an Critical node in an specific Collection the Interface is still
in
status Critical....
Is this works as designed ? anyone have/had the same problem ?
Thanks for any help,
Kr, Dietmar
|