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 17.2R2 for the PTX Series.

Forwarding and Sampling

  • In Junos OS Release 17.2R2, and later, the SelectorID field (element id: 302) is sent instead of the Bytes field (element id: 1) in the system scope of version-ipfix Option template records for all PTX Series Routers. All other elements of the template remain the same.

General Routing

  • Support for deletion of static routes when the BFD session goes down (PTX Series)—Starting with Junos OS 17.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.

Interfaces and Chassis

  • Value of sysObjectID now displays jnxProductNamePTX1000 (PTX1000)—Starting in Junos OS Release 17.2R1, the value of sysObjectID is now displayed as jnxProductNamePTX1000 instead of jnxProductPTX1000 (which is an incorrect value), as shown in the following example:

    The sysObjectID value is updated to jnxProductNamePTX1000 to maintain synchronization across devices (or routers) belonging to the PTX Series.

  • Change in command outputs after a health check failure (PTX5000)—Starting in Junos OS Release 17.2R1, when a health check fail for a PSM is detected on a PTX5000 router, until a system reboot or restart chassisd occurs, the following changes are displayed in the command outputs:

    • The output of the show chassis environment pdu displays the reason for the health check fail and the following information:

    • The status of the PSM which failed the health check is set to offline and the output of show chassis alarms command displays the following existing alarm:

    After a system reboot or restart chassisd, the router checks the PSM register 0x1D bit-0:

    • The output of the show chassis environment pdu displays the reason for the health check fail and the following information for the PSM:

  • Restart FPC option supported on PTX1000 router—In Junos OS Release 17.2R2, you can reboot the FPC gracefully using request chassis fpc restart slot slot-number command on a PTX1000 router. Note that request chassis fpc (online|offline) slot slot-number command is not supported, which means only restart option is supported, but online and offline options are not supported. See [request chassis fpc.]

Management

  • Junos OS YANG module namespace and prefix changes (PTX Series)—Starting in Junos OS Release 17.2, Junos OS YANG modules are specific to a device family, and each module’s namespace includes the module name, device family, and Junos OS release string. Furthermore, each juniper-command module uses its own unique module name as the module’s prefix. In earlier releases, Junos OS YANG modules used only a unique identifier to differentiate the namespace for each module, and the prefix for all juniper-command modules was jrpc.

    Device families include junos, junos-es, junos-ex, and junos-qfx. The Junos OS YANG extension modules, junos-extension and junos-extension-odl, use the junos device family identifier in the namespace, but the modules are common to all device families.

    [See Understanding Junos OS YANG Modules.]

  • Changes to the rfc-compliant configuration statement (PTX Series)—Starting in Junos OS Release 17.2R1, Junos OS YANG modules are specific to a device family, and each module’s namespace includes the module name, device family, and Junos OS release string. If you configure the rfc-compliant statement at the [edit system services netconf] hierarchy level and request configuration data in a NETCONF session on a device running Junos OS Release 17.2R1 or later, the NETCONF server sets the default namespace for the <configuration> element in the RPC reply to the same namespace as in the corresponding YANG model.

    [See Configuring RFC-Compliant NETCONF Sessions and rfc-compliant.]

  • Enhancement to the Junos Telemetry Interface (PTX Series)—Starting with Junos OS Release 17.2R1, the values displayed in the oper-status key-value field of data streamed through gRPC for the physical interfaces sensor have changed.

    The following values are now displayed to indicate the operational status of an interface:

    • operational status up—UP

    • operational status down—DOWN

    • operational status unknown—UNKNOWN

  • Enhancement to NPU memory sensors for Junos Telemetry Interface (PTX Series)—Starting with Junos OS Release 17.2R1, the path used to subscribe to telemetry data for network processing unit (NPU) memory and NPU memory utilization through gRPC has changed. The new path is /components/component[name="FPC<fpc-id>:NPU<npu-id>"]/

    [See Guidelines for gRPC Sensors.]

Network Management and Monitoring

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

    • OLD - AgentX master agent failed to respond to ping. Attempting to re-register

      NEW - AgentX master agent failed to respond to ping, triggering cleanup!

    • OLD - NET-SNMP version %s AgentX subagent connected

      NEW - NET-SNMP version %s AgentX subagent Open-Sent!

    [See the MIB Explorer.]

Routing Protocols

  • Syslog error message RPD_ISIS_PREFIX_SID_CNFLCT to resolve conflicting prefix segment advertisement (PTX Series)—Starting in Junos OS Release 17.2R2, the RPD_ISIS_PREFIX_SID_CNFLCT syslog error message is emitted only when the prefix segment advertisement from the remote node is conflicting with an advertisement from the self node. This conflict happens because the same prefix segment index is assigned on different IP addresses or different prefix segment indexes are assigned to the same IP address. To rectify this conflict, identify the remote node in the network originating the conflicting prefix segment advertisement and change the prefix segment index on the local node or on the remote node.

    [See Example: Configuring Anycast and Prefix Segments in SPRING for ISIS.]