Multicast usage examples: Difference between revisions
No edit summary |
|||
| (5 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
==Summary== | ==Summary== | ||
RouterOS supports [[Multicast|PIM-SM]] and [[IGMP | RouterOS supports [[Multicast|PIM-SM]] and [[IGMP-Proxy]] as possible tools to manage and enable multicast traffic in network user is controlling. It is important to use correct tools and correct values to avoid problems that can arise while using multicast traffic. | ||
==Configuration types== | ==Configuration types== | ||
There are several configurations available, each of them have its | There are several configurations available, each of them have its benefits and drawbacks. | ||
==== | ====PIM-SM==== | ||
If router hardware resources allow, it is possible to configure multicast network using just PIM-SM | If router hardware resources allow, it is possible to configure multicast network using just PIM-SM | ||
Drawbacks: | Drawbacks: | ||
*use more router resources to manage it. | *use more router resources to manage it. | ||
| Line 17: | Line 18: | ||
*works for all possible network topologies | *works for all possible network topologies | ||
==== | ====IGMP-Proxy==== | ||
Network can be IGMP-Proxy only if network topology is simple and without loops (for example star topology) | Network can be IGMP-Proxy only if network topology is simple and without loops (for example star topology) | ||
| Line 28: | Line 29: | ||
*simple configuration | *simple configuration | ||
*uses little resources to sustain multicast | *uses little resources to sustain multicast | ||
*with static multicast routes, clients can be IGMP unaware. | *with static multicast routes, clients can be IGMP unaware. | ||
====Mixed configuration==== | ====Mixed configuration==== | ||
| Line 44: | Line 45: | ||
[[IGMP-Proxy]] | [[IGMP-Proxy]] | ||
[[Category:Multicast]] | |||
[[Category:Examples]] | |||
Latest revision as of 16:30, 17 April 2018
Summary
RouterOS supports PIM-SM and IGMP-Proxy as possible tools to manage and enable multicast traffic in network user is controlling. It is important to use correct tools and correct values to avoid problems that can arise while using multicast traffic.
Configuration types
There are several configurations available, each of them have its benefits and drawbacks.
PIM-SM
If router hardware resources allow, it is possible to configure multicast network using just PIM-SM
Drawbacks:
- use more router resources to manage it.
- clients should be IGMP aware to manage joins to groups
Benefits:
- more information about what is happening
- more control over what is supported and what is not
- works for all possible network topologies
IGMP-Proxy
Network can be IGMP-Proxy only if network topology is simple and without loops (for example star topology)
Drawbacks:
- if you have complex network topology it will not be suitable
- almost no control over multicast streaming
- no multicast sources in network
Benefits:
- simple configuration
- uses little resources to sustain multicast
- with static multicast routes, clients can be IGMP unaware.
Mixed configuration
when combining both methods together then it is possible to get best out of both. Backbone with PIM-SM configuration for management, client areas with IGMP proxy.
Drawbacks:
- routers with complex configuration become even more complex
Benefits:
- configuration with simple configurations does not get any more complex
- Full control over what happens where, due to PIM-SM controls every necessary aspect.