Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

What’s Changed in Release 21.3R1

Class of Service (CoS)

  • On a Layer 2 interface, use unit * to apply a classifier or rewrite rule to all of the logical units on that interface.

EVPN

  • Support for displaying SVLBNH information—You can now view shared VXLAN load balancing next hop (SVLBNH) information when you display the VXLAN tunnel endpoint information for a specified ESI and routing instance by using show ethernet-switching vxlan-tunnel-end-point esi esi-identifier esi-identifier instance instance svlbnh command.

  • Community information no longer included in VRF routing table—The QFX series switches will no longer include the inherited advertised route target communities, EVPN extended communities, or vxlan encapsulation communities for EVPN Type 2 and EVPN Type 5 routes when an IP host is added in the VRF routing table.

  • Support for Maximum Response Time in EVPN Type 8 Routes—Junos OS now supports the Maximum Response Time (MRT) attribute field in EVPN Type 8 Route messages. This attribute is defined in the IETF draft of IGMP and MLD Proxy for EVPN, version 13. MRT is used to synchronize the wait time before responding to IGMP messages. To maintain compatibility with devices running previous versions of Junos OS that do not support MRT, set protocols evpn leave-sync-route-oldstyle.

    [See evpn.]

  • Ethernet tag ID set to 0 for EVPN Type 6 and EVPN Type 7 routes—For VLAN bundle and VLAN-based services, Junos OS now automatically sets the Ethernet tag ID (VLAN ID) to zero for EVPN Type 6 and EVPN Type 7 routes per RFC 7432. In earlier releases, Junos OS used the VXLAN Network Identifier (VNI) as the Ethernet tag ID. To interoperate with devices that uses the VNI as the Ethernet tag ID, set routing-instances routing-instance-name protocols evpn smet-etag-carry-vid.

  • Output for show Ethernet switching flood extensive—The output for show ethernet-switching flood extensive now displays the correct next-hop type for Virtual Ethernet and WAN mesh group in an EVPN-VXLAN network as unilist. Previously, the output for show ethernet-switching flood extensive would misidentify the next-hop type as composite.

General Routing

  • Juniper Agile Licensing (QFX5200-32C) Starting from this release onwards, the QFX Series switch supports following features ?

    • Standard: BFD, Filters (Layer 2 and Layer 3), Layer 2 (xSTP, 802.1Q, LAG), Layer 3 (static), QoS (Layer 2 and Layer 3), and SNMP

    • Advanced 1: Standard features, BGP, IS-IS, FBF, VRRP, MC-LAG, Layer 3 (static), GRE tunnel, OSPF, RIP, sFlow, and Virtual Chassis

    • Advanced 2: Advanced 1 features, CFM, Q-in-Q, VXLAN, PCEP, ESI-LAG, Timing, Ethernet OAM, EVPN-VXLAN, IGMP version 1, IGMP version 2, and IGMP version 3, PIM, and Multicast Listener Discovery (MLD) version 1 or version 2

    • Premium: Advanced 2 features, Layer 3 VPN, LDP, RSVP, Layer 2 circuit, EVPN-MPLS, Segment routing, MPLS, and MACsec

    See Flex Software License for QFX Series Switches and

  • Juniper Agile Licensing (EX2300-VC, EX3400-VC, EX4300-VC, EX4400-24MP, EX4400-48MP, PTX10003, PTX10016, QFX5130-32CD, QFX5110-32Q, QFX5110-48S, QFX5120-48T, QFX5210-64C, QFX5200, and QFX5220)—Starting from this release onwards, the Juniper Agile License Manager is deprecated. You can use the Juniper Agile Licensing Portal to activate, install, manage, and monitor licenses on Juniper Networks devices.

    [See Juniper Agile Licensing Guide.]

Interfaces and Chassis

  • When configuring multiple flexible tunnel interface (FTI) tunnels, the source and destination address pair needs to be unique only among the FTI tunnels of the same tunnel encapsulation type. Prior to this PR, the source and destination address pair had to be unique among all the FTI tunnels regardless of the tunnel encapsulation type.

Junos XML API and Scripting

  • Changes to how command-line arguments are passed to Python op scripts (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—When the device passes command-line arguments to a Python op script, it prefixes a hyphen (-) to single-character argument names, and it prefixes two hyphens (--) to multi-character argument names. The prefix enables you to use standard command-line parsing libraries to handle the arguments. In earlier releases, the device prefixes a single hyphen (-) to all argument names.

    [See Declaring and Using Command-Line Arguments in Op Scripts.]

Layer 2 Ethernet Services

  • Link selection support for DHCP—We have introduced the link-selection statement at the [edit forwarding-options dhcp-relay relay-option-82] hierarchy level, which allows DHCP relay to add suboption 5 to option 82. Suboption 5 allows DHCP proxy clients and relay agents to request an IP address for a specific subnet from a specific IP address range and scope. Prior to this release, the DHCP relay dropped packets during the renewal DHCP process and the DHCP server used the leaf's address as a destination to acknowledge the DHCP renewal message.

    [See relay-option-82.]

Network Management and Monitoring

  • Changes to how command-line arguments are passed to Python action scripts (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—When a custom YANG RPC invokes a Python action script and passes command-line arguments to the script, the device prefixes a hyphen (-) to single-character argument names, and it prefixes two hyphens (--) to multi-character argument names. The prefix enables you to use standard command-line parsing libraries to handle the arguments. In earlier releases, the device passes the unmodified argument names to the script.

    [See Creating Action Scripts for YANG RPCs on Devices Running Junos OS and Displaying Valid Command Option and Configuration Statement Values in the CLI for Custom YANG Modules.]

  • Enhancement to the snmp mib walk command (PTX Series, QFX Series, EX Series, MX Series, SRX Series)— The ipv6IfOperStatus field displays the current operational state of the interface. The noIfIdentifier(3) state indicates that no valid Interface Identifier is assigned to the interface. This state usually indicates that the link-local interface address failed Duplicate Address Detection. When you specify the 'Duplicate Address Detected' error flag on the interface, the new value (noIfIdentifier(3)) is displayed. Previously, the snmp mib walk command did not display the new value (noIfIdIdentifier(3)).

  • Changes in contextEngineID for SNMPv3 INFORMS (PTX Series, QFX Series, ACX Series, EX Series, MX Series, and SRX Series)—Now the contextEngineID of SNMPv3 INFORMS is set to the local engine-id of Junos devices. In earlier releases, the contextEngineID of SNMPv3 INFORMS was set to remote engine-id.

    [See SNMP MIBs and Traps Supported by Junos OS.]

  • Change in behavior of SNMP MIB object ifAlias—SNMP MIB object ifAlias now shows the configured interface alias. In earlier releases, ifAlias used to show configured interface description.

Platform and Infrastructure

  • Enhancement to the show chassis pic command—You can now view additional information about the optics when you run the show chassis pic command. The output now displays the following additional field:

    MSA Version: Multi-source Agreements (MSA) version that the specified optics is compliant to. Values supported are: SFP+/SFP28 -- SFF-8472 (versions 9.3 - 12.3), QSFP+/QSFP28 -- SFF 8363 (versions 1.3 - 2.10), and QSFP-DD -- CMIS 3.0, 4.0, 5.0.

    Previously, the show chassis pic command did not display this additional field.

    [See show chassis pic.]

  • Enhancement to the show interfaces (Aggregated Ethernet) command (ACX Series, PTX Series, and QFX Series)—When you run the show interfaces extensive command for Aggregated Ethernet interfaces. You can now view following additional fields for MAC statistics : Receive, Transmit, Broadcast and Multicast packets.

    [See show chassis pic.]