# QoS Pre-Classify on Cisco IOS

**URL:** https://forum.networklessons.com/t/qos-pre-classify-on-cisco-ios/1159
**Category:** Lessons Discussion
**Created:** [December 27, 2016, 4:49pm UTC](https://forum.networklessons.com/t/qos-pre-classify-on-cisco-ios/1159 "2016-12-27T16:49:28Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![andrew](https://cdn-forum.networklessons.com/user_avatar/forum.networklessons.com/andrew/32/645_2.png) [@andrew](https://forum.networklessons.com/u/andrew)
#### Post date: [November 25, 2015, 2:32am UTC](https://forum.networklessons.com/t/qos-pre-classify-on-cisco-ios/1159/4 "2015-11-25T02:32:33Z")

</div>

Hello Rene,

I was very happy to find you had a lab on this subject. I went through this myself and everything worked as described, except one area. When I moved the service policy off the FA0/0 interface and put it on the Tunnel 0 interface (and removed the qos pre-qualify from the tunnel), the encapsulated IP header had the CS5 markings, but the outer header did not (as seen below)

Outer:

**Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00: Not-ECT (Not ECN-Capable Transport))**

Inner:

**Differentiated Services Field: 0xa0 (DSCP 0x28: Class Selector 5; ECN: 0x00: Not-ECT (Not ECN-Capable Transport))**

If I check the output from show policy-map interface tunnel 0, it shows my “interesting” traffic being identified and marked.

With no service policy applied, if I do the extended ping commands (as you did), then both IP headers are marked with CS5 as expected.

The only deviation I had from your lab was to use a policy-map set command of “set dscp cs5” instead of a police command

```
R1#sh policy-map
Policy Map PM_ICMP
Class CM_ICMP
set dscp cs5

```

Odd, huh?

&nbsp;

---

_[View the full topic](https://forum.networklessons.com/t/qos-pre-classify-on-cisco-ios/1159)._