The Layer 2 feature in InterMapper uses information from polling SNMP enabled devices (mainly switches) to determine connections.
Layer 2 wonâ€™t add interfaces or devices to the map. The devices should be present on the map, with their interfaces selected in the Interfaces window (including unnumbered interfaces) prior to running the scan for best results. The Edit > Map Settings > Layer 2 features tool allows control over what happens to the map following the scan.
Please note that this can cause your map to be rearranged and require some manual adjustment. The tables and objects used to determine connections include:
The algorithms used to determine connections depend on much of the above information being available and generally give best results if the switch is forwarding traffic, since many entries time out in slack periods.
Often information will show up in the Layer 2 window (device list view) that isnâ€™t included on the map, particularly switch-to-switch connections. Information about connections received from one side of a connection needs to be confirmed from the other side or by adjacent devices before it has been validated and can be included in map changes. These are the entries in the Connections (lower right) pane of the Layer 2 view that have asterisks shown to their left.
ref: The Layer 2 View |_____2
Often, by repeating the scan once or twice a day, additional information can be added and can cause further detail to be added to the map.
The layer 2 feature is not a discovery feature in InterMapper, though. It tries to show the layer 2 information that is available in addition to or instead of the default IP-centric view of the network.
For best results with DNS, be sure include DNS server addresses in the Edit > Server Settings > DNS/WINS Settings tool. If a device shows the SNMP sysName value, it means we didnâ€™t get a DNS response for its IP address. Please verify that PTR records are updated on the DNS server so that reverse lookups are possible (or test it from the command-line).