# Add VLAN interfaces to Master Engines

Master Engines can have two types of VLAN interfaces: VLAN interfaces for the Master Engine’s own traffic, and VLAN interfaces that are used by the Virtual Engines hosted on the Master Engine.

##

The maximum number of VLANs for a single physical interface is 4094. The VLANs must also be defined in the configuration of the external switch or router to which the interface is connected.

On Master Engines that host Virtual IPS engines or Virtual Layer 2 Engines, the Virtual Engines can inspect traffic from VLAN interfaces without configuring VLAN tagging.

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

## Steps

1. Select Engine.
2. Right-click a Security Engine, then select Edit <element type>.
3. Browse to Interfaces.
4. Right-click a physical interface, then select New > VLAN Interface.
5. Configure the settings, then click OK.
   The specified VLAN ID is added to the physical interface.
6. Click Save.

## Next steps

Add IP addresses to the physical interfaces or VLAN interfaces for Master Engine system communications.

## VLAN Interface Properties dialog box (Engine)

Use this dialog box to define the VLAN Interface properties for a Single Engine, Engine Cluster, Virtual Engine, or Master Engine in the Engine role.

Note: The available options can vary depending on the type of Security Engine, whether an interface is layer 2 or layer 3, and the type of layer 2 interface.

Option | Definition
--- | ---
General tab
VLAN ID | Enter the VLAN ID (1–4094). The VLAN IDs you add must be the same as the VLAN IDs that are used in the switch at the other end of the VLAN trunk. Each VLAN Interface is identified as Interface-ID.VLAN-ID, for example, 2.100 for Interface ID 2 and VLAN ID 100.

Option | Definition
--- | ---
Virtual Resource section (Master Engines only)
Virtual Resource | The Virtual Resource associated with the interface. Select the same Virtual Resource in the properties of the Virtual Engine to add the Virtual Engine to the Master Engine.
Virtual Engine Interface ID | Specifies the Interface ID of the Physical Interface in the Virtual Engine that is associated with this interface.
Interface Throughput Limit | Enter the throughput for the link on this interface as megabits per second. If the Virtual Resource element has a limit defined, the limit defined in that element is always used.
Virtual Resources table | (When the VLAN interface is under a shared physical interface) Select the Virtual Resources that you want to use for the associated Virtual Engines. Click Add to add an element to the table, or Remove to remove the selected element.
Virtual Resource | The selected Virtual Resource element.
Interface ID | Specifies the Interface ID of the Physical Interface in the Virtual Engine that is associated with this interface.
Throughput Limit | Enter the throughput for the link on this interface as megabits per second. If the Virtual Resource element has a limit defined, the limit defined in that element is always used.

Option | Definition
--- | ---
Interface Settings for Master Engine section (Master Engines only) The options in this section apply only to the Master Engines system communications.

Option | Definition
--- | ---
QoS Mode (Optional) | Select the QoS mode to apply to the link on this interface. You can select from one of the following options: No QoS: When selected, no QoS mode is enabled. QoS Statistics Only: It allows the collection of QoS Class-based counters without activating any other QoS feature. DSCP Handling and Throttling: When selected, no queues and no throttling of all traffic. Only the connections that are tagged with QoS Class are treated as per the action that is defined in the QoS policy. Full QoS: It throttles all traffic to the Interface Throughput Limit that is set in the interface properties Note: If Full QoS or DSCP Handling and Throttling is selected, a QoS policy must also be selected. If Full QoS is selected, the throughput must also be defined. If the interface is a Physical Interface, the same QoS mode is automatically applied to any VLANs created under it.
QoS Policy | (When QoS Mode is Full QoS or DSCP Handling and Throttling) The QoS policy for the link on this interface. If the interface is a Physical Interface, the same QoS policy is automatically selected for any VLANs created under it. Note: If a Virtual Resource has a throughput limit defined, the interfaces on the Virtual Engine that use a QoS policy all use the same policy. The policy used in the first interface is used for all the interfaces.
Interface Throughput Limit | (When QoS Mode is Full QoS) Enter the throughput for the link on this interface as megabits per second. If the interface is a Physical Interface, the same throughput is automatically applied to any VLANs created under it. The throughput is for uplink speed (outgoing traffic) and typically must correspond to the speed of an Internet link (such as an ADSL line), or the combined speeds of several such links when connected to a single interface. CAUTION: Make sure that you set the interface speed correctly. When the bandwidth is set, the Engine always scales the total amount of traffic on this interface to the bandwidth you defined. This scaling happens even if there are no bandwidth limits or guarantees defined for any traffic. CAUTION: The throughput for a Physical Interface for a Virtual Engine must not be higher than the throughput for the Master Engine interface that hosts the Virtual Engine. Contact the administrator of the Master Engine before changing this setting.

