On 03/22/2011 04:16 AM, Morten Brekkevold wrote:
On Mon, 21 Mar 2011 10:40:53 +0700 Roykeroyke4k@cbn.net.id wrote:
Correction, the connection view in netmap is established now. But I think I found a bugs (or is it a feature ?). My Prefix definition is dissapear , but my Vlan seems automagically filled with lot of Nettypes definition namely : core, elink, vlan. I think it is a normal behaviour, is it or not ?
I'm not sure what you're referring to here? What prefix definition has disappeared?
I refering to link in (http://metanav.int.cbn.net.id/seeddb/prefix/). I already fill the prefix with the subnet of the point-to-point link between routers and switches of the network. Then change the description of the interface. And suddenly the prefix dissapear. I guess the autodetected vlan prefix superseed the prefix I already fill in the prefix tab and filling the vlan (http://metanav.int.cbn.net.id/seeddb/vlan/) with the network type aforementioned.
NAV autodetects your prefixes from your routers. The only prefixes you'll need to add yourself are "scope" and "reserved" prefixes.
A "scope" prefix is an indication of what network address would encompass your entire network (though you may add multiple scopes if your delegated network block addresses vary wildly). The scope prefix is only used for things such as the graphical network scope report, which shows you your subnet allocations and utilization.
A "reserved" prefix is a prefix you do not route, or which is routed by something you aren't monitoring with your NAV. They can be added just to designate them as such in the scope report mentioned above.
As for the prefixes/vlans autodiscovered by NAV, NAV will try to classify each as either "link", "elink", "core" or "lan".
I believe all these are described adequately at the Wiki page you already referred to, http://metanav.uninett.no/subnetsandvlans#network_types .
Yes , it explained a lot.
Also I found many error from ipdevpoll.log like below (cannot paste all but I paste the most important parts I think) :
File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 243, in callback self._startRunCallbacks(result) File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 312, in _startRunCallbacks self._runCallbacks() ---<exception caught here> --- File "/usr/lib/python2.6/dist-packages/twisted/internet/defer.py", line 328, in _runCallbacks self.result = callback(self.result, *args, **kw) File "/usr/local/nav/lib/python/nav/ipdevpoll/schedule.py", line 236, in reset self.netbox_reload_loop.call.reset(1) exceptions.AttributeError: 'NoneType' object has no attribute 'reset'
Looks like a bug in the handling of devices that have been physically replaced. The rest of your errors may be caused by the same problem, since this seems to create some scheduling problem for the duration of the ipdevpoll process.
If you would report these error messages at https://bugs.launchpad.net/nav/+filebug I would be gratefaul :)
I will post this at launchpad bugzilla.
Thks. Regards Royke