Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

ON THIS PAGE

Junos OS Release Notes for vMX

 

These release notes accompany Junos OS Release 20.4R3 for vMX. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.

You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located at https://www.juniper.net/documentation/product/en_US/junos-os.

What’s New

Learn about new features introduced in the Junos OS main and maintenance releases for vMX.

What's New in Release 20.4R3

There are no new features for vMX in Junos OS Release 20.4R3.

What's New in Release 20.4R2

There are no new features for vMX in Junos OS Release 20.4R2.

What's New in Release 20.4R1

EVPN

  • MC-LAG emulation in an EVPN deployment (EX Series, MX Series, and vMX)—Starting in Junos OS Release 20.4R1, you can emulate the function of an MC-LAG in active-standby mode in an EVPN configuration without having to configure an ICCP or ICL interface. In a standard EVPN configuration, logical interfaces configured on an aggregated Ethernet interface can have different designated forwarder election roles. To emulate an MC-LAG configuration, the designated forwarder (DF) takes on the role of the aggregated Ethernet interface. The provider edge (PE) that is the non-DF will send LACP out-of-sync packets to the CE. This causes LACP to go down on the CE device, and the CE device does not use the links connected to the non-DF for sending traffic. If the connection between a CE and a DF PE fails, the PE is re-elected as a DF. If the connection between a CE and a non-DF PE fails, the current DF PE is not changed.

    To enable this functionality, configure the lacp-oos-on-ndf statement at the [edit interfaces interface name esi df-election-granularity per-esi] hierarchy.

Juniper Extension Toolkit (JET)

  • Juniper Extension Toolkit (JET) support for 64-bit applications (MX5, MX10, MX40, MX80, MX104, MX150, MX204, MX240, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10008, MX ELM, JunosV Firefly, cSRX, SRX100, SRX110, SRX210, SRX220, SRX240, SRX300, SRX320, SRX340, SRX345, SRX550, SRX550HM, SRX650, SRX720E, SRX750E, SRX1400, SRX1500,SRX3400, SRX3600, SRX4100, SRX4200, SRX4400, SRX4600, SRX4800, SRX5400, SRX5600, SRX5800, SRX7X0E, SRX-ES7, SRX-ES8, VMX, and VSRX)—Starting in Junos OS Release 20.4R1, JET supports 64-bit applications. Use the following commands to compile 64-bit applications for use with the AMD64 or ARM64 64-bit processor architecture.

    • mk-amd64: Compiles the application for use with AMD64 and Junos OS with FreeBSD.

    • mk-amd64,bsdx: Compiles the application for use with AMD64 and Junos OS with upgraded FreeBSD.

    • mk-arm64,bsdx: Compiles the application for use with ARM64 and Junos OS with upgraded FreeBSD.

    [See Develop On-Device JET Applications.]

  • Configure inner source MAC address for flexible VXLAN tunnels (MX Series and vMX with MPC1-MPC9E or LC2101)—Starting in Junos OS Release 20.4R1, you can 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. The source MAC addresses is stored in the inner Ethernet header of VXLAN encapsulation. 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.

    Use the show route detail, show route extensive, and show flexible-tunnels profiles CLI commands or the get-route-information and get-flexible-tunnels-profiles RPC/NETCONF commands to view the source MAC address that is specified in the flexible tunnel profile.

    [See Understanding Programmable Flexible VXLAN Tunnels and JET APIs on Juniper EngNet.]

Junos OS XML ,API, and Scripting

  • Support for Certificate Authority Chain Profile (EX2300, EX3400, EX4300, MX240, MX480, MX960, PTX-5000, VMX, vSRX and QFX5200)—Starting in Junos OS Release 20.4R1, you can configure intermediate Certificate Authority (CA) chain profile certificate and perform https REST API request using mutual and server authentications.

    To configure intermediate ca-chain certificate, configure ca-chain ca-chain statement at the [edit system services rest https] hierarchy level.

