Cisco Cisco IOS Software Release 12.2(27)SBC
Configuring Multicast VPN Extranet Support
How to Configure Multicast VPN Extranet Support
14
Cisco IOS IP Multicast Configuration Guide
Configuring RPF for MVPN Extranet Support Using Static Mroutes
Perform this task to configure RPF for extranet MVPNs using static mroutes.
RPF for MVPN Extranet Support Using Static Mroutes
By default, extranet MVPN relies on the unicast routing policies to determine the RPF interface. When
the RPF lookup originates in a receiver MVRF, and it finds that the RPF interface does not lie in the same
MVRF, the router uses the information in the BGP imported route to determine the source MVRF. The
RPF lookup then continues and resolves in the source MVRF. In cases where the multicast and unicast
topologies are incongruent, you can override the default behavior by configuring a static mroute in the
receiver MVRF to explicitly specify the source MVRF using the ip mroute command with the
fallback-lookup keyword and vrf vrf-name keyword and argument.
the RPF lookup originates in a receiver MVRF, and it finds that the RPF interface does not lie in the same
MVRF, the router uses the information in the BGP imported route to determine the source MVRF. The
RPF lookup then continues and resolves in the source MVRF. In cases where the multicast and unicast
topologies are incongruent, you can override the default behavior by configuring a static mroute in the
receiver MVRF to explicitly specify the source MVRF using the ip mroute command with the
fallback-lookup keyword and vrf vrf-name keyword and argument.
Static mroutes can also be configured to support RPF for extranet MVPN in the case where the source
is present in an MVRF and the receiver is in the global table. In this case, because BGP does not allow
VPNv4 routes to be imported into the IPv4 routing table, unicast cannot obtain the source MVRF
information needed to resolve the RPF lookup. To enable the RPF lookup to be resolved in this case, a
static mroute can be configured to explicitly specify the source MVRF using the ip mroute command
with the fallback-lookup keyword and the global keyword.
is present in an MVRF and the receiver is in the global table. In this case, because BGP does not allow
VPNv4 routes to be imported into the IPv4 routing table, unicast cannot obtain the source MVRF
information needed to resolve the RPF lookup. To enable the RPF lookup to be resolved in this case, a
static mroute can be configured to explicitly specify the source MVRF using the ip mroute command
with the fallback-lookup keyword and the global keyword.
Prerequisites
You must configure support for extranet MVPN services prior to performing this task. For more
information, see the
information, see the
task.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip mroute vrf vrf-name source-address mask fallback-lookup {global | vrf vrf-name} [distance]
4.
end
5.
show ip mroute [vrf vrf-name] group-address
6.
show mls ip multicast group group-address
Step 8
show
ip mroute [vrf vrf-name] group-address
Example:
Router# show ip mroute 232.1.1.1
(Optional) Displays the contents of the IP multicast mroute
table for a specific group address.
table for a specific group address.
Step 9
show mls ip multicast
group group-address
Example:
Router# show mls ip multicast group 232.3.3.3
(Optional) Displays MLS information related to a specific
multicast group.
multicast group.
Note
This command only can be used to verify support
for extranet MVPN services on Catalyst 6500 series
switches running Cisco IOS Release 12.2(33)SXH
or a subsequent 12.2SX release.
for extranet MVPN services on Catalyst 6500 series
switches running Cisco IOS Release 12.2(33)SXH
or a subsequent 12.2SX release.
Command or Action
Purpose