Additional Features | Junos OS Evolved

CoS support for EVPN-VXLAN (ACX7024).

EVPN-VXLAN support (ACX7024). We support the following features:

VXLAN Layer 2 gateways that provide Layer 2 connectivity between leaf devices separated by an underlay Layer 3 network

[See Understanding EVPN with VXLAN Data Plane Encapsulation.]
Layer 3 Gateway Encapsulation support for Layer 3 over an IPv4 underlay

[See Understanding VXLANs.]
EVPN-VXLAN support for Active/Active multihoming with Ethernet Switch Identifier for Link Aggregation Groups (ESI-LAG)

[See EVPN VXLAN User Guide - Leaf Device Forwarding.]
Storm control support in an Ethernet VPN-Virtual Extensible LAN (EVPN-VXLAN) overlay

[See Understanding Storm Control.]
VLAN-aware bundle , VLAN-based and VLAN bundle MAC-VRF service types

[See MAC-VRF Routing Instance Type Overview.]
Spine role with edge-routed bridging (ERB)

Note:
Overlapping VLANs is not supported between different MAC-VRF instances.
BPDU protection in EVPN-VXLAN

[See Understanding BPDU Protection for EVPN-VXLAN.]
Preference-based DF election

[See Designated Forwarder Election.]
EVPN BGP policy options support for control plane
Service provider style interface configuration with VXLAN, including:
- Encapsulation types ethernet-bridge, extended-vlan-bridge, and flexible-ethernet-services
  
  [See encapsulation.]
- Flexible VLAN tagging for single- and dual-tagged logical interfaces on the same port.
- Q-in-Q
  
  [See Examples: Tunneling Q-in-Q Traffic in an EVPN-VXLAN Overlay Network and Understanding Flexible Ethernet Services Support With EVPN-VXLAN. ]
Extensions to enterprise style interface configuration support with VXLAN, including:
- Trunk interfaces with flexible Ethernet services and flexible VLAN tagging
- Multiple trunk interfaces on the same port
  
  [See Understanding Flexible Ethernet Services Support with EVPN-VXLAN.]
Layer 2 (L2) and Layer 3 (L3) logical interfaces on the same port, with L2 logical interfaces as part of the VXLAN VLAN or tenant VLANs

[See EVPN User Guide.]

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 devices).

FAT label support includes these features:

Transmit and receive direction on Layer 2 circuits and Layer 2 VPNs.
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 that includes these features:

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

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

Inline active flow monitoring IPv6 addressing support for IPFIX and version 9 flow collectors (PTX10001-36MR, PTX10003, PTX10004, and the PTX10008 and PTX10016 routers with the JNP10K-LC1201 or the JNP10K-LC1202 line card). You can configure either IPv4 or IPv6 collectors for each family within a sampling instance; you cannot specify both for the same family. You can specify up to four collectors for each family within a sampling instance.

[See Understand Inline Active Flow Monitoring.]

Inline active flow monitoring support for IPFIX and v9 export formats (ACX7509, ACX7100). We support ingress and egress sampling of IPv4 and IPv6 traffic on aggregated Ethernet and IRB interfaces and interfaces mapped to non-default VRFs, for both the IPFIX and version 9 export formats. You can configure up to four IPv4 collectors for inline active flow monitoring.

[See Understand Inline Active Flow Monitoring.]

IPv4 address conservation method for hosting providers (ACX7100). Support for static route with next hop as integrated routing and bridging (IRB) over VLAN and VXLAN to significantly reduce the number of routable IPv4 addresses that you use for your hosting customers.

[See IPv4 Address Conservation Method for Hosting Providers, Static Route Preferences and Qualified Next Hops, and Configure Static Routes.]

MACsec on logical interfaces (ACX7100-32C).

[See Media Access Control Security (MACsec) over WAN.]

MVPN feature support with sharding (PTX10001-36MR, PTX10003, PTX10004, PTX10008, QFX5130-32CD, and QFX5700).We support the following MVPN features:

