Re: ip multicast rate-limit [KZ]

From: Chris Broadway (midatlanticnet@gmail.com)
Date: Thu Jun 08 2006 - 07:20:49 ART


I would be very interested in "The Brians" and Scotts view on this. I
brought this up months ago and noone attempted to touch it. The closest
answer I recieved was to use nested policies when needing to rate limit
multiple multicast streams. Anyone ????

-Chris

On 6/8/06, Darby Weaver <darbyweaver@yahoo.com> wrote:
>
> I find the topic very interesting Koen.
>
> Thanks for the insight.
>
> Please continue. I think many may benefit from your
> postings and queries.
>
>
>
> --- Koen Zeilstra <koen@koenzeilstra.com> wrote:
>
> > Too bad nobody replied to this. I thinks this
> > information is quite
> > valuable and omitted from univercd or CCO in
> > general. The only reference I
> > could find was a tiny bit in Developing IP Multicast
> > networks by Beau
> > Williamson.
> >
> > In theory, ip multicast rate-limit without group or
> > source list aggregates
> > all multicast traffic passin an interface. With
> > group or source list it is
> > more granular specified to the specific group or
> > source list.
> >
> > After playing around with various options I found
> > this:
> >
> > interface Serial0/0
> > ip multicast rate-limit out group-list 10 600
> > ip multicast rate-limit out 1000
> > end
> >
> > Router#sh ip mroute
> > IP Multicast Routing Table
> > Flags: D - Dense, S - Sparse, B - Bidir Group, s -
> > SSM Group, C -
> > Connected,
> > L - Local, P - Pruned, R - RP-bit set, F -
> > Register flag,
> > T - SPT-bit set, J - Join SPT, M - MSDP
> > created entry,
> > X - Proxy Join Timer Running, A - Candidate
> > for MSDP Advertisement,
> > U - URD, I - Received Source Specific Host
> > Report,
> > Z - Multicast Tunnel, z - MDT-data group
> > sender,
> > Y - Joined MDT-data group, y - Sending to
> > MDT-data group
> > , Outgoing interface flags: H - Hardware switched, A
> > - Assert winner
> > Timers: Uptime/Expires
> > Interface state: Interface, Next-Hop or VCD,
> > State/Mode
> >
> > (*, 224.2.2.2), 13:07:37/00:02:08, RP 0.0.0.0,
> > flags: DCL
> > Incoming interface: Null, RPF nbr 0.0.0.0
> > Outgoing interface list:
> > Serial0/0, Forward/Dense, 13:07:37/00:00:00,
> > limit 600 kbps
> >
> > (*, 224.0.1.40), 13:08:32/00:02:06, RP 0.0.0.0,
> > flags: DCL
> > Incoming interface: Null, RPF nbr 0.0.0.0
> > Outgoing interface list:
> > Serial0/0, Forward/Dense, 13:08:28/00:00:00, Int
> > limit 1000 kbps
> > Ethernet0/0, Forward/Dense, 13:08:33/00:00:00
> > !
> >
> > And with
> >
> > interface Serial0/0
> > ip multicast rate-limit out 1000
> > end
> >
> > Router#sh ip mroute
> > IP Multicast Routing Table
> > Flags: D - Dense, S - Sparse, B - Bidir Group, s -
> > SSM Group, C -
> > Connected,
> > L - Local, P - Pruned, R - RP-bit set, F -
> > Register flag,
> > T - SPT-bit set, J - Join SPT, M - MSDP
> > created entry,
> > X - Proxy Join Timer Running, A - Candidate
> > for MSDP Advertisement,
> > U - URD, I - Received Source Specific Host
> > Report,
> > Z - Multicast Tunnel, z - MDT-data group
> > sender,
> > Y - Joined MDT-data group, y - Sending to
> > MDT-data group
> > Outgoing interface flags: H - Hardware switched, A -
> > Assert winner
> > Timers: Uptime/Expires
> > Interface state: Interface, Next-Hop or VCD,
> > State/Mode
> >
> > (*, 224.2.2.2), 13:08:30/00:02:10, RP 0.0.0.0,
> > flags: DCL
> > Incoming interface: Null, RPF nbr 0.0.0.0
> > Outgoing interface list:
> > Serial0/0, Forward/Dense, 13:08:30/00:00:00, Int
> > limit 1000 kbps
> >
> > (*, 224.0.1.40), 13:09:26/00:02:13, RP 0.0.0.0,
> > flags: DCL
> > Incoming interface: Null, RPF nbr 0.0.0.0
> > Outgoing interface list:
> > Serial0/0, Forward/Dense, 13:09:22/00:00:00, Int
> > limit 1000 kbps
> > Ethernet0/0, Forward/Dense, 13:09:27/00:00:00
> >
> >
> > It still seems that the two groups have 1000 kbps
> > each, however I guess
> > the "Int" keywords reveals the secret. That is not
> > present at the
> > grouplist rate-limit 600 before.
> >
> > Very curious what the abbrevations Int means,
> > though.
> >
> > Any thoughts?
> >
> > kind regards,
> >
> > Koen Zeilstra
> >
> >
> >
> >
> > -----------------------
> > November, n.:
> > The eleventh twelfth of a weariness.
> > -- Ambrose Bierce, "The Devil's Dictionary"
> >
> > On Tue, 30 May 2006, Koen Zeilstra wrote:
> >
> > | 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
> >
> === message truncated ===
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Sat Jul 01 2006 - 07:57:32 ART