SD-WAN
Every SD-WAN fabric you run, in one health view
Tracix reads the APIs of the SD-WAN controllers you already run and shows sites, edges, tunnels and controller alarms side by side, with a health verdict that names its evidence. Cisco Catalyst SD-WAN adds tunnel state and loss, latency and jitter in each direction.
- 7 controller APIs
- Read-only
- 60-second polling
How it works
From a controller API to a site you can explain
Connectors only read. Tracix never pushes policy to your controllers or steers traffic.
- 01ConnectAdd a controller's URL and its API credential: a password, key, token or OAuth client, depending on the vendor.
- 02PollEvery 60 seconds by default, read WAN links, overlay paths, application quality, device health and events.
- 03JudgeEach site is healthy, degraded, critical or unknown, with the evidence and coverage behind it.
- 04FoldController alarms for the same device and condition become one episode instead of an alarm storm.
- 05InvestigatePin an interval at a site and compare it with the period before, one explanation at a time.
Tunnels
Both directions of every tunnel, on Cisco Catalyst SD-WAN
For Cisco Catalyst SD-WAN, Tracix reads each BFD session in both directions, so a tunnel that loses packets one way shows as one-way trouble instead of an average that hides it.
- Loss, latency and jitter per direction, judged against one published policy: 1% loss, 250 ms latency or 30 ms jitter
- The controller's own App-route SLA verdict beside Tracix's, and TLOCs and control connections for each WAN Edge
- Meraki, EdgeConnect and Prisma SD-WAN report path loss, latency and jitter without direction or tunnel state
Investigate
Ask what changed at a site, and see the evidence for each answer
Pin an interval at one site and Tracix compares it with the same length of time just before it, then ranks eight explanations, from a failing access circuit to a telemetry gap, by the evidence the controller actually reported.
Eight explanations
Each is supported, possible, not supported or short of evidence, with a confidence.
Honest about gaps
No connector reports carriers or config changes, so those answers say so.
Episodes, not alarm storms
Alarms for one device and condition fold into one episode.
Coverage you can see
Every site says whether its evidence is complete, partial, stale or unavailable.
Explanations
Better together
The WAN next to the network and apps it connects
SD-WAN health lives in the same workspace as your device metrics and application checks, so a slow branch and the app it reaches are one search apart.
- Network device monitoringPoll the routers, switches and firewalls at each site over SNMP, with traps and syslog.Learn more
- Synthetic monitoringTest the apps each site depends on, with an optional hop-by-hop path on each run.Learn more
- BrainAsk about a site in plain language; Brain reads its sites, episodes and tunnels with your permissions.Learn more
Controllers
What each controller gives you, stated plainly
Coverage depends on what each controller's API reports. Verified means checked against a real controller in our lab, implemented means tested against modelled API responses, and partial means collected with gaps.
| Controller | Device inventory | Tunnel state | Loss, latency and jitter | Applications | Controller events |
|---|---|---|---|---|---|
| Cisco Catalyst SD-WAN | Verified | Verified, per direction | Verified, per direction | Not collected | Partial |
| Cisco Meraki | Partial | Not collected | Partial | Partial | Partial |
| Cato Networks | Partial | Not collected | Not collected | Not collected | Partial |
| VMware VeloCloud | Partial | Not collected | Not collected | Partial | Partial |
| HPE Aruba EdgeConnect | Partial | Not collected | Partial | Partial | Partial |
| Juniper Mist WAN Assurance | Partial | Not collected | Not collected | Partial | Partial |
| Prisma SD-WAN | Not collected | Not collected | Partial | Partial | Partial |
Edge CPU and memory come from Cisco Catalyst SD-WAN (verified) and Juniper Mist (implemented). No connector reports HA state, the carrier behind a link or configuration changes yet. Cisco Catalyst SD-WAN was verified against SD-WAN Manager 20.x; the other six connectors have not yet been tested against a real controller, and the Sources tab in Tracix lists the gaps for each.
Can Tracix change SD-WAN policy or steer traffic?
Do SD-WAN alarms raise Tracix alerts?
Which connectors are tested against real controllers?
Does Tracix show the path a tunnel takes?
Connect your first SD-WAN controller
Add the controller URL and an API credential, and the fabric view fills in on the next poll.