QoS marking question

dahua.huang · ‎10-01-2012

Hi, all QoS experts

I have a question about QoS.

Distribution Switch A is a L3 switch for vlan 200 and a inter G1/1 downlink to Access Layer Switch B G0/25

what is the correct way to put service-policy input?

****************************************

Distribton Switch - A

interface G1/1

des link to Access layer switch B

mls qos trust dscp

interface vlan 200

ip address x.x.x.x

service-policy input QOS ????

# Should I put a policy here,

****************************************

Access Layer Switch - B

interface G0/25

des uplink to Distribution layer switch A

mls qos trust dscp

interface range g0/1 - 24

mls qos vlan-based

interface vlan 200

service-policy input QOS

****************************************

Here is my question:

Do I need put service-policy into distribution layer vlan interface? ( this switche designed for L3 only, and around 60 L3 vlan interface inside )

If yes, does the packets will be market again and again through the vlans?

Thanks a lot.

Harish Balakrishnan · ‎10-01-2012

hello Dahua,

What is the gateway of the User end stations is it going to be access or distribution. I assume that is the distribution switch and in that case there is no point in having service policy in vlan 200 in access switch

regards

Harish.

dahua.huang · ‎10-02-2012

then we have another problem.

our distribution is 6509 with sup720-10G.

it has too many vlans inside and it will cause tcam exceed limited if I put service-policy in all.

Any good way to reduce it?

Alessio Andreoli · ‎10-01-2012

Hi there,

Remember that apply a service policy on the svi is not possible on all the platforms (for example 3550 and older can't). By the rest, assuming your platform has at least the same capabilities than a 3560, you can apply a policy there.

Hth

Alessio

Sent from Cisco Technical Support iPad App

Pronoy Dasgupta · ‎10-03-2012

Hello Dahua,

I am interestedin finding out the intent of using the service policy. Are you simply trying to mark some sort of traffic or police / markdown other traffic? The placement of the service policy to some extent might depend on what the desired action is. Also, the input service policy can be placed on the physical interface itself on a 6500. It does not need to be placed specifically on an interface vlan. That limitation comes into the picture when you are trying to configure an out-bound service policy.

If you let us know what the configuration of the service policy would look like, maybe we can help you further.

Thanks

PD

dahua.huang · ‎10-03-2012

Hi, Pronoy Gupta

Thanks first

Here is our QoS template.

*********************************************

class-map match-any VoIP

description Voice IP Phone RTP

match access-group 162

.

class-map match-any Signaling

description SCCP (skinny) signaling

match access-group 166

.

class-map match-any BACKUP

description Generic TSM, NFS

match access-group 169

*********************************************

policy-map QOS

.

class VoIP

set dscp ef

.

class Signaling

set dscp cs3

.

class BACKUP

set dscp af11

class class-default

set dscp default

*********************************************

access-list 162 remark * VoIP class (IP Precedence 5)

access-list 162 remark *** UDP 16384-32767 IP Conference Video & Audio Stream ***

access-list 162 permit udp any gt 16384 any range 16384 32767

access-list 162 permit udp any range 16384 32767 any gt 16384

.

*********************************************

interface config in 6509 Distrition layer:

int range g1/1 - 48

description 1P3Q8T

wrr-queue bandwidth 255 120 40

wrr-queue queue-limit 100 100 100

wrr-queue random-detect min-threshold 1 70 70 70 70 70 70 80 90

wrr-queue random-detect min-threshold 2 70 70 70 70 70 70 80 90

wrr-queue random-detect min-threshold 3 70 70 70 70 70 70 80 90

wrr-queue cos-map 1 6 0

wrr-queue cos-map 1 7 1

wrr-queue cos-map 1 8 2

wrr-queue cos-map 2 7 3

wrr-queue cos-map 2 8 4

wrr-queue cos-map 3 7 6

wrr-queue cos-map 3 8 7

mls qos trust dscp

same for mod 2 - 8 (all the inferface are connected to L2 Access Layer switches, such as 3750 or 4507.)

interface vlan xxx

ip address x.x.x.x

standby 0 ip x.x.x.x

service-policy input QOS

We have over 90 vlan interfaces in each 6509. only put service-policy into 35 vlans. and it take 64% of TCAM already. it will shows tcam exceed limited if over 60 vlans with service-policy.

Config in access-layer

Class-map

Policy-map

ACL

interface G0/25

des uplink to Distribution layer A

mls qos trust dscp

interface G0/26

des uplink to Distribution layer B

mls qos trust dscp

interface range g0/1 - 24

srr-queue bandwidth share 8 30 60 2

srr-queue bandwidth shape 0 0 0 0

priority-queue out

mls qos vlan-based

interface vlan 200

service-policy input QOS

******************************

6509#show mod

Mod Ports Card Type Model Serial No.

--- ----- -------------------------------------- ------------------ -----------

1 48 CEF720 48 port 1000mb SFP WS-X6748-SFP SAL1432PYL8

2 48 CEF720 48 port 1000mb SFP WS-X6748-SFP SAL1432PYJW

3 8 CEF720 8 port 10GE with DFC WS-X6708-10GE SAL1431P87P

4 8 CEF720 8 port 10GE with DFC WS-X6708-10GE SAL1431P8C2

5 5 Supervisor Engine 720 10GE (Active) VS-S720-10G SAL1426LQ6M

7 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL1431P7TS

8 24 SFM-capable 24-port 100FX Multi mode WS-X6524-100FX-MM SAL085283ZD

9 10 WiSM WLAN Service Module WS-SVC-WISM-1-K9 SAL1442WSBG

#show tcam counts
           Used        Free        Percent Used       Reserved
           ----        ----        ------------       --------
Labels:(in) 49        4023            1                    24
Labels:(eg) 0        4072            0                    24

ACL_TCAM
--------
Masks: 100 3996 2 72
Entries: 150 32618 0 576

QOS_TCAM
--------
Masks: 2644 1452 64 25
Entries: 9965 22803 30 200

    LOU:     19         109           14
ANDOR:      0          16            0
ORAND:      0          16            0
    ADJ:      4        2044            0

#show ver

Cisco IOS Software, s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(33)SXI6, RELEASE SOFTWARE (fc4)

Technical Support:

http://www.cisco.com/techsupport

Compiled Mon 28-Mar-11 12:09 by prod_rel_team