Is it possible to have topology map view in Spectrum for servers configured as Pingable model like we have for Network devices
search cancel

Is it possible to have topology map view in Spectrum for servers configured as Pingable model like we have for Network devices

book

Article ID: 442451

calendar_today

Updated On:

Products

Network Observability CA Performance Management

Issue/Introduction

Like we are having the information in the Neighbors component details pane for SNMP configured devices, can we get the same information for Windows/Linux servers to which Network components they are connected.

Environment

 Spectrum :: All Supported Versions

Cause

Unlike SNMP-enabled devices that can provide their own connectivity data via MIB tables (such as the Bridge Table), Pingable models rely on external references from upstream Layer 3 devices to establish topology map views.

Technical Requirements

In order for Spectrum to resolve a connection between a Pingable model and a network device (Switch/Router), the following criteria must be met:

1. AutoDiscovery Configuration

The protocol for reading neighbor information is not enabled by default for ping-only discovery.

  • Action: In the AutoDiscovery Console, navigate to Modeling Options > Protocol Options.
  • Setting: Ensure "ARP Tables for Pingables" is checked.

2. Landscape Consistency

Spectrum must be able to correlate data between the server and its gateway.

  • Requirement: A Layer 3 device (Router or Switch) that resides in the same subnet as the Pingable model must be modeled in the same Spectrum Landscape.

3. Upstream Data Availability

Spectrum identifies the connection by querying the upstream device:

  • Mechanism: Spectrum reads the ipNetToMediaTable (ARP Table) of the modeled Layer 3 device.

Validation: If the IP address of the Pingable model is found in the ARP cache of the Layer 3 device, Spectrum populates the MAC_Address attribute (0x110df) on the Pingable model and creates the link.

Resolution

If you are seeing the pingable device (whether it is a network device or a windows/linux server that didn't respond to snmp) with no neighbors, then the upstream router did not have any connection information for that device.

Additional Information

how-to-discover-and-model-the-network