Flexible Ethernet services is a type of encapsulation that enables a physical interface to support different types of Ethernet encapsulations at the logical interface level. You can configure the Flexible Ethernet services encapsulation to support the service provider and the enterprise-style configuration. The below topics discuss the overview of flexible Ethernet services encapsulation and its configuration details.
Understanding Flexible Ethernet Services Encapsulation on Switches
Junos OS supports two different styles of configurationfor switch interfaces: the service provider style and the enterprisestyle. The service provider style requires more configuration butprovides greater flexibility. The enterprise style is easier to configurebut offers less functionality. Each configuration style requires adifferent Ethernet encapsulation type. You can configure a physicalinterface to support both styles of configuration using flexible Ethernetservices.
Note:
On EX4300, QFX5100 (running Junos OS 16.1R5 or earlier),and QFX5200, the service provider style and enterprise style interfaceconfigurations are handled differently within Junos OS. If the serviceprovider style and enterprise style interface configurations are mixed,the egress VLAN translation within the hardware can be incorrectlyprogrammed leading to forwarding issues across the configured ports.Use the service provider style configuration in a Q-in-Q scenario.For all other scenarios, use the enterprise style configuration.
Flexible Ethernet services is a type of encapsulation that enablesa physical interface to support different types of Ethernet encapsulationsat the logical interface level. Defining multiple per-unit Ethernetencapsulations makes it easier to customize Ethernet-based servicesto multiple hosts connected to the same physical interface.
- Service Provider Style
- Enterprise Style
- Flexible Ethernet Services
Service Provider Style
The service provider style of configuration allows for customizationof Ethernet-based services at the logical interface level. Serviceproviders typically have multiple customers connected to the samephysical interface. Using the service provider style, you can configuremultiple logical interfaces on the physical interface, and associateeach unit with a different VLAN. This provides the flexibility toconfigure different services for each customer, but also requiresmore configuration, because each feature must be explicitly configuredon the logical interface.
When configuring a physical interface to support only the serviceprovider style, the physical interface must be encapsulated with the extended-vlan-bridge option to support bridging features. VLANtagging must also be configured on the physical interface so thatit can operate in trunk mode and transmit Ethernet frames with VLANtags for multiple VLANs. Each logical interface is bound to a uniqueVLAN ID.
Enterprise Style
The enterprise style of configuration is designed to providebasic bridging functionality for consumers of Ethernet-based services.The isolation of services for different customers on a single portis not required, because each port is typically connected to a hostor is providing a trunk to another switch.
With the enterprise style of configuration, logical interfacesare placed into Layer 2 mode by specifying ethernet-switching as the interface family. Without using flexible Ethernet services, ethernet-switching can only be configured on a single logicalunit, unit0. You cannot bind a VLAN ID to unit0, becausethese interfaces operate either in trunk mode, which supports trafficwith various VLAN tags, or in access mode, which supports untaggedtraffic.
Flexible Ethernet Services
The flexible Ethernet services encapsulation type enables aphysical interface to support both styles of configuration. To supportthe service provider style, flexible Ethernet services allows forencapsulations to be configured at the logical interface level insteadof the physical interface. To support the enterprise style, flexibleEthernet services allows the ethernet-switching familyto be configured on any logical interface unit number instead of onlyunit0.
For example, the configuration below shows three logical interfacesconfigured on a physical interface, xe-0/0/51, that is encapsulatedfor flexible Ethernet services. Unit100 and unit200 areconfigured in the service provider style and unit300 is configuredin the enterprise style. The encapsulation type of vlan-bridge is used to enable bridging on unit100 and unit200, and family ethernet-switching enables bridging on unit300.
interfaces { xe-0/0/51 { flexible-vlan-tagging; encapsulation flexible-ethernet-services; unit 100 { encapsulation vlan-bridge; vlan-id 100; } unit 200 { encapsulation vlan-bridge; vlan-id 200; } unit 300 { family ethernet-switching { interface-mode trunk; vlan members 300; } } }}Following are the guidelines to follow when you configure theflexible Ethernet services encapsulation:
On the QFX10000 line of switches, configuring either
vlan-taggingorflexible-vlan-taggingwithfamily ethernet-switchingon the same interface is not supported.Only on the QFX10000 and EX9200 line of switches, youcan enable
vlan-cccencapsulation whenflexible-ethernet-servicesis already enabled.On QFX5100 switches, you can combine encapsulations onthe same physical interface for
vlan-bridgeandfamilyethernet switching. Starting with Junos OS Release 16.1R6, you can also combine encapsulationson the same physical interface forfamily inetandfamily ethernet-switching.It is not required that the unit number and VLAN ID match,but it is considered a best practice.
Configuring Flexible Ethernet Services Encapsulation to Supportthe Service Provider and Enterprise Styles of Configuration
Flexible Ethernet services is a type of encapsulation that enables a physical interface tospecify Ethernet encapsulations at the logical interface level. Eachlogical interface can have a different Ethernet encapsulation. Definingmultiple per-unit Ethernet encapsulations makes it easier to customizeEthernet-based services to multiple hosts connected to the same physicalinterface.
An Ethernet interface that is not encapsulated with flexibleEthernet services and is operating in Layer 2 mode is limited to asingle logical interface unit (0). Bridging is enabled on the interfaceby configuring ethernet-switching as the interface familyon unit0. The ethernet-switching family can be configuredonly on logical interface unit0, and no other logical unitscan be defined on that interface.
Some switching features, however, cannot be configured on logicalinterface unit0. Features such as Q-in-Q tunneling require thelogical interface to transmit VLAN-tagged frames. To enable a logicalinterface to receive and forward Ethernet frames tagged with a matchingVLAN ID, you must bind the logical interface to that VLAN. These featuresmust be configured on a logical interface unit other than0,because you cannot bind a VLANID to unit0.
When you encapsulate an interface by using flexible Ethernetservices, you can configure a logical interface unit other than0with family ethernet-switching. You can also configureother logical interfaces on that same interface with different typesof Ethernet encapsulations. This enables logical interfaces that arebound to a VLAN ID to coexist with logical interfaces configured with family ethernet-switching.
For example, if you configure PVLAN on the same physical interfaceon which you are configuring Q-in-Q tunneling, you can use flexibleethernet services to support the enterprise style of configurationfor PVLAN, using family ethernet-switching, along with vlan-bridge encapsulation for Q-in-Q tunneling.
Best Practice:
We recommend you configure the following statements using groupswhen configuring devices that function as hardware VTEPs:
set interfaces interface-name flexible-vlan-tagging
set interfaces interface-name encapsulationextended-vlan-bridge
set interfaces interface-name native-vlan-id vlan-id
To configure the interface to support both the serviceprovider and enterprise styles of configuration:
- Enable flexible Ethernet services encapsulation on theinterface. The
flexible-ethernet-servicesstatement allowsconfiguration of both service-provider-style logical interfaces andenterprise-style logical interfaces:[edit interfaces interface-name]user@switch# set encapsulation flexible-ethernet-services
- Enable the interface to transmit packets with 802.1Q VLANsingle-tagged and dual-tagged frames:
[edit interfaces interface-name]user@switch# set flexible-vlan-tagging
- Configure a logical interface (unit) on the interface:
[edit interfaces interface-name]user@switch# set unit unit-number
Note:
Do not use logical interface unit 0. You must later binda VLAN tag ID to the unit you specify in this step, and you cannotbind a VLAN tag ID to unit 0. It is a best practice to match the unitnumber to the VLAN ID to which the interface is bound.
- Encapsulate the logical interface for service providerstyle bridging configuration—for example, use
vlan-bridgeencapsulation on an interface to be used for Q-in-Q tunneling. (Ifyou were configuring the interface only for Q-in-Q tunneling, youwould useencapsulation extended-vlan-bridgeon the physical interface.)[edit interfaces interface-name]user@switch# set unit unit-number encapsulation vlan-bridge
- Bind the logical interface from the preceding step toa VLAN ID:
[edit interfaces interface-name]user@switch# set unit unit-number vlan-id vlan-id
- Configure another logical interface. (If you were configuringjust PVLAN, we would recommend that you configure a single logicalinterface for all PVLAN domains on an interface.)
[edit interfaces interface-name]user@switch# set unit unit-number
- Enable the logical interface in the preceding step forenterprise style bridging configuration:
[edit interfaces interface-name]user@switch# set unit unit-number family ethernet-switching
- Assign VLAN membership to the logical interface:
[edit interfaces interface-name]user@switch# set unit unit-number family ethernet-switching vlan members vlan-id
- Configure the interface as a trunk interface to transmitframes with 802.1Q VLAN tags:
[edit interfaces interface-name]user@switch# set unit unit-number family ethernet-switching interface-mode trunk
Note:
For EX4300 device, the service provider style configuration(encapsulation extended-vlan-bridge) is recommended only for QinQscenarios. For other scenarios, use the enterprise style configuration.
See Also
Configuring Q-in-Q Tunnelingon QFX Series, NFX Series, and EX4600 Switches with ELS Support
Creating a Private VLAN on a Single Switch withELS Support (CLI Procedure)
Configure Flexible Ethernet Services Encapsulation to Include Layer 2 Interface Support with Other Encapsulations
SUMMARYFlexible Ethernet services is a type of encapsulation that enables a physical interface to specify Ethernet encapsulations at the logical interface level. Perform the following steps to configure flexible Ethernet services to support a Layer 2 bridging interface while simultaneously supporting other encapsulation options on the same physical interface.
Note:
On the QFX10000 line of Switches running Junos OS releases earlier than Release 21.2R1, you cannot configure vlan-bridging and any other encapsulations on an interface that has flexible-ethernet-services enabled.
Configure a physical or aggregated Ethernet interface to simultaneously support a VLAN based circuit cross-connect (CCC) connection, Layer 3 IP routing, and Layer 2 bridging:
- Enable flexible Ethernet services encapsulation on the interface.
[edit interfaces interface-name]user@switch# set encapsulation flexible-ethernet-services
- Configure the interface to support 802.1Q VLAN single-tagged and dual-tagged frames.
[edit interfaces interface-name]user@switch# set vlan-tagging
- Define a logical interface to support Ethernet VLAN encapsulation for CCC:
[edit interfaces interface-name]user@switch# set unit unit-number encapsulation vlan-ccc
- Bind the L2 CCC logical interface from the preceding step to a VLAN ID. This step is needed for all logical interfaces because the physical interface is set for VLAN tagged traffic.
[edit interfaces interface-name]user@switch# set unit unit-number vlan-id vlan-id
- Configure a second logical interface as an L3 routed IP interface.
[edit interfaces interface-name]user@switch# set unit unit-number family inet address ip-address/mask
- Bind the L3 logical interface from the preceding step to a VLAN ID:
[edit interfaces interface-name]user@switch# set unit unit-number vlan-id vlan-id
- Configure a third logical interface to support VLAN based bridging by specifying
vlan-bridgeencapsulation on the logical unit.[edit interfaces interface-name]user@switch# set unit unit-number encapsulation vlan-bridge
- Bind the logical interface from the preceding step to a VLAN ID.
[edit interfaces interface-name]user@switch# set unit unit-number vlan-id vlan-id
- Define a bridge domain and add the L2 logical interface.
[edit]user@switch# set bridge-domains bridge-domain-name vlan-id vlan-id
[edit]user@switch# set bridge-domains bridge-domain-name interface interface-id
Verify your configuration using the show interfaces interface-name command in the configuration mode.
user@switch> show interfaces xe-0/0/0vlan-tagging;encapsulation flexible-ethernet-services;unit 1 { encapsulation vlan-ccc; vlan-id 103; }unit 2 { vlan-id 102; family inet { address 10.0.0.1/30; }unit 3 { encapsulation vlan-bridge; vlan-id 101; }}See Also
encapsulation (interfaces)
encapsulation (Logical Interface)
vlan-tagging
Configure Flexible Ethernet Services Encapsulation to Support Multiple Logical Interfaces on the Same Physical Interface Mapped to the Same Bridge Domain
SUMMARYFlexible Ethernet services is a type of encapsulation that enables a physical interface to specify Ethernet encapsulations at the logical interface level. Perform the following steps to configure multiple logical interfaces on the same physical interface mapped to the same bridge domain.
Note:
The QFX10002-60C switches do not support this feature.
Configure a physical or aggregated Ethernet interface to simultaneously support multiple logical interfaces using the same bridge domain. You cannot configure an ESI interface as one of the logical interfaces over a physical interface when both are part of the same VLAN. ESI interfaces have a limitation.
Note:
The combination of enterprise-style and service provider-style interfaces on the same physical interface is not supported when there are multiple service provider style logical interfaces attached to the same bridge domain.
- Configure the interface to support 802.1Q VLAN single-tagged and dual-tagged frames.
[edit interfaces interface-name]user@switch# set vlan-tagging
- Enable flexible Ethernet services encapsulation on the interface.
[edit interfaces interface-name]user@switch# set encapsulation flexible-ethernet-services
- Configure a logical interface to support VLAN based bridging by specifying
vlan-bridgeencapsulation on the logical unit.[edit interfaces interface-name]user@switch# set unit unit-number encapsulation vlan-bridge
- Bind the logical interface from the preceding step to a VLAN ID. This step is needed for all logical interfaces because the physical interface is set for VLAN tagged traffic.
[edit interfaces interface-name]user@switch# set unit unit-number vlan-id vlan-id
- Configure another logical interface to support VLAN based bridging by specifying
vlan-bridgeencapsulation on the logical unit.[edit interfaces interface-name]user@switch# set unit unit-number encapsulation vlan-bridge
- Bind the logical interface from the preceding step to a VLAN ID.
[edit interfaces interface-name]user@switch# set unit unit-number vlan-id vlan-id
- Configure a bridge domain by specifying the VLAN name and assigning a VLAN ID:
[edit]user@switch# set vlans vlan-name vlan-id vlan-id
- Bind the first logical interface to the bridge domain:
[edit]user@switch# set vlans vlan-name interfaces interface-name.unit
- Bind the second logical interface to the bridge domain.
[edit]user@switch# set vlans vlan-name interfaces interface-name.unit
Verify your configuration using the show interfaces interface-name and command in the configuration mode.show vlans
user@switch> show interfaces xe-0/0/2:2flexible-vlan-tagging;encapsulation flexible-ethernet-services;unit 1 { encapsulation vlan-bridge; vlan-id 1;}unit 2 { encapsulation vlan-bridge; vlan-id 2;}user@switch> show vlansv100 { vlan-id 100; interface xe-0/0/2:2.1; interface xe-0/0/2:2.2;}See Also
encapsulation (interfaces)
encapsulation (Logical Interface)
vlan-tagging
vlans
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.
Release
Description
16.1R3
Starting with Junos OS Release 16.1R6, you can also combine encapsulationson the same physical interface for family inet and family ethernet-switching.