Option | Definition
--- | ---
Zone (Optional) | Select the network zone to which the interface belongs. Click Select to select an element, or click New to create an element.
MTU (Optional) | The maximum transmission unit (MTU) size on the connected link. Either enter a value between 400–65535 or select a common MTU value from the list. If the interface is a Physical Interface, the same MTU is automatically applied to any VLANs created under it. The default value (also the maximum standard MTU in Ethernet) is 1500. Do not set a value larger than the standard MTU, unless you know that all devices along the communication path support it. To set the MTU for a Virtual Engine, you must configure the MTU for the interface on the Master Engine that hosts the Virtual Engine, then refresh the policy on the Master Engine and the Virtual Engine.
Comment (Optional) | A comment for your own reference.

Option | Definition
--- | ---
DHCPv4 or DHCPv6 tab
DHCP Mode | Select the DHCP mode: Disabled — DHCP relay is disabled. DHCP Relay — Enables DHCP relay on the interface. DHCP Server (DHCPv4 only) — Activates the integrated DHCP server on the interface.

Option | Definition
--- | ---
DHCPv4 or DHCPv6 tab, DHCPv4 Relay or DHCPv6 Relay settings (When DHCP Mode is DHCPv4 Relay or DHCPv6 Relay)
Resources section. Add elements from this list to the list in the Content section. Click Add to add an element to the list, or Remove to remove the selected element. You can also drag and drop elements.
Filter | Allows you to filter the elements shown.
Up | Navigates up one level in the navigation hierarchy. Not available at the top level of the navigation hierarchy.
More actions | A menu that contains various options, such as for creating new elements or showing elements that have been moved to the Trash.
Max Packet Size | Set the maximum allowed packet size.
DHCP Relay | Select the CVI or IP address you want to use for DHCP relay.
Trusted Circuit | When selected, DHCP relay agents that terminate switched or permanent circuits and can identify the remote host end of the circuit are allowed to add the Remote-ID option to the DHCP messages before relaying them.

Option | Definition
--- | ---
DHCPv4 tab, DHCPv4 Server settings (When DHCP Mode is DHCPv4 Server)
DHCP Address range | Defines the DHCP address range that the Engine assigns to clients in one of the following ways: Select — Allows you to select an address range element. Address — Allows you to enter a single IP address or an IP address range. On Engine Clusters, the DHCP address range is automatically divided between the nodes. Note: The DHCP address range must be in the same network space defined for the Physical Interface. The DHCP address range must not contain the Engine's NDI or CVI addresses or broadcast IP addresses of networks behind the Engine.
Primary DNS Server | Enter the primary DNS server IP address that clients use to resolve domain names. If there is a listening IP address for DNS Relay on the same interface, clients use the DNS services provided by the engine by default. If you want clients to use a different external DNS server, enter the IP address of the external DNS server.
Secondary DNS Server | Enter the secondary DNS server IP address that clients use to resolve domain names.
Primary WINS Server | Enter the primary WINS server IP address that clients use to resolve NetBIOS computer names.
Secondary WINS Server | Enter the secondary WINS server IP address that clients use to resolve NetBIOS computer names.
Default Gateway | Enter the IP address through which traffic from clients is routed.
Default Lease Time | Enter the time after which IP addresses assigned to clients must be renewed.
Domain Name Search List (Optional) | Enter a comma-separated Domain Name Search List to configure DNS search suffixes.
Override DHCP Ranges per Node (Engine Clusters only) | Enter the DHCP address range for each node. CAUTION: Enter unique ranges for each node. Overlapping ranges can cause IP address duplication.

