When a new link is added, the following verification steps should have already been conducted:
Tested the speed of the new link.
Ensured a valid IP address is used (if it is an Internet link then go to www.whatsmyip.org, or other similar sites).
Next, work through the layers to troubleshoot this issue.
Verify the Ethernet settings by going to Configuration > Appliance Setting > Network Adaptors > Ethernet tab.
As shown in the following screenshot, the interfaces are set to auto-negotiate. It will indicate what the ports have negotiated. Configured ports 1/1 and 1/3 have negotiated to 100Mb/Full, while port 1/2 has negotiated to 1000Mb/Full. If a connected port has been hard-coded to 100/Full and SD-WAN Virtual WAN has been set for auto-negotiate, you might see 100Mb/Half. The ports are operating in half-duplex because of duplex mismatch and can reduce performance and hence must be resolved immediately.
Go to Monitoring > Statistics > under Show, select Ethernet from the drop-down list. Verify if there are any interface errors.
Examine the interface settings on all applicable external devices (switch, firewall/router).
Go to Monitoring > Statistics > under Show, select ARP from the drop-down list. Verify if there is an ARP entry for each Gateway and also verify if the ARP entry is on the correct interface. Verify the gateway IP address from the configuration file or from Configuration > Virtual WAN > View Configuration > under View, select WAN links from the drop-down list.
In the following example, a gateway for the DEAD path is 220.127.116.11. The gateway is not responding because there is no MAC address in the table and the State column reports “REPLY_PENDING.”
The next step is to capture packet traces at both the appliances (MCN and Client). Prior to taking a packet trace, you will have to understand what IP address is in the frame. A description of an Intranet versus Internet follows:
The IP addressing of the frame is going to be SD-WAN Virtual WAN MCN-VIP <–> Client VIP.
Review Configuration > Virtual WAN > View Configuration > under View, select Paths from the drop-down to identify the IP addressing for the MPLS path.
The Internet path can be defined as a public IP address or as behind a NAT device. If defined behind a NAT device, the SD-WAN Virtual WAN configuration can be defined with either a static IP address or in a learning mode. In learning mode, the MCN will learn what public IP address the Client uses. In either case, the user should know what IP and public IP’s are before collecting the packet capture. The MCN must be statically defined so that the public IP address will be in the SD-WAN Virtual WAN configuration file. The Client static IP address is defined in the configuration file.
For learned IP address on the MCN, review Monitoring > Statistics > under Show, select WAN link from the drop-down. This page will show the learned IP address for the clients in the network. If there is no entry for the client, verify if the SD-WAN Virtual WAN configuration is defined for learning mode and the Client SD-WAN Virtual WAN is sending frames for this WAN link.
Go to Configuration > System Maintenance > Diagnostics > Packet Capture tab and ensure that the correct interface is selected. Determine this from the ARP entry for the WAN Link gateway which provides the port that the gateway was learnt on.
Ensure that the traffic is being sourced from each appliance with the correct source and destination IP address. Verify router, NAT statements and/or port-forwarding rules. If there is a misconfigured NAT statement, both appliances will source the packets to the proper destination. At the site with the misconfigured NAT statement, however, the traceroute will likely fail after the first hop.
If the SD-WAN Virtual WAN is connected to a switch prior to the router/firewall, ensure VLAN settings are correct. If access to routers is available, perform ping and traceroute on the path to ensure IP addresses are reachable.