Enable the Physical Interface and Configure Ethernet Settings
This section describes how to:
-
Enable the physical interface. By default, physical interfaces are disabled (with the exception of the Management interface).
-
Set a specific speed and duplex. By default, speed and duplex are set to Auto.
This procedure only covers a small subset of Interface settings. Refrain from setting other parameters at this point. For example, you cannot name an interface that you want to use as part of an EtherChannel interface.
Note | For the Firepower 4100/9300, you configure basic interface settings in FXOS. See Configure a Physical Interface for more information. |
Note | For Firepower 1010 and Secure Firewall 1210/1220 switch ports, see Configure Firepower 1010 and Secure Firewall 1210/1220 Switch Ports. |
Before you begin
If you changed the physical interfaces on the device after you added it to the management center, you need to refresh the interface listing by clicking Sync Interfaces from device on the top left of Interfaces. For the Secure Firewall 3100/4200, which supports hot swapping, see Manage the Network Module for the Secure Firewall 3100/4200 before you change interfaces on a device.
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 | (Optional) Set the duplex and speed by clicking .
| ||||||||||||||||||||||||
Step 6 | (Optional) (Firepower 1100/Secure Firewall 1200/3100/4200) Enable Link Layer Discovery Protocol (LLDP) by clicking .
| ||||||||||||||||||||||||
Step 7 | (Optional) (Secure Firewall 3100/4200) Enable pause (XOFF) frames for flow control by clicking , and checking Flow Control Send. Flow control enables connected Ethernet ports to control traffic rates during congestion by allowing congested nodes to pause link operation at the other end. If the threat defense port experiences congestion (exhaustion of queuing resources on the internal switch) and cannot receive any more traffic, it notifies the other port by sending a pause frame to stop sending until the condition clears. Upon receipt of a pause frame, the sending device stops sending any data packets, which prevents any loss of data packets during the congestion period.
The internal switch has a global pool of 8000 buffers of 250 bytes each, and the switch allocates buffers dynamically to each port. A pause frame is sent out every interface with flowcontrol enabled when the buffer usage exceeds the global high-water mark (2 MB (8000 buffers)); and a pause frame is sent out of a particular interface when its buffer exceeds the port high-water mark (.3125 MB (1250 buffers)). After a pause is sent, an XON frame can be sent when the buffer usage is reduced below the low-water mark (1.25 MB globally (5000 buffers); .25 MB per port (1000 buffers)). The link partner can resume traffic after receiving an XON frame. Only flow control frames defined in 802.3x are supported. Priority-based flow control is not supported. | ||||||||||||||||||||||||
Step 8 | In the Mode drop-down list, choose one of the following:.
| ||||||||||||||||||||||||
Step 9 | In the Priority field, enter a number ranging from 0–65535. This value is used in the policy based routing configuration. The priority is used to determine how you want to distribute the traffic across multiple egress interfaces. | ||||||||||||||||||||||||
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. | ||||||||||||||||||||||||
Step 12 | Continue configuring interfaces. |