Additional Features | Junos OS Evolved

Accept BGP routes with accept-own community (ACX7100-32C, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)

[See BGP accept-own Community and accept-own.]

Adaptive RSVP update-threshold for optimal IGP flooding (PTX10001-36MR, PTX10002, PTX10003, PTX10004, PTX10008, and PTX10016)—You can now configure the RSVP update threshold percentage and threshold value to adaptively pace IGP updates.

[See update-threshold.]

Collect ON_CHANGE BGP RIB telemetry statistics (PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, and QFX5220)

[See Telemetry Sensor Explorer.]

Collect ON_CHANGE BGP RIB telemetry statistics and BGP neighbor telemetry with sharding (ACX7100-32C, ACX7100-48L, ACX7509, PTX10001-36MR, PTX10004, PTX10008, PTX10016, QFX5130-32CD, and QFX5700)

[See Telemetry Sensor Explorer.]

EVPN E-LAN Active-Active Multihoming with EVPN Aliasing Support for ESI LAG (ACX7509)

[See EVPN Multihoming Overview, Example: Configuring EVPN Active-Active Multihoming, Using the evpn-aliasing-optimize command, and EVPN Features in EVPNs using EVPN LAGs]

Firewall filter actions (ACX7100-32C, ACX7100-48L, and ACX7509)—We support the following:

next-ip firewall filter action for IPv4 address
next-ip6 firewall filter action for IPv6 address
next-interface firewall filter action for an interface

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

Flow-Aware Transport for Pseudowires (FAT) label and Entropy label support for Layer 2 circuit and Layer 2 VPN(ACX7100-32C, ACX7100-48L, and ACX7509)—

FAT Label support includes these features:

Transmit and receive direction on Layer 2 circuits and Layer 2 VPNs
Transmit and receive direction on Layer 2 VPN
Layer 2 VPN with multihoming
Layer 2 circuits with redundant pseudowire
Load balancing over LAG
Static flow label for Layer 2 circuits

Entropy Label support includes these features:

Entropy label indication for LDP and RSVP transport
Load balancing over LAG

[See FAT Flow Labels Overview and Configuring Entropy Labels.]

GRES support for Connectivity Fault Management (CFM) and Link Fault Management (LFM) (ACX7509)

[See Introduction to OAM Connectivity Fault Management (CFM) and Introduction to OAM Link Fault Management (LFM).]

GRES support for ERPS (ACX7509)

[See Understanding Ethernet Ring Protection Switching Functionality.]

GRES support for MPLS, L3VPN, L3 Multicast, and BGP (ACX7509)

[See MPLS Overview.]

GRES support for VRRP (ACX7509)

[See Understanding VRRP.]

High availability support for BFD (centralized mode), L3 protocols (ISIS,OSPF, ECMP), static routes, SR-ISIS, and SR-OSPF (ACX7509)

[See Configuring BFD.]

High availability support for Periodic Packet Management (ACX7509)

[See Periodic Packet Management.]

Inline active flow monitoring using IP Flow Information Export (IPFIX) and version 9 templates (PTX10003)—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 IPFIX and Version 9 Templates.]

Inline monitoring services (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016 routers with the JNP10K-LC1201 or JNP10K-LC1203 linecards)—

Inline monitoring services enable you to monitor different streams of traffic at different sampling rates on the same interface. The inline monitoring services in the Junos OS Evolved implementation show the following differences from the inline monitoring services in the Junos OS implementation:

A maximum of seven inline-monitoring instances
A maximum clip length of 256 bytes starting from the Ethernet header
Sampling rate per instance only
Port-mirroring and inline-monitoring firewall filter actions on different terms
Some inline-monitoring-services configuration options are available only in the Junos OS implementation, such as the options to specify the DSCP bits, forwarding class, routing instance, template ID, and option template ID.

[See Inline Monitoring Services Configuration.]

IP-IP tunnel stitching (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)

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

IPFIX IPv4 and IPv6 template support for forwarding class and packet loss priority (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)

[See IPFIX and Version 9 Templates.]

Juniper Resiliency Interface (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016 routers with the JNP10K-LC1201 or JNP10K-LC1203 linecards)

[See Juniper Resiliency Interface.]

LACP redundancy support (ACX7509)

[See Configuring Link Aggregation Control Protocol.]

Media Access Control Security (MACsec) (QFX5700 with 20x25G line cards)—

Support includes:

AES-128 and AES-256 encryption
Extended packet numbering
Fallback preshared key (PSK)
Timer-based MACsec secure association key (SAK) refresh
Jumbo MTU support
Fail-open mode
PSK hitless rollover

[See Understanding Media Access Control Security (MACsec).]

