David,

When discover new nodes is off you can run a netmon -y to reload the
seed file this may put the connection back, but if not here are a couple
of other suggestions

Do you have multiple maps?  The connection may exist in another map so
it will not rediscover as it is still in the database... Try deleting
from all maps and then rediscover it (netmon -y)

If there is only one map try deleting and rediscovering the object it
connects and see does the connection return (again netmon -y  if the
object does not return try putting the object into the seed file and run
netmon -y)

Of course you should try these tasks in test first to ensure you do not
get undesired results :-)

Regards

Colin Mulkerrins
Enterprise Systems Management
An Post




-----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT 
com]
On Behalf Of Liu, David
Sent: 02 February 2005 09:29
To: 'nv-l AT lists.us.ibm DOT com'
Subject: [nv-l] Mis-delete connection


Hi list,

By mistake I cut a connection instead of a object, but I cannot past it
back. And NV is not discover it itself (I turned discovery new nodes
off). Did anyone give a clue?

Rgds,
David


***********************************************************************************
This e-mail and its attachments, is confidential and is intended for the 
addressee(s) only. If you are not the intended recipient, disclosure, 
distribution or any action taken in reliance on it is prohibited and may be 
unlawful. Please note that any information expressed in this message or its 
attachments is not given or endorsed by An Post unless otherwise indicated by 
an authorised representative independently of this message. An Post does not 
accept responsibility for the contents of this message and although it has been 
scanned for viruses An Post will not accept responsibility for any damage 
caused as a result of a virus being passed on.
***********************************************************************************