[Top] [All Lists]

sec:unclas : [nv-l] Location.conf file changed -instructions

To: <nv-l@lists.us.ibm.com>
Subject: sec:unclas : [nv-l] Location.conf file changed -instructions
From: "Jermyn, Michael MR" <Michael.Jermyn@defence.gov.au>
Date: Fri, 24 Jun 2005 16:32:08 +1000
Delivery-date: Fri, 24 Jun 2005 07:32:52 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Thread-index: AcV4AeIzZqMLoKw6R4mBSqD0k745DQAgYP5Q
Thread-topic: [nv-l] Location.conf file changed -instructions
We make the changes on the map and then use the following script to build the 
location.conf file.
It takes a snap shot of relevent details from the dB and updates the 
location.conf file
Here is the original script we modified:


Mick Jermyn
Network Management Administrator
Defence Network Operations Centre
HMAS Harman
Canberra ACT 
Ph: 02 6127 8277
Fax: 02 6127 8239 
IMPORTANT: This e-mail remains the property of the Australian Defence 
Organisation and is subject to the jurisdiction of section 70 of the Crimes Act 
1914. If you have received the message in error, you are requested to 
immediately contact the sender by e-mail or telephone and then erase the 


-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]
Sent: Friday, 24 June 2005 00:43
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Location.conf file changed -instructions

The ipmap application is what reads that file, and it reads it at map open. A 
rediscovery is not necessary. 
Here's how  I do it. 

Method #1: the location.conf is pretty close to correct, I'm making small 
revisions or additions: 
1) Update the location.conf 
2) Close the map 
3) Open the map 
4) Delete and rediscover the things that need to be moved. 

Method #2: major revision of the map 
1) Update the location.conf 
2) On the default map, 'File..New Map'. Name it something like 'test2'. Wait 
for it to draw the map. 
3) Evaluate the results. Check /usr/OV/log/location.log. 
4) Repeat with new map names as necessary 
5) When you like what you have, 'File...Open Map', select 'default', and delete 
6) 'File...Save Map ' and save it as 'default' 
7) 'File...Open Map' and switch to the default map 
8) 'File..Open Map' and select and delete all of the test maps until you only 
have 'default' left. 
9) run 'ovmapcount -a' to get rid of symbol references to the discarded maps. 

Note: do NOT run 'ovmapcount' during the time when you don't have a map called 
Note: the location.log may complain about every single location even though 
they are correct. 
Sometimes it does this, and sometimes it does not (like when you are trying to 
report it to Support..) 
If you are sure it is correct, and it puts things where you want them, ignore 


Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager

Alejandro Gabay <Alejandro.Gabay@reuters.com> 
Sent by: owner-nv-l@lists.us.ibm.com 

06/16/2005 04:48 PM 

Please respond to



[nv-l] Location.conf file changed


Hi All: 
Is there any way to force Netview to re-read the location.conf file without 
going for a whole map rebuild? 
We are adding new segments to our network and we do not wont to lose our 
existing map customization. 
PS: Netview 7.1.3 FP2 Solaris 8. 
B. Regards 
Alejandro Gabay 
Technical Center Supervisor, Argentina 
Reuters Ltd 

----------------------------------------------------------- -----
Visit our Internet site at http://www.reuters.com

To find out more about Reuters Products and Services visit 

Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Reuters Ltd. 

<Prev in Thread] Current Thread [Next in Thread>
  • sec:unclas : [nv-l] Location.conf file changed -instructions, Jermyn, Michael MR <=

Archive operated by Skills 1st Ltd

See also: The NetView Web