Resolution: |
Sometimes LANsurveyor cannot determine your exact network configuration from your switches and hubs. Some nodes accessing the network through a switch or hub may not be shown as connected through that switch or hub on the LANsurveyor map for any of the following reasons:
-
The correct SNMP community string for the unmapped device was not entered.
LANsurveyor requires access to the device's management features to gather port information.
-
One or more switches or hubs are not managed.
LANsurveyor uses SNMP (Simple Network Management Protocol) to map managed switches and hubs, and it is unable to collect required information from any device that either does not support SNMP or is unmanaged. For more information, see "Appendix C - SNMP Checklist" in the SolarWinds LANsurveyor Administrator Guide.
-
An SNMP router or common device (server, printer, etc.) isn't included.
Switches return tables of known Ethernet addresses. Since switches know nothing about IP addresses (they operate on layer 2, not layer 3), it is essential that other nodes on the network provide mappings among Ethernet and IP addresses. LANsurveyor acquire mapping information from the ARP caches of other devices on the network, using SNMP queries. Routers are ideal sources of this information, since the traffic from most nodes goes through routers. If a router is not available, a shared printer or server will often provide the required information.
-
One or more unmanaged switches or hubs are connected to a managed switch or hub.
In some environments, users may have multiple computers connected to the network with an inexpensive switch or hub. In this situtation, it is impossible to determine the managed device to which an unmanaged device is connected, especially when the managed device is connected to other managed devices, because the Ethernet addresses for the devices connected to the unmanaged device appear in multiple switches. In other words, the port through which the unmanaged device is connected looks just like any other uplink port and the connection is not definitive. You may be able to determine your actual port configuration using LANsurveyor's standard Switch/Hub Ports Report. See Physical Address below. For more information about the LANsurveyor Switch/Hub Ports Report, see the Switch/Hub Port Connectivity FAQ Detail.
Note:The Switch/Hub Port Report shows the current content of the switch table for the switch on which you run the report. The values in this table may change over time depending on the switch, the network traffic, and the network connections. Further, what you see on the map is based on data from several different sources and intelligence to put it all together in a meaningful way. As a result, what you see in the report and what is on the map will not necessarily always be the same.
Before contacting support, please create a new map and log file. The following procedure generates a new customer map and the associated log file required to address layer-2 mapping issues.
To generate a new map and log file:
1. If Continuous Scan is running, click Monitor > Continuous Scan > Stop Scanning to stop it.
2. Restart LANsurveyor.
3. Click Tools > Options > Logging to ensure that all logging on .
4. Run a new discovery.
5. Save both the map and the log file.
Note: To access the log file, click Start > SolarWinds LANsurveyor > LANsurveyor Log.txt.
6. At this point you can restore Continuous Scan by clicking Monitor > Continuous Scan > Start Scanning.
7. Please attach both the map and the log file to your NetSuite case with a full explanation of exactly what you consider inaccurate on the map and what the connectivity should be. For example, "On the map, Node X at IP address 192.168.0.1 is shown connected to Switch Y on port Z. My internal documentation shows that Node X is really connected to Switch V on port W."
For more information about layer-2 mapping with LANsurveyor, see the Switch/Hub Port Connectivity FAQ Detail.
This article applies to:
All versions of LANsurveyor
|
