Re: WAN terminated on VLAN

TalalTayyaroğlu · ‎08-25-2023

Good day,

At a branch, I have configured the active 510 GE4 as DHCP client (routed port mode). This works (as expected) by bringing the Edge to the network and it shows up in Orchestrator.

The problem is in GE3: I have configured this port as switched trunk, and added two VLANs that I have already configured with static IP addresses, each representing a different WAN.

How can I add default gateways for each VLAN so it can communicate with the internet.

I added default routes as can be seen in the attached screenshot but will the Edge be able to identify which CLAN is connected with which route?

Also will it use it to build overlays?

After I have done this, the Edge still shows as having one link, meaning the VLANs did not register as WAN links.

Am I missing something here?

Just to confirm one thing, I can ping both VLAN IP addresses from outside.

This means the default routes worked.

However Orchestrator still shows the edge have only one link rather than 3

yusukehirata01 · ‎08-26-2023

Hi

Edge packets are processed by routing. In this case, it's a good idea to check the Edge's routing table.
Also, overlays cannot be enabled on switching ports. I think it would be good to set it to a routed port and configure a secondary interface.

Regard

TalalTayyaroğlu · ‎08-26-2023

Good day,

So if I configure it as a routed port (and assign the correct VLAN to it), and add a secondary interface (and add the correct VLAN to it), how do I program the opposite Cisco switch interface (switched)? in a trunk mode or what?

yusukehirata01 · ‎09-08-2023

Hi,

Is it the opposite port of Edge's GE3?
If you know GE3 to be a routed port,
I think the opposite port should also be routed.

Regard

TalalTayyaroğlu · ‎09-08-2023

The secondary IP addresses and sub-interfaces ended up not being the solution.

Here is the bottom line:

Switched Ports (like you mentioned before) do not support Overlay. They are used for LAN only.
In order to terminate multiple WAN links on a single interface, the interface must be routed, and, at the Edge level, multiple User-Defined WAN links must be created and then linked to that routed interface.

The exact method had been lost to me since the deprecation of the old GUI after the Orchestrator upgrade to SD-WAN software version 5.2.

Once I figure it out, I will publish a walkthrough

View solution in original post

khirom · ‎09-15-2023

Hi,

I think you should be careful with the default route "0.0.0.0/0".
VMware SD-WAN Edge has a default route when the interface gateway is configured.
If multiple Internet lines terminate to the VMware SD-WAN Edge, the route selection to the Internet is configured by business policy.
If the default route is obtained by static or dynamic routing, it is preferred.
Default routes obtained by static or dynamic routing can cause them to take precedence in many cases, causing unintended behavior.
This kb might be helpful.

Troubleshooting Unexpected Business Policy Behavior in VeloCloud SD-WAN (71317)
https://kb.vmware.com/s/article/71317

VMware SD-WAN switch ports are L2 switch access ports.
It is not available for cases where routing is desired.

This KB will help you understand the interface settings.

VMware SD-WAN by VeloCloud Interface Types and WAN Overlay (74846)
https://kb.vmware.com/s/article/74846?lang=en_us

If you want to set up an overlay using multiple VLANs on a single routing interface, the following description is helpful.

”2. Multiple Overlays Per Physical Interface”

If you set the WAN overlay setting to User defined instead of Auto,you should be able to set up a WAN overlay that uses multiple VLANs.