Option | Definition
--- | ---
Advanced tab (All optional settings)
Override Engine's Default Settings | When selected, the default settings of the Security Engine are overridden.
SYN Rate Limits | Default — The interface uses the SYN rate limits defined for the Security Engine on the Advanced Settings branch of the Engine Editor. None — Disables SYN rate limits on the interface. Automatic — This is the recommended mode if you want to override the general SYN rate limits defined on the Advanced Settings branch of the Engine Editor. The Engine calculates the number of allowed SYN packets per second and the burst size (the number of allowed SYNs before the Security Engine starts limiting the SYN rate) based on the Engine’s capacity and memory size. Custom — Enter the values for Allowed SYNs per Second and Burst Size.
Allowed SYNs per Second | Defines the number of allowed SYN packets per second.
Burst Size | The number of allowed SYNs before the Engine starts limiting the SYN rate. We recommend that you set the burst size to be at least one tenth of the Allowed SYNs per Second value. If the burst size is too small, SYN rate limits do not work. For example, if the value for Allowed SYNs per Second is 10000, set the value for Burst Size to at least 1000.
Enable Log Compression | By default, each generated Antispoofing and Discard log entry is logged separately and displayed as a separate entry in the Logs view. Log Compression settings allow you to define the maximum number of separately logged entries. When the defined limit is reached, a single antispoofing log entry or Discard log entry is logged. The single entry contains information about the total number of the generated Antispoofing log entries or Discard log entries. After this log entry, the logging returns to normal and all generated entries are once more logged and displayed separately. Log Compression is useful when the routing configuration generates a large volume of antispoofing logs or the number of Discard logs becomes high. For each event type, Antispoofing or Discard, you can define: Log Rate (Entries/s) — The maximum number of entries per second. The default value for antispoofing entries is 100 entries/s. By default, Discard log entries are not compressed. Burst Size (Entries) — The maximum number of matching entries in a single burst. The default value for antispoofing entries is 1000 entries. By default, Discard log entries are not compressed.
Set to Default | Returns all changes to the log compression settings to the default settings.
Send IPv6 Router Advertisements | Select and specify what configuration information is offered in the Router Advertisement messages to devices that connect to the same network as the engine.
Managed address configuration | When selected, the router advertisement messages that the Engine sends instruct the hosts to use the DHCPv6 protocol to acquire IP addresses and other configuration information.
Other configuration | When selected, the router advertisement messages that the Engine sends instruct the hosts to acquire the IPv6 prefix and the default route information from the router advertisement messages, and to use the DHCPv6 protocol to acquire other configuration information (such as DNS server addresses).

## VLAN Interface Properties dialog box (IPS engine)

Use this dialog box to define the VLAN Interface properties for a Single IPS engine, IPS Cluster, Virtual IPS engine, or Master Engine in the IPS role.

Note: The available options can vary depending on the type of IPS engine and the type of Physical Interface that the VLAN Interface belongs to.

Option | Definition
--- | ---
General tab
VLAN ID | Enter the VLAN ID (1–4094). The VLAN IDs you add must be the same as the VLAN IDs that are used in the switch at the other end of the VLAN trunk. Each VLAN Interface is identified as Interface-ID.VLAN-ID, for example, 2.100 for Interface ID 2 and VLAN ID 100.
Second VLAN ID | (When Type is Inline Interface) Enter the VLAN ID (1–4094) for the Second Interface in the Inline Interface pair. The VLAN IDs you add must be the same as the VLAN IDs that are used in the switch at the other end of the VLAN trunk. Each VLAN Interface is identified as Interface-ID.VLAN-ID, for example, 2.100 for Interface ID 2 and VLAN ID 100. Note: The VLAN identifier must be identical in both Inline Interfaces. For example, 3.101 and 4.101 would be a valid pair of VLAN Inline Interfaces.
Zone (Optional) | Select the network zone to which the interface belongs. Click Select to select an element, or click New to create an element.
MTU (Optional) | The maximum transmission unit (MTU) size on the connected link. Either enter a value between 400–65535 or select a common MTU value from the list. If the interface is a Physical Interface, the same MTU is automatically applied to any VLANs created under it. The default value (also the maximum standard MTU in Ethernet) is 1500. Do not set a value larger than the standard MTU, unless you know that all devices along the communication path support it. To set the MTU for a Virtual Engine, you must configure the MTU for the interface on the Master Engine that hosts the Virtual Engine, then refresh the policy on the Master Engine and the Virtual Engine.
Comment (Optional) | A comment for your own reference.
Reset Interface | (When Type is Capture Interface) Select the Reset Interface to specify the interface through which TCP connection resets are sent when Reset responses are used in your policy.
Logical Interface | Specifies the Logical Interface. You cannot use the same Logical Interface element for both Inline and Capture Interfaces on the same Virtual Engine.
Second Interface (Optional) | (When Type is Inline Interface) VLAN ID — Enter the VLAN ID (1-4094) for the Second Interface in the Inline Interface pair. The VLAN IDs you add must be the same as the VLAN IDs that are used in the switch at the other end of the VLAN trunk. Each VLAN Interface is identified as Interface-ID.VLAN-ID, for example, 2.100 for Interface ID 2 and VLAN ID 100. Note: The VLAN identifier must be identical in both Inline Interfaces. For example, 3.101 and 4.101 would be a valid pair of VLAN Inline Interfaces. Zone — Select the network zone to which the Second Interface belongs. To browse for a Zone element, select Select. To create a Zone element, select New.

