Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Junos OS Release Notes for PTX Series Packet Transport Routers

 

These release notes accompany Junos OS Release 18.3R3 for the PTX Series. They describe new and changed features, limitations, and known and resolved problems in the hardware and software.

You can also find these release notes on the Juniper Networks Junos OS Documentation webpage, located at https://www.juniper.net/documentation/product/en_US/junos-os.

New and Changed Features

This section describes the new features and enhancements to existing features in the Junos OS main release and the maintenance releases for PTX Series.

Release 18.3R3 New and Changed Features

There are no new features or enhancements in Junos OS Release 18.3R3 for the PTX Series.

Release 18.3R2 New and Changed Features

MPLS

  • Control transport address used for targeted-LDP session (PTX Series)—Currently, only the router-ID or interface address is used as the LDP transport address. Starting in Junos OS Release 18.3R2, you can configure any other IP address as the transport address of targeted LDP sessions, session-groups, and interfaces. This new configuration is applicable only for configured LDP neighbors that have Layer 2 circuit, MPLS, and VPLS adjacencies.

    This feature is beneficial when you have multiple loopback interface addresses, and different IGPs associated with LDP interfaces, and you can control the session established between targeted LDP neighbors with the configured transport address.

    [See Control Transport Address Used for Targeted-LDP Session.]

Release 18.3R1 New and Changed Features

