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.1R3 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.1R3 New and Changed Features

There are no new features or enhancements to existing features for PTX Series in Junos OS Release 18.1R3.

Release 18.1R2 New and Changed Features

There are no new features or enhancements to existing features for PTX Series in Junos OS Release 18.1R2.

Release 18.1R1 New and Changed Features

Hardware

  • New Routing Engine RE-PTX-X8-128G (PTX5000)—Starting in Junos OS Release 18.1R1, the RE-PTX-X8-128G Routing Engine is supported on the PTX5000 packet transport router. The Routing Engine has increased memory and storage to support node virtualization in future releases. The Routing Engine is equipped with an 8-Core 2.3-GHz processor, 128-GB memory, and 200-GB SSDs and also supports Secure Boot for enhanced boot security.

Class of Service (CoS)

  • Support for explicit-null packet classification using the EXP value from MPLS explicit-null labels (PTX Series)—The default classification for explicit-null packets is based on the payload (IPv4 or IPv6 DSCP bits). Starting with Junos OS 18.1R1, PTX Series routers with third-generation FPCs (FPC3) support a new CLI option, [explicit-null-cos inet|inet6] at the [edit forwarding-options] hierarchy level, that makes the packet classification based on the MPLS EXP value rather than on the payload, thus preserving the MPLS classification of the packet.

    [See explicit-null-cos.]

  • Support for enabling a queue's buffer space to be 100 percent of the interface’s buffer space (PTX Series)—Starting in Junos OS 18.1R1, PTX Series devices provide a new CLI option that enables you to set a queue’s buffer to be up to 100 percent of the interface’s buffer. This option allows the queue’s buffer to grow as large as 100 percent of the interface's buffer if and only if it is the only active queue for the interface. This option can be enabled by setting buffer-size shared at the [edit class-of-service schedulers scheduler-name] hierarchy level.

    [See buffer-size (Schedulers).]

Interfaces and Chassis

  • Support for the removal of child next-hop usage for aggregated Ethernet Interfaces and clients (PTX Series routers with FPC3-PTX-U2 and FPC3-PTX-U3)—Starting in Junos OS Release 18.1R1, Junos OS supports removal of child next-hop usage for aggregated Ethernet Interfaces and clients. Removal of child next-hop usage helps reduce the memory and CPU resources required to support aggregated Ethernet Interfaces and improves the overall system performance and scaling numbers. This feature is enabled by default if the network services mode on the router is configured to enhanced-mode. You can disable this feature by using the set chassis aggregated-devices disable-lag-enhanced. You must reboot the router for the configuration to take effect.

    Previously, each unicast next hop over aggregated Ethernet Interfaces resulted in creation of a number of children next hops as well. For an aggregated Ethernet Interface with 16 member links, addition of one unicast next hop over the aggregated Ethernet Interface results in installing total of 17 next hops. As a result, with aggregated Ethernet configuration, the number of next hops supported decreases in proportion to the number of aggregated Ethernet links.

    Note

    Child next-hop optimizations are supported for aggregated Ethernet interfaces, interfaces that make use of aggregated Ethernet interfaces, and for both unicast and multicast scenarios.

    [See Aggregated Ethernet Interfaces Overview.]

  • Upgraded SSD size and RAM size (PTX5000)—Starting in Junos OS Release 18.1R1, PTX5000, routers with the RE-PTX-X8-128G-S Routing Engine support Secure Boot BIOS. The SSD size and the RAM size of the Routing Engine is upgraded to 2x200 GB and 128 GB.

    [See Salient Features of the Routing Engines with VM Host Support].

Junos OS XML API and Scripting