Option | Definition
--- | ---
Virtual Resource section (Master Engines only)
Virtual Resource | The Virtual Resource associated with the interface. Select the same Virtual Resource in the properties of the Virtual Engine to add the Virtual Engine to the Master Engine.

Option | Definition
--- | ---
QoS Mode (Optional) | Select the QoS mode to apply to the link on this interface. You can select from one of the following options: No QoS: When selected, no QoS mode is enabled. QoS Statistics Only: It allows the collection of QoS Class-based counters without activating any other QoS feature. DSCP Handling and Throttling: When selected, no queues and no throttling of all traffic. Only the connections that are tagged with QoS Class are treated as per the action that is defined in the QoS policy. Full QoS: It throttles all traffic to the Interface Throughput Limit that is set in the interface properties Note: If Full QoS or DSCP Handling and Throttling is selected, a QoS policy must also be selected. If Full QoS is selected, the throughput must also be defined. If the interface is a Physical Interface, the same QoS mode is automatically applied to any VLANs created under it.
QoS Policy | (When QoS Mode is Full QoS or DSCP Handling and Throttling) The QoS policy for the link on this interface. If the interface is a Physical Interface, the same QoS policy is automatically selected for any VLANs created under it. Note: If a Virtual Resource has a throughput limit defined, the interfaces on the Virtual Engine that use a QoS policy all use the same policy. The policy used in the first interface is used for all the interfaces.
Interface Throughput Limit | (When QoS Mode is Full QoS) Enter the throughput for the link on this interface as megabits per second. If the interface is a Physical Interface, the same throughput is automatically applied to any VLANs created under it. The throughput is for uplink speed (outgoing traffic) and typically must correspond to the speed of an Internet link (such as an ADSL line), or the combined speeds of several such links when connected to a single interface. CAUTION: Make sure that you set the interface speed correctly. When the bandwidth is set, the Engine always scales the total amount of traffic on this interface to the bandwidth you defined. This scaling happens even if there are no bandwidth limits or guarantees defined for any traffic. CAUTION: The throughput for a Physical Interface for a Virtual Engine must not be higher than the throughput for the Master Engine interface that hosts the Virtual Engine. Contact the administrator of the Master Engine before changing this setting.

