--- title: "Interface groups (port clusters)" slug: "interface-groups-port-clusters-2" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:31:15Z published: 2026-11-19T12:31:15Z canonical: "docs.trellix.com/interface-groups-port-clusters-2" --- > ## 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. # Interface groups (port clusters) An interface group, also known as *port clustering* in networking parlance, combines the traffic processed on separate Sensor interfaces—or, in the case of a HA pair, on separate Sensors—into a single logical interface for state and intrusion analysis. Asymmetric routing is a good example of where an interface group is recommended. In asymmetric routing, a TCP connection does not always send and receive along the same network path. Therefore, a single-interface Sensor monitoring this transmission may only see the traffic received, not the traffic sent in response; thus not seeing all data from a transmission. Sensors' multiple interfaces make the monitoring of asymmetric traffic possible. For example, consider an NS9500's G1 interface module that has 4 ports. The ports are wired in pairs by default. Peer ports G1/1 and G1/2 can monitor one direction of an asymmetric transmission, while peer ports G1/3 and G1/4 can monitor the other direction. By making an interface group of G1/1-G1/2 and G1/3-G1/4, the Sensor is able to see all the traffic for all sessions in the asymmetrically routed network and still is able to maintain state and accurately detect all attacks. **Interface groups in an asymmetric network**![Interface groups in an asymmetric network](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-8bda4fda-fb96-1453-9633-ef914c5c24c7(7).png?sv=2026-02-06&spr=https&st=2026-11-20T12%3A44%3A37Z&se=2026-11-20T13%3A44%3A37Z&sr=c&sp=r&sig=%2FnGa1HNMV%2BgwxeW%2BW8JemFj2GHD2Wx8%2BNa%2Bt4aQ0Eeg%3D)