Hardware

  • PTX10K-LC1104 DWDM line card on PTX10016 routers—Starting in Junos OS Release 18.3R1, the PTX10016 Packet Transport Router supports the PTX10K-LC1104 DWDM line card. The PTX10K-LC1104 DWDM line card provides packet forwarding speed up to 1.2 Tbps for cloud providers, service providers, and enterprises that need coherent dense wavelength-division multiplexing (DWDM) with MACsec security features. The six-port line card, with built-in optics, supports flexible rate modulation at 100-Gbps, 150-Gbps, and 200-Gbps speeds. The PTX10016 routers support a maximum of four PTX10K-LC1104 line cards.

    [See PTX10K-LC1104 Line Card.

Authentication, Authorization, and Accounting (AAA) (RADIUS)

  • Support for password change policy enhancement (PTX Series)—Starting in Junos OS Release 18.3R1, the Junos password change policy for local user accounts is enhanced to comply with certain additional password policies. As part of the policy improvement, you can configure the following:

    • minimum-character-changes—The number of characters by which the new password should be different from the existing password.

    • minimum-reuse—The number of older passwords, which should not match the new password.

    [See password]

Class of Service

  • Support for classification override (PTX Series)—Starting with Junos OS 18.3R1, PTX Series devices support overriding the input classification of traffic streams, whether the input classification is the default forwarding class or some other forwarding class set by an input filter, assigning the streams to a different forwarding class by defining a policy class and referencing this class when configuring a routing policy. To override the input classification, configure the classification-override forwarding-class class-name statement at the [edit class-of-service forwarding-policy class class-name] hierarchy level.

    [See Overriding the Input Classification.]

  • RED drop and tail drop differentiation (PTX Series)—Starting in Junos OS Release 18.2X75-D10 and Junos OS Release 18.3R1, PTX Series devices display traffic drops through tail drop counters unless there is an explicit RED drop profile configured. With a RED drop profile configured, traffic drops are reported under a RED drop counter. This configuration helps to differentiate between RED drop and tail drop scenarios.

    [See show interfaces queue.]

Interfaces and Chassis

  • Support for PTX10K-LC1104 coherent line card (PTX10008 and PTX10016)—Starting with Junos OS Release 18.3R1, PTX10008 and PTX10016 routers support the PTX10K-LC1104 coherent DWDM line card. The following are some of the software features supported by this line card:

    • Compliance with ITU G.709 and ITU G.798

    • Performance-monitoring features such as alarms, threshold-crossing alarms, OTU/ODU error seconds, and FEC and bit error rate (BER) statistics

    • SNMP management of the MIC based on RFC 3591

    • IEEE 802.1ag OAM

    • IEEE 802.3ah OAM

    • IFINFO/IFMON

    • IEEE 802.3ad link aggregation

    • Flexible Ethernet services encapsulation

    • Flexible VLAN tagging

    • Source address MAC accounting per logical interface

    • Source address MAC filter per port

    • Source address MAC filter per logical interface

    • Destination address MAC filter per port

    • Up to 8000 logical interfaces shared across all ports on a single Packet Forwarding Engine

    See Understanding the PTX10K-LC1104 Line Card.

  • Support for BGP Monitoring Protocol on a nondefault management instance (PTX Series)—Starting in Junos OS Release 18.3R1, the BGP Monitoring Protocol (BMP) can send monitoring packets to BMP monitoring stations that are reachable through a VRF table. This feature can be used with the management-instance configuration statement to create the routing instance mgmt-junos for BMP to move through. Previously, BMP could send monitoring packets to a BMP monitoring station that could be looked up only using the default (inet.0 or inet6.0) routing table.

    [See Configuring BGP Monitoring Protocol to Run Over a Different Routing Instance.]

Junos Telemetry Interface

  • Support for the Junos Telemetry Interface (ACX6360, MX Series, and PTX Series)—Starting with Junos OS Release 18.3R1, Junos Telemetry Interface support is available for the ACX6360 Universal Metro Router and MX Series and PTX Series routers with a CFP2-DCO optics module that provides a high-density, long-haul optical transport network (OTN) transport solution with MAC capability.

    You can provision sensors to export telemetry data to an outside collector.

    The following native (UDP) and gRPC sensors can be provisioned for 100-Gigabit Ethernet interfaces and OTN interfaces:

    • /junos/system/linecard/optical

    • /junos/system/linecard/otn

    To provision the sensor to export data through gRPC, use the telemetrySubcribe RPC to specify telemetry parameters. For streaming through UDP, all parameters are configured at the [edit services analytics] hierarchy level. Streaming telemetry data through gRPC also requires you to download the OpenConfig for Junos OS module.

    [See sensor (Junos Telemetry Interface), Configuring a Junos Telemetry Interface Sensor (CLI Procedure), and Guidelines for gRPC Sensors (Junos Telemetry Interface).]

  • Expanded physical interface queue and traffic statistics sensors for Junos Telemetry Interface (JTI) (PTX, MX, EX, QFX, ACX)—Starting with Junos OS Release 18.3R1, additional resource paths are added to stream physical (IFD) statistics.

    Prior to Junos OS Release 18.3R1, both traffic and queue statistics for physical interfaces (IFD) are sent out together using the resource path /interfaces for gRPC streaming (which is internally used to create /junos/system/linecard/interface/) or /junos/system/linecard/interface/ for UDP (native) sensors.

    Now, traffic and queue statistics can be delivered separately. Doing so can reduce the reap time for non-queue data for platforms supporting Virtual Output Queues (VOQ).

    The following UDP resource paths can be configured:

    • /junos/system/linecard/interface/ is the existing resource path (no change). Traffic and queue statistics are sent together.

    • /junos/system/linecard/interface/traffic/ exports all fields except queue statistics.

    • /junos/system/linecard/interface/queue/ exports queue statistics.

    The gRPC resource path /interfaces now has the following behavior:

    • In releases prior to Junos OS 18.3R1, it delivers all IFD traffic and queue statistics. In Junos OS 18.3R1 and higher, it delivers statistics in two sensors:

      • /junos/system/linecard/interface/traffic/ exports all fields except queue statistics.

      • /junos/system/linecard/interface/queue/ exports queue statistics.

    To provision the sensor to export data through gRPC, use the telemetrySubcribe RPC to specify telemetry parameters. For streaming through UDP, all parameters are configured at the [edit services analytics] hierarchy level. Streaming telemetry data through gRPC also requires the OpenConfig for Junos OS module. Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundled into the Junos OS image by default. Both packages support the Junos Telemetry Interface (JTI).

    [See sensor (Junos Telemetry Interface), Configuring a Junos Telemetry Interface Sensor (CLI Procedure), and Guidelines for gRPC Sensors (Junos Telemetry Interface).]

    For exporting statistics using UDP native sensors, configure parameters at the [edit services analytics] hierarchy level.

  • Expanded ON_CHANGE support for LLDP telemetry data through Junos Telemetry Interface (JTI) (MX Series and PTX Series)—Starting with Junos OS Release 18.3R1, OpenConfig support through remote procedure calls (gRPC) and JTI is expanded to support additional ON-CHANGE support for LLDP telemetry sensors. Periodical streaming of OpenConfig operational states and counters collects information at regular intervals. ON_CHANGE support streams operational states as events (only when there is a change), and is preferred over periodic streaming for time-sensitive missions.

    When you create a subscription using a top-level container as the resource path (for example, /lldp), leaves under the resource path /lldp with ON_CHANGE support are automatically streamed based on events. Other leaves will not be streamed.

    These paths, previously supporting periodical streaming only, now also support ON_CHANGE streaming:

    • /lldp/state/enabled

    • /lldp/state/chassis-id

    • /lldp/state/chassis-id-type

    • /lldp/state/system-name

    • /lldp/state/system-description

    • /lldp/state/hello-timer

    • /lldp/interfaces/interface/state/name

    • /lldp/interfaces/interface/state/enabled

    • /lldp/interfaces/interface/neighbors/neighbor/state/chassis-id

    • /lldp/interfaces/interface/neighbors/neighbor/state/chassis-id-type

    • /lldp/interfaces/interface/neighbors/neighbor/state/port-id

    • /lldp/interfaces/interface/neighbors/neighbor/state/port-id-type

    • /lldp/interfaces/interface/neighbors/neighbor/state/port-description

    • /lldp/interfaces/interface/neighbors/neighbor/state/system-name

    • /lldp/interfaces/interface/neighbors/neighbor/state/system-description

    • /lldp/interfaces/interface/neighbors/neighbor/state/management-address

    • /lldp/interfaces/interface/neighbors/neighbor/state/management-address-type

    • /lldp/interfaces/interface/neighbors/neighbor/capabilities

    These resource paths from the above list do not change with an event, but will be streamed on creation and deletion:

    • /lldp/interfaces/interface/neighbors/neighbor/state/chassis-id

    • /lldp/interfaces/interface/neighbors/neighbor/state/chassis-id-type

    • /lldp/interfaces/interface/neighbors/neighbor/state/system-name

    Before events are streamed, there is an initial stream of states to the collector, followed by an END_OF_INITIAL_SYNC notice. This notice signals the start of event streaming.

    To provision the sensor to export data through gRPC streaming, use the telemetry Subscribe RPC to specify telemetry parameters. Streaming telemetry data through gRPC also requires you to download the OpenConfig for Junos OS module.

    [See Configuring a Junos Telemetry Interface Sensor (CLI Procedure) and Guidelines for gRPC Sensors (Junos Telemetry Interface).]

  • BGP and statically configured SRTE traffic statistics sensor support for Junos Telemetry Interface (JTI) (MX Series and PTX Series)—Starting with Junos OS Release 18.3R1, you can export traffic statistics for both ingress IP traffic and transit MPLS traffic that take segment routing traffic engineering (SRTE) paths. This feature provides support for BGP [draft-SRTE] and statically configured SRTE policies at ingress routers.

    JTI statistics can be exported using either gRPC streaming or UDP native sensors. The following resource paths are supported.

    For UDP native sensors:

    • /junos/services/segment-routing/traffic-engineering/ingress/usage/

    • /junos/services/segment-routing/traffic-engineering/transit/usage/

    For gRPC streaming:

    • /mpls/signaling-protocols/segment-routing/

    For exporting statistics by using UDP native sensors, configure parameters at the [edit services analytics] hierarchy level.

    To provision the sensor to export data through gRPC streaming, use the telemetry Subscribe RPC to specify telemetry parameters. Streaming telemetry data through gRPC also requires you to download the OpenConfig for Junos OS module.

    For both export methods, you also must specify that these statistics be collected. To do this, configure collection at the [edit protocols source-packet-routing telemetry statistics] hierarchy level.

    [See sensor, sensor, source-packet-routing and Guidelines for gRPC Sensors (Junos Telemetry Interface).]

  • Bundling OpenConfig and Network Agent packages into Junos OS (MX Series, EX Series, PTX Series, ACX Series, QFX Series)—OpenConfig and Network Agent packages are now bundled into the Junos OS image by default. Both packages support the Junos Telemetry Interface (JTI).

    OpenConfig can be found as a default package named junos-openconfig, and Network Agent content exists in the Junos OS as a daemon through the na-telemetry package. You can also install the OpenConfig package as an add-on package on top of the default package if you want to upgrade OpenConfig without upgrading Junos OS.

    [See Installing the OpenConfig Package, and Installing the Network Agent Package (Junos Telemetry Interface).]

MPLS

  • Support for next-hop-based dynamic UDP tunnels (PTX Series)—Starting in Junos OS Release 18.3R1, next-hop-based MPLS-over-UDP dynamic tunnels are supported on the PTX Series routers. For every dynamic tunnel configured on a PTX router, a tunnel composite next hop, an indirect next hop, and a forwarding next hop is created to resolve the tunnel destination route. You can also use policy control to resolve the dynamic tunnel over select prefixes.

    The next-hop-based dynamic tunnel feature benefits data center deployments that require mesh IP connectivity from one provider edge (PE) device to all other PE devices in the network.

    [See Example: Configuring Next-Hop-Based MPLS-Over-UDP Dynamic Tunnels.]

Network Management and Monitoring

  • Support for customized MIBs for sending custom traps based on syslog events (PTX Series)—Starting in Junos OS Release 18.3R1, there is a process whereby customers can define their own MIBs for trap notifications. The customized MIB maps a particular error message with a custom OID rather than a generic one. Juniper Networks provides two new MIB roots reserved for customer MIBs, one for the custom MIB modules and the other for the trap notifications. For this process, you must convert the MIB to YANG format, and a tool is available for that.

    [See Customized SNMP MIBs for Syslog Traps.]

Routing Policy and Firewall Filters

  • Support added for logical and physical interface policers (PTX Series routers with third-generation FPCs)—Starting with Junos OS Release 18.3R1, you can police both IPv4 and IPv6 traffic on the same link, at the physical and or logical interface level, by using an aggregate policer for both traffic types.

    As such, you can define a policer for a physical interface and then reference it in different firewall filters that can then be applied to a physical interface. For example, you can configure a single aggregate policer for a physical interface, and then apply that policer to different logical interfaces and traffic families (IPv4 and IPv6) configured on the interface.

    [See: Logical Interface (Aggregate) Policer Overview .]

  • Support to configure IPv6 packet flow labels as the load-balancing hash key (PTX Series routers)—Starting in Junos OS Release 18.3R1, you can configure IPv6 packet flow labels for hash calculations on PTX Series routers. In releases before Junos OS Release 18.3R1, the ipv6-flow-label field in the IPv6 header is not used as the hashing key for load balancing. With this feature support, if you want the load balancing to be based on the flow label of the IPv6 header, include the ipv6-flow-label configuration statement at the [edit forwarding-options hash-key family inet6 layer-3] hierarchy level.

    [See ipv6-flow-label.]

Routing Protocols

  • Junos OS, OpenConfig, and Network Agent packages are delivered in a single TAR file (PTX Series)—Starting in Junos OS Release 18.3R1, the Junos OS image includes the OpenConfig package and Network Agent; therefore, you do not need to install OpenConfig or Network Agent separately on your device.

    [See Installing the OpenConfig Package and Installing the Agent Network Package.]

Software-Defined Networking (SDN)

  • Support for PCE-initiated point-to-multipoint LSPs (PTX Series)—Starting in Junos OS Release 18.3R1, the Path Computation Element Protocol (PCEP) functionality is extended to allow a stateful PCE to initiate, provision, and modify point-to-multipoint traffic engineering LSPs through a PCC.

    Currently, Junos OS supports only point-to-point PCE-initiated LSPs. With the introduction of point-to-multipoint PCE-initiated LSPs, a PCE can initiate and provision a point-to-multipoint LSP dynamically without the need for local LSP configuration on the PCC. The PCE can also control the timing and sequence of the point-to-multipoint path computations within and across PCEP sessions, thereby creating a dynamic network that is centrally controlled and deployed.

    [See Understanding Path Computation Element Protocol for MPLS RSVP-TE with Support for PCE-Initiated Point-to-Multipoint LSPs.]

User Interface and Configuration

  • Support for configuring the ephemeral database using the NETCONF and Junos XML protocols (PTX Series)—Starting in Junos OS Release 18.3R1, NETCONF and Junos XML protocol client applications can configure the ephemeral configuration database. The ephemeral database provides a fast programmatic interface that enables multiple clients to simultaneously load and commit configuration changes on a device running Junos OS and with significantly greater throughput than when committing data to the candidate configuration database. The active configuration of a device is a merged view of the committed configuration database and the configuration data in all instances of the ephemeral configuration database. Ephemeral configuration data is volatile and is deleted when the device is rebooted.

    [See Understanding the Ephemeral Configuration Database.]

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 18.3R3 for the PTX Series.

General routing

  • User confirmation prompt for configuring the sub options of request vmhost commands (MX Series and PTX series)—While configuring the following request vmhost commands, the CLI now prompts you to confirm a [yes,no] for the sub options also.

    • request vmhost reboot

    • request vmhost poweroff

    • request vmhost halt

    In previous releases, the confirmation prompt was available for only the main options.

Interfaces and Chassis

  • Change in behavior for new port speed configuration on the PTX10K-LC1101 line card—In Junos OS Release 18.3R1 and later, if you modify the port speed configuration on the PTX10k-LC1101 line card, then the new port speed configuration does not cause an FPC to reboot automatically, but it triggers an FPC need bounce alarm. To ensure that the new port speed configuration takes effect, you must manually reboot the FPC. The alarm is cleared when you manually reboot the FPC or delete the new port speed configuration.

    This change in behavior is also observed in Junos OS Releases 17.2X75-D102, 17.2R3, 17.4R2, 18.1R3, 18.1R2, 18.2X75-D10, 18.2R1, and later.

  • On a PTX10K-LC1104 line card on the PTX10008 routers, the optical interface, when configured in QPSK modulation format with FEC mode SDFEC, the encoding scheme should be Differential. The Non Differential encoding scheme is not supported for such a configuration and Link will not come up if configured.

  • New XML tag element <lacp-hold-up-state> added in show lacp interfaces XML display (PTX Series)—In Junos OS Release 18.3R2, the show lacp interfaces | display xml command displays a new XML tag element <lacp-hold-up-state>. The <lacp-hold-up-state> displays the time interval an interface holds before it changes from state, down to up. In earlier Junos OS releases, the LACP hold up the information for all interfaces were in a single <lacp-hold-up-information> XML tag. Now, for each interface it is displayed in a separate <lacp-hold-up-information> XML tag.

  • New option to configure IP address to be used when the Routing Engine is the current master—In Junos OS Release 18.3R3, a new option, master-only, is supported on routers with RE-MX-X6, RE-MX-X8, and RE-PTX-X8 Routing Engines at the following hierarchies:

    • [edit vmhost interfaces management-if interface (0|1) family inet address IPv4 address]

    • [edit vmhost interfaces management-if interface (0|1) family inet6 address IPv6 address]

    In routing platforms with dual Routing Engines and VM host support, the master-only option enables you to configure the IP address to be used for the VM host when the Routing Engine is the current master. The master Routing Engine and the backup Routing Engine can have independent host IP addresses configured. In earlier releases, the same IP address is applied on the master and backup Routing Engines, resulting in configuration issues.

Junos OS XML API and Scripting

  • MD5 and SHA-1 hashing algorithms are no longer supported for script checksums (PTX 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

  • New debug statistics counter (PTX Series)—The show system statistics mpls command has a new output field, called Packets dropped, over p2mp composite nexthop, to record the packet drops over composite point-to-multipoint next hops.

Network Management and Monitoring

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

  • Change in Error Severity (PTX10016)—Starting in Junos OS Release 18.3R2, on PTX10016 routers, the severity of the FPC error, shown in the syslog as PE Chip::FATAL ERROR!! from PE2[2]: RT: Clear Fatal if it is detected LLMEM Error MEM:llmem, MEMTYPE: 1, is changed from fatal to non-fatal (or minor). In case of this error, only a message is displayed for information purpose. To view the error details, you can use the show commands show chassis fpc errors and show chassis errors active.

    [See show chassis fpc errors]

  • The NETCONF server omits warnings in RPC replies when the rfc-compliant statement is configured and the operation returns <ok/> (PTX Series)—Starting in Junos OS Release 18.3R2, when you configure the rfc-compliant statement at the [edit system services netconf] hierarchy level to enforce certain behaviors by the NETCONF server, if the server reply after a successful operation includes both an <ok/> element and one or more <rpc-error> elements with a severity level of warning, the warnings are omitted. In earlier releases, or when the rfc-compliant statement is not configured, the NETCONF server might issue an RPC reply that includes both an <rpc-error> element with a severity level of warning and an <ok/> element.

Openconfig

  • The native Junos OS OpenConfig package does not display in operational mode (PTX Series)—Starting in Junos OS Release 18.3R1, the show system yang package command in operational mode does not display the native Junos OS OpenConfig package. This is because the Junos OS image includes the OpenConfig package.

Routing Policy and Firewall Filters

  • Error caused by firewall filters with syslog and accept action (PTX1000 or PTX series routers with type 3 FPCs)—In this release of Junos OS, under rare circumstances, the host interface may stop sending packets and the connections to and from the peer might fail if an outbound firewall filter is configured with an action of syslog and accept. This condition applies to IPv4 and IPv6 traffic families. Juniper recommends that you do not use the syslog and accept action in the output filter for these systems.

    An example configuration is provided (shows IPv4).

    [For more information, see PR 1354580.]

Software Installation and Upgrade

  • ssh-keygen output is tagged in XML (PTX1000)—Starting in Junos OS Release 18.3R1, the output of the ssh-keygen utility that is invoked when generating the ssh keys, is now in XML format, and is wrapped in <output> tags. You can see this change in the console output at the time a device boots up with a new image.

    [See Junos OS Installation Package Names.]

Subscriber Management and Services

  • DHCPv6 lease renewal for separate identity association (IA) renew requests (PTX 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.]

Known Behavior

This section contains the known behavior, system maximums, and limitations in hardware and software in Junos OS Release 18.3R3 for PTX Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

General Routing

  • In the specific case of semi-graceful RCB reboot initiated by the internal shell command vhclient init 0, GRES takes longer to complete (3 minutes as opposed to 21 seconds). The regular CLI command request vmhost reboot (graceful) and a jack-out-jack-in of the Routing Engine (ungraceful) do not exhibit this delay. PR1312065

  • The Routing Engine boots from the secondary disk when you:

    • a) Press the reset button, on the RCB front panel, while Routing Engine is booting up but before Junos OS is up.

    • b) Upgrade software, by booting from the network using the request vmhost reboot network command, and the system fails to boot from the network

    • c) Upgrade BIOS and the upgrade fails.

    • d) Reboot and the system hangs before Junos OS is up. PR1344342

  • Due to ZH ASIC limitation, MAC statistics under show interface, in Routing Engine, might not reflect "Mac error Counters" properly if ingress packet size is greater than default mtu (1518) or user configured MTU size set interface <interface-name> mtu <288...9600>. PR1345779

  • 100G DAC connected between QFX5200 and PTX10002-60C/QFX10002-60C will not link up. This is because BCM based devices have link-training enabled and PE based devices do not have link-training enabled for 100G DAC/CR4. PR1356834

  • Logical systems feature is not supported. PR1361016

  • On a PTX1000 router, after the system is rebooted by issuing the request vmhost reboot command, the netproxy service might fail to start. PR1365664

  • Back-to-back speed changes on interface ports might cause the relevant port physical interface not to be created. PR1367946

  • The DHCP relay functionality does not work on PTX10001-20C devices. DHCP relay functionality: The DHCP requests and the DHCP offers are snooped by the box, the snooping happens via firewall, firewall snoops all the DHCP packets ingressing the default route table, and all the offers and requests are punted unto the host/control-plane. When a DHCP client sends the DHCP request, it gets intercepted by the filter block and punted up to the control plane. Upon receiving this packet, control plane unicasts (relays) this packet to DHCP server. DHCP server responds back with a DHCP Offer, which again gets intercepted by the firewall block and punted up. Upon receiving the DHCP offer, control plane broadcasts this DHCP offer to the clients VLAN and eventually client receives the DHCP offer. PR1407476

  • DDoS counter does not reflect the real max arrival rate and arrival rate on PTX platform From 17.4, ddos is supported on PTX platform with PE chipset Packet Forwarding Engines. Due to known limitation, the ddos "arrival rate" and "max arrival rate" is not reflecting real time violated packet counts. This is a product limitation. PR1425009

