Just installed LANSurveyor yesterday and doing some test runs to get used to the program.
One big flaw I keep seeing is inaccurate port assignment information.. For examble, I have a Cisco 3560 that is connected to a Cisco 1131 AP. Physically it is on port 1/42 but LANSurveyor shows (and yes I did multiple scans) it is on port 1/46. Even more perplexing is the fact that tere is NOTHING plugged into port 46..
Any thoughts why this is happening or what I can do to make the scans more accurate?
Thanks
Troy
I think your best bet is to open a support case and we can work with you to troubleshoot this further.
No one else has noticed this in LAN Surveyor??? Has anyone paid attention to their maps??
I have been through several days of support only to get the answer that they use a particulat MIB to populate that information, which is fine, but why can't they use a MIB that means something to a human... All I can get is Port 1/46 or Port 46, when in reality the device is on Port 42. I use the Engineers Toolset, Orion and Cirrus products and they all label interfaces the way the switch does, IE FastEthernet0/42. So why does this product have to act differently???
I can't believe that no one else has noticed this before......
Cisco switches often use non-unique names for all their interface names, e.g. "FastEthernet10/100". Further, Cisco has Cisco-specific SNMP data/MIBs that contain more humanly-readable data. LANsurveyor uses that Cisco-specific name rather than the interface name because of the two preceding facts.
Unfortunately, your switch returns names that don't agree with the hardware labeling on the switch itself. We've never seen a switch do this before and, in reviewing the support case you opened, it appears this is the only switch on your network that is experiencing this problem. If you have a current Cisco support contract for that switch, it would be interesting to submit a support case asking why the names returned in their Stack MIB differ from the hardware labeling. We would be glad to provide additional technical details regarding this situation if you would like.
We have also entered a LANsurveyor feature request to have LANsurveyor use the interface name as a switch label for Cisco switches.