Marking RFC 1918 traffic for prioritization

thomuff · ‎08-11-2009

The question is How do I mark 1918 traffic so my vendor can prioritize this traffic over 1918 traffic without messing up my voice traffic?

We have MPLS connectivity where the Public and Private (Voice and Data) traffic travel across the same WAN links.

One suggestion is to prioritize enterprise (1918) traffic over Internet traffic.

To accomplish this task, we have to mark the 1918 traffic on our router.

Would I add a class map to my existing policy map whic is applied to my interface using a service policy?

Any input is greatly appreciated.

.

paolo bevilacqua · ‎08-11-2009

Before you do anything, are you sure that you MPLS provider supports different classes of service ?

Not all do.

thomuff · ‎08-11-2009

Yes, the MPLS provider supports different class of service. They stated, if we can mark it, they can prioritize it. Today, we have four different planes.

paolo bevilacqua · ‎08-11-2009

Then just look an example of DSCP marking.

You can use any criteria you like. Some voice traffic comes already marked.

Edison Ortiz · ‎08-11-2009

ip access-list extended RFC1918

permit ip 10.0.0.0 0.255.255.255 10.0.0.0 0.255.255.255

permit ip 10.0.0.0 0.255.255.255 172.16.0.0 0.15.255.255

permit ip 10.0.0.0 0.255.255.255 192.168.0.0 0.0.255.255

permit ip 172.16.0.0 0.15.255.255 10.0.0.0 0.255.255.255

permit ip 172.16.0.0 0.15.255.255 172.16.0.0 0.15.255.255

permit ip 172.16.0.0 0.15.255.255 192.168.0.0 0.0.255.255

permit ip 192.168.0.0 0.0.255.255 10.0.0.0 0.255.255.255

permit ip 192.168.0.0 0.0.255.255 172.16.0.0 0.15.255.255

permit ip 192.168.0.0 0.0.255.255 192.168.0.0 0.0.255.255

class-map RFC1918

match access-group name RFC1918

policy-map XXXX

class RFC1918

set ip dscp xxx

HTH,

__

Edison.