[nsp] VLAN Traffic shaping not working on 6500

[Tim Stevenson]

Not really, I don't think. I think this is the flow you are suggesting:

vlan 10 (in) <-> vlan 10 (out) <-(loopback)-> vlan 20 (in) <-> vlan 20 (out)

So say you put an egress policer on vlan 20, then it applies to traffic exiting vlan 20 on the actual egress port, but also affects traffic going out the looped back port to vlan 10. So you are not really applying the policer on "egress" traffic only, it really becomes an ingress policer into vlan 10 as well.

Or maybe I am missing what you are suggesting.

Tim

At 08:14 AM 2/4/2004, cisco-nsp-request at puck.nether.net observed:
>Date: Wed, 04 Feb 2004 07:49:05 -0600
>From: Pete Templin <petelists at templin.org>
>Subject: Re: [nsp] VLAN Traffic shaping not working on 6500
>To: Tim Stevenson <tstevens at cisco.com>
>Cc: cisco-nsp at puck.nether.net
>Message-ID: <4020F851.4070305 at templin.org>
>Content-Type: text/plain; charset=us-ascii; format=flowed
>
>Could I patch one VLAN to another, and do ingress policing on the 
>adjacent two ports to achieve two-way policing?
>
>Tim Stevenson wrote:
>> 6500 does not do any *shaping*, it does policing/rate limiting. In other words, we won't "smooth out a bursty flow" by buffering traffic, we basically put a hard cap on usage.
>> 
>> Both sup1 & sup2 support *ingress* policing only, and you need to make sure you are using the right combination of CLI commands to accomplish this, otherwise it won't work or won't work as expected. There should be some example configs on cisco.com in the support area, or use the config guide (which admittedly can be a bit hard to follow).
>> 
>> Sup720 supports ingress & egress policing, but do note on egress that it is aggregate policing only and only on a per-routed (L3) interface or per VLAN basis only, *not* on a per-Layer 2 switch port basis.
>> 


Tim Stevenson, tstevens at cisco.com
Routing & Switching CCIE #5561
Technical Marketing Engineer, Catalyst 6500
Cisco Systems, http://www.cisco.com
IP Phone: 408-526-6759
********************************************************
The contents of this message may be *Cisco Confidential*
and are intended for the specified recipients only.