Hello,
I recently downloaded the LANSurveyor Express product and am experiencing an issue. All network discovery works fine, until it reaches one device. The device is a Cisco Catalyst 2900XL switch.
The top progress bar reads "Searching for IP Nodes" while the progress bar below that reads "Determining connectivity for {router/switch name}.
I have let it sit here for over an hour with no change, even narrowing it down to only mapping this device, still no result.
Anyone able to give me any tips on this?
Thanks,
Derek Humes
Matrix Healthcare Management Solutions
Hi Derek,
Sorry you are having trouble mapping your Cisco 2900XL switch. We are unaware of any problems with that particular model and have 29xx switches configured here at SolarWinds. Do you have a lot of VLANs configured for this device? That could potentially cause LANsurveyor Express to spend a lot of time querying it (although probably not for an hour or more).
If you would, please start LANsurveyor Express, click the Advanced button, click the Logging tab and check all the logging options. Then start a discovery including that 2900XL switch. When LANsurveyor gets hung up on the switch (let it hang for a few minutes to be sure), you can stop the discovery. Then post the LANsurveyor Express Log file (Start>LANsurveyor Express>LANsurveyor Express Log) to this forum. We'd be glad to take a look to see what might be happening.
Here is the log with the device name as ROUTER/SWITCH NAME, internal ip of device is 10.1.1.240. You can notice the part towards the bottom where it starts looping at 4:53PM on June 6th.
Also there are no VLANs on this switch besides the default VLAN1 for administration.
06/06/2008 16:53:43 (3188): LANsurveyor Express version 10.2 starting up...06/06/2008 16:53:43 (3188): Administrator status = 1 (1243976).06/06/2008 16:53:50 (3492): Start autodiscovery: NR:1, Ping:1, Reto:0, SNMP:1, SNMPv2c:1, SNMPv3:1, TB2:0, NB:1, SIP:1, Hops=006/06/2008 16:53:50 (3492): Autodiscover: SCD=1, err=0, dir=C:\Program Files\SolarWinds\LANsurveyor Express\06/06/2008 16:53:51 (3492): Autodiscovering 10.1.1.240-10.1.1.240...06/06/2008 16:53:51 (3492): DoIPNodeSearch: started DoICMPReceiptThread06/06/2008 16:53:51 (1052): DoICMPReceiptThread starting = 2050970406/06/2008 16:53:51 (3492): DoIPNodeSearch: starting UDP probes...06/06/2008 16:53:51 (1052): Discover new node: "" (10.1.1.240), flag=0x00001006/06/2008 16:53:51 (1052): Discover duplicate node: "" (10.1.1.240), flag=0x000010 (Port Unreachable)06/06/2008 16:53:51 (3492): DoIPNodeSearch: wait for responses06/06/2008 16:53:51 (3492): Received SNMP response from 10.1.1.240: SNMPv106/06/2008 16:53:51 (3492): Discover duplicate node: "ROUTER/SWITCH NAME" (10.1.1.240), flag=0x00000806/06/2008 16:53:51 (3492): Received SNMP response from 10.1.1.240: SNMPv106/06/2008 16:53:51 (3492): Discover duplicate node: "ROUTER/SWITCH NAME" (10.1.1.240), flag=0x00000806/06/2008 16:53:51 (3492): Received SNMP response from 10.1.1.240: SNMPv306/06/2008 16:53:51 (3492): Received SNMP response from 10.1.1.240: SNMPv106/06/2008 16:53:51 (3492): Discover duplicate node: "ROUTER/SWITCH NAME" (10.1.1.240), flag=0x00000806/06/2008 16:53:51 (3492): Received SNMP response from 10.1.1.240: SNMPv2c06/06/2008 16:53:51 (3492): Discover duplicate node: "ROUTER/SWITCH NAME" (10.1.1.240), flag=0x00000806/06/2008 16:53:51 (3492): Received SNMP response from 10.1.1.240: SNMPv106/06/2008 16:53:51 (3492): Discover duplicate node: "ROUTER/SWITCH NAME" (10.1.1.240), flag=0x00000806/06/2008 16:53:51 (3492): Received SNMP response from 10.1.1.240: SNMPv2c06/06/2008 16:53:51 (3492): Discover duplicate node: "ROUTER/SWITCH NAME" (10.1.1.240), flag=0x00000806/06/2008 16:53:51 (3492): Received SNMP response from 10.1.1.240: SNMPv2c06/06/2008 16:53:51 (3492): Discover duplicate node: "ROUTER/SWITCH NAME" (10.1.1.240), flag=0x00000806/06/2008 16:53:51 (3492): Received SNMP response from 10.1.1.240: SNMPv2c06/06/2008 16:53:51 (3492): Discover duplicate node: "ROUTER/SWITCH NAME" (10.1.1.240), flag=0x00000806/06/2008 16:53:52 (3492): DoIPNodeSearch: finished with address block06/06/2008 16:53:52 (3492): DoIPNodeSearch: starting reverse DNS resolutions...06/06/2008 16:53:52 (1052): Discover duplicate node: "ROUTER/SWITCH NAME" (10.1.1.240), flag=0x000010 (Port Unreachable)06/06/2008 16:53:52 (1052): DoICMPReceiptThread: ending06/06/2008 16:53:52 (3492): DoIPNodeSearch: finished reverse DNS resolutions06/06/2008 16:53:52 (3492): Finished autodiscovering 10.1.1.240-10.1.1.240.06/06/2008 16:53:52 (3492): Postprocessing "ROUTER/SWITCH NAME" (10.1.1.240)06/06/2008 16:53:52 (3492): DoNewMIBIITableSNMP: oid=1.3.6.1.2.1.4.20.1.1.10.1.1.240.06/06/2008 16:53:52 (3492): DoNewMIBIITableSNMP: oid=1.3.6.1.2.1.4.20.1.2.10.1.1.240.06/06/2008 16:53:52 (3492): DoNewMIBIITableSNMP: oid=1.3.6.1.2.1.4.20.1.3.10.1.1.240.06/06/2008 16:53:52 (3492): DoNewMIBIITableSNMP: oid=1.3.6.1.2.1.4.20.1.4.10.1.1.240.06/06/2008 16:53:52 (3492): DoNewMibIITableSNMP: (no match on header)06/06/2008 16:53:52 (3492): Postprocessing: adding subnet 10.1.1.0-10.1.1.25506/06/2008 16:53:52 (3492): DoMIBIITableSNMP: entry06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: oid=1.3.6.1.2.1.2.2.1.1.1.06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: oid=1.3.6.1.2.1.2.2.1.1.2.06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: oid=1.3.6.1.2.1.2.2.1.1.3.06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: oid=1.3.6.1.2.1.2.2.1.1.4.06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: oid=1.3.6.1.2.1.2.2.1.1.5.06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: oid=1.3.6.1.2.1.2.2.1.1.6.06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: oid=1.3.6.1.2.1.2.2.1.1.7.06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: oid=1.3.6.1.2.1.2.2.1.1.8.06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: oid=1.3.6.1.2.1.2.2.1.1.9.06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: oid=1.3.6.1.2.1.2.2.1.1.10.06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: oid=1.3.6.1.2.1.2.2.1.1.11.06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: oid=1.3.6.1.2.1.2.2.1.1.12.06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: oid=1.3.6.1.2.1.2.2.1.1.13.06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: oid=1.3.6.1.2.1.2.2.1.1.14.06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: finished with table (0).06/06/2008 16:53:52 (3492): DoMIBIITableSNMP: exit.06/06/2008 16:53:52 (3492): Failed to query cisco table. Error: -60 : Missing variables in PDU06/06/2008 16:53:52 (3492): Getting switch data "ROUTER/SWITCH NAME" (10.1.1.240)06/06/2008 16:53:52 (3492): DoBridgeTableSNMP(VLAN): oid=1.3.6.1.4.1.9.9.68.1.2.1.1.2.1.06/06/2008 16:53:52 (3492): Getting QBRIDGE switch data 10.1.1.24006/06/2008 16:53:58 (3492): DoActualBridgeTableSNMP: scanning TP bridge table.06/06/2008 16:54:01 (3492): DoActualBridgeTableSNMP: scanning STP bridge table.06/06/2008 16:54:04 (3492): DoActualBridgeTableSNMP: scanning BasePort bridge table.06/06/2008 16:54:07 (3492): DoBridgeTableSNMP(VLAN): oid=1.3.6.1.4.1.9.9.68.1.2.1.1.2.2.06/06/2008 16:54:07 (3492): Getting QBRIDGE switch data 10.1.1.24006/06/2008 16:54:13 (3492): DoActualBridgeTableSNMP: scanning TP bridge table.06/06/2008 16:54:16 (3492): DoActualBridgeTableSNMP: scanning STP bridge table.06/06/2008 16:54:19 (3492): DoActualBridgeTableSNMP: scanning BasePort bridge table.06/06/2008 16:54:23 (3492): DoBridgeTableSNMP(VLAN): oid=1.3.6.1.4.1.9.9.68.1.2.1.1.2.3.06/06/2008 16:54:23 (3492): Getting QBRIDGE switch data 10.1.1.24006/06/2008 16:54:29 (3492): DoActualBridgeTableSNMP: scanning TP bridge table.06/06/2008 16:54:32 (3492): DoActualBridgeTableSNMP: scanning STP bridge table.06/06/2008 16:54:35 (3492): DoActualBridgeTableSNMP: scanning BasePort bridge table.06/06/2008 16:54:38 (3492): DoBridgeTableSNMP(VLAN): oid=1.3.6.1.4.1.9.9.68.1.2.1.1.2.4.06/06/2008 16:54:38 (3492): Getting QBRIDGE switch data 10.1.1.24006/06/2008 16:54:44 (3492): DoActualBridgeTableSNMP: scanning TP bridge table.06/06/2008 16:54:47 (3492): DoActualBridgeTableSNMP: scanning STP bridge table.06/06/2008 16:54:50 (3492): DoActualBridgeTableSNMP: scanning BasePort bridge table.06/06/2008 16:54:53 (3492): DoBridgeTableSNMP(VLAN): oid=1.3.6.1.4.1.9.9.68.1.2.1.1.2.5.06/06/2008 16:54:53 (3492): Getting QBRIDGE switch data 10.1.1.24006/06/2008 16:54:59 (3492): DoActualBridgeTableSNMP: scanning TP bridge table.06/06/2008 16:55:02 (3492): DoActualBridgeTableSNMP: scanning STP bridge table.06/06/2008 16:55:05 (3492): DoActualBridgeTableSNMP: scanning BasePort bridge table.06/06/2008 16:55:08 (3492): DoBridgeTableSNMP(VLAN): oid=1.3.6.1.4.1.9.9.68.1.2.1.1.2.6.06/06/2008 16:55:08 (3492): Getting QBRIDGE switch data 10.1.1.24006/06/2008 16:55:14 (3492): DoActualBridgeTableSNMP: scanning TP bridge table.06/06/2008 16:55:17 (3492): DoActualBridgeTableSNMP: scanning STP bridge table.06/06/2008 16:55:20 (3492): DoActualBridgeTableSNMP: scanning BasePort bridge table.06/06/2008 16:55:23 (3492): DoBridgeTableSNMP(VLAN): oid=1.3.6.1.4.1.9.9.68.1.2.1.1.2.7.06/06/2008 16:55:23 (3492): Getting QBRIDGE switch data 10.1.1.24006/06/2008 16:55:29 (3492): DoActualBridgeTableSNMP: scanning TP bridge table.06/06/2008 16:55:32 (3492): DoActualBridgeTableSNMP: scanning STP bridge table.06/06/2008 16:55:35 (3492): DoActualBridgeTableSNMP: scanning BasePort bridge table.
The log file was very helpful. From the standpoint of SNMP on that switch, it thinks it has a *lot* of VLANs. The log file indicates there is a VLAN at every possible index: the entries start at VLAN #1 and going through at least VLAN #7 before your log runs out. This is what the switch is telling LANsurveyor Express so we have to trust it. For each VLAN, LANsurveyor Express (Ls/E) tries to gather switch (Bridge MIB) information. And, for whatever reason, that switch is not answering those queries (rather than returning an error or data) which causes the maximum timeout to occur. This means for every VLAN the switch is reporting, there is a 15-second timeout. This would definitely account for Ls/E appearing to be "hung" on that device.
I see three possible ways to resolve this:
1. Please make sure that the switch is configured as you describe it. The switch is telling Ls/E via SNMP that there are lots of VLANs and Ls/E has no reason to doubt those VLANs are real. However, the timeout indicates the switch isn't understanding those VLANs.
2. It's a little unlikely but can you make sure that the switch has the latest firmware installed? While Cisco is usually very accurate in their SNMP implementations, it may be that an early version of firmware has a bug with respect to VLAN reporting.
3. You can simply turn off the special Cisco VLAN processing of switches within Ls/E since you're reporting there is only a single VLAN. There is no user interface to do this however you can edit the Ls/E configuration/preferences file. That file is in the following folder: "C:\Documents and Settings\All Users\Application Data\SolarWinds\LANsurveyor Express". (The "Application Data" folder is normally hidden so you may have to turn off folder hiding.) Edit the file called "LANsurveyorVisio.ini" with a text editor and look for a line that has the following format: "bCiscoVLANIndexing=1". Change the "1" to a "0" (zero). Save the file then start up Ls/E. Cisco VLANs will not be processed and the 2900XL switch should be fairly quickly processed.