About VLAN Subinterfaces
About VLAN Subinterfaces
About VLAN Subinterfaces
Note For multiple context mode, complete all tasks in this section in the system execution space. If you are not
already in the system execution space, in the Configuration > Device List pane, double-click System under
the active device IP address.
VLAN Subinterfaces
1
VLAN Subinterfaces
Guidelines and Limitations for VLAN Subinterfaces
ASASM No support.
Note For an interface to count against the VLAN limit, you must assign a VLAN to it.
Additional Guidelines
• Preventing untagged packets on the physical interface—If you use subinterfaces, you typically do not
also want the physical interface to pass traffic, because the physical interface passes untagged packets.
This property is also true for the active physical interface in a redundant interface pair and for EtherChannel
VLAN Subinterfaces
2
VLAN Subinterfaces
Default Settings for VLAN Subinterfaces
links. Because the physical, redundant, or EtherChannel interface must be enabled for the subinterface
to pass traffic, ensure that the physical, redundant, or EtherChannel interface does not pass traffic by not
configuring a name for the interface. If you want to let the physical, redundant, or EtherChannel interface
pass untagged packets, you can configure the name as usual.
• The ASA does not support the Dynamic Trunking Protocol (DTP), so you must configure the connected
switch port to trunk unconditionally.
• You might want to assign unique MAC addresses to subinterfaces defined on the ASA, because they use
the same burned-in MAC address of the parent interface. For example, your service provider might
perform access control based on the MAC address. Also, because IPv6 link-local addresses are generated
based on the MAC address, assigning unique MAC addresses to subinterfaces allows for unique IPv6
link-local addresses, which can avoid traffic disruption in certain instances on the ASA.
Procedure
VLAN Subinterfaces
3
VLAN Subinterfaces
Examples for VLAN Subinterfaces
• For multiple mode in the System execution space, choose the Configuration > Context Management
> Interfaces pane.
Step 3 From the Hardware Port drop-down list, choose the physical, redundant, or port-channel interface to which
you want to add the subinterface.
Step 4 If the interface is not already enabled, check the Enable Interface check box.
The interface is enabled by default.
Step 5 In the VLAN ID field, enter the VLAN ID between 1 and 4094.
Some VLAN IDs might be reserved on connected switches, so check the switch documentation for more
information. For multiple context mode, you can only set the VLAN in the system configuration.
Step 6 In the Subinterface ID field, enter the subinterface ID as an integer between 1 and 4294967293.
The number of subinterfaces allowed depends on your platform. You cannot change the ID after you set it.
Step 7 (Optional) In the Description field, enter a description for this interface.
The description can be up to 240 characters on a single line, without carriage returns. For multiple context
mode, the system description is independent of the context description. In the case of a failover or state link,
the description is fixed as “LAN Failover Interface,” “STATE Failover Interface,” or “LAN/STATE Failover
Interface,” for example. You cannot edit this description. The fixed description overwrites any description
you enter here if you make this interface a failover or state link.
Related Topics
Licensing for VLAN Subinterfaces, on page 1
VLAN Subinterfaces
4
VLAN Subinterfaces
History for VLAN Subinterfaces
security-level 100
ip address 192.168.6.6 255.255.255.0
no shutdown
Increased VLANs 7.2(2) VLAN limits were increased for the ASA 5510 (from 10 to 50 for the Base license,
and from 25 to 100 for the Security Plus license), the ASA 5520 (from 100 to 150),
the ASA 5550 (from 200 to 250).
Increased VLANs for the ASA 5580 8.1(2) The number of VLANs supported on the ASA 5580 are increased from 100 to 250.
VLAN Subinterfaces
5
VLAN Subinterfaces
History for VLAN Subinterfaces
VLAN Subinterfaces
6