nv-l
[Top] [All Lists]

RE: [nv-l] xnmsnmpconf and Topology/Status Polling intervals and other r

To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] xnmsnmpconf and Topology/Status Polling intervals and other related questions..
From: Leslie Clark <lclark@us.ibm.com>
Date: Fri, 15 Jul 2005 08:59:17 -0400
Delivery-date: Fri, 15 Jul 2005 14:00:20 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <000e01c586f8$d1c77b90$6400a8c0@corp1a95969199>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com

Yes, it will discover and draw them but from a layer3 viewpoint.  The layer3 switches will be positioned as routers between the subnets on which they have interfaces. The layer2 switches will be in the network submaps on which their management IP interfaces place them.

Cordially,

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



"John Sobrinho" <john_sobrinho@sympatico.ca>
Sent by: owner-nv-l@lists.us.ibm.com

07/12/2005 11:46 AM
Please respond to
nv-l

To
<nv-l@lists.us.ibm.com>
cc
Subject
RE: [nv-l] xnmsnmpconf and Topology/Status Polling intervals and other related questions..





Hi Leslie..
 
Thanks for your guidance...
 
one last question with regards to L2 and switch discovery. We are not using switch analyzer, so I was wondering if Netview will correctly collect info and create the topology map and it's linkink relationships ? We have a mix of L2 and L2/L3 switches, and primarily using vlans.
 
Thanks
John
 
 
-----Original Message-----
From:
owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On Behalf Of Leslie Clark
Sent:
Monday, July 11, 2005 11:47 PM
To:
nv-l@lists.us.ibm.com
Subject:
RE: [nv-l] xnmsnmpconf and Topology/Status Polling intervals and other related questions..


That's the right plan, I'd say. You could flush the xnmsnmpconf for the rediscovery and get it repopulated.
The autoadjust applies only to new node discovery. If you want new node discovery to happen only at a certain time, along with the config poll, you could set it to fixed, then put in a time like 30 hours. For config poll, put in 30 hours. Then schedule a stop of netmon, an ovtopofix -a, and a restart of netmon to runnightly. It will never get to the 30 hours. It will do all of that work at startup. Be warned, however, that it might take netmon a while to get current on status polling.

Cordially,

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



"John Sobrinho" <john_sobrinho@sympatico.ca>
Sent by: owner-nv-l@lists.us.ibm.com

07/11/2005 04:01 PM
Please respond to
nv-l


To
<nv-l@lists.us.ibm.com>
cc
Subject
RE: [nv-l] xnmsnmpconf and Topology/Status Polling intervals and other related questions..







 
 

Hi Leslie..

 

Thank you for your assistance..

 

Since most of our topology db and object db is dated, we would probably would want to start from scratch. Our seedfile, and location.conf file is  clean. Would it be a matter of just running the clear databases (save customizations) routine from Server setup to generate a new map and topology, and object dbs  ? or is there a little more to it than that ?


We still need to review and clean up xnmscnmpconf, we could nuke the whole thing and let netview "auto populate it" after deleting the databases and forcing a new fresh discovery. But I still can't seem to find how to schedule the config poll, and details on default settings of - - - are scketchy I assume netview would use the  Auto Adjust.. (I still have to look for documentation on how Auto adjust works).  

 

Cheers,
John

 

-----Original Message-----
From:
owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On Behalf Of Leslie Clark
Sent:
Thursday, June 30, 2005 7:41 AM
To:
nv-l@lists.us.ibm.com
Subject:
Re: [nv-l] xnmsnmpconf and Topology/Status Polling intervals and other related questions..



Regarding xnmsnmpconf repopulation: you can export the data in that database any time and reload it. See the man page. There are some new options in 7.1.4. FP3. If you lose the data and don't have a backup, switch netmon to use the alternates 'every time' and force a config poll, and it will repopulate it quickly with the community strings, but it will not appy any custom entries you might have made in the other fields. If you want to use the default entries for those other fields anyway, it is not necessary to enter them. There is a lot if information in the man page for ovsnmp.conf.'  Note that if you want to import saved data, the names must all still resolve. Things that have been removed from the network and from DNS but remain in this database will cause problems on reloading, and you will have to edit it to remove them.

Polling for configuration changes should not be a major load. Most people do it reqularly. It tries to spread the work out over time to reduce network impact, but you can trick it into running at a certain time. If you stop netmon and do an ovtopofix -a, all nodes are flagged as being due for a config check. When you start up netmon, it will do the config poll. So set the config poll period in xnmsnmpconf to something longer than the period you have in mind, and schedule the housekeeping in cron or Tivoli.  On Windows, the config poll is schedulable.

I like the ospf area approach to mapping and have used it in the past, because the information you need to construct the location.conf is available programmatically using snmpget, or the mibtable command.

This mib table gives the ospf area information: .1.3.6.1.2.1.14.7.1

This mib table gives the ospf neighbor information:
.1.3.6.1.2.1.14.10.1

Cordially,

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


"John Sobrinho" <john_sobrinho@sympatico.ca>
Sent by: owner-nv-l@lists.us.ibm.com

06/29/2005 10:13 PM
Please respond to
nv-l


To
<nv-l@lists.us.ibm.com>
cc
Subject
[nv-l] xnmsnmpconf and Topology/Status Polling intervals and other related questions..










Hello All..

I know there is a ton of info on xnmsnmpconf posts, but I'd like to find out
if there is away to auto populate / auto manage this as netview netmon
discovers devices. There must be some automation somewhere as one time I
accidentally nuked 800 or so entries, so I deleted the whole thing.  I am
not sure if reloading netmon repopulated this field or running ovtopofix,
mapdelete, or what I did, but a few days later voila a good portion of the
data came back but the polling fields were filled automatically filled
ith  -  -  -  -  "blanks" for timeout retry Port and Polling interval. Does
anyone know how this is populated automatically so I can delete and refresh
at will ?  which will lead in to my second question what would be the
defaults in this scenario if all fields are set to  - - - and can this be
pre-determined as what ever triggers the auto population  behavior? . (I
should mention we are alternatecommunitynames.conf)

I also would like to know what kind of additional load could I expect on my
server if we were to enable Poll for Configuration Changes. I finally have
requirement to develop topology maps. I most likely will not create submaps
but split the main map and use locations.conf to split the default map. I
was thinking of using OSPF areas instead of geographical areas.. any advice
on one vs. the other ?

I read some documentation somewhere that Polling for Configuration changes
occur once a day, but could not find when it occurs or how to tell netmon to
get config info does anyone know where this info lives ? If we can time
control this to be off peek production times and days that would be
beneficial.

More generically our ultimate goal would be to do  mapping  with mimimal
user intervention, as there is so much change in our environment and I would
like make netview as dynamic as possible. Knowing of I need to understand
some the fundamental basics. I have a good grasp of discovery and seed
file., now the art of mapping 2500 + devices.

I'll be looking forward to your feedback..

Regards,
John



<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web