Hardware

• Support for EVPN-MPLS. The router supports MAC VRF routing instances on the EVPN-MPLS network. [See EVPN User Guide.]

Interfaces and chassis

• Support for custom optics profile. You can now configure the optical module parameters of QSFP modules by using the CLI from the configuration prompt. In earlier releases, you could not configure the parameters from the configuration prompt. We do not support these module parameters for QSFP direct attach copper (DAC) cable modules or QSFP load modules. [See optics-options.]

Junos telemetry interface (JTI)

• Support for optics diagnostics, openconfig-platform-transceiver.yang, version 0.5.0, output power, input power, laser bias for JTI. We’ve enhanced support for physical and logical interface transceiver statistics. Use the new sensors under the resource paths /components/component/transceiver/ and /components/component/transceiver/physical-channels/ to export statistics to an outside collector using JTI and RPC or gNMI services.

  To export statistics, include the following sensors in a subscription:

  • /components/component/transceiver/oc-instant:transceiver:output-power
  • /components/component/transceiver/oc-instant:transceiver:input-power
  • /components/component/transceiver/oc-instant:transceiver:laser-bias-current
  • /components/component/transceiver/physical-channels/oc-instant:transceiver:output-power

• /components/component/transceiver/physical-channels/oc-instant:transceiver:input-power
• /components/component/transceiver/physical-channels/oc-instant:transceiver:laser-bias-current

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

Layer 2 features

• Support for the IRB interface, which enables routing of Layer 3 traffic between a bridge domain and another routed interface. [See Integrated Routing and Bridging.]

MPLS

• Support for point-to-multipoint (P2MP) ping and P2MP label-switched path (LSP) traceroute. [See MPLS Applications User Guide.]

• Support for SNMP for PFC and ECN. You can monitor the PFC and ECN status from the remote network using SNMP. [See Enterprise-Specific SNMP MIBs Supported by Junos OS.]

Routing protocols

• Support to label interfaces and match the interface-group ID on firewall filter. We support labeling of interfaces with specified group IDs from 1 to 255 and matching the interface-group ID on the firewall filter. The filter can identify which interface a packet comes from and perform actions specified only for a certain interface group. [See Understanding BGP Flow Routes for Traffic Filtering.]

• Support for FIB compression. Forwarding information base (FIB) compression overcomes the hardware limitation of storing a limited number of uncompressed routes. We've enabled FIB compression by default. You can now store a larger number of compressed IPv4 and IPv6 routes.

• Support for higher scale of flows in the BGP FlowSpec filter. We now support a higher scale of flows in BGP FlowSpec filter. You can achieve this by reducing the number of terms in the BGP FlowSpec filter using the filter optimization techniques without affecting the functionality. The per-term counter is not configured by default. To create room for term compression, the default per-term counters are disabled. However, to enable per-term counter a new CLI command, per-route-accounting has been introduced under the existing [edit routing-options flow] hierarchy level.” [See “per-route-accounting”].

Routing policy and firewall filters

• Support for nested filters. This feature enables you to reference a common firewall filter by attaching it to multiple firewall policies (a filter being one or more match conditions and corresponding actions). You can bind nested filters to the following interface types:

  • inet—Input and output directions
  • inet6—Input and output directions
  • mpls—Input direction only

  You can also bind them to routing instances, and in the input direction, the output direction, or both directions. [See Guidelines for Nesting References to Multiple Firewall Filters and Example: Nesting References to Multiple Firewall Filters.]

• Support for firewall filters. We've added support for Layer 2 firewall filter match conditions and actions. [See Understanding Firewall Filter Match Conditions.]

Services applications

• Support for configuring GRE tunnel encapsulation on flexible tunnel interfaces (FTIs). You can configure encapsulation by using the tunnel encapsulation udp source address destination address command at the [edit interfaces fti unit unit] hierarchy level.

  • If you add the tunnel-termination statement, it makes the tunnel a de-encapsulation-only tunnel and disables the encapsulation.
  • You must specify both the source and destination addresses if you do not configure tunnel-termination.
  • You cannot configure a variable prefix mask on the source address.

  [See encapsulation.]

