Hello nav-users
I'm just starting to use NAV. After browsing a little throug the documentation I have a few questions that maybe some ou you guys can answer:
- NAV looks a complex system with lot of automation going on behind the scenes. How do I find out if all this automation (started fron CRON I assume) is running well? Is there some error log somewhere?
- How do I list the forwarding database of an ethernet switch?
thanks João Pagaime
On Wed, Apr 14, 2010 at 09:32:33AM +0100, João Pagaime wrote:
I'm just starting to use NAV. After browsing a little throug the documentation I have a few questions that maybe some ou you guys can answer:
- NAV looks a complex system with lot of automation going on behind
the scenes. How do I find out if all this automation (started fron CRON I assume) is running well? Is there some error log somewhere?
Some of NAV's backend processes are daemon programs, while some are plain cron jobs. Each of these processes are controlled from the shell using the "nav start/stop" set of commands.
Each of these processes logs to its own file, found in the log directory. The default location of the logs are in /usr/local/nav/var/log, but if you installed NAV using a Debian package, you will find them in /var/log/nav .
- How do I list the forwarding database of an ethernet switch?
I'm assuming you are talking about listing this from NAV's user interface. You won't get a complete listing of a switch's forwarding database - NAV logs forwarding entries (CAM data) for access ports only. You can go to the Machine Tracker tool (found in the toolbox) and choose to do a switch search. Enter the switch's sysname and all records from the past 7 days will be shown.
Hello all
I have a few 3Com 4500G/V5.01.03s56 that don't appear connected on the "netmap" (NAV 3.5.6), although we know they're connected to other switches that do appear on netmap
Is there any way I can make those 3com appear connected on netmap?
Another question: is there any way to detect switch candidates analysing NAV's database? I'm trying to configure all switches into NAV, but there are many and the lists I have may be incomplete. Another reason to do this analysis regularly might be to detect "rogue" switches connected onto the network
best regards, thanks, João Pagaime
Another question: is there any way to detect switch candidates analysing NAV's database? I'm trying to configure all switches into NAV, but there are many and the lists I have may be incomplete. Another reason to do this analysis regularly might be to detect "rogue" switches connected onto the network
You can find (CDP enabled) switches (and phones...) not added to NAV by looking at the predefined "Unrecognized CDP neighbours" under Reports :-)
Good luck!
Best regards,
Vidar S
Stokkenes Vidar wrote:
Another question: is there any way to detect switch candidates analysing NAV's database? I'm trying to configure all switches into NAV, but there are many and the lists I have may be incomplete. Another reason to do this analysis regularly might be to detect "rogue" switches connected onto the network
You can find (CDP enabled) switches (and phones...) not added to NAV by looking at the predefined "Unrecognized CDP neighbours" under Reports :-)
Yes and somewhere down the road (say NAV 3.7) we should get LLDP [1] support and then all LLDP capable neighbours can be detected as well. That should help even more :) Does 3com support LLDP?
regards, - Vidar F
[1] Link Layer Discovery Protocol
the new ones seem to:
------- http://www.3com.com/other/pdfs/products/en_US/400952_1003.pdf 3COM SWITCH 4500 10/100 FAMILY .... Link Layer Discovery Protocol (LLDP / LLDP-MED) --------------
I guess a hint that some port is more than an ordinary port, would be the fact that it has more than one mac-address assigned on the forwarding database to that port. That of course wouldn't say much as to what is on the other side of the cable
--jp
Em 23-04-2010 14:40, Vidar Faltinsen escreveu:
Stokkenes Vidar wrote:
Another question: is there any way to detect switch candidates analysing NAV's database? I'm trying to configure all switches into NAV, but there are many and the lists I have may be incomplete. Another reason to do this analysis regularly might be to detect "rogue" switches connected onto the network
You can find (CDP enabled) switches (and phones...) not added to NAV by looking at the predefined "Unrecognized CDP neighbours" under Reports :-)
Yes and somewhere down the road (say NAV 3.7) we should get LLDP [1] support and then all LLDP capable neighbours can be detected as well. That should help even more :) Does 3com support LLDP?
regards,
- Vidar F
[1] Link Layer Discovery Protocol
-
João Pagaime -
Morten Brekkevold -
Stokkenes Vidar -
Vidar Faltinsen