Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VMware SD-WAN Edge Configuration Changes That Can Trigger an Edge Service Restart (60247)

Last Updated: 12/1/2023Categories: InformationalTotal Views: 38910Language:
JapaneseEnglish

71 like this article

Subscribe to get an email
newsletter with new updates

71 people found this helpful Please provide article feedback:

Purpose

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.

Resolution

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 UI

Enterprise > 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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

VMware SD-WAN Edge Configuration Changes That Can Trigger an Edge Service Restart, December 2023

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware SD-WAN by VeloCloud

Take Our Survey

Support Assistant