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?
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.
Topology & Impact
Expand a branch, highlight descendants and inspect the evidence behind its connections. This demo uses fictional data.
CORE-01 · Core router
Root device · Healthy in this scenario
Immediate downstream: DIST-01, BH-01.
Accessible network inventory and connection evidence
| Device | Parent | Evidence |
|---|---|---|
| Root | Root device | |
| CORE-01 | Confirmed · LLDP | |
| DIST-01 | Confirmed · LLDP | |
| ACCESS-01 | Confirmed · CDP | |
| OLT-01 | Supported vendor-profile association | |
| ONT-01 | Forwarding-table evidence | |
| OLT-01 | Supported vendor-profile association | |
| ONT-02 | Forwarding-table evidence | |
| CORE-01 | Manual boundary reference | |
| BH-01 | Manual site dependency | |
| TOWER-01 | Manual site dependency | |
| SEC-01 | Wireless association | |
| SEC-01 | Wireless 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.
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