Platform / Network Topology & Impact Analysis

See How Everything Connects. Know What Every Failure Affects.

Explore relationships discovered through LLDP, CDP, forwarding information and wireless associations. Trace downstream dependencies while keeping the evidence behind each connection visible.

NOC operators, engineers and maintenance planners

Which customers depend on this device?

Sample · Downstream impact3 devicesTOWER-01 · 2 affected customers

Feature guide 5 features

Upstream tracing

Follow the path from customer equipment toward its parent infrastructure.

Why it helpsLocate the first shared dependency when several customers report the same symptom.

Downstream tracing

Select a device and inspect its dependent branch.

Why it helpsEstimate the scope of a maintenance interruption.

Connection evidence

Inspect discovery evidence, manually recorded dependencies and uncertain candidate links.

Why it helpsDecide which connections need field verification.

Customer and device impact

Count affected equipment and customers separately.

Why it helpsGive the NOC a repair scope and support a subscriber impact count.

Site and branch exploration

Filter by site, expand a branch and inspect individual devices.

Why it helpsFocus on one access path while retaining its upstream context.

Try it for yourself

Topology & Impact

Expand a branch, highlight descendants and inspect the evidence behind its connections. This demo uses fictional data.

Topology & ImpactFICTIONAL SAMPLE NETWORK
PON-01
PON-02
— Discovery-supported⋮ Manual dependency┄ Uncertain candidate: ACCESS-01 → RTR-02 (excluded from confirmed impact)

CORE-01 · Core router

Root device · Healthy in this scenario

Immediate downstream: DIST-01, BH-01.

Accessible network inventory and connection evidence
DeviceParentEvidence
RootRoot device
CORE-01Confirmed · LLDP
DIST-01Confirmed · LLDP
ACCESS-01Confirmed · CDP
OLT-01Supported vendor-profile association
ONT-01Forwarding-table evidence
OLT-01Supported vendor-profile association
ONT-02Forwarding-table evidence
CORE-01Manual boundary reference
BH-01Manual site dependency
TOWER-01Manual site dependency
SEC-01Wireless association
SEC-01Wireless association

OLT-01 connects ONT-01 via PON-01 and ONT-02 via PON-02. ONT-02 connects RTR-02. Logical PON ports are not additional monitored devices. An uncertain ACCESS-01 → RTR-02 candidate is excluded from confirmed impact calculations.

Confirmed links use discovery evidence. Tower relationships and the cross-company backhaul reference are manual operational dependencies.

Fixed sample · 12 Nov 2026, 09:00 UTC · No real equipment
Connect your network. Connect your operations.

See your network. In a new light.

See how IconWave can simplify monitoring, automate device management and give your team a complete view of your network.

Request a Demo