--- title: "Scenario 4: High-level steps for Virtual Sensor deployment" slug: "scenario-4-high-level-steps-for-virtual-sensor-deployment" tags: ["Product Usage", "vIPS 10.1.10"] updated: 2026-09-11T20:35:28Z published: 2026-09-11T20:35:28Z canonical: "docs.trellix.com/scenario-4-high-level-steps-for-virtual-sensor-deployment" --- > ## 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. # Scenario 4: High-level steps for Virtual Sensor deployment This section assumes the following for deploying the Virtual Sensor for scenario 4. - The ESX server meets the requirements as discussed in [Requirements for deploying the Virtual Sensor](/network-and-platform/docs/requirements-for-deploying-virtual-sensors). - You have the privileges on the ESX server to add and modify vSwitches and port groups. - You have installed the Virtual Sensor and established trust with the Manager successfully. As an example in this scenario, the management port is connected to vSwitch2. - As an example, this section uses the IPS-VM600 Virtual Sensor to explain the deployment. - This scenario involves only a Sensor monitoring port pair deployed in inline fail-closed mode. - This section uses only the vSphere Client for configurations on the ESX. ## Task 1. Connect the trunk port of Physical switch 1 and Physical switch 2 to two different physical NICs on the ESX. 2. Create two standard vSwitches for connecting Sensor monitoring ports 1 and 2. Refer to the section [Create a standard vSwitch for a monitoring port](/network-and-platform/docs/create-a-standard-vswitch-for-a-monitoring-port). Both these switches need physical adapters. For this scenario, vSwitch0 must be assigned a physical adapter that is connected to Physical switch 1. Similarly, vSwitch1 must be assigned a physical adapter that is connected to Physical switch 2. 3. Create a switch port group in vSwitch0, which corresponds to the trunk port on Physical switch 1. 1. Log on to the ESX as the root user in VMware vSphere Web Client. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-ED003931-0EA0-43A9-889D-8C1D10FE78FE-low.png?sv=2026-02-06&spr=https&st=2026-11-20T06%3A20%3A09Z&se=2026-11-20T07%3A20%3A09Z&sr=c&sp=r&sig=MiNikNwdHk%2B6l8Ii%2FhQIKRNv7Xg%2FSKA06mCKALLe5kQ%3D) 2. On the vSphere **Home** tab, select **Hosts and Clusters.** ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-37E5F81F-CB03-4D67-864C-875E4C707864-low.png?sv=2026-02-06&spr=https&st=2026-11-20T06%3A20%3A09Z&se=2026-11-20T07%3A20%3A09Z&sr=c&sp=r&sig=MiNikNwdHk%2B6l8Ii%2FhQIKRNv7Xg%2FSKA06mCKALLe5kQ%3D) 3. Select the required ESX server and select **Manage** → **Networking** → **Virtual switches** → **vSwitch0.** ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-EFF4167D-2437-4338-AD0F-88BB19DB084F-low.png?sv=2026-02-06&spr=https&st=2026-11-20T06%3A20%3A09Z&se=2026-11-20T07%3A20%3A09Z&sr=c&sp=r&sig=MiNikNwdHk%2B6l8Ii%2FhQIKRNv7Xg%2FSKA06mCKALLe5kQ%3D) 4. Click on **Add host networking** icon for vSwitch0. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-B9BC241D-6A6C-4474-9D07-49733A9CA879-low.png?sv=2026-02-06&spr=https&st=2026-11-20T06%3A20%3A09Z&se=2026-11-20T07%3A20%3A09Z&sr=c&sp=r&sig=MiNikNwdHk%2B6l8Ii%2FhQIKRNv7Xg%2FSKA06mCKALLe5kQ%3D) 5. For **Select target device**, select **Select an existing standard switch** and make sure vSwitch0 is selected. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-9B1CCC58-B150-49E1-9A03-76946B3BF73E-low.png?sv=2026-02-06&spr=https&st=2026-11-20T06%3A20%3A09Z&se=2026-11-20T07%3A20%3A09Z&sr=c&sp=r&sig=MiNikNwdHk%2B6l8Ii%2FhQIKRNv7Xg%2FSKA06mCKALLe5kQ%3D) 6. In the **Network Label** field, enter a name. For example, enter *Physical Client Port*. 7. In the **VLAN ID (Optional)** field, select **All (4095)** because this switch port group corresponds to the trunk port of a physical switch. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-353CE53E-47B8-47A6-B6AB-98FC0D95C321-low.png?sv=2026-02-06&spr=https&st=2026-11-20T06%3A20%3A09Z&se=2026-11-20T07%3A20%3A09Z&sr=c&sp=r&sig=MiNikNwdHk%2B6l8Ii%2FhQIKRNv7Xg%2FSKA06mCKALLe5kQ%3D) 8. Click **Next** and then **Finish**. 9. Under **Standard switch: vSwitch0 (VM Network)**, click on the switch port group that you created. In this example, it is *Physical Client Port*. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-0F410B03-C1B4-42D8-AC1F-68C19E8A3B5C-low.png?sv=2026-02-06&spr=https&st=2026-11-20T06%3A20%3A09Z&se=2026-11-20T07%3A20%3A09Z&sr=c&sp=r&sig=MiNikNwdHk%2B6l8Ii%2FhQIKRNv7Xg%2FSKA06mCKALLe5kQ%3D) 10. With the switch port group selected, click on the **Edit Settings** icon for the switch port group. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-592A1CF4-3E81-4109-B102-30DBCC89D0CD-low.png?sv=2026-02-06&spr=https&st=2026-11-20T06%3A20%3A09Z&se=2026-11-20T07%3A20%3A09Z&sr=c&sp=r&sig=MiNikNwdHk%2B6l8Ii%2FhQIKRNv7Xg%2FSKA06mCKALLe5kQ%3D) 11. In the **Edit Settings** dialog, select the **Security** tab and make sure the fields are set with the following values and click **OK.** - **Promiscuous mode —** Accept. This is set to accept because traffic related to all the hosts connected to Physical switch 1 is involved. - **MAC Address Changes —** Reject - **Forged Transmits —** Accept ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-A527EE98-A07D-46F1-81CE-0401DB527D0F-low.png?sv=2026-02-06&spr=https&st=2026-11-20T06%3A20%3A09Z&se=2026-11-20T07%3A20%3A09Z&sr=c&sp=r&sig=MiNikNwdHk%2B6l8Ii%2FhQIKRNv7Xg%2FSKA06mCKALLe5kQ%3D) 4. Use the previous step to create a similar switch port group in vSwitch1. This corresponds to the trunk port on Physical switch 2. 5. Assign the switch port group that you created in step 3 to monitoring port 1. See the section [Specify the switch port groups for monitoring ports](/network-and-platform/docs/specify-the-switch-port-groups-for-monitoring-ports). 6. Assign the switch port group that you created in step 4 to monitoring port 2. See the section [Specify the switch port groups for monitoring ports](/network-and-platform/docs/specify-the-switch-port-groups-for-monitoring-ports). Make sure the monitoring port 1 is connected to the corresponding port group (VIPS600-PG-Port1) on vSwitch0 and the monitoring port 2 is connected to the corresponding port group (VIPS600-PG-Port2) on vSwitch1. Both these port groups must have their VLAN ID as All (4095). This is required since the monitoring ports are connected to trunk ports of the physical switches. 7. Verify if you have deployed the Virtual Sensor correctly and whether it is inspecting traffic. Refer to the section [Verify the deployment](/network-and-platform/docs/verify-the-deployment).