Interfaces and Chassis

  • Incorrect MAC statistics—On the PTX10001 routers, the show interfaces interface-name media detail command might not display the MAC error counters correctly for oversized frames, that is, the ingress packets with size greater than the default maximum transmission unit (MTU) size (1518) or the MTU size configured by a user (by using the command set interface interface-name mtu bytes).

  • The request support information command executes additional show commands—On PTX Series routers, the request support information command executes the following show commands in addition to the existing show commands:

    • show chassis fabric summary

    • show chassis fabric fpcs

    • show chassis fabric sibs

    • show chassis fabric topology

    • show chassis fabric reachability

    • show chassis fpc

    • show chassis power

    • show pfe statistics traffic

  • On a PTX10K-LC1104 line card on the PTX10008 routers, the optical interface, when configured in QPSK modulation format with FEC mode SDFEC, the encoding scheme should be differential. The link does not come up when configured with a non-differential encoding scheme because it is not supported.

Routing Policy and Firewall Filters

  • Error caused by firewall filters with syslog action (PTX1000 or PTX series routers with type 3 FPCs)—In this release of Junos OS, under rare circumstances, the host interface may stop sending packets and the connections to and from the peer might fail if an outbound firewall filter is configured with an action of syslog. This condition applies to IPv4 and IPv6 traffic families. Juniper recommends that you do not use the syslog action in the output filter for these systems.

    An example configuration is provided (shows IPv4).

    [For more information, see PR 1354580.]

