VeloCloud SD-WAN Edge Multicast Configuration and Monitoring

Products

• VMware SD-WAN by VeloCloud

Issue/Introduction

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

Environment

VMware SD-WAN by VeloCloud

Resolution

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:

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

 

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

           

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

              
 

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

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

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