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.

  • EVPN Proxy ARP and Proxy NDP (PTX10002-36QDD)

    [See EVPN Proxy ARP and ARP Suppression, and Proxy NDP and NDP Suppression.]

  • 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 and Layer 3 gateway operations in edge-routed bridging (ERB) and centrally routed bridging (CRB) 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.]

  • Overlays: Static-VXLAN Layer2 Gateway (PTX10002-36QDD)

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

  • EVPN Proxy ARP and Proxy NDP (PTX10002-36QDD)

    [See EVPN Proxy ARP and ARP Suppression, and Proxy NDP and NDP Suppresion .]

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

    [See Overview of VPWS with EVPN Signaling Mechanisms.]

  • Support for VPLS (PTX10002-36QDD,)—You can configure VPLS on the PTX10002-36QDD.

    • 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.
    • When you configure VPLS support on the PTX 10000 series, 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

  • Support for flexible firewall filter match conditions(PTX10002-36QDD)

    [See Flexible Firewall Filter Match Conditions.]

  • Support for fast-lookup-filter on Any, ethernet switching, and CCC firewall family filters (PTX10002-36QDD)

    [See fast-lookup-filter.]

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

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

  • Support for Q-in-Q tunneling (PTX1000236QDD) .

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

  • Support for tunnel decapsulation using firewall filters for GRE and UDP tunnels (PTX10002-36QDD)

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

  • 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.]