The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Restrictions for Configuring mVPN Extranet Support
The multicast VPN (mVPN) extranet support feature supports only Protocol Independent Multicast (PIM) sparse mode (PIM-SM)
and Source Specific Multicast (SSM) traffic; PIM dense mode (PIM-DM) and bidirectional PIM (bidir-PIM) traffic are not supported.
When configuring mVPN extranet in a PIM-SM environment, the source and the rendezvous point (RP) must reside in the same
site of the mVPN behind the same provider edge (PE) router.
IPv6 based mVPN extranet is not supported.
Information About mVPN Extranet Support
The mVPN extranet support feature enables service providers to distribute IP multicast content originating from one enterprise
site to other enterprise sites. With this feature, service providers can offer the next generation of flexible extranet services,
helping to enable business partnerships between different enterprise VPN customers. Service providers can offer multicast
extranet contracts to meet various business partnership requirements, including short-term, annual, and rolling contracts.
An extranet can be viewed as part of a company’s intranet that is extended to users outside the company. With this feature,
a VPN is used as a way to do business with other companies as well as to sell products and content to customers and companies.
An extranet is a VPN connecting a corporate site or sites to external business partners or suppliers to securely share part
of a business’s information or operations among them. mVPN extranet support feature enables efficient content distribution
between enterprises and from service providers or content providers to their different enterprise VPN customers.
Multiprotocol Label Switching (MPLS) VPNs inherently provide security, ensuring that users access only appropriate information.
MPLS VPN extranet services offer extranet users unicast connectivity without compromising the integrity of their corporate
data. The mVPN extranet support feature extends this offer to include multicast connectivity to the extranet community of
interest.
Overview of mVPN Extranet Support
For unicast, there is no difference between an intranet or extranet from a routing perspective, that is, when a VRF imports
a prefix, that prefix is reachable through a label-switched path (LSP). If the enterprise owns the prefix, the prefix is considered
a part of the corporate intranet. Otherwise, the prefix is considered a part of an extranet. For multicast, however, the reachability
of a prefix (especially through an LSP) is not sufficient to build a multicast distribution tree (MDT).
In order to provide support for mVPN extranet services, the same default MDT group must be configured in the source and receiver
multicast VPN routing and forwarding (MVRF).
In the mVPN extranet support feature, the receiver and source MVRF multicast route (mroute) entries are linked. The Reverse
Path Forwarding (RPF) check relies on unicast routing information to determine the interface through which the source is reachable.
This interface is used as the RPF interface.
Components of an mVPN Extranet
The figure below illustrates the components that constitute an mVPN extranet.
Figure 1. Components of an mVPN Extranet
MVRF: An MVRF is a multicast-enabled VRF. A VRF consists of an IP routing table, a derived forwarding table, a set of interfaces
that use the forwarding table, and a set of rules and routing protocols that determine what goes into the forwarding table.
In general, a VRF includes the routing information that defines a customer VPN site that is attached to a provider edge (PE)
router.
Source MVRF: An MVRF that can reach the source through a directly connected customer edge (CE) router.
Receiver MVRF: An MVRF to which receivers are connected through one or more CE devices.
Source PE: A PE router that has a multicast source behind a directly connected CE router.
Receiver PE: A PE router that has one or more interested receivers behind a directly connected CE router.
Configuring mVPN Extranet Support
The following mVPN extranet service configuration options are available:
Option 1: Configure the source MVRF on the receiver PE router.
Option 2: Configure the receiver MVRF on the source PE router.
mVPN Extranet Support Configuration - Option 1
You can provide mVPN extranet services to enterprise VPN customers by configuring a source MVRF on a receiver PE router.
On a receiver PE router that has one or more interested receivers in a extranet site behind a directly connected CE router,
configure an additional MVRF that has the same default MDT group as the site connected to the multicast source, if the MVRF
is not configured.
Configure the same unicast routing policy to import routes from the source MVRF to the receiver MVRF.
The figure illustrates the flow of multicast traffic in an extranet MVPN topology where the source MVRF is configured on
a receiver PE router (Option 1). In the topology, an MVRF is configured for VPN-Green and VPN-Red on PE2, a receiver PE router.
A multicast source behind PE1, the source PE router, is sending out a multicast stream to the MVRF for VPN-Green. There are
interested receivers behind PE2, the receiver PE router for VPN-Red, and behind PE3, the receiver PE router for VPN-Green.
After PE1 receives the packets from the source in the MVRF for VPN-Green, it replicates and forwards the packets to PE2 and
PE3, because both routers are connected to receivers in VPN-Green. The packets that originated from VPN-Green are then replicated
on PE2 and forwarded to the interested receivers in VPN-Red and are replicated on PE3 and forwarded to the interested receivers
in VPN-Green.
While configuring the source MVRF on the receiver PE router, the MDT group configuration of the source MVRF must be the same
on both the source and receiver PE routers. In addition, you must configure the same unicast routing policy to import routes
from the source MVRF (the MVRF for VPN-Green) to the receiver MVRF (the MVRF for VPN-Red).
Figure 2. Packet Flow for mVPN Extranet Support Configuration Option 1
mVPN Extranet Support Configuration - Option 2
You can provide mVPN extranet services to enterprise VPN customers by configuring the receiver MVRF on the source PE router.
For each extranet site, you must configure an additional MVRF on the source PE router that has the same default MDT group
as the receiver MVRF, if the MVRF is not configured on the source PE.
In the receiver MVRF configuration, you must configure the same unicast routing policy on the source and receiver PE routers
to import routes from the source MVRF to the receiver MVRF.
The figure illustrates the flow of multicast traffic in an mVPN extranet topology where a receiver MVRF is configured on
the source PE router (Option 2). In the topology, an MVRF is configured for VPN-Green and VPN-Red on PE1, the source PE router.
A multicast source behind PE1 is sending out a multicast stream to the MVRF for VPN-Green, and there are interested receivers
behind PE2 and PE3, the receiver PE routers for VPN-Red and VPN-Green, respectively. After PE1 receives the packets from the
source in the MVRF for VPN-Green, it independently replicates and encapsulates the packets in the MVRF for VPN-Green and VPN-Red
and forwards the packets. After receiving the packets from this source, PE2 and PE3 decapsulate and forward the packets to
the respective MVRFs.
While configuring the receiver MVRF on the source PE router, in the receiver MVRF configuration, the default MDT group must
be the same on both the source and receiver PE routers. In addition, you must configure the same unicast routing policy to
import routes from the source MVRF (the MVRF for VPN-Green) to the receiver MVRF (the MVRF for VPN-Red).
Figure 3. Packet Flow for mVPN Extranet Support Configuration Option 2
RPF for mVPN Extranet Support Using Imported Routes
You must configure either the receiver MVRF on the source PE router (Option 1) or the source MVRF on the receiver PE router
(Option 2) for extranet links to be created. Once configured, RPF relies on unicast routing information to determine the interface
through which the source is reachable. This interface is used as the RPF interface. No additional configuration is required
for RPF resolution. The mVPN extranet support feature supports RPF from one VRF to another VRF, from a VRF to the global routing
table, and from the global routing table to a VRF.
RPF for mVPN Extranet Support Using Static Mroutes
By default, an mVPN extranet relies on 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 Border Gateway Protocol (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 ipmroute command with the fallback-lookup keyword and vrfvrf-name keyword and argument.
Static mroutes can also be configured to support RPF for mVPN extranet 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 theipmroute command with the fallback-lookup keyword and the global keyword.
mVPN Extranet VRF Select
The mVPN extranet VRF Select feature provides the capability for RPF lookups to be performed to the same source address in
different VRFs using the group address as the VRF selector. This feature enhances mVPN extranets by enabling service providers
to distribute content streams coming in from different mVPNs and redistributing them from there.
The mVPN VRF Select feature is configured by creating group-based VRF selection policies. Group-based VRF selection policies
are configured using the ipmulticastrpfselect command. The ipmulticastrpfselect command is used to configure RPF lookups originating in a receiver MVRF or in the global routing table to be resolved in
a source MVRF or in the global routing table based on group address. Access Control Lists (ACLs) are used to define the groups
to be applied to group-based VRF selection policies.
The figure illustrates an mVPN extranet topology with the mVPN VRF Select feature configured. In this topology, (S, G1) and
(S, G2) PIM joins originating from VPN-Green, the receiver VRF, are forwarded to PE1, the receiver PE. Based on the group-based
VRF selection policies configured, PE1 sends the PIM joins to VPN-Red and VPN-Blue for groups G1 and G2, respectively.
Figure 4. RPF Lookups Using Group-Based VRF Selection Policies
How to Configure mVPN Extranet Support
Configuring mVPN Support
Perform one of the following tasks to provide mVPN extranet capabilities in an IPv4 core network:
Configuring the Source MVRF on the Receiver PE - Option 1
Perform this task to configure the source MVRF on the receiver PE router (Option 1) and provide support for mVPN extranet
services.
Before you begin
You must configure Intranet VPN in the source and receiver VPNs prior to performing this task.
Procedure
Command or Action
Purpose
Step 1
enable
Example:
Device> enable
Enables privileged EXEC mode.
Enter your password if prompted.
Step 2
configureterminal
Example:
Device# configure terminal
Enters global configuration mode.
Step 3
vrf definitionvrf-name
Example:
Device(config)# vrf definition VPN-Red
Defines the VPN routing instance by assigning a VRF name and enters VRF configuration mode.
The vrf-name argument is the name assigned to a VRF.
Step 4
rdroute-distinguisher
Example:
Device(config-vrf)# rd 55:1111
Creates routing and forwarding tables.
The route-distinguisher argument adds an 8-byte value to an IPv4 prefix to create a VPN IPv4 prefix. You can enter an RD in either of these formats:
16-bit autonomous system number: your 32-bit number, for example, 101:3
32-bit IP address: your 16-bit number, for example, 192.168.122.15:1
Step 5
route-targetimportroute-target-ext-community
Example:
Device(config-vrf)# route-target import 55:1111
Creates a route-target extended community for a VRF.
The import keyword exports routing information to the target VPN extended community.
The route-target-ext-community argument adds the route-target extended community attributes to the VRF’s list of import, export, or both (import and export)
route-target extended communities.
Note
For content to be distributed from the source MVRF to the receiver MVRF, you must configure the same unicast routing policy
on the source and receiver PE routers to import routes from the source VRF to the receiver VRF.
Step 6
mdtdefaultgroup-address
Example:
Device(config-vrf)# mdt default 232.1.1.1
Configures the multicast group address range for data MDT groups for a VRF.
A tunnel interface is created as a result of this command.
By default, the destination address of the tunnel header is the group-address argument.
Step 7
end
Example:
Device(config-vrf)# end
Exits VRF configuration mode and returns to privileged EXEC mode.
Step 8
showipmroute [vrfvrf-name] group-address
Example:
Device# show ip mroute 232.1.1.1
(Optional) Displays the contents of the IP multicast mroute table for a specific group address.
Step 9
show platform software fed switch { switch-number | active | standby } ip multicast groups [ vrf-id vrf-id | vrf-name vrf-name] [ group-address | count | summary]
Example:
Device# show platform software fed switch active ip multicast groups 232.3.3.3/32
(Optional) Displays information related to the specified multicast group.
Configuring the Receiver MVRF on the Source PE - Option 2
Perform this task to configure the receiver MVRF on the source PE router (Option 2) and provide support for mVPN extranet
services.
Before you begin
You must configure Intranet VPN in the source and receiver VPNs prior to performing this task.
Procedure
Command or Action
Purpose
Step 1
enable
Example:
Device> enable
Enables privileged EXEC mode.
Enter your password if prompted.
Step 2
configureterminal
Example:
Device# configure terminal
Enters global configuration mode.
Step 3
vrf definitionvrf-name
Example:
Device(config)# vrf definition VPN-Red
Defines the VPN routing instance by assigning a VRF name and enters VRF configuration mode.
The vrf-name argument is the name assigned to a VRF.
Step 4
rdroute-distinguisher
Example:
Device(config-vrf)# rd 55:2222
Creates routing and forwarding tables.
Specify the route-distinguisher argument to add an 8-byte value to an IPv4 prefix to create a VPN IPv4 prefix. You can enter an RD in either of these formats:
16-bit autonomous system number: your 32-bit number, for example, 101:3
32-bit IP address: your 16-bit number, for example, 192.168.122.15:1
Step 5
route-targetimportroute-target-ext-community
Example:
Device(config-vrf)# route-target import 55:1111
Creates a route-target extended community for a VRF.
The import keyword imports routing information from the target VPN extended community.
The route-target-ext-community argument adds the route-target extended community attributes to the VRF’s list of import, export, or both (import and export)
route-target extended communities.
Note
For content to be distributed from the source MVRF to the receiver MVRF, you must configure the same unicast routing policy
on the source and receiver PE routers to import routes from the source VRF to the receiver VRF.
Step 6
mdtdefaultgroup-address
Example:
Device(config-vrf)# mdt default 232.3.3.3
Configures the multicast group address range for data MDT groups for a VRF.
A tunnel interface is created as a result of this command.
By default, the destination address of the tunnel header is the group-address argument.
Step 7
end
Example:
Device(config-vrf)# end
Exits VRF configuration mode and returns to privileged EXEC mode.
Step 8
showipmroute [vrfvrf-name] group-address
Example:
Device# show ip mroute 232.3.3.3
(Optional) Displays the contents of the IP multicast mroute table for a specific group address.
Configuring RPF for mVPN Extranet Support Using Static Mroutes
Before you begin
You must configure support for mVPN extranet services prior to performing this task.
Device(config)# ip mroute vrf VPN-Red 224.100.0.5 255.255.255.255 fallback-lookup vrf VPN-Green
Configures the RPF lookup originating in a receiver MVRF to continue and be resolved in a source MVRF or in the global routing
table using a static mroute.
The global keyword is used to specify that the source MVRF is in the global routing table.
The vrf keywordandvrf-name argument are used to explicitly specify a VRF as the source MVRF.
Step 4
end
Example:
Device(config)# end
Exits global configuration mode and enters privileged EXEC mode.
Step 5
showipmroute [vrfvrf-name] group-address
Example:
Device# show ip mroute 224.100.0.5
(Optional) Displays the contents of the IP multicast mroute table for a specific group address.
Configuring Group-Based VRF Selection Policies with mVPN Extranet
Perform this task to configure group-based VRF selection policies with mVPN.
This task enables RPF lookups to be performed to the same source address in different VRFs using the group address as the
VRF selector.
Before you begin
You must configure support for mVPN extranet services prior to performing this task.
You must configure the ACLs to be applied to group-based VRF selection policies.
Configures RPF lookups originating in a receiver MVRF or in the global routing table to be resolved in a source MVRF or in
the global routing table based on group address.
Step 4
Repeat step 3 to create additional group-based VRF selection policies.
--
Step 5
end
Example:
Device(config)# end
Exits global configuration mode and enters privileged EXEC mode.
Displays information about how IP multicast routing does RPF.
Use this command after configuring group-based VRF selection policies to confirm that RPF lookups are being performed based
on the group address, and to display the VRF where the RPF lookup is being performed.
Configuration Examples for mVPN Extranet Support
Example: Configuring the Source VRF on the Receiver PE Router- Option 1
The following configuration example is based on the mVPN extranet topology illustrated in the figure. This example shows
the configurations for PE2, the receiver PE router, and PE1, the source PE router. In this example, mVPN extranet services
are supported between VPN-Green and VPN-Red by configuring the source MVRF for VPN-Green on PE2. The same unicast routing
policy is configured to import routes from VPN-Green to VPN-Red.
Figure 5. Topology for mVPN Extranet Support Option 1 Configuration Example
States in the Global Table on PE1 and PE2 for the MDT Default Group 232.1.1.1
The following are sample outputs from the showipmroute command on PE1 and PE2. The sample outputs show the global table for the MDT default group 232.1.1.1 on PE1 and PE2.
Device# show ip mroute 232.1.1.1
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(10.2.0.2, 232.1.1.1), 00:01:19/00:02:42, flags: sTIZ
Incoming interface: Ethernet0/0, RPF nbr 10.0.1.4
Outgoing interface list:
MVRF VPN-Green, Forward/Sparse-Dense, 00:01:19/00:02:07
(10.1.0.1, 232.1.1.1), 00:02:19/00:03:11, flags: sT
Incoming interface: Loopback0, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0, Forward/Sparse-Dense, 00:02:00/00:02:36
Device# show ip mroute 232.1.1.1
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(10.1.0.1, 232.1.1.1), 00:02:04/00:02:38, flags: sTIZ
Incoming interface: Ethernet1/0, RPF nbr 10.0.2.4
Outgoing interface list:
MVRF VPN-Green, Forward/Sparse-Dense, 00:02:04/00:02:09
(10.2.0.2, 232.1.1.1), 00:02:04/00:03:09, flags: sT
Incoming interface: Loopback0, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet1/0, Forward/Sparse-Dense, 00:01:22/00:03:09
States in the Global Table on PE1 and PE2 for the MDT Default Group 232.1.1.1 When PE1 and PE2 Are Switches Configured for
mVPN Extranet Support
Device# show ip mroute 232.1.1.1
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(10.2.0.2, 232.1.1.1), 00:01:19/00:02:42, flags: sTIZ
Incoming interface: GigabitEthernet2/16, RPF nbr 10.0.1.4, RPF-MFD
Outgoing interface list:
MVRF VPN-Green, Forward/Sparse-Dense, 00:01:19/00:02:07, H
(10.1.0.1, 232.1.1.1), 00:02:19/00:03:11, flags: sT
Incoming interface: Loopback0, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list:
GigabitEthernet2/16, Forward/Sparse-Dense, 00:02:00/00:02:36, H
Device# show ip mroute 232.1.1.1
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(10.1.0.1, 232.1.1.1), 00:02:04/00:02:38, flags: sTIZ
Incoming interface: GigabitEthernet4/1, RPF nbr 10.0.2.4, RPF-MFD
Outgoing interface list:
MVRF VPN-Green, Forward/Sparse-Dense, 00:02:04/00:02:09, H
(10.2.0.2, 232.1.1.1), 00:02:04/00:03:09, flags: sT
Incoming interface: Loopback0, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list:
GigabitEthernet4/1, Forward/Sparse-Dense, 00:01:22/00:03:09, H
States in the VRF Table for VPN-Green on PE1 After Receivers in VPN-Red Join Multicast Group 228.8.8.8
The following is sample output from the showipmroute command on PE1. The sample output shows the state of the VRF table for VPN-Green on PE1 when receivers join the multicast
group 228.8.8.8.
Device# show ip mroute vrf VPN-Green 228.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.8.8.8), 00:01:43/00:02:52, RP 10.100.0.5, flags: S
Incoming interface: Ethernet3/0, RPF nbr 10.1.1.5
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 00:01:43/00:02:52
(10.1.1.200, 228.8.8.8), 00:01:15/00:03:26, flags: T
Incoming interface: Ethernet3/0, RPF nbr 10.1.1.5
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 00:01:15/00:03:19
States in the VRF Table for VPN-Green on PE1 After Receivers in VPN-Red Join Multicast Group 228.8.8.8 When PE1 Is a Switch
Configured for mVPN Extranet Support
Device# show ip mroute vrf VPN-Green 228.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.8.8.8), 00:01:43/00:02:52, RP 10.100.0.5, flags: S
Incoming interface: GigabitEthernet3/1, RPF nbr 10.1.1.5, RPF-MFD
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 00:01:43/00:02:52, H
(10.1.1.200, 228.8.8.8), 00:01:15/00:03:26, flags: T
Incoming interface: GigabitEthernet3/1, RPF nbr 10.1.1.5, RPF-MFD
Outgoing interface list:
Tunnel0, Forward/Sparse-Dense, 00:01:15/00:03:19, H
States in the VRF Table for VPN-Green on PE2 After Receivers in VPN-Red Join Multicast Group 228.8.8.8
The following is sample output from the showipmroute command on PE2. The output shows the state of the VRF table for VPN-Green on PE1 when receivers join the multicast group
228.8.8.8. The output indicates that extranet receivers in VPN-Red are receiving content from the source in VPN-Green that
is sending to multicast group 228.8.8.8. The “E” flag indicates that a (*, G) or (S, G) entry in the VRF routing table is
a source VRF entry and has extranet receiver MVRF mroute entries linked to it.
Device# show ip mroute vrf VPN-Green 228.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.8.8.8), 00:01:59/stopped, RP 10.100.0.5, flags: SE
Incoming interface: Tunnel0, RPF nbr 10.1.0.1
Outgoing interface list: Null
Extranet receivers in vrf VPN-Red:
(*, 228.8.8.8), 00:01:59/stopped, RP 10.100.0.5, OIF count: 1, flags: S
(10.1.1.200, 228.8.8.8), 00:01:31/00:02:59, flags: TE
Incoming interface: Tunnel0, RPF nbr 10.1.0.1
Outgoing interface list: Null
Extranet receivers in vrf VPN-Red:
(10.1.1.200, 228.8.8.8), 00:01:31/00:03:29, OIF count: 1, flags:
States in the VRF Table for VPN-Green on PE2 After Receivers in VPN-Red Join Multicast Group 228.8.8.8 When PE2 Is a Switch
Configured for mVPN Extranet Support
Device# show ip mroute vrf VPN-Green 228.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.8.8.8), 00:01:59/stopped, RP 10.100.0.5, flags: SE
Incoming interface: Tunnel0, RPF nbr 10.1.0.1, RPF-MFD
Outgoing interface list: Null
Extranet receivers in vrf VPN-Red:
(*, 228.8.8.8), 00:01:59/stopped, RP 10.100.0.5, OIF count: 1, flags: S
(10.1.1.200, 228.8.8.8), 00:01:31/00:02:59, flags: TE
Incoming interface: Tunnel0, RPF nbr 10.1.0.1, RPF-MFD
Outgoing interface list: Null
Extranet receivers in vrf VPN-Red:
(10.1.1.200, 228.8.8.8), 00:01:31/00:03:29, OIF count: 1, flags:
States in the VRF Table for VPN-Red on PE2 After Receivers in VPN-Red Join Multicast Group 228.8.8.8
The following is sample output from the showipmroute command on PE2. The sample output shows the state of the VRF table for VPN-Red on PE2 when receivers join the multicast group
228.8.8.8. The “using vrf VPN-Green” field indicates that VPN-Red is using unicast routing information from VPN-Green to determine
the RPF interface through which the source is reachable.
Device# show ip mroute vrf VPN-Red 228.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.8.8.8), 00:02:00/stopped, RP 10.100.0.5, flags: S
Incoming interface: Tunnel0, RPF nbr 10.1.0.1, using vrf VPN-Green
Outgoing interface list:
Ethernet9/0, Forward/Sparse-Dense, 00:02:00/00:02:34
(10.1.1.200, 228.8.8.8), 00:01:32/00:03:28, flags:
Incoming interface: Tunnel0, RPF nbr 10.1.0.1, using vrf VPN-Green
Outgoing interface list:
Ethernet9/0, Forward/Sparse-Dense, 00:01:32/00:03:01
States in the VRF Table for VPN-Red on PE2 After Receivers in VPN-Red Join Multicast Group 228.8.8.8 When PE2 Is a Switch
Configured for mVPN Extranet Support
Device# show ip mroute vrf VPN-Red 228.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.8.8.8), 00:02:00/stopped, RP 10.100.0.5, flags: S
Incoming interface: Tunnel0, RPF nbr 10.1.0.1, using vrf VPN-Green, RPF-MFD
Outgoing interface list:
GigabitEthernet9/1, Forward/Sparse-Dense, 00:02:00/00:02:34, H
(10.1.1.200, 228.8.8.8), 00:01:32/00:03:28, flags:
Incoming interface: Tunnel0, RPF nbr 10.1.0.1, using vrf VPN-Green, RPF-MFD
Outgoing interface list:
GigabitEthernet9/1, Forward/Sparse-Dense, 00:01:32/00:03:01, H
Example: Configuring the Receiver VRF on the Source PE Router - Option 2
The following example shows the configurations for PE1, the source PE router, and PE2, the receiver PE router, in the figure.
In this example, mVPN extranet services are supported between VPN-Green and VPN-Red by configuring the receiver MVRF for VPN-Red
on PE1, the source PE router. The MVRF configuration for VPN-Red is configured to import routes from the MVRF for VPN-Green
to the MVRF for VPN-Red.
Figure 6. Topology for mVPN Extranet Support Option 2 Configuration Example
States in the Global Table on PE1 and PE2 for the MDT Default Group 232.3.3.3
The following are sample outputs from the showipmroute command on PE1 and PE2. The sample outputs show the global table for the MDT default group 232.3.3.3 on PE1 and PE2.
PE1# show ip mroute 232.3.3.3
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(10.1.0.1, 232.3.3.3), 00:46:27/00:03:27, flags: sT
Incoming interface: Loopback0, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0, Forward/Sparse-Dense, 00:45:17/00:02:44
(10.2.0.2, 232.3.3.3), 00:45:17/00:02:57, flags: sTIZ
Incoming interface: Ethernet0/0, RPF nbr 224.0.1.4
Outgoing interface list:
MVRF VPN-Red, Forward/Sparse-Dense, 00:45:17/00:01:09
PE2# show ip mroute 232.3.3.3
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(10.1.0.1, 232.3.3.3), 00:45:08/00:02:37, flags: sTIZ
Incoming interface: Ethernet1/0, RPF nbr 224.0.2.4
Outgoing interface list:
MVRF VPN-Red, Forward/Sparse-Dense, 00:45:08/00:01:27
(10.2.0.2, 232.3.3.3), 00:46:19/00:03:07, flags: sT
Incoming interface: Loopback0, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet1/0, Forward/Sparse-Dense, 00:45:08/00:02:49
States in the Global Table on PE1 and PE2 for the MDT Default Group 232.3.3.3 When PE1 and PE2 Are Switches Configured for
mVPN Extranet Support
The following are sample outputs from the showipmroute on PE1 and PE2, when PE1 and PE2 are switches that have been configured to support mVPN extranet services. The sample output
from the showipmroute command shows the global table for the MDT default group 232.3.3.3 on PE1 and PE2. In the output, the “RPF-MFD” flag indicates
that a multicast flow is completely hardware switched and “H” flag indicates that the flow is being hardware switched on an
outgoing interface.
Device# show ip mroute 232.3.3.3
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(10.1.0.1, 232.3.3.3), 00:46:27/00:03:27, flags: sT
Incoming interface: Loopback0, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list:
GigabitEthernet2/16, Forward/Sparse-Dense, 00:45:17/00:02:44, H
(10.2.0.2, 232.3.3.3), 00:45:17/00:02:57, flags: sTIZ
Incoming interface: GigabitEthernet2/16, RPF nbr 224.0.1.4, RPF-MFD
Outgoing interface list:
MVRF VPN-Red, Forward/Sparse-Dense, 00:45:17/00:01:09, H
Device# show ip mroute 232.3.3.3
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(10.1.0.1, 232.3.3.3), 00:45:08/00:02:37, flags: sTIZ
Incoming interface: GigabitEthernet4/1, RPF nbr 224.0.2.4, RPF-MFD
Outgoing interface list:
MVRF VPN-Red, Forward/Sparse-Dense, 00:45:08/00:01:27, H
(10.2.0.2, 232.3.3.3), 00:46:19/00:03:07, flags: sT
Incoming interface: Loopback0, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list:
GigabitEthernet4/1, Forward/Sparse-Dense, 00:45:08/00:02:49, H
States in the VRF Table for VPN-Green on PE1 After Receivers in VPN-Red Join Multicast Group 228.8.8.8
The following is sample output from the showipmroute command on PE1. The sample output shows the state of the VRF table for VPN-Green on PE1 when receivers join the multicast
group 228.8.8.8. The output indicates that extranet receivers in VPN-Red are receiving content from a source in VPN-Green
that is sending to multicast group 228.8.8.8. The “E” flag in the output indicates that a (*, G) or (S, G) entry in the VRF
routing table is a source VRF entry and has extranet receiver MVRF mroute entries linked to it.
Device# show ip mroute vrf VPN-Green 228.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.8.8.8), 00:01:38/stopped, RP 10.100.0.5, flags: SE
Incoming interface: Ethernet3/0, RPF nbr 10.1.1.5
Outgoing interface list: Null
Extranet receivers in vrf VPN-Red:
(*, 228.8.8.8), 00:01:38/stopped, RP 10.100.0.5, OIF count: 1, flags: S
(10.1.1.200, 228.8.8.8), 00:00:05/00:02:54, flags: TE
Incoming interface: Ethernet3/0, RPF nbr 10.1.1.5
Outgoing interface list: Null
Extranet receivers in vrf VPN-Red:
(10.1.1.200, 228.8.8.8), 00:00:05/stopped, OIF count: 1, flags:
States in the VRF Table for VPN-Green on PE1 After Receivers in VPN-Red Join Multicast Group 228.8.8.8 When PE1 Is a Switch
Configured for mVPN Extranet Support
The following are sample outputs from the showipmroute on PE1, when PE1 is a Catalyst 6500 series switch configured to support extranet MVPN services. The sample output from the
showipmroute command shows the state of the VRF table for VPN-Green on PE1 when receivers join the multicast group 228.8.8.8. The sample
output indicates that extranet receivers in VPN-Red are receiving content from a source in VPN-Green that is sending to multicast
group 228.8.8.8.
Device# show ip mroute vrf VPN-Green 228.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.8.8.8), 00:01:38/stopped, RP 10.100.0.5, flags: SE
Incoming interface: GigabitEthernet3/1, RPF nbr 10.1.1.5, RPF-MFD
Outgoing interface list: Null
Extranet receivers in vrf VPN-Red:
(*, 228.8.8.8), 00:01:38/stopped, RP 10.100.0.5, OIF count: 1, flags: S
(10.1.1.200, 228.8.8.8), 00:00:05/00:02:54, flags: TE
Incoming interface: GigabitEthernet3/1, RPF nbr 10.1.1.5, RPF-MFD
Outgoing interface list: Null
Extranet receivers in vrf VPN-Red:
(10.1.1.200, 228.8.8.8), 00:00:05/stopped, OIF count: 1, flags:
States in the VRF Table for VPN-Red on PE1 After Receivers in VPN-Red Join Multicast Group 228.8.8.8
The following is sample output from the showipmroute command on PE1. The sample output shows the state of the VRF table for VPN-Red on PE1 when receivers join the multicast group
228.8.8.8. The “using vrf VPN-Green” field indicates that VPN-Red is using unicast routing information from VPN-Green to determine
the RPF interface through which the source is reachable.
Device# show ip mroute vrf VPN-Red 228.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.8.8.8), 00:01:45/stopped, RP 10.100.0.5, flags: S
Incoming interface: Ethernet3/0, RPF nbr 10.1.1.5, using vrf VPN-Green
Outgoing interface list:
Tunnel2, Forward/Sparse-Dense, 00:01:45/00:02:49
(10.1.1.200, 228.8.8.8), 00:00:12/00:03:27, flags:
Incoming interface: Ethernet3/0, RPF nbr 10.1.1.5, using vrf VPN-Green
Outgoing interface list:
Tunnel2, Forward/Sparse-Dense, 00:00:12/00:03:18
States in the VRF Table for VPN-Red on PE1 After Receivers in VPN-Red Join Multicast Group 228.8.8.8 When PE1 Is a Switch
Configured for mVPN Extranet Support
Device# show ip mroute vrf VPN-Red 228.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.8.8.8), 00:01:45/stopped, RP 10.100.0.5, flags: S
Incoming interface: GigabitEthernet3/1, RPF nbr 10.1.1.5, using vrf VPN-Green, RPF-MFD
Outgoing interface list:
Tunnel2, Forward/Sparse-Dense, 00:01:45/00:02:49, H
(10.1.1.200, 228.8.8.8), 00:00:12/00:03:27, flags:
Incoming interface: GigabitEthernet3/1, RPF nbr 10.1.1.5, using vrf VPN-Green, RPF-MFD
Outgoing interface list:
Tunnel2, Forward/Sparse-Dense, 00:00:12/00:03:18, H
States in the VRF Table for VPN-Red on PE2 After Receivers in VPN-Red Join Multicast Group 228.8.8.8
The following is sample output from the showipmroute command on PE2. The sample output shows the VRF table for VPN-Red on PE2 when receivers join the multicast group 228.8.8.8.
PE2# show ip mroute vrf VPN-Red 228.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.8.8.8), 00:00:28/stopped, RP 10.100.0.5, flags: S
Incoming interface: Tunnel1, RPF nbr 10.1.0.1
Outgoing interface list:
Ethernet9/0, Forward/Sparse-Dense, 00:00:28/00:03:02
(10.1.1.200, 228.8.8.8), 00:00:00/00:03:29, flags:
Incoming interface: Tunnel1, RPF nbr 10.1.0.1
Outgoing interface list:
Ethernet9/0, Forward/Sparse-Dense, 00:00:00/00:03:29
States in the VRF Table for VPN-Red on PE2 After Receivers in VPN-Red Join Multicast Group 228.8.8.8 When PE2 Is a Switch
Configured for mVPN Extranet Support
PE2# show ip mroute vrf VPN-Red 228.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.8.8.8), 00:00:28/stopped, RP 10.100.0.5, flags: S
Incoming interface: Tunnel1, RPF nbr 10.1.0.1, RPF-MFD
Outgoing interface list:
GigabitEthernet9/1, Forward/Sparse-Dense, 00:00:28/00:03:02, H
(10.1.1.200, 228.8.8.8), 00:00:00/00:03:29, flags:
Incoming interface: Tunnel1, RPF nbr 10.1.0.1, RPF-MFD
Outgoing interface list:
GigabitEthernet9/1, Forward/Sparse-Dense, 00:00:00/00:03:29, H
Example: Displaying Statistics for mVPN Extranet Support
This example is a stand alone example and does not refer to any other technologies.
The MFIB-based implementation of IP multicast updates counters in source MVRF mroute entries for mVPN extranet. Counters in
the source MVRF can be displayed using Cisco IOS commands. Counters in the receiver MVRF mroute entries will remain zero.
Use the show ip mroute command to determine the source and receiver MVRFs. The following sample output shows that VRF blue is the source MVRF and
VRF red is the receiver MVRF:
Device# show ip mroute vrf blue 228.1.1.1
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.1.1.1), 00:05:48/stopped, RP 202.100.0.5, flags: SE
Incoming interface: Ethernet3/0, RPF nbr 200.1.1.5
Outgoing interface list: Null
Extranet receivers in vrf red:
(*, 228.1.1.1), 00:05:48/stopped, RP 202.100.0.5, OIF count: 1, flags: S
(220.1.1.200, 228.1.1.1), 00:02:42/00:02:09, flags: TE
Incoming interface: Ethernet3/0, RPF nbr 200.1.1.5
Outgoing interface list: Null
Extranet receivers in vrf red:
(220.1.1.200, 228.1.1.1), 00:02:42/stopped, OIF count: 1, flags: T
Device# show ip mroute vrf red 228.1.1.1
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 228.1.1.1), 00:05:55/stopped, RP 202.100.0.5, flags: S
Incoming interface: Ethernet3/0, RPF nbr 200.1.1.5, using vrf blue
Outgoing interface list:
Tunnel16, Forward/Sparse-Dense, 00:05:55/00:03:26
(220.1.1.200, 228.1.1.1), 00:02:49/stopped, flags: T
Incoming interface: Ethernet3/0, RPF nbr 200.1.1.5, using vrf blue
Outgoing interface list:
Tunnel16, Forward/Sparse-Dense, 00:02:49/00:03:26
Use the show ip mfib vrf vrf-name command, with the source MVRF for the vrf-name argument, to display statistics.
The following example shows statistics for the source MVRF blue. Inspect the output to ensure that the forwarding statistics
in the source MVRF MFIB are correct and that the A and F flags are set in the source MVRF. Notice that there is no indication
of extranet forwarding in the MFIB.
Device# show ip mfib vrf blue 228.1.1.1
Entry Flags: C - Directly Connected, S - Signal, IA - Inherit A
flag,
ET - Data Rate Exceeds Threshold, K - Keepalive
DDE - Data Driven Event, HW - Hardware Installed
I/O Item Flags: IC - Internal Copy, NP - Not platform switched,
NS - Negate Signalling, SP - Signal Present,
A - Accept, F - Forward, RA - MRIB Accept, RF - MRIB
Forward,
MA - MFIB Accept
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kbits per
second
Other counts: Total/RPF failed/Other drops
I/O Item Counts: FS Pkt Count/PS Pkt Count
VRF blue
(*,228.1.1.1) Flags: C
SW Forwarding: 1/0/100/0, Other: 0/0/0
Ethernet3/0 Flags: A
Tunnel16, MDT/239.3.3.3 Flags: F
Pkts: 1/0
(220.1.1.200,228.1.1.1) Flags:
SW Forwarding: 37/0/100/0, Other: 0/0/0
Ethernet3/0 Flags: A NS
Tunnel16, MDT/239.3.3.3 Flags: F
Pkts: 37/0
The following example shows the following information for the receiver MVRF red:
There are no forwarding statistics in the receiver MVRF MFIB because these statistics are collected in the source MVRF.
The A and F flags are not set because these flags are only set in the source MVRF for mVPN extranet.
There is no indication of extranet forwarding in the MFIB.
Note
The NS flag in the output is present for the purpose of receiving PIM control traffic in the receiver MVRF.
Device# show ip mfib vrf red 228.1.1.1
Entry Flags: C - Directly Connected, S - Signal, IA - Inherit A
flag,
ET - Data Rate Exceeds Threshold, K - Keepalive
DDE - Data Driven Event, HW - Hardware Installed
I/O Item Flags: IC - Internal Copy, NP - Not platform switched,
NS - Negate Signalling, SP - Signal Present,
A - Accept, F - Forward, RA - MRIB Accept, RF - MRIB
Forward,
MA - MFIB Accept
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kbits per
second
Other counts: Total/RPF failed/Other drops
I/O Item Counts: FS Pkt Count/PS Pkt Count
VRF red
(*,228.1.1.1) Flags: C
SW Forwarding: 0/0/0/0, Other: 0/0/0
Tunnel16, MDT/239.3.3.3 Flags: NS
(220.1.1.200,228.1.1.1) Flags:
SW Forwarding: 0/0/0/0, Other: 0/0/0
Tunnel16, MDT/239.3.3.3 Flags: NS
You can also use the show ip mroute count command to display the mVPN extranet statistics. However, we recommend that you use the show ip mfib command instead. If you use the show ip mroute countcommand to display statistics, inspect the output to ensure that the forwarding statistics in the source MVRF are correct
and that there are no forwarding statistics in the receiver MVRF.
The following sample output from the show ip mroute count command shows statistics for the source MVRF blue:
Device# show ip mroute vrf blue 228.1.1.1 count
Use "show ip mfib count" to get better response time for a large number of
mroutes.
IP Multicast Statistics
3 routes using 1354 bytes of memory
2 groups, 0.50 average sources per group
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)
Group: 228.1.1.1, Source count: 1, Packets forwarded: 38, Packets received: 38
RP-tree: Forwarding: 1/0/100/0, Other: 1/0/0
Source: 220.1.1.200/32, Forwarding: 37/0/100/0, Other: 37/0/0
The following sample output from the show ip mroute count command is for the receiver MVRF red:
Device# show ip mroute vrf red 228.1.1.1 count
Use "show ip mfib count" to get better response time for a large number of
mroutes.
IP Multicast Statistics
3 routes using 1672 bytes of memory
2 groups, 0.50 average sources per group
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)
Group: 228.1.1.1, Source count: 1, Packets forwarded: 0, Packets received: 0
RP-tree: Forwarding: 0/0/0/0, Other: 0/0/0
Source: 220.1.1.200/32, Forwarding: 0/0/0/0, Other: 0/0/0
Example: Configuring RPF for mVPN Extranet Support Using Static Mroutes
The following example shows how to configure the RPF lookup originating in VPN-Red to be resolved in VPN-Green using the
static mroute 192.168.1.1:
ip mroute vrf VPN-Red 192.168.1.1 255.255.255.255 fallback-lookup vrf VPN-Green
Example: Configuring Group-Based VRF Selection Policies with mVPN Extranet Support
The following example shows how to use group-based VRF selection policies to configure RPF lookups originating in VPN-Green
to be performed in VPN-Red for group addresses that match ACL 1 and to be performed in VPN-Blue for group addresses that match
ACL 2.
Basic IP multicast concepts, configuration tasks, and examples
“Configuring Basic IP Multicast Routing” module
IP multicast overview
“IP Multicast Routing Technology Overview” module
MPLS Layer 3 VPN concepts and configuration tasks
“Configuring MPLS Layer 3 VPN” module
Multicast VPN concepts, configuration tasks, and examples
“Configuring Multicast VPN” module
Feature History for mVPN Extranet Support
This table provides release and related information for the features explained in this module.
These features are available in all the releases subsequent to the one they were introduced in, unless noted otherwise.
Release
Feature
Feature Information
Cisco IOS XE Amsterdam 17.1.1
mVPN Extranet Support
The mVPN extranet support feature enables service providers to distribute IP multicast content originated from one enterprise
site to other enterprise sites. This feature enables service providers to offer the next generation of flexible extranet services,
helping to enable business partnerships between different enterprise VPN customers.
Use the Cisco Feature Navigator to find information about platform and software image support. To access Cisco Feature Navigator,
go to https://cfnng.cisco.com/
Feedback