With sharding, the information required by MVPN, such as inactive L3vpn routes, primary, and secondary details for auto-exported routes were only in the shard thread due to which some MVPN features were only partially supported earlier.
As part of the update, these information will be retrieved from shard to main thread. MVPN upstream multicast hop (UMH) mechanisms, sender-based Reverse-path Forwarding (RPF), extranet, and bootstrap (BSR) using auto-export scenarios which depend on these information, will now be in parity/compliant with non-sharding deployments.

You can use the “show mvpn c-multicast” command to display all the routes on the main thread.

[See rib-sharding and show mvpn c-multicast.]

MVPN support for MLAN, PIM-DIM, and type 7 withdrawal on stream threshold (sharding and non-sharding) (PTX10001-36MR, PTX10003, PTX10004, PTX10008, QFX5130-32CD, and QFX5700). We support MVPN for MLAN, PIM-DIM, and type 7 withdrawal on stream threshold.

[See source-active-advertisement, rib-sharding, and show mvpn c-multicast.]

Next-Generation MVPN (PTX10003). We 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.]

Next-generation MVPN Inter-AS option B with or without sharding enabled (PTX10001-36MR, PTX10004, PTX10008, and PTX10016).

[See BGP-MVPN Inter-AS Option B Overview and Sharding and UpdateIO on cRPD.]

OpenConfig interface configuration support (ACX7100-32C, ACX7100-48L, and ACX7509).

[See Mapping OpenConfig Interface Commands to Junos Configuration.]

Platform Resiliency Support (ACX Series Devices). We include chassis synchronization and fault-handling support for components such as:

Fan.
Clocking.
PTP.
FPGA.

With resiliency enabled, the device can detect and log errors, raise alarms, send SNMP traps, provide error indication through LEDs, self-heal, and take components out of service.

[See show system errors active.]

Prevent script execution based on current system memory usage (ACX7024, ACX7100-32C, ACX7100-48L, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5220, and QFX5700). You can configure the system memory usage threshold above which the device prevents the execution of certain op, event, SNMP, or Juniper Extension Toolkit (JET) scripts. [See Configure Script Start Options.]

Real-time Performance Monitoring (RPM) IPv6 source and target address support (ACX7024, ACX7100, ACX7509, PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5220, and QFX5700). You can configure IPv6 source and target addresses for RPM. We've also added support for IPv6 addresses to the SNMP RFC2925a MIB control and results tables. For IPv6 RPM probes, you can enable timestamps only in the Routing Engine.

[See source-address and target.]

Support for BGP Classful Transport (BGP CT) (ACX7100-32C, ACX7100-48L, ACX7509, and ACX7024 Devices). Support for BGP transport address family or BGP Classful Transport (BGP CT) that includes:

