QoS - Best Effort not being remarked to Scavenger

Unanswered Question
Jun 24th, 2008

I have a QoS deployment using 3750s and 3560s.

As part of the QoS design, we want to mark down excessive BE and other traffic to Scavenger Class.

This mechanism works for other classes (NET_MGMT_SERVICES & CALL-SIG), but not for Best Effort.

I have checked the SRND, and can't find anything to say that BE cant be marked down to Scavenger.

Has anyone seen this before?

See attachment for an edited example of the config.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
andrew.butterworth Tue, 06/24/2008 - 04:32

You are not matching anything with your class 'DATA'. Your CALL-SIG & NET_MGMT_SERVICES should be marked down to CS1 if they exceed their rates (assuming the ACLs are correct). Anything that doesn't match any of your classes will hit the class-default (which isn't listed by default, however it is there).

I would either add an ACL and tie this to the DATA class or just remove the DATA class and edit the class-default in the policy:

class class-default

set dscp default

police 5000000 8000 exceed-action policed-dscp-transmit




This Discussion