Operations / illustrative inventory
Demo topology explorer
Explore example gateway, switch, access point and camera relationships without connecting to a network. These parent/child links are invented teaching fixtures, not verified cabling or real discovery.
Example states: connected, disconnected and pending. They do not indicate current availability.
- Gateways
- 1
- Switches
- 1
- Access points
- 1
- Cameras
- 1
Illustrative device hierarchy for Demo Branch A
Use Up/Down to move through devices and Left/Right to collapse or expand branches. These are example relationships, not observed links.
Try a modeled downstream impact
SyntheticChoose an invented device. This exercise follows only the example parent-child tree, assuming one path and no redundancy. It does not simulate real failover, predict an outage, or change any device state.
3 modeled devices in the hypothetical branch including Example PoE switch; 2 below it. These are counts of invented nodes, not devices observed offline.
- Gateways
- 0
- Switches
- 1
- Access points
- 1
- Cameras
- 1
Modeled branch: Example PoE switch → Example access point → Example camera. Arrows indicate traversal order, not confirmed physical links.
Modeled upstream chain
- Example gateway (gateway)
- Example PoE switch (switch)
1 modeled parent-child step from the fictional gateway. This is not a verified physical path or actual packet route.
What-if JSON includes fictional device IDs, labels, roles and counts; upstream path JSON additionally includes modeled parent IDs. Neither contains IPs, credentials, observation timestamps or real link evidence. A real topology may have alternate paths that this exercise cannot represent.
Explore modeled dependency concentration
Fictional treeSee which invented devices have the most modeled descendants. This count is not a real-world risk score, outage likelihood, service criticality, or proof of a single point of failure. Alternate links and failover are not modeled.
Rank 1: Example gateway
gateway · 3 modeled downstream devices · 4 including itself
Rank 2: Example PoE switch
switch · 2 modeled downstream devices · 3 including itself
Rank 3 (tied): Example access point
access point · 0 modeled downstream devices · 1 including itself
1 more fictional device tied at rank 3 is hidden. Use Show all to inspect the full tie group.
Scenario A selected: Example PoE switch. Review its modeled downstream impact above, or compare it with B below.
Download contains only allowlisted fictional identifiers, labels, roles, derived counts and an explicit unsampled source. It contains no IP addresses, device health, actual network paths or timestamps.
Compare two modeled branches
Synthetic A/BScenario A uses the device selected above: Example PoE switch. Choose a second invented device below. These are independent single-path assumptions, not simultaneous failures or a redundancy/failover analysis.
Illustrative A/B difference
Example PoE switch versus Example camera · invented devices only
Scenario A: 3 modeled nodes. Scenario B: 1. B has 2 fewer modeled nodes than A. No observed outage is implied.
- Shared by both
- 1
- Only in A
- 2
- Only in B
- 0
- Combined unique
- 3
Shared: Example camera.
Only A: Example PoE switch, Example access point. Only B: none.
Overlap means the same fictional node appears in both hypothetical branches. It does not demonstrate physical redundancy, actual reachability, or how a real device would fail over.
A/B downloads contain only fictional device IDs, labels, roles and calculated membership. CSV explicitly marks unsampled data and neutralizes common formula prefixes; spreadsheet importers vary. Neither format contains demo status, parent IDs, IPs or observed timestamps.
Export schema v1 includes only example site name, node labels, roles, demo states and parent IDs. No IP/MAC addresses, secrets or observation timestamps. PDF exports are not available; future PDFs must use pdfcn.
Reference: NetBox cabling and inventory concepts. Unlike real cabling records, these relationships are illustrative only.