Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

What’s New


Learn about new features introduced in Junos OS Evolved Release 19.2R1 for the PTX10003.

Class of Service

  • Support for Class-of-Service (CoS) features for 25G interfaces (PTX10003)—Starting with Junos OS Evolved 19.2R1, support is provided for Class-of-Service (COS) features at 25G port speeds on PTX Series routers.

    [See Understanding Class of Service.]

General Routing

  • IPv6 traffic can transport over IPv4 MPLS core network (PTX10003)—Starting in Junos OS Evolved Release 19.2R1, the provider edge (PE) routers can hold all the advertised IPv6 routes in the PE router’s global IPv6 table.

  • Segment routing (PTX10003)—Starting in Junos OS Evolved Release 19.2R1, segment routing is supported. Source packet routing or segment routing is a control-plane architecture that enables an ingress router to steer a packet through a specific set of nodes and links in the network without relying on the intermediate nodes in the network to determine the actual path it should take. In this context, the term source means “the point at which the explicit route is imposed.” The following subfeatures of segment routing are supported in Junos OS Evolved Release 19.2R1:

    • Advertising MPLS labels in IS-IS

    • Advertising MPLS labels in OSPF

    • Configurable Segment Routing Global Blocks Label Ranges for SPRING protocols (ISIS only)

    • Support for SPRING anycast and prefix segments in ISIS

    • Adjacency segment identifier (SID) support for different use cases (ISIS)

    • BGP binding SID (draft-previdi-idr-segment-routing-te-policy)

    • LDP mapping client/server support (LDP, SPRING,ISIS)

    • Static segment routing (SR) LSP with label stack (non-color)

    • Topology independent loop free alternate (TI-LFA) procedures for Link, SR-LG protection (ISIS)

    [See Understanding Source Packet Routing in Networking (SPRING).]

  • PCEP support (PTX10003)—Starting in Junos OS Evolved Release 19.2R1, PCEP is supported on the PTX10003.

    [See PCEP Overview.]

