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

VeloCloud SD-WAN Edge Multicast Configuration and Monitoring (71223)

Last Updated: 8/12/2019Categories: InformationalTotal Views: 8603Language:
Chinese (Simplified)JapaneseEnglish

13 like this article

Subscribe to get an email
newsletter with new updates

13 people found this helpful Please provide article feedback:

Details

This article covers configuring and monitoring Multicast for the VeloCloud SD-WAN Edge

Solution

There are many applications and services which transport data by using multicast over a WAN. This article covers the configuration and monitoring of the Multicast feature in VeloCloud SD-WAN.

This figure illustrates how IP multicast is used to deliver data from one source to interested recipients

Multicast support in VeloCloud SD-WAN includes:

Multicast support on both overlay and underlay

Protocol-Independent Multicast - Sparse Mode (PIM-SM) on VCE

Internet Group Management Protocol (IGMP) version 2 on VCE

Static Rendezvous Point (RP) configuration, where RP is enabled on a 3rd party router.

Multicast is supported only on the global segment

Multicast is not supported between dynamic E2E tunnels

Configuration

Let's use the topology below for the Multicast configuration:

Configure Multicast on the Hub Edge as shown below. Statically configure the RP address and add the Multicast Group of interest.

Enable IGMP and PIM on the Interface connected to the RP.  There is no requirement to enable IGMP or PIM on the WAN interfaces used for Overlays. In this example, we are using the GE3 and GE4 interfaces for Overlays and the GE5 interface is connected to the RP and configured with PIM as shown below.

A Branch Edge multicast configuration is as below. In this example, the Branch is interested in subscribing only to multicast group address 226.0.0.1

Configure IGMP & PIM on the interface connected to the Receiver. In this example, we are using VLAN 1 on the Branch Edge.

Note: IGMP and PIM must both be enabled on the interfaces connected to the receiver.
Multicast will not work if you enable only IGMP on the Edge interface as IGMP needs PIM to be configured.

Ensure that the RP and Multicast Source are reachable from the Hub and Branch Edges. This may be verified by checking the Edge routing table via Remote Diagnostics  ->  Route Table Dump.

Monitoring

Multicast traffic is monitored on the Orchestrator under the Monitor -> Routing page.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
请求批量导出失败并显示错误：“创建导出时出错: 值不能为 null。参数名称: stringToEscape (An error occurred while creating export: Value cannot be null. Parameter name: stringToEscape)” (71263)

KB
•
如何使用 dbms_scheduler 程序启用/禁用在 Oracle 数据库中调度的作业 (71154)

KB
•
cloud-init を使用してカスタマイズされた仮想マシンが再起動後に DHCP に設定される (71264)

Results 1-3 of 3

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