RRAS Routing Protocol Registration
Applies To: Windows Server 2008
The Multicast Group Manager (MGM) application programming interface (API) enables developers to write multicast routing protocols that interoperate with routers running the Multicast Group Manager. When more than one multicast routing protocol is enabled on a router, the MGM coordinates operations between all routing protocols. The MGM informs each routing protocol when group membership changes occur, and when multicast data from a new source or destined to a new group is received.
After the routing protocol registers with MGM, group membership changes can be communicated.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-RasServer |
IPMGM could not find the protocol component: (%1, %2) | |
Microsoft-Windows-RasServer |
Protocol component has already registered with IPMGM. | |
Microsoft-Windows-RasServer |
IPMGM failed to register the protocol component. The data is in the error code. | |
Microsoft-Windows-RasServer |
The protocol component that is attempting to deregister is currently enabled on one or more interfaces. | |
Microsoft-Windows-RasServer |
This protocol component has already been enabled on this interface. | |
Microsoft-Windows-RasServer |
Specified interface was not present in Multicast Group Manager (MGM). | |
Microsoft-Windows-RasServer |
Another routing protocol component has already been enabled on this interface. Only one routing protocol component can be enabled on an interface at any time. | |
Microsoft-Windows-RasServer |
The handle specified by the protocol component is not valid. This maybe because the protocol component is not registered with IPMGM. | |
Microsoft-Windows-RasServer |
Failed to set timer for forwarding entry. The error code is in the data. |