Management

  • Enhancement to NPU memory sensors for Junos Telemetry Interface (PTX Series)—Starting with Junos OS Release 18.1R1, the format of telemetry data exported through gRPC for NPU memory and memory utilization implements prefix compression. This change reduces the payload size of data exported. The following example shows the new format:

    key: __prefix__

    str_value: /components/component[name='FPC0:NPU0']/properties/property

    key: [name='mem-util-edmem-size']/value

    uint_value: 12345

    Telemetry data is exported in key-value pairs. Previously, the data exported included the component and property names in a single key string.

    [See Guidelines for gRPC Sensors.]

  • Physical interface operational status sensor (int-exp) support on Junos Telemetry Interface (JTI) (PTX Series)—Starting with Junos OS Release 18.1R1, sensor int-exp (interface express) is supported to export interface operational UP and DOWN status at a user-configurable rate. This sensor leverages statistics out of the physical interface sensor, providing faster and more frequent operational status statistics. Only the physical interfaces’ operational status from the Flexible PIC Concentrator (FPC) is collected and reported. Statistics from the Routing Engine interface are not reported.

    You can apply the intf-exp sensor using the following paths:

    • Subscription path

      /junos/system/linecard/intf-exp/

    • OpenConfig path

      /interfaces_exp/interface_exp[name='et-x/y/z:ch']/state/oper-statusdetails

    Streaming telemetry data through gRPC requires you to download the OpenConfig for Junos OS module.

    [See Guidelines for gRPC Sensors (Junos Telemetry Interface).]

  • Expanded support for chassis sensors for Junos Telemetry Interface (MX Series and PTX3000 and PTX5000 Transport Series Routers)—Starting with Junos OS Release 18.1R1, Junos Telemetry Interface (JTI) provides new sensors that expand optics and power information.

    To export telemetry data from Juniper equipment to an external collector requires both Junos Telemetry Interface (JTI) and gRPC to be configured.

    Enhanced sensor information is also supported through operational mode commands show chassis fpc detail , show chassis power detail, and show chassis pic fpc-slot id pic-slot id.

    Streaming telemetry data through gRPC also requires you to download the OpenConfig for Junos OS module.

    [See Guidelines for gRPC Sensors (Junos Telemetry Interface).]

  • “ON CHANGE” sensor support through gRPC Network Management Interface (gNMI) for Junos Telemetry Interface (MX Series) (PTX Series)—Starting with Junos OS Release 18.1R1, ON_CHANGE streaming of Address Resolution Protocol (ARP), Network Discovery Protocol (NDP), and IP sensor information associated with interfaces is supported on Junos Telemetry Interface (JTI).

    Periodical streaming of OpenConfig operational states and counters has been supported since Junos OS Release 16.1, exporting telemetry data from Juniper equipment to an external collector. While useful in collecting all the needed information and creating a baseline “snapshot,” periodical streaming is less useful for time-critical missions. In such instances, you can configure ON_CHANGE streaming for an external collector to receive information only when operational states experience a change in state.

    To support ON_CHANGE streaming, Google has developed a new specification called gRPC Network Management Interface (gNMI) for the modification and retrieval of configurations from a network element. Additionally, the gNMI specification can be used to generate and control telemetry streams from a network element to a data collection system. Using the new gNMI specification, one gRPC service definition can provide a single implementation on a network element for both configuration and telemetry as well as a single NMS element to interact with a device by means of telemetry and configuration RPCs.

    Information about the RPCs supporting this feature can be found in the gNMI Proto file version 0.4.0 (the supported version) and the specification released by Google at:

    • https://github.com/openconfig/reference/blob/master/rpc/gnmi/gnmi-specification.md

    • https://github.com/openconfig/gnmi/blob/master/proto/gnmi/gnmi.proto

    The telemetry RPC subscribe under gNMI service supports ON_CHANGE streaming. RPC subscribe allows a client to request the target to send it values of particular paths within the data tree. Values may be streamed (STREAM), sent one-off on a long-lived channel (POLL), or sent one-off as a retrieval (ONCE).

    If a subscription is made for a top level container with a sample frequency of 0, leaves with ON_CHANGE support are streamed based on events. Other leaves will not be streamed.

    Note

    In order to permit a device to decide which nodes will be streamed as ON_CHANGE and which will SAMPLE, the collector should subscribe for TARGET_DEFINED with sample_interval.

    Streaming telemetry data through gRPC requires you to download the OpenConfig for Junos OS module.

    [See Understanding OpenConfig and gRPC on Junos Telemetry Interface.]

  • ON_CHANGE support for Junos Telemetry Interface (JTI) (PTX Series)—Starting with Junos OS Release 18.1R1, OpenConfig support through gRPC Remote Procedure Calls (gRPC) and JTI is extended to support client streaming and bidirectional streaming of telemetry sensor information.

    APIs have been implemented in Junos based on Protobuf specifications released by Google for OpenConfig. These APIs perform configuration, operational state retrieval, and telemetry on Junos routers using gRPC as the transport mechanism.

    Starting in Junos OS 18.1R1, client streaming and bidirectional streaming are supported. With client streaming, the client sends a stream of requests to the server instead of a single request. The server typically sends back a single response containing status details and optional trailing metadata. With bidirectional streaming, both client and server send a stream of requests and responses. The client starts the operation by invoking the RPC and the server receives the client metadata, method name, and deadline. The server can choose to send back its initial metadata or wait for the client to start sending requests. The client and server can read and write in any order. The streams operate completely independently.

    Junos devices can be managed through API (RPC) prototypes:

    • rpc Capabilities (CapabilityRequest)

      Returns (CapabilityResponse). Allows the client to retrieve the set of capabilities that is supported by the target.

    • rpc Get (GetRequest)

      Returns (GetResponse). Retrieves a snapshot of data from the target.

    • rpc Set (SetRequest)

      Returns (SetResponse). Allows the client to modify the state of data on the target.

    • rpc Subscribe (stream SubscribeRequest)

      Returns (stream SubscribeResponse). Allows a client to request the target to send it values for particular paths within the data tree. These values may be streamed (STREAM) or sent one-off on a long-lived channel (POLL), or sent as a one-off retrieval (ONCE). If a subscription is made for a top-level container with a sample frequency of 0, leaves with ON_CHANGE support are streamed based on events. Other leaves will not be streamed.

    Juniper Extension Toolkit (JET) support provides insight to users regarding the status of clients connected to JSD. JET support for gRPC includes expanding the maximum number of clients that can connect to JSD from 8 to 30 (the default remains 5). To specify the maximum number of connections, include the max-connections statement at the [edit system services extension-service request-response grpc] hierarchy level.

    To provide information regarding the status of clients connected to JSD, issue the enhanced show extension-service client information command and include the clients or servers options. The clients option displays request-response client information. The servers option displays request-response server information.

    [See Understanding OpenConfig and gRPC on Junos Telemetry Interface.]