User Interface and Configuration

  • Auto-complete caution for QFX10002-60c and PTX10002-60c personalities—Starting in Junos OS Release 18.3R2, for QFX10002-60c and PTX10002-60c personalities, do not use auto-complete to display the list of arguments for the request system software delete command. You must look for the package name using the show system software command and then explicitly type the software package name in the request system software delete command.

    [See request system software delete].

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 18.3R3 for the PTX Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

General Routing

  • Control packets might get dropped when the Packet Forwarding Engine experiences heavy congestion. PR1163759

  • When an FPC goes offline or restarts, source FPC sends traffic to destination FPC. The following error messages are seen and a corresponding alarm is set on the destination FPC. Specific to PTX10000, the transient alarm gets set when this condition occurs. The alarm clears later because the source FPC goes offline. Apr 09 10:31:24 [TRACE] [asta] Apr 9 10:19:59 asta fpc4 Error (0x210613), module: PE Chip, type: Apr 09 10:31:24 [TRACE] [asta] Apr 9 10:19:59 asta fpc4 Cmerror Op Set: PE Chip: PE1[1]: FO:core intr: 0x00000010: Grant spray drop due to unspray-able condition error Apr 09 10:31:24 [TRACE] [asta] Apr 9 10:19:59 asta fpc4 Error (0x210614), module: PE Chip, type: Apr 09 10:31:24 [TRACE] [asta] Apr 9 10:19:59 asta fpc4 Cmerror Op Set: PE Chip: PE1[1]: FO:core intr: 0x00000008: Request spray drop due to unspray-able condition error. PR1268678

  • On a PTX Series PIC with the CFP2-DCO-T-WDM transceiver installed, after repeated configuration rollback, the link sometimes takes a long time to come up. PR1301462

  • When CFP2-DCO-T-WDM-1 is plugged in PTX Series PIC, after FPC restart sometimes carrier frequency offset TCA is raised even when TCA not enabled. PR1301471

  • Repeated log message %PFE-3 fpcX expr_nh_index_tree_ifl_get and expr_nh_index_tree_ipaddr_get are observed when sampling packets are discarded with log (or syslog) statements under the firewall filter. PR1304022

  • On a PTX Series router with a third-generation FPC, the error message is displayed when the FPC goes online or offline. PR1322491

  • On 30-Port MACsec Linecard (LC1101-M - 30C / 30Q / 96X) of PTX Series chassis, under certain circumstances, while exclude-protocol lacp configuration under hierarchy level [edit security macsec connectivity-association connectivity-association-name], is deleted or deactivated, the LACP protocol's "Mux State" shown under the output of CLI command show lacp interface, might remain as "attached" or "detached" and would not transition to "distributing" state. PR1331412

  • PTX3000 reports CCL (chip to chip link) CRC errors while FPC3-SFF-PTX-1X is offlined via CLI command or by pressing the offline button. The syslog error is generated by an FPC just before it goes offline, so there is no detectable traffic loss. Messages: Apr 2 08:43:00 fpc4 CMSNGFM: cmsngfpc_fm_send_spry_ctrl_ack: ev_id:11 fm_st:ALL fm_type:FPC_OFF fm_op:DEL Apr 2 08:43:00 fpc2 CMSNGFM: cmsngfpc_platform_fm_periodic: PFE 0 detected link error for S00F0_0(11,0,11)->FPC02FE0(0,00) Apr 2 08:43:00 fpc2 CCL: Logging statistics for FPC02FE0(0,00) Apr 2 08:43:00 fpc2 CCL: SOT:0x0000037649c2c43e Apr 2 08:43:00 fpc2 CCL: FrameCnt:0x00000000000419dc Apr 2 08:43:00 fpc2 CCL: LastCRCErrCnt:0x00000003 Apr 2 08:43:00 fpc2 CCL: AggrCRCErrCnt:0x0000000000000003 Apr 2 08:43:00 fpc2 CCL: AggrBERCnt:0x0000000000000001 Apr 2 08:43:00 fpc2 CCL: pe0-Avg-28nm-link-10-18 CRC error history (last 5 polls): Apr 2 08:43:00 fpc2 CCL: 0x0 0x0 0x0 0x0 0x3 Apr 2 08:43:00 fpc2 CCL: FEC Uncorrectable FEC Correctable Apr 2 08:43:00 fpc2 CCL: 00000004, 00000000 Apr 2 08:43:00 fpc2 CCL: 00000000, 00000000 Apr 2 08:43:00 fpc2 BEGIN Rx serdes info for asic pe0-0 serdes 18 Apr 2 08:43:00 fpc2 Signal & port condition for serdes_num 18 Apr 2 08:43:00 fpc2 Rx Signal : Signal Not OK Apr 2 08:43:00 fpc2 Rx Electrical Idle : High Apr 2 08:43:00 fpc2 Rx Frequency Lock: Set Apr 2 08:43:00 fpc2 Rx Port : Ready Apr 2 08:43:00 fpc2 DFE TAPs : -- snip -- Apr 2 08:43:00 fpc2 CCL: FrameCnt:0x0000000000041a0d Apr 2 08:43:00 fpc2 CCL: LastCRCErrCnt:0x00000003 Apr 2 08:43:00 fpc2 CCL: AggrCRCErrCnt:0x0000000000000003 Apr 2 08:43:00 fpc2 CCL: AggrBERCnt:0x0000000000000001 Apr 2 08:43:00 fpc2 CCL: pe0-Avg-28nm-link-14-22 CRC error history (last 5 polls): Apr 2 08:43:00 fpc2 CCL: 0x0 0x0 0x0 0x0 0x3 Apr 2 08:43:00 fpc2 CCL: FEC Uncorrectable FEC Correctable Apr 2 08:43:00 fpc2 CCL: 00000004, 00000000 Apr 2 08:43:00 fpc2 CCL: 00000000, 00000000 Apr 2 08:43:00 fpc2 BEGIN Rx serdes info for asic pe0-0 serdes 22 Apr 2 08:43:00 fpc2 Signal & port condition for serdes_num 22 Apr 2 08:43:00 fpc2 Rx Signal : Signal Not OK Apr 2 08:43:00 fpc2 Rx Electrical Idle : High Apr 2 08:43:00 fpc2 Rx Frequency Lock: Set Apr 2 08:43:00 fpc2 Rx Port : Ready Apr 2 08:43:00 fpc2 DFE TAPs : -- snip -- Apr 2 08:43:00 fpc2 CCL: Logging errors for FPC02FE0(0,00) Apr 2 08:43:00 fpc2 CCL: BER Err Apr 2 08:43:00 fpc2 CCL: Frame Lock Loss Apr 2 08:43:00 fpc2 CCL: Align Loss Apr 2 08:43:00 fpc2 CCL: Header Comparison Error Apr 2 08:43:00 fpc2 CCL: Header Preamble Error Apr 2 08:43:00 fpc2 CMSNGFM: cmsngfpc_platform_fm_periodic: PFE 0 detected link error for S00F1_0(14,0,14)->FPC02FE0(1,00) Apr 2 08:43:00 fpc2 CMSNGFM: cmsngfpc_platform_fm_periodic: PFE 1 detected link error for S00F0_0(11,0,11)->FPC02FE1(0,00) Apr 2 08:43:00 fpc2 CMSNGFM: cmsngfpc_platform_fm_periodic: PFE 1 detected link error for S00F1_0(14,0,14)->FPC02FE1(1,00) User@PTX3000> show chassis hardware detail Hardware inventory: FPC 0 REV 43 750-057064 ACPV7514 FPC3-SFF-PTX-1XCPU BUILTIN BUILTIN SMPC PMB FPC 2 REV 40 750-057064 ACPJ9145 FPC3-SFF-PTX-1XCPU BUILTIN BUILTIN SMPC PMB FPC 4 REV 43 750-057064 ACPR8506 FPC3-SFF-PTX-1XCPU BUILTIN BUILTIN SMPC PMB SIB 0 REV 10 750-057067 ACPJ8829 SIB3-SFF-PTX SIB 1 REV 10 750-057067 ACPJ8683 SIB3-SFF-PTX SIB 2 REV 10 750-057067 ACPJ8843 SIB3-SFF-PTX SIB 3 REV 10 750-057067 ACPJ8920 SIB3-SFF-PTX PR1348733

  • With TIC offline/online, MPLS bidirectional traffic flow might stop working. PR1367920

  • The DHCP Relay functionality does not work on PTX10001-20C devices. DHCP relay functionality: The DHCP requests and the DHCP offers are snooped by the box, the snooping happens via firewall, firewall snoops all the DHCP packets ingressing the default route table and all the offers and requests are punted unto the host/control-plane. When a DHCP client sends the DHCP request, it gets intercepted by the filter block and punted up to the control plane. Upon receiving this packet, control-plane unicast (relay) this packet to DHCP server. DHCP server responds back with a DHCP Offer, which again gets intercepted by the firewall block and punted up. Upon receiving the DHCP offer, control plane broadcast this DHCP offer to the clients vlan and eventually client receives the DHCP offer. PR1407476

  • The rx_power value streamed to the telemetry server is the raw value (mW) returned directly from the transceiver driver. The Junos OS CLI value has been transformed in the transportd daemon into different units: (Rx input total power(0.01dBm). PR1411023

  • In PTX3000 system, only if the IPLC card is present in the system, and when GRES is performed, we will observe IPLC crash during the GRES operation. No impact on other line cards in the system. If there is no IPLC card in the system, there is no impact during the GRES. PR1415145

  • Firewall counter for lo0 is not incrementing for L2 traffic. PR1420560

  • On PTX1000/10000, PTX3000/5000 with FPC3 or QFX10000 series, if the prefix entries configured in prefix-list exceed the limit that the Packet Forwarding Engine (PFE) chipset supports, some unexpected behavior might be observed (for example, the host-bound traffic drops) after performing change operation related to the prefix-list configuration (for example, add a prefix to prefix-list that is associated with filter). PR1426539

  • Due to broadcom firmware issue under some error condition broadcom retimer will assert pmd-lock bit with a closed eye, in order to recover from this condition Junos code will issue force pmd-lock command every time we trying to bring up a link in "DOWN" state. PR1428307

  • JDI-L3VPN-REGRESSIONS: More packet loss seen after unified ISSU with InterAS Layer 3 VPN OptionB configuration. PR1435578

  • Upgrade broadcom retimer firmware version d00e to de2e is automatic, t6e-pic driver will check broadcom retimer firmware version is de2e or not, if firmware is not at version de2e pic driver will do firmware update for all retimers on gladiator PIC. This process will take up to 5 minutes, before firmware upgrade complete interface will stay in down state. PR1445473

  • We are updating the broadcom 8238x retimer line side serdes SI parameter amplitude value from 15 to 3, juniper SI group recommended the value of 3; with old value we are overdriving optic's line side serdes which could cause optic reliability issue. PR1453217

Interfaces and Chassis

  • Upgrading Junos OS Release 14.2R5 and later maintenance releases and Junos OS Release 16.1 and later mainline releases with CFM configuration might cause the cfmd process to crash after upgrade. This is because of the old version of /var/db/cfm.db. PR1281073

  • Recover link after a fiber cut: To recover the link, we can either do interface disable/enable or dfe tuning. To do dfe tune: Got to vty -Go to vty fpc# From this you can get the PE number, sbus id and the number of links show t6e-pic 0 port_map 2 1-2 0 0 10 10 0/24/155 1/25 2/26 3/27 4/28 5/29 6/30 7/31 8/32 9/33/164 -Run dfe tune for the problem link (link which is not receiving packets) test asic pe1-1(43) avago-serdes dfe 155 10 SPICObased single_loop (using the info from the above command) - Status of the dfe LNX-FPC4(macadamia vty)# show asic pe1-1(43) avago-serdes 179 dfe iCal (Coarse tune) status of serdes 0xb3 : Completed pCal (Fine tune) status of serdes 0xb3 : Completed pCal Adaptive status of serdes 0xb3 : disabled - Check is LACP is transmitting and receiving and is in "collecting/distributing" state. PR1429279

Routing Protocols

  • With BFD configured on aggregated Ethernet interface, if disable/enable aggregated Ethernet interface, after that ae interface and Bidirectional Forwarding Detection (BFD) session might not come up. PR1354409

Resolved Issues

This section lists the issues fixed in the Junos OS main release and the maintenance releases for the PTX Series.

For the most complete and latest information about known Junos OS defects, use the Juniper Networks online Junos Problem Report Search application.

Resolved Issues: 18.3R3

General Routing

  • slu.l2_domain_lookup_failure traps might be observed when using sampling on FPC-P1/FPC-P2. PR1368381

  • Power usage ST components in PTX5000 do not work as intended. PR1372369

  • Fail to decap l2l hdr & invalid L2Lheader error messages are seen on FPCs during master/backup Routing Engine reboot. PR1374372

  • Telemetry data export might be missed when multiple LLDP sensors are getting exported simultaneously. PR1382691

  • Disable reporting of correctable single-bit error on Hybrid Memory Cube (HMC) and prevent major alarm. PR1384435

  • The agentd sensor transmits multiple interface telemetry statistics per FPC slot. PR1392880

  • Confirmation message is missing when issuing request vmhost reboot re*. PR1397912

  • The DHCPv6 relay-reply packet might be dropped by the DHCP relay. PR1399683

  • On PTX3000/5000, backup CB's chassis environment status keeps testing after backup CB removal/reinsertion. PR1405181

  • Openconfig-network-instance:network-instances support for IS-IS must be hidden unless supported. PR1408151

  • The port at FPC (for example, JNP10K-LC1101) might fail to come up. PR1409585

  • Junos OS PCC might reject PCUpdate/PCCreate message if there is metric type other than type 2. PR1412659

  • The PTX1000/PTX10002/QFX10002 might stop forwarding packets after the chassis-control process restarts. PR1414434

  • RX alarms are not set as according to the threshold value configured for the DCO Tunable Optics. PR1419204

  • An interface might go to down state on QFX10000/PTX10000 platform. PR1421075

  • Virtual Chassis might become unstable and generate FXPC core files when there are a lot of configured filter entries. PR1422132

  • Packet Forwarding Engine wedge might be observed after performing the command show forwarding-options load-balance .... PR1422464

  • Four 10-Gigabit Ethernet interfaces on PTX3000/PTX5000 FPC type 3 might not come up after frequently flap for a large amount of time. PR1422535

  • While committing huge configuration customer is seeing the error error: mustd trace init failed. PR1423229

  • Traffic is dropped after FPC reboot with aggregated Ethernet member links deactivated by remote device. PR1423707

  • Specific interface on P3-15-U-QSFP28 PIC card remains down until another interface comes up. PR1427733

  • An interface with port 7, 9, 17, 19, 27, 29 might go to down state on 30 port 40-Gigabit Ethernet or 100-Gigabit Ethernet line cards. PR1427883

  • PTX10K/LC1101: When an interface is configured with jumbo frames support (for example, MTU = 9216), the effective MTU size for locally sourced traffic is 24 bytes less than the expected value. PR1428094

  • Inline J-Flow might cause PECHIP Major error. PR1429419

  • IPFIX Flow timestamp is not matching with NTP synchronized system time. PR1431498

  • SIB Link Error detected on a specific Packet Forwarding Engine might cause complete service impact. PR1431592

  • Scaled-filter leads to packets drop as flt.Dispatcher.flt_err on PTX Series routers.PR1433648

  • IPv6 neighbor solicitation packets are getting dropped on PTX Series routers.PR1434567

  • Interfaces on PTX might not come up after FPC restart or port flap. PR1442159

  • The KRT queue might be stuck when more than 65000 IPv6 labeled-unicast routes are received on BGP-LU IPv6 session that is configured on PTX10000 series platform. PR1442760

  • The process jdhcpd might crash after issuing the command show access-security router-advertisement-guard. PR1446034

  • PTX: After running protocols and traffic for a decent duration, observed all the Gladiator FPCs throwing "Hard Error" and SPMBs showing offline. PR1446090

  • Egress sampling for sflow might stop working for more than 8 interfaces on PTX platforms. PR1448778

  • Interfaces might flap forever after deleting the interface disable configuration. PR1450263

  • Firewall filter applied at interface level not working when entropy level is present in certain scenarios. PR1452716

  • The FPC might crash when the severity of error is modified by URI format error-id. PR1453871

Infrastructure

  • The request system recover oam-volume command might fail on PTX Series routers. PR1425003

  • Unsupported package warning after system upgrade. PR1427344

Interfaces and Chassis

  • Syslog message : /kernel: %KERN-3: pointchange for flag 04000000 not supported on IFD aex occurs upon LFM related configuration commit on aggregated Ethernet interfaces. PR1423586

  • Some ports on PTX Series routers might remain down after rebooting the FPC/device at remote site. PR1429315

MPLS

  • RSVP path error received on PSB:2 ( new path calculated by CSPF) is not treated as Optimization when CSPF is computed and optimization retry is not honoring 2^retry + rsvp-error-hold-time. PR1416948

  • The dynamic bypass RSVP LSP tears down when being used to protect LDP LSP. PR1425824

  • The transit packets might be dropped if an LSP is added or changed on MX Series or PTX Series device. PR1447170

Platform and Infrastructure

  • FB-CSIM: PTX10008: master-only option needed for vmost mgmt interface for host IP. PR1375012

Routing Protocols

  • Routing Engine-based micro BFD packets do not go out with configured source IP when the interface is in logical system. PR1370463

  • Syslog message is seen whenever prefix SID coincides with the node SID. PR1403729

  • Dynamic routing protocol flapping occurs with vmhost Routing Engine switchover on next-generation Routing Engine. PR1415077

  • PTX Series device cannot intercept PIM BSR message. PR1419124

  • RPD might crash with ospf overload configuration. PR1429765

  • The rpd might crash with SR-TE configuration change. PR1442952

VPNs

  • In a specific CE device environment in which asynchronous-notification is used, after the link between the PE and CE devices goes up, the L2 circuit flaps repeatedly. PR1282875

  • Memory leak might happen if PIM messages are received over an MDT (mt- interface) in Draft-Rosen MVPN scenario. PR1442054

Resolved Issues: 18.3R2

General Routing

  • Status LED on the chassis does not show UP on PTX10002-60C. PR1332991

  • Member of IPv4 unilist next-hops might be stuck in "Replaced" state after interface flaps. PR1336201

  • Multicast traffic packet drop of more than 50 percent is seen when having FPC1/FPC2 mix with FPC3. PR1339481

  • Traffic drop might be seen after GRES if uRPF is configured. PR1354285

  • The host interface might stop sending packets on PTX Series routers with FPC3 or PTX1000 when using outbound firewall filter with syslog option. PR1354580

  • PTX10001 platform: FRR link-protection convergence time is not within limits. PR1355953

  • Netproxy service client component fails to start after issuing request vmhost reboot. PR1365664

  • The 'Normal discards' Packet Forwarding Engine statistics traffic counter might increase at a higher rate when Inline-Jflow or sFlow is enabled. PR1368208

  • The IPLC card might take a long time to come up. PR1368637

  • Inline BFD might keep flapping when inline sampling is configured. PR1376509

  • Traffic might be dropped on third-generation FPCs on PTX Series routers. PR1378392

  • With the given configuration, continuous error messages are observed: expr_sensor_detach_rt_cntr_from_sgid:2793: Invalid sensor group ID 0.PR1379730

  • FPC might crash on PTX Series routers or QFX10000 after lo0 filter change. PR1380917

  • BFD sessions flap when restarting one FPC on PTX10000 routersPR1383703

  • Packet Forwarding Engine-based local repair does not happen for IP routes pointing to unilist of composites with indirect next hops. PR1383965

  • CPSM daemon memory leak is observed in VMHOST. PR1387903

  • BFD flaps are seen on PTX Series routers or QFX10000 platforms with inline BFD. PR1389569

  • Forwarding issue on mixed link-speed aggregated Ethernet interface after FPC reloads. PR1390417

  • lcmd core and FPC restarted. PR1391443

  • High jsd or na-grpcd CPU usage might be seen even when JET or JTI is not used. PR1398398

  • CPU overuse might be observed on PTX/QFX10000 platform. PR1399369

  • The DHCPv6 relay-reply packet might be dropped by the DHCP relay. PR1399683

  • Only one Packet Forwarding Engine could be disabled on FPC with multiple Packet Forwarding Engines in error/wedge condition. PR1400716

  • jlock hog by tcp_timer_delack caused ppmd connection to drop with Packet Forwarding Engine. PR1401507

  • The log message JAM HW data base open failed for ptx5kpic_3x400ge-cfp8 is seen during commit. PR1403071

  • Incorrect memory statistics message is seen in FPC logs of PTX Series Type 1 FPC. PR1404088

  • PTX3000: FPCs are not able to come online for tens of minutes after a reboot of the chassis. PR1404611

  • 100G SR4 Optics with part number 740-061405 should be displayed as "QSFP-100G-SR4-T2". PR1405399

  • No chassis alarm is raised on PTX1000 when PEM is removed or power lost to PEM. PR1405430

  • Layer2 VPN will flap repeatedly after link up between PE and CE under "asynchronous-notification" and "some types of MICs" conditions. PR1407345

  • The L2circuit egress PE might drop the traffic in FAT+CW enabled L2circuit scenario when another FAT+CW enabled L2circuit PW flaps. PR1415614

  • Traffic loss might be seen for duration of hold-time down timer when flapping an interface with hold-time down timer configured. PR1418425

Infrastructure

  • The FPC might go down on some vmhost-based PTX Series platforms. PR1367477

  • The error of jlaunchd: disk-monitoring is thrashing, not restarted might be seen. PR1380032

Interfaces and Chassis

  • PE Chip:pe0[0]: IPW: oversize_drop error causes major error on FPC. PR1375030

MPLS

  • MPLS LSP will keep down state due to routing loop detection after flapping link between P router and egress PE. PR1384929

  • The rpd might crash when LDP route with indirect next-hop is deleted. PR1398876

  • A single-hop bypass LSP might not be used for traffic when both transit chaining mode and sensor-based-stats are used. PR1401152

Platform and Infrastructure

  • Some files are missing during log archiving. PR1405903

Routing Protocols

  • The rpd process might crash after executing commit the configuration related to mapping-server-entry. PR1379558

  • The rpd generates core files on backup Routing Engine during neighborship flap when using an authentication-key with size larger than 20 characters. PR1394082

  • Syslog message is seen whenever prefix sid coincides with the node sid. PR1403729

  • Memory leaks when labeled-isis transit routes are created as chain composite next hop. PR1404134

Resolved Issues: 18.3R1

General Routing

  • On a PTX1000 router, upgrade from Junos OS Release 16.1X65D45 to Junos OS Release 17.3 fails frequently when sampling is enabled. PR1296533

  • On PTX10008 and PTX10016 routers, the suppress chassis alarm is displayed for switched-off PEMS. PR1311574

  • On a PTX10000 router, when the PIC or port speed is changed in configuration, an alarm or warning is issued. PR1311875

  • On a PTX10000 router, for 100-gigabit LR4 optics with part number 740-061409 change the show chassis hardware display to QSFP-100G-LR4-T2. PR1322082

  • The GRE traffic is not decapsulated by the firewall filter. PR1325104

  • On PTX10016 router, VXLAN is not supported and it has to be either removed or disabled in the [edit switch-options] hierarchy. PR1328502

  • A next-hop programming issue occurs during link flapping on PTX Series routers. PR1333274

  • The Tc_count counters in a filter configured with the scale-optimized statement do not increment. PR1334580

  • On PTX10016 router, traffic stops flowing out of the aggregated Ethernet interface 70 after some FPC restarted a few times. PR1335118

  • The FPC might get rebooted a few minutes after a configuration is loaded. PR1346467

  • No DHCP service or configuration is running after the system is returned to zero. PR1347730

  • Sensors are not getting cleared up after a Routing Engine switchover is performed. PR1347779

  • The MPLS traceroute for P2MP LSPs configured with link protection causes the FPC to crash. PR1348314

  • On PTX Series routers, the threshold is not getting configured correctly when it is configured using scope and category options. PR1350841

  • BFD sessions do not come up on PTX3000 router. PR1352112

  • If the 15-port 100-Gigabit Ethernet PIC is used on PTX Series routers, the interface might be delayed by 60 seconds to come up from the down status. PR1357410

  • The multicast replication traffic might be lost on an aggregated Ethernet bundle interface after one member link goes down. PR1359974

  • Traffic continues to be forwarded through the member links of an aggregated Ethernet bundle interface even when the Link-Layer-Down flag is set. PR1365263

  • On PTX IPLC (OPT3-SFF-PTX FPC), the first J-UKERN crash triggers multiple secondary J-UKERN crashes. PR1365791

  • The commit or commit check command might fail due to the error of cannot have lsp-cleanup-timer without lsp-provisioning. PR1368992

  • Packet is dropped after the filter is deleted on the interface. PR1372957

  • Layer 3 VPN traffic might be dropped because of the selector weight is set to 65535 after one core-facing interface goes down. PR1380783

MPLS

  • MPLS LSP statistics are not shown in the output of the show mpls lsp ingress statistics command. PR1344039

  • Some LSPs might be stuck on the upstream devices after interfaces flap occurs on downstream devices. PR1349157

  • IPv6 routes are dead in the mpls.0 table and S=0 leads traffic loss in v6-indirect next-hop stitching. PR1355878

  • LSP with auto-bandwidth enabled goes down during an HMC error condition. PR1374102

Platform and Infrastructure

  • Running RSI through the console port might cause the system to crash and reboot. PR1349332

  • Traffic might be silently dropped and the following error message for next hops is displayed: JPRDS_NH:jprds_nh_alloc(),651: JNH[0] failed to grab new region. PR1357707

  • Unable to commit Junos OS configuration during the ZTP process and ZTP process stop is completed. PR1358919

Routing Protocols

  • All OSPF neighbors go down after start the LDP session. PR1304504

  • The primary path of an MPLS LSP might switch to other address. PR1316861

  • Protocol churn might cause the rpd to crash. PR1341466

  • An rpd core file might be generated while running streaming telemetry. PR1347431

Documentation Updates

There are no errata or changes in Junos OS Release 18.3R3 documentation for PTX Series.

Migration, Upgrade, and Downgrade Instructions

This section contains the procedure to upgrade Junos OS, and the upgrade and downgrade policies for Junos OS for the PTX Series. Upgrading or downgrading Junos OS might take several hours, depending on the size and configuration of the network.

Basic Procedure for Upgrading to Release 18.3

When upgrading or downgrading Junos OS, use the jinstall package. For information about the contents of the jinstall package and details of the installation process, see the Installation and Upgrade Guide. Use other packages, such as the jbundle package, only when so instructed by a Juniper Networks support representative.

Note

Back up the file system and the currently active Junos OS configuration before upgrading Junos OS. This allows you to recover to a known, stable environment if the upgrade is unsuccessful. Issue the following command:

Note

The installation process rebuilds the file system and completely reinstalls Junos OS. Configuration information from the previous software installation is retained, but the contents of log files might be erased. Stored files on the router, such as configuration templates and shell scripts (the only exceptions are the juniper.conf and ssh files), might be removed. To preserve the stored files, copy them to another system before upgrading or downgrading the routing platform. For more information, see the Installation and Upgrade Guide.

Note

We recommend that you upgrade all software packages out of band using the console because in-band connections are lost during the upgrade process.

To download and install Junos OS Release 18.3R3:

  1. Using a Web browser, navigate to the All Junos Platforms software download URL on the Juniper Networks webpage:

    https://www.juniper.net/support/downloads/

  2. Select the name of the Junos OS platform for the software that you want to download.
  3. Select the release number (the number of the software version that you want to download) from the Release drop-down list to the right of the Download Software page.
  4. Select the Software tab.
  5. In the Install Package section of the Software tab, select the software package for the release.
  6. Log in to the Juniper Networks authentication system using the username (generally your e-mail address) and password supplied by Juniper Networks representatives.
  7. Review and accept the End User License Agreement.
  8. Download the software to a local host.
  9. Copy the software to the routing platform or to your internal software distribution site.
  10. Install the new jinstall package on the router.Note

    We recommend that you upgrade all software packages out of band using the console because in-band connections are lost during the upgrade process.

    All customers except the customers in the Eurasian Customs Union (currently composed of Armenia, Belarus, Kazakhstan, Kyrgyzstan, and Russia) can use the following package:

    user@host> request system software add validate reboot source/junos-install-ptx-x86-64-18.3R3.9.tgz

    Customers in the Eurasian Customs Union (currently comprising Armenia, Belarus, Kazakhstan, Kyrgyzstan, and Russia) can use the following package (Limited encryption Junos OS package):

    user@host> request system software add validate reboot source/junos-install-ptx-x86-64-18.3R3.9-limited.tgz

    Replace the source with one of the following values:

    • /pathname—For a software package that is installed from a local directory on the router.

    • For software packages that are downloaded and installed from a remote location:

      • ftp://hostname/pathname

      • http://hostname/pathname

      • scp://hostname/pathname

    The validate option validates the software package against the current configuration as a prerequisite to adding the software package to ensure that the router reboots successfully. This is the default behavior when the software package being added is a different release.

    Adding the reboot command reboots the router after the upgrade is validated and installed. When the reboot is complete, the router displays the login prompt. The loading process might take 5 to 10 minutes.

    Rebooting occurs only if the upgrade is successful.

Note

You need to install the Junos OS software package and host software package on the routers with the RE-PTX-X8 Routing Engine. For upgrading the host OS on this router with VM Host support, use the junos-vmhost-install-x.tgz image and specify the name of the regular package in the request vmhost software add command. For more information, see the VM Host Installation topic in the Installation and Upgrade Guide.

Note

After you install a Junos OS Release 18.3 jinstall package, you cannot return to the previously installed software by issuing the request system software rollback command. Instead, you must issue the request system software add validate command and specify the jinstall package that corresponds to the previously installed software.

Note

Most of the existing request system commands are not supported on routers with RE-PTX-X8 Routing Engines. See the VM Host Software Administrative Commands in the Installation and Upgrade Guide.

Upgrade and Downgrade Support Policy for Junos OS Releases

Support for upgrades and downgrades that span more than three Junos OS releases at a time is not provided, except for releases that are designated as Extended End-of-Life (EEOL) releases. EEOL releases provide direct upgrade and downgrade paths—you can upgrade directly from one EEOL release to the next EEOL release even though EEOL releases generally occur in increments beyond three releases.

You can upgrade or downgrade to the EEOL release that occurs directly before or after the currently installed EEOL release, or to two EEOL releases before or after. For example, Junos OS Releases 17.4, 18.1, and 18.2 are EEOL releases. You can upgrade from Junos OS Release 17.1 to Release 17.2 or from Junos OS Release 17.1 to Release 17.3. However, you cannot upgrade directly from a non-EEOL release that is more than three releases ahead or behind.

To upgrade or downgrade from a non-EEOL release to a release more than three releases before or after, first upgrade to the next EEOL release and then upgrade or downgrade from that EEOL release to your target release.

For more information about EEOL releases and to review a list of EEOL releases, see https://www.juniper.net/support/eol/junos.html.

Upgrading a Router with Redundant Routing Engines

If the router has two Routing Engines, perform a Junos OS installation on each Routing Engine separately to avoid disrupting network operation as follows:

  1. Disable graceful Routing Engine switchover (GRES) on the master Routing Engine and save the configuration change to both Routing Engines.

  2. Install the new Junos OS release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine.

  3. After making sure that the new software version is running correctly on the backup Routing Engine, switch over to the backup Routing Engine to activate the new software.

  4. Install the new software on the original master Routing Engine that is now active as the backup Routing Engine.

For the detailed procedure, see the Installation and Upgrade Guide.

Product Compatibility

Hardware Compatibility

To obtain information about the components that are supported on the devices, and special compatibility guidelines with the release, see the Hardware Guide and the Interface Module Reference for the product.

To determine the features supported on PTX Series devices in this release, use the Juniper Networks Feature Explorer, a Web-based application that helps you to explore and compare Junos OS feature information to find the right software release and hardware platform for your network. Find Feature Explorer at: https://apps.juniper.net/feature-explorer/.

Hardware Compatibility Tool

For a hardware compatibility matrix for optical interfaces and transceivers supported across all platforms, see the Hardware Compatibility tool.

Release History Table
Release
Description
Starting in Junos OS Release 18.3R1, OpenConfig and Network Agent packages are bundled into the Junos OS image by default. Both packages support the Junos Telemetry Interface (JTI).