Cisco Nexus 7000 Series Configuration Manual page 194

Configuring MoFRR
Information about MoFRR
Figure 21: Multicast only Fast Re-Route
In the example above, when a routing failure occurs due to a link failure between R4 and R6 routers, R3
becomes the primary upstream router to reach the source. This link to the router then becomes the RPF
interface, and a copy of the multicast stream being received on the link is accepted and forwarded to the
downstream links.
When a routing failure occurs, for example due to a link failure in the blue path, the red upstream router in
the red plane becomes the primary upstream router to reach the source. This link to the router then becomes
the RPF interface, and the copy of the multicast stream being received on the link is accepted and forwarded
to the downstream links.
MoFRR achieves faster convergence by prebuilding the alternate multicast tree and receiving the traffic on
that alternate path. The example discussed above is a simple case where there are two paths from each PE
device toward the source, one along the blue plane and one along the red plane. MoFRR switchover as a result
of routing convergence is expected to be in the order of -200 milliseconds.
Beginning with Release 8.2(1), Cisco Nexus 7000 Series Switches targets to achieve sub-sec convergence
delay for 16K (S, G) running on F3/M3 cards, using MoFRR feature. MoFRR feature allows faster programming
and improved convergence.
Cisco Nexus 7000 Series NX-OS Multicast Routing Configuration Guide
180