Network Management and Monitoring

  • Configuration retrieval using the configuration revision identifier (EX3400, EX4300, MX204, MX240, MX480, MX960, MX2020, PTX3000, PTX10008, QFX5100, QFX10002-60C, SRX5800, vMX, and vSRX)—Starting in Junos OS Release 20.4R1, you can use the configuration revision identifier feature to view the configuration for a specific revision. This configuration database revision can be viewed with the CLI command show system configuration revision.

    [See show system configuration revision.]

  • Junos XML protocol operations support loading and comparing configurations using the configuration revision identifier (EX3400, EX4300, MX204, MX240, MX480, MX960, MX2020, PTX3000, PTX10008, QFX5100, QFX10002-60C, SRX5800, vMX, and vSRX)—Starting in Junos OS Release 20.4R1, the Junos XML management protocol operations support loading and comparing configurations by referencing the configuration revision identifier of a committed configuration. You can execute the <load-configuration> operation with the configuration-revision attribute to load the configuration with the given revision identifier into the candidate configuration. Additionally, you can compare the candidate or active configuration to a previously committed configuration by referencing the configuration revision identifier for the comparison configuration. The <get-configuration> operation supports the compare="configuration-revision" and configuration-revision attributes to perform the comparison.

    [See <get-configuration> and <load-configuration>.]

