OPERATIONAL DEFECT DATABASE
...
...
Updated December, 2023 The December, 2023 revision impacts changes involving routed interface configurations. Previously these actions were listed as not causing an Edge Service restart beginning with Version 5.1.0. This was incorrect. Only switched interfaces were fixed in that regard and routed interface configuration changes remain subject to an Edge Service restart through Release 5.4.0. The update also removes Edge versions that are End of Service Life: 3.4.x and 4.0.x, and adds 5.2.0 and 5.4.0. This KB article covers the VMware SD-WAN Edge configuration changes which can cause an Edge dataplane service restart, also known as the edged process. Edged is one of many services that run on an Edge and this service handles dataplane tasks, i.e. managing customer traffic.A restart of the edged service is not the same as a full Edge hardware reboot. Restarting this software process does cause a brief interruption in service and customer traffic will be disrupted until this dataplane service resumes.The configuration changes seen below are made using the VMware SD-WAN Orchestrator UI.The tables in this article are not searchable, but you may download a PDF version of these tables with fully searchable text.
Device Settings This section covers changes made to the Device settings for either a VMware SD-WAN Edge or a configuration Profile. These changes are made on the Orchestrator under: Configure > Edge/Profile > Device using the Classic UIEnterprise > SD-WAN > Configure > Edge/Profile > Device using the New UI (default for 5.2.0 and later Orchestrators). For Edges in a High Availability topology, the Edge service restart will cause an HA failover.A PDF version of all these tables with fully searchable text is also available for download.Note: If a Profile configuration change is made and an Edge using that profile already has an Edge Override configured for that particular Device setting, the Edge will not be affected by the Profile level configuration change. Business Policy This applies for both Edge and Profile level changes to Business Policies on the Configure > Business Policy page of the Orchestrator. For Edges in a High Availability topology, the Edge service restart will cause an HA failover.A PDF version of all these tables with fully searchable text is also available for download.Note: If a Profile business policy change is made and an Edge using that profile already has a matching, Edge-specific business policy configured, the Edge will not be affected by the Profile level business policy change as the Edge business policy overrides a matching Policy business policy. Business Policy: IPv4 Only Business Policy: IPv6 Only Business Policy: IPv4/IPv6 Dual Stack (Mixed Mode) Firewall This applies for both Edge and Profile level changes to setting found on the Configure > Firewall page. Changes include Firewall rules, 1:1 NAT rules, and Port-Forwarding rules. For Edges in a High Availability topology, the Edge service restart will cause an HA failover.A PDF version of all these tables with fully searchable text is also available for download.Note: If a Profile rule change is made and an Edge using that profile already has a matching, Edge-specific rule configured, the Edge will not be affected by the Profile level rule change as the Edge rule overrides a matching Policy rule. Firewall Rules: IPv4 Only Firewall Rules: IPv6 Only Firewall Rules: IPv4/IPv6 Dual Stack (Mixed Use) Segments This section covers changes made to the Segments page of the Orchestrator.For Edges in a High Availability topology, the Edge service restart will cause an HA failover. Overlay Flow Control (OFC) This section covers configuration changes made to the Overlay Flow Control (OFC) page of the Orchestrator.For Edges in a High Availability topology, the Edge service restart will cause an HA failover. Network Services This section covers changes made to the Network Services page of the Orchestrator.For Edges in a High Availability topology, the Edge service restart will cause an HA failover.
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