Option | Definition
--- | ---
Advanced tab (All optional settings)
Override Engine's Default Settings | When selected, the default settings of the Security Engine are overridden.
SYN Rate Limits | Default — The interface uses the SYN rate limits defined for the Security Engine on the Advanced Settings branch of the Engine Editor. None — Disables SYN rate limits on the interface. Automatic — This is the recommended mode if you want to override the general SYN rate limits defined on the Advanced Settings branch of the Engine Editor. The Engine calculates the number of allowed SYN packets per second and the burst size (the number of allowed SYNs before the Security Engine starts limiting the SYN rate) based on the Engine’s capacity and memory size. Custom — Enter the values for Allowed SYNs per Second and Burst Size.
Allowed SYNs per Second | Defines the number of allowed SYN packets per second.
Burst Size | The number of allowed SYNs before the Engine starts limiting the SYN rate. We recommend that you set the burst size to be at least one tenth of the Allowed SYNs per Second value. If the burst size is too small, SYN rate limits do not work. For example, if the value for Allowed SYNs per Second is 10000, set the value for Burst Size to at least 1000.
Enable Log Compression | By default, each generated Antispoofing and Discard log entry is logged separately and displayed as a separate entry in the Logs view. Log Compression settings allow you to define the maximum number of separately logged entries. When the defined limit is reached, a single antispoofing log entry or Discard log entry is logged. The single entry contains information about the total number of the generated Antispoofing log entries or Discard log entries. After this log entry, the logging returns to normal and all generated entries are once more logged and displayed separately. Log Compression is useful when the routing configuration generates a large volume of antispoofing logs or the number of Discard logs becomes high. For each event type, Antispoofing or Discard, you can define: Log Rate (Entries/s) — The maximum number of entries per second. The default value for antispoofing entries is 100 entries/s. By default, Discard log entries are not compressed. Burst Size (Entries) — The maximum number of matching entries in a single burst. The default value for antispoofing entries is 1000 entries. By default, Discard log entries are not compressed.
Set to Default | Returns all changes to the log compression settings to the default settings.

## VLAN Interface Properties dialog box (Layer 2 Engine)

Use this dialog box to define the VLAN Interface properties for a Single Layer 2 Engine, Layer 2 Engine Cluster, Virtual Layer 2 Engine, or Master Engine in the Layer 2 Engine role.

Note: The available options can vary depending on the type of Layer 2 Engine and the type of Physical Interface that the VLAN Interface belongs to.

Option | Definition
--- | ---
General tab
VLAN ID | Enter the VLAN ID (1–4094). The VLAN IDs you add must be the same as the VLAN IDs that are used in the switch at the other end of the VLAN trunk. Each VLAN Interface is identified as Interface-ID.VLAN-ID, for example, 2.100 for Interface ID 2 and VLAN ID 100.
Second VLAN ID | (When Type is Inline Interface) Enter the VLAN ID (1–4094) for the Second Interface in the Inline Interface pair. The VLAN IDs you add must be the same as the VLAN IDs that are used in the switch at the other end of the VLAN trunk. Each VLAN Interface is identified as Interface-ID.VLAN-ID, for example, 2.100 for Interface ID 2 and VLAN ID 100. Note: The VLAN identifier must be identical in both Inline Interfaces. For example, 3.101 and 4.101 would be a valid pair of VLAN Inline Interfaces.
Zone (Optional) | Select the network zone to which the interface belongs. Click Select to select an element, or click New to create an element.
MTU (Optional) | The maximum transmission unit (MTU) size on the connected link. Either enter a value between 400–65535 or select a common MTU value from the list. If the interface is a Physical Interface, the same MTU is automatically applied to any VLANs created under it. The default value (also the maximum standard MTU in Ethernet) is 1500. Do not set a value larger than the standard MTU, unless you know that all devices along the communication path support it. To set the MTU for a Virtual Engine, you must configure the MTU for the interface on the Master Engine that hosts the Virtual Engine, then refresh the policy on the Master Engine and the Virtual Engine.
Comment (Optional) | A comment for your own reference.
Reset Interface | (When Type is Capture Interface) Select the Reset Interface to specify the interface through which TCP connection resets are sent when Reset responses are used in your policy.
Logical Interface | Specifies the Logical Interface. You cannot use the same Logical Interface element for both Inline and Capture Interfaces on the same Virtual Engine.
Second Interface (Optional) | (When Type is Inline Interface) VLAN ID — Enter the VLAN ID (1-4094) for the Second Interface in the Inline Interface pair. The VLAN IDs you add must be the same as the VLAN IDs that are used in the switch at the other end of the VLAN trunk. Each VLAN Interface is identified as Interface-ID.VLAN-ID, for example, 2.100 for Interface ID 2 and VLAN ID 100. Note: The VLAN identifier must be identical in both Inline Interfaces. For example, 3.101 and 4.101 would be a valid pair of VLAN Inline Interfaces. Zone — Select the network zone to which the Second Interface belongs. To browse for a Zone element, select Select. To create a Zone element, select New.

