Back to All Scenarios
PASSEDvendor / sdwan_path_failover
SD-WAN Path Failover — Primary ISP Down
The primary MPLS circuit at a branch office goes down. SD-WAN fails over to the backup broadband link. Voice quality degrades due to higher jitter on the broadband path.
Pattern
SDWAN_EVENT
Severity
CRITICAL
Confidence
85%
Remediation
Remote Hands
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | SDWAN_EVENT | SDWAN_EVENT | |
| Severity Assessment | CRITICAL | CRITICAL | |
| Incident Correlation | Yes | 36 linked | |
| Cascade Escalation | Yes | Yes | |
| Remediation | — | Remote Hands — Corax contacts on-site support via call, email, or API |
Scenario Conditions
Branch office with SD-WAN (Fortinet/FortiGate). Primary: 100Mbps MPLS (20ms latency). Backup: 200Mbps broadband (45ms latency, 15ms jitter). 50 users, 20 VoIP phones.
Injected Error Messages (3)
SD-WAN path failover at Branch-ATL — primary MPLS link down, traffic rerouted to broadband backup, sdwan overlay tunnel re-established on secondary WAN
MPLS circuit down at Branch-ATL — PE-CE link failure detected, carrier reporting fiber cut, LDP session to PE router lost, MPLS VPN route withdrawn
SD-WAN jitter threshold exceeded on backup path — voice quality degraded, MOS score dropped from 4.2 to 2.8, latency threshold breach at 48ms, packet loss 2.1%
Neural Engine Root Cause Analysis
The primary MPLS link at Branch-ATL has failed, causing the SD-WAN infrastructure to automatically failover to the broadband backup connection. While the failover mechanism is working as designed and the SD-WAN overlay tunnel has been re-established, the primary MPLS circuit remains down, creating a single point of failure. The 14 correlated incidents suggest this is likely affecting multiple services or endpoints that rely on this SD-WAN hub for connectivity.
Remediation Plan
1. Verify SD-WAN failover status and confirm broadband backup is stable 2. Contact MPLS service provider to report circuit outage and obtain estimated time to repair 3. Monitor broadband link utilization and performance to ensure adequate capacity 4. Implement traffic prioritization on backup link if bandwidth constraints exist 5. Coordinate with network team to assess if additional backup circuits need activation 6. Monitor all dependent services for performance degradation 7. Once MPLS is restored, verify automatic failback or manually restore primary path
Tested: 2026-03-30Monitors: 3 | Incidents: 3Test ID: cmncjdr5l00k6obqe9c6ou7we