Qos on 3560 - bandwidth limitation
One ISP 100Mb ---- WAN Switch 3560
Two clients connected (F1/0/14, F1/0/15), 50Mb each
One subnet, one vlan.
switchport access vlan 13
switchport mode access
srr-queue bandwidth limit 50
service-policy input CLIENT-POLICE3
sh policy-map CLIENT-POLICE3
Policy Map CLIENT-POLICE3
police 52428500 950000 exceed-action drop
sh class CLIENT3
Class Map match-any CLIENT3 (id 4)
Match access-group name IP_ANY
sh access-l IP_ANY
Extended IP access list IP_ANY
10 permit ip any any
1. Policing for 50Mbps but a test laptop gets only 4MB, without this policy 12MB?
2. Is there a way to shape using 'srr' command but to combine it with a class-map like in policing?
Any suggestions are welcome. Thx
|reply to m1979 |
1. are you sure about your units of measurement? 50Mbit policy, 4MBytes with, 12MBytes without?
If so, sounds about the right numbers to get, factoring in TCP / IP overhead
2. I'd go hit the Cisco docs for that... unless someone else has more experience with srr. I generally
haven't played with it much before.
EDIT : found this url
for QOS for 3560s. From what I read so far, SRR configurations are only
done in global config mode.
|reply to HELLFIRE |
3560 are not the greatest carrier access switch if you need to do anything beyond basic switching or QoS.
Shaping using SRR, IIRC, is limited to increments of 6% of interface speed. Or maybe that was something else?
Either way, if you're trying to shape an interface that came up as GigE, you're limited to 60mbit increments, which is not helpful if you wanted to shape to a couple of tens of mbits.
Lots of caveats with that platform I think. They look good on paper, then you buy one and try to use it. I got bitten by it as well.
...so while ME switches may be descended from 3560 / 3750 devices, they're alittle more granular with their QOS,
is that one reason to get such gear? I never got to play with such gear, but initially I don't see much differentiation
from their non-ME counterparts.
tubbynetreminds me of the danse russePremium,MVM
me3400/me3750 use cat-qos. which sucks.
me3600x/me3800x use mqc.
[edited to add] the c3600x/c3800x -- use a completely different asic (whales) to accomplish what they need. its a completely redesigned switch and only shares the "metro ethernet" prefix with the earlier variants -- nothing else.
Will keep that in mind if my career path ever takes me that way tubbynet
, thanks for the pointers.