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

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 the show ethernet-switching vxlan-tunnel-end-point esi esi-identifier esi-identifier instance instance svlbnh command.

General Routing

  • Commit checks against incorrect configuration of SLC values (MX2020 and MX2010)—We have introduced commit checks against incorrect configuration of sub line cards (SLCs). While configuring SLCs, if you specify any incorrect values (for example, unsupported Packet Forwarding Engine ranges, CPU cores, or DRAM values), the configuration commit fails with an appropriate message to indicate the error.

    [See Configuring Sub Line Cards and Assigning Them to GNFs.]

  • Enhancement to the show chassis pic command (Junos|Evo)—You can now view additional information about the optics when you run the <cli>show chassis pic </cli> 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 &-8212; SFF-8472 (versions 9.3 - 12.3), QSFP+/QSFP28 & -8212; SFF 8363 (versions 1.3 - 2.10), and QSFP-DD &# -8212; 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 (Junos|Evo)—You can now view additional information about the MAC statistics when you run the show interfaces extensive ae command. The output now displays the following additional field: MAC statistics: Receive Transmit Broadcast packets 0 0 Multicast packets 0 0. Previously, the show interfaces extensive ae command did not display this additional field.

    [See show chassis pic.]

  • Enhanced response to URR query or remove request (MX Series)—When the control plane function sends a URR query or remove request, the Junos Multi-Access User Plane now sends the usage report in the modify response.

  • Support for multiple proxy-id list (MX5, MX10, MX40, MX80, MX104, MX240, MX480, MX960, MX2008, MX2010, and MX2020)—MX Series routers does not support ID list except for the following two cases:

    • MX Series routers accept any-any traffic selector in proxy-id list from the remote device that supports ID lists.

    • MX Series routers accept the ID list if list can be reduced by removing duplicates to specific ID. For example, reduce ID list having 80.0.0.1 and 80.0.0.0/24 to super set ID 80.0.0.0/24.

      list(any:0,ipv4(any:0-65535,0..3=80.0.0.1), ipv4_subnet(any:0-65535,0..7=80.0.0.0/24))

  • ISSU is not supported—Unified in-service software upgrade (ISSU) is not supported when clock synchronization is configured for Precision Time Protocol (PTP) and Synchronous Ethernet.

Junos XML API and Scripting

  • 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 (&#8212;) 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.]

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

  • 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 (ACX Series, EX Series, MX Series, PTX Series, QFX 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.

Subscriber Access Management

  • PPPoE Active Discovery Network (PADN) deprecation (MX Series)—We've deprecated the padn statement at the [edit access domain map domain-map-name] hierarchy level.