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.3R2

Authentication and Access Control

  • Enhanced UAC authentication (SRX Series)— To regulate the lifespan (default 60 seconds) of event table entries, we've added a new configuration statement set services unified-access-control event-table-lifetime time interval in seconds . If there is a delay in authentication at the SRX Series device, use this configuration statement to enable UAC traffic after the user is authorized from the IC.

    [See Configuring Junos OS Enforcer Failover Options (CLI Procedure).]

General Routing

  • No support for PKI operational mode commands on the Junos Limited version (MX Series, PTX Series, and SRX Series devices)— We do not support request , show , and clear PKI-related operational commands on the limited encryption Junos image ("Junos Limited"). If you try to execute PKI operational commands on a limited encryption Junos image, then an appropriate error message is displayed. The pkid process does not run on Junos Limited version image. Hence, the limited version does not support any PKI-related operation.

J-Web

  • Changes to the Dashboard and Monitor pages (SRX Series)— To improve the J-Web UI loading speed: On the Dashboard page, we've removed the on-box reports related widgets. On the Monitor > Maps and Charts > Traffic Map page, we?ve changed the default duration from Last 1 hour" to Last "5 minutes."

Network Management and Monitoring

  • 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.

  • Changes when deactivating or deleting instances of the ephemeral configuration database (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—The following changes apply when you deactivate or delete ephemeral database instances in the static configuration database:

    • When you deactivate the entire [edit system configuration-database ephemeral] hierarchy level, the device deletes the files and corresponding configuration data for all user-defined ephemeral instances. In earlier releases, the files and configuration data are preserved; however, the configuration data is not merged with the static configuration database.

    • When you delete an ephemeral instance in the static configuration database, the instance's configuration files are also deleted. In earlier releases, the configuration files are preserved.

    • You can delete the files and corresponding configuration data for the default ephemeral database instance by configuring the delete-ephemeral-default statement in conjunction with the ignore-ephemeral-default statement at the [edit system configuration-database ephemeral] hierarchy level.

    [See Enable and Configure Instances of the Ephemeral Configuration Database.]