• Support for RFC 5357 Two-Way Active Measurement Protocol (TWAMP) monitoring service. TWAMP sends out probes to measure network performance and is often used to check compliance with service-level agreements. You can configure TWAMP at the [edit services monitoring twamp] hierarchy level. The support for this service is limited to the following:

  • IPv4 traffic only for control sessions and test sessions
  • Probe statistics and history
  • Control and test session status
  • Test session probe generation and reception, as well as reflection
  • Timestamps set by the Routing Engine or the Packet Forwarding Engine
  • Error reporting through system log messages only
  • Unauthenticated mode only

  [See Understanding Two-Way Active Measurement Protocol on Routers.]

• Support for multiple collectors in inline active flow monitoring. You can now configure inline active flow monitoring to export flow records to up to four different collectors. Previously, inline flow monitoring could export flow records only to a single collector. [See Configuring Inline Active Flow Monitoring on PTX Series Routers.]

• Support for reporting of the true incoming interface for the sample packets for inline active flow monitoring. Inline active flow monitoring now reports the true incoming interface for the GRE-de-encapsulated packets entering the router for the configured inline active flow monitoring filter criteria. [See Understanding Inline Active Flow Monitoring and Configuring Flow Aggregation to Use IPFIX Flow Templates on PTX Series Routers.]

• Support for configuring UDP tunnel encapsulation on flexible tunnel interfaces (FTIs). You can configure encapsulation by using the tunnel encapsulation udp source address destination address command at the [edit interfaces fti unit unit] hierarchy level.

  • If you add the tunnel-termination statement, it makes the tunnel a de-encapsulation-only tunnel and disables the encapsulation.
  • You must specify both the source and destination addresses if you do not configure tunnel-termination.
  • You cannot configure a variable prefix mask on the source address.

  [See encapsulation.]

Software installation and upgrade

• Support for listing incompatible field-replaceable units (FRUs) in the output of the request system software add restart and request system software validate-restart commands, and giving users the opportunity to take the unsupported FRUs offline and continue with the restart or validation. [See request system software add and request system software validate-restart.]

DHCP

• Support for stateless DHCP relay on IRB interfaces and bridge domains. Support includes DHCPv4 and DHCPv6. [See DHCP Relay Agent.]

Junos telemetry interface (JTI)

• Support for platform, interface, and alarm statistics using JTI and gRPC Network Management Interface (gNMI) services. You can use this feature to send ON_CHANGE statistics of a device to an outside collector.

  This feature supports these OpenConfig models:

  • openconfig-platform.yang: oc-ext:openconfig-version 0.12.1
  • openconfig-interfaces.yang: oc-ext:openconfig-version 2.4.1
  • openconfig-alarms.yang: oc-ext:openconfig-version 0.3.1

  Use the following resource paths in a gNMI subscription:

  • /components/component (for each installed FRU)
  • /interfaces/interface/state/
  • /interfaces/interface/subinterfaces/subinterface/state/
  • /alarms/alarm/

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

Layer 2 VPN

• Support for virtual private wire service (VPWS) with single segment and multisegment pseudowires using FEC 129. [See "Example: Configuring FEC 129 BGP Autodiscovery for VPWS".]

• Support for EVPN-MPLS. The router supports MAC VRF routing instances on the EVPN-MPLS network. [See EVPN User Guide.]

Interfaces and chassis

• Support for custom optics profile. You can now configure the optical module parameters of QSFP modules by using the CLI from the configuration prompt. In earlier releases, you could not configure the parameters from the configuration prompt. We do not support these module parameters for QSFP direct attach copper (DAC) cable modules or QSFP load modules. [See optics-options.]

• Support for ALB on multiple Packet Forwarding Engines for aggregated Ethernet bundles. Adaptive load balancing (ALB) for aggregated Ethernet bundles evenly redistributes the traffic load across multiple ingress Packet Forwarding Engines on the same line card. [See Load Balancing on Aggregated Ethernet Interfaces.]

IP tunneling

• Support for IPv4 unicast tunneling. To support IP-over-IP on the PTX models, the routing protocol process (rpd) sends fully resolved next-hop-based tunnels to the Packet Forwarding Engine. [See Overview of Next-Hop-Based Dynamic Tunneling Using IP-Over-IP Encapsulation.]

