On Thu, 22 Mar 2012 12:45:46 +0000 Rene Romijn r.romijn@deli-ict.nl wrote:
Hi,
Maybe a stupid question, but we have several type of switches/routers in our network, nav does a good job with recognizing the hp and cisco ports. But we also have some Gbe2c switches, they are sold by hp but the original is from another branche (wich I forgot). Nav does see the type of switch but it doesn't see the individual switch ports. I would realy like to see that nav/cricket also keeps track of those switchports.
I have no experience with Gbe2c switches, but recognition of switch ports requires proper support for BRIDGE-MIB (RFC 4188, or at the very least RFC 1493).
Specifically, a switch with proper support will list all its interfaces operating in bridging/switching mode in the BRIDGE-MIB::dot1dBasePortTable. If you have the NetSNMP command line programs installed and this MIB loaded, you can query a switch to see the list of switch ports like so:
snmpwalk -v2c -c <community> <switch ip> dot1dBasePortIfIndex
(If you don't have the MIB loaded, or don't know how, use .1.3.6.1.2.1.17.1.4.1.2 instead of dot1dBasePortIfIndex)
We have recently had a case with complaints that NAV didn't find switch ports on some Cisco Nexus L3 switches; what we found was the ports on these switched needed to be explicitly configured to operate as switch ports (which was not the default).
If you check with the web report at /report/interfaces, did NAV collect any interfaces at all for your Gbe2c switches?