nv-l

RE: [NV-L] Network name resolution using /etc/networks file foralready discovered networks

2007-03-06 09:11:11
Subject: RE: [NV-L] Network name resolution using /etc/networks file foralready discovered networks
From: <Blane.Robertson AT capgeminienergy DOT com>
To: <nv-l AT lists.ca.ibm DOT com>
Date: Tue, 6 Mar 2007 08:08:28 -0600

Probably the easiest things to do would be to delete them from the map then run netmon –y to rediscover them?  Just a thought…

 

Peace,

Blane Robertson

Capgemini / Dallas

Enterprise Systems Management/ Capgemini Energy

Office: +1 214 879 1666/ www.us.capgemini.com

 

Whether you think you can, or you think you can’t, you’re right! – Henry Ford

 

 

 


From: nv-l-bounces AT lists.ca.ibm DOT com [mailto:nv-l-bounces AT lists.ca.ibm DOT com] On Behalf Of Leslie Clark
Sent: Tuesday, March 06, 2007 6:48 AM
To: Tivoli NetView Discussions
Subject: Re: [NV-L] Network name resolution using /etc/networks file foralready discovered networks

 


I have not used that feature in a long time, but I saw the same thing. I needed to rediscover the networks to get them named.  You might try unmanage/manage on the network object, but I think you may be out of luck.  Networks don't get updated during configuration polls like nodes do.

Cordially,

Leslie A. Clark
IT Services Specialist, Network Mgmt
Information Technology Services Americas
IBM Global Services
(248) 552-4968 Voicemail, Fax, Pager


_______________________________________________
NV-L mailing list
NV-L AT lists.ca.ibm DOT com
Unsubscribe:NV-L-leave AT lists.ca.ibm DOT com
http://lists.ca.ibm.com/mailman/listinfo/nv-l (Browser access limited to 
internal IBM'ers only)
<Prev in Thread] Current Thread [Next in Thread>