To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] detail information |
From: | Leslie Clark <lclark@us.ibm.com> |
Date: | Tue, 20 Jan 2004 21:56:37 -0500 |
Delivery-date: | Wed, 21 Jan 2004 03:23:17 +0000 |
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 |
Well, Chris, I suspect that certain details about how discovery is actually done would be considered proprietary. Not to make anybody mad, but because it is a differentiating feature among products in this field. How to USE the discovery capability is another matter. That is covered in the Admin Guide. More is available in the man pages for the daemons. Beyond that, asking specific questions in this forum as they come to you is a good way to go, I think. People here are pretty helpful if you have poked around a bit and can ask a clear question. The archives of this listserver are also very helpful. http://lists.skills-1st.co.uk/mharc/html/nv-l/ I'll take a stab at a couple of the items you listed. Which interface is a router found by? It is found by the closest one to the netview server, unless you force its discovery by a particular interface by specifying it in the seedfile. Then the labeling of the device depends on name resolution provided by the operating system. Assigning your wan routers to location submaps: First try a manual arrangement and see what is useful for you. You can manually create the location icons for a couple of your remote sites right there on the IP Internet level submap. Cut (from THIS submap) the remote routers and paste it into the location submap. See how it looks. If the network between them is serial, it will probably be drawn as a straight line, no bubble. Include subnets for the far side of the remote router in the remote location submap. You might end up with you two core routers loose on the top map, and a dozen or so remote location icons, each containing a remote router and a few subnets. Once you get the hang of it, then go back to the location.conf file and codify it. To see how to specify the networks, look at one on the map with 'Tools....Display Object Info' and look at its Network Address. Specifying that 4-octet thing would place that exact network. Cordially, Leslie A. Clark IBM Global Services - Systems Mgmt & Networking Detroit
Hi All, Looking to find out where I can get detailed information about things like AutoDiscovery, mpaings of devices, how new devices are discovered via SNMP. Autodiscovery: information on how it performs autodiscovery on a router, such as when a new router is added to the seedfile, does it first do a traceroute to get to the device, and if this device is a WAN device does it use the serial interface out of the LAN over the WAN to the device as the primary object Identification for that device. Does ituse arp table lookups to find the device? Things of that detail Also more indepth about location.conf, such as I have two routers which serve as the WAN entry points. each router has a set of subnets for each site attached to it. the serial interface on the near side and the serial interface on the far side. in a location.conf file how would I dictate where to put the subnet(network). I know that gateways belong outside the sub containers. I have looked through all the redbooks and the release notes, admin guides, user guides but there is not much int he way of intense detail about these things? Thanks for the Help Chris Petrina |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | [nv-l] [nv 7.1.4] Suppressing duplicate clogMessageGenerated traps prior to reaching TEC, Van Order, Drew \(US - Hermitage\) |
---|---|
Next by Date: | [nv-l] xnmappmon & ovwinit, Laurie . Gellatly |
Previous by Thread: | Re: [nv-l] detail information, Jane Curry |
Next by Thread: | [nv-l] [nv 7.1.4] Suppressing duplicate clogMessageGenerated traps prior to reaching TEC, Van Order, Drew \(US - Hermitage\) |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web