From: Koen Zeilstra (koen@koenzeilstra.com)
Date: Tue May 30 2006 - 03:33:32 ART
I found that the "ip multicast rate-limit out 750" command, without
group-lists, aggregates all multicast traffic and rate-limits it.
With a group list a more granular rate-limiting is applied.
Then two additional questions arise:
1. Is rate-limiting with a group-list applied per flow or per destination?
2. Would you need to exclude the 239.1.1.1 range from acl2 or is the order
in which the ACL's are placed of more importance?
regards,
Koen
-----------------------
"What do you give a man who has everything?" the pretty
teenager asked her mother.
"Encouragement, dear," she replied.
On Mon, 29 May 2006, Koen Zeilstra wrote:
| Hi group,
|
| I want to limit multicast traffic destined to 239.1.1.1 to 500K and traffic to
| all other groups to 750K
|
| Is there a difference between (question/answer related wise) the 2 options
| below?
|
|
| [option 1]
| interface serial 0
| ip multicast rate-limit out group-list 1 500
| ip multicast rate-limit out group-list 2 750
| !
| access-list 1 permit 239.1.1.1 0.0.0.0
| access-list 2 permit 0.0.0.0 255.255.255.255
|
|
| [option 2]
| interface serial 0
| ip multicast rate-limit out group-list 1 500
| ip multicast rate-limit out 750
| !
| access-list 1 permit 239.1.1.1 0.0.0.0
|
| regards,
|
| Koen
|
|
| -----------------------
| May Euell Gibbons eat your only copy of the manual!
|
| _______________________________________________________________________
| Subscription information may be found at:
| http://www.groupstudy.com/list/CCIELab.html
|
This archive was generated by hypermail 2.1.4 : Thu Jun 01 2006 - 06:33:22 ART