What’s Changed in Release 21.2R3
General Routing
-
Log messages are removed (MX Series)—When PTP Aggregate Ethernet primary is configured, and PTP Aggregate Ethernet secondary is not configured, the log message
Profiles are being modified
is removed. -
No support for PKI operational mode commands on the Junos Limited version (MX Series routers, PTX Series routers, and SRX Series devices)— We do not support
request
,show
, andclear
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. Thepkid
process does not run on Junos Limited version image. Hence, the limited version does not support any PKI-related operation.
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.
Layer 2 Ethernet Services
-
New output fields for subscriber management statistics (MX Series)—If you enable the enhanced subscriber management, the non-DHCPv4 bootstrap protocol (BOOTP) requests might not get processed even if you configure the DHCP relay or server with the
overrides bootp-support
statement at the [edit forwarding-options dhcp-relay
] hierarchy level. To monitor the DHCP transmit and receive packet counters, we've introduced the following output fields for theshow system subscriber-management statistics dhcp extensive
operational command. - BOOTP boot request packets received - BOOTP boot reply packets received - BOOTP boot request packets transmitted - BOOTP boot reply packets transmitted
Network Management and Monitoring
-
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 theignore-ephemeral-default
statement at the[edit system configuration-database ephemeral]
hierarchy level.
[See Enable and Configure Instances of the Ephemeral Configuration Database.]
-
- Changes to the NETCONF
<edit-config>
RPC response (ACX Series, EX Series, MX Series, PTX Series, QFX Series, SRX Series, vMX, and vSRX)—When the<edit-config>
operation returns an error, the NETCONF server does not emit a<load-error-count>
element in the RPC response. In earlier releases, the<edit-config>
RPC response includes the<load-error-count>
element when the operation fails.
Routing Protocols
-
To achieve consistency among resource paths, the resource path /mpls/signalling-protocols/segment-routing/aggregate-sid-counters/aggregate-sid-counterip-addr='address'/state/countersname='name'/out-pkts/ is changed to /mpls/signaling-protocols/segment-routing/aggregate-sid-counters/aggregate-sid-counterip-addr='address'/state/countersname='name'/. The leaf
out-pkts
is removed from the end of the path, andsignalling
is changed tosignaling
(with one "l").