68
Figure 27 Creating an RPF route
As shown in
, the RIP domain and the OSPF domain are unicast isolated from each other.
For the receiver hosts in the OSPF domain to receive multicast packets from the multicast source in
the RIP domain, you must configure Device C and Device D as follows:
•
On Device C, configure a static multicast route for the multicast source and specify Device B as
the RPF neighbor.
•
On Device D, configure a static multicast route for the multicast source and specify Device C as
the RPF neighbor.
NOTE:
A static multicast route is effective only on the multicast router on which it is configured, and will not
be advertised throughout the network or redistributed to other routers.
Multicast forwarding across unicast subnets
Routers forward the multicast data from a multicast source hop by hop along the forwarding tree, but
some routers might not support multicast protocols in a network. When the multicast data is
forwarded to a router that does not support IP multicast, the forwarding path is blocked. In this case,
you can enable multicast forwarding across two unicast subnets by establishing a tunnel between
the routers at the edges of the two unicast subnets.
Vlan-int10
1.1.1.2/24
Vlan-int10
1.1.1.1/24
Vlan-int20
2.2.2.2/24
Vlan-int20
2.2.2.1/24
Source
192.168.0.1/24
Source/Mask
Static multicast routing table on Device C
192.168.0.0/24
Interface
Vlan-int10
RPF neighbor/Mask
1.1.1.1/24
Source/Mask
Static multicast routing table on Device D
192.168.0.0/24
Interface
Vlan-int20
RPF neighbor/Mask
2.2.2.2/24
OSPF domain
RIP domain
Device A
Device B
Device C
Device D
Receiver
Receiver
Multicast packets
Static multicast route