Importing Routes from Other Protocols

You can import routing information from other protocols into the DVMRP routing table. Only routes that appear in the RPF table can be imported. To do so:

If you want to use IS-IS, OSPF, or RIP routes, make those routes available to multicast protocols. See Defining Static Routes for Reverse-Path Forwarding.
Access Router Configuration mode.
Specify a route map.
Import information from one type of routing domain into another.

redistribute

Use to import information from another type of routing domain to the DVMRP domain. DVMRP can import only routes that appear in the RPF table.
Specify the source protocol from which routes are being redistributed. It can be one of the following keywords: bgp, isis, ospf, static, or connected.
Use the static keyword to redistribute static IP multicast routes into DVMRP.
Use the connected keyword to redistribute routes that are established automatically in the RPF table when another multicast routing protocol, such as PIM, is enabled on an interface.
Use the route-map keyword to configure the route map to filter imported routes from the source routing protocol to the current routing protocol. If you do not specify the route-map option, all routes are redistributed. If you specify the route-map option, but no route map tags are listed, no routes are imported.
Example—Importing routing information from BGP into DVMRP
host1:boston(config-router)#redistribute bgp 100 route-map boston-map
Use the no version to disable redistribution.
See redistribute.

route-map

Use to specify a route map.
Example
host1:boston(config-router)#route-map boston-map atm 3/2
Use the no version to delete the route map. If you do not specify an interface, it removes the global route map if one exists.
See route-map.

router dvmrp

Use to create and enable DVMRP processing on a VR or to access DVMRP Router Configuration mode.
Example
host1:boston(config)#router dvmrp
Use the no version to remove DVMRP from the VR.
See router dvmrp.