Visible devices
6Two routers, three switches and a server
Guided example
Explore the interactive topology, then follow a device through interfaces, monitoring and support.
Visible devices
6Two routers, three switches and a server
Example connections
5Port labels and a sample uplink fault
Example sites
Blantyre + LilongweFictional ITES-style office and branch
Explore a fictional ITES-style network across two sites. Select a router, switch or server for details; zoom or drag to inspect the links. The WAN link illustrates the site connection, not a discovered physical cable.
Simulated example — no live network access or automatic refresh. Use Tab or arrow keys to navigate devices.
Green: example link up. Red: example uplink down. Green device icons mean the device still responds in this scenario.
Simulated device response. Example condition: Uplink down. No network check was performed.
Explore sample device →Simulated device response. Example condition: No open incident. No network check was performed.
Explore sample device →Simulated device response. Example condition: Low available memory. No network check was performed.
Explore sample device →Simulated device response. Example condition: LAN uplink down. No network check was performed.
Explore sample device →Simulated device response. Example condition: No open incident. No network check was performed.
Explore sample device →Simulated device response. Example condition: No open incident. No network check was performed.
Explore sample device →Explore the six devices shown on the map. Compare the uplink incident with working branch links and a server memory warning.
Selected demo device
18 Mbit/s
Simulated demo value
Unavailable in this profile
Simulated demo value
Unavailable in this profile
Simulated demo value
Example link states and traffic; no actual observations or network checks were performed.
| Port | Connected to | Link | Speed | Example traffic |
|---|---|---|---|---|
| ether1 | Blantyre WAN router | Up | 1 Gbit/s | 18 Mbit/s |
| ether2 | Branch LAN | Up | 1 Gbit/s | 12 Mbit/s |
No incident in this sample scenario
Review port traffic and link status. Choose a separate BGP profile if you need BGP neighbour information and your router exposes the required MIB.
In real monitoring, unsupported or missing data is shown as unavailable. These sample values do not certify hardware support.
Simulated response example
01
A configured rule opens an incident. Your alert policy selects the site, severity and email recipient or signed webhook.
02
Quiet hours and maintenance windows shape collaboration notifications. A delayed escalation can notify support if the incident remains unacknowledged.
03
An authorised engineer can review the incident in the Android companion, assign it to themselves and record incident notes. Offline work stays pending until sync.
Illustrative workflow only. No notifications are sent and no mobile work is synchronised by this demo.
The Netriva advantage
Keep monitoring, response and incident evidence in one workflow, with clear visibility when connectivity or data is missing.
Use the Android companion to review incidents, acknowledge and assign work to yourself, and capture incident notes. Encrypted offline notes and acknowledgements show their pending sync status. QR scanning, maintenance checklists and private photos support site visits.
Choose sites, recipients and severity for email or signed webhooks. Set quiet hours, critical overrides, maintenance windows and escalation delays. Keep notification attempts and delivery status alongside the incident.
Collectors can buffer observations during WAN interruptions within configured limits. Optional site monitoring can evaluate rules and notify locally when configured. Older evidence keeps its original time when the connection returns.
Missing or stale readings stay visible. Acknowledging an incident records a response; new measurements confirm recovery. Coverage reports show the observed period and data gaps so your team can judge the evidence.
Connect incidents to devices, interfaces, owners, notes and runbooks. With the required sources configured, verified service dependencies reveal impact and configuration history helps explain what changed.
Choose your own server or ITES hosting. Give people access by workspace, role and site, including the mobile companion. Monitoring uses approved read-only collection and diagnostics.
The Android companion is available to all Netriva users. Sign in with your Netriva account; your workspace role controls the sites and actions you can access. Notification delivery follows your configured alert settings.