Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?



  • Controller-based BGP multicast signaling (MX Series, PTX Series, and QFX Series)—Starting in Junos OS Release 21.1R1, we’ve introduced controller-based BGP multicast signaling that can be used instead of hop-by-hop signaling to program multicast forwarding states on routers. An external controller that is aware of the topology and network events within that topology calculates the optimum multicast trees between the source and receivers. The external controller then uses BGP signaling to send a new type of BGP network layer reachability information (NLRI) with modified attributes to convey the multicast state information to all the routers on the multicast trees.

    You can use this feature instead of multicast routing protocols, such as Protocol Independent Multicast (PIM) or multipoint LDP (MLDP). You can enable this feature using bgpmcast configuration option at the [edit protocols] hierarchy.

  • Support for next-generation multicast VPN (QFX10002, QFX10008, and QFX10016)—Starting in Junos OS Release 21.1R1, we support Multiprotocol BGP (MBGP) next-generation multicast VPNs with the following types of provider tunnels:

    • Ingress replication
    • RSVP-Traffic Engineering (RSVP-TE) point-to-multipoint (P2MP)
    • Multipoint LDP P2MP

    A P2MP is a Multiprotocol Label Switching (MPLS) label-switched path (LSP) with a single source and multiple destinations. By taking advantage of MPLS packet replication capability of the network, P2MP LSPs avoid unnecessary packet replication at the ingress router. Packet replication takes place only when packets are forwarded to two or more different destinations requiring different network paths.

    [See Multiprotocol BGP MVPNs Overview and provider-tunnel.]

  • MVPN live-live solution support (MX Series)—Starting in Junos OS Release 21.1R1, we’ve added support to enable the MVPN live-live feature in next-generation multicast VPN (MVPN) with multicast LDP point-to-multipoint (P2MP) provider tunnel. This feature helps to keep your network live all the time.

    To enable the MVPN live-live solution:

    • Configure the sender-based-rpf option by running the set routing-instances routing-instance-name protocols mvpn sender-based-rpf command. This option is disabled by default.
    • Configure the hot-root-standby option by running the set routing-instances routing-instance-name protocols mvpn hot-root-standby command. You can configure this option only if sender-based RPF is enabled.

    When you enable this configuration, the receiving PE automatically switches over to the backup path if it encounters any failure while forwarding the traffic from the primary path to the customer network. The transition from primary path to backup path happens in less than 50 milliseconds.

    For previous Junos OS releases, we provided support only for RSVP-TE and IR provider tunnels.

    [See sender-based-rpf and hot-root-standby.]