Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Interfaces

  • Support for VLAN rewrite operations on CCC interfaces (MX480 and MX960)—Starting in Junos OS Release 21.2R1, you can configure VLAN rewrite operations on CCC interfaces.

    [See Configuring Q-in-Q Tunneling and VLAN Q-in-Q Tunneling and VLAN Translation.]

  • MRU support (SRX1500, SRX4100, SRX4200, SRX4600, SRX5400, SRX5600, and SRX5800)—Starting in Junos OS Release 21.2R1, you can configure maximum receive unit (MRU) size to accept packet sizes which are bigger than the configured MTU size and configure different values for both MTU and MRU to prevent frequent fragmentation and reassembly of larger packets on the receiving side. You can configure MRU on the xe, ge, et, and reth interfaces.

    Use the CLI command mru under the [edit interfaces name gigether-options] hierarchy level to configure the MRU size in bytes.

    [See mru.]

  • Flexible Ethernet support (QFX10002, QFX10008, and QFX10016)—Starting in Junos OS Release 21.2R1, you can configure flexible Ethernet services to support a Layer 2 bridging interface while simultaneously supporting other encapsulation options on the same physical interface. You can configure a physical or aggregate Ethernet interface to simultaneously support Layer 2 bridging, Layer 3 IP routing, and VLAN-based CCC connections.

    Note:

    On QFX10000 line of Switches running Junos OS releases earlier than Release 21.2R1, we do not support configuring vlan-bridge and any other encapsulations on an interface that has flexible-ethernet-services enabled.

    [See Flexible Ethernet Services Encapsulation.]

  • Support for coexistence of source IP hash with consistent hash (MX Series)—Starting in Junos OS Release 21.2R1, source IP hash, which allows the flow from a particular source IP to always be hashed to the same link while load-balancing the flows across multiple paths, supports consistent hash, which prevents the reordering of flows to active paths in an ECMP group when one or more paths fail.

    Note:

    This feature is applicable only to external BGP (EBGP) ECMP paths.

    [See Configuring Load Balancing Using Source or Destination IP Only and Configuring Consistent Load Balancing for ECMP Groups.]

  • AMS on MPC10E line card (MX240, MX480, and MX960 with MX-SPC3)—Starting in Junos OS Release 21.2R1, we support load balancing and high availability (HA) features on aggregated multiservices (AMS) interfaces for Layer 4 and Layer 7 services such as stateful firewall, intrusion detection service (IDS), and the Traffic Load Balancer (TLB) application.