cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
962
Views
0
Helpful
2
Replies

QoS help on 3550

jlamanna1
Level 1
Level 1

Hi,

I'm trying to get the following QoS configuration working on a 3550.

I have 2 ports on a switch, say 0/1 is customer facing, and 0/24 is facing a L3 link (non-private) back to our datacenter.

I'd like to use priority queueing on each port and mark the DSCP appropriately for ingress traffic.

I'm trying to use the following classes and policy-maps:

mls qos

class-map match-all cm_voip_signaling

match access-group name voip_signaling

class-map match-all cm_voip_voice

match access-group name voip_voice

!

!

policy-map MARK_VOIP_IN_NET

class cm_voip_voice

  set ip dscp ef

class cm_voip_signaling

  set ip dscp cs3

class class-default

    [police statement]

and on the interfaces:

interface FastEthernet0/1

description TO CUSTOMER

...

wrr-queue bandwidth 10 20 70 1

wrr-queue min-reserve 1 5

wrr-queue min-reserve 2 6

wrr-queue min-reserve 3 7

wrr-queue min-reserve 4 8

wrr-queue cos-map 1 0 1

wrr-queue cos-map 2 2 4

wrr-queue cos-map 3 3 6 7

wrr-queue cos-map 4 5

service-policy input MARK_VOIP_IN_NET

priority-queue out

interface FastEthernet0/24

description TO DATACENTER

...

wrr-queue bandwidth 10 20 70 1

wrr-queue min-reserve 1 5

wrr-queue min-reserve 2 6

wrr-queue min-reserve 3 7

wrr-queue min-reserve 4 8

wrr-queue cos-map 1 0 1

wrr-queue cos-map 2 2 4

wrr-queue cos-map 3 3 6 7

wrr-queue cos-map 4 5

service-policy input MARK_VOIP_IN_NET

priority-queue out

However, if I monitor dscp 24 and 46 of FastEthernet 0/24 I never see any of them on the Egress side, even though I see them being marked

on the Ingress of FE 0/1.

Can anyone explain why this might be?

I do see 24 and 46 on the Egress of FE 0/1.

Thanks.

-- James

2 Replies 2

lgijssel
Level 9
Level 9

How do you verify traffic is actually being marked?

From the partial config it looks like you are using an acl to classify traffic.

This acl may be working only in one direction but source and destination are reversed when coming from fa0/1.

This may not be the cause but more info is needed to solve this.

regards,

Leo

Well, thank you for making me go look at my access list.

For some reason I had assumed I added both directions, but apparently on this switch I did not...sigh.

Review Cisco Networking for a $25 gift card