deterministic-ar-policy
Syntax
deterministic-ar-policy [ deterministic-ar-policy-name ... ];
Hierarchy Level
[edit routing-instances name protocols evpn assisted-replication leaf]
Description
Assign routing policies to an EVPN instance on an assisted replication (AR) leaf device to deterministically steer multicast flows to specific preferred AR replicator devices. With this feature, you can control how the leaf device load-balances multicast flows among the available AR replicator devices, rather than using the default load-balancing method on the device.
AR is a multicast traffic flow optimization feature where an ingress leaf device sends one copy of a multicast stream to another device called an AR replicator in the EVPN network. AR replicators are devices that can efficiently handle replicating and forwarding multicast streams to the other multicast receivers in the network. See Assisted Replication Multicast Optimization in EVPN Networks for details on how AR works and how to configure AR leaf and AR replicator devices.
We support setting deterministic AR replicator policies only in EVPN-VXLAN networks running AR with optimized intersubnet multicast (OISM).
You can define and assign AR replicator routing policies as follows:
-
You can include match conditions for IPv4 or IPv6 multicast traffic with IGMP or MLD multicast groups.
With IGMPv2 (IPv4) or MLDv1 (IPv6) multicast traffic, you can match a multicast flow for a multicast group and/or a bridge domain (a VLAN-mapped virtual network identifier [VNI]).
With IGMPv3 (IPv4) or MLDv2 (IPv6 traffic), you can match a multicast flow for any combination of the following:
-
A multicast group
-
A bridge domain (a VLAN-mapped VNI)
-
A multicast source address, because these are source-specific multicast (SSM) protocols.
-
-
You can configure the policy in either of the following modes—these options are mutually exclusive:
-
Strict mode—Include the
strict
option to strictly direct matching flows only to the preferred AR replicator. If that AR replicator goes down, the AR leaf device drops any matching flows even if the device detects other available AR replicators in the network. When the preferred AR replicator comes back up again, the AR leaf resumes sending matching traffic to that AR replicator. -
Loose mode—The default mode. You can optionally include a fallback AR replicator to use if the preferred AR replicator goes down. If the fallback AR replicator is also down or you don't specify a fallback, but the AR leaf device detects other AR replicators in the network, the device uses its default AR replicator load balancing method to distribute flows among the available other AR replicators. (See Default AR Leaf Load-Balancing When Detecting Multiple AR Replicators.)
If the AR leaf device doesn't detect any available AR replicators in the network, the device defaults to ingress replication (replicates and forwards the multicast flows itself to the other devices with receivers interested in those flows).
-
Options
deterministic-ar-policy-name |
Routing policy name that deterministically directs matching multicast flows to specified AR replicators. You set deterministic AR routing policy conditions to match multicast flows in
the You set the policy action in the The policy action must include the |
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Evolved Release 23.4R2.