Specifications

you no longer have to configure a tunnel profile on the LAC. In earlier releases, tunnel
switching failed when you did not also configure the LAC, even when the RADIUS
attributes were present.
User Interface and Configuration
User-defined identifiers using the reserved prefix junos- now correctly cause a commit
error in the CLI (M Series, MX Series, and T Series)Junos OS reserves the prefix
junos- for the identifiers of configurations defined within the junos-defaults configuration
group. User-defined identifiers cannot start with the string junos-. If you configured
user-defined identifiers using the reserved prefix through a NETCONF or Junos XML
protocol session, the commit correctly fails. Prior to Junos OS Release 13.3, if you
configured user-defined identifiers through the CLI using the reserved prefix, the commit
incorrectly succeeded. Junos OS Release 13.3 and later releases exhibit the correct
behavior. Configurations that currently contain the reserved prefix for user-defined
identifiers other than junos-defaults configuration group identifiers will now correctly
result in a commit error in the CLI.
Change in show version command output (M Series, MX Series, and T
Series)—Beginning in Junos OS Release 13.3, the show version command output includes
the new Junos field that displays the Junos OS version running on the device. This new
field is in addition to the list of installed sub-packages running on the device that also
display the Junos OS version number of those sub-packages. This field provides a
consistent means of identifying the Junos OS version, rather than extracting that
information from the list of installed subpackages.
In Junos OS Release 13.2 and earlier, the show version command does not have the
single Junos field in the output that displays the Junos OS version running on the device.
The only way to determine the Junos OS version running on the device is to review the
list of installed subpackages.
Junos OS Release 13.3 and Later Releases With the Junos
Field
Junos OS Release 13.2 and Earlier Releases Without the
Junos Field
user@host> show version
Hostname: lab
Model: mx960
Junos: 13.3R1.4
JUNOS Base OS boot [13.3R1.4]
JUNOS Base OS Software Suite [13.3R1.4]
JUNOS Kernel Software Suite [13.3R1.4]
JUNOS Crypto Software Suite [13.3R1.4]
...
user@host> show version
Hostname: lab
Model: mx960
JUNOS Base OS boot [12.2R2.4]
JUNOS Base OS Software Suite [12.2R2.4]
JUNOS Kernel Software Suite [12.2R2.4]
JUNOS Crypto Software Suite [12.2R2.4]
...
[See show version.]
Configuring regular expressions (M Series, MX Series, and T Series)—In all supported
Junos OS releases, regular expressions can no longer be configured if they require more
than 64 MB of memory or more than 256 recursions for parsing.
This change in the behavior of Junos OS is in line with the FreeBSD limit. The change
was made in response to a known consumption vulnerability that allows an attacker
to cause a denial of service (resource exhaustion) attack by using regular expressions
67Copyright © 2015, Juniper Networks, Inc.
Changes in Behavior and Syntax