• Support for optics diagnostics, openconfig-platform-transceiver.yang, version 0.5.0, output power, input power, laser bias for JTI. We’ve enhanced support for physical and logical interface transceiver statistics. Use the new sensors under the resource paths /components/component/transceiver/ and /components/component/transceiver/physical-channels/ to export statistics to an outside collector using JTI and RPC or gNMI services.

• To export statistics, include the following sensors in a subscription:

  • /components/component/transceiver/oc-instant:transceiver:output-power
  • /components/component/transceiver/oc-instant:transceiver:input-power
  • /components/component/transceiver/oc-instant:transceiver:laser-bias-current
  • /components/component/transceiver/physical-channels/oc-instant:transceiver:output-power
  • /components/component/transceiver/physical-channels/oc-instant:transceiver:input-power
  • /components/component/transceiver/physical-channels/oc-instant:transceiver:laser-bias-current

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

Layer 2 features

• Support for the following basic Layer 2 learning, bridging, and flooding features:

  • Enterprise-style bridging (trunk and access modes)
  • Service-provider-style bridging (also known as sub-interface mode)
  • BUM (broadcast, unknown unicast, and multicast) traffic handling, including split horizon
  • MAC learning and aging
  • Static MAC addresses
  • Trunk port, VLAN membership, and native-vlan-id
  • 802.1Q EtherType - 8100
  • 802.1Q VLAN tagging: Single tagging with normalization
  • Clearing of all MAC address information
  • Global MAC limit
  • Global source MAC aging time
  • MAC moves
  • Disabling of MAC learning at global and interface levels.
  • 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 are not supported under flexible Ethernet services encapsulation.

  • Virtual switch
  • Persistent MAC learning (sticky MAC)
  • Service provider bridging:
    • Multiple logical interfaces (on a physical interface) which are part of same bridge domain
    • Ethernet bridge encapsulation

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

MPLS

• Support for next-hop-based dynamic UDP tunnels, also known as MPLS-over-UDP tunnels. When you configure an MPLS-over-UDP tunnel, Junos OS dynamically creates a tunnel composite next hop, an indirect next hop, and a forwarding next hop to resolve the tunnel destination route. You can also use policy control to resolve MPLS-over-UDP tunnels over select IP prefixes. When you enable next hops by default, the MPLS-over-UDP feature provides a scaling advantage for the number of IP tunnels supported on the router. [See Example: Configuring Next-Hop-Based MPLS-Over-UDP Dynamic Tunnels.]

Network management and monitoring

• Support for remote port mirroring with ToS or DSCP settings. This feature enables you to send sampled copies of incoming packets to remote network management software. You can send the packets through flexible tunnel interfaces (FTIs) using GRE encapsulation. You can set type of service (ToS) and DiffServ code point (DSCP) values to provide necessary priorities in the network for these packets. You can also apply policing to sampled packets that are leaving the FTI. Configure the settings in the [edit forwarding-options port-mirroring instance <instance-name> output] hierarchy. [See instance (Port Mirroring).]

Routing protocols

• Support to label interfaces and match the interface-group ID on firewall filter. We support labeling of interfaces with specified group IDs from 1 to 255 and matching the interface-group ID on the firewall filter. The filter can identify which interface a packet comes from and perform actions specified only for a certain interface group. [See Understanding BGP Flow Routes for Traffic Filtering.]

• Support for higher scale of flows in the BGP FlowSpec filter. We now support a higher scale of flows in BGPFlowSpec filter. You can achieve this by reducing the number of terms in the BGP FlowSpec filter using the filter optimization techniques without affecting the functionality. The per-term counter is not configured by default. To create room for term compression, the default per-term counters are disabled. However, to enable per-term counter a new CLI command, per-route-accounting has been introduced under the existing [edit routing-protocols-flow] hierarchy level.” [See “per-route-accounting”].

Routing policy and firewall filters

• Support for nested filters. This feature enables you to reference a common firewall filter by attaching it to multiple firewall policies (a filter being one or more match conditions and corresponding actions). You can bind nested filters to the following interface types:

  • inet—Input and output directions
  • inet6—Input and output directions
  • mpls—Input direction only

  You can also bind them to routing instances, and in the input direction, the output direction, or both directions. [See Guidelines for Nesting References to Multiple Firewall Filters and Example: Nesting References to Multiple Firewall Filters.]

