For TE, traffic can be classified to a service-class which in turn maps to one of our four priority queues in two ways. If the session matches a configured session-type by transport protocol and destination port, that is the first method. There are default session-types included in the configuration even if you have not configured any. If the service the traffic matches has a service-policy which features a service-class, this will override the service-class of the session type. If the traffic does not match a configured session-type and the service's service-policy is not configured with a service-class, the traffic will receive best effort treatment.
If you are unsure if your traffic is being properly classified, you can create a custom report in the conductor to view aggregate-session/service-class/bandwidth and that should show you the amount of bandwidth going into each service-class.
But classification is not enough to ensure the system is doing what you want. You also will need to ensure enforcement is setup correctly. On your router, on the egress device-interface (likely your WAN in most scenarios), ensure that the traffic-engineering is enabled and that the transmit-cap is configured correctly to match the upstream bandwidth of your circuit. You also may want to configure a traffic-profile that allocates percentages of your available bandwidth into the four priority queues. In order for TE to provide functionality, the router needs to be able to make intelligent decisions about what to drop before the upstream network makes arbitrary discards without caring about what is high priority or not. In order to do this appropriately, we have to know at what point the upstream network will start to drop packets so we can kick in first and do it intelligently.
Lane
------------------------------
Mark Shields
------------------------------
Original Message:
Sent: 04-28-2022 16:38
From: Kylie Hetzel
Subject: Traffic Engineering - Default Behavior
I am trying to prioritize my simulated voice traffic (SIP/RTP) and have service policies with service classes assigned with high priority traffic classes. Now when I try to push TCP traffic, I see my high priority voice traffic is being affected. If I don't have a service policy assigned for TCP traffic should it default to best-effort? Or do I need a service class/policy assigned to this traffic so it doesn't step on my high priority voice?
Any help/advice is appreciated here!
Thank you
------------------------------
Kylie Hetzel
------------------------------