104-SDWAN Lab
104-SDWAN Lab
Name the New SD-WAN Zone in this case SDWAN-ZONE and click OK to create.
New SD-WAN Zone are ready however, down there is no interface that’s why.
Set the Interface to WAN-1. Change the SD-WAN Zone to SDWAN-ZONE created earlier.
Set Gateway set to 192.168.1.254. Leave the Cost as 0. Leave the Priority to 1. Set Status to
Enable, and click OK.
Repeat the above steps for WAN-2, setting Gateway to the ISP's gateway: 192.168.2.254.
Let’s enable this command: diagnose sniffer packet any icmp 4 it is using both interfaces.
Also, can be verified from navigate to Log & Report > Forward Traffic.
If the traffic is from any source going to any destination besides, DNS:1.1.1.1 it will goto WAN-2.
Order of the rules matter first it will check if the traffic is destination to 1.1.1.1 will use WAN-1
Navigate to Log & Report > Forward Traffic. Here you can see if the traffic destination is
DNS:1.1.1.1 it used WAN-1 Link while for rest of traffic it used WAN-2 Link.
Let’s enable this command: diagnose sniffer packet any icmp 4 it is using both interfaces.
Enter a name for the SLA and select a protocol. In the Server field, enter the detection server IP
address 8.8.8.8 in this case. In the Participants field, select both wan1 and wan2 or All SD-WAN
Members. Enable SLA Targets and configure the setting as per your requirements. Configured
the remaining settings as needed, then click OK.
Go to Network > SD-WAN > SD-WAN Rules. Create a new SD-WAN rule. Name the rules in this
case SDWAN-Rule, set the source address to all, set the destination to all, set the protocol
number to ANY, leave the Internet Service and Application.
Let’s enable back WAN-2 again this time change the Delay, Jitter and Packet Loss.
To verify, the traffic is again diverted to WAN-1 Link because of Packet Loss, Latency and Jitter.