--- title: "Separating management traffic and data traffic" slug: "separating-management-traffic-and-data-traffic" tags: ["Product Usage", "CMS 11.x", "EX 11.x", "FX 11.x", "AX 11.x", "NX 11.x", "IVX 11.x", "Network Security"] updated: 2026-08-24T20:40:19Z published: 2026-08-24T20:40:19Z canonical: "docs.trellix.com/separating-management-traffic-and-data-traffic" stale: true --- > ## 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. # Separating management traffic and data traffic While configuring IVX with sensors such as NX, EX to keep management and data traffic separated, Trellix recommends that you configure one interface (for example, ether1) for management and a different interface (for example, ether2) as the submission interface. TrellixIntelligent Virtual Execution - Server appliances have one Ethernet management interface (labeled **ether1**) and three submission and cluster communication ports (labeled **ether2**, **ether3**), and **ether4**). By default, the ether1 management interface carries both management traffic and data traffic. For API submissions and integrations with Trellix products such as TIE, SWG, and IPS, make sure to use the same interface for both management and submission. Using different interfaces for these will result in submission failure. For deployment details, see the *Trellix* *Network Security Deployment Guide for MVX Smart Grid*. For network configuration settings, see [Configuration wizard steps](/network-and-platform/docs/configuration-wizard-steps-1) .