From: chrlewis@cisco.com
Date: Thu Sep 15 2005 - 16:25:12 GMT-3
There are a few things that don't seem right to me with the question as
presented here.
Assuming that the server and the router are on the same vlan, and
connecetd to say fa0/1 and fa0/2 respectively on the switch.
Taking the requirement, the server uses port 2000. Without being able to
clarify this with a proctor, I would read this as there is an
application on the server that responds to packets destined for port
2000. That is packets going to the server has a destination port of
2000.
The terms max 256 and normal 64 do not mean anything to me in the
context of QoS configuration. Any one else please offer an opinion.
Looking at what you have configured (I think you meant to classify on
port 2000, not 4000 :)
Configuring police cir and just specifying the bc and be is the same as
configuring it without the cir option, so I don't see the purpose.
If you configure a 64000 rate with a Bc of 2000, that gives you a Tc of
1/4 not 1/8 by my math. It looks like you are trying to use Be to
provide the 256K maximum rate. I don't think this is feasible. Be is a
byte value, not a rate value and any attempt to make it so is
non-deterministic as it depends upon packet arrival rate.
Typically if there are two rates specified in the question, it is
looking for the two rate policer, specified with the police cir and pir
command (you need to look on the 12.3 command reference for that).
If you are told traffic comes from the router to the server via the
switch, the question is doable. You can mark traffic destined for port
2000 at ingress to the switch, then police based off internal DSCP on
egress.
There are however significant differences between the router police
command and the switch police command. The 3550 does not support the two
rate policer model, however the newer 3750 metro does, so that may open
up more possibilities next year.
I don't know if this helps, but the question does not make sense to me
as presented.
Chris
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Stefan Grey
Sent: Thursday, September 15, 2005 12:05 PM
To: ccielab@groupstudy.com
Subject: Scenario 3550 + police problem. Help!!
Hello group,
I have got the tasK:
The problem is with the Catalys configuration. Do Catalyst and Router
have different police commands??
TASK:
SW1 - R6. Between this devices is a server which uses UDP port 2000. We
should limit traffic so that max would be 256 Kbps and normal would be
64 Kbps. Between SW1 and R1 is ethernet.
END
Please comment my solution. Suggest somethig. Why can't I complete
this??
My solution:
We need to limit the input traffic so this should be policing (since as
we know traffic shaping Is usually used for output traffic. So for R1
the config would be:
R6(config)#access-list 100 permit udp any eq 4000 any
Is the access-list correct?? As I learned within my study eq should be
on the side of the server. That's why any eq 4000 any.
R6(config)#class-map match-all UDPCLASS
R6(config-cmap)#match access-group 100
R6(config)#police-map UDPPOLICY
R6(config-pmap)#CLASS UDPCLASS
R6(config-pmap-c)#police cir 64000 bc 2000 be 24000 tc = 125 so the
parametrs are as above R6(config-if)#service-policy input UDPPOLICY
R6(config-if)#
NOW trying to do the same for the CAT1
CAT1(config)#access-list 100 permit udp any eq 4000 any
CAT1(config)#class-map match-all UDPCLASS CAT1(config-cmap)#match acc
CAT1(config-cmap)#match access-group 100 CAT1(config-cmap)#exit
CAT1(config)#poli CAT1(config)#policy-map UDPPOLICY
CAT1(config-pmap)#class UDPCLASS CAT1(config-pmap-c)#poli
CAT1(config-pmap-c)#police cir ?
% Unrecognized command
CAT1(config-pmap-c)#police cir ?
% Unrecognized command
CAT1(config-pmap-c)#police 64000 ?
<8000-2000000> Normal burst bytes
There is no police cir command. And the minimum normal burst is 8000 and
I can't set it to 2000.
According to this I just don't know how to finish the task on SW1 and am
mixed up with police commands. HOw different is policing on Catalyst and
Router???
Any comments are very appreciated.
This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:15 GMT-3