[c-nsp] Traffic shaping on a GE interface

Tim Franklin tim at pelican.org
Wed Sep 7 08:08:06 EDT 2011


> In some L2 services (usually ethernet based metroE), the policy
> applied
> by the service provider uses ingress policers, and depending on the
> vendor/platform/configuration it may count the whole L2 byte count or
> in
> some cases only the L3 content of the frame...

Indeed, the entire Cisco QoS framework counts completely different things at different parts of the process (input interface, policy map, policer, shaper, egress interface), depending on the interface type, platform, phase of the moon...

The last is slightly unfair, it *is* deterministic, but by $DEITY it's complex...

Regards,
Tim.


More information about the cisco-nsp mailing list