• Support for interface and class-usage accounting profiles. Use accounting profiles to collect persistent (locally saved) traffic statistics as an alternative to SNMP. Data collected through interface profiles can include input and output byte and packet counts for various protocols, interface errors, and RPF checks. Data collected through source and destination class-usage profiles can include per-interface traffic counts for the prefixes specified, for example to track traffic received on a per-customer basis for billing. Configure accounting profiles at the [edit accounting-options] hierarchy level. [See Understanding Accounting Profiles.]

Services applications

• Support for multiple collectors in inline active flow monitoring. You can now configure inline active flow monitoring to export flow records to up to four different collectors. Previously, inline flow monitoring could export flow records only to a single collector. [See Configuring Inline Active Flow Monitoring on PTX Series Routers.]

• Support for reporting of the true incoming interface for the sample packets for inline active flow monitoring. Inline active flow monitoring now reports the true incoming interface for the GRE-de-encapsulated packets entering the router for the configured inline active flow monitoring filter criteria. [See Understanding Inline Active Flow Monitoring and Configuring Flow Aggregation to Use IPFIX Flow Templates on PTX Series Routers.]

• Support for configuring UDP tunnel encapsulation on flexible tunnel interfaces (FTIs). You can configure encapsulation by using the tunnel encapsulation udp source address destination address command at the [edit interfaces fti unit unit] hierarchy level.

  • If you add the tunnel-termination statement, it makes the tunnel a de-encapsulation-only tunnel and disables the encapsulation.
  • You must specify both the source and destination addresses if you do not configure tunnel-termination.
  • You cannot configure a variable prefix mask on the source address.

  [See encapsulation.]

• Support for optics drivers upgrade. We’ve extended support to upgrade the optics drivers without a full Junos OS Evolved upgrade. You can upgrade the optics drivers by executing the request system software add variable>package_name</variable> command. [See Hardware Supported by Junos Continuity Software.]

• Support for FTI-based encapsulation and de-encapsulation of IPv4 and IPv6 packets. You can configure IP-IP encapsulation and de-encapsulation on an FTI. [See ipip.]

Class of service

• Support for priority-based flow control (PFC) of untagged traffic at Layer 3 and support for explicit congestion notification (ECN). [See Understanding PFC Using DSCP at Layer 3 for Untagged Traffic and Understanding CoS Explicit Congestion Notification.]

• Support for PFC watchdog. Use this feature to detect and mitigate PFC pause storms received for PFC-enabled queues. When a PFC-enabled port receives PFC pause frames for an extended period of time, the PFC watchdog mitigates the situation by disabling the affected queue for a configurable length of time called the recovery time. After the recovery time passes, the PFC watchdog re-enables PFC. [See PFC Watchdog.]

• Support for EVPN-MPLS. The router supports MAC VRF routing instances on the EVPN-MPLS network. [See EVPN User Guide.]

Hardware

• Use the hardware compatibility matrix to know about the optical interfaces and transceivers, active optical cables (AOCs), and direct attach copper (DAC) cables that we support on the PTX10K-LC1202-36MR line card. [See the Hardware Compatibility Tool.]

Interfaces and chassis

• We support RSVP-based and LDP-based point-to-multipoint (P2MP) label-switched paths (LSPs). [See Port Speed on PTX10K-LC1201 Overview.]

• Support for custom optics profile. You can now configure the optical module parameters of QSFP modules by using the CLI from the configuration prompt. In earlier releases, you could not configure the parameters from the configuration prompt. We do not support these module parameters for QSFP direct attach copper (DAC) cable modules or QSFP load modules. [See optics-options.]

• Support for 10-Gbps speed on SFP+-10G-T-DWDM-ZR and SFP+-10G-CWDM optics. We support 10-Gbps speed on these optics modules through the QSA adapter (MAM1Q00A-QSA) plugged into the QSFP or QSFP+ ports. You can select the wavelength on the SFP+-10G-T-DWDM-ZR optics. To see the list of optics supported by the PTX10K-LC1202-36MR line card, visit the Hardware Compatibility Tool page.

  Note:

  The ports 1, 3, 19, and 21 are disabled if the preceding ports (0, 2, 18, and 20) are not in 100-Gbps mode. This means, of the 36 ports on the line card, only 32 ports are available to be configured as 4x25-Gbps and 4x10-Gbps ports.

  [See PTX10K-LC1202-36MR Line Card.]

