From: Mark Lewis (markl11@xxxxxxxxxxx)
Date: Thu Sep 21 2000 - 07:04:06 GMT-3
Well, you can use the command 'ip igmp join-group xxxx' on one of the leaf
routers (ie. at the bottom of your distribution tree/ connected to lan).
This command is useful so that you can ping multicast addresses and also
VERY useful if you have an application like Ghost which doesn't send IGMP
join (membership reports) to the local router as it 'should'.
Or, try getting an evaluation copy of IPTV from Cisco.
Or, try going to www.hugewave.com/blacktools (I think. It's a link that is
referenced at the back of the Little Black Book of IP Routing!). Little
multicast app. for testing.
Mark
>From: "Eddie Parra" <eparra@telocity.com>
>Reply-To: <eparra@telocity.com>
>To: "Mark Lewis" <markl11@hotmail.com>, <eparra@telocity.com>
>Subject: RE: Multicasting Questions...
>Date: Wed, 20 Sep 2000 14:54:17 -0400
>
>Thank you very much for spending so much time on this answer. After
>reading
>this I only have 1 other question. How can you test your multicast
>configs?
>
>-Eddie
>
>-----Original Message-----
>From: Mark Lewis [mailto:markl11@hotmail.com]
>Sent: Wednesday, September 20, 2000 11:29 AM
>To: eparra@telocity.com
>Subject: Re: Multicasting Questions...
>
>
>
>
>Right, big question!
>
>Rendezvous Point are a common distribution point for multicast traffic when
>using a sparse mode multicast routing protocol (eg. PIM SM/CBT (although
>with CBT it has a different name).
>
>With multicast there are three important levels of interaction:
>
>1.Interaction between hosts on subnets and 'local' routers (registration
>not
>of clients (only the last reporter is registered per group),but of
>multicast
>groups (traffic) that hosts on that segment require). This process is
>handled by IGMP.
>
>2.There's interaction between switches and local routers via CGMP or IGMP
>snooping (registration of multicast clients on the switches so that
>multicast traffic is not just flooded (default behavior). This (CGMP/IGMP
>snooping) is optional, but recommended.
>
>3.Interaction between routers.
>
> a. Dense mode (eg. DVMRP/PIM DM/MOSPF) : traffic is flooded throughout
>the
>network initially, until 'downstream' routers tell upstream ones that they
>don't want the traffic (pruning). Routers use RPF checks to switch over to
>SPT (shortest path tree) back to source.
>
>b. Sparse mode: traffic here is not flooded. 'Downstream' routers here
>request traffic from the RP intially and then switch over to SPT (shortest
>path back to 'real' source (ie. multicast server) when they know where it
>is
>(they find out after they get initial packets from the RP by looking at the
>source address of the packets).
>
>It's best to have a few RP candidates on the network (use auto rp instead
>of
>manual rp config on large net.s) for redundancy. Can be in core of net or
>close to multcast servers.
>
>Hope that helps,
>
>Mark
>
>
>
> >From: "Eddie Parra" <eparra@telocity.com>
> >Reply-To: "Eddie Parra" <eparra@telocity.com>
> >To: "CCIE Group Study" <ccielab@groupstudy.com>
> >Subject: Multicasting Questions...
> >Date: Wed, 20 Sep 2000 10:23:34 -0400
> >
> >Can anyone answer a few multicasting questions. Am I correct in saying
> >that
> >the RP handles registration for all multicast clients? My other question
> >is, where do you place the RP's? Do I need a RP on every segment? Every
> >VLAN? Could someone explain this a little better. Thanks...
> >
> >-Eddie
> >
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:59 GMT-3