Network Bridge Connectivity Mapping for Hosts Without LLDP

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network analysis tools struggle to determine connectivity information for host devices that do not implement Layer 2 discovery protocols like LLDP, leading to incomplete network topology visualization and hindered network troubleshooting and analysis.

Innovation Solution

A network analysis system collects underlay and overlay flow information, correlates remote MAC addresses with IP addresses using SNMP queries, and determines connectivity data even for devices lacking LLDP, enabling comprehensive network topology visualization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If LLDP protocol is used for network device discovery, then connectivity information can be obtained for devices implementing the protocol, but connectivity information cannot be obtained for devices that do not implement LLDP

Engineering Contradiction:
Improveconnectivity informationVSAvoidprotocol compatibility
Core Design Contradiction:
Loss of informationVSAdaptability or versatility

Solution Approach 1:

The patent uses an intermediary approach by leveraging the bridge device's LLDP capability to discover connectivity information about non-LLDP host devices. The bridge device acts as a mediator that can identify connected hosts through its LLDP implementation, thereby providing connectivity information for devices that themselves do not support LLDP.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent substitutes the direct LLDP mechanism (which requires both devices to support it) with an alternative approach using the bridge device's LLDP capability combined with MAC address correlation. This replacement mechanism achieves the same goal of discovering connectivity information without requiring the host device to implement LLDP.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Ease of manufacture

If only LLDP-implementing devices are tracked, then connectivity data is easier to obtain, but network topology visualization remains incomplete

Engineering Contradiction:
Improveease of obtaining connectivity dataVSAvoidnetwork topology completeness
Core Design Contradiction:
Ease of manufactureVSLoss of information

Solution Approach 1:

The patent performs preliminary action by having the bridge device collect and store MAC address information of connected host devices in advance. This pre-collected MAC address data is then correlated with LLDP connectivity information to complete the network topology, ensuring both ease of data acquisition and completeness of visualization.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges two different data sources: LLDP connectivity information from the bridge device and MAC address information from flow data or other sources. By combining these data sources and correlating them through MAC addresses, the system achieves complete network topology visualization while maintaining ease of data collection.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP3937425B1Deriving network device and host connection
Publication Date: 2025.09.10 JUNIPER NETWORKS INC
  • EP3937425B1 patent drawingFigure 1
  • EP3937425B1 patent drawingFigure 2
  • EP3937425B1 patent drawingFigure 3

AI summary

This disclosure describes techniques that determine device connectivity in the absence of a network layer 2 discovery protocol such as Link Layer Discovery Protocol (LLDP). In one example, this disclosure describes a method that includes retrieving, from a bridge data store of a bridge device on a network having one or more host devices, a plurality of first interface indexes, wherein each first interface index corresponds to a network interface of network interfaces of the bridge device; retrieving, from the bridge data store, remote network addresses corresponding to the network interfaces of the bridge device, each remote network address of the remote network addresses corresponding to a second interface index; selecting a remote network address having a second interface index that matches the first interface index; determining a host device having the selected remote network address; and outputting an indication that the bridge device is coupled to the host device.