Switch Port Mapper Problems

rshanks

I was pretty excited to see the switch port mapper program, however, it doesn't seem to work on the majority of my switches. An example is a closet with two 2950T switches. One Gig port on each switch goes back to the backbone switch, the other Gig ports are connected to each other but placed in blocking by spanning tree for redundancy. Every time I try to run the switch port mapper I get this:

Run-time error '457':
This key is already associated with an element of this collection.

If I shut down the redundant Gig port on the switch, I don't get this error anymore, instead switch port mapper stops responding part of the way through the process and my switch is dead for about 60 seconds. It does not reboot, it simply stops responding to network traffic, and then, just as suddenly, starts again.

Anyone else had similar problems with switch port mapper? It seems to run fine on switches that I don't have deployed a redundant spanning tree design. I've tried it from multiple machines, so I don't think the problem is my install of SolarWinds.

RS

zmerch

I was pretty excited to see the switch port mapper program, however, it doesn't seem to work on the majority of my switches.... Run-time error '457': This key is already associated with an element of this collection. RS

I found out why this is happening (as I also have an older version of the Port Mapper software and searched for this error) - Certain switches can return multiple exact MIBs while still continuing through the SNMPwalk - but the array type that SolarWinds used cannot handle multiple like entries in their index; and instead of checking to see if the index already exists, ignoring that entry & continuing it's abending.

Linux SNMP tools can help diagnose the problem if you have access to a linux box with them - there are also freeware tools for Win32 - google is your friend here. This is what I did:

snmpwalk -On -c mycommunityhere -v 2c -Ct -Cc 10.123.456.789 > AllDellSwitchInfo.txt

[[ If you leave off the -Cc switch, the SNMPwalk command will barf on the first duplicate (or non-increasing) MIB... but if you left it in, you can use linux to find the offending lines pretty easily:  ]]

awk '{print $1}' < AllDellSwitchInfo.txt | uniq -d

These are the repeated MIBs on my Dell PowerConnect switch:

.1.3.6.1.2.1.17.4.3.1.1.0.22.199.44.153.18 = Hex-STRING: 00 16 C7 2C 99 12
.1.3.6.1.2.1.17.4.3.1.1.0.22.199.44.185.191 = Hex-STRING: 00 16 C7 2C B9 BF

There were 3 instances of each of these MIBs in the full SNMPWalk.

Hope this helps!
Roger "Merch" Merchberger