Support for service mapping over colored transport tunnels (RSVP, IS-IS flexible algorithm) to transport classes and map service routes over an intended transport class. The transport tunnels can span multiple domains(autonomous systems (ASs) or IGP areas.
Network slicing and interoperability between network domains.
IPv6 and Segment Routing TrafficEngineered (SR-TE) color-only support.
IPv6 and BGP service-routes with a color-only mapping community.
Enhanced transport-class configuration to provide precise resolution.

[See use-transport-class.]

SRv6 network programming in IS-IS (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024). You can configure segment routing in a core IPv6 network without an MPLS data plane.

To enable SRv6 network programming in an IPv6 domain, use the source-packet-routing srv6 command.

To advertise the Segment Routing Header (SRH) locator with a mapped flexible algorithm, use the algorithm at [edit protocols isis source-packet-routing srv6 locator] hierarchy level.

To configure a topology-independent loop-free alternate backup path for SRv6 in an IS-IS network, include the transit-srh-insert statement at the [edit protocols isis source-packet-routing srv6] hierarchy level.

[See source-packet-routing srv6 and How to Enable SRv6 Network Programming in IS-IS Networks.]

SRv6 support for static SR-TE policy (ACX7100-32C, ACX7100-48L, ACX7509, and ACX7024 routers). You can configure static segment routing–traffic engineering (SR-TE) tunnels over an SRv6 data plane.

[See Understanding SR-TE Policy for SRv6 Tunnel.]

SRv6 network programming in IS-IS (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024 with MPC7E, MPC8E and MPC9E line cards). You can configure segment routing in a core IPv6 network without an MPLS data plane.

To enable SRv6 network programming in an IPv6 domain, use the source-packet-routing srv6 command. [See source-packet-routing srv6.]

To advertise the Segment Routing Header (SRH) locator with a mapped flexible algorithm, use the algorithm [edit protocols isis source-packet-routing srv6 locator] hierarchy level.

To configure a topology-independent loop-free alternate backup path for SRv6 in an IS-IS network, include the transit-srh-insert statement at the [edit protocols isis source-packet-routing srv6] hierarchy level.

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

Support for BGP link-state distribution with SPRING extensions (ACX Series). Support for BGP link-state extensions export source packet routing in networking (SPRING) and segment-routing topology information to software-defined networking controllers on ACX7100-32C, ACX7100-48L, ACX7509, and ACX7024.

This feature benefits networks that are moving to SPRING but also have RSVP deployed and continue to use both SPRING and RSVP in their networks.

[See Link-State Distribution Using BGP Overview, show route table, and show route command.]

Support for EVPN VxLAN ACLs and Policers (ACX7024). Firewall filtering and policing support on EVPN-VXLAN traffic.

[See Firewall Filters Overview and Understanding EVPN with VXLAN Data Plane Encapsulation.]

Support for Flow-Aware Transport for Pseudowires (FAT) label and Entropy label support for EVPN VPWS and flexible cross-connect (FXC) (ACX7100-32C, ACX7509, and ACX7024 routers). [See FAT Flow Labels Overview .]

Support for EVPN VxLAN ACLs and Policers (ACX7204). Firewall filtering and policing support on EVPN-VXLAN traffic. [See Firewall Filters Overview andUnderstanding EVPN with VXLAN Data Plane Encapsulation.]

Support for fan module replacement related alarms and temperature-based system shutdown (QFX5230-64CD).

[See How to Configure Flexible Algorithms in IS-IS for Segment Routing Traffic Engineering

and BGP Link-State Extensions for Source Packet Routing in Networking (SPRING).]

Support for hybrid mode (Synchronous Ethernet and PTP) over LAG with PTP over Ethernet (PTX10001-36MR with LC1201-36CD). [See Hybrid Mode.]

Support for IPv6 payload-protocol match condition for management interface in ingress and/or egress direction and loopback interface in egress direction (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5700, QFX5220, and QFX5230-64CD).

[See Firewall Filter Match Conditions for IPv6 Traffic.]

Support for PTP, Synchronous Ethernet, and hybrid mode over LAG (PTX10001-36MR). We support Precision Time Protocol (PTP), synchronous Ethernet, and hybrid mode over a LAG.

[See Precision Time Protocol and Hybrid Mode.]

Support for QSFP-100G-4WDM40 optics (PTX10001-36MR).

[See optics-options.]

Support for remote authorization on tacplus servers for locally certificate-based authenticated users (ACX7100-32C, ACX7100-48L, ACX7509, ACX7024, PTX10001-36MR, PTX10003, PTX10004, PTX10008, PTX10016, QFX5130-32CD, QFX5700, and QFX5220). We support remote authorization on TACPLUS servers for locally authenticated users by using certificate-based authentication.

Note:

You must configure the password under authentication-order when password-options is configured. The feature does not work in a local fallback scenario, because the password is not configured under authentication-order for a local fallback scenario.

To configure remote authorization, include the tacplus-authorization option under the password-options configuration statement at the [edit system] hierarchy level.

[See password-options.]

Support for Segment Routing for IPv6 (SRv6) flexible algorithms in traffic engineering database (TED) and BGP Link State (LS) (ACX7100-32C, ACX7100-48L. ACX7509 and ACX7024). You cannot define flexible algorithms specifically for either SR-MPLS or SRv6. If a node is participating in a flexible algorithm, it would apply to both SR-MPLS and SRv6 nodes.

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

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

[See Hardware Compatibility Tool.]

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 the HCT and provide the first supported release information when the optic becomes available.