Consider a network scenario where the internal network of a University is connected to the internet, and Trellix IPS and the router are deployed as shown in the below diagram.
.png "GUID-AF120A80-7F89-4657-93E4-83A3EF74847F-low.png")
Suppose you want to prioritize the HTTP and P2P traffic coming from the University network to the internet. To prioritize the traffic, you can configure the Sensor for DiffServ or VLAN tagging. The role of the Sensor is just to tag the packets and pass it on to an external network device (here router) for DiffServ or VLAN classification.
Suppose you want to give high priority to the HTTP traffic coming from the University network to the internet. You can configure the Sensor port G0/2 with a DiffServ rule, in which the DiffServ field is set to a value, say 60, for HTTP traffic. When the HTTP traffic from the University network reaches Sensor port G0/2, the Sensor tags the packet headers with the DiffServ field value specified in the configuration (60, in this example). The tagged packets are sent to the router, which is configured to do DiffServ categorization. Now the traffic is prioritized according to the DiffServ priority defined in the router. Note that the Sensor only tags the incoming traffic and passes it on to the external network device (in this case, it is the router) which further performs the DiffServ classification.
Similarly, to provide low priority to the P2P traffic coming from the University network to the internet, you can configure port G0/2 of the Sensor with a DiffServ rule, in which the DiffServ field is set to a value, say 5. When the P2P traffic from the University network reaches Sensor port G0/2, the Sensor tags the packet headers with the DiffServ field value specified in the configuration (5, in this example). The tagged packets then reach the router which performs DiffServ classification and prioritization, based on the rules configured in the router.