[c-nsp] cisco 2901 qos
Alex Pressé
alex.presse at gmail.com
Tue Nov 5 14:20:13 EST 2013
You are doing it right; all traffic will be shaped to a max of 10M; with
best effort getting at least 2M (or more, if there is no congestion).
class-default just matches everything that hasn't been matched already. In
this case you're matching everything and then applying child policies.
Within ELA_QUEUING_POLICY you might also have class-default statements -
simply to match non IP traffic (depends on purpose of link).
On Tue, Nov 5, 2013 at 12:00 PM, Michael Sprouffske
<msprouffske at yahoo.com>wrote:
> class-map match-any Best-effort
> match ip precedence 0 1
> class-map match-any Priority-Three
> match ip precedence 2 3
> class-map match-any Priority-Two
> match ip precedence 4 6 7
> class-map match-any Priority-One
> match ip precedence 5
> !
> !
> policy-map ELA_QUEUING_POLICY
> class Priority-One
> bandwidth percent 40
> random-detect
> class Priority-Two
> bandwidth percent 20
> random-detect
> class Best-effort
> bandwidth percent 20
> random-detect
> class Priority-Three
> policy-map ELA_SHAPING_POLICY
> class class-default
> shape average 10000000
> service-policy ELA_QUEUING_POLICY
>
> Does this actually shape my trafffic for the class-default if i'm matching
> best-effort on ip pres 1 and 0? Or does that shape command need to be in
> the class best-effort and say remove the class-default?
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
--
Alex Presse
"How much net work could a network work if a network could net work?"
More information about the cisco-nsp
mailing list