--- title: "Configure the VM-Aware interface in the Manager" slug: "configure-the-vm-aware-interface-in-the-manager" tags: ["Product Usage", "IPS 10.1.10"] updated: 2026-09-06T12:31:24Z published: 2026-10-05T15:41:20Z canonical: "docs.trellix.com/configure-the-vm-aware-interface-in-the-manager" --- > ## 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. # Configure the VM-Aware interface in the Manager ## Before you begin 1. You have deployed the Sensor monitoring port in SPAN or hub mode, and this port is up and running. 2. This SPAN port receives the traffic mirrored to the uplink port on the VDS. For this you can connect the SPAN port directly to the physical NIC on the ESX associated with the uplink port on the VDS. Alternatively, you can connect to a SPAN port on a physical switch to which the traffic from the uplink port is mirrored. 3. Make sure this SPAN port of the Sensor does not have any subinterfaces defined. For the Manager to identify VM traffic, you must configure a SPAN port's type as *VM-Aware*. A VM-Aware port functions just like a dedicated SPAN port, but the traffic detected at this port is generated by VMs. For each VM-Aware interface, you configure the details of the vendor applications - VMware or Reflex. When the Sensor generates an alert, the Manager checks if the associated interface is of type VM-Aware. If yes, it integrates with the configured vendor applications to collect more information and to quarantine the attacking VM. The Manager supports the following with respect to VM traffic: - You can include source and destination VM host names when sending alert information to syslog servers. - If you want to configure the Manager to notify you—through email, pager, or script—for alerts based on alert severity, you can now also include the source and destination VM host names. - Data source for the next generation **User Defined** reports includes destination VM name and source VM name. - If you have an MDR pair in your deployment, then the VM-Aware configuration and alerts related to VM traffic on the primary Manager are automatically synchronized with the secondary Manager. ## Task 1. Click the **Devices** tab. 2. Select the domain from the **Domain** drop-down list. 3. On the left pane, click the **Devices** tab. 4. Select the device from the **Device** drop-down list. 5. Select **IPS Interfaces** → **** → **Properties**. 6. Select the **Interface Type** as **VM-Aware** and click **Edit**. > [!NOTE] > Note > > The **VM-Aware** option is listed only if the port is deployed in SPAN mode. **Properties** page is displayed. ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-B1F98AB9-B221-4E6B-AC69-8E03E724AD22-low(1).png?sv=2026-02-06&spr=https&st=2026-11-22T15%3A24%3A41Z&se=2026-11-22T16%3A24%3A41Z&sr=c&sp=r&sig=xJCCw6MKqM9evAjw4uJEmlCfOCPDFAPrNUFzl3lZHb4%3D) 7. Specify the details in the **Properties** page. | Option | Definition | | --- | --- | | **Interface Type** | The **Interface Type** is selected as **VM-Aware**. | | **Interface Name** | Optionally, modify the **Interface Name**. | | **Description** | Optionally, modify the default description. | | **Virtualization Management Server Type** | Select VMware or Reflex as the type for this interface. > [!NOTE] > Note > > You can specify only one **Virtualization Management Server Type** per VM-Aware interface. That is, a VM-Aware interface can either have VMware or Reflex as the vendor. To configure the other vendor on the same Sensor, configure a different SPAN port as VM-Aware interface. You can configure multiple SPAN ports on the same Sensor as VM-Aware interfaces. | | **Save** | Saves the configuration in the Manager. | Next, you need to configure the details of the vendor applications based on your choice for **Virtualization Management Server Type**.