Chapter 35: SD-WAN
This chapter follows the topics shown in the Networking chapter menu. Work through each section in order, then use the review questions to check recall and troubleshooting reasoning.
35.1 SD-WAN Overview
SD-WAN uses centralized policy and an overlay to steer application traffic across multiple WAN transports according to availability, latency, loss, jitter, and business intent.
Example: place SD-WAN Overview in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
35.2 WAN Underlay
WAN Underlay is one of the core topics in SD-WAN. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place WAN Underlay in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
35.3 WAN Overlay
WAN Overlay is one of the core topics in SD-WAN. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place WAN Overlay in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
35.4 Centralized Policy
Centralized Policy is one of the core topics in SD-WAN. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Centralized Policy in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
35.5 Multiple WAN Circuits
Multiple WAN Circuits is one of the core topics in SD-WAN. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Multiple WAN Circuits in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
35.6 Application-Aware Routing
Application-Aware Routing affects how Layer 3 devices choose a path toward destination networks. Correct routing depends on the destination prefix, route source, next hop or exit interface, route preference, metric, and reachability of the next step.
Example: a router receives a packet for 10.20.30.40 and has several matching routes. It selects the most specific matching prefix, then forwards toward the route's next hop or exit interface if that path is usable.
What to check
- Check the destination prefix and the most-specific matching route.
- Verify next-hop reachability, route source, preference, metric, and return path.
- Confirm that ACLs, NAT, VPN policy, or upstream routing are not blocking an otherwise-correct route.
35.7 Dynamic Path Selection
PAT lets many inside hosts share one or a small number of public IPv4 addresses by tracking transport protocol and port mappings.
Example: place Dynamic Path Selection in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
35.8 Latency Monitoring
Latency is the time required for traffic to travel between endpoints. Propagation, serialization, queueing, processing, and path choice can all contribute.
Example: place Latency Monitoring in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Confirm the symptom and determine whether the problem affects one host, one segment, one site, or many sites.
- Compare actual configuration and measurements with the intended design, baseline, or documentation.
- Change one variable at a time, verify the result, and document both the cause and the final fix.
35.9 Jitter Monitoring
Jitter is variation in packet delay. Real-time voice and video are especially sensitive to excessive delay variation.
Example: place Jitter Monitoring in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Confirm the symptom and determine whether the problem affects one host, one segment, one site, or many sites.
- Compare actual configuration and measurements with the intended design, baseline, or documentation.
- Change one variable at a time, verify the result, and document both the cause and the final fix.
35.10 Packet-Loss Monitoring
Packet-Loss Monitoring is one of the core topics in SD-WAN. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Packet-Loss Monitoring in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Confirm the symptom and determine whether the problem affects one host, one segment, one site, or many sites.
- Compare actual configuration and measurements with the intended design, baseline, or documentation.
- Change one variable at a time, verify the result, and document both the cause and the final fix.
35.11 SLA-Based Path Selection
PAT lets many inside hosts share one or a small number of public IPv4 addresses by tracking transport protocol and port mappings.
Example: place SLA-Based Path Selection in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
35.12 Encryption
Encryption is one of the core topics in SD-WAN. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Encryption in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
35.13 Branch Connectivity
Branch Connectivity is one of the core topics in SD-WAN. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Branch Connectivity in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
35.14 Local Internet Breakout
Local Internet Breakout is one of the core topics in SD-WAN. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Local Internet Breakout in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
35.15 Failover
Failover is one of the core topics in SD-WAN. Understand what the term represents, where it operates in the network, what information it uses, and what observable behavior confirms that it is working correctly.
Example: place Failover in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
35.16 SD-WAN Controllers
SD-WAN uses centralized policy and an overlay to steer application traffic across multiple WAN transports according to availability, latency, loss, jitter, and business intent.
Example: place SD-WAN Controllers in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
35.17 SD-WAN Security
SD-WAN uses centralized policy and an overlay to steer application traffic across multiple WAN transports according to availability, latency, loss, jitter, and business intent.
Example: place SD-WAN Security in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify the trust boundary and the traffic that should be permitted or denied.
- Check authentication, authorization, encryption, policy order, logs, and time synchronization.
- Verify the control with an allowed test and a denied test so policy behavior is observable.
35.18 SD-WAN Advantages
SD-WAN uses centralized policy and an overlay to steer application traffic across multiple WAN transports according to availability, latency, loss, jitter, and business intent.
Example: place SD-WAN Advantages in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
35.19 SD-WAN Limitations
SD-WAN uses centralized policy and an overlay to steer application traffic across multiple WAN transports according to availability, latency, loss, jitter, and business intent.
Example: place SD-WAN Limitations in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Identify which OSI/TCP-IP layer and device type are primarily responsible.
- Check configuration, interface or service state, counters, logs, and a simple end-to-end test.
- Verify both normal operation and one realistic failure case so you understand what changes when the feature breaks.
35.20 SD-WAN Troubleshooting
SD-WAN uses centralized policy and an overlay to steer application traffic across multiple WAN transports according to availability, latency, loss, jitter, and business intent.
Example: place SD-WAN Troubleshooting in a small office network containing clients, switches, a router, wireless access, DNS/DHCP services, and an internet connection. Identify which device or layer owns the function and what evidence you would inspect to verify it.
What to check
- Confirm the symptom and determine whether the problem affects one host, one segment, one site, or many sites.
- Compare actual configuration and measurements with the intended design, baseline, or documentation.
- Change one variable at a time, verify the result, and document both the cause and the final fix.