Hi!
I'm missing some interfaces and descriptions in my cricket-configuration on specific Cisco-models, on all my WS-C2960-48TC-L (48port 10/100 and 2x dual-purpose 1Gbit) the two first ports in the cricket configuration are given interface-index of the Gi's and the index for the two first Fa's are missing in the configuration.
this is an example:
target "1_1" order = 48 interface-index = 10101 short-desc = "Cisco 2960 48ports switch, 22A, 22A-skap, Forskjellige patcheskap"
target "1_2" order = 47 interface-index = 10102 short-desc = "Cisco 2960 48ports switch, 22A, 22A-skap, Forskjellige patcheskap"
target "1_3" order = 46 interface-index = 10003 short-desc = "Cisco 2960 48ports switch, 22A, 22A-skap, Forskjellige patcheskap"
If I go to "IP device info" in NAV the ports Fa0/1 and Fa0/2 are missing from the figure at the bottom.
On all my 2960, 3560 and 3750 interface descriptions are missing, but it's ok on 2940 and 4500.
To me it looks like something wrong with NAVs data collection, but I have no idea where to start looking...
This installation is a few months old, all running the latest and greatest Debian and NAV-package: $ cat /etc/debian_version 5.0.4 $ dpkg -l | grep nav ii nav 2+3.5.6-1lenny1 Network Administration Visualized
Any help is appreciated!
Cheers,
-Sigurd
On Wed, May 12, 2010 at 08:05:42AM +0200, Sigurd Mytting wrote:
If I go to "IP device info" in NAV the ports Fa0/1 and Fa0/2 are missing from the figure at the bottom.
Please use the switch port report. Either find the device in the All IP Devices report, or click on the # of swports in the summary on the IP Device Info page. Are these ports missing from this report? Are any switch ports lacking a port number in the port column?
On all my 2960, 3560 and 3750 interface descriptions are missing, but it's ok on 2940 and 4500.
It sounds like getDeviceData might have gotten confused while checking SNMP OID support on your devices.
When viewing the All IP Devices report there is a column titled "snmp". This shows the number of NAV-used SNMP OIDs the device has been found to reply to. Clicking this column will take you to a report of all the OIDs supported by that device. Make sure your 2960s, 3560s and 3750s have the ifAlias oidkey listed in these reports.
Alternately, you could install this report in report.local.conf to find the specific switches that NAV thinks does not support the ifAlias oidkey:
no_portname_support { $sql = " SELECT sysname, catid FROM netbox WHERE netboxid NOT IN (SELECT netboxid FROM netboxsnmpoid JOIN snmpoid USING (snmpoidid) WHERE oidkey='ifAlias') AND catid IN ('GSW', 'SW'); "; $title = "Switches apparently without ifAlias support"; }
On 05/25/2010 01:25 PM, Morten Brekkevold wrote:
Are these ports missing from this report? Are any switch ports lacking a port number in the port column?
Interfaces are missing and all switch ports have a port number, screenshot from one of the 2960 switches:
http://sm.at.ifi.uio.no/b3f44.png
Found this several times in /var/log/nav/getDeviceData/getDeviceData-stderr.log:
Want to delete port: 820, 1, 00a-sw-b3f44.vegvesen.no Want to delete port: 820, 2, 00a-sw-b3f44.vegvesen.no Want to delete port: 820, 2, 00a-sw-b3f44.vegvesen.no Want to delete port: 820, 1, 00a-sw-b3f44.vegvesen.no
(the same 2960 as in the screenshot above)
From getDeviceData.log it looks like data is collected and some of the ports dropped, did a grep on this device in todays log:
http://sm.at.ifi.uio.no/b3f44.txt
Make sure your 2960s, 3560s and 3750s have the ifAlias oidkey listed in these reports.
It seems like all my switches have the ifAlias oidkey.
The exact same thing happens on my test system with only 5 devices registered, the "normal" NAV installation have about 600 devices registered.
Any ideas?
Cheers,
-Sigurd
On Tue, May 25, 2010 at 09:34:48PM +0200, Sigurd Mytting wrote:
Interfaces are missing and all switch ports have a port number, screenshot from one of the 2960 switches:
Hi again, sorry for the late reply; we've been quite busy with NAV 3.6 lately, and since we're replacing gDD, it hasn't been given much priority lately.
Found this several times in /var/log/nav/getDeviceData/getDeviceData-stderr.log:
Want to delete port: 820, 1, 00a-sw-b3f44.vegvesen.no Want to delete port: 820, 2, 00a-sw-b3f44.vegvesen.no Want to delete port: 820, 2, 00a-sw-b3f44.vegvesen.no Want to delete port: 820, 1, 00a-sw-b3f44.vegvesen.no
(the same 2960 as in the screenshot above)
From getDeviceData.log it looks like data is collected and some of the ports dropped, did a grep on this device in todays log:
Well, my gut tells me this has something to do with a port number conflict (which is why I hate the concept of "port numbers" and why we've been trying to reduce its importance in NAV).
Seeing your gDD log and the final result, it seems it wants to assign port number 2 and 3 to two ports each: Fa0/1 and Gi0/1 both want port number 1, and Fa0/2 and Gi0/2 both want port number 2. It all depends on which MIB we're querying.
And so it seems the Gigabit ports are winning the conflict.
Using standard MIBs only, it would be Gi0/1 = 1, Gi0/2 = 2, Fa0/1 = 3, while Cisco MIBs will say Fa0/1 = 1, Fa0/2 = 2, Gi0/1 = 49, Gi0/2 = 50.
I haven't actually seen a conflict like this turn into missing ports before, but it is likely that some data structure in gDD still identifies each port by its "number". Your logs certainly indicate that it thinks there are duplicate ports, based on port numbers, and its deleting something it shouldn't
This should be reported as a bug: https://bugs.launchpad.net/nav/+filebug
It seems like all my switches have the ifAlias oidkey.
I've had another user complain about the exact same portname problem on IRC just last week. We debugged it to no avail, but it seems only a deep dive into the murky gDD code will help. Not sure whether he reported this as a bug, though...
-
Morten Brekkevold -
Sigurd Mytting