Topology change notification for multicast traffic – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual
Page 513
![background image](/manuals/361635/513/background.png)
Multi-Service IronWare Switching Configuration Guide
483
53-1003036-02
How ring breaks are detected and healed
14
Topology change notification for multicast traffic
shows a Layer 2 aggregation network which runs on Brocade MRP. In this scenario,
switch A acts as the MRP master and also the Internet Group Management Protocol (IGMP) querier.
When a link failure is detected on the port 1/1 of switch A, the port 1/2 of switch A will transition
from blocking state to forwarding state allowing the ring to re-converge in sub-second time. With
the transition of port 1/2 to forwarding state, the IGMP querier sends the IGMP reports through the
port 1/2 and the IGMP receivers will send the join message to the querier causing the multicast
traffic to re-converge immediately.
FIGURE 111
MRP ring with switch A as the querier
shows a Layer 2 aggregation network which runs on Brocade MRP. In this scenario,
switch A acts as the MRP master and switch B acts as the IGMP querier. When a link failure is
detected on the switch B, the port 1/2 of switch A will transition from blocking state to forwarding
state causing the multicast traffic to re-converge. The failover time of the multicast traffic is
determined by the IGMP query interval and the IGMP group membership time on the querier. These
timers can be set by ip igmp query-interval and ip igmp group-membership-time commands.