Can someone please explain to me how this rendevous_point works in this whole schema of multicasting? I have a huge multicast network (Live price quote feeds) going out to workstations and across a backbone of 6509 switch connected to various 3600's, 2600's, stray 7200, which are then connected to 2943GL3's and 3550's which are connected to the workstations. Just to give you a picture. I just walked into this mess 9 days ago and I am already drowning. HELP!!!
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Multicast Setup
- Thread starter CavemanNT
- Start date
Basic:
Normal: Five hosts want the same resouce from a server. The server sees five converstaions.
Multicast: Five hosts want the same info from the same server, the server sends the info in one stream.
How Multicasting is done:
6 routers, partial mesh
Active: A massive poll-storm is done to establish who wants the stream and where they are. Each router know “4 hosts out of my eth 0 want this stream. I still need to let it though” The poll is re-done periodicly to refresh the ‘topology’
Passive: The server advertises it’s services to the rondev point and it doesn’t go any father. A host says, “I want to hear the president speak, hook me up!” and the local gateway finds the rondevu point(who knows all regarding multicasts) who says, “Listen to server S”. The local gateway will then listen to server S(while opomizing the path taken) and connect the host up.
Note: This behavior is not natural for routers. You will need to configure a protocol to do this for you. PIM and IGMP/CGMP is reccomoended by cisco.
It’s a rough expliation but I hope it helps.
Normal: Five hosts want the same resouce from a server. The server sees five converstaions.
Multicast: Five hosts want the same info from the same server, the server sends the info in one stream.
How Multicasting is done:
6 routers, partial mesh
Active: A massive poll-storm is done to establish who wants the stream and where they are. Each router know “4 hosts out of my eth 0 want this stream. I still need to let it though” The poll is re-done periodicly to refresh the ‘topology’
Passive: The server advertises it’s services to the rondev point and it doesn’t go any father. A host says, “I want to hear the president speak, hook me up!” and the local gateway finds the rondevu point(who knows all regarding multicasts) who says, “Listen to server S”. The local gateway will then listen to server S(while opomizing the path taken) and connect the host up.
Note: This behavior is not natural for routers. You will need to configure a protocol to do this for you. PIM and IGMP/CGMP is reccomoended by cisco.
It’s a rough expliation but I hope it helps.
- Thread starter
- #3
The intersting thing is that I have a mish-mosh of eigrp groups, IGRP grps, and RIP but nothing is standard (which is my job i guess to get done) but I feel like i want to go with eigrp to kind of give it some sorta back bone. As far as implementing this idea how hard is it to get eigrp up and running on a network?
EIGRP is fairly easy to get going on a network and generally it is best to run a single Routing Protocols vs what you have where tehre are many. Sometimes it's worth changing to a single protocol, but if you came into an existing large network ten it might be difficult. But it is fairly straight forward to setup EIGRP, just remember that your network has to be all Cisco to do it (as with IGRP).
Burke
Burke
Rburke is right, EIGRP is by far one of the easier (excluding RIP) protocols to configure. But, you have to take certain things into concideration. Do I have an all cisco network infrastructure? What are all the protocols I am running and how will they react to changes made? What do I need to do to make sure connectivity is maintained during the changes? Etc., Etc.
Make sure you map things out well.
Make sure you map things out well.
If the above questions are YES, and after mapping things out, you might smoothly migrating from XX Protocol to EIGRP. Start by portions of your network.
As far as multicast concerns, Rendez-vous Point-RP-requires a bit of configuration as well, not tough though. Actually I can't remember reading any rule of thumb when comes to choosing which router is to be the RP. I would suggest using 2 RPs, either for load balancing or, simply put, redundancy. I would choose the ones closer to the sources/servers.
best regards,
As far as multicast concerns, Rendez-vous Point-RP-requires a bit of configuration as well, not tough though. Actually I can't remember reading any rule of thumb when comes to choosing which router is to be the RP. I would suggest using 2 RPs, either for load balancing or, simply put, redundancy. I would choose the ones closer to the sources/servers.
best regards,
- Status
Similar threads
