Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?



  • We've added the following features to the MPC10E (MPC10E-15C-MRATE and MPC10E-10C-MRATE) and MPC11E (MX2K-MPC11E) in Junos OS Release 21.1.

    Table 1: Feature Support on MPC10E and MPC11E on MX Series Routers
    Feature Description
    • Configure inner source MAC address for flexible VXLAN tunnels—Use the Juniper Extension Toolkit (JET) RIB Service API to configure the source MAC address used in IPv4 and IPv6 flexible VXLAN tunnel encapsulation profiles. If you don’t specify a source MAC address, the default source MAC address 00:00:5e:00:52:01 is used to encapsulate IPv4 and IPv6 flexible VXLAN tunnels.

      [See Understanding Programmable Flexible VXLAN Tunnels and Juniper Extension Toolkit (JET).]

    • Support for auto-derived route targets on EVPN-MPLS.Junos OS supports the automatic derivation of route targets on EVPN-MPLS in an MPC10E line card on an MX Series router. When you enable the auto-derived route target feature, route targets are automatically derived from the VLAN ID for EVPN Type 2 and EVPN Type 3 routes and can be imported to the EVPN routing instance table.

      To enable the auto-derived route targets option, include the auto statement at the [edit routing-instances routing-instance-name protocols evpn vrf-target] hierarchy level.

      [See Auto-derived Route targets.]

    • Support for IPv4 unicast VXLAN encapsulation optimization on MPC10E and MPC11E line cards running on MX240, MX480, MX960, MX2008, MX2010, and MX2020 routers. By default, these routers optimize VXLAN-encapsulated throughput for IPv4 unicast packets that are 512 through 1500 bytes in size over the following VXLAN tunnel types:

      • PIM-based VXLAN

      • EVPN-VXLAN

      • Static VXLAN

      This feature doesn’t provide additional optimization over EVPN Type 5 tunnels (which are already optimized), and is not supported with forwarding table filters.

      [See Understanding VXLANs.]

    High availability (HA) andresiliency
    • MX Series Virtual Chassis (MX-VC) support for MPC10E-10C-MRATE and MPC10E-15C-MRATE (MX240, MX480, and MX960)— You can operate the MPC10E-10C-MRATE and MPC10E-15C-MRATE line cards in a router in an MX Series Virtual Chassis. The MPC10E support in MX-VC is only for uplink usage.

      [See Virtual Chassis Components Overview.]

    Juniper Extension Toolkit (JET)
    • Support for static backup paths with IP-in-IP tunnel encapsulation and provisioning APIs (MX240, MX480, MX960, MX2010 and MX2020)—We've enhanced Juniper Extension Toolkit (JET) APIs to enable a controller to set up underlay network backup paths that use IP-in-IP tunnels with IPv4 encapsulation.

      [See Juniper Extension Toolkit (JET).]

    Layer 2 features
    Port security
    • Support for Media Access Control Security (MACsec) on logical interfaces (MPC10E and MPC11E). VLAN tags are transmitted in clear text, which allows intermediate switches that are MACsec-unaware to switch the packets based on the VLAN tags.

      [See Media Access Control Security (MACsec) over WAN.]

    Services applications
    • Support for Mapping of Address and Port with Encapsulation (MAP-E) and inline 6rd (MPC10E and MX2K-MPC11E)— You can configure MAP-E and inline IPv6 rapid deployment (inline 6rd) on the following MPCs:

      • MPC10E-15C-MRATE and MPC10E-10C-MRATE on MX240, MX480, and MX960 routers

      • MX2K-MPC11E on MX2010 and MX2020 routers

      [See Configuring Mapping of Address and Port with Encapsulation (MAP-E) and Configuring Inline 6rd.]

    • Support for tunnel interfaces on the MPC10E line card—Junos OS supports three tunnel interfaces on the MPC10E line card: generic routing encapsulation (GRE) tunnel, logical tunnel (LT), and virtual tunnel (VT).

      • The GRE tunnel interface supports the tunnel statement with these options: destination, key, source, traffic-class and ttl. The copy-tos-to-outer-ip-header statement is also supported.

      • The LT interface supports the family inet, inet6, and iso options. The encapsulation statement supports the Ethernet and VLAN physical interface options only.

      • The VT interface supports the family inet option only.

      [See Tunnel Services Overview].

    • AMS support (MX240, MX480, MX960, MX2010, and MX2020 routers)—Junos OS supports aggregated multiservices (AMS) interfaces on the MPC10E and MX2K-MPC11E line cards to provide load balancing and high availability features for stateful firewall and NAT services. You can configure AMS interfaces with next-hop style service sets and with MS-MPC or MS-MIC only.

      [See Understanding Aggregated Multiservices Interfaces.]

    System management
    • Support for Synchronous Ethernet over link aggregation group interfaces (MX240, MX480, and MX960)—MPC10E line cards support Synchronous Ethernet over a link aggregation group (LAG).

      [See Synchronous Ethernet Overview.]

    • Support for PTP over Ethernet, hybrid mode, and G.8275.1 profile (MX240, MX480, and MX960)—MPC10E line cards support Precision Time Protocol (PTP) over Ethernet, G.8275.1 profile, and hybrid mode.

      [See Precison Time Protocol Overview and Understanding Hybrid Mode.]

    • Support for PTP over Ethernet and hybrid mode over link aggregation group interfaces (MX240, MX480, and MX960)— MPC10E line cards support Precision Time Protocol (PTP) over Ethernet and hybrid mode over a link aggregation group (LAG).

      [See Understanding Hybrid Mode and Precison Time Protocol Overview.]