QoS remarking to dscp 0

[tmarlow]

I'm trying to figure out why everytime that I see a policy-map configured, it doesn't take into account the routing protocols, why is that?

I want to remark all traffic coming into our network from our BGP upstreams to be dscp 0, but I'm afraid of messing up the BGP updates. Is this dealt with automatically or do you have to compensate for BGP in the QoS policy?

[Giuseppe Larosa]

Hello Travis,

it would be safer to deny BGP traffic an ACL like

access-list 111 deny tcp any any eq bgp

access-list 111 deny tcp any eq bgp any

access-list 111 permit ip any any

can be used to define what to remark to DSCP0

Hope to help

Giuseppe

[Joseph W. Doherty]

One possible reason, routing protocols tend to be locally sourced and often Cisco treats locally source traffic differently from transit traffic.

For example, when you write "I want to remark all traffic coming into our network from our BGP upstreams to be dscp 0 . . .", would this be the same device that accepts the BGP packets? If so, why would there be a need to remark them?

[tmarlow]

I want to remark all external traffic entering the network to be dscp 0. I do not want this to affect the bgp communications between the two routers though. This is the same device that is accepting the bgp packets from the upstream device.

[Joseph W. Doherty · Accepted solution]

In the case as explained, remarking inbound BGP, along with all other packets, to be DSCP 0 shouldn't cause any issue with those BGP packets.