• Support for performance monitoring and TCA. We support transport performance monitoring and threshold-crossing alert (TCA) information for the QSFP28 100GE DWDM optical transceiver modules. You can view the diagnostic data, warnings, and alarms for transport performance monitoring interfaces. TCAs give the management system an early indication about the state of the associated entity when it crosses a certain threshold. [See show interfaces transport pm and tca.]

• Support for ALB on multiple Packet Forwarding Engines for aggregated Ethernet bundles. Adaptive load balancing (ALB) for aggregated Ethernet bundles evenly redistributes the traffic load across multiple ingress Packet Forwarding Engines on the same line card. [See Load Balancing on Aggregated Ethernet Interfaces.]

IP tunneling

• Support for IPv4 unicast tunneling. To support IP-over-IP on the PTX models, the routing protocol process (rpd) sends fully resolved next-hop-based tunnels to the Packet Forwarding Engine. [See Overview of Next-Hop-Based Dynamic Tunneling Using IP-Over-IP Encapsulation.]

Junos telemetry interface (JTI)

• Support for Jvision sensors cmerror configuration and cmerror counter for JTI. Junos telemetry interface (JTI) supports streaming chassis management error (cmerror) configuration and counters as well as Flexible PIC Concentrator (FPC) optics statistics to an outside collector using remote procedure calls (gRPC).

  We support the following cmerror base resource paths:

  • /junos/chassis/cmerror/configuration
  • /junos/chassis/cmerror/counters

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

• Support for platform, interface, and alarm statistics using JTI and gRPC Network Management Interface (gNMI) services. You can use this feature to send ON_CHANGE statistics of a device to an outside collector.

  This feature supports these OpenConfig models:

  • openconfig-platform.yang: oc-ext:openconfig-version 0.12.1
  • openconfig-interfaces.yang: oc-ext:openconfig-version 2.4.1
  • openconfig-alarms.yang: oc-ext:openconfig-version 0.3.1

  Use the following resource paths in a gNMI subscription:

  • /components/component (for each installed FRU)
  • /interfaces/interface/state/
  • /interfaces/interface/subinterfaces/subinterface/state/
  • /alarms/alarm/

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

Layer 2 features

• Support for the following basic Layer 2 learning, bridging, and flooding features:

  • Enterprise-style bridging (trunk and access modes)
  • Service-provider-style bridging (also known as sub-interface mode)
  • BUM (broadcast, unknown unicast, and multicast) traffic handling, including split horizon
  • MAC learning and aging
  • Static MAC addresses
  • Trunk port, VLAN membership, and native-vlan-id
  • 802.1Q EtherType - 8100
  • 802.1Q VLAN tagging: Single tagging with normalization
  • Clearing of all MAC address information
  • Global MAC limit
  • Global source MAC aging time
  • MAC moves
  • Disabling of MAC learning at global and interface levels.
  • 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 are not supported under flexible Ethernet services encapsulation.

  • Virtual switch
  • Persistent MAC learning (sticky MAC)
  • Service provider bridging:
    • Multiple logical interfaces (on a physical interface) which are part of same bridge domain
    • Ethernet bridge encapsulation

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

MPLS

• Support for LDP tunneling over segment routing–traffic engineering (SR-TE). You can tunnel LDP LSPs over SR-TE in your network. Tunneling LDP over SR-TE provides consistency and coexistence of LDP LSPs and SR-TE LSPs. [See Tunneling LDP LSPs in RSVP LSPs Overview.]

• Support for next-hop-based dynamic UDP tunnels, also known as MPLS-over-UDP tunnels. When you configure an MPLS-over-UDP tunnel, Junos OS dynamically creates a tunnel composite next hop, an indirect next hop, and a forwarding next hop to resolve the tunnel destination route. You can also use policy control to resolve MPLS-over-UDP tunnels over select IP prefixes. When you enable next hops by default, the MPLS-over-UDP feature provides a scaling advantage for the number of IP tunnels supported on the router. [See Example: Configuring Next-Hop-Based MPLS-Over-UDP Dynamic Tunnels.]

