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.
Kind regards,
Rene.
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?
In the /report/interfaces it does show up with the interfaces, also with the right names. But in the /report/netbox detail list, it doesn't show the interfaces as switchports, wich probably the reason why cricket doesn't graph the ports.
On Fri, 23 Mar 2012 08:13:32 +0000 Rene Romijn r.romijn@deli-ict.nl wrote:
In the /report/interfaces it does show up with the interfaces, also with the right names. But in the /report/netbox detail list, it doesn't show the interfaces as switchports, wich probably the reason why cricket doesn't graph the ports.
Correct, cricket will only be configured to get data from what NAV recognizes as either switching or routing interfaces.
Follow the BRIDGE-MIB lead and tell us what you find.
In the /report/interfaces it does show up with the interfaces, also with the right names. But in the /report/netbox detail list, it doesn't show the interfaces as switchports, wich probably the reason why cricket doesn't graph the ports.
Correct, cricket will only be configured to get data from what NAV recognizes as either switching or routing interfaces.
Follow the BRIDGE-MIB lead and tell us what you find.
-- Morten Brekkevold UNINETT
The snmpwalk gives me the following output:
snmpwalk -v2c -c public 172.17.205.17 .1.3.6.1.2.1.17.1.4.1.2 iso.3.6.1.2.1.17.1.4.1.2.1 = INTEGER: 257 iso.3.6.1.2.1.17.1.4.1.2.2 = INTEGER: 258 iso.3.6.1.2.1.17.1.4.1.2.3 = INTEGER: 259 iso.3.6.1.2.1.17.1.4.1.2.4 = INTEGER: 260 iso.3.6.1.2.1.17.1.4.1.2.5 = INTEGER: 261 iso.3.6.1.2.1.17.1.4.1.2.6 = INTEGER: 262 iso.3.6.1.2.1.17.1.4.1.2.7 = INTEGER: 263 iso.3.6.1.2.1.17.1.4.1.2.8 = INTEGER: 264 iso.3.6.1.2.1.17.1.4.1.2.9 = INTEGER: 265 iso.3.6.1.2.1.17.1.4.1.2.10 = INTEGER: 266 iso.3.6.1.2.1.17.1.4.1.2.11 = INTEGER: 267 iso.3.6.1.2.1.17.1.4.1.2.12 = INTEGER: 268 iso.3.6.1.2.1.17.1.4.1.2.13 = INTEGER: 269 iso.3.6.1.2.1.17.1.4.1.2.14 = INTEGER: 270 iso.3.6.1.2.1.17.1.4.1.2.15 = INTEGER: 271 iso.3.6.1.2.1.17.1.4.1.2.16 = INTEGER: 272 iso.3.6.1.2.1.17.1.4.1.2.17 = INTEGER: 273 iso.3.6.1.2.1.17.1.4.1.2.18 = INTEGER: 274 iso.3.6.1.2.1.17.1.4.1.2.19 = INTEGER: 275 iso.3.6.1.2.1.17.1.4.1.2.20 = INTEGER: 276 iso.3.6.1.2.1.17.1.4.1.2.21 = INTEGER: 277 iso.3.6.1.2.1.17.1.4.1.2.22 = INTEGER: 278 iso.3.6.1.2.1.17.1.4.1.2.23 = INTEGER: 279 iso.3.6.1.2.1.17.1.4.1.2.24 = INTEGER: 280
On Fri, 23 Mar 2012 08:20:51 +0000 Rene Romijn r.romijn@deli-ict.nl wrote:
Follow the BRIDGE-MIB lead and tell us what you find.
The snmpwalk gives me the following output:
snmpwalk -v2c -c public 172.17.205.17 .1.3.6.1.2.1.17.1.4.1.2 iso.3.6.1.2.1.17.1.4.1.2.1 = INTEGER: 257 iso.3.6.1.2.1.17.1.4.1.2.2 = INTEGER: 258 iso.3.6.1.2.1.17.1.4.1.2.3 = INTEGER: 259 iso.3.6.1.2.1.17.1.4.1.2.4 = INTEGER: 260 iso.3.6.1.2.1.17.1.4.1.2.5 = INTEGER: 261 iso.3.6.1.2.1.17.1.4.1.2.6 = INTEGER: 262 iso.3.6.1.2.1.17.1.4.1.2.7 = INTEGER: 263 iso.3.6.1.2.1.17.1.4.1.2.8 = INTEGER: 264 iso.3.6.1.2.1.17.1.4.1.2.9 = INTEGER: 265 iso.3.6.1.2.1.17.1.4.1.2.10 = INTEGER: 266 iso.3.6.1.2.1.17.1.4.1.2.11 = INTEGER: 267 iso.3.6.1.2.1.17.1.4.1.2.12 = INTEGER: 268 iso.3.6.1.2.1.17.1.4.1.2.13 = INTEGER: 269 iso.3.6.1.2.1.17.1.4.1.2.14 = INTEGER: 270 iso.3.6.1.2.1.17.1.4.1.2.15 = INTEGER: 271 iso.3.6.1.2.1.17.1.4.1.2.16 = INTEGER: 272 iso.3.6.1.2.1.17.1.4.1.2.17 = INTEGER: 273 iso.3.6.1.2.1.17.1.4.1.2.18 = INTEGER: 274 iso.3.6.1.2.1.17.1.4.1.2.19 = INTEGER: 275 iso.3.6.1.2.1.17.1.4.1.2.20 = INTEGER: 276 iso.3.6.1.2.1.17.1.4.1.2.21 = INTEGER: 277 iso.3.6.1.2.1.17.1.4.1.2.22 = INTEGER: 278 iso.3.6.1.2.1.17.1.4.1.2.23 = INTEGER: 279 iso.3.6.1.2.1.17.1.4.1.2.24 = INTEGER: 280
Then the interfaces with ifindexes from 257 through 280 should be recognized as switch ports by NAV (the ifindex numbers should be available in the interfaces report from before).
If this isn't the case, you should check to see if ipdevpoll.log contains any errors related to this switch (and when viewing the ipdevinfo page for the switch, what does it say is the "last updated" time?).
Then the interfaces with ifindexes from 257 through 280 should be recognized as switch ports by NAV (the ifindex numbers should be available in the interfaces report from >before).
If this isn't the case, you should check to see if ipdevpoll.log contains any errors related to this switch (and when viewing the ipdevinfo page for the switch, what does it say is the >"last updated" time?).
-- Morten Brekkevold UNINETT
Those interfaces are so called uplink interfaces to connect the switch to the network, still those interfaces doesn't show up as switch ports.
I checked the ipdevpoll.log, but besides a warning about DNS it doesn't give any error:
cat ipdevpoll.log |grep '172.17.205.17' 2012-03-22 10:54:16,555 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.17] DNS lookup error for 172.17.205.17: DNSNameError 2012-03-22 10:54:16,555 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.17] Unable to find PTR record for 172.17.205.17 (17.205.17.172.in-addr.arpa.) 2012-03-22 10:54:16,601 [WARNING plugins.typeoid.typeoid] [inventory 172.17.205.17] Netbox has changed type from unknown to unknown (sysObjectID 1.3.6.1.4.1.11.2.3.7.11.33.4.1.1) 2012-03-22 11:04:16,457 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.17] DNS lookup error for 172.17.205.17: DNSNameError 2012-03-22 11:04:16,457 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.17] Unable to find PTR record for 172.17.205.17 (17.205.17.172.in-addr.arpa.) 2012-03-22 17:04:16,666 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.17] DNS lookup error for 172.17.205.17: DNSNameError 2012-03-22 17:04:16,666 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.17] Unable to find PTR record for 172.17.205.17 (17.205.17.172.in-addr.arpa.) 2012-03-22 17:59:36,310 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.17] DNS lookup error for 172.17.205.17: DNSNameError 2012-03-22 17:59:36,311 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.17] Unable to find PTR record for 172.17.205.17 (17.205.17.172.in-addr.arpa.) 2012-03-22 23:59:34,170 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.17] DNS lookup error for 172.17.205.17: DNSNameError 2012-03-22 23:59:34,170 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.17] Unable to find PTR record for 172.17.205.17 (17.205.17.172.in-addr.arpa.) 2012-03-23 05:59:36,293 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.17] DNS lookup error for 172.17.205.17: DNSNameError 2012-03-23 05:59:36,293 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.17] Unable to find PTR record for 172.17.205.17 (17.205.17.172.in-addr.arpa.)
I have added 2 screenshots how it shows up in nav:
On Fri, 23 Mar 2012 08:47:30 +0000 Rene Romijn r.romijn@deli-ict.nl wrote:
Those interfaces are so called uplink interfaces to connect the switch to the network, still those interfaces doesn't show up as switch ports.
Well, according to BRIDGE-MIB they should, so something is obviously not working.
If you could enable debug logging for the bridge plugin and see what it reports, that would be interesting.
Create the file "logging.conf" in the same directory as the rest of your NAV config files (not the same as the logger.conf file). Add the following three lines:
[levels] nav.ipdevpoll = INFO nav.ipdevpoll.plugins.bridge = DEBUG
Restart NAV and tail/grep ipdevpoll.log again, let's see what comes out.
Create the file "logging.conf" in the same directory as the rest of your NAV config files (not the same as the logger.conf file). Add the following three lines:
[levels] nav.ipdevpoll = INFO .nav.ipdevpoll.plugins.bridge = DEBUG
Restart NAV and tail/grep ipdevpoll.log again, let's see what comes out.
-- Morten Brekkevold UNINETT
Ok, i have done what you have asked and i added another Gbe2c to see how it will be populated. It does give some errors now:
2012-03-23 11:05:40,994 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.18] DNS lookup error for 172.17.205.18: DNSNameError 2012-03-23 11:05:41,023 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.18] Unable to find PTR record for 172.17.205.18 (18.205.17.172.in-addr.arpa.) 2012-03-23 11:05:41,033 [INFO schedule.netboxjobscheduler] [snmpcheck 172.17.205.18] completed in 0:00:00.236147. next run in 0:29:59.763909. 2012-03-23 11:05:41,166 [INFO schedule.netboxjobscheduler] [linkcheck 172.17.205.18] completed in 0:00:00.357684. next run in 0:04:59.642371. 2012-03-23 11:05:43,255 [INFO plugins.oidprofiler.oidprofiler] [profiling 172.17.205.18] profile update: add 46 / del 0 2012-03-23 11:05:43,266 [ERROR jobs.jobhandler] [profiling 172.17.205.18] Caught exception during save. Last manager = DefaultManager(<class 'nav.ipdevpoll.shadows.NetboxSnmpOid'>, 'ContainerRepository'(...)). Last model = <class 'nav.ipdevpoll.shadows.NetboxSnmpOid'> 2012-03-23 11:05:43,269 [ERROR jobs.jobhandler] [profiling 172.17.205.18] Save stage failed with unhandled error 2012-03-23 11:05:43,271 [ERROR jobs.jobhandler] [profiling 172.17.205.18] Job 'profiling' for 172.17.205.18 aborted: null value in column "snmpoidid" violates not-null constraint 2012-03-23 11:05:43,272 [INFO schedule.netboxjobscheduler] [profiling 172.17.205.18] failed in 0:00:02.448178. next run in 0:08:41.999977.
On Fri, 23 Mar 2012 10:09:36 +0000 Rene Romijn r.romijn@deli-ict.nl wrote:
Create the file "logging.conf" in the same directory as the rest of your NAV config files (not the same as the logger.conf file). Add the following three lines:
[levels] nav.ipdevpoll = INFO .nav.ipdevpoll.plugins.bridge = DEBUG
I didn't write a leading dot in front of nav.ipdevpoll.plugins.bridge in my original message, I hope you didn't do that in logging.conf either...
Ok, i have done what you have asked and i added another Gbe2c to see how it will be populated. It does give some errors now:
I see the profiling job fails, that's interesting in itself, but unrelated to the issue at hand.
The bridge plugin doesn't report any findings of switch ports, which is strange. I want to add some more debugging to see if the bridge plugin is ever run (it runs in the inventory job, so the log messages marked as inventory are the interesting ones here).
Please add these three options to logging.conf and try again:
nav.ipdevpoll.jobs.jobhandler = DEBUG nav.ipdevpoll.jobs.jobhandler.timings = INFO nav.ipdevpoll.jobs.jobhandler.queue = INFO
I didn't write a leading dot in front of nav.ipdevpoll.plugins.bridge in my original message, I hope you didn't do that in logging.conf either...
The dot was accidently added the reply, not in the logging.conf ;-)
Ok, i have done what you have asked and i added another Gbe2c to see how it will be populated. It does give some errors now:
I see the profiling job fails, that's interesting in itself, but unrelated to the issue at hand.
The bridge plugin doesn't report any findings of switch ports, which is strange. I want to add some more debugging to see if the bridge plugin is ever run (it runs in the inventory >job, so the log messages marked as inventory are the interesting ones here).
Please add these three options to logging.conf and try again:
nav.ipdevpoll.jobs.jobhandler = DEBUG nav.ipdevpoll.jobs.jobhandler.timings = INFO nav.ipdevpoll.jobs.jobhandler.queue = INFO
Allright, this is the content of the loggings.conf at this moment:
[levels] nav.ipdevpoll = INFO nav.ipdevpoll.plugins.bridge = DEBUG nav.ipdevpoll.jobs.jobhandler = DEBUG nav.ipdevpoll.jobs.jobhandler.timings = INFO nav.ipdevpoll.jobs.jobhandler.queue = INFO
I added another GbE2c (I have some... ;-) ), to see how it does reflect in the loggings:
2012-03-23 11:42:15,756 [DEBUG jobs.jobhandler] [topo 172.17.205.19] Job 'topo' initialized with plugins: ['cam', 'lldp', 'cdp'] 2012-03-23 11:42:15,759 [DEBUG jobs.jobhandler] [topo 172.17.205.19] AgentProxy created for 172.17.205.19: <nav.ipdevpoll.snmp.pynetsnmp.AgentProxy object at 0xb37c35cc> 2012-03-23 11:42:15,781 [DEBUG jobs.jobhandler] [snmpcheck 172.17.205.19] Job 'snmpcheck' initialized with plugins: ['snmpcheck'] 2012-03-23 11:42:15,783 [DEBUG jobs.jobhandler] [snmpcheck 172.17.205.19] AgentProxy created for 172.17.205.19: <nav.ipdevpoll.snmp.pynetsnmp.AgentProxy object at 0xb8cf86c> 2012-03-23 11:42:15,783 [DEBUG jobs.jobhandler] [snmpcheck 172.17.205.19] Plugins to call: SnmpCheck 2012-03-23 11:42:15,784 [DEBUG jobs.jobhandler] [snmpcheck 172.17.205.19] Starting job 'snmpcheck' for 172.17.205.19 2012-03-23 11:42:15,784 [DEBUG jobs.jobhandler] [snmpcheck 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.snmpcheck.SnmpCheck(u'172.17.205.19') 2012-03-23 11:42:15,805 [DEBUG jobs.jobhandler] [linkcheck 172.17.205.19] Job 'linkcheck' initialized with plugins: ['linkstate'] 2012-03-23 11:42:15,807 [DEBUG jobs.jobhandler] [linkcheck 172.17.205.19] AgentProxy created for 172.17.205.19: <nav.ipdevpoll.snmp.pynetsnmp.AgentProxy object at 0xaec07ec> 2012-03-23 11:42:15,816 [DEBUG jobs.jobhandler] [linkcheck 172.17.205.19] Plugins to call: LinkState 2012-03-23 11:42:15,816 [DEBUG jobs.jobhandler] [linkcheck 172.17.205.19] Starting job 'linkcheck' for 172.17.205.19 2012-03-23 11:42:15,816 [DEBUG jobs.jobhandler] [linkcheck 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.linkstate.LinkState(u'172.17.205.19') 2012-03-23 11:42:15,831 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Job 'inventory' initialized with plugins: ['dnsname', 'typeoid', 'system', 'modules', 'ciscosup', 'bridge', 'interfaces', 'dot1q', 'ciscovlan', 'extremevlan', 'prefix', 'sensors', 'psu', 'lastupdated'] 2012-03-23 11:42:15,833 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] AgentProxy created for 172.17.205.19: <nav.ipdevpoll.snmp.pynetsnmp.AgentProxy object at 0xaec084c> 2012-03-23 11:42:15,868 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Plugin ciscosup wouldn't handle 172.17.205.19 2012-03-23 11:42:15,974 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Plugins to call: DnsName,TypeOid,System,Modules,Bridge,Interfaces,Dot1q,CiscoVlan,ExtremeVlan,Prefix,Sensors,PowerSupplyUnit,LastUpdated 2012-03-23 11:42:15,974 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Starting job 'inventory' for 172.17.205.19 2012-03-23 11:42:15,975 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.dnsname.DnsName(u'172.17.205.19') 2012-03-23 11:42:15,979 [DEBUG jobs.jobhandler] [profiling 172.17.205.19] Job 'profiling' initialized with plugins: ['oidprofiler'] 2012-03-23 11:42:15,981 [DEBUG jobs.jobhandler] [profiling 172.17.205.19] AgentProxy created for 172.17.205.19: <nav.ipdevpoll.snmp.pynetsnmp.AgentProxy object at 0xb8bd24c> 2012-03-23 11:42:15,987 [DEBUG jobs.jobhandler] [profiling 172.17.205.19] Plugins to call: OidProfiler 2012-03-23 11:42:15,987 [DEBUG jobs.jobhandler] [profiling 172.17.205.19] Starting job 'profiling' for 172.17.205.19 2012-03-23 11:42:15,987 [DEBUG jobs.jobhandler] [profiling 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.oidprofiler.OidProfiler(u'172.17.205.19') 2012-03-23 11:42:16,016 [DEBUG jobs.jobhandler] [logging 172.17.205.19] Job 'logging' initialized with plugins: ['arp'] 2012-03-23 11:42:16,017 [DEBUG jobs.jobhandler] [logging 172.17.205.19] AgentProxy created for 172.17.205.19: <nav.ipdevpoll.snmp.pynetsnmp.AgentProxy object at 0xb8c666c> 2012-03-23 11:42:16,017 [DEBUG jobs.jobhandler] [logging 172.17.205.19] Plugin arp wouldn't handle 172.17.205.19 2012-03-23 11:42:16,017 [DEBUG jobs.jobhandler] [logging 172.17.205.19] No plugins for this job 2012-03-23 11:42:16,074 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.19] DNS lookup error for 172.17.205.19: DNSNameError 2012-03-23 11:42:16,074 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.19] Unable to find PTR record for 172.17.205.19 (19.205.17.172.in-addr.arpa.) 2012-03-23 11:42:16,074 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.typeoid.TypeOid(u'172.17.205.19') 2012-03-23 11:42:16,597 [DEBUG jobs.jobhandler] [topo 172.17.205.19] Plugin cam wouldn't handle 172.17.205.19 2012-03-23 11:42:17,187 [DEBUG jobs.jobhandler] [snmpcheck 172.17.205.19] Storing to database complete (11.158 ms) 2012-03-23 11:42:17,884 [DEBUG jobs.jobhandler] [topo 172.17.205.19] Plugin lldp wouldn't handle 172.17.205.19 2012-03-23 11:42:17,897 [DEBUG jobs.jobhandler] [snmpcheck 172.17.205.19] Job snmpcheck for 172.17.205.19 done. 2012-03-23 11:42:17,901 [INFO schedule.netboxjobscheduler] [snmpcheck 172.17.205.19] completed in 0:00:02.119964. next run in 0:29:57.880076. 2012-03-23 11:42:18,848 [DEBUG jobs.jobhandler] [topo 172.17.205.19] Plugin cdp wouldn't handle 172.17.205.19 2012-03-23 11:42:18,848 [DEBUG jobs.jobhandler] [topo 172.17.205.19] No plugins for this job 2012-03-23 11:42:18,855 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.system.System(u'172.17.205.19') 2012-03-23 11:42:19,461 [DEBUG jobs.jobhandler] [linkcheck 172.17.205.19] Storing to database complete (217.207 ms) 2012-03-23 11:42:19,677 [DEBUG jobs.jobhandler] [linkcheck 172.17.205.19] Job linkcheck for 172.17.205.19 done. 2012-03-23 11:42:19,682 [INFO schedule.netboxjobscheduler] [linkcheck 172.17.205.19] completed in 0:00:03.876638. next run in 0:04:56.123420. 2012-03-23 11:42:20,542 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.modules.Modules(u'172.17.205.19') 2012-03-23 11:42:23,376 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.bridge.Bridge(u'172.17.205.19') 2012-03-23 11:43:17,743 [INFO plugins.oidprofiler.oidprofiler] [profiling 172.17.205.19] profile update: add 46 / del 0 2012-03-23 11:43:17,776 [ERROR jobs.jobhandler] [profiling 172.17.205.19] Caught exception during save. Last manager = DefaultManager(<class 'nav.ipdevpoll.shadows.NetboxSnmpOid'>, 'ContainerRepository'(...)). Last model = <class 'nav.ipdevpoll.shadows.NetboxSnmpOid'> 2012-03-23 11:43:17,788 [INFO schedule.netboxjobscheduler] [profiling 172.17.205.19] failed in 0:01:01.808774. next run in 0:09:56.999967. 2012-03-23 11:43:17,802 [ERROR schedule.netboxjobscheduler] [profiling 172.17.205.19] Unhandled exception raised by JobHandler
On Fri, 23 Mar 2012 10:46:33 +0000 Rene Romijn r.romijn@deli-ict.nl wrote:
I added another GbE2c (I have some... ;-) ), to see how it does reflect in the loggings:
Sure, have at it, but we only need to observe the logs for at least one of the problematic ones :)
2012-03-23 11:42:15,831 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Job 'inventory' initialized with plugins: ['dnsname', 'typeoid', 'system', 'modules', 'ciscosup', 'bridge', 'interfaces', 'dot1q', 'ciscovlan', 'extremevlan', 'prefix', 'sensors', 'psu', 'lastupdated']
[...]
2012-03-23 11:42:23,376 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.bridge.Bridge(u'172.17.205.19')
Well, the bridge plugin is apparently running, though it seems you cut the log short, so I can't be sure what comes next. It would be better if you grepped the log for "inventory 172.17.205.19" and made sure to include everything up to the point where it says the inventory job was finished for 172.17.205.19.
Well, the bridge plugin is apparently running, though it seems you cut the log short, so I can't be sure what comes next. It would be better if you grepped the log for "inventory >172.17.205.19" and made sure to include everything up to the point where it says the inventory job was finished for 172.17.205.19.
Ok, last log was "Job inventory for 172.17.205.19 done."
cat ipdevpoll.log |grep 'inventory 172.17.205.19'
2012-03-23 11:42:15,831 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Job 'inventory' initialized with plugins: ['dnsname', 'typeoid', 'system', 'modules', 'ciscosup', 'bridge', 'interfaces', 'dot1q', 'ciscovlan', 'extremevlan', 'prefix', 'sensors', 'psu', 'lastupdated'] 2012-03-23 11:42:15,833 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] AgentProxy created for 172.17.205.19: <nav.ipdevpoll.snmp.pynetsnmp.AgentProxy object at 0xaec084c> 2012-03-23 11:42:15,868 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Plugin ciscosup wouldn't handle 172.17.205.19 2012-03-23 11:42:15,974 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Plugins to call: DnsName,TypeOid,System,Modules,Bridge,Interfaces,Dot1q,CiscoVlan,ExtremeVlan,Prefix,Sensors,PowerSupplyUnit,LastUpdated 2012-03-23 11:42:15,974 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Starting job 'inventory' for 172.17.205.19 2012-03-23 11:42:15,975 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.dnsname.DnsName(u'172.17.205.19') 2012-03-23 11:42:16,074 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.19] DNS lookup error for 172.17.205.19: DNSNameError 2012-03-23 11:42:16,074 [WARNING plugins.dnsname.dnsname] [inventory 172.17.205.19] Unable to find PTR record for 172.17.205.19 (19.205.17.172.in-addr.arpa.) 2012-03-23 11:42:16,074 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.typeoid.TypeOid(u'172.17.205.19') 2012-03-23 11:42:18,855 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.system.System(u'172.17.205.19') 2012-03-23 11:42:20,542 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.modules.Modules(u'172.17.205.19') 2012-03-23 11:42:23,376 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.bridge.Bridge(u'172.17.205.19') 2012-03-23 11:52:00,441 [DEBUG plugins.bridge.bridge] [inventory 172.17.205.19] Found 0 base (switch) ports: {} 2012-03-23 11:52:00,441 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.interfaces.Interfaces(u'172.17.205.19') 2012-03-23 11:52:00,671 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.dot1q.Dot1q(u'172.17.205.19') 2012-03-23 11:52:00,689 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.ciscovlan.CiscoVlan(u'172.17.205.19') 2012-03-23 11:52:00,986 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.extremevlan.ExtremeVlan(u'172.17.205.19') 2012-03-23 11:52:00,991 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.prefix.Prefix(u'172.17.205.19') 2012-03-23 11:52:01,231 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.sensors.Sensors(u'172.17.205.19') 2012-03-23 11:52:01,545 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.psu.PowerSupplyUnit(u'172.17.205.19') 2012-03-23 11:52:01,573 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Now calling plugin: nav.ipdevpoll.plugins.lastupdated.LastUpdated(u'172.17.205.19') 2012-03-23 11:52:01,749 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Storing to database complete (160.313 ms) 2012-03-23 11:52:01,752 [DEBUG jobs.jobhandler] [inventory 172.17.205.19] Job inventory for 172.17.205.19 done.
On Fri, 23 Mar 2012 14:33:48 +0000 Rene Romijn r.romijn@deli-ict.nl wrote:
2012-03-23 11:52:00,441 [DEBUG plugins.bridge.bridge] [inventory 172.17.205.19] Found 0 base (switch) ports: {}
There it is. It says it found nothing. I'm beginning to suspect we've introduced a bug in the way this is handled for non-Cisco devices. Unfortunately, I won't have time to look at it properly until Monday.
It may be you can get some more info to confirm/disconfirm this in the meantime, by adding debug logging to even more parts of the code:
nav.mibs.entity_mib = DEBUG nav.mibs.bridge_mib = DEBUG
I will test a non-Cisco device myself when I get into work on Monday.
Have nice weekend!
On Fri, 23 Mar 2012 15:49:23 +0100 Morten Brekkevold morten.brekkevold@uninett.no wrote:
On Fri, 23 Mar 2012 14:33:48 +0000 Rene Romijn r.romijn@deli-ict.nl wrote:
2012-03-23 11:52:00,441 [DEBUG plugins.bridge.bridge] [inventory 172.17.205.19] Found 0 base (switch) ports: {}
There it is. It says it found nothing. I'm beginning to suspect we've introduced a bug in the way this is handled for non-Cisco devices. Unfortunately, I won't have time to look at it properly until Monday.
I forgot one important question: Which NAV version is this?
2012-03-23 11:52:00,441 [DEBUG plugins.bridge.bridge] [inventory 172.17.205.19] Found 0 base (switch) ports: {}
There it is. It says it found nothing. I'm beginning to suspect we've introduced a bug in the way this is handled for non-Cisco devices. Unfortunately, I won't have time to look at it properly until Monday.
No worries, its not that high priority ;-)
It may be you can get some more info to confirm/disconfirm this in the meantime, by adding debug logging to even more parts of the code:
nav.mibs.entity_mib = DEBUG nav.mibs.bridge_mib = DEBUG
I will add those options aswell.
I will test a non-Cisco device myself when I get into work on Monday.
Have nice weekend!
You too!
Kind regards,
Rene
On Fri, 23 Mar 2012 14:54:39 +0000 Rene Romijn r.romijn@deli-ict.nl wrote:
2012-03-23 11:52:00,441 [DEBUG plugins.bridge.bridge] [inventory 172.17.205.19] Found 0 base (switch) ports: {}
There it is. It says it found nothing. I'm beginning to suspect we've introduced a bug in the way this is handled for non-Cisco devices. Unfortunately, I won't have time to look at it properly until Monday.
No worries, its not that high priority ;-)
I finally had time to look at it, but I'm unable to confirm it with various non-Cisco switches we have.
If you issue a couple of more snmpwalk commands against the switch, one for .1.3.6.1.2.1.47.1.2.1.1.2 (ENTITY-MIB::entLogicalDescr) and one for .1.3.6.1.2.1.47.1.2.1.1.3 (ENTITY-MIB::entLogicalType), what do you get?
It may be you can get some more info to confirm/disconfirm this in the meantime, by adding debug logging to even more parts of the code:
nav.mibs.entity_mib = DEBUG nav.mibs.bridge_mib = DEBUG
I will add those options aswell.
I did too, but these don't appear to log the details I would need.
If you issue a couple of more snmpwalk commands against the switch, one for .1.3.6.1.2.1.47.1.2.1.1.2 (ENTITY-MIB::entLogicalDescr) and one for .1.3.6.1.2.1.47.1.2.1.1.3 (ENTITY-MIB::entLogicalType), what do you get?
For .1.3.6.1.2.1.47.1.2.1.1.2 I get:
iso.3.6.1.2.1.47.1.2.1.1.2.1 = STRING: "Spanning Tree Group 1" iso.3.6.1.2.1.47.1.2.1.1.2.2 = STRING: "Spanning Tree Group 2" iso.3.6.1.2.1.47.1.2.1.1.2.3 = STRING: "Spanning Tree Group 3" iso.3.6.1.2.1.47.1.2.1.1.2.4 = STRING: "Spanning Tree Group 4" iso.3.6.1.2.1.47.1.2.1.1.2.5 = STRING: "Spanning Tree Group 5" iso.3.6.1.2.1.47.1.2.1.1.2.6 = STRING: "Spanning Tree Group 6" iso.3.6.1.2.1.47.1.2.1.1.2.7 = STRING: "Spanning Tree Group 7" iso.3.6.1.2.1.47.1.2.1.1.2.8 = STRING: "Spanning Tree Group 8" iso.3.6.1.2.1.47.1.2.1.1.2.9 = STRING: "Spanning Tree Group 9" iso.3.6.1.2.1.47.1.2.1.1.2.10 = STRING: "Spanning Tree Group 10" iso.3.6.1.2.1.47.1.2.1.1.2.11 = STRING: "Spanning Tree Group 11" iso.3.6.1.2.1.47.1.2.1.1.2.12 = STRING: "Spanning Tree Group 12" iso.3.6.1.2.1.47.1.2.1.1.2.13 = STRING: "Spanning Tree Group 13" iso.3.6.1.2.1.47.1.2.1.1.2.14 = STRING: "Spanning Tree Group 14" iso.3.6.1.2.1.47.1.2.1.1.2.15 = STRING: "Spanning Tree Group 15" iso.3.6.1.2.1.47.1.2.1.1.2.16 = STRING: "Spanning Tree Group 16" iso.3.6.1.2.1.47.1.2.1.1.2.17 = STRING: "Spanning Tree Group 17" iso.3.6.1.2.1.47.1.2.1.1.2.18 = STRING: "Spanning Tree Group 18" iso.3.6.1.2.1.47.1.2.1.1.2.19 = STRING: "Spanning Tree Group 19" iso.3.6.1.2.1.47.1.2.1.1.2.20 = STRING: "Spanning Tree Group 20" iso.3.6.1.2.1.47.1.2.1.1.2.21 = STRING: "Spanning Tree Group 21" iso.3.6.1.2.1.47.1.2.1.1.2.22 = STRING: "Spanning Tree Group 22" iso.3.6.1.2.1.47.1.2.1.1.2.23 = STRING: "Spanning Tree Group 23" iso.3.6.1.2.1.47.1.2.1.1.2.24 = STRING: "Spanning Tree Group 24" iso.3.6.1.2.1.47.1.2.1.1.2.25 = STRING: "Spanning Tree Group 25" iso.3.6.1.2.1.47.1.2.1.1.2.26 = STRING: "Spanning Tree Group 26" iso.3.6.1.2.1.47.1.2.1.1.2.27 = STRING: "Spanning Tree Group 27" iso.3.6.1.2.1.47.1.2.1.1.2.28 = STRING: "Spanning Tree Group 28" iso.3.6.1.2.1.47.1.2.1.1.2.29 = STRING: "Spanning Tree Group 29" iso.3.6.1.2.1.47.1.2.1.1.2.30 = STRING: "Spanning Tree Group 30" iso.3.6.1.2.1.47.1.2.1.1.2.31 = STRING: "Spanning Tree Group 31" iso.3.6.1.2.1.47.1.2.1.1.2.32 = STRING: "Spanning Tree Group 32" iso.3.6.1.2.1.47.1.2.1.1.2.33 = STRING: "Spanning Tree Group 33" iso.3.6.1.2.1.47.1.2.1.1.2.34 = STRING: "Spanning Tree Group 34" iso.3.6.1.2.1.47.1.2.1.1.2.35 = STRING: "Spanning Tree Group 35" iso.3.6.1.2.1.47.1.2.1.1.2.36 = STRING: "Spanning Tree Group 36" iso.3.6.1.2.1.47.1.2.1.1.2.37 = STRING: "Spanning Tree Group 37" iso.3.6.1.2.1.47.1.2.1.1.2.38 = STRING: "Spanning Tree Group 38" iso.3.6.1.2.1.47.1.2.1.1.2.39 = STRING: "Spanning Tree Group 39" iso.3.6.1.2.1.47.1.2.1.1.2.40 = STRING: "Spanning Tree Group 40" iso.3.6.1.2.1.47.1.2.1.1.2.41 = STRING: "Spanning Tree Group 41" iso.3.6.1.2.1.47.1.2.1.1.2.42 = STRING: "Spanning Tree Group 42" iso.3.6.1.2.1.47.1.2.1.1.2.43 = STRING: "Spanning Tree Group 43" iso.3.6.1.2.1.47.1.2.1.1.2.44 = STRING: "Spanning Tree Group 44" iso.3.6.1.2.1.47.1.2.1.1.2.45 = STRING: "Spanning Tree Group 45" iso.3.6.1.2.1.47.1.2.1.1.2.46 = STRING: "Spanning Tree Group 46" iso.3.6.1.2.1.47.1.2.1.1.2.47 = STRING: "Spanning Tree Group 47" iso.3.6.1.2.1.47.1.2.1.1.2.48 = STRING: "Spanning Tree Group 48" iso.3.6.1.2.1.47.1.2.1.1.2.49 = STRING: "Spanning Tree Group 49" iso.3.6.1.2.1.47.1.2.1.1.2.50 = STRING: "Spanning Tree Group 50" iso.3.6.1.2.1.47.1.2.1.1.2.51 = STRING: "Spanning Tree Group 51" iso.3.6.1.2.1.47.1.2.1.1.2.52 = STRING: "Spanning Tree Group 52" iso.3.6.1.2.1.47.1.2.1.1.2.53 = STRING: "Spanning Tree Group 53" iso.3.6.1.2.1.47.1.2.1.1.2.54 = STRING: "Spanning Tree Group 54" iso.3.6.1.2.1.47.1.2.1.1.2.55 = STRING: "Spanning Tree Group 55" iso.3.6.1.2.1.47.1.2.1.1.2.56 = STRING: "Spanning Tree Group 56" iso.3.6.1.2.1.47.1.2.1.1.2.57 = STRING: "Spanning Tree Group 57" iso.3.6.1.2.1.47.1.2.1.1.2.58 = STRING: "Spanning Tree Group 58" iso.3.6.1.2.1.47.1.2.1.1.2.59 = STRING: "Spanning Tree Group 59" iso.3.6.1.2.1.47.1.2.1.1.2.60 = STRING: "Spanning Tree Group 60" iso.3.6.1.2.1.47.1.2.1.1.2.61 = STRING: "Spanning Tree Group 61" iso.3.6.1.2.1.47.1.2.1.1.2.62 = STRING: "Spanning Tree Group 62" iso.3.6.1.2.1.47.1.2.1.1.2.63 = STRING: "Spanning Tree Group 63" iso.3.6.1.2.1.47.1.2.1.1.2.64 = STRING: "Spanning Tree Group 64" iso.3.6.1.2.1.47.1.2.1.1.2.65 = STRING: "Spanning Tree Group 65" iso.3.6.1.2.1.47.1.2.1.1.2.66 = STRING: "Spanning Tree Group 66" iso.3.6.1.2.1.47.1.2.1.1.2.67 = STRING: "Spanning Tree Group 67" iso.3.6.1.2.1.47.1.2.1.1.2.68 = STRING: "Spanning Tree Group 68" iso.3.6.1.2.1.47.1.2.1.1.2.69 = STRING: "Spanning Tree Group 69" iso.3.6.1.2.1.47.1.2.1.1.2.70 = STRING: "Spanning Tree Group 70" iso.3.6.1.2.1.47.1.2.1.1.2.71 = STRING: "Spanning Tree Group 71" iso.3.6.1.2.1.47.1.2.1.1.2.72 = STRING: "Spanning Tree Group 72" iso.3.6.1.2.1.47.1.2.1.1.2.73 = STRING: "Spanning Tree Group 73" iso.3.6.1.2.1.47.1.2.1.1.2.74 = STRING: "Spanning Tree Group 74" iso.3.6.1.2.1.47.1.2.1.1.2.75 = STRING: "Spanning Tree Group 75" iso.3.6.1.2.1.47.1.2.1.1.2.76 = STRING: "Spanning Tree Group 76" iso.3.6.1.2.1.47.1.2.1.1.2.77 = STRING: "Spanning Tree Group 77" iso.3.6.1.2.1.47.1.2.1.1.2.78 = STRING: "Spanning Tree Group 78" iso.3.6.1.2.1.47.1.2.1.1.2.79 = STRING: "Spanning Tree Group 79" iso.3.6.1.2.1.47.1.2.1.1.2.80 = STRING: "Spanning Tree Group 80" iso.3.6.1.2.1.47.1.2.1.1.2.81 = STRING: "Spanning Tree Group 81" iso.3.6.1.2.1.47.1.2.1.1.2.82 = STRING: "Spanning Tree Group 82" iso.3.6.1.2.1.47.1.2.1.1.2.83 = STRING: "Spanning Tree Group 83" iso.3.6.1.2.1.47.1.2.1.1.2.84 = STRING: "Spanning Tree Group 84" iso.3.6.1.2.1.47.1.2.1.1.2.85 = STRING: "Spanning Tree Group 85" iso.3.6.1.2.1.47.1.2.1.1.2.86 = STRING: "Spanning Tree Group 86" iso.3.6.1.2.1.47.1.2.1.1.2.87 = STRING: "Spanning Tree Group 87" iso.3.6.1.2.1.47.1.2.1.1.2.88 = STRING: "Spanning Tree Group 88" iso.3.6.1.2.1.47.1.2.1.1.2.89 = STRING: "Spanning Tree Group 89" iso.3.6.1.2.1.47.1.2.1.1.2.90 = STRING: "Spanning Tree Group 90" iso.3.6.1.2.1.47.1.2.1.1.2.91 = STRING: "Spanning Tree Group 91" iso.3.6.1.2.1.47.1.2.1.1.2.92 = STRING: "Spanning Tree Group 92" iso.3.6.1.2.1.47.1.2.1.1.2.93 = STRING: "Spanning Tree Group 93" iso.3.6.1.2.1.47.1.2.1.1.2.94 = STRING: "Spanning Tree Group 94" iso.3.6.1.2.1.47.1.2.1.1.2.95 = STRING: "Spanning Tree Group 95" iso.3.6.1.2.1.47.1.2.1.1.2.96 = STRING: "Spanning Tree Group 96" iso.3.6.1.2.1.47.1.2.1.1.2.97 = STRING: "Spanning Tree Group 97" iso.3.6.1.2.1.47.1.2.1.1.2.98 = STRING: "Spanning Tree Group 98" iso.3.6.1.2.1.47.1.2.1.1.2.99 = STRING: "Spanning Tree Group 99" iso.3.6.1.2.1.47.1.2.1.1.2.100 = STRING: "Spanning Tree Group 100" iso.3.6.1.2.1.47.1.2.1.1.2.101 = STRING: "Spanning Tree Group 101" iso.3.6.1.2.1.47.1.2.1.1.2.102 = STRING: "Spanning Tree Group 102" iso.3.6.1.2.1.47.1.2.1.1.2.103 = STRING: "Spanning Tree Group 103" iso.3.6.1.2.1.47.1.2.1.1.2.104 = STRING: "Spanning Tree Group 104" iso.3.6.1.2.1.47.1.2.1.1.2.105 = STRING: "Spanning Tree Group 105" iso.3.6.1.2.1.47.1.2.1.1.2.106 = STRING: "Spanning Tree Group 106" iso.3.6.1.2.1.47.1.2.1.1.2.107 = STRING: "Spanning Tree Group 107" iso.3.6.1.2.1.47.1.2.1.1.2.108 = STRING: "Spanning Tree Group 108" iso.3.6.1.2.1.47.1.2.1.1.2.109 = STRING: "Spanning Tree Group 109" iso.3.6.1.2.1.47.1.2.1.1.2.110 = STRING: "Spanning Tree Group 110" iso.3.6.1.2.1.47.1.2.1.1.2.111 = STRING: "Spanning Tree Group 111" iso.3.6.1.2.1.47.1.2.1.1.2.112 = STRING: "Spanning Tree Group 112" iso.3.6.1.2.1.47.1.2.1.1.2.113 = STRING: "Spanning Tree Group 113" iso.3.6.1.2.1.47.1.2.1.1.2.114 = STRING: "Spanning Tree Group 114" iso.3.6.1.2.1.47.1.2.1.1.2.115 = STRING: "Spanning Tree Group 115" iso.3.6.1.2.1.47.1.2.1.1.2.116 = STRING: "Spanning Tree Group 116" iso.3.6.1.2.1.47.1.2.1.1.2.117 = STRING: "Spanning Tree Group 117" iso.3.6.1.2.1.47.1.2.1.1.2.118 = STRING: "Spanning Tree Group 118" iso.3.6.1.2.1.47.1.2.1.1.2.119 = STRING: "Spanning Tree Group 119" iso.3.6.1.2.1.47.1.2.1.1.2.120 = STRING: "Spanning Tree Group 120" iso.3.6.1.2.1.47.1.2.1.1.2.121 = STRING: "Spanning Tree Group 121" iso.3.6.1.2.1.47.1.2.1.1.2.122 = STRING: "Spanning Tree Group 122" iso.3.6.1.2.1.47.1.2.1.1.2.123 = STRING: "Spanning Tree Group 123" iso.3.6.1.2.1.47.1.2.1.1.2.124 = STRING: "Spanning Tree Group 124" iso.3.6.1.2.1.47.1.2.1.1.2.125 = STRING: "Spanning Tree Group 125" iso.3.6.1.2.1.47.1.2.1.1.2.126 = STRING: "Spanning Tree Group 126" iso.3.6.1.2.1.47.1.2.1.1.2.127 = STRING: "Spanning Tree Group 127" iso.3.6.1.2.1.47.1.2.1.1.2.128 = STRING: "Spanning Tree Group 128"
And for .1.3.6.1.2.1.47.1.2.1.1.3 I got:
iso.3.6.1.2.1.47.1.2.1.1.3.1 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.2 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.3 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.4 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.5 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.6 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.7 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.8 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.9 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.10 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.11 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.12 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.13 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.14 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.15 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.16 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.17 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.18 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.19 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.20 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.21 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.22 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.23 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.24 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.25 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.26 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.27 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.28 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.29 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.30 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.31 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.32 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.33 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.34 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.35 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.36 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.37 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.38 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.39 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.40 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.41 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.42 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.43 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.44 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.45 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.46 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.47 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.48 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.49 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.50 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.51 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.52 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.53 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.54 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.55 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.56 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.57 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.58 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.59 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.60 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.61 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.62 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.63 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.64 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.65 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.66 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.67 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.68 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.69 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.70 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.71 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.72 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.73 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.74 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.75 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.76 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.77 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.78 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.79 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.80 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.81 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.82 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.83 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.84 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.85 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.86 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.87 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.88 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.89 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.90 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.91 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.92 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.93 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.94 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.95 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.96 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.97 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.98 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.99 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.100 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.101 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.102 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.103 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.104 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.105 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.106 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.107 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.108 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.109 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.110 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.111 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.112 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.113 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.114 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.115 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.116 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.117 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.118 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.119 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.120 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.121 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.122 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.123 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.124 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.125 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.126 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.127 = OID: iso.3.6.1.2.1.17 iso.3.6.1.2.1.47.1.2.1.1.3.128 = OID: iso.3.6.1.2.1.17
On Wed, 28 Mar 2012 13:59:11 +0000 Rene Romijn r.romijn@deli-ict.nl wrote:
If you issue a couple of more snmpwalk commands against the switch, one for .1.3.6.1.2.1.47.1.2.1.1.2 (ENTITY-MIB::entLogicalDescr) and one for .1.3.6.1.2.1.47.1.2.1.1.3 (ENTITY-MIB::entLogicalType), what do you get?
For .1.3.6.1.2.1.47.1.2.1.1.2 I get:
iso.3.6.1.2.1.47.1.2.1.1.2.1 = STRING: "Spanning Tree Group 1"
[...]
And for .1.3.6.1.2.1.47.1.2.1.1.3 I got:
iso.3.6.1.2.1.47.1.2.1.1.3.1 = OID: iso.3.6.1.2.1.17
[...]
Ok, do a final one for .1.3.6.1.2.1.47.1.2.1.1.4 (ENTITY-MIB::entLogicalCommunity). You don't need to paste the output, since it will likely be a bunch of community strings.
Are all these strings the same, and are they all the SNMP community of your device? If so, I think I know what the problem could be.
Ok, do a final one for .1.3.6.1.2.1.47.1.2.1.1.4 (ENTITY-MIB::entLogicalCommunity). You don't need to paste the output, since it will likely be a bunch of community strings.
Are all these strings the same, and are they all the SNMP community of your device? If so, I think I know what the problem could be.
I have paste i little part of the command:
iso.3.6.1.2.1.47.1.2.1.1.4.93 = STRING: "@stg93" iso.3.6.1.2.1.47.1.2.1.1.4.94 = STRING: "@stg94" iso.3.6.1.2.1.47.1.2.1.1.4.95 = STRING: "@stg95" iso.3.6.1.2.1.47.1.2.1.1.4.96 = STRING: "@stg96" iso.3.6.1.2.1.47.1.2.1.1.4.97 = STRING: "@stg97"
It goes from @stg1 to @stg128
On Thu, 29 Mar 2012 06:40:29 +0000 Rene Romijn r.romijn@deli-ict.nl wrote:
Ok, do a final one for .1.3.6.1.2.1.47.1.2.1.1.4 (ENTITY-MIB::entLogicalCommunity). You don't need to paste the output, since it will likely be a bunch of community strings.
Are all these strings the same, and are they all the SNMP community of your device? If so, I think I know what the problem could be.
I have paste i little part of the command:
iso.3.6.1.2.1.47.1.2.1.1.4.93 = STRING: "@stg93" iso.3.6.1.2.1.47.1.2.1.1.4.94 = STRING: "@stg94" iso.3.6.1.2.1.47.1.2.1.1.4.95 = STRING: "@stg95" iso.3.6.1.2.1.47.1.2.1.1.4.96 = STRING: "@stg96" iso.3.6.1.2.1.47.1.2.1.1.4.97 = STRING: "@stg97"
It goes from @stg1 to @stg128
Are those actual community strings that were reported, or are they prefixed by your switch' community?
I'm guessing your Gbe2c switch supports the MSTP protocol, and this is how it reports spanning tree groups (since the BRIDGE-MIB is only adapted to a single spanning tree). I quickly googled Gbe2c and found they have a proprietary MIB to map VLANs to spanning tree groups.
Nevertheless, it seems Gbe2c doesn't use multiple BRIDGE-MIB instances to add per VLAN-information in the same manner as Cisco does. I think maybe the best way for NAV to work around this is to limit itself to doing it the "Cisco way" only if the device reports a Cisco enterprise ID.
Even if we do fix it like that, NAV will not be able to get a proper list of STP blocking ports on your Gbe2c switches. That would require an implementation of their proprietary MIB, and I have no Gbe2c device to test on. NAV should, however, be able to get a proper switch port listing for your switch.
On Thu, 29 Mar 2012 08:58:22 +0200 Morten Brekkevold morten.brekkevold@uninett.no wrote:
Nevertheless, it seems Gbe2c doesn't use multiple BRIDGE-MIB instances to add per VLAN-information in the same manner as Cisco does. I think maybe the best way for NAV to work around this is to limit itself to doing it the "Cisco way" only if the device reports a Cisco enterprise ID.
Rene, I reported your issue in the bugtracker and added a patch that will possibly fix the problem:
https://bugs.launchpad.net/nav/+bug/972211
Could you apply the patch and test again?
Rene, I reported your issue in the bugtracker and added a patch that will possibly fix the problem:
Could you apply the patch and test again?
-- Morten Brekkevold UNINETT
Sure, no problem, can you give me a little hand how to apply the diff file? .
On Tue, 3 Apr 2012 09:19:45 +0000 Rene Romijn r.romijn@deli-ict.nl wrote:
Rene, I reported your issue in the bugtracker and added a patch that will possibly fix the problem:
Could you apply the patch and test again?
Sure, no problem, can you give me a little hand how to apply the diff file? .
If you're using the Debian package, something like this should work (as the python libraries are installed into /usr/share/pyshared):
patch -p2 -d /usr/share/pyshared < patchfile
If you're using the Debian package, something like this should work (as the python libraries are installed into /usr/share/pyshared):
patch -p2 -d /usr/share/pyshared < patchfile
I patched the file and it seems to be working! :).
http://www.romijnfotografie.nl/web/gbe2cw.png
Thanks for your support and fast fixing this issue.
Rene.
On Tue, 3 Apr 2012 09:51:14 +0000 Rene Romijn r.romijn@deli-ict.nl wrote:
I patched the file and it seems to be working! :). Thanks for your support and fast fixing this issue.
Thanks for report the issue and testing the patch :-)
-
Morten Brekkevold -
Rene Romijn