Option | Definition
--- | ---
Virtual Resource section (Master Engines only)
Virtual Resource | The Virtual Resource associated with the interface. Select the same Virtual Resource in the properties of the Virtual Engine element to add the Virtual Engine to the Master Engine.

Option | Definition
--- | ---
QoS Mode (Optional) | Select the QoS mode to apply to the link on this interface. You can select from one of the following options: No QoS: When selected, no QoS mode is enabled. QoS Statistics Only: It allows the collection of QoS Class-based counters without activating any other QoS feature. DSCP Handling and Throttling: When selected, no queues and no throttling of all traffic. Only the connections that are tagged with QoS Class are treated as per the action that is defined in the QoS policy. Full QoS: It throttles all traffic to the Interface Throughput Limit that is set in the interface properties Note: If Full QoS or DSCP Handling and Throttling is selected, a QoS policy must also be selected. If Full QoS is selected, the throughput must also be defined. If the interface is a Physical Interface, the same QoS mode is automatically applied to any VLANs created under it.
QoS Policy | (When QoS Mode is Full QoS or DSCP Handling and Throttling) The QoS policy for the link on this interface. If the interface is a Physical Interface, the same QoS policy is automatically selected for any VLANs created under it. Note: If a Virtual Resource has a throughput limit defined, the interfaces on the Virtual Engine that use a QoS policy all use the same policy. The policy used in the first interface is used for all the interfaces.
Interface Throughput Limit | (When QoS Mode is Full QoS) Enter the throughput for the link on this interface as megabits per second. If the interface is a Physical Interface, the same throughput is automatically applied to any VLANs created under it. The throughput is for uplink speed (outgoing traffic) and typically must correspond to the speed of an Internet link (such as an ADSL line), or the combined speeds of several such links when connected to a single interface. CAUTION: Make sure that you set the interface speed correctly. When the bandwidth is set, the Engine always scales the total amount of traffic on this interface to the bandwidth you defined. This scaling happens even if there are no bandwidth limits or guarantees defined for any traffic. CAUTION: The throughput for a Physical Interface for a Virtual Engine must not be higher than the throughput for the Master Engine interface that hosts the Virtual Engine. Contact the administrator of the Master Engine before changing this setting.

Option | Definition
--- | ---
Advanced tab (All optional settings)
Override Engine's Default Settings | When selected, the default settings of the Security Engine are overridden.
SYN Rate Limits | Default — The interface uses the SYN rate limits defined for the Security Engine on the Advanced Settings branch of the Engine Editor. None — Disables SYN rate limits on the interface. Automatic — This is the recommended mode if you want to override the general SYN rate limits defined on the Advanced Settings branch of the Engine Editor. The Engine calculates the number of allowed SYN packets per second and the burst size (the number of allowed SYNs before the Security Engine starts limiting the SYN rate) based on the Engine’s capacity and memory size. Custom — Enter the values for Allowed SYNs per Second and Burst Size.
Allowed SYNs per Second | Defines the number of allowed SYN packets per second.
Burst Size | The number of allowed SYNs before the Engine starts limiting the SYN rate. We recommend that you set the burst size to be at least one tenth of the Allowed SYNs per Second value. If the burst size is too small, SYN rate limits do not work. For example, if the value for Allowed SYNs per Second is 10000, set the value for Burst Size to at least 1000.
Enable Log Compression | By default, each generated Antispoofing and Discard log entry is logged separately and displayed as a separate entry in the Logs view. Log Compression settings allow you to define the maximum number of separately logged entries. When the defined limit is reached, a single antispoofing log entry or Discard log entry is logged. The single entry contains information about the total number of the generated Antispoofing log entries or Discard log entries. After this log entry, the logging returns to normal and all generated entries are once more logged and displayed separately. Log Compression is useful when the routing configuration generates a large volume of antispoofing logs or the number of Discard logs becomes high. For each event type, Antispoofing or Discard, you can define: Log Rate (Entries/s) — The maximum number of entries per second. The default value for antispoofing entries is 100 entries/s. By default, Discard log entries are not compressed. Burst Size (Entries) — The maximum number of matching entries in a single burst. The default value for antispoofing entries is 1000 entries. By default, Discard log entries are not compressed.
Set to Default | Returns all changes to the log compression settings to the default settings.