Configuring Flexible Tunnel Interfaces
Flexible Tunnel Interfaces Overview
A flexible tunnel interface (FTI) is a type of logical tunnel interface that uses static routing and BGP protocols to exchange routes over a tunnel that connects endpoints to routers.
- Flexible Tunnel Interfaces on MX Series Routers and SRX Series Firewalls
- Flexible Tunnel Interfaces on PTX Series Routers and QFX Series Switches
- MPLS Support for FTI tunnels on PTX Series Routers
- Flexible Tunnel Interfaces on ACX Series Routers
- MPLS Support for FTI tunnels on ACX Series Routers
- Benefits of Flexible Tunnel Interfaces
- Limitations of Flexible Tunnel Interfaces
Flexible Tunnel Interfaces on MX Series Routers and SRX Series Firewalls
FTIs have the following features on MX Series routers and SRX Series firewalls:
-
FTI supports only VXLAN encapsulation with Layer 2 pseudo-headers.
-
FTI is used between a router and a server hosting multiple virtual machines, or between routers in two different data centers.
-
FTI can be configured as port-mirror destinations.
-
FTI support logical interface statistics streaming.
In the VXLAN encapsulation process, the Layer 2 address is populated with “pseudo” source (source MAC: 00-00-5E-00-52-00) and destination (destination MAC: 00-00-5E-00-52-01) MAC addresses without VLAN tagging; however, these addresses are ignored when the packets reach the remote endpoint. The remote endpoint is identified by the destination IP address and a specified destination UDP port number. The corresponding FTI on the remote endpoint is identified by the virtual network identifier (VNI) value, the source IP address of the tunnel, and the destination UDP port number. All of these values can be configured on an FTI with VXLAN encapsulation.
Figure 1 illustrates how an FTI works to provide connectivity into a virtual private cloud from a remote location. Individual flexible tunnels (1 through N) are provisioned for every customer. The customer-facing logical interface and the corresponding FTIs are configured to operate in one routing instance. The FTI uses BGP protocols (eBGP and iBGP) to carry packets from the customer device to the remote gateway and vice versa.
Flexible Tunnel Interfaces on PTX Series Routers and QFX Series Switches
Some PTX Series routers and QFX Series switches support FTIs. For details on platform and Junos version support, see Feature Explorer. FTI support on PTX and QFX switches include the following features:
-
FTI is supported in releases starting Junos OS Release 19.3R1.
-
FTI supports only UDP encapsulation.
-
FTI can be initiated at any place in the MPLS tunnel: MPLS transit, ingress, egress, and PHP.
-
FTI with UDP encapsulation supports the following payloads:
-
IPV4 inside IPV4 UDP packet
-
IPV6 inside IPV4 UDP packet
-
MPLS inside IPV4 UDP packet
-
ISO inside IPV4 UDP packet
-
FTI with UDP encapsulation supports the following features and functionality:
-
MPLS link protection and node-link protection.
-
Manual configuration of RSVP bandwidth.
-
BFD support for liveliness detection, excluding BFD over LDP and RSVP.
-
Support for the following protocols:
-
BGP
-
RSVP
-
LDP
-
OSPF
-
ISIS
-
-
Static routes.
-
FTI logical interface statistics.
-
MTU configuration on FTI and fragmentation of payload before entering the tunnel.
-
Underlay can be Aggregated Ethernet or regular interface, and can be tagged sub-interface or regular Layer 3 interfaces.
-
Overlay and underlay ECMP.
To configure an FTI interface with UDP encapsulation, include the udp
statement at the [edit interfaces fti0 unit
unit tunnel encapsulation] hierarchy level.
For example:
[edit interfaces]
fti0 {
unit unit_number {
tunnel {
encapsulation udp {
source {
address ipv4_address;
}
destination{
address ipv4_address;
}
}
}
family inet {
destination-udp-port udp port [range 10000-10009] ;
}
family inet6 {
destination-udp-port udp port [range 10010-10019];
}
family mpls {
destination-udp-port udp port [range 10020-10029];
}
family iso {
destination-udp-port udp port [range 10030-10039];
}
}
}
MPLS Support for FTI tunnels on PTX Series Routers
Starting In Junos OS Evolved Release 21.4R1, you can configure MPLS protocols over FTI tunnels, thereby transporting MPLS packets over IP networks which does not support MPLS.
In Junos OS Evolved Release 21.4R1, generic routing encapsulation (GRE) and UDP tunnels support MPLS protocol for IPv4 and IPv6 traffic. You can configure encapsulation and decapsulation for the GRE and UDP tunnels.
The following features are supported :
-
Encapsulation and decapsulation for IPv4 and IPv6 traffic
-
UDP port number configuration
-
MPLS node-link protection
-
Ingress, egress, PHP, and transit roles for LSP
-
Ping and traceroute support in ingress, egress, PHP, and transit roles for LSP
-
Overlay and underlay ECMP
-
Manual configuration of RSVP bandwidth.
-
MPLS services
-
L3VPN
-
6VPE
-
L2 circuit
-
BGP-LU with per nexhop or prefix label
-
-
Routing instance
-
Class-of-service (CoS) including the configuration of rewrite rules and classifiers
-
MTU configuration and fragmentation of payload
-
BFD support for liveliness detection.
-
Jvision
The following features and functionality are not supported:
-
MPLS link protection
-
RSVP bandwidth Inheritance based on next hop to tunnel destination for FTI interfaces
-
TTL propagation.
-
Class-of-service on tunnel endpoints .
-
FT-over-FT resolution .
-
FT destination IP should be reachable through IGP and not BGP (no indirect next hop). The reachability should be through an IPV4 route and not through an LSP.
-
Path MTU discovery .
To allow the MPLS traffic on the UDP tunnels include the mpls
port-number statement at the [edit
forwarding-options tunnels udp port-profile
profile-name] hierarchy level. To allow the MPLS
traffic on the GRE tunnels, include the mpls statement at the
[edit interfaces fti0 unit unit
family] hierarchy.
For example:
[edit forwarding-options]
tunnels {
udp {
port-profile p1 {
inet <port num>
inet6 <port num>
mpls <port num>
iso <port num>
}
}
}
Flexible Tunnel Interfaces on ACX Series Routers
Starting in Junos OS Evolved Release 24.2R1, you can
configure encapsulation by using the tunnel encapsulation gre source
address destination address
command at the [edit interfaces fti unit unit]
hierarchy level. For details on platform and Junos version support, see Feature Explorer.
The following features are supported:
-
FTI interface based GRE encapsulation and de-encapsulation mode
-
inet, inte6, iso payloads
-
Both IPv4 and IPv6 as overlay
-
Both IPv4 and IPv6 as underlay
-
BFD, OSPF, ISIS, and static route
-
Underlay and overlay ECMP
-
FTI IFL statistics
-
MTU configuration on FTI.
-
TTL configuration on FTI.
-
Host ping
-
FTI link up or down status based on tunnel end point reachability
-
ECMP of FTI and regular interfaces
-
Input Filter support on FTI at de-encapsulation side.
-
Tunnel-termination only mode
-
Path MTU discovery for both IPv4 and IPv6 encapsulation
-
Anti-spoofing at tunnel decapsulation for the inner source IP
-
Flexible-vlan-tagging
-
Tunnel destination reachablility over other tunnel
-
MTU exception generation when FTI IFF MTU value is high and underlay IFF MTU is low
-
Output filter applied on tunnel underlay interface for tunnelled packet as well as payload due to data path limitation
-
Input filter applied on NNI interface at tunnel de-encapsulation node for tunnelled packet as well as payload due to data path limitation
-
FTI tunnel along with dynamic next hop tunnel for the same tunnel configuration.
-
FTI IFF disable and enable
-
IP Fragmentation at tunnel start point and end point
-
Tunnel encapsulation stats is not supported for MPLS encapsulated packet sent over a tunnel with both tunnel and MPLS stats enabled. Only MPLS stats is supported.
-
You can configure tunnel encapsulation or de-encapsulation stats using the
set system packet-forwarding-options tunnel encap-stats-enableandset system packet-forwarding-options tunnel decap-stats-enablestatements. When you use the CLI (set/delete/deactivate),datapath restartoccurs to associate or disassociate counters with the tunnel.
To configure an FTI interface with GRE encapsulation, include the
gre
statement at the [edit interfaces fti0 unit
unit tunnel encapsulation] hierarchy
level.
For example:
[edit interfaces]
fti0 {
unit unit-number{
tunnel {
encapsulation gre {
source {
address ipv4/ipv6_address;
}
destination {
address ipv4/ipv6_address;
}
tunnel-routing-instance {
routing-instance instance name;
}
bypass-loopback;
ttlttl-value;
}
}
family inet {
address ip_address ;
}
family inet6 {
address ip_address;
}
family mpls;
family iso;
}
}Starting in Junos OS Evolved Release 24.2R1, ACX series support FTI with UDP encapsulation and de-encapsulation. For details on platform and Junos version support, see Feature Explorer.
The following features are supported:
-
FTI with UDP supports the following payloads:
-
IPv4 inside IPv4 UDP packet
-
IPv6 inside IPv4 UDP packet
-
MPLS inside IPv4 UDP packet
-
ISO inside IPv4 UDP packet
-
IPv4 inside IPv6 UDP packet
-
IPv6 inside IPv6 UDP packet
-
MPLS inside IPv6 UDP packet
-
ISO inside IPv6 UDP packet
-
-
Support for the following protocols:
-
BGP
-
BFD
-
OSPF
-
ISIS
-
-
Static routes.
-
FTI logical interface statistics.
-
MTU configuration on FTI.
-
TTL configuration on FTI.
-
Overlay and underlay ECMP.
-
bypass-loopbackconfiguration andpayload-port-profile profile nameconfiguration is mandatory.
-
Tunnel-termination only mode
-
Path MTU discovery for both IPv4 and IPv6 encapsulation
-
Anti-spoofing at tunnel decapsulation for the inner source IP
-
Flexible-vlan-tagging
-
Tunnel destination reachablility over other tunnel
-
MTU exception generation when FTI IFF MTU value is high and underlay IFF MTU is low
-
Output filter applied on tunnel underlay interface for tunnelled packet as well as payload due to data path limitation
-
Input filter applied on NNI interface at tunnel de-encapsulation node for tunnelled packet as well as payload due to data path limitation
-
FTI tunnel along with dynamic next hop tunnel for the same tunnel configuration.
-
FTI IFF disable and enable
-
IP Fragmentation at tunnel start point and end point
-
Tunnel encapsulation stats is not supported for MPLS encapsulated packet sent over a tunnel with both tunnel and MPLS stats enabled. Only MPLS stats is supported.
-
You can configure tunnel encapsulation or de-encapsulation stats using the
set system packet-forwarding-options tunnel encap-stats-enableandset system packet-forwarding-options tunnel decap-stats-enablestatements. When you use the CLI (set/delete/deactivate),datapath restartoccurs to associate or disassociate counters with the tunnel.
To configure an FTI interface with UDP encapsulation, include the udp
statement at the [edit interfaces fti0 unit
unit tunnel encapsulation] hierarchy
level.
For example:
[edit interfaces]
fti0 {
unit unit-number{
tunnel {
encapsulation udp {
source {
address ipv4/ipv6_address;
}
destination {
address ipv4/ipv6_address;
}
tunnel-routing-instance {
routing-instance instance name;
}
bypass-loopback;
payload-port-profile profile name{
inet port num;
inet6 port num;
mpls port num;
iso port num;
}
ttlttl-value;
}
}
family inet {
address ip_address ;
}
family inet6 {
address ip_address;
}
family mpls;
family iso;
}
}MPLS Support for FTI tunnels on ACX Series Routers
Starting In Junos OS Evolved Release 24.2R1, you can configure MPLS protocols over FTI tunnels on ACX series routers, thereby transporting MPLS packets over IP networks which does not support MPLS.
In Junos OS Evolved Release 24.2R1, generic routing encapsulation (GRE) and UDP tunnels support MPLS protocol for IPv4 and IPv6 traffic on ACX series routers. You can configure encapsulation and decapsulation for the GRE and UDP tunnels. For details on platform and Junos version support, see Feature Explorer.
The following features are supported :
-
Encapsulation and decapsulation for IPv4 and IPv6 traffic
-
UDP port number configuration
-
Ping and traceroute support in ingress, egress, PHP, and transit roles for LSP
-
Overlay and underlay ECMP
-
LDP, RSVP, static LSP, and BGP protocols with encapsulation and decapsulation
-
Support different tunnel termination scenarios, MPLSoGRE or MPLSoUDP tunnel can start at any of the following cases:
-
MPLS Label Edge Router (LER)
-
MPLS Label Switch Router (LSR)
-
MPLS PHP
-
MPLS Egress PE
-
-
MPLS services
-
L3VPN
-
6VPE
-
6PE
-
-
Tunnel-termination only mode
-
Path MTU discovery for both IPv4 and IPv6 encapsulation
-
Anti-spoofing at tunnel decapsulation for the inner source IP
-
Flexible-vlan-tagging
-
Tunnel destination reachablility over other tunnel
-
MTU exception generation when FTI IFF MTU value is high and underlay IFF MTU is low
-
Output filter applied on tunnel underlay interface for tunnelled packet as well as payload due to data path limitation
-
Input filter applied on NNI interface at tunnel de-encapsulation node for tunnelled packet as well as payload due to data path limitation
-
FTI tunnel along with dynamic next hop tunnel for the same tunnel configuration.
-
FTI IFF disable and enable
-
IP Fragmentation at tunnel start point and end point
-
Tunnel encapsulation stats is not supported for MPLS encapsulated packet sent over a tunnel with both tunnel and MPLS stats enabled. Only MPLS stats is supported.
-
You can configure tunnel encapsulation or de-encapsulation stats using the
set system packet-forwarding-options tunnel encap-stats-enableandset system packet-forwarding-options tunnel decap-stats-enablestatements. When you use the CLI (set/delete/deactivate),datapath restartoccurs to associate or disassociate counters with the tunnel.
To configure MPLS traffic on GRE or UDP tunnel include the
mpls statement at the [edit interfaces
fti0 unit unit family]
hierarchy.
[edit interfaces]
fti0 {
unit unit-number{
tunnel {
encapsulation (gre | udp) {
source {
address ipv4/ipv6_address;
}
destination {
address ipv4/ipv6_address;
}
tunnel-routing-instance {
routing-instance instance name;
}
bypass-loopback;
payload-port-profile profile name{
inet port num;
inet6 port num;
mpls port num;
iso port num;
}
ttlttl-value;
}
}
family inet {
address ip_address;
}
family inet6 {
address ip_address;
}
family mpls;
family iso;
}
}Benefits of Flexible Tunnel Interfaces
-
Entropy and load balancing occur in transit. Unlike over tunnel encapsulations, such as IP in IP or generic routing encapsulation (GRE), VXLAN encapsulation supports passing of the hash computation result in the source port of the UDP datagram. This enables you to load-balance traffic efficiently in transit.
-
FTIs have an extensible design that enables them to support multiple encapsulations.
-
The
vniattribute of the VXLAN encapsulation in FTIs helps in customer isolation. -
FTIs with UDP encapsulation use the source and destination port in the UDP header. Because the UDP source port is derived from the hash value of the inner payload, you can benefit from better traffic distribution over ECMP.
Limitations of Flexible Tunnel Interfaces
-
Policing follows the distributed forwarding model of the FTIs; therefore provisioned bandwidth limits are enforced at an individual Packet Forwarding Engine level. As a result, more traffic might be admitted.
-
Currently, FTI-tunneled traffic is strictly routed in the
inet.0instance. Therefore, FTIs support only IPv4 traffic. -
The MX80 does not support FTIs.
-
Class-of-service (CoS) configuration, including the configuration of rewrite rules and classifiers is not supported on FTIs.
-
Time-to-live (TTL) on the tunnel header is set to the default value 64.
-
Differentiated Services code point (DSCP) value is set to the default value 0, but internal forwarding class and loss priority fields are retained and can be used to rewrite DSCP in the egress interface rewrite rules.
-
IP fragmentation is not supported on FTIs.
FTI with UDP encapsulation do not support the following features and functionality:
-
BFD over LDP and RSVP is not supported.
-
Aggregate Ethernet member statistics on QFX1000 device is not supported.
-
10,000 routes per FTI logical interface is not supported.
-
Routing instance is not supported.
-
Logical systems is not supported.
-
Path MTU discovery is not supported.
-
Policing and firewall is not supported.
-
BGP signaling for UDP tunnels is not supported.
-
Class-of-service on tunnel endpoints is not supported.
-
TTL propagation is not supported.
-
Multicast traffic is not supported.
-
Plain IPV6 UDP tunnel is not supported.
-
Anti-spoofing check for tunneled traffic is not supported.
-
MPLS FRR is not supported.
-
FT-over-FT resolution is not supported.
-
FT destination IP should be reachable through IGP and not BGP (no indirect next hop). The reachability should be through an IPV4 route and not through an LSP.
-
FT physical interface level statistics is not supported.
-
All the interfaces under FTI except for fti0 are not supported.
-
Un-numbered address is not supported.
See Also
Configuring Flexible Tunnel Interfaces
You can configure flexible tunnel Interfaces (FTIs) that support the Virtual Extensible LAN (VXLAN) encapsulation with Layer 2 pseudo-headers on MX Series routers, or UDP encapsulation on PTX Series routers and QFX Series switches. A flexible tunnel interface (FTI) is a point-to-point Layer 3 interface that can be used to create IPv4 and IPv6 overlays over an IPv4 transport network. A BGP protocol session can be configured to run over FTIs in order to distribute routing information.
The following sections describe how to configure FTIs on your
device and to enable multiple encapsulations using the udp or vxlan-gpe parameter under the
mandatory tunnel-endpoint vxlan encapsulation
identified with the vni and destination-udp-port values:
Configuring FTI on PE1
You can configure an FTI by including the tunnel-endpoint
vxlan statement at the [edit interfaces] hierarchy
level.
To configure an FTI and define its attributes for an IPv4 network:
Verification
Purpose
Verify that the FTI is configured and verify its status.
Action
In configuration mode, you can verify if FTI on MX Series
router has been configured by executing the show interfaces fti number command.
user@host# show interfaces fti0
Physical interface: fti0, Enabled, Physical link is Up
Interface index: 136, SNMP ifIndex: 504
Type: FTI, Link-level type: Flexible-tunnel-Interface, MTU: Unlimited, Speed: Unlimited
Device flags : Present Running
Interface flags: SNMP-Traps
Link type : Full-Duplex
Link flags : None
Last flapped : Never
Input packets : 0
Output packets: 0
Logical interface fti0.0 (Index 340) (SNMP ifIndex 581)
Flags: Up Point-To-Point SNMP-Traps Encapsulation: VXLAN-GPEv4
Destination UDP port: 4789, VNI: 1000, Source address: 5.5.5.5, Destination address: 6.6.6.6
Input packets : 0
Output packets: 0
Protocol inet, MTU: Unlimited
Max nh cache: 0, New hold nh limit: 0, Curr nh cnt: 0, Curr new hold cnt: 0, NH drop cnt: 0
Flags: Sendbcast-pkt-to-re
Addresses, Flags: Is-Preferred Is-Primary
Destination: 3.3.3/24, Local: 3.3.3.5, Broadcast: 3.3.3.255
Similarly you can execute the show interfaces fti0 detail, show interfaces fti0 extensive, show interfaces
fti0 terse, and show interfaces fti0 statistics commands
to get more details FTIs. See show interfaces
fti.
Meaning
The show interfaces fti0 command displays
the status of the FTIs that have been configured with the new encapsulation vxlan-gpe. The output verifies that the FTI is configured and
the physical link is up.
Configuring a Flexible Tunnel Interface on an SRX Firewall
When you configure a Flexible Tunnel Interface (FTI) on an SRX firewall, you must also configure the zone and security policy for the interface.
A security zone is a collection of one or more network segments that requires the regulation of inbound and outbound traffic through policies. You assign the FTI to one of the security zone and the FTI functions as a security doorway from one security zone to another. Security policies control the traffic flow through the FTI. You can configure the security policies on the SRX firewall to permit or deny traffic pass through the FTI. The following sample configuration shows how to configure an FTI on the SRX firewall.
-
Configure the FTI with
vxlan-gpeencapsulation.set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe source address 198.51.100.1 set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe destination address 198.51.100.2 set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe tunnel-endpoint vxlan set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe destination-udp-port 4789 set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe vni 22701 set interfaces fti0 unit 0 family inet address 198.51.100.1/24 set interfaces lo0 unit 0 family inet address 192.168.100.1
-
Configure and assign the FTI to a security zone. For more information on security zones, see https://www.juniper.net/documentation/us/en/software/junos/security-policies/topics/topic-map/security-zone-configuration.html.
set security zones security-zone FTI-ZONE host-inbound-traffic system-services all set security zones security-zone FTI-ZONE host-inbound-traffic protocols all set security zones security-zone FTI-ZONE interfaces fti0.0
-
Create a policy for traffic being sent to the FTI and the actions that need to take place as the traffic passes through the interface. In this example, we permit all traffic to pass through. For more information on configuring security policies, see https://www.juniper.net/documentation/us/en/software/junos/security-policies/topics/topic-map/security-policy-configuration.html.
set security policies from-zone FTI-ZONE to-zone trust policy fti-out match source-address any set security policies from-zone FTI-ZONE to-zone trust policy fti-out match destination-address any set security policies from-zone FTI-ZONE to-zone trust policy fti-out match application any set security policies from-zone FTI-ZONE to-zone trust policy fti-out then permit set security policies from-zone FTI-ZONE to-zone trust policy fti-in match source-address any set security policies from-zone FTI-ZONE to-zone trust policy fti-in match destination-address any set security policies from-zone FTI-ZONE to-zone trust policy fti-in match application any set security policies from-zone FTI-ZONE to-zone trust policy fti-in then permit set routing-options static route 198.51.100.2/32 next-hop 10.100.12.2
Verify Flexible Tunnel Creation
Use the show interfaces fti0.0 command to display information about the flexible tunnel interface:
user@device1>show interfaces fti0.0
Logical interface fti0.0 (Index 72) (SNMP ifIndex 520)
Flags: Up Point-To-Point SNMP-Traps Encapsulation: VXLAN-GPEv4
Destination UDP port: 4789, Source UDP port range: [49160 - 65535],
VNI: 22701, Source address: 10.0.0.2, Destination address: 10.0.0.1
Input packets : 0
Output packets: 5
Security: Zone: FTI-ZONE
Allowed host-inbound traffic : bootp bfd bgp dns dvmrp igmp ldp msdp nhrp ospf ospf3 pgm pim rip ripng router-discovery
rsvp sap vrrp dhcp finger ftp tftp ident-reset http https ike netconf ping reverse-telnet reverse-ssh rlogin rpm rsh snmp
snmp-trap ssh telnet traceroute xnm-clear-text xnm-ssl lsping lsselfping ntp sip dhcpv6 r2cp webapi-clear-text webapi-ssl
tcp-encap sdwan-appqoe high-availability
Protocol inet, MTU: 1450
Max nh cache: 0, New hold nh limit: 0, Curr nh cnt: 0, Curr new hold cnt: 0, NH drop cnt: 0
Flags: Sendbcast-pkt-to-re
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.18.1/24, Local: 10.18.1.2, Broadcast: 10.18.1.255
Example: Configuring Flexible Tunnel Interfaces on MX Series Routers
Requirements
This example uses the following hardware and software components:
An MX10003 and an MX Series 5G Universal Routing Platform.
Junos OS Release 18.3 or later.
Overview
In this example, flexible tunnel interfaces are used to create a Layer 3 VPN overlay network between two routers. In the actual deployment, one of the endpoints can be the server in a data center or a data center gateway.
Consider a sample topology in which a gateway device, PE1, functions as a link between the enterprise customers to represent the customer side for an FTI tunnel. eBGP is used to distribute routes between customer edge (CE1) and provider edge (PE1) devices. IPv4 is used for transmission of test frames over the Layer 3 network. This test is used to transfer the traffic between CE1 and CE2. Logical interfaces on both the routers are configured with IPv4 addresses to create an FTI to transfer the traffic of network devices for the IPv4 service.
Figure 2 shows the sample topology of how an FTI performs for a Layer 3 IPv4 service.
Configuration
In this example, you configure FTI for a Layer 3 IPv4 service that is between interface fti0 on PE1 and interface fti0 on PE2 to form a tunnel interface of the interconnecting routers.
CLI Quick Configuration
To quickly configure this example, copy the
following commands, paste them in a text file, remove any line breaks,
change any details necessary to match your network configuration,
and then copy and paste the commands into the CLI at the [edit] hierarchy level:
To Configure Parameters on PE1
set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe source address 198.51.100.1 set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe destination address 198.51.100.2 set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe tunnel-endpoint vxlan set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe destination-udp-port 4789 set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe vni 22701 set interfaces fti0 unit 0 family inet address 198.51.100.1/24
To Configure Parameters on PE2
set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe source address 198.51.100.2 set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe destination address 198.51.100.1 set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe tunnel-endpoint vxlan set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe destination-udp-port 4789 set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe vni 22701 set interfaces fti0 unit 0 family inet address 198.51.100.2/24
Configuring on PE1
Step-by-Step Procedure
The following steps require you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the Junos OS CLI User Guide.
To configure the parameters on PE1:
In configuration mode, go to the
[edit interfaces]hierarchy level:[edit] user@host# edit interfaces
Configure the FTI and a logical unit and specify the protocol family.
[set interfaces] user@host# set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe
Specify the source address for the logical interface.
[set interfaces] user@host# set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe source address 198.51.100.1
Specify the destination address for the logical interface.
[set interfaces] user@host# set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe destination address 198.51.100.2
Set
tunnel-endpointwith the encapsulationvxlan.[set interfaces] user@host# set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe tunnel-endpoint vxlan
Specify the UDP port value of the destination to be used in the UDP header for the generated frames.
[set interfaces] user@host# set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe destination-udp-port 4789
Specify the
vnivalue to be used to identify the encapsulationvxlan-gpeon the interface.[set interfaces] user@host# set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe vni 22701
Specify the address type family for the interface.
[set interfaces] user@host# set interfaces fti0 unit 0 family inet address 198.51.100.1/24
Configuring on PE2
Step-by-Step Procedure
The following steps require you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the Junos OS CLI User Guide.
To configure the parameters on PE2:
In configuration mode, go to the
[edit interfaces]hierarchy level:[edit] user@host# edit interfaces
Configure the FTI and a logical unit and specify the protocol family.
[set interfaces] user@host# set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe
Specify the source address for the logical interface.
[set interfaces] user@host# set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe source address 198.51.100.2
Specify the destination address for the logical interface.
[set interfaces] user@host# set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe destination address 198.51.100.1
Set
tunnel-endpointwith the encapsulationvxlan.[set interfaces] user@host# set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe tunnel-endpoint vxlan
Specify the UDP port value of the destination to be used in the UDP header for the generated frames.
[set interfaces] user@host# set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe destination-udp-port 4789
Specify the
vnivalue to be used to identify the encapsulationvxlan-gpeon the interface.[set interfaces] user@host# set interfaces fti0 unit 0 tunnel encapsulation vxlan-gpe vni 22701
Specify the address type family for the interface.
[set interfaces] user@host# set interfaces fti0 unit 0 family inet address 198.51.100.2/24
After the configuration is successfully completed, you can view the parameters by entering the
show fti0command.
Results
In configuration mode, confirm your configuration on
PE1 and PE2 by entering the show command. If the output
does not display the intended configuration, repeat the configuration
instructions in this example to correct it.
Parameters on PE1:
[edit interfaces]
fti0{
unit 0 {
tunnel {
encapsulation vxlan-gpe {
source {
address 198.51.100.1;
}
destination {
address 198.51.100.2;
}
tunnel-endpoint vxlan;
destination-udp-port 4789;
vni 22701;
}
}
family inet {
address 198.51.100.1/24;
}
} Parameters on PE2:
[edit interfaces]
fti0{
unit 0 {
tunnel {
encapsulation vxlan-gpe {
source {
address 198.51.100.2;
}
destination {
address 198.51.100.1;
}
tunnel-endpoint vxlan;
destination-udp-port 4789;
vni 22701;
}
}
family inet {
address 198.51.100.2/24;
}
} After you have configured the interface, enter the commit command in configuration mode.
Verification
Verifying the Results
Purpose
Verify that the necessary and desired tunnel displays the values configured for the FTI test that is run on the flexible tunnel between PE1 and PE2.
Action
In operational mode, enter the show interfaces
fti0 command to display status of the FTIs that have been configured
with the new encapsulation vxlan-gpe. The output verifies
that the FTI is configured and the physical link is up.
Configuring IP-IP Decapsulation by Tunnel Termination on FTI
In filter based decapsulation, the decapsulated packets are
re-circulated for inner header lookup and forwarded accordingly. However,
tunnel termination is completed in a single pass of packet processing,
thus providing performance improvement over filter based process. Starting in Junos OS Evolved Release 20.1R2,
you can configure IP-IP decapsulation on a flexible tunnel interface
on PTX series routers by configuring tunnel termination. You can configure IP-IP decapsulation on a flexible tunnel interface
by configuring tunnel termination at the [edit interfaces fti0
unit number tunnel encapsulation IPIP] hierarchy
level.
For the Junos OS Evolved Release 20.1R2, FTI does not support encapsulation.
To configure IP-IP decapsulation by tunnel termination:
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.