Catalyst 6513 outbound rate-limit config~!

[#1]

We operate Catalyst 6513 equipment.

I want to set rate for outbound traffic on specific ports.

I want to set the limit as below, but how do I set it?

Please help me.

(Example)

---Before---

int gi1/48

rate-limit output 2000000 250000 250000 conform-action transmit exceed-action drop

----After---

mls qos

int gi1/48

wrr-queue bandwitdh ?? ?? ??

wrr-queue queue-limit ?? ?? ??

[Philip D'Ath]

I think use you can use:

srr-queue bandwidth limit <percentage of physical link size>

[#3]

Hello.
There is no " srr-queue " command.
I must use the " wrr-queue " command

Also, I'd like to place a limit on egress traffic.
"wrr-bandwidth" commands represent all in / out?

[Philip D'Ath]

Will it accept a service-policy?

[#5]

Can I set it down like that?

Is it set right?
Please help me.
I don't know much about qos.

<<BEFORE>>

int gi1/48

rate-limit output 100000000 conform-action transmit exceed-action drop

<<AFTER>>

policy-map outbound_100M
 class class-default
  police 100000000 conform-action transmit exceed-action drop

interface gi1/48
 service-policy input outbound_100M

[Philip D'Ath]

Yes, but it would need to be an output policy to match what you had before.

[#7]

Modified.
It is not possible to verify that this is the correct syntax.

rate-limit < limit-bps > < bust bps min> < bust bps max >

Is this right?
Thank you very much for your answers.

[Philip D'Ath]

police bps [burst-normal] [burst-max] conform-action action exceed-action action [violate-action  action]

http://www.cisco.com/c/en/us/td/docs/ios/qos/command/reference/qos_book/qos_n1.html

[#9]

Thank you very very very much.
Finally, let me ask you one more question.
Couldn't the MQC be the L2 interface out?
Does it include in/out unconditionally?
I want to place a limit on out-bound of certain L2 ports.

[Philip D'Ath]

Yes it can be put directly onto a layer 2 interface.

You can usually police in and out - but not all functions of MQC can be done in both directions.

[#11]

Thank you very much.
It helped a lot!

[#12]

hellow. Philip D'Ath.

Currently we are implementing VSS.
S2T-10G is in use.
It doesn't apply to VSL.
You are about to set it on the L2 interface of the normal line card.
"Mls qos" command does not exist.

Example:

core(config)#mls qos ?
% Unrecognized command
core(config)#mls
shc-e06005-core(config)#mls ?
% Unrecognized command
core(config)#int g1/1/3
core(config-if)#mls qo?
% Unrecognized command

The IOS version is using 15.1 (1) SY.

We must use the " wrr-queue" command
Which document should I refer to in order to convert to the same format as "mls  qos"?

Can you help me?...T.T

[Philip D'Ath]

Does it have a PFC4 on the Sup2T-10G?  It looks like it should be supported.

http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/white_paper_c11-652042.html

[#14]

Thank you.

I saw the above two documents.
What is the difference between the global qos and the port unit?

[Philip D'Ath]

Do you have the "wrr-queue shape" command?

http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/white_paper_c11_538840.html