Crazy about VMware SD-WAN

In this first part we look into   History Flow Table Gateway Routing and BGP Table  Firewall Logs on VCO Part 2 will follow with information on troubleshooting using the Edge CLI History Flow Table for Private Segments only a summary will be displayed (see last line in above screenshot) NOTE: the actual flow table can still be gathered via Remote Diagnostics Gateway Routing Table and BGP Routes     After the 2 minutes the VCO closes the connection to the gateway   Firewall Logs on VCO       Again here on all my 2 VCOs the same 400 error appears, it seems that there is an unknown conversion to run, as the firewall log uses a newer clickhouse database now instead of the standard mysql. Unfortunately up to now, none of my contacts at VMware could help me, as i assume that there is a conversion script needed for that feature. Next blog will have a look into Toubleshooting using the Edge CLI, stay tuned...

Around 2 months ago when doing a Speedtest check of my links I experienced a substancial reduction of measured UPlink and DOWNlink speed. As I only have a single link to the Internet using Cable Modem connectivity which is a shared linktype, after some retries I assumed the problem to be at the Service Provider and some congestion there. I contacted the Service Provider but he assured me, that this is not the case. Then I found the real "culprit". It was my VMware SD WAN Edge which drastically reduced the bandwidth sent out via the Overlay. When checking the Edge I found out that the last measured Bandwidth was around 40/10 instead of 180/40 Mbps.   I was quite unsure about that measured  bandwidth and found out that according to this VMware knowledge base article ... ... on wired links the bandwidth test is only done when there is a Link Up event or after 7 days . So what seemed have happened was, that the last bandwidth measurement took place at a time, where due to s...