Configure Switch Ports as Trunk Ports
This procedure describes how to create a trunk port that can carry multiple VLANs using 802.1Q tagging. Trunk ports accept untagged and tagged traffic. Traffic on allowed VLANs pass through the trunk port unchanged.
When the trunk receives untagged traffic, it tags it to the native VLAN ID so that the ASA can forward the traffic to the correct switch ports, or can route it to another firewall interface. When the ASA sends native VLAN ID traffic out of the trunk port, it removes the VLAN tag. Be sure to set the same native VLAN on the trunk port on the other switch so that the untagged traffic will be tagged to the same VLAN.
Procedure
Step 1 | Select Edit () for your threat defense device. The Interfaces page is selected by default. and click |
Step 2 | Click Edit () for the interface you want to edit. |
Step 3 | Enable the interface by checking the Enabled check box. |
Step 4 | (Optional) Add a description in the Description field. The description can be up to 200 characters on a single line, without carriage returns. |
Step 5 | Set the Port Mode to Trunk. |
Step 6 | In the Native VLAN ID field, set the native VLAN for this switch port, between 1 and 4070. The default native VLAN ID is 1. Each port can only have one native VLAN, but every port can have either the same or a different native VLAN. |
Step 7 | In the Allowed VLAN IDs field, enter the VLANs for this trunk port between 1 and 4070. You can identify up to 20 IDs in one of the following ways:
If you include the native VLAN in this field, it is ignored; the trunk port always removes the VLAN tagging when sending native VLAN traffic out of the port. Moreover, it will not receive traffic that still has native VLAN tagging. |
Step 8 | (Optional) Check the Protected check box to set this switch port as protected, so you can prevent the switch port from communicating with other protected switch ports on the same VLAN. You might want to prevent switch ports from communicating with each other if: the devices on those switch ports are primarily accessed from other VLANs; you do not need to allow intra-VLAN access; and you want to isolate the devices from each other in case of infection or other security breach. For example, if you have a DMZ that hosts three web servers, you can isolate the web servers from each other if you enable Protected on each switch port. The inside and outside networks can both communicate with all three web servers, and vice versa, but the web servers cannot communicate with each other. |
Step 9 | (Optional) Set the duplex and speed by clicking Hardware Configuration. Check the Auto-negotiation check box (the default) to auto-detect the speed and duplex. If you uncheck it, you can set the speed and duplex manually:
|
Step 10 | Click OK. |
Step 11 | Click Save. You can now go to and deploy the policy to assigned devices. The changes are not active until you deploy them. |