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 18.3R1 for MX Series routers.

Interfaces and Chassis

  • On MX Series routers with the RE-S-X6-64G and RE-MX2K-X8-64G Routing Engines, when the user changes the router configuration on a live system, or when the user deletes an interface that has active traffic, the message select: protocol failure in circuit setup is randomly displayed. However, there is no known functional impact.

Junos FIPs

  • In Junos OS Release 18.3R1, on MX Series Routers, if you attempt to configure XPN cipher suite (gcm-aes-xpn-128 or gcm-aes-xpn-256) for a connectivity association and attach the connectivity association to an interface on the PIC that does not support XPN cipher suite, then during runtime, a syslog is logged as below (and default non-xpn cipher suite is used):

    macsec_ciphersuite_is_supported MACSec: ifd ifd_id (ifd_name), Cipher suite cipher id (cipher name) NOT SUPPORTED.

Junos OS XML, API, and Scripting

  • MD5 and SHA-1 hashing algorithms are no longer supported for script checksums (MX Series)—Starting in Junos OS Release 18.3R1, Junos OS does not support configuring an MD5 or SHA-1 checksum hash to verify the integrity of local commit, event, op, SNMP, or Juniper Extension Toolkit (JET) scripts or support using an MD5 or SHA-1 checksum hash with the op url url key option to verify the integrity of remote op scripts.

MPLS

  • When the no-interface-hello statement is configured under the [edit protocols rsvp] hierarchy, and there is no interface-specific configuration for the hello interval, the show rsvp interface detail command output displayed the default HelloInterval of 9 seconds.

    Starting in Junos OS Release 18.3R1, with a similar configuration, the HelloInterval output field displays 0 as the hello interval.

  • Change in get-pm-mpls-lsp-information tag—Starting in Junos OS Release 18.3R1, the show performance-monitoring mpls lsp command output in the YANG module is changed to match the root XML tag for get-pm-mpls-lsp-information. The tag change is from performance-monitor-mpls-lsp-information to pm-information.

  • Change in get-egress-protection-information tag—Starting in Junos OS Release 18.3R1, the show mpls egress-protection command output in the YANG module is changed to match the root XML tag for get-egress-protection-information. The tag change is from egress-protection-information to ep-operational-information.

  • Bandwidth allocation—For a label-swtiched path (LSP) that has both bandwidth and minimum-bandwidth for autobandwidth configured under the [edit protocols mpls label-switched-path lsp-name] hierarchy level, the LSP bandwidth is adjusted differently.

    The LSP is initiated with the bandwidth value configured under the bandwidth statement at the [edit protocols mpls label-switched-path lsp-name] hierarchy level. At the expiry of the adjust-interval timer, the LSP bandwidth gets adjusted based on the traffic flow.

    If the bandwidth to be signaled is less than the value configured under the minimum-bandwidth statement at the [edit protocols mpls label-switched-path lsp-name autobandwidth] hierarchy level, then the LSP is signaled only using the minimum bandwidth.

    If the bandwidth to be signaled is greater than the value configured under the maximum-bandwidth statement at the [edit protocols mpls label-switched-path lsp-name autobandwidth] hierarchy level, then the LSP is signaled only using the maximum bandwidth.

  • Change in command syntax—Starting in Junos OS Release 18.3R1, the show ldp database label-requests command name is changed to show ldp database-label-requests with no change to command functionality.

Network Management and Monitoring

  • Junos OS does not support managing YANG packages in configuration mode (MX Series)—Starting in Junos OS Release 18.3R1, Junos OS does not support adding, deleting, or updating YANG packages using the run command in configuration mode.

Routing Protocols

  • IS-IS adjacency SID routes retained only when backup path is available—Starting in Junos OS Release 18.3R1, when an IS-IS link flaps the adjacency SID routes are retained in the RIB, (also known as the routing table) and the FIB, (also known as the forwarding table) only if a backup path is available. In earlier Junos OS releases, adjacency SID routes were retained in the RIB and FIB even when a backup path was not available.

Software Installation and Upgrade

  • ZTP is supported on MX PPC platforms (MX Series)—As of Junos OS Release 17.2R3, zero touch provisioning (ZTP) is supported on MX PPC platforms (which are MX5, MX10, MX40, MX80, and MX104 routers). Before the fix, the ZTP process did not start to load image and configuration for MX PPC routers.

    [See Junos OS Installation Package Names.]

Subscriber Management and Services

  • DHCPv6 lease renewal for separate IA renew requests (MX Series)—Starting in Junos OS Release 18.3R1, the jdhcpd process handles the second renew request differently in the situation where the DHCPv6 client CPE device does both of the following:

    • Initiates negotiation for both the IA_NA and IA_PD address types in a single solicit message.

    • Sends separate lease renew requests for the IA_NA and the IA_PD and the renew requests are received back-to-back.

    The new behavior is as follows:

    1. When the reply is received for the first renew request, if a renew request is pending for the second address type, the client stays in the renewing state, the lease is extended for the first IA, and the client entry is updated.

    2. When the reply is received for the second renew request, the lease is extended for the second IA and the client entry is updated again.

    In earlier releases:

    1. The client transitions to the bound state instead of staying in the renewing state. The lease is extended for the first IA and the client entry is updated.

    2. When the reply is received for the second renew request, the lease is not renewed for the second address type and the reply is forwarded to the client. Consequently, when that lease ages out, the binding for that address type is cleared, the access route is removed, and subsequent traffic is dropped for that address or address prefix.

    [See Using DHCPv6 IA_NA with DHCPv6 Prefix Delegation Overview.]

  • Disabling a pseudowire underlying interface (MX Series)—You cannot disable the underlying logical tunnel (lt) interface or redundant logical tunnel (rlt) interface when a pseudowire is anchored on that interface. If you want to disable the underlying interface, you must first deactivate the pseudowire.

    [See Configuring a Pseudowire Subscriber Logical Interface Device.]

  • Bandwidth options match for inline services and tunnel services (MX Series)—Starting in Junos OS Release 18.3R1, you can configure the same bandwidth options for inline services with the bandwidth statement at the [edit chassis fpc slot-number pic number inline-services hierarchy level as you can configure for tunnel services with the bandwidth statement at the [edit chassis fpc slot-number pic number tunnel-services] hierarchy level.

    [See bandwidth (Inline Services) and bandwidth (Tunnel Services)]

VPNs

  • Output of show l2vpn connections extensive command in XML—Starting in Junos OS Release 18.3R1, the output for show l2vpn connections extensive | display xml will correctly display the output in XML.