Network Topology & Dependencies
See what connects. Understand what depends on it.
A device list tells you what exists. Assure adds the relationships: which switch serves an access point, which uplink carries its traffic and which downstream devices share the same infrastructure.
01 / THE EVIDENCE
What Assure
brings together.
Device-to-port placement
Combine collected MAC tables and neighbour evidence to place access points, servers and other devices on their likely switch ports. MAC-table analysis provides a path when LLDP is unavailable.
Switch hierarchy
Follow access switches toward their parent switches and core. Use the hierarchy to investigate upstream faults before treating every disconnected device as a separate incident.
VLAN delivery
Inspect collected VLAN membership along the service path. Distinguish a missing membership from an unknown hop, and account for whether a WLAN is locally bridged or controller-tunnelled.
Impact context
Use topology to identify potentially affected downstream devices before a response. An inferred connection is evidence to investigate, not proof that every service takes that path.
03 / DEPLOYMENT & SCOPE
Agree what
good evidence needs.
Start with your estate.
Identify the sites, assets, service owners and existing collection paths. Confirm the measurements you need, their freshness and the supported platform versions.
Understand the capability boundary.
Topology depends on collection coverage and freshness. Unmanaged switches, incomplete tables and ambiguous paths can leave gaps. Confirm the path before using it to justify a configuration change.
Discuss coverage and deployment ↗SEE ASSURE IN CONTEXT
Your estate.
Your priorities.
Request a tailored demonstration of network topology & dependencies and the connected capabilities that matter to your team.
- Walk through a relevant investigation.
- Confirm platform and collection coverage.
- Discuss deployment and permitted responses.