大网数据广告活动
网络与域名解析

How the Multicast Architecture Fits Together

· 52CE 我爱测

This section describes a sample configuration and how the major components fit together.

This section describes a sample configuration and how the major components fit together.

The following illustration shows the relationship between the various components of a router.

relationship between components of windows 2000 router

The multicast group manager is a part of the RRAS service that runs on a server that is operating as a router.

The router shown has three multicast routing protocols (Protocol 1, Protocol 2, Protocol 3) running on it. Each protocol can own one or more interfaces (in this illustration, Protocol 1 owns Interface 1, Protocol 2 owns Interface 2, and Protocol 3 owns Interface 3). Each interface can be owned by only one routing protocol (in addition to IGMP, which is a special case).

The multicast group manager runs on the router and coordinates the distribution of group information between the routing protocols.

The following illustration shows the relationship between two routers in a multicast architecture.

relationship between two routers in multicast architecture

In the previous illustration, Router 2 sends a multicast message to Network 2 on Interface 3. Router 1 receives the multicast message from Network 2 on Interface 3. On both routers, Protocol 3 owns the respective Interface 3.

The following illustration shows the path a message from a multicast source (to a multicast group) takes to reach the host that has joined the multicast group. The routers in the illustration use the same configuration as previous illustrations; however, the interface and protocol details are not shown in order to keep the figure simple.

path of message from multicast source to destination host

The following scenario describes the events that take place when a host joins a multicast group. Refer to the previous illustration for relationships between the various entities.

  1. Host 1 joins the multicast group G on Network 3.
  2. Router 3 learns about G via IGMP.
  3. The multicast group manager on Router 3 notifies Protocol 3 on Router 3 that there are new receivers for G.
  4. Protocol 3 on Router 3 then notifies Protocol 3 on Router 1 about G.
  5. In turn, Protocol 3 on Router 1 notifies the multicast group manager on Router 1 about G.
  6. The multicast group manager on Router 1 then notifies Protocol 1 and Protocol 2 about G.
  7. Protocol 2 may inform Router 2 about G, if the protocol is designed to do so.

The following scenario describes the events that take place when a message is sent to a multicast group. Refer to the previous illustration for the relationships between the various entities.

  1. A source on Network 1 sends a message to Group G.
  2. The message sent from Source S goes first to Router 2, which then forwards it to Router 1 using Interface 2 (since Router 2 has been informed by Protocol 2 that receivers are present downstream).
  3. Router 1 forwards the message to Router 3 (since Router 1 has been informed by Protocol 2 that receivers are present downstream).
  4. Router 3 forwards the message to Network 3, and therefore it arrives at Host 1.

For further information on multicast routing protocol interaction, see RFC 2715, Interoperability Rules for Multicast Routing Protocols.

Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Win32 documentation
适用范围
Windows Win32 API · Source date 05/31/2018
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。