There are two physical interfaces in an inline Layer 2 Engine interface. The traffic is forwarded from one interface to the other. 
 
	  
			The traffic that the Engine Cluster allows goes through the inline Layer 2 Engine interface as if it was going through a network cable. The Engine Cluster drops the traffic you want to
				stop. If the Engine Cluster is unable to process traffic, all traffic that goes through the inline Layer 2 Engine interface is blocked.
 
		Inline interfaces are associated with a Logical interface element. The Logical interface is used in the Layer 2 Interface Engine Policies and the traffic inspection process to represent one or
				more inline Layer 2 Engine interfaces. 
 
		
 For more details about the product and how to configure features, click Help or
            press F1.
 
	 
 
	 Steps
- 
				Right-click the Engine Cluster and select Edit <element type>. 
				
The Engine Editor opens. 
			 
-  
		  In the navigation pane on the left, browse to 
			 Interfaces. 
		   
		
 
- 
				Right-click the empty space and select . 
			
 
-  
		  From the 
			 Interface ID drop-down list, select an ID number. 
		   
		
 
- 
				From the Type drop-down list, select Inline Layer 2 Engine Interface. 
			
 
-  
		  (Optional) From the 
			 Second Interface ID drop-down list, change the automatically selected interface ID. 
		   
		
 
- 
				If your configuration requires you to change the logical interface from Default_Eth, select the logical interface in one of the following ways: 
				
					- Select an existing Logical Interface element from the list. 
 
					- Click Select and browse to another Logical Interface element. 
 
					- Click New to create a Logical Interface element, then click OK. 
 
				
			 
- 
				If you want the Engine Cluster to inspect traffic from VLANs that are not included in the Engine Cluster's interface configuration, leave Inspect Unspecified
						VLANs selected. 
			
 
- 
				If you want the Engine Cluster to inspect double-tagged VLAN traffic, leave Inspect QinQ selected.
			
 
- 
				Click OK. 
			
 
- 
				Click 
                            Save. 
				Do not close the Engine Editor. 
			 
		Next steps
Continue the configuration in one of the following ways: 
				- Add VLAN interfaces to the inline Layer 2 Engine interface.
 
				- Select system communication roles for interfaces.
 
				- Bind engine licenses to Engine Cluster elements.