MPLS

  • Support for static adjacency segment identifier for aggregated Ethernet member links (PTX Series)—Starting with Junos OS Release 18.1R1, you can configure a transit single-hop static label switched path (LSP) for a specific member link of an aggregated Ethernet (AE) interface, without enabling the enhanced-ip network services mode. A static labeled route is added with next-hop pointing to the AE member link of an aggregated interface. Label for these routes is picked from the segment routing local block (SRLB) pool of the configured static label range. This feature is supported for AE interfaces on PTX routers with FPC1, FPC2, and FPC3. The member-interface CLI statement is added under transit configuration to configure the AE member interface name. The static LSP label is configured from defined static label range.

    Note
    • In the previous release, this feature was supported only when the enhanced-ip network services mode was enabled.

    • If the ingress port for the OAM traffic is on FPC1 or FPC2, and the egress port (member link) has the Link Aggregation Control Protocol (LACP) Mux state as 'Detached', and the corresponding physical port (on FPC1, FPC2, or FPC3) is up, the traffic is forwarded at ingress.

    [See Configuring Static Adjacency Segment Identifier for Aggregate Ethernet Member Links Using Single-hop Static LSP.]

  • Support for segment routing statistics at the ingress (PTX Series)— Starting in Junos OS Release 18.1R1, the traffic statistics in a segment routing (SR) network can be recorded in an OpenConfig compliant format for Layer 3 interfaces. The statistics is recorded at the ingress for the Source Packet Routing in Networking (SPRING) traffic only, excluding RSVP and LDP-signaled traffic, and the family MPLS statistics per interface is accounted for separately. The SR statistics also includes SPRING traffic statistics per link aggregation group (LAG) member, and per segment identifier (SID).

    To enable recording of SR statistics, include the sensor-based-stats per-interface-per-member-link ingress statement at the [edit protocols isis source-packet-routing] hierarchy level.

    [See per-interface-per-member-link.]

Network Management and Monitoring

  • Enhancement to Junos OS SNMP MIB PCC funtionality (PTX Series)—Starting in Junos OS Release 18.1R1, Junos OS provides enhanced MIB support for Path Computation Clients. This enhancement enables the Path Computation Client (PCC) process to accept SNMP get and getnext commands for Path Computation Client Protocol (PCEP) peer and PCEP session tables and reply to them. This feature monitors PCEP interactions between a PCC and a Path Computation Element (PCE). Not all members of PCEP peer and PCEP session tables mentioned in the RFC (RFC 7420) are supported. For exceptions, see Standard SNMP MIBs Supported by Junos OS.

    [See MIB Explorer. Name of MIB is pcep.mib.]

