Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Additional Features

We've extended support for the following features to these platforms.

  • Additional family in port mirroring (PTX10002-36QDD). You can configure family any (as well as the earlier family options, inet and inet6) for local port mirroring and remote port mirroring. You use family any for family any, ccc, ethernet-switching, or mpls.

    Note:

    You use the family any configuration option to process all four families.

    You no longer configure port mirroring by using the [edit forwarding-options port-mirroring analyzer] hierarchy on the PTX devices. You now use [edit forwarding-options port-mirroring] for local port mirroring or [edit forwarding-options port-mirroring instance instance-name] for remote port mirroring, with both of those configurations also requiring a firewall filter.

    The following configuration statements are no longer part of the port mirroring configuration on PTX:

    • next-hop for family any

    • family vpls

    • no-filter-check

    • hosted-service

    • server-profile

    [See Example: Configure Port Mirroring with Family any and a Firewall Filter and port-mirroring.]

  • Avoid microloops in IS-IS SRv6 networks (PTX10002-36QDD). You can enable post-convergence path calculation on a device to avoid microloops if a link or metric changes in an SRv6 network.

    [See How to Configure Microloop Avoidance for IS-IS in SRv6 Networks.]

  • BGP autodiscovery underlay in EVPN-VXLAN (ACX7100-32C, ACX7100-48L, PTX10001-36MR, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5700, and QFX5220)

    [See BGP Auto-Discovered Neighbors.]

  • Connectivity fault management and enhanced CFM (PTX10002-36QDD). Support includes:

    • Up and down maintenance association end points (MEPs) on bridges, circuit cross-connect (CCC), and Ethernet VPN (EVPN) in inline mode

    • ITU-T Y.1731 on synthetic loss measurement (SLM) and delay measurement (DM)

    • Inline session support for connectivity fault management (CFM) on aggregated Ethernet

    • Enhanced CFM mode by default

    • Supported inline performance monitoring (PM) sessions include:

      • PM Tx

      • PM Rx

      • PM responder

    • IPv4 (inet) and IPv6 (inet6) support for continuity check messages (CCM), delay measurement (DM), and synthetic loss message (SLM)

    • DM on aggregated Ethernet with at least one child link on the anchor Packet Forwarding Engine

    • Action profile for marking a link down, except for EVPN and bridge up MEP

    • Supported CFM protocol data units (PDUs) for inline handling include:

      • CCM

      • Delay measurement message (DMM)

      • Delay measurement reply (DMR)

      • Synthetic loss message (SLM)

      • Synthetic loss reply (SLR)

    • Enterprise and service provider configurations

    • VLAN normalization

    • VLAN transparency for CFM PDUs

    • CoS forwarding class and CoS packet loss priority (PLP) for CFM

    • Combination of up MEP, down MEP, or maintenance association intermediate point (MIP) configuration over the same interface

    [See Connectivity Fault Management (CFM).]

  • CoS interface telemetry support (PTX10002-36QDD). Support for gRPC Network Management Interface (gNMI) streaming of CoS interface queue statistics. To stream statistics, use the resource path /qos/interfaces/interface/output/queues/queue/state/.

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

  • EVPN-VXLAN fabric with an IPv6 underlay (PTX10002-36QDD). Support includes:

    • Quality of service (QoS) and class of service (CoS) classification with explicit congestion notification (ECN) copy upon VXLAN tunnel encapsulation and de-encapsulation.

      Priority-based flow control (PFC), differentiated services code point (DSCP) copy, and IEEE 802.1p rewrite are not supported.

    • Dynamic Host Configuration Protocol (DHCP) relay with DHCPv4 and DHCPv6.

    [See EVPN-VXLAN with an IPv6 Underlay and Example: Configure an IPv6 Underlay for Layer 2 VXLAN Gateway Leaf Devices.]

  • EVPN-VXLAN L2 gateways and L3 gateways with EVPN Type 5 routes (PTX10002-36QDD).

    Support includes:

    • Ethernet VPN–Virtual Extensible LAN (EVPN-VXLAN) Layer 2 (L2) and Layer 3 (L3) gateway operations in edge-routed bridging (ERB) overlay and centrally routed bridging (CRB) overlay fabrics

    • EVPN instances using the MAC-VRF instance type with VLAN-based, VLAN-bundle, or VLAN-aware bundle service types

    • Pure EVPN Type 5 (IP prefix) route virtual routing and forwarding (VRF) model

    • Integrated routing and bridging (IRB) for IPv4 and IPv6 data traffic

    • Q-in-Q dual tagging for VXLAN network identifier (VNI) mapping with service provider-style logical interface configurations only

    • Overlapping VLAN IDs across MAC-VRF instances

    • Underlay reachability over ECMP

    • Active/active multihoming with Ethernet segment identifiers (ESIs) per physical interface

    • Proxy Address Resolution Protocol (ARP) and proxy Network Discovery Protocol (NDP), and ARP or NDP suppression

    • Multicast IRB support without IGMP snooping or MLD snooping

    • IEEE 802.1p and Differentiated Services code point (DSCP) class of service (CoS) on EVPN-VXLAN tunnel interfaces, with both service provider-style or enterprise-style interface configurations (including classification and rewrite operations, but not DSCP copy support)

    [See EVPN User Guide.]

  • Firewall filtering using flood policer, IRB, and service provider egress filtering (PTX10002-36QDD). You can use the flood policer feature to control flooding of the network with broadcast, unknown unicast, and multicast (BUM) traffic, and this control includes the EVPN flood policer.

    Note:

    EVPN-MPLS configurations also support flood policers.

  • IGMP snooping and MLD snooping (PTX10002-36QDD)

    [See IGMP Snooping Overview and Understanding MLD Snooping.]

  • Inline active flow monitoring for IPv4 and IPv6 traffic using IP Flow Information Export (IPFIX) and version 9 templates (PTX10002-36QDD)

    [See Understand Inline Active Flow Monitoring.]

  • Inline active flow monitoring using IP Flow Information Export (IPFIX) and version 9 templates for IRB interfaces and BGP next-hop addresses (PTX10002-36QDD). We now support:

    • IPv4 and IPv6 traffic on IRB interfaces.

    • A BGP next-hop address in the IPv6 and MPLS-IPv6 templates. Information Element 63, IPv6 BGP NextHop Address, is now available.

    [See Inline Active Flow Monitoring on IRB Interfaces and Understand Inline Active Flow Monitoring.]

  • IP-IP tunnel stitching (PTX10002-36QDD).

    [See Overview of Next-Hop-Based Dynamic Tunneling Using IP-Over-IP Encapsulation and Example: Configuring Next-Hop-Based IP-Over-IP Dynamic Tunnels.]

  • Layer 2 and Layer 3 support for flood policers (PTX10002-36QDD). You can configure firewall filters for flood policers on Layer 2 (family ccc) and Layer 3 (family any) traffic, in both the ingress and egress directions. Most match conditions (except packet-length) and most actions are supported.

  • Next-hop-based dynamic tunnels with IPv6 in the underlay network (PTX10002-36QDD). You can encapsulate IPv4 and IPv6 packets inside the IPv6 packets between two IPv6 nodes. This encapsulation mechanism helps to create next-hop-based dynamic tunnels with IPv6 in the underlay network.

    [See Next-Hop-Based Dynamic Tunnels and show dynamic-tunnels database.]

  • OAM ping support for SRv6 network programming (PTX10002-36QDD, PTX10004, PTX10008, and PTX10016). You can perform an Operations, Administration and Management (OAM) ping operation for any Segment Routing with IPv6 (SRv6) segment identifier (SID) whose behavior allows upper layer header processing for an applicable OAM payload.

    [See ITU-T Y.1731 Ethernet Service OAM Overview How to Enable SRv6 Network Programming in IS-IS Networks.]

  • On-box aggregation support (PTX10002-36QDD).

    [See Junos YANG Data Model Explorer.]

  • OpenConfig QoS operational state sensors (PTX10002-36QDD).

    [See Telemetry Sensor Explorer.]

  • OpenConfig QoS queue management profile and ECN configuration (PTX10002-36QDD).

    [See Mapping OpenConfig QoS Commands to Junos Configuration.]

  • Optimized intersubnet multicast (OISM) for IPv4 multicast traffic in EVPN-VXLAN fabrics (PTX10002-36QDD). Support on this device includes:

    • Regular OISM mode only—the original symmetric bridge domains model, also called the bridge domains everywhere (BDE) model

    • MAC-VRF EVPN instances with vlan-based or vlan-aware service types only

    • IPv4 multicast traffic with IGMPv2, IGMPv3, and IGMP snooping

    • Server leaf, border leaf, or lean spine OISM device roles

    • External multicast source and receiver communication using any of the following methods:

      • Classic Layer 3 (L3) interfaces

      • EVPN multicast VLAN (M-VLAN) integrated routing and bridging (IRB) interfaces

      • Non-EVPN IRB interfaces

    [See Optimized Intersubnet Multicast in EVPN Networks.]

  • QoS configuration and streaming with OpenConfig (PTX10002-36QDD).

    [See Mapping OpenConfig QoS Commands to Junos Configuration and Junos YANG Data Model Explorer.]

  • Static VXLAN L2 gateway overlays (PTX10002-36QDD)

    [See Static VXLAN, remote-vtep-list, and static-remote-vtep-list.]

  • QSFP-100G coherent ZR optics performance monitoring (ACX7024, ACX7348, and PTX10001-36MR; and the PTX10004, PTX10008, and PTX10016 with the PTX10K-LC1201-36CD and PTX10K-LC1202-36MR line cards installed). Monitor the performance of QSFP-100G coherent ZR optics and receive threshold-crossing alert (TCA) information to efficiently manage the optical transport link. Accumulate performance metrics into 15-minute and 1-day interval bins. Use the show interfaces transport pm command to view current and historical performance data.

    [See optics-options, and show interfaces transport pm.]

  • Redistribution of IPv4 routes with IPv6 next hop into BGP (PTX10002-36QDD). Devices can forward IPv4 traffic over an IPv6-only network, which generally cannot forward IPv4 traffic. As described in RFC 5549, IPv4 traffic is tunneled from CPE devices to IPv4-over-IPv6 gateways. These gateways are announced to CPE devices through anycast addresses. The gateway devices then create dynamic IPv4-over-IPv6 tunnels to remote CPE devices and advertise IPv4 aggregate routes to steer traffic. Route reflectors with programmable interfaces inject the tunnel information into the network. The route reflectors are connected through IBGP to gateway routers, which advertise the IPv4 addresses of host routes with IPv6 addresses as the next hop.

    [See Understanding Redistribution of IPv4 Routes with IPv6 Next Hop into BGP.]

  • SRv6 flexible algorithms in TED and BGP-LS (PTX10002-36QDD). The router supports Segment Routing for IPv6 (SRv6) flexible algorithms in the traffic engineering database (TED) and in BGP Link State (BGP-LS).

    [See Flexible Algorithms in IS-IS for Segment Routing Traffic Engineering and BGP Link-State Extensions for Source Packet Routing in Networking (SPRING).]

  • Static route tracking using the results of RPM and TWAMP tests (ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7024, ACX7024X, PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, and PTX10016). We've extended support for static route tracking to Junos OS Evolved and included Two-Way Active Measurement Protocol (TWAMP) test support as well. You use RPM or TWAMP probes to detect link status and to change the preferred-route state on the basis of the probe results. Tracked static routes can be IPv4 or IPv6, and each IPv4 and IPv6 tracked static route supports up to 16 next hops. You can also configure the metric, route preference, and tag values for each IPv4 or IPv6 destination prefix. However, you configure this feature differently on Junos OS Evolved devices; you configure the sla-tracking statement at the [edit routing-options] hierarchy level. For Junos OS, you would configure the rpm-tracking statement at the same hierarchy level.

    [See Understanding Using Probes for Real-Time Performance Monitoring on M, T, ACX, MX, and PTX Series Routers, EX and QFX Switches, Understand Two-Way Active Measurement Protocol, sla-tracking, and show route sla-tracking.]

  • Support for automatic ingress LSP Policing in P2MP LSPs (PTX10002-36QDD).

    [See Configuring Automatic Policers.]

  • Support for basic Layer 2 features (PTX10002-36QDD). The PTX10002-36QDD router supports the following Layer 2 basic learning, bridging and flooding features:

    • Enterprise-style bridging (support both trunk and access mode)

    • Service provider-style bridging (also known as sub-interface mode)

    • Handle BUM (broadcast, unknown unicast and multicast) traffic, including split horizon

    • MAC learning and aging

    • Static MAC addresses

    • Trunk port and VLAN membership

    • 802.1Q EtherType—8100

    • 802.1Q VLAN tagging—Single tagging with normalized to bridge domain tag at ingress

    • Clearing all MAC address information

    • Global MAC limit

    • Global source MAC aging time

    • MAC moves

    • LACP and LLDP

    • Disabling MAC learning at global and interface level

    • Native VLAN ID for Layer 2 logical interfaces

    • Single VLAN-tagged Layer 2 logical interfaces

    • Interface statistics

      Note:

      The show ethernet-switching statistics command and child logical interface statistics for aggregated Ethernet are not supported.

    • Flexible Ethernet services

      Note:

      Enterprise-style Layer 2 logical interfaces aren't allowed under the flexible-ethernet-services encapsulation.

    • Virtual switch

    • Persistent MAC learning (sticky MAC)

    • Service provider bridging:

      • Multiple logical interfaces on the same physical interface that are part of the same bridge domain

      • Ethernet bridge encapsulation

    [See Layer 2 Bridging, Address Learning, and Forwarding User Guide.]

  • Support for flexible algorithms for SRv6 in IS-IS (PTX10002-36QDD, PTX10004, PTX10008, and PTX10016). Configuration of segment routing in a core IPv6 network without an MPLS data plane supports these flexible algorithm (flex algo) features in IS-IS networks:

    • Advertisement of a Segment Routing Extension Header (SRH) locator with a mapped flexible algorithm

    • Use of application-specific link attributes (ASLA) for flexible algorithms

    • Configuration of a TI-LFA backup path for SRv6

    • Use of application-specific link attributes (ASLA) for flexible algorithms

    • Compression of SRv6 addresses into a single IPv6 address (micro-SID) in flex algo path computations

    [See How to Enable SRv6 Network Programming in IS-IS Networks.]

  • Support for G.8275.1 profile, PTP over Ethernet encapsulation, and hybrid mode over LAG with PTP over Ethernet (PTX10002-36QDD).

    [See G.8275.1 Telecom Profile, Guidelines for Configuring PTP over Ethernet, andHybrid Mode.]

  • Support for the gRPC Network Operations Interface (gNOI) certificate management cert service (PTX10002-36QDD). You can execute supported cert service remote procedure calls (RPCs) to manage certificates on the network device. Using gNOI operations enables you to use the same suite of microservices to efficiently manage large-scale multivendor networks.

    [See gNOI Certificate Management (Cert) Service.]

  • Support for IRB (PTX10002-36QDD). You can use integrated routing and bridging (IRB) to route Layer 3 traffic between a bridge domain and another routed interface. The PTX10002-36QDD router supports the following IRB features:

    • All Layer 2 protocols already supported on the router

    • Layer 3 protocols BGP, IGMP, IS-IS, OSPF, PIM, and RIP

    • Per-IRB logical interface MAC and statistics

    • IRB Layer 3 multicast support with flooding only

    • Address family support for IPv4 and IPv6, and support for IPv4 maximum transmission units (MTUs) and IPv6 MTUs with different MTU values

    • IRB interface in virtual routing and forwarding (VRF) routing instances

    • Directed subnet broadcast support with IRB

    • Support for VRRP on IRB

    [See Integrated Routing and Bridging, Configuring a Layer 2 Virtual Switch with a Layer 2 Trunk Port, and Understanding VRRP.]

  • Support for LLDP, xSTP, and BPDU protection. (PTX10002-36QDD) Support includes:

    • Rapid Spanning Tree Protocol (RSTP), VLAN Spanning Tree Protocol (VSTP), Multiple Spanning Tree Protocol (MSTP), Spanning Tree Protocol (STP), root protection for STP, concurrent configuration of RSTP and VSTP, virtual switch, and BPDU protection for spanning-tree protocols

    • Bridge protocol data unit (BPDU) protection for EVPN-VXLAN

    • LLDP support, including:

      .

      • LLDP on em0 interfaces

      • Disabling of LLDP time, length, and value (TLV) messages

    [See Configuring STP, Understanding BPDU Protection for EVPN-VXLAN, and Device Discovery Using LLDP.]

  • Support for micro-SIDs in TI-LFA, microloop avoidance, flex algo, and IS-IS MT (PTX10002-36QDD). We extend the support of compressing SRv6 addresses into a single IPv6 address (micro-SID) in Topology Independent Loop-Free Alternate (TI-LFA), microloop avoidance, and Flexible Algorithm (flex algo) path computations. We also support IPv6 unicast topology (part of IS-IS MT) in TI-LFA, microloop avoidance, and flex algo computations.

    [See How to Enable SRv6 Network Programming in IS-IS Networks.]

  • Support for Q-in-Q tunneling (PTX10002-36QDD).

    [See Configuring Q-in-Q Tunneling and Q-in-Q Tunneling and VLAN Translation.]

  • Support for SRv6 LSPs in PCEP (ACX7348 and PTX10002-36QDD). The Path Computation Element Protocol (PCEP) supports all types of SRv6 LSPs, such as PCE-initiated, locally created, and delegated SRv6 LSPs.

    [See SRv6 LSP in PCEP.]

  • Support for SRv6 traceroute (PTX10002-36QDD, PTX10004, PTX10008, and PTX10016). We support the traceroute mechanism for Segment Routing for IPv6 (SRv6) segment identifiers.

    [See How to Enable SRv6 Network Programming in IS-IS Networks.]

  • Support for EVPN-VPWS(PTX10002-36QDD)

    [See Overview of VPWS with EVPN Signaling Mechanisms.]

  • Support for transit traffic rates in bits per second (bps) and packets per second (pps) for both IPv4 and IPv6 at a logical interface level (PTX10002-36QDD). Support includes:

    • Support for classification override configured under a forwarding policy

    • Support for VRRP

    • Unicast RPF support for both IPv4 and IPv6 traffic flows

    • Loose-mode unicast RPF on IPv4 and IPv6

    • Support for destination class usage (DCU) and source class usage (SCU) accounting

    • Class-based firewall filters

    • Forwarding IPv6 transit statistics

    • Operational state statistics for IPv6 logical interfaces

    [See Configuring IPv4 and IPv6 Accounting, CoS Features and Limitations on PTX Series Routers, Overriding the Input Classification, Understanding VRRP, Configuring Unicast RPF Loose Mode, Understanding Source Class Usage and Destination Class Usage Options, Configure the Filter Profile, BGP User Guide, and Guidelines for gRPC and gNMI Sensors (Junos Telemetry Interface).]

  • Support for VPLS (PTX10001-36MR, PTX10002-36QDD, PTX1000, PTX10008, and PTX10016). —You can configure VPLS on the PTX10000 line of routers running Junos OS Evolved.

    • To configure VPLS, configure the instance-type virtual-switch statement at the [edit routing-instances routing-instance-name] hierarchy level.
    • In this release, we support single bridge domains. You must configure service-type single statement at the [edit routing-instances routing-instance-name vpls] hierarchy level.
    • You must enable control-word at the [edit routing-instances routing-instance-name protocols vpls] hierarchy level.

    • Encapsulation of ethernet-vpls and vlan-vpls is not supported on CE interfaces.

    • To display VPLS MAC address information, use the show ethernet-switching table command.

    [See Introduction to Configuring VPLS

  • Supported transceivers, optical interfaces, and DAC cables (PTX10004, PTX10008, and PTX10016)—Select your product in the Hardware Compatibility Tool to view supported transceivers, optical interfaces, and direct attach copper (DAC) cables for your platform or interface module. We update the HCT and provide the first supported release information when the optic becomes available.

  • Support for tunnel decapsulation using firewall filters for GRE and UDP tunnels (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)

    [See Configuring a Filter to De-Encapsulate GRE Traffic and decapsulate (Firewall Filter).]

  • Support for filter-based forwarding to a specific outgoing interface or destination IP address (PTX10001-36MR, PTX10002-36QDD, PTX10003, PTX10004, PTX10008, and PTX10016). Support for next-interface, next-ip and next-ip6.

    [See Understanding Filter-Based Forwarding to a Specific Outgoing Interface or Destination IP Address.]

  • Support for per-packet random spray load balancing (PTX10001-36MR, PTX10002-36QDD, PTX10004, PTX10008, and PTX10016)

    [See Configuring Per-Packet Load Balancing.]

  • Support for flexible firewall filter match conditions (QFX5220, QFX5230, QFX5240, and PTX10002-36QDD)

    [See Firewall Filter Flexible Match Conditions.]

  • Fast lookup filter (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—Support extended to ethernet switching, any, mpls, and ccc firewall filter families for fast lookup filters on PTX Series routers.

    [See fast-lookup-filter (PTX).]

  • Support for VPLS (PTX10002-36QDD). We support the following VPLS features:

  • Exclude hops in the RSVP LSP path (ACX7332, ACX7509, PTX10002-36QDD, PTX10008)—You can configure a list of hops to be excluded in the label-switched path (LSP) so that RSVP LSPs avoid those hops and links in the traffic engineering (TE) domain. When an RSVP LSP is signaled in the network, the path message carries the excluded list of hops. When the downstream routers perform loose hop expansion, such as inter-domain LSP or abstract node expansion, the transit routers use the same excluded list of hops that the ingress router uses for path computation. This mechanism enables intermediate routers to avoid the routers included in the excluded hop list. The routers try alternative paths to help with the convergence of LSPs when a complete end-to-end path computation is not possible.

    Additionally, ingress routers receive PathErr messages and when computing another path, the routers use a PathErr message sender's address to avoid the link or node that generates an error. Transit routers also need this error avoidance information during retry attempts. RFC4814 defines the exclude hop information and is accepted in RSVP signaling.

    To configure LSPs to exclude a list of hops, include the exclude statement at the [edit protocols mpls path path-name next-hop] hierarchy level. The ingress routers exclude the hops in CSPF computation and are also included in RSVP LSP signaling.

  • Support for VNI based match for EVPN-VXLAN (PTX10002-36QDD)

    [See Firewall Filter Match Conditions and Actions (PTX Series Routers).]

  • Support for output filter-based GRE (PTX10002-36QDD)—For an outgoing packet matching the filter term, the packet is encapsulated inside an IP + GRE header as specified by the tunnel configuration. IP lookup is performed on the outer header and packet is forwarded accordingly. The IP lookup for GRE-encap capable route is limited to the implicit default routing-instance.

    [See Understanding Filter-Based Tunneling Across IPv4 Networks.]

  • Support for configuring output filter action with non-default routing instance or a specified routing instance (PTX10002-36QDD)

    [See Firewall Filter Terminating Actions.]

  • Support for filter-based forwarding (PTX10002-36QDD, PTX10004, PTX10008, and PTX10016)

    [See Example: Configuring Filter-Based Forwarding to a Specific Outgoing Interface or Destination IP Address.]

  • Firewall filter support for bitwise logical operations for TCP Flag match (PTX10002-36QDD, PTX10004, PTX10008, and PTX10016)

    [See Firewall Filter Match Conditions Based on Bit-Field Values.]