Next-Generation MVPN (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—We now support:

Rendezvous-point tree (RPT)-shortest-path tree (SPT) mode.
Restart individual PFE instances.
Turnaround provider edge (PE) device.
RP Mechanisms, including auto rendezvous point (RP), bootstrap router (BSR), and embedded RP.

[See Understanding Next-Generation MVPN Control Plane.]

NSR Support for RIP and RIPng (PTX10004, PTX10008, and PTX10016)

[See Nonstop Active Routing Concepts.]

Per Packet Forwarding Engine-Restart support (PTX10004, PTX10008, and PTX10016)—

Support includes:

Disable, offline, and restart of individual Packet Forwarding Engines.
Filter-based GRE encapsulation.
Segment routing–traffic engineering (SR-TE) per path telemetry statistics support, including ingress IP/binding-segment identifiers (SIDs) and MPLS transit traffic.
Flow Aware Transport (FAT) label transport for Layer 2 VPN.
VLAN tag manipulation support for CCC.
Segment routing over UDP.
Multicast-only fast reroute (MoFRR) for both IPv4 and IPv6 traffic flows.

[See fpc (M320, T320, T640, and PTX Series Routers), Understanding Filter-Based Tunneling Across IPv4 Networks, source-packet-routing, flow-label-transmit, Configuring an MPLS-Based VLAN CCC with Pop, Push, and Swap and Control Passthrough, Next-Hop-Based Dynamic Tunnels, and Understanding Multicast-Only Fast Reroute.]

Redundancy support for Spanning Tree Protocol (STP) (ACX7509)

[See Spanning-Tree Protocol Overview.]

sFlow ingress support(ACX7100-32C, ACX7100-48L, and ACX7509)

[See sFlow Monitoring Technology and Understanding How to Use sFlow Technology for Network Monitoring.]

SPRING support for SR-TE (ACX7509)

Segment routing policy to steer labeled or IP traffic at ingress routers.
Segment routing paths for a non-colored static label-switched path (LSP).
Color-based traffic steering of Layer 2 and Layer 3 VPN services.
SR policy-based dynamic tunnel module triggered SR-TE.
Indirect next hop and composite next hop modes.

[See Segment Routing Traffic Engineering at BGP Ingress Peer Overview.]

Support for all-active multi-homing redundancy in both Ethernet VPN–virtual private wire service (EVPN-VPWS) and EVPN-VPWS with flexible cross-connect. Support for EVPN VPWS Multi-Homing All-Active for Segment Routing over MPLS (ACX7509)

[See Overview of Flexible Cross-Connect Support on VPWS with EVPN and erview of VPWS with EVPN Signaling Mechanisms.]

Support for BGP Classful Transport (CT) with underlying colored Segment Routing Traffic-Engineered (SRTE) tunnels (PTX10001-36MR, PTX10003, PTX10004, PTX10008 and PTX10016)

—BGP-CT can resolve service routes using the transport routing information bases (RIB)s, also known as routing tables and compute the next hop. Services currently supported over BGP-CT can also use the underlying SRTE colored tunnels for route resolution.

[See use-transport-class.]

Support for EVPN-virtual private wire service (VPWS) (PTX10001-36MR, PTX10004, PTX10008, and PTX10016)—We've extended support for EVPN-VPWS to the listed PTX Series routers. By default, control-word is enabled on these platforms. To disable the control word feature, use the set routing-instances routing-instance-name protocols evpn no-control-wordcommand.

[See Overview of VPWS with EVPN Signaling Mechanisms.]

Support for firewall filtering using flood policer, IRB, and service provider egress filtering (PTX10003)

Support for G.8275.1 telecom profile, Precision Time Protocol (PTP) over Ethernet encapsulation, and hybrid mode (ACX7100-32C|ACX7100-48L)

[See G.8275.1 Telecom Profile, Guidelines to Configure PTP over Ethernet, and Hybrid Mode Overview .]

Support for Precision Time Protocol (PTP) G.8275.1 enh and G.8275.2 enh profiles with PTP over IPv4 and IPv6 unicast (ACX7100-32C and ACX7100-48L) —The profiles also support ordinary and boundary clocks. The G.8275.1 enh profile does not support unicast negotiation.

[See PTP profiles.]

Support for match conditions next-header and payload-protocol to filter IPv6 packets based on Next Header (NH) values of first and last headers (PTX10003)

The next-header matches on intermediate extension headers are not supported. The payload-protocol match is applicable only if the first extension header is Hop-by-Hop.

[See Firewall Filter Match Conditions for IPv6 Traffic]

Support for Layer 2 Features - MAC move limit and multiple trunk ports (ACX7100-32C, ACX7100-48L, and ACX7509)—

The Layer 2 feature support includes:

The MAC move limit on Layer 2 bridge domains, VXLAN, virtual private LAN service (VPLS), and EVPN networks. Juniper Networks ACX7509 routers do not support MAC move limit over VXLAN routing instances or data center logical interfaces.
Multiple trunk ports. Juniper Networks ACX7509 routers do not support multiple trunk ports on data center logical interfaces.

[See Understanding MAC Limiting and MAC Move Limiting.]

Support for multiprotocol BGP MVPN (also known as "Next Generation MVPN" or "NG-MVPN") with MDLP as Provider Tunnel. NSR and GRES support for NG-MVPN (ACX7509)

[See Multiprotocol BGP MVPNs Overview]

Support for Redundant Pseudowire Layer 2 Circuits (ACX7100-32C and ACX7100-48L). Multichassis Link Aggregation Group (MC-LAG) is not supported with redundant pseudowire Layer 2 circuits (ACX7509)

[See Redundant Pseudowires for Layer 2 Circuits and VPLS]

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

Support for TCP authentication and keychain (QFX5700 and QFX5220)—We asupport TCP authentication and key update mechanism for BGP and LDP routing protocols, which enables you to update authentication keys without interrupting associated routing and signaling protocols.

[See Authentication for Routing Protocols, authentication-key-chain (Protocols LDP), authentication-algorithm, and authentication-key-chain (Protocols BGP and BMP).]

Support for TCP Authentication Option (TCP-AO) (QFX5220)—You can now use TCP-AO to authenticate TCP segments exchanged during BGP and LDP sessions.

[See TCP Authentication Option (TCP-AO) and authentication-key-chains (TCP-AO).]

Translation of multicast virtual private network (MVPN) Type 5 routes to Multicast Source Discovery Protocol (MSDP) SA routes (PTX10001-36MR, PTX10003, PTX10004, PTX10008, and PTX10016)

[See Converting MVPN Type 5 Routes to MSDP SA.]