Routing Policy and Firewall Filters

  • Filter-based GRE encapsulation (PTX Series)—Starting with Junos OS Release 18.1R1, for PTX Series routers running third-generation line cards, you can use tunnel-end-point commands to enable line-rate, filter-based, GRE tunneling of IPv4 and IPv6 payloads across IPv4 networks.

    This GRE encapsulation is not supported for logical systems, or for MPLS traffic, and the route lookup for GRE encapsulated traffic is supported on the default routing instance only.

    The following commands are introduced for this feature:

    set firewall tunnel-end-point tunnel-name gre.

    set firewall tunnel-end-point tunnel-name ipv4.

    set firewall tunnel-end-point tunnel-name ipv6.

    [See tunnel-end-point and Filter-Based Tunneling Across IPv4 Networks.]

  • Firewall filter enhancement for better resource optimization (PTX Series)—When an interface specific firewall filter is configured with multiple Interface bind point instances, the PTX Series Help software allocates resources for each interface instance separately, and the resources consumption is directly proportional to the number of bind points. For better resource optimization, a new scale-optimized configuration statement is introduced starting in Junos OS Release 18.1R1 that optimizes interface specific firewall filters in the Packet Forwarding Engine itself. The ingress and egress traffic cannot have the same scale-optimized filter configured.

    For more information, see Guidelines for Configuring Firewall Filters.

Routing Protocols

  • Support for BGP multipath at global level (PTX Series)—Starting with Junos OS Release 18.1R1, BGP multipath is available at the global level in addition to the group and neighbor level. In earlier Junos OS releases BGP multipath is supported only at the group and neighbor levels. A new configuration option disable is available at the [edit protocols bgp multipath] hierarchy level to disable BGP multipath for specific groups or neighbors. This allows you to configure BGP multipath globally and disable it for specific groups according to your network requirements.

    [See disable.]

Security

  • Secure Boot (PTX5000 with Routing Engine RE-PTX-X8-128G)—Starting in Junos OS Release 18.1R1, a significant system security enhancement, Secure Boot, has been introduced. The Secure Boot implementation is based on the UEFI 2.4 standard. The BIOS has been hardened and serves as a core root of trust. The BIOS updates, the bootloader, and the kernel are cryptographically protected and thus safeguarded from tampering or modification. By default, Secure Boot is enabled on supported routers.

    [See Feature Explorer and enter Secure Boot.]

Services Applications

  • Support for MPLS-over-UDP inner payload flow monitoring with IPFIX and version 9 formats (PTX Series) —Starting with Junos OS Release 18.1R1 on PTX Series routers with an FPC3, PTX10K-LC1101, PTX10K-LC1102, or PTX1000 card, you can perform flow monitoring for MPLS-over-UDP flows to look past the tunnel header to sample and report on the inner payload at both the transit and egress nodes of the tunnel. This feature supports MPLS IPv4 and IPv6 payloads and both IPFIX and version 9 templates. Only ingress sampling is supported.

    [See Inline Active Flow Monitoring of MPLS-over-UDP Flows on PTX Series Routers.]

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

Interfaces and Chassis

  • Modified output of the request vmhost zeroize command—The command request vmhost zeroize, upon execution, prompts the user for confirmation to proceed. The following line is displayed:

    See request vmhost zeroize.

  • Power supply alarm is not raised when the input switch status is OFF or power not connected (PTX10008, PTX10016)—Starting in Junos OS release 17.4R2 and 18.1R2, the power supply alarm A power supply input has failed will not be raised if INP1/INP2 switch status if OFF and the power is not connected. Earlier, an alarm is raised for the Power Entry Module (PEM) that are not powered on as Not Powered irrespective of the switch state. Now, to know the power supply status, execute show chassis power or show chassis power detail CLI command. The DC input is the new output parameter that provides information about the status of the input feed.

    Previous Behavior:

    user@host> show chassis power

    Current Behavior:

    user@host> show chassis power

    [See show chassis power.]