Routing Protocols

  • Support for multiple single-hop EBGP sessions on different links using the same IPv6 link-local address (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—Starting in Junos OS Release 20.4R1, you are no longer required to have unique peer addresses for Juniper devices for every EBGP session. You can now enable single-hop EBGP sessions on different links over multiple directly connected peers that use the same IPv6 link-local address.

    In earlier Junos OS Releases, BGP peers could be configured with link-local addresses, but multiple BGP peers could not be configured to use the same link-local address on different interfaces.

    [See Configure Multiple Single-Hop EBGP Sessions on Different Links Using the Same Link-Local Address (IPv6).]

What's Changed

Learn about what changed in the Junos OS main and maintenance releases for vMX.

What’s Changed in Release 20.4R3

Network Management and Monitoring

  • The configuration accepts only defined identity values for nodes of type identityref in YANG data models (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—If you configure a statement that has type identityref in the corresponding YANG data model, the device accepts only defined identity values (as defined by an identity statement) as valid input. In earlier releases, the device also accepts values that are not defined identity values.

Platform and Infrasturcture

  • We are discontinuing support for vMX on Microsoft Azure starting in Junos OS Release 18.1R1.

What’s Changed in Release 20.4R2

Junos OS XML API and Scripting

  • Refreshing scripts from an HTTPS server requires a certificate (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—When you refresh a local commit, event, op, SNMP, or Juniper Extension Toolkit (JET) script from an HTTPS server, you must specify the certificate (Root CA or self-signed) that the device uses to validate the server's certificate, thus ensuring that the server is authentic. In earlier releases, when you refresh scripts from an HTTPS server, the device does not perform certificate validation.

    When you refresh a script using the request system scripts refresh-from operational mode command, include the cert-file option and specify the certificate path. Before you refresh a script using the set refresh or set refresh-from configuration mode command, first configure the cert-file statement under the hierarchy level where you configure the script. The certificate must be in Privacy-Enhanced Mail (PEM) format.

    [See request system scripts refresh-from and cert-file.]

What’s Changed in Release 20.4R1

Licensing

  • Change in license bandwidth command on vMX virtual routers—Starting in Junos OS, to use the available license bandwidth, explicitly set the license bandwidth use the set chassis license bandwidth <In Mbps> command

    [See Configuring Licenses on vMX Virtual Routers.]

Known Limitations

Learn about known limitations in this release for vMX.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Platform and Infrastructure

  • The eODN feature supports up to 1K SRTE LSPs with 32K express segment links in TED. PR1561947

  • RPM is a Juniper Networks proprietary feature. In the case of Junos OS, the RPM client never set the DF bit. Hence, we don't see this issue between a Junos OS RPM client and a Junos OS RPM server. Whereas in the case of Junos OS Evolved, the RPM client is setting the DF bit while sending the RPM probes to RPM server. In case of Junos OS TVP-based platforms, the RPM server is not able to decode the DF bit properly. This causes an interwork failure between Junos OS Evolved as the RPM client and TVP platforms as the RPM server (and vice versa). This issue is not applicable for non-TVP-based Junos OS platforms acting as the RPM server. PR1508127

Open Issues

Learn about open issues in this release for vMX.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

General Routing

  • On vMX, the blockpointer in the ktree is getting corrupted leading to core-file generation. There is no function impact such as fpc restart or system down and the issue is not seen in hardware setups. PR1525594

Resolved Issues

Learn which issues were resolved in the Junos OS main and maintenance releases for vMX.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Resolved Issues: 20.4R3

Platform and Infrastructure

  • Communication between two CEs might be failed when BGP rib-sharding is enabled. PR1582210

  • Interface hold-time up does not work on vMX and MX150. PR1604554

  • In the VXLAN scenario, the locally originated packets have UDP source port 0. PR1571970

  • The l2ald process might crash on changing the routing-instance. PR1584737

  • Interwork failure between Junos OS Evolved as RPM client and TVP platforms as RPM server and vice versa. PR1508127

  • Traffic loss might be observed due to FPC crash on MX and vMX platforms. PR1563144

Resolved Issues: 20.4R2

General Routing

  • Multiple vmxt processes might generate core files. PR1534641

  • Configuring HFRR (link-protection) on an interface might cause the rpd process to crash. PR1555866

Resolved Issues: 20.4R1

Interfaces and Chassis

  • Random packet drop with flow cache disabled, when NIC mapped to NUMA node 1. PR1458742

  • On vMX instances, configuring the statement ranges for autosensed VLANs (either stacked VLANs or single-tag VLANs) might not work. This is because the VLANs are not programmed on the NIC drivers. PR1503538

  • After the peer is moved out of the protection group, the path protection is not removed from the PE device. Multipath route is still present. PR1538956

Network Management and Monitoring

  • After l2cpd service is restarted, the context of registration from l2cpd to snmpd was failing due to incorrect reinitialization. Because of this, if an NMS polls the dot1dStp objects by prefixing the context might fail. As a workaround, restart snmpd or reconfigure protocols hierarchy. PR1561736

Licensing

Starting in Junos OS Release 19.2R1, Juniper Agile Licensing introduces a new capability that significantly improves the ease of license management network wide. The Juniper Agile License Manager is a software application that runs on your network and provides an on-premise repository of licenses that are dynamically consumed by Juniper Networks devices and applications as required. Integration with Juniper's Entitlement Management System and Portal provides an intuitive extension of the existing user experience that enables you to manage all your licenses.

  • The Agile License Manager is a new option that provides more efficient management of licenses, but you can continue to use individual license keys for each device if required.

  • To use vMX or vBNG feature licenses in the Junos OS Release 19.2R1 version, you need new license keys. Previous license keys will continue to be supported for previous Junos OS releases, but for the Junos OS Release 19.2R1 and later you need to carry out a one-time migration of existing licenses. Contact Customer Care to exchange previous licenses. Note that you can choose to use individual license keys for each device, or to deploy Agile License Manager for more efficient management of licenses.

  • For more information about Agile Licensing keys and capabilities, see Juniper Agile Licensing portal FAQ.

See Juniper Agile Licensing Guide for more details on how to obtain, install, and use the License Manager.

Upgrade Instructions

You cannot upgrade Junos OS for the vMX router from earlier releases using the request system software add command.

You must deploy a new vMX instance using the downloaded software package.

Remember to prepare for upgrades with new license keys and/or deploying Agile License Manager.