# Define interfaces for converted Master Engine elements

All Master Engine interfaces must either have Interface Options defined or be associated with a Virtual Resource.

##

For more details about the product and how to configure features, click Help or press F1.

## Steps

1. If you want to use a Physical Interface to host a Virtual Engine, right-click a Physical Interface and select Edit Physical Interface.
   CAUTION:
   The Control Interface is used for Master Engine communications. Do not add a Virtual Resource to the Physical Interface that is used as the Control Interface.
2. Select the Virtual Resource to associate with the interface.
3. (Optional) Select Allow VLAN Definition in Virtual Engine to allow VLAN Interfaces to be added to the automatically created Physical Interfaces in the Virtual Engine that is associated with this interface.
4. Select the Virtual Engine Interface ID.
   This is the Physical Interface ID of the Virtual Engine that is associated with this interface.
5. Click OK to close the Physical Interface Properties dialog box.
6. (Optional) Click Options to select which IP addresses are used in particular roles in system communications.
7. (Optional) Add ARP Entries.
8. (Optional) Click Virtual Resources if you want to edit the name of the Virtual Resources.
9. Click Next and continue the configuration in one of the following ways:
   - If Tunnel Interfaces are defined for the Single Engine or Engine Cluster on which the configuration is based, the Distribute Tunnel Interfaces to Virtual Engines page opens. Move the Tunnel Interfaces into the interface configuration for the Virtual Engines.
   - If the Single Engine or Engine Cluster on which the configuration is based is associated with a VPN Gateway element, the Review Distribution of Internal Gateways to Virtual Engines page opens. Move the VPN Gateway elements into the configuration for the Virtual Engines.
   - Otherwise, the Define Routing for the Master Engine page opens. Define routing for the converted Master Engines.