Management

  • Enhancement to LSP statistics sensor for Junos Telemetry Interface (PTX Series)—Starting with Junos OS 18.1R1, the telemetry data exported for the LSP statistics sensor no longer includes the phrase and source 0.0.0.0 after the LSP name in the value string for the prefix key. This change reduces the payload size of data exported. The following is an example of the new format:

    str_value: /mpls/lsps/constrained-path/tunnels/tunnel[name='LSP-4-3']/state/counters[name='c-27810']/

Network Management and Monitoring

  • SNMP syslog messages changed (PTX Series)—In Junos OS Release 18.1R1, 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.]

  • New context-oid option for trap-options configuration statement to distinguish the traps that come from a non-default routing instance and a non-default logical system (PTX Series)—Starting in Junos OS Release 18.1R3, 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.]

Network Operations and Troubleshooting Automation

  • JET - Correction to escaped characters notification events (PTX Series routers)–Per RFC7159, certain characters must be escaped. Data returned from JET notification subscriptions contained escaped characters that were not required. This has been corrected to comply with RFC7159.

  • respawn-on-normal-exit option added to [edit system extensions extension-service application file <application-name>] hierarchy (PTX Series routers)–This option helps to ensure that daemonized Juniper Extension Toolkit (JET) applications that exit normally will restart without user intervention. Daemonized JET applications that exit unexpectedly will still restart without user intervention. This is the default behavior.

Subscriber Management and Services

  • DHCPv6 lease renewal for separate IA renew requests (PTX Series)—Starting in Junos OS Release 18.1R3, 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.1R3 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

  • For CFP2-DCO-T-WDM-1 pluggable, Rx payload type is shown incorrectly (shown as 0 instead of 7). PR1300423

  • When a CFP2-DCO-T-WDM-1 plugged in a PTX Series PIC, when backward frr is enabled on the far end the convergence time is higher because extra delay (average 500 msec) is incurred in the triggering FRR, because of SW-based polling. PR1303820

  • EPR queue is not getting drained during FRR test, and the packets already in the queue timeout eventually, causing this interrupt. This is a minor alarm. PR1319520

  • This is expected behavior for TQ-chip ASICs. It is primarily due to strict-high priority queue and the shared shaper. Credits that are unused by an Output Queue (that is, the queue actual rate is less than the tx-rates) will cause the queue's credit bucket to reach its maximum value. Once a queue hits its maximum credit value, the remaining credits will be distributed to other queues. Once the other queues get transmit credits, they can then transmit. Thus with TQ-chip and the shared shaper, it is virtually impossible to completely shut off a queue by means of a guaranteed rate mechanism. PR1319923

  • Aggregated Ethernet MIX feature is not supported. PR1330204

Interfaces and Chassis

  • On PTX10008 and PTX10016 routers, if you remove the redundant Switch Interface Board (SIB) after upgrading Junos OS from Release 17.4R1 or Release 17.2X75-D90 to a later release, then an alarm is not generated. This is a known behavior and has no impact on the performance of the router.

Known Issues

This section lists the known issues in hardware and software in Junos OS Release 18.1R3 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

  • When a CFP2-DCO-T-WDM-1 is plugged into a PTX Series PIC, after repeated configuration rollback, link can take a long time to come up. PR1301462

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

  • Internal latency is high during initial subscription of sensors when multiple sensors (in order of 15-20) are subscribed together. This is not observed with lesser number of subscriptions. This is for a small period when sensors are being installed. PR1303393

  • This type of crash indicates simultaneous operation on an ephemeral instance. When a process wants to open an ephemeral configuration in merge view, some other activity (like purging, deletion/re-creation) is being carried out on this ephemeral instance. The occurrence of this core file is rare. PR1305424

  • Memory leak in chassisd daemon is noticed while streaming telemetry subscriptions are active. PR1315672

  • On PTX10000, 100G LR4 optics with Part Number 740-061409 will show as QSFP-100G-LR4-T2 instead of QSFP-100G-LR4 and optics that shows as QSFP-100G-LR4 is not supported on PTX10000. PR1322082

  • On PTX platform with FPC type 3, the error message could be observed when FPC card goes online or off-line. PR1322491

  • On PTX Series platforms with cards such as FPC1 and FPC2 and class of service (CoS) used, a high-priority queue might not get the entire configured bandwidth.. PR1324853

  • In a streaming telemetry scenario, if performing "commit full", the na-grpd daemon might restart, causing disconnection of streaming telemetry. PR1326366

  • If a filter is configured with the scale-optimized command, traffic-class-count will not increment. PR1334580

  • MPLS ingress LSP statistics are not supported. PR1337814

  • The issue is with interoperability of TQ- chip with PTX Series routers based line cards. PR1339481

  • RHI interface on PTX Series router can carry a maximum of 4 Mbps of traffic on OQ1 and hence NDP, which is mapped to OQ1 and a bandwidth assigned earlier of 500 pps is reduced to 100 pps due to this limitation. PR1345938

  • PTX3000 reports chip to chip link (CCL) CRC errors while FPC3-SFF-PTX-1X is offlined through the 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@router> show chassis hardware detail Hardware inventory: FPC 0 REV 43 750-057064 ACPV7514 FPC3-SFF-PTX-1X CPU BUILTIN BUILTIN SMPC PMB FPC 2 REV 40 750-057064 ACPJ9145 FPC3-SFF-PTX-1X CPU BUILTIN BUILTIN SMPC PMB FPC 4 REV 43 750-057064 ACPR8506 FPC3-SFF-PTX-1X CPU 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

  • If the output firewall filter is configured with the "syslog" option, the host interface might be wedged on a PTX1000 or a PTX Series platform with FPC type 3. PR1354580

