--- title: "Configuring 1 Gbps (SFP) Monitoring Ports" slug: "configuring-1-gbps-sfp-monitoring-ports" tags: ["Product Usage", "IPS 10.1.10"] updated: 2026-10-05T15:40:31Z published: 2026-10-05T15:40:31Z canonical: "docs.trellix.com/configuring-1-gbps-sfp-monitoring-ports" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring 1 Gbps (SFP) Monitoring Ports You can view or configure settings for the 1 Gbps monitoring ports. ## Task 1. Navigate to **Devices** → **** → **Devices** → **** → **Setup** → **Physical Ports**. 2. Double-click on the row of the monitoring port that displays the Connector Type as **SFP**. The **Monitoring Port Details** window is displayed. View Monitoring Port window ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-844A4324-7EBF-4C7D-9D85-A02B1AB2B235-low.jpg?sv=2026-02-06&spr=https&st=2026-11-22T15%3A14%3A55Z&se=2026-11-22T16%3A14%3A55Z&sr=c&sp=r&sig=uxJOKTN58cSlE2f%2FeQ9on3260KluGlPQoI%2F5xwxu7xs%3D) 3. Select the **Auto Negotiate** checkbox if the speed of the port has to match with the rest of the network. 4. Select the **Speed** of the port. Port speed details the speed of traffic being monitored. You can set the port speed by selecting from the following values on the drop-down list: The LED link will turn green if the speed is set to 10 Mbps or 100 Mbps. - **1 Gbps (full)** - **100 Mbps (full)** - **100 Mbps (half)** - **10 Mbps (full)** - **10 Mbps (half)** 5. Specify whether a Trellix Certified SFP type should be used. 6. Select the **State** as either **Enabled** (on) or **Disabled** (off). The **Link** displays **Up** (on) or **Down** (off) accordingly. > [!NOTE] > Note > > If your **Link** displays as **Down** and your **State** is **Enabled**, there may be a problem. Check the system faults on the **Faults** tab in **Logs** page for more information. 7. Select an **Mode** from the following: > [!NOTE] > Caution > > Your device cabling must match the selected operating mode for correct system functionality. Improper deployment may result in system faults, including missed attacks and system failure. If a port is functioning as part of a *Port Pair*, the *Peer Port* is listed. For example, if port 1A is configured for Tap mode, port 1B is listed as the Peer Port. All ports are wire-matched internally with a single peer, for example 1A-1B make up a port pair. However, 1A-2B cannot be a port pair. - **Inline Fail Open - Active** - **Inline Fail Open - Passive** - **Inline Fail Closed** > [!NOTE] > Note > > Inline fail-open and Inline fail-closed are determined by how the port cables are connected. Fail-open operation for GE ports requires use of the optional Bypass Switch provided in the Gigabit Optical Fail-Open Bypass Kit (sold separately). You should *not* select the **Inline Fail Open** option if the optional external Bypass Switch is not present. - **SPAN or Hub** - **Tap** For FE ports configured in Tap mode, select **External** if using an external tap, or **Internal** if using the internal tap feature. GE ports can only be configured for External Tap mode. > [!NOTE] > Caution > > If FE ports fail when configured in Internal Tap Mode, traffic will continue to pass. However, your device will experience some latency that may block traffic upto a minute before the passthru is established. 8. Select **Placement** of your network where the current port is connected: **Inside Network** or **Outside Network**. This step applies to **Tap** or **Inline** modes only. 9. Wherever applicable, select a **Response Port**. The following choices are available: > [!NOTE] > Tip > > You can assign a response port to more than one device monitoring port. However, knowing where your response ports are connected in the network will make for the best response system. - **This Port**: Respond out of the detection port to the segment. This is selected by default for Inline and SPAN operating modes. - **R1**: Sends responses through a R1 port - **R2**: Sends responses through a R2 port 10. Click **Save** to save changes.