--- title: "Configuring inline operational modes using the CLI" slug: "configuring-inline-operational-modes-using-the-cli" tags: ["Product Usage", "EX 11.x", "FX 11.x", "AX 11.x", "NX 11.x", "Network Security"] updated: 2026-09-12T20:42:26Z published: 2026-09-12T20:42:26Z canonical: "docs.trellix.com/configuring-inline-operational-modes-using-the-cli" --- > ## 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 inline operational modes using the CLI Use the CLI commands in this procedure to configure operational modes for an inline policy on an interface. > [!NOTE] > Note > > You must use the **policymgr interface re-configure** command for the changes to take effect. **To configure operational modes for an inline policy on the Network Security appliance:** 1. Enable the CLI configuration mode. ``` hostname > enable ``` ``` hostname # configure terminal ``` 2. Specify the relevant operational mode for each port pair. - To operate without inline functionality in TAP mode: ``` hostname (config) # policymgr interface op-mode tap ``` where `<port-pair-name>` specifies the designation (A or B) that is configured on the appliance interface. > [!NOTE] > Note > > TAP mode is the default for out-of-band monitoring. - To allow traffic to pass through the appliance or sensor: ``` hostname (config) # policymgr interface op-mode bypass ``` where `<port-pair-name>` specifies the designation (A or B) that is configured on the appliance interface. - To monitor all packets without any blocking and generate alerts about potential infections: ``` hostname (config) # policymgr interface op-mode monitor ``` where `<port-pair-name>` specifies the designation (A or B) that is configured on the appliance interface. - Specify inline blocking attacks. - (Recommended) To allow all packets to pass through the appliance or sensor in case of a failure of software, hardware, or power: ``` hostname (config) # policymgr interface op-mode block fail-safe open ``` where `<port-pair-name>` specifies the designation (A or B) that is configured on the appliance interface. - To block all traffic in case of a failure of hardware or power: ``` hostname (config) # policymgr interface op-mode block fail-safe close ``` where `<port-pair-name>` specifies the designation (A or B) that is configured on the appliance interface. | ![caution.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-b3560060-f56d-1a8b-b955-dcd2a5f9b6f4.png?sv=2026-02-06&spr=https&st=2026-11-20T02%3A56%3A51Z&se=2026-11-20T03%3A56%3A51Z&sr=c&sp=r&sig=1Dh0MKrHQqhFOpCz5kqk26vP0HE9pusW9bpst3w6M40%3D) | If you select the fail-safe close inline blocking type, you must use active end-to-end monitoring of the device to enable the re-routing of traffic around the device in the event of a hardware or power failure. | | --- | --- | 3. Reapply the configuration to the specified interface. ``` hostname (config) # policymgr interface re-configure ``` where `<port-pair-name>` specifies the designation (A or B) that is configured on the appliance interface. 4. Verify the settings of the operational modes. ``` hostname (config) # show policymgr interfaces Policy enabled: yes Interface A Active      : yes op mode     : tap (tapping) fail-safe   : close policy      : mixed tolerance   : 1 mirror-port : Ports       : pether3  pether4 QinQ        : no QinQ-evet   : 0x88a8 ``` 5. Save your changes. ``` hostname (config) # write memory ``` ``` Saving configuration file ... Done! ```