Infrastructure

  • A file system corruption might create a kernel core file. The Routing Engine reboots with the message ffs_blkfree: freeing free block. PR1028972

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 crash the cfmd process. This is because of using the older version of /var/db/cfm.db. PR1281073

MPLS

  • When the rpd daemon is terminating, the process of signaling the deletion of all RSVP LSPs might take so long that a watchdog timer begins firing, resulting in an rpd core file. PR1257367

Resolved Issues

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

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.1R3

General Routing

  • On a PTX1000, upgrade from Junos OS Release 16.1X65D45 to Junos OS Release 17.3-20170721 fails frequently with sampling enabled. PR1296533

  • FPC is being reported down in chassisd logs related to Streaming Telemetry, whereas the FPC is online. PR1300795

  • PTX10000: Suppress chassis alarm for switched off PEMS. PR1311574

  • PTX10000: Do not bounce FPC without warning or alarm for different port speed settings. PR1311875

  • MPLS traceroute fails across PTX Series platforms. PR1327609

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

  • Telemetry software package is not running after system is returned to zero. PR1336004

  • FPC got rebooted a few minutes after loading the configuration. PR1346467

  • Threshold is not getting configured correctly in PTX Series router when threshold is configured using scope and category options. PR1350841

  • BFD sessions do not come up on PTX3000. PR1352112

  • The interface of 15 100G ports PIC might delay 60 seconds to come up. PR1357410

  • P2MP LSP replication traffic loss occurs on aggregated Ethernet bundle after member link goes down on PTX Series router. PR1359974

  • The route might be stuck after BGP neighbor and route flapping. PR1362560

  • The traffic is still forwarded through the member link of an aggregated Ethernet bundle interface even with the "Link-Layer-Down" flag set. PR1365263

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

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

MPLS

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

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

Platform and Infrastructure

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

  • Traffic black hole is seen along with JPRDS_NH:jprds_nh_alloc(),651: JNH[0] failed to grab new region for NH messages. PR1357707

Routing Protocols

  • Protocol churn will create rpd crash. PR1341466

  • Rpd core might be seen while running streaming telemetry. PR1347431

Resolved Issues: 18.1R2

General Routing

  • Remove show chassis spmb command/response. PR1244059

  • De-encapsulated GRE traffic is not passing to the egress port upon initial customer configuration. PR1325104

  • On PTX5000 line packet transport routers with FPC3 linecards, PTX10000 line, and PTX1000 line output firewall filters that are configured with syslog and discard actions do not perform the syslog action. PR1328426

  • PTX10000 line card might reboot continuously after upgrading to Junos OS Release 17.2R1 or later if HMC BIST fails. PR1330618

  • Traffic stops flowing out of ae70 after some FPC restart iterations. PR1335118

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

  • FPC/FPC2/FPC E on PTX Series does not forward traffic. PR1339524

  • PTX1008: 30-Port Coherent Line Card (DWDM-lC) does not come up. PR1344732

