Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Changes in Behavior and Syntax


This section lists the changes in behavior of Junos OS features and changes in the syntax of Junos OS statements and commands from Junos OS Release 17.1R2 for the QFX Series.


  • Representation for OSPF designated router node—Up until version -10 of the Internet Engineering Task Force (IETF) BGP-LS draft, the OSPF designated router node representation was ambiguous. One could represent designated router nodes as 'AdvertisingRouterId-InterfaceIpAddress' or 'InterfaceIpAddress-1'. Junos OS used to follow the 'InterfaceIpAddress-1' format. Starting with version -11 of the IETF BGP-LS draft, the representation for OSPF designated router node must be 'AdvertisingRouterId-InterfaceIpaddress'. Junos OS now follows the latest format.

Network Management and Monitoring

  • Cloud Analytics Engine disabled in Junos OS by default (QFX Series)—Starting in Junos OS Release 17.1R1 and later, Cloud Analytics Engine network analytics probe processing is disabled by default in Junos OS. Probe processing is enabled automatically when you configure any supported Cloud Analytics Engine configuration statement in the [edit system services cloud-analytics] configuration statement hierarchy. In Junos OS Release 16.1R3 and earlier, Cloud Analytics Engine Junos OS functionality is enabled by default, and no configuration steps are required for the Junos OS to process and respond to probes.

    [See Configuring Cloud Analytics Engine on Devices.]

Services Applications

  • Device discovery with device-initiated connection (QFX Series)—Starting in Junos OS Release 17.1R1 and later, when you configure statements and options under the [system services ssh] hierarchy and commit the configuration, make sure that the system reaches a stable state before you commit any outbound-ssh configurations.

    You use the device discovery feature in the Devices workspace to add devices to Junos Space Network Management Platform. By default, Junos Space manages devices by initiating and maintaining a connection to the device.

    [See Device Discovery Overview.]

Software Installation and Upgrade

  • In-service software upgrade (QFX5100 switches)—Unified ISSU is not supported from earlier Junos OS releases to Junos OS Release 17.1R1.

System Management

  • Peers option not supported in batch configuration mode— Starting in Junos OS Release 17.1R1, the peers option at the [edit system commit] hierarchy level is not supported in batch configuration mode.

User Interface and Configuration

  • Integers in configuration data in JSON format are displayed without quotation marks (QFX Series)—Starting in Junos OS Release 17.1R1, integers in Junos OS configuration data emitted in JavaScript Object Notation (JSON) format are not enclosed in quotation marks. Prior to Junos OS Release 17.1R1, integers in JSON configuration data were treated as strings and enclosed in quotation marks.

  • Changes to the show system schema module juniper-command output directory (QFX Series)—Starting in Junos OS Release 17.1, when you issue the show system schema module juniper-command operational command in the Junos OS CLI, the device places the generated output files in the current working directory, which defaults to the user’s home directory. Prior to Junos OS Release 17.1, the generated output files are placed in the /var/tmp directory.