Multicast
Configuration > Networking > Routing > Multicast
Orchestrator supports multicast routing, a method of sending data from a single IP address to a larger group of recipients.
-
Up to 60 multicast routes are supported, including up to 30 (S,G) and 30 (*,G) groups.
-
Up to 1,000 sites can participate in the same multicast stream. HPE Networking recommends up to 200 sites.
-
All versions of IGMP are supported (IGMPv1, IGMPv2, and IGMPv3).
-
Multicast routing is supported in Inline Router mode only.
Multicast and Segments
In Orchestrator 9.7.1 and later, you can enable multicast on up to eight segments (VRFs) independently. This allows multicast traffic to operate within multiple isolated routing domains while maintaining end-to-end segmentation. Multicast routing between segments is not supported.
IMPORTANT: Multicast traffic is not routed between segments. Sources and receivers must reside within the same multicast-enabled segment (VRF). To support multicast in multiple segments, configure multicast independently for each segment.
-
Each multicast-enabled segment requires its own multicast configuration.
-
Each segment can use a different Rendezvous Point (RP) and Allowed Group configuration.
Before multicast can be enabled, a segment must be created and interfaces must be assigned to that segment.
TIP: Beginning with Orchestrator 9.7.0, the Multicast template enables you to configure multicast settings across multiple appliances. HPE Networking recommends using the template to ensure configuration consistency and simplify multicast deployments. See Multicast Template.
Multicast Configuration Workflow Overview
Deploying multicast in a multi-segment environment requires more than simply enabling multicast on an interface. Before multicast traffic can flow, you must create the required segments (VRFs), associate interfaces with those segments, configure a Rendezvous Point (RP), and enable multicast on the interfaces that will participate in multicast routing.
The following workflow provides a high-level overview of the recommended deployment process and helps illustrate the relationship between segments, interfaces, multicast configuration, and multicast routing.
Configuring multicast in a multi-segment environment typically involves the following tasks:
-
Configure segments.
- Define the required segments (VRFs).
- Assign LAN interfaces to the appropriate segments.
- Optionally, create multicast address groups that can be used to restrict multicast traffic.
-
Enable multicast on each segment.
- Enable multicast for the segment.
- Configure the Rendezvous Point (RP) IP address.
- Optionally, configure allowed multicast address groups.
-
Configure a Rendezvous Point (RP) for the segment.
- Optionally create a loopback interface to serve as the RP.
- Assign the RP IP address.
- For high-availability deployments, configure a secondary RP and the appropriate failover mechanism.
-
Associate interfaces with the multicast-enabled segment.
- Verify that the interface is bound to the correct segment (VRF).
- Add one or more LAN interfaces to the multicast-enabled segment.
- Enable Internet Group Management Protocol (IGMP) and Protocol Independent Multicast (PIM) as required.
- Configure any required PIM parameters.
-
Verify multicast operation.
- Verify IGMP group membership.
- Verify PIM neighbors.
- Verify multicast routes.
- Verify multicast traffic flows.
Multicast Tab Views
Orchestrator provides four views of multicast status, each accessible by one of the corresponding buttons at the top of the Multicast tab: Summary, Interfaces, Neighbors, and Routes.
Descriptions of fields on the Summary view follow:
| Field | Description |
|---|---|
| Appliance | Name of the appliance associated with the multicast configuration. |
| Enable | Indicates whether multicast is enabled. |
| Rendezvous Point IP | IP address of the Rendezvous Point (RP) used by PIM Sparse Mode. The RP acts as a meeting point for multicast sources and receivers during multicast tree enablement. |
| Allowed Group | Only addresses included in the specified multicast address group are allowed. If no address group is specified, any IP address can multicast. The message Feature is not supported for the appliance displays in this field if the appliance does not support the Allowed Group feature. |
Click the edit icon to enable or disable multicast, add an interface for multicast, or edit an existing interface.
Segment Filter
Use the Segment drop-down list at the top of the tab to filter the display by a specific segment. Select All Segments to view multicast data across all segments or select a specific segment to view only its multicast configuration.
For Orchestrator 9.7.1 and later, multicast information can be filtered by segment. Depending on the selected view, the information displayed reflects either all configured segments or the selected segment.
NOTE: For appliance versions 9.6.0.0 and earlier, only the Default segment is displayed.
Multicast Dialog Box
From the Summary, Interfaces, Neighbors, or Routes view on the Multicast tab:
-
Click the edit icon next to the appliance for which you want to set up multicast.
The Multicast dialog box opens.
-
Move the Enable multicast toggle to the right to enable multicast for this appliance with its SD-WAN fabric peers.
-
In the Rendezvous point IP address field, enter the appropriate IP address.
NOTE: When deploying an EdgeConnect appliance as the Rendezvous Point (RP), you can use a loopback interface address as the RP address. Using a loopback interface provides a stable RP address that remains available regardless of the state of individual physical interfaces.
IMPORTANT: Only static Rendezvous Point (RP) configurations are supported. Bootstrap Router (BSR) and Anycast RP configurations are not supported.
-
In the Allowed group field, select an available address group from the drop-down list or enter a new address group. All IP addresses included in the specified address group will be allowed to multicast. This field is not displayed if the appliance does not support the Allowed Group feature. Address group names can include alphanumeric characters, periods, underscores, or hyphens.
NOTE: Multicast cannot be enabled on more than eight segments. Attempting to do so will result in an error message.
IMPORTANT: The address group you specify in the Address Group field must be valid. If you enter a new address group, ensure that you also create and set it up on the Address Groups tab (Configuration > Templates & Policies > ACLs > Address Groups). If the new address group remains invalid, no IP addresses will be allowed to multicast.
Interfaces
| Field | Description |
|---|---|
| Interface | Name of the interface you want to connect. |
| PIM enabled | Indicates whether Protocol Independent Multicast (PIM) is enabled on the interface. When enabled, the interface can participate in multicast routing and exchange multicast routing information with neighboring routers. |
| IGMP enabled | Indicates whether Internet Group Management Protocol (IGMP) is enabled on the interface. When enabled, the interface can process multicast group membership messages from connected hosts and support multicast traffic delivery. |
| DR priority | Specifies the priority used during Designated Router (DR) elections. Interfaces with higher priority values are preferred when electing the DR. |
| DR router IP | Displays the IP address of the Designated Router (DR) elected for the multicast-enabled segment. |
| Actions | Hover to view available actions for this row (edit, delete, and so on). |
To add an interface:
-
Click Add.
The Add Interface dialog box opens.
-
Select the desired interface from the Interface drop-down list.
-
Select the Enable PIM check box if you want to enable it.
-
Select the Enable IGMP check box if you want to enable it.
-
In the DR priority field, specify the priority to use during Designated Router (DR) elections on the interface.
-
In the Hello interval field, select the number of seconds (1-300) for this interval. PIM messages are sent to the interface each time this interval is reached. The default value is 30.
-
In the Join / Prune interval field, select the number of seconds (30-180) that you want to send PIM messages to inform upstream routers about multicast group membership to join or prune interfaces. The default value is 30.
-
Click Done.
-
Click Save.
Neighbors
| Field | Description |
|---|---|
| Interface | Name of the interface associated with the multicast neighbor. |
| PIM enabled | Indicates whether the neighboring router is participating in Protocol Independent Multicast (PIM) on the selected interface. |
| IGMP enabled | Indicates whether Internet Group Management Protocol (IGMP) is enabled on the neighboring multicast interface. |
| DR priority | Determines the interface’s priority in Designated Router (DR) elections. Higher values increase the likelihood that the router will be elected as the DR. |
| DR router IP | IP address of the neighbor. |
Routes
| Field | Description |
|---|---|
| Source | Transmitter of the multicast data. |
| Segment | SD-WAN segment (VRF) for which multicast is enabled and managed. Multicast traffic remains within the selected segment. |
| Group | IP address of the multicast group. |
| Incoming interface/Peer | Interface that receives inbound traffic. |
| Outgoing interfaces/Peers | Interfaces or peers to which multicast traffic is forwarded. |
On the Multicast tab, you can click the Export CSV icon to export a spreadsheet of the multicast report. You can also click the refresh button to update information displayed on the tab.