Interfaces and Chassis

  • On PTX3000 line, when CPM is configured, the CFM filter is not getting programmed. The command show oam ethernet connectivity-fault-management is not checking interfaces ae0.0 extensive. PR1335305

Platform and Infrastructure

  • On PTX1000 and QFX10002-60C: Python scripts/shell scripts cannot be executed during ZTP because veriexec is enabled. PR1334425

Routing Protocols

  • The rpd might constantly consume high CPU in BGP setup. PR1315066

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

  • On PTX1000, rpd core file is generated at ispfc_incrementally_mend_one_postf_sp_tree (postf_spf_res= <optimized out>, topo= <optimized out>) at ../../../../../../../../src/junos/usr.sbin/rpd/lib/igp-spf-compute/igp_spf_compute_ti_lfa.c:3364. PR1339296

Resolved Issues: 18.1R1

General Routing

  • restart na-grpc-server and restart na-mqtt for MTRE does not work. PR1284121

  • Traffic passing LSP with entropy label might be dropped after the bypass path goes down. PR1291036

  • The routing protocol process (rpd) might generate a core file while restarting the process from the CLI. PR1291110

  • Incorrect SNMP OID values are sent in SNMP traps for removal or insertion of front panel display on PTX Series routers. PR1294741

  • LINK LED is red when the port is disabled on PTX Series routers. PR1294871

  • Classifier binding for logical interface (IFL) is lost when changing from trunk to access with L2 classifier configured. PR1295043

  • After deleting and re-adding an interface that had a classifier bound, the binding to the default classifier is not restored. PR1295477

  • FPC might crash after Routing Engine switchover. PR1296282

  • An mgd core file is generated when downgrading from Junos OS Release 17.3-20170721 to Junos OS Release 16.1X65D40.2. The mgd core file is overwritten if downgrading is attempted multiple times. PR1296504

  • On a PTX1000, upgrade from Junos OS Release 16.1X65D45 to Junos OS Release 17.3-20170721 fails frequently with sampling enabled. PR1296533

  • Upon configuring protect core, rpd keeps thrashing at rt_attrib.c - nhp->rtn_n_gw > 1 && nhp->rtn_n_gw <= 64. PR1297044

  • Alarms and syslog errors are seen with priority strict-high on an AF4 queue, on the oversubscription cases (1X100G egress to 1X10G egress setup). PR1297343

  • Link errors alarm messages might be seen after migrating to FPC3 on PTX3000. PR1298841

  • The disable-pfe action upon Hybrid Memory Cube (HMC) fatal errors might have a system-wide impact on PTX Series platforms. PR1300180

  • On PTX3000 platforms, powering on a FPC (PTX-IPLC-B-32) card might cause the other FPC cards to reboot. PR1302304

  • The third-generation FPC (FPC3-SFF-PTX) might not boot on a PTX3000 with the Control Board or Routing Engine. PR1303295

  • On PTX3000 and PTX5000 platforms, the 100G interfaces might not come up. PR1303324

  • If MPLS LSP self-ping is enabled (self-ping is enabled by default), the kernel might panic with the error message Fatal trap 12: page fault while in kernel mode. PR1303798

  • Repeated log messages %PFE-3 fpcX expr_nh_index_tree_ifl_get and expr_nh_index_tree_ipaddr_get are observed when the sampling packet is discarded with log (or syslog) command under the firewall filter. PR1304022

  • The interface hold-time down timer does not take effect on PTX5000 with optical interface. PR1307302

  • Packet Forwarding Engine error messages are flooding as expr_sensor_update_cntr_to_sid_tree after deleting and rolling back protocols isis source-packet-routing node-segment. PR1309288

  • After ZTP gets completed, the configuration on the backup Routing Engine is rolled back to the factory-default configuration in a few minutes. PR1310117

  • The SIB LED on the FPD goes to green steady state even before an SIB comes online. PR1311632

  • PTX Series routers might fail to grab a new region for the next hop during a link flap. PR1311850

  • Rpd core observed after multiple session flaps on scale setup. PR1312169

  • The 10g interface might flap if it is set to 100g speed. PR1315079

  • Continuous logs from vhclient are seen for all the commands executed. PR1315128

  • ZTP config file fails to be loaded and committed, Cannot open configuration file /config/auto_image_upgrade.conf. PR1315857

  • The physical interfaces (IFDs)might generate framing errors when ports are connected to an odd interface. PR1317827

  • After jack-out/jack-in FPCs show "No-Power" for some time; however, FPCs eventually come up. PR1319156

  • No traffic is flowing with IPV6 payload prefixes on PTX Series platform. PR1319273

  • The rpd might crash when OpenConfig package is upgraded with JTI streaming data in the background. PR1322553

  • The aggregated Ethernet interface might be in an error blocked state after enabling and disabling aggregated Ethernet member link in a large scale of routes scenario. PR1323398

  • Fan tray 0(FAN-PTX-V-S) Failure alarm is set and cleared on multiple PTX Series routers. PR1324905

  • On PTX1000, the local time on FPC might be different from the local time on Junos VM host. PR1325048

  • Firewall filter is not supported on aggregated Ethernet. PR1325237

  • On PTX5000 w/ FPC3 linecards, PTX10000, and PTX1000 platforms, output firewall filters that are configured with "syslog" and "discard" actions do not perform the "syslog" action. PR1328426

  • Sensor configuration is not deleted from ephemeral database after collector disconnects. PR1329134

  • Additional TX reset during link-down events can cause link instabilities. PR1330708

  • PTX FPC might reboot in certain rare scenarios when an flapping interface configuration is committed. PR1335161

