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 in Junos OS Release 15.1R7 for the PTX Series.

High Availability (HA) and Resiliency

  • A check option is added for command request chassis routing-engine master (all platforms)—Starting in Junos OS Release 15.1, a check option available with the switch, release, and acquire options checks the GRES status of the standby Routing Engine before toggling mastership. The force option is also removed from all platforms.

    [See request chassis routing-engine master.]

  • GRES readiness is part of show system switchover output (PTX Series)—Starting in Junos OS Release 15.1, switchover readiness status is reported as part of the output for operational mode command show system switchover.

IPv6

  • IPv6 addresses with padded zeros in MIC or MS-MPC system log messages (PTX Series)—Starting with Junos OS Release 15.1R2, all system log messages originating from MIC or MS-MPC line cards display padded zeros in IPv6 addresses to make them compatible with MS-DPC line cards. Earlier, the system log messages from MIC or MS-MPC line cards displayed IPv6 addresses with ”::” instead of padded zeros.

Junos OS XML API and Scripting

  • Escaping of special XML characters required for request_login (PTX Series)—Beginning with Junos OS Release 15.1R2 , you must escape any special characters in the username and password elements of a request_login XML RPC request. The following five symbols are considered special characters: greater than (>), less than (<), single quote (’), double quote (“), and ampersand (&). Both entity references and character references are acceptable escape sequence formats. For example, &amp; and &#38; are valid representations of an ampersand. Previously no escaping of these characters was required.

Management

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

Network Management and Monitoring

  • Enhancement for SONET interval counter (PTX Series)—Starting with Junos OS Release 15.1R3, only the Current Day Interval Total output field in the show interfaces interval command for SONET interfaces is reset after 24 hours. In addition, the Previous Day Interval Total output field displays the last updated time in hh:mm.

    [See show interfaces interval.]

  • New 64-bit counter of octets for interfaces (PTX Series)—Starting with Release 15.1R3, Junos OS supports two new Juniper Networks enterprise-specific Interface MIB Extension objects—ifHCIn1SecOctets and ifHCOut1SecOctets—that act as 64-bit counters of octets passing through an interface.

  • Modified SNMP syslog messages (PTX Series)—In Junos OS Release 15.1R7, two misleading SNMP syslog messages have been rewritten to accurately describe the event:

    • Old message: AgentX master agent failed to respond to ping. Attempting to re-register

      New, corrected message: AgentX master agent failed to respond to ping, triggering cleanup!

    • Old message: NET-SNMP version %s AgentX subagent connected

      New, corrected message: NET-SNMP version %s AgentX subagent Open-Sent!

    [See the MIB Explorer.]

  • Juniper Networks MIBs loading errors fixed (PTX Series)—Starting with Junos OS Release 15.1R5, duplicated entries and errors while loading MIBs on the ManageEngine MIB browser are fixed for the following MIB files:

    • jnx-chas-defines.mib

    • jnx-gen-set.mib

    • jnx-ifotn.mib

    • jnx-optics.mib

    [See MIB Explorer.]

  • New context-oid option for trap-options configuration statement to distinguish the traps which come from a non-default routing instance and non-default logical system (PTX Series)—In Junos OS Release 15.1, a new option, context-oid, for the trap-options statement allows you to handle prefixes such as <routing-instance name>@<trap-group> or <logical-system name>/<routing-instance name>@<trap-group> as an additional varbind.

    [See trap-options.]

Routing Policy and Firewall Filters

  • Support for logical queue-depth in the Packet Forwarding Engine for IP options packets for a given protocol (PTX Series)— Starting with Junos OS Release 15.1R4, you can configure logical queue-depth in the Packet Forwarding Engine for IP options packets for a given protocol. The queue-depth indicates the number of IP options packets that can be enqueued in the Packet Forwarding Engine logical queue, beyond which it would start dropping the packets.

Routing Protocols

  • New IS-IS adjacency holddown CLI command (PTX Series)—Beginning with Junos OS Release 15.1, a new operational command, show isis adjacency holddown, is introduced to display the adjacency holddown status. This command is useful to verify whether the adjacency holddown is enabled and facilitates troubleshooting when there are adjacency issues due to IS-IS adjacency holddown.

    [See show isis adjacency holddown.]

  • Configure and establish targeted sessions with third-party controllers using LDP targeted neighbor (PTX Series)— Starting with Junos OS Release 15.1, you can configure LDP targeted neighbor to third-party controllers for applications such as route recorder that wants to learn label-FEC bindings of an LSR. LDP targeted neighbor helps to establish a targeted session with controllers for a variety of applications.

User Interface and Configuration

  • Changed available REST interface cipher suites when Junos OS is in FIPS mode (PTX Series)—Starting with Junos OS Release 15.1, when Junos OS is in FIPS mode, you can only configure cipher suites with a FIPS-compliant hash algorithm for the REST interface to the device. To configure a cipher suite, specify the cipher-list statement at the [edit system services rest] hierarchy level.

    [See cipher-list (REST API).]

  • New flag to control errors when executing multiple RPCs through a REST interface (PTX Series)—Starting with Junos OS Release 15.1, you can stop on an error when executing multiple RPCs through a REST interface by specifying the stop-on-error flag in the HTTP POST method.

    [See Submitting a POST Request to the REST API.]

  • New warning message for the configuration changes to extend-size (PTX Series)—Starting with Junos OS Release 15.1R2, any operation on the system configuration-database extend-size configuration statement such as deactivate, delete, or set, generates the following warning message:

    Change in 'system configuration-database extend-size' will be effective at next reboot only.