Additional Features

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

• DHCP security (EX9200, MX240, MX480, MX960, MX2010, MX2020). MPC10E line cards support the following DHCP security features:

  • DHCP snooping with Option 82.
  • DHCPv6 snooping with Option 16, Option 18, Option 37, and Option 79.
  • Lightweight DHCPv6 Relay Agent.

  [See DHCP Snooping.]

• Dynamic routing protocols (MX240, MX480, and MX960 with MX-SPC3, SRX5000 line of devices with SPC3 card and vSRX running iked). We support the exchange of dynamic routing information through IPsec VPN tunnels. You can now enable the dynamic routing protocol, such as OSPF, BGP, BFD, PIM, and RIP on a st0 interface of an IPsec VPN tunnel.

  This feature is supported only if the junos-ike package is installed in your device.

  [See Routing Protocols Support on IPsec VPN Tunnels.]

• Enhancements to increase traffic selector flexibility (MX240, MX480, and MX960 with MX-SPC3). You can do the following to add flexibility to your traffic selectors in different deployment scenarios:

  • Configure the routing metric for a traffic selector.
  • Define the source port range, destination port range, and protocol for a traffic selector.
  • Define multiple terms within a traffic selector, instead of creating multiple traffic selectors (or child security associations or SAs) for a VPN. Each term comprises the local and remote IP prefixes, the source and destination port ranges, and the protocol identifier. You can use these parameters in a single IPsec SA negotiation. In earlier Junos OS releases, you configure each traffic selector with one set of local and remote IP prefixes to be used in an IPsec SA negotiation with a peer.

  This feature is supported only if the junos-ike package is installed in your device.

  We recommend that you configure the same metric value if you define multiple traffic selectors under the same [edit security ipsec vpn vpn_name] hierarchy with the same value for remote-ip ip-address/netmask. If you configure different metric values, then the metric value of the st0 route installed will be the same as that for the traffic selector that is negotiated or installed first.

  [See traffic-selector and show security ipsec security-associations detail.]

• EVPN Type 2 and Type 5 route coexistence (EX9200, EX9251, EX9253, MX204, MX240, MX480, MX960, MX2010, MX10003, MX10008, and QFX10002-60C)

  [See EVPN Type 2 and Type 5 Route Coexistence with EVPN-VXLAN.]

• Hybrid mode (Synchronous Ethernet and Precision Time Protocol) over LAG supports PTP over IPv4 and PTP over Ethernet (MX204 and MX10003)

  [See PTP Overview and Hybrid Mode Overview.]

• Hold timer support on aggregated Ethernet (ae-) interfaces (MX150, MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, PTX1000, PTX5000, PTX10002, PTX10008, PTX10016) Specify the hold-time value to delay the advertisement of up and down transitions (flapping) on an interface.

  [See hold-time.]

• Redistribution of IPv4 routes with IPv6 Next Hop into BGP through tunnels: (MX10008 and MX10016):

  IPv4 traffic is tunneled from CPE devices to IPv4-over-IPv6 gateways as described in RFC 5549.

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

• Support for Precision Time Protocol (PTP) over Ethernet in hybrid mode over link aggregation group (LAG) (MX10008 with JNP10K-LC2101 MPC line card)

  [See Precision Time Protocol Overview and Hybrid Mode Overview.]

• Supported transceivers, optical interfaces, and DAC cables (ACX Series, EX Series, PTX Series, MX Series, and QFX Series).—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.