Infrastructure

  • ixlv interface statistics not accounting properly. PR1313364

  • PTX device may get to abnormal state due to the malfunction of the protection mechanism for F-Label. PR1336207

Interfaces and Chassis

  • The transportd might crash when SNMP 1335438query on jnxoptIfOChSinkCurrentExtTable with unsupported interface index. PR1335438

MPLS

  • Traffic drop occurs during NSR switchover for RSVP P2MP provider tunnels used by MVPN. PR1293014

  • Traffic loss occurs for static LSP configured with the stitch command. PR1307938

  • Rpd crashes on backup Routing Engine due to memory exhaustion. PR1328974

Platform and Infrastructure

  • Continuous log messages occur: for example: tftpd[23724]: Timeout #35593 on DATA block 85. PR1315682

  • PTX1000 & QFX10002-60C: Python scripts/shell scripts cannot be executed during ZTP as veriexec is enabled. PR1334425

Routing Protocols

  • With BGP LU FRR in an inter-AS scenario, a very high FRR time is visible once the link is up. PR1307258

  • Assignment of Sub-TLV values for segment routing TE policy Sub-TLVs occurs. PR1315486

  • The rpd process might crash continuously on both Routing Engines when "backup-spf-options remote-backup-calculation" is configured in IS-IS protocol. PR1326899

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

Documentation Updates

This section lists the errata and changes in Junos OS Release 18.1R3 documentation for the PTX Series.

New Simplified Documentation Architecture

  • With the release of Junos OS Release 18.1, Juniper is simplifying its technical documentation to make it easier for you to find information and know that you can rely on it when you find it. In the past, we organized documentation about Junos OS software features into platform-specific documents. In many cases, features are supported on multiple platforms, so you might not easily find the document you want for your platform.

    With Junos OS Release 18.1, we have eliminated the platform-specific software feature documents. For example, if you want to find documentation on OSPF, there is only one document regardless of which platform you have. Here are some of the benefits of our new simplified architecture:

    • Over time, you will see better search results when looking for Juniper documentation. You will be able to find what you want faster and be assured that is the right document.

    • If a software feature is supported on multiple platforms, you can find information about all the platforms in one place.

    • Because we have eliminated many documents that covered similar topics, you will now find one document with all the information.

    • You can know that you are always getting the most current and accurate information.

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.

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.1, 17.2, and 17.3 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.

You cannot upgrade directly from a non-EEOL release to a 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 acting as the backup Routing Engine.

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

Basic Procedure for Upgrading to Junos OS Release 18.1

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 Junos OS Administration Library.

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.1R3:

  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

    After you install a Junos OS Release 18.1R3 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.

    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 for 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.

    Customers in the United States and Canada, use the following command:

    user@host> request system software add validate reboot source/jinstall-18.1R3.SPIN-domestic-signed.tgz

    All other customers, use the following command:

    user@host> request system software add validate reboot source/jinstall-18.1R3.SPIN-export-signed.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 (available only for Canada and U.S. version)

    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.1 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.

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://pathfinder.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.