Multicast

• Support for PIM multicast features on the Layer 2 IRB interface. We support any-source multicast (ASM), PIM source-specific multicast (PIM SSM), and PIM dense mode (PIM DM). [See Multicast Routing Protocols.]

Network management and monitoring

• Support for RFC 3635. Junos OS Evolved supports all objects and tables defined in RFC 3635, except dot3StatsRateControlAbility and dot3StatsRateControlStatus in the dot3StatsEntry table.

  [See Standard SNMP MIBs Supported by Junos OS.]

• On PTX10K-LC1202-36MR line cards, you can configure 50-Gbps speed on ports 0, 2, 18, and 20 through QSFP28 optics. When you configure the port speed of any of the even ports (0, 2, 18, 20) as 2 x 50 Gbps, you must configure the odd ports (1, 3, 19, 21) as unused. You cannot configure 4x10GbE, 2x50GbE, 1x40GbE, and 4x25GbE simultaneously on the following ports:

  • 0 and 2
  • 18 and 20

  [See PTX10K-LC1202-36MR Port Speed.]

Routing protocols

• Support to label interfaces and match the interface-group ID on firewall filter. We support labeling of interfaces with specified group IDs from 1 to 255 and matching the interface-group ID on the firewall filter. The filter can identify which interface a packet comes from and perform actions specified only for a certain interface group. [See Understanding BGP Flow Routes for Traffic Filtering.]

• Support for FIB compression. Forwarding information base (FIB) compression overcomes the hardware limitation of storing a limited number of uncompressed routes. We've enabled FIB compression by default. You can now store a larger number of compressed IPv4 and IPv6 routes.

• Support for higher scale of flows in the BGP FlowSpec filter. We now support a higher scale of flows in BGPFlowSpec filter. You can achieve this by reducing the number of terms in the BGP FlowSpec filter using the filter optimization techniques without affecting the functionality. The per-term counter is not configured by default. To create room for term compression, the default per-term counters are disabled. However, to enable per-term counter a new CLI command, per-route-accounting has been introduced under the existing [edit routing-protocols-flow] hierarchy level.” [See “per-route-accounting”].

Segment routing

• Support for color-based mapping of VPN services over SR-TE LSPs. You can use both color-attribute and IP protocol next hops to resolve transport tunnels over static colored and BGP segment routing–traffic engineering (SR-TE) label-switched paths (LSPs). [See Color-Based Mapping of VPN Services Overview.]

Services applications

• Support for RFC 5357 Two-Way Active Measurement Protocol (TWAMP) monitoring service. TWAMP sends out probes to measure network performance and is often used to check compliance with service-level agreements. You can configure TWAMP at the [edit services monitoring twamp] hierarchy level. The support for this service is limited to the following:

  • IPv4 traffic only for control sessions and test sessions
  • Probe statistics and history
  • Control and test session status
  • Test session probe generation and reception, as well as reflection
  • Timestamps set by the Routing Engine or the Packet Forwarding Engine
  • Error reporting through system log messages only
  • Unauthenticated mode only

  [See Understanding Two-Way Active Measurement Protocol on Routers.]

• Support for configuring UDP tunnel encapsulation on flexible tunnel interfaces (FTIs). You can configure encapsulation by using the tunnel encapsulation udp source address destination address command at the [edit interfaces fti unit unit] hierarchy level.

  • If you add the tunnel-termination statement, it makes the tunnel a de-encapsulation-only tunnel and disables the encapsulation.
  • You must specify both the source and destination addresses if you do not configure tunnel-termination.
  • You cannot configure a variable prefix mask on the source address.

  [See encapsulation.]

• Support for FTI-based encapsulation and de-encapsulation of IPv4 and IPv6 packets. You can configure IP-IP encapsulation and de-encapsulation on an FTI. [See ipip.]

Software installation and upgrade

• Support for dynamically detecting the port speed of WAN interfaces during zero-touch provisioning (ZTP). [See Zero Touch Provisioning.]

• Support for either WAN interfaces or management interfaces to automatically download and install the appropriate software and the configuration file on your device during the ZTP bootstrap process. [See Zero Touch Provisioning.]