Using codepoints to assign per-hop behaviors

Quality of service (QoS) uses the suggested codepoints to assign per-hop behaviors to traffic.

In the Class of service wizard, you need to assign a per-hop behavior to your policy. You must determine which codepoints to use based on your individual network needs. Only you can decide what codepoint schemes make sense for your environment. You need to consider what applications are most important to you and what policies might be assigned higher priority. The most important thing is to be consistent with your markings, so that you get the results you expect. For example, policies that hold similar importance might use similar codepoints so that you get consistent results for those policies. If you are unsure which codepoint to assign, use trial and error. You can create test policies, monitor these policies, and make adjustments accordingly.

The tables in the following sections display the suggested codepoints that are based on industry standards. Most Internet service providers (ISPs) support the industry-standard codepoints, and you can verify whether your ISP supports these codepoints. Across domains, every ISP must agree to support QoS requests. Your service agreements must be able to give your policies what they request. Verify that you are receiving the amount of service you need. If not, you might waste your resources. QoS policies allow you to negotiate service levels with your ISP, which might decrease network service costs. You can also create your own codepoints; however, it is not suggested for external use. Your own codepoints might be best used in a testing environment.