Crazy about VMware SD-WAN

 I recently installed Version 5.0.0.0 on one of my SD-WAN environments and there is some new information regarding  Route Table Dump NOTE: the last 2 (new) columns are only displayed when using the NEW UI, not when started from the old JS UI Beside some small changes regarding Type :Connected and Next Hop: LO1 or LO2 for loopback interfaces a new field has been added called (Not) Reachable Reason It displays the reason for the route being reachable or not reachable and here are the different possible Reason Codes Unfortunately still there is no available list of Lost Reason Codes available which is quite important to detect why a route is preferred or depreferred towards another route So here you find available Reason Codes and its explanation: SNO Reason code EDGEs Description 1 LR_NO_ELECTION Best route. 2 LR_NP_SWAN_VS_VELO Predecessor won because it is a non-preferred static WAN route (route configured with preferr...

As already described in my Blog regarding  Lost OFC Routes  https://sd-wahn.blogspot.com/2022/01/where-have-all-ofc-routes-gone-or-my.html there were considerable routing behaviour changes starting with version 3.4.0 Excerpt from VMware SD-WAN Operator Guide Version 4.5 Configure Distributed Cost Calculation By default, the Orchestrator is actively involved in learning the dynamic routes. VMware SD-WAN Edges and Gateways rely on the Orchestrator to calculate initial route preferences and return them to the Edge and Gateway. The Distributed Cost Calculation feature enables you to distribute the route cost calculation to the Edges and Gateways. Note: Enabling Distributed Cost Calculation is recommended for all customers. This default method of involving the Orchestrator in both dynamic route calculation and the distribution of those routes to Edges and Gateways has drawbacks of significant higher route convergence time ...