Interfaces and Chassis

  • Support for 25-Gigabit Ethernet (PTX10003)—Starting with Junos OS Evolved release 19.2R1, the PTX10003-80C now supports 25-Gigabit Ethernet in addition to 40-Gigabit Ethernet, 100-Gigabit Ethernet and 2x100-Gigabit Ethernet. Using QSFP-28 optical transceivers, you can channelize a 100-Gigabit Ethernet port into four independent 25-Gigabit Ethernet interfaces and then use breakout cables to connect the channelized ports to other devices. Similarly, using QSFP28-DD optical transceivers, you can channelize a 2x100-Gigabit Ethernet port into eight independent 25-Gigabit Ethernet interfaces. The 25-Gigabit Ethernet ports support FEC modes FEC74, FEC91 and NONE.

    [See Channelizing Interfaces on PTX10003 Routers

  • Virtual routing and forwarding (VRF) support (PTX10003)—Starting in Junos OS Evolved Release 19.2R1, there is VRF table and L3VPN support.

  • Support for physical interface damping (PTX10003)—Starting with Junos OS Evolved Release 19.2R1, the physical interfaces on your device support interface damping to address periodic flapping with long up and down durations (in seconds). Interface hold timers can address very short-duration, instantaneous flapping (in milliseconds), but not the longer duration flaps. When you configure interface damping, an exponential back-off algorithm suppresses reporting of interface up and down events to the upper-level protocols.

    To configure damping on a physical interface, include the damping statement at the [edit interfaces interface-name] hierarchy level. To view the damping values and link state, run the show interfaces extensive command.

    [See Damping Longer Physical Interface Transitions.]

  • 25-Gbps channelized interfaces (PTX10003)—Starting with Junos OS evolved Release 19.2R1, you can channelize QSFP28 and QSFP-DD ports on your PTX10003 routers to achieve the following interface speed configurations:

    • Four 25-Gbps interfaces on the 100-Gigabit Ethernet QSFP28 ports

    • Eight 25-Gbps interfaces on the 200-Gigabit Ethernet (2x100-Gbps) QSFP-DD ports

    To configure the port speed as 25 Gbps, use the set chassis fpc fpc-slot pic pic-slot port port-num number-of-subports (4|8) speed 25g command.

    [See Channelizing Interfaces on PTX10003 Routers.]

Junos Telemetry Interface

  • Support for JTI (PTX10003)—Starting in Junos OS Evolved Release 19.2R1, Junos telemetry interface (JTI) supports the remote collection of statistics using gRPC services through BGP neighbors, LSP, and RSVP sensors.


  • Open-R (PTX10003)—Starting in Junos OS Evolved Release 19.2R1, Open-R (a third-party application developed by Facebook) runs on platforms running Junos OS Evolved.


  • Multicast-related features (PTX10003)—Starting in Junos OS Evolved Release 19.2R1, the following multicast features are supported:

    • IP multicast (PIM/IGMP)

    • Protocol Independent Multicast sparse mode (PIM SM) for IPv4 and IPv6

    • Protocol Independent Multicast source-specific multicast (PIM SSM)

    • MLDP Protocol Independent Multicast (PIM) for IPv6 multicast

    • BGP link state distribution

    The following multicast features are not supported:

    • MPLS P2MP/ P2MP

    • Bidirectional PIM support (PTX5000)

Network Management and Monitoring

  • Syslog clients in Routing-Instance (PTX10003)—A new configuration for routing-instance is introduced at appropriate hierarchies that lets you specify the routing instance through which the remote server is reachable. The syslog client can now send log messages to servers that are reachable through user defined VRFs.

    [See Management Interface in a Nondefault Instance.]

Routing Protocols

  • BGP flow specification (PTX10003)—Starting in Junos OS Evolved Release 19.2R1, BGP can carry flow-specification network layer reachability information (NLRI) messages on PTX10003 routers. Propagating firewall filter information as part of BGP enables you to propagate firewall filters against denial-of-service (DOS) attacks dynamically across autonomous systems.

    The following match conditions are not supported:

    • ICMP Codes alone [INET/INET6]

    • Source/Destination Prefix with offset [ASIC Limitation] for INET6

    • Flow label [ASIC Limitation] for INET6

    • Fragment [for INET6]

    The following actions are not supported:

    • Traffic Marking (INET6) [ASIC Limitation]

  • Distributed BFD and BFD-triggered local repair support (PTX10003)—Starting with Junos OS Evolved Release 19.2R1, the distributed BFD.

    [See Understanding Distributed BFD]

  • BGP Service APIs support (PTX10003)—Starting with Junos OS Evolved Release 19.2R1, the following BGP service APIs are supported:

    • BGP-labeled unicast (BGP-LU) and segment routing policy for traffic engineering (SRTE)—BGP-LU is the label signaling and routing protocol that provides the edge-to-edge or PE to PE reachability. SRTE uses a policy to steer traffic through the network and its support with BGP simplifies the data center network operation.

    • Community based BGP lookup

    • Implement RFC 7947—Attribute transparency and multiple route server routing tables sections

    • Provide programmability for external BGP routes (EBGP) and for injecting routes into route server client routing tables

    • Route server functionality to applicable address families. The virtual route server (vRS) specifically requires support for IPv4, IPv6, and VPNv4.

    [See Junos OS routing IDL - Protocol Documentation.]

Software Installation and Upgrade

  • Component-level upgrade available (PTX10003)—The command for upgrade provides for restarting applications and nodes in an optimal manner. You use one upgrade command, request system software add, and by default, the upgrade process identifies and upgrades only those components that differ in the target release. An option to the upgrade command allows you to perform the equivalent of a cold boot upgrade should it be required. Output specifies whether the software is upgraded using cold boot or by application restart.

    [See request system software add.]