I forgot to show the result of this testing.
R1#sh int f0/0
FastEthernet0/0 is up, line protocol is up
Hardware is AmdFE, address is cc02.0ccc.0000 (bia cc02.0ccc.0000)
R2#sh run int f0/0
Building configuration...
Current configuration : 520 bytes
!
interface FastEthernet0/0
ip address 150.50.12.2 255.255.255.0
rate-limit input access-group 700 8000000 1500000 3000000
conform-action transmit exceed-action drop
R2#sh access-list 700
Bridge address access list 700
permit cc02.0ccc.0000 0000.0000.0000
permit 1111.1111.1111 0000.0000.0000
R2#sh int f0/0 rate-limit
FastEthernet0/0
Input
matches: access-group 700
params: 8000000 bps, 1500000 limit, 3000000 extended limit
conformed 1676 packets, 419715 bytes; action: transmit
exceeded 0 packets, 0 bytes; action: drop
last packet: 3836ms ago, current burst: 0 bytes
last cleared 01:01:45 ago, conformed 0 bps, exceeded 0 bps
Best Regards,
Marut
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Marut
[EMAIL PROTECTED]@DCTH-BKK
Sent: Wednesday, 19 December, 2007 4:52 PM
To: [EMAIL PROTECTED]; [email protected]
Cc: [EMAIL PROTECTED]
Subject: Re: [OSL | CCIE_SP] access-list rate-limit
Hi All,
Has anyone test with access-list rate-limit? I wonder what
is the different between
access-list rate-limit 100 1111.1111.1111 apply with rate-limit
input access-group rate-limit 100 .....
and
access-list 700 1111.1111.1111 0000.0000.0000 apply with
rate-limit input access-group 700 ...
I have read from the document and found
"using the rate-limit command, to individual rate-limit access lists.
When packets in an access list are classified in this manner, the
packets with different IP precedences, MAC addresses, or MPLS
experimental field values are treated differently by the CAR process"
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cr/hq
os_r/qos_a1h.htm#wp1139072
Seem like cisco design to use access-list rate-limit for matching
with ip-prec, mac and mpls. But I think the second method could also
useful. Any idea for this
Thanks
Marut
************************************************************************
****
This email and all contents are subject to the following disclaimer:
http://www.datacraft-asia.com/disclaimer
************************************************************************
****
