Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Changes in Default 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 16.2R1 for the ACX Series.

General Routing

  • Support for deletion of static routes when the BFD session goes down (ACX Series)—Starting with Junos OS 16.2R2, the default behavior of the static route at the [edit routing-options static static-route bfd-admin-down] hierarchy level is active. So, the static routes are deleted when the BFD receives a session down message.


  • Support for status deprecated statement in YANG modules (ACX Series)—Starting in Junos OS Release 16.1R2, Juniper Networks YANG modules include the status deprecated statement to indicate configuration statements, commands, and options that are deprecated.

Network Management and Monitoring

  • Possible change to the object identifier (ACX Series)—Starting in Junos OS Release 16.2R2, the many warnings that occurred previously during MIB loading in the SNMP client has been reduced. This update could change the resulting OID depending on the SNMP client-loading logic. For example, jnxProductACX1000 is defined under the two following nodes:

    • jnxProductACX1000 OBJECT IDENTIFIER ::= { jnxProductVariationACX 1 }

    • jnxProductACX1000 OBJECT IDENTIFIER ::= { jnxProductVariationACX1000 1 }

    Because the second definition is the duplicate, it is removed. Previously, the SNMP client referred to the second OID based on MIB loading logic and then you would see a change in OID for the client.

Platform and Infrastructure

  • Improvements to MIB validation during Junos OS build (libjsnmp) (ACX Series)—Many warnings can be ignored if produced while MIBs are compiling. The following warnings should be considered errors because they can break the build:

    [0-9]:.*failed to locateAn OID failed to be located.
    [0-9]:.*redefinition of identifierRedefinition of OIDs found in jnx-chas-defines.
    [0-9]:.*sequence-type-mismatchType mismatch found in sequence syntax of the table and actual OID type.
    [0-9]:.*cannot be imported from moduleMIB failed to import because order is not defined properly.

User Interface and Configuration

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

  • Changes to the XML and JSON output when displaying the differences between the candidate and active configurations (ACX Series)—Starting in Junos OS Release 16.2R2, when you compare the candidate and active configurations and display the differences in XML or JSON format, for example by using the show | compare | display (json | xml) CLI command or the <get-configuration compare="rollback" format="(json | xml)"> RPC, the device omits the <configuration> tag in the XML output and omits the configuration object in the JSON output if the comparison either returns no differences or if the comparison returns differences for only non-native configuration data, for example, configuration data associated with an OpenConfig data model.