Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 02-H3C_Multicast_VPN_Configuration_Examples | 217.74 KB |
|
|
|
H3C Multicast VPN Configuraton Examples |
|
|
|
|
|
|
Software version: Release 7951P01
Document version: 6W100-20200625
Copyright © 2020 New H3C Technologies Co., Ltd. All rights reserved.
No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.
The information in this document is subject to change without notice.
Contents
General restrictions and guidelines
Example: Configuring intra-AS MDT-based MVPN
Assigning IP addresses to interfaces
Configuring routing and basic MPLS L3VPN
Configuring multicast routing and MDT-based MVPN
Example: Configuring inter-AS option A MDT-based MVPN
Assigning IP addresses to interfaces
Configuring routing and basic MPLS L3VPN
Configuring multicast routing and inter-AS option A MDT-based MVPN
Example: Configuring inter-AS option C MDT-based MVPN
Assigning IP addresses to interfaces
Configuring routing and basic MPLS L3VPN
Configuring multicast routing and inter-AS option A MDT-based MVPN
Introduction
This document provides multicast VPN configuration examples.
Prerequisites
The configuration examples in this document were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.
This document assumes that you have basic knowledge of multicast VPN.
General restrictions and guidelines
Multicast VPN is supported only on CSPEX and CEPC cards.
Example: Configuring intra-AS MDT-based MVPN
Network configuration
· Customer A has two branches that connect to the MPLS L3VPN network of a service provider.
· PIM-SM runs within the two branches.
· The multicast source and the receiver host are in different branches.
Configure intra-AS MDT-based MVPN so that the receiver host can receive the multicast data from the source.
Table 1 Interface and IP address assignment
|
Device |
Interface |
IP address |
Device |
Interface |
IP address |
|
S 1 |
— |
10.11.3.2/24 |
PE 2 |
GE3/1/2 |
192.168.2.2/24 |
|
PE 1 |
GE3/1/2 |
192.168.1.2/24 |
PE 2 |
GE3/1/1 |
10.11.2.1/24 |
|
PE 1 |
GE3/1/1 |
10.11.1.1/24 |
PE 2 |
Loop1 |
1.1.1.2/32 |
|
PE 1 |
Loop1 |
1.1.1.1/32 |
CE a1 |
GE3/1/1 |
10.11.3.1/24 |
|
P |
GE3/1/1 |
192.168.1.1/24 |
CE a1 |
GE3/1/2 |
10.11.1.2/24 |
|
P |
GE3/1/2 |
192.168.2.1/24 |
CE a1 |
Loop0 |
2.2.2.2/32 |
|
P |
Loop1 |
3.3.3.3/32 |
CE a2 |
GE3/1/2 |
10.11.4.1/24 |
|
R 1 |
— |
10.11.4.2/24 |
CE a2 |
GE3/1/1 |
10.11.2.2/24 |
Analysis
To meet the network requirement, you must run PIM on the devices of the public network, and configure MDT-based MVPN on each PE. In addition, make sure the PIM protocol on the public network is independent from the PIM protocol for the VPN instance.
Restrictions and guidelines
The MTI interfaces take effect only after the default-group and the MVPN source interface are specified and the MVPN source interface obtains the public IP address.
You must enable the same PIM mode on all interfaces that belong to the same VPN instance (including the interfaces associated with the VPN instance on the PEs).
You must specify the same default-group for the same VPN instance on different PEs.
The IP address of the MVPN source interface must be the same as the source address used for establishing BGP peer relationship. Otherwise, correct routing information cannot be obtained.
Procedures
Assigning IP addresses to interfaces
# Assign an IP address and subnet mask to each interface on CE a1, as shown in Table 1.
<CEa1> system-view
[CEa1] interface gigabitethernet 3/1/1
[CEa1-GigabitEthernet3/1/1] ip address 10.11.3.1 24
[CEa1-GigabitEthernet3/1/1] quit
[CEa1] interface loopback 0
[CEa1-LoopBack0] ip address 2.2.2.2 32
[CEa1-LoopBack0] quit
[CEa1] interface gigabitethernet 3/1/2
[CEa1-GigabitEthernet3/1/2] ip address 10.11.1.2 24
[CEa1-GigabitEthernet3/1/2] quit
# Configure PE 1, P, PE 2, and CE a2 in the same way CE a1 is configured. (Details not shown.)
Configuring routing and basic MPLS L3VPN
# Configure a unicast routing protocol and basic MPLS VPN on all devices so that all devices are interoperable at the network layer. (Details not shown.) For more information about configuring basic MPLS VPN, see H3C CR16000-F Routers MPLS Configuration Guide.
Configuring multicast routing and MDT-based MVPN
1. Enable IP multicast routing on the public network, and enable PIM-SM on the public network interfaces (including Loopback interfaces).
# On PE 1, enable IP multicast routing, and enable PIM-SM on the public network interfaces.
<PE1> system-view
[PE1] multicast routing
[PE1-mrib] quit
[PE1] interface gigabitethernet 3/1/2
[PE1-GigabitEthernet3/1/2] pim sm
[PE1-GigabitEthernet3/1/2] quit
[PE1] interface loopback 1
[PE1-LoopBack1] pim sm
[PE1-LoopBack1] quit
# On P, enable IP multicast routing, and enable PIM-SM on the public network interfaces.
<P> system-view
[P] multicast routing
[P-mrib] quit
[P] interface gigabitethernet 3/1/1
[P-GigabitEthernet3/1/1] pim sm
[P-GigabitEthernet3/1/1] quit
[P] interface gigabitethernet 3/1/2
[P-GigabitEthernet3/1/2] pim sm
[P-GigabitEthernet3/1/2] quit
[P] interface loopback 1
[P-LoopBack1] pim sm
[P-LoopBack1] quit
# Configure Loopback 1 as a C-BSR and a C-RP.
[P] pim
[P-pim] c-bsr 3.3.3.3
[P-pim] c-rp 3.3.3.3
[P-pim] quit
# On PE 2, enable IP multicast routing, and enable PIM-SM on the public network interfaces.
<PE2> system-view
[PE2] multicast routing
[PE2-mrib] quit
[PE2] interface gigabitethernet 3/1/2
[PE2-GigabitEthernet3/1/2] pim sm
[PE2-GigabitEthernet3/1/2] quit
[PE2] interface loopback 1
[PE2-LoopBack1] pim sm
[PE2-LoopBack1] quit
2. Enable IP multicast routing for the VPN instance, enable PIM-SM on the private network interfaces, and enable IGMP on interfaces that have receiver hosts attached.
# On CE a1, enable IP multicast routing, and enable PIM-SM on each interface.
<CEa1> system-view
[CEa1] multicast routing
[CEa1-mrib] quit
[CEa1] interface gigabitethernet 3/1/1
[CEa1-GigabitEthernet3/1/1] pim sm
[CEa1-GigabitEthernet3/1/1] quit
[CEa1] interface gigabitethernet 3/1/2
[CEa1-GigabitEthernet3/1/2] pim sm
[CEa1-GigabitEthernet3/1/2] quit
[CEa1] interface loopback 0
[CEa1-LoopBack0] pim sm
[CEa1-LoopBack0] quit
# Configure Loopback 0 as a C-BSR and a C-RP.
[CEa1] pim
[CEa1-pim] c-bsr 2.2.2.2
[CEa1-pim] c-rp 2.2.2.2
[CEa1-pim] quit
# On CE a2, enable IP multicast routing, enable PIM-SM on GigabitEthernet 3/1/1, and enable IGMP on the receiver-side interface GigabitEthernet 3/1/2.
<CEa2> system-view
[CEa2] multicast routing
[CEa2-mrib] quit
[CEa2] interface gigabitethernet 3/1/1
[CEa2-GigabitEthernet3/1/1] pim sm
[CEa2-GigabitEthernet3/1/1] quit
[CEa2] interface gigabitethernet 3/1/2
[CEa2-GigabitEthernet3/1/2] igmp enable
[CEa2-GigabitEthernet3/1/2] quit
# On PE 1, create a VPN instance named customerA.
[PE1] ip vpn-instance customerA
[PE1-vpn-instance-customerA] route-distinguisher 100:1
[PE1-vpn-instance-customerA] vpn-target 111:1
[PE1-vpn-instance-customerA] quit
# Associate GigabitEthernet 3/1/1 with VPN instance customerA.
[PE1] interface gigabitethernet 3/1/1
[PE1-GigabitEthernet3/1/1] ip binding vpn-instance customerA
[PE1-GigabitEthernet3/1/1] quit
# Enable IP multicast routing for VPN instance customerA.
[PE1] multicast routing vpn-instance customerA
[PE1-mrib-customerA] quit
# Enable PIM-SM on GigabitEthernet 3/1/1.
[PE1] interface gigabitethernet 3/1/1
[PE1-GigabitEthernet3/1/1] pim sm
[PE1-GigabitEthernet3/1/1] quit
# On PE 2, create a VPN instance named customerA.
[PE2] ip vpn-instance customerA
[PE2-vpn-instance-customerA] route-distinguisher 100:1
[PE2-vpn-instance-customerA] vpn-target 111:1
[PE2-vpn-instance-customerA] quit
# Associate GigabitEthernet 3/1/1 with VPN instance customerA.
[PE2] interface gigabitethernet 3/1/1
[PE2-GigabitEthernet3/1/1] ip binding vpn-instance customerA
[PE2-GigabitEthernet3/1/1] quit
# Enable IP multicast routing for VPN instance customerA.
[PE2] multicast routing vpn-instance customerA
[PE2-mrib-customerA] quit
# Enable PIM-SM on GigabitEthernet 3/1/1.
[PE2] interface gigabitethernet 3/1/1
[PE2-GigabitEthernet3/1/1] pim sm
[PE2-GigabitEthernet3/1/1] quit
3. Configure the MVPN for the VPN instance:
# On PE 1, create an MDT-based MVPN for VPN instance customerA.
[PE1] multicast-vpn vpn-instance customerA mode mdt
# Create an MVPN IPv4 address family for VPN instance customerA.
[PE1-mvpn-customerA] address-family ipv4
# Specify the default group, MVPN source interface, and data group range for VPN instance customerA.
[PE1-mvpn-customerA-ipv4] default-group 239.1.1.1
[PE1-mvpn-customerA-ipv4] source loopback 1
[PE1-mvpn-customerA-ipv4] data-group 225.2.2.0 28
[PE1-mvpn-customerA-ipv4] quit
[PE1-mvpn-customerA] quit
# On PE 2, create an MDT-based MVPN for VPN instance customerA.
[PE2] multicast-vpn vpn-instance customerA mode mdt
# Create an MVPN IPv4 address family for VPN instance customerA.
[PE2-mvpn-customerA] address-family ipv4
# Specify the default group, MVPN source interface, and data group range for VPN instance customerA.
[PE2-mvpn-customerA-ipv4] default-group 239.1.1.1
[PE2-mvpn-customerA-ipv4] source loopback 1
[PE2-mvpn-customerA-ipv4] data-group 225.2.2.0 28
[PE2-mvpn-customerA-ipv4] quit
[PE2-mvpn-customerA] quit
Verifying the configuration
# Verify the establishment of the default-MDT for the public network on PEs and P. The following example shows PIM routing table for the public network on P.
[P] display pim routing-table
Total 1 (*, G) entry; 2 (S, G) entry
(*, 239.1.1.1)
RP: 3.3.3.3 (local)
Protocol: pim-sm, Flag: SPT LOC ACT
UpTime: 02:54:43
Upstream interface: Register
Upstream neighbor: NULL
RPF prime neighbor: NULL
Downstream interface(s) information:
Total number of downstreams: 2
1: GigabitEthernet3/1/1
Protocol: pim-sm, UpTime: 02:54:43, Expires: -
2: GigabitEthernet3/1/2
Protocol: pim-sm, UpTime: 02:33:57, Expires: -
(1.1.1.1, 239.1.1.1)
RP: 3.3.3.3 (local)
Protocol: pim-sm, Flag: SPT LOC ACT
UpTime: 01:57:13
Upstream interface: GigabitEthernet3/1/1
Upstream neighbor: 192.168.1.2
RPF prime neighbor: 192.168.1.2
Downstream interface(s) information: None
(1.1.1.2, 239.1.1.1)
RP: 3.3.3.3 (local)
Protocol: pim-sm, Flag: SPT LOC ACT
UpTime: 01:57:13
Upstream interface: GigabitEthernet3/1/2
Upstream neighbor: 192.168.2.2
RPF prime neighbor: 192.168.2.2
Downstream interface(s) information: None
The output shows that an RPT for (*, 239.1.1.1), an SPT for (1.1.1.1, 239.1.1.1), and an SPT for (1.1.1.2, 239.1.1.1) have been established on the public network. The RPT and SPTs constitute the default-MDT for the public network.
Configuration files
· PE 1:
#
ip vpn-instance customerA
route-distinguisher 100:1
vpn-target 100:1 import-extcommunity
vpn-target 100:1 export-extcommunity
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
pim sm
#
interface GigabitEthernet3/1/1
ip binding vpn-instance customerA
ip address 10.11.1.1 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip address 192.168.1.2 255.255.255.0
pim sm
#
multicast routing
#
multicast routing vpn-instance customerA
#
multicast-vpn vpn-instance customerA mode mdt
address-family ipv4
source LoopBack1
default-group 239.1.1.1
data-group 225.1.1.0 255.255.255.240
#
· PE 2:
#
ip vpn-instance customerA
route-distinguisher 100:1
vpn-target 100:1 import-extcommunity
vpn-target 100:1 export-extcommunity
#
interface LoopBack1
ip address 1.1.1.2 255.255.255.255
pim sm
#
interface GigabitEthernet3/1/1
ip binding vpn-instance customerA
ip address 10.11.2.1 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip address 192.168.2.2 255.255.255.0
pim sm
#
multicast routing
#
multicast routing vpn-instance customerA
#
multicast-vpn vpn-instance customerA mode mdt
address-family ipv4
source LoopBack1
default-group 239.1.1.1
data-group 225.1.1.0 255.255.255.240
#
· P:
#
interface LoopBack1
ip address 3.3.3.3 255.255.255.255
pim sm
#
interface GigabitEthernet3/1/1
ip address 192.168.1.1 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip address 192.168.2.1 255.255.255.0
pim sm
#
multicast routing
#
pim
c-bsr 3.3.3.3
c-rp 3.3.3.3
#
· CE a1:
#
interface LoopBack0
ip address 2.2.2.2 255.255.255.255
pim sm
#
interface GigabitEthernet3/1/1
ip address 10.11.3.1 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip address 10.11.1.2 255.255.255.0
pim sm
#
multicast routing
#
pim
c-bsr 2.2.2.2
c-rp 2.2.2.2
#
· CE a2:
#
interface GigabitEthernet3/1/1
ip address 10.11.2.2 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip address 10.11.4.1 255.255.255.0
igmp enable
#
multicast routing
#
Example: Configuring inter-AS option A MDT-based MVPN
Network configuration
As shown in Figure 2:
· Customer A has two branches that separately connect to AS 100 and AS 200.
· ASBR-PE 1 and ASBR-PE 2 are interconnected by using the inter-AS option A solution.
· PIM-SM runs within the two branches.
· The multicast source and the receiver host are in different branches.
Configure inter-AS option A MDT-based MVPN so that the receiver host can receive the multicast data from the source.
Table 2 Interface and IP address assignment
|
Device |
Interface |
IP address |
Device |
Interface |
IP address |
|
S 1 |
— |
10.11.3.2/24 |
R 1 |
— |
10.11.4.2/24 |
|
PE 1 |
GE3/1/1 |
192.168.1.2/24 |
ASBR-PE 2 |
GE3/1/1 |
192.168.2.2/24 |
|
PE 1 |
GE3/1/2 |
10.11.1.1/24 |
ASBR-PE 2 |
GE3/1/2 |
192.168.3.2/24 |
|
PE 1 |
Loop1 |
1.1.1.1/32 |
ASBR-PE 2 |
Loop1 |
1.1.1.3/32 |
|
ASBR-PE 1 |
GE3/1/1 |
192.168.1.1/24 |
ASBR-PE 2 |
Loop2 |
22.22.22.22/32 |
|
ASBR-PE 1 |
GE3/1/2 |
192.168.2.1/24 |
PE 2 |
GE3/1/1 |
192.168.3.1/24 |
|
ASBR-PE 1 |
Loop1 |
1.1.1.2/32 |
PE 2 |
GE3/1/2 |
10.11.2.1/24 |
|
ASBR-PE 1 |
Loop2 |
11.11.11.11/32 |
PE 2 |
Loop1 |
1.1.1.4/32 |
|
CE a1 |
GE3/1/1 |
10.11.3.1/24 |
CE a2 |
GE3/1/1 |
10.11.2.2/24 |
|
CE a1 |
GE3/1/2 |
10.11.1.2/24 |
CE a2 |
GE3/1/2 |
10.11.4.1/24 |
|
CE a1 |
Loopback 0 |
2.2.2.2/32 |
|
|
|
Analysis
To meet the network requirement, you must create a separate MDT-based MVPN for each AS.
Restrictions and guidelines
You must enable the same PIM mode for all interfaces that belong to the same VPN instance (including the interface associated with the VPN instance). You may enable different PIM modes for the public network in different ASs.
You must specify the same default-group for the same VPN instance in the same AS. You may specify different default-groups for the same VPN instance in different ASs.
Procedures
Assigning IP addresses to interfaces
# Assign an IP address and subnet mask to each interface on CE a1, as shown in Table 2.
<CEa1> system-view
[CEa1] interface gigabitethernet 3/1/1
[CEa1-GigabitEthernet3/1/1] ip address 10.11.3.1 24
[CEa1-GigabitEthernet3/1/1] quit
[CEa1] interface loopback 0
[CEa1-LoopBack0] ip address 2.2.2.2 32
[CEa1-LoopBack0] quit
[CEa1] interface gigabitethernet 3/1/2
[CEa1-GigabitEthernet3/1/2] ip address 10.11.1.2 24
[CEa1-GigabitEthernet3/1/2] quit
# Configure PE 1, ASBR-PE 1, ASBR-PE2, PE 2, and CE a2 in the same way CE a1 is configured. (Details not shown.)
Configuring routing and basic MPLS L3VPN
# Configure a unicast routing protocol and MPLS L3VPN inter-AS option A on all devices so that all devices in the ASs are interoperable at the network layer. (Details not shown) For more information about configuring basic MPLS VPN, see H3C CR16000-F Routers MPLS Configuration Guide.
Configuring multicast routing and inter-AS option A MDT-based MVPN
1. Enable IP multicast routing on the public network, and enable PIM-SM on the public network interfaces (including Loopback interfaces).
# On PE 1, enable IP multicast routing, and enable PIM-SM on the public network interfaces.
<PE1> system-view
[PE1] multicast routing
[PE1-mrib] quit
[PE1] interface gigabitethernet 3/1/1
[PE1-GigabitEthernet3/1/1] pim sm
[PE1-GigabitEthernet3/1/1] quit
[PE1] interface loopback 1
[PE1-LoopBack1] pim sm
[PE1-LoopBack1] quit
# On ASBR-PE 1, enable IP multicast routing, and enable PIM-SM on the public network interfaces.
<ASBR-PE1> system-view
[ASBR-PE1] multicast routing
[ASBR-PE1-mrib] quit
[ASBR-PE1] interface gigabitethernet 3/1/1
[ASBR-PE1-GigabitEthernet3/1/1] pim sm
[ASBR-PE1-GigabitEthernet3/1/1] quit
[ASBR-PE1] interface loopback 1
[ASBR-PE1-LoopBack1] pim sm
[ASBR-PE1-LoopBack1] quit
[ASBR-PE1] interface loopback 2
[ASBR-PE1-LoopBack2] pim sm
[ASBR-PE1-LoopBack2] quit
# Configure Loopback 2 as a C-BSR and a C-RP.
[ASBR-PE1] pim
[ASBR-PE1-pim] c-bsr 11.11.11.11
[ASBR-PE1-pim] c-rp 11.11.11.11
[ASBR-PE1-pim] quit
# On PE 2, enable IP multicast routing, and enable PIM-SM on the public network interfaces.
<PE2> system-view
[PE2] multicast routing
[PE2-mrib] quit
[PE2] interface gigabitethernet 3/1/1
[PE2-GigabitEthernet3/1/1] pim sm
[PE2-GigabitEthernet3/1/1] quit
[PE2] interface loopback 1
[PE2-LoopBack1] pim sm
[PE2-LoopBack1] quit
# On ASBR-PE 2, enable IP multicast routing, and enable PIM-SM on the public network interfaces.
<ASBR-PE2> system-view
[ASBR-PE2] multicast routing
[ASBR-PE2-mrib] quit
[ASBR-PE2] interface gigabitethernet 3/1/2
[ASBR-PE2-GigabitEthernet3/1/2] pim sm
[ASBR-PE2-GigabitEthernet3/1/2] quit
[ASBR-PE2] interface loopback 1
[ASBR-PE2-LoopBack1] pim sm
[ASBR-PE2-LoopBack1] quit
[ASBR-PE2] interface loopback 2
[ASBR-PE2-LoopBack2] pim sm
[ASBR-PE2-LoopBack2] quit
# Configure Loopback 2 as a C-BSR and a C-RP.
[ASBR-PE2] pim
[ASBR-PE2-pim] c-bsr 22.22.22.22
[ASBR-PE2-pim] c-rp 22.22.22.22
[ASBR-PE2-pim] quit
2. Enable IP multicast routing for the VPN instances, enable PIM-SM on the VPN instance interfaces, and enable IGMP on the interfaces that have receiver hosts attached.
|
|
NOTE: The route targets for the same VPN instance on the ASBRs and PEs within the same AS must match. Those within different ASs do not need to match. |
# On CE a1, enable IP multicast routing, enable PIM-SM on each interface.
<CEa1> system-view
[CEa1] multicast routing
[CEa1-mrib] quit
[CEa1] interface gigabitethernet 3/1/1
[CEa1-GigabitEthernet3/1/1] pim sm
[CEa1-GigabitEthernet3/1/1] quit
[CEa1] interface gigabitethernet 3/1/2
[CEa1-GigabitEthernet3/1/2] pim sm
[CEa1-GigabitEthernet3/1/2] quit
[CEa1] interface loopback 0
[CEa1-LoopBack0] pim sm
[CEa1-LoopBack0] quit
# Configure Loopback 0 as a C-BSR and a C-RP.
[CEa1] pim
[CEa1-pim] c-bsr 2.2.2.2
[CEa1-pim] c-rp 2.2.2.2
[CEa1-pim] quit
# On CE a2, enable IP multicast routing, enable PIM-SM on GigabitEthernet 3/1/1, and enable IGMP on GigabitEthernet 3/1/2.
<CEa2> system-view
[CEa2] multicast routing
[CEa2-mrib] quit
[CEa2] interface gigabitethernet 3/1/1
[CEa2-GigabitEthernet3/1/1] pim sm
[CEa2-GigabitEthernet3/1/1] quit
[CEa2] interface gigabitethernet 3/1/2
[CEa2-GigabitEthernet3/1/2] igmp enable
[CEa2-GigabitEthernet3/1/2] quit
# On PE 1, create a VPN instance named customerA.
[PE1] ip vpn-instance customerA
[PE1-vpn-instance-customerA] route-distinguisher 100:1
[PE1-vpn-instance-customerA] vpn-target 100:1 both
[PE1-vpn-instance-customerA] quit
# Associate GigabitEthernet 3/1/2 with VPN instance customerA.
[PE1] interface gigabitethernet 3/1/2
[PE1-GigabitEthernet3/1/2] ip binding vpn-instance customerA
[PE1-GigabitEthernet3/1/2] quit
# Enable IP multicast routing for VPN instance customerA, and enable PIM-SM on GigabitEthernet 3/1/2.
[PE1] multicast routing vpn-instance customerA
[PE1-mrib-customerA] quit
[PE1] interface gigabitethernet 3/1/2
[PE1-GigabitEthernet3/1/2] pim sm
[PE1-GigabitEthernet3/1/2] quit
# On PE 2, create a VPN instance named customerA.
[PE2] ip vpn-instance customerA
[PE2-vpn-instance-customerA] route-distinguisher 12:12
[PE2-vpn-instance-customerA] vpn-target 3:3 import-extcommunity
[PE2-vpn-instance-customerA] vpn-target 3:3 export-extcommunity
[PE2-vpn-instance] quit
# Associate GigabitEthernet 3/1/2 with VPN instance customerA.
[PE2] interface gigabitethernet 3/1/2
[PE2-GigabitEthernet3/1/2] ip binding vpn-instance customerA
[PE2-GigabitEthernet3/1/2] quit
# Enable IP multicast routing for VPN instance customerA, and enable PIM-SM on GigabitEthernet 3/1/2.
[PE2] multicast routing vpn-instance customerA
[PE2-mrib-customerA] quit
[PE2] interface gigabitethernet 3/1/2
[PE2-GigabitEthernet3/1/2] pim sm
[PE2-GigabitEthernet3/1/2] quit
# On ASBR-PE 1, create a VPN instance named customerA.
[ASBR-PE1] ip vpn-instance customerA
[ASBR-PE1-vpn-instance-customerA] route-distinguisher 100:1
[ASBR-PE1-vpn-instance-customerA] vpn-target 100:1 both
[ASBR-PE1-vpn-instance-customerA] quit
# Associate GigabitEthernet 3/1/2 with VPN instance customerA.
[ASBR-PE1] interface gigabitethernet 3/1/2
[ASBR-PE1-GigabitEthernet3/1/2] ip binding vpn-instance customerA
[ASBR-PE1-GigabitEthernet3/1/2] quit
# Enable IP multicast routing for VPN instance customerA, and enable PIM-SM on GigabitEthernet 3/1/2.
[ASBR-PE1] multicast routing vpn-instance customerA
[ASBR-PE1-mrib-customerA] quit
[ASBR-PE1] interface gigabitethernet 3/1/2
[ASBR-PE1-GigabitEthernet3/1/2] pim sm
[ASBR-PE1-GigabitEthernet3/1/2] quit
# On ASBR-PE 2, create a VPN instance named customerA.
[ASBR-PE2] ip vpn-instance customerA
[ASBR-PE2-vpn-vpn-customerA] route-distinguisher 200:1
[ASBR-PE2-vpn-vpn-customerA] vpn-target 200:1 both
[ASBR-PE2-vpn-vpn-customerA] quit
# Associate GigabitEthernet 3/1/1 with VPN instance customerA.
[ASBR-PE2] interface gigabitethernet 3/1/1
[ASBR-PE2-GigabitEthernet3/1/1] ip binding vpn-instance customerA
[ASBR-PE2-GigabitEthernet3/1/1] quit
# Enable IP multicast routing for VPN instance customerA, and enable PIM-SM on GigabitEthernet 3/1/1.
[ASBR-PE2] multicast routing vpn-instance customerA
[ASBR-PE2-mrib-customerA] quit
[ASBR-PE2] interface gigabitethernet 3/1/1
[ASBR-PE2-GigabitEthernet3/1/1] pim sm
[ASBR-PE2-GigabitEthernet3/1/1] quit
3. Configure the MDT-based MVPN for the VPN instance.
# On PE 1, create an MDT-based MVPN for VPN instance customerA.
[PE1] multicast-vpn vpn-instance customerA mode mdt
# Create an MVPN IPv4 address family for VPN instance customerA.
[PE1-mvpn-customerA] address-family ipv4
# Specify the default group, MVPN source interface, and data group range for VPN instance customerA.
[PE1-mvpn-customerA-ipv4] default-group 239.1.1.1
[PE1-mvpn-customerA-ipv4] source loopback 1
[PE1-mvpn-customerA-ipv4] data-group 225.2.2.0 28
[PE1-mvpn-customerA-ipv4] quit
[PE1-mvpn-customerA] quit
# On ASBR-PE 1, create an MDT-based MVPN for VPN instance customerA.
[ASBR-PE1] multicast-vpn vpn-instance customerA mode mdt
# Create an MVPN IPv4 address family for VPN instance customerA.
[ASBR-PE1-mvpn-customerA] address-family ipv4
# Specify the default group, MVPN source interface, and data group range for VPN instance customerA.
[ASBR-PE1-mvpn-customerA-ipv4] default-group 239.1.1.1
[ASBR-PE1-mvpn-customerA-ipv4] source loopback 1
[ASBR-PE1-mvpn-customerA-ipv4] data-group 225.2.2.0 28
[ASBR-PE1-mvpn-customerA-ipv4] quit
[ASBR-PE1-mvpn-customerA] quit
# On PE 2, create an MDT-based MVPN for VPN instance customerA.
[PE2] multicast-vpn vpn-instance customerA mode mdt
# Create an MVPN IPv4 address family for VPN instance customerA.
[PE2-mvpn-customerA] address-family ipv4
# Specify the default group, MVPN source interface, and data group range for VPN instance customerA.
[PE2-mvpn-customerA-ipv4] default-group 239.1.1.1
[PE2-mvpn-customerA-ipv4] source loopback 1
[PE2-mvpn-customerA-ipv4] data-group 225.2.2.0 28
[PE2-mvpn-customerA-ipv4] quit
[PE2-mvpn-customerA] quit
# On ASBR-PE 2, create an MDT-based MVPN for VPN instance customerA.
[ASBR-PE2] multicast-vpn vpn-instance customerA mode mdt
# Create an MVPN IPv4 address family for VPN instance customerA.
[ASBR-PE2-mvpn-customerA] address-family ipv4
# Specify the default group, MVPN source interface, and data group range for VPN instance customerA.
[ASBR-PE2-mvpn-customerA-ipv4] default-group 239.1.1.1
[ASBR-PE2-mvpn-customerA-ipv4] source loopback 1
[ASBR-PE2-mvpn-customerA-ipv4] data-group 225.2.2.0 28
[ASBR-PE2-mvpn-customerA-ipv4] quit
[ASBR-PE2-mvpn-customerA] quit
Verifying the configuration
# Verify that the default-MDT has been established on the public network in each AS on PEs and ASBR-PEs. The following example shows PIM routing table for the public network on ASBR-PE 1.
[ASBR-PE1] display pim routing-table
Total 1 (*, G) entry; 1 (S, G) entry
(*, 239.1.1.1)
RP: 11.11.11.11 (local)
Protocol: pim-sm, Flag: SPT LOC ACT
UpTime: 02:54:43
Upstream interface: Register
Upstream neighbor: NULL
RPF prime neighbor: NULL
Downstream interface(s) information:
Total number of downstreams: 1
1: GigabitEthernet3/1/1
Protocol: pim-sm, UpTime: 02:54:43, Expires: -
(1.1.1.1, 239.1.1.1)
RP: 11.11.11.11 (local)
Protocol: pim-sm, Flag: SPT LOC ACT
UpTime: 01:57:13
Upstream interface: GigabitEthernet3/1/1
Upstream neighbor: 192.168.1.2
RPF prime neighbor: 192.168.1.2
Downstream interface(s) information: None
The output shows that an RPT for (*, 239.1.1.1) and an SPT for (1.1.1.1, 239.1.1.1) have been established on the public network. The RPT and SPT constitute the default-MDT for the public network.
Configuration files
· PE 1:
#
ip vpn-instance customerA
route-distinguisher 100:1
vpn-target 100:1 import-extcommunity
vpn-target 100:1 export-extcommunity
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
pim sm
#
interface GigabitEthernet3/1/1
ip address 192.168.1.2 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip binding vpn-instance customerA
ip address 10.11.1.1 255.255.255.0
pim sm
#
multicast routing
#
multicast routing vpn-instance customerA
#
multicast-vpn vpn-instance customerA mode mdt
address-family ipv4
source LoopBack1
default-group 239.1.1.1
data-group 225.1.1.0 255.255.255.240
#
· PE 2:
#
ip vpn-instance customerA
route-distinguisher 200:1
vpn-target 200:1 import-extcommunity
vpn-target 200:1 export-extcommunity
#
interface LoopBack1
ip address 1.1.1.4 255.255.255.255
pim sm
#
interface GigabitEthernet3/1/1
ip address 192.168.3.1 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip binding vpn-instance customerA
ip address 10.11.2.1 255.255.255.0
pim sm
#
multicast routing
#
multicast routing vpn-instance customerA
#
multicast-vpn vpn-instance customerA mode mdt
address-family ipv4
source LoopBack1
default-group 239.1.1.1
data-group 225.1.1.0 255.255.255.240
#
· ASBR-PE 1:
#
ip vpn-instance customerA
route-distinguisher 100:1
vpn-target 100:1 import-extcommunity
vpn-target 100:1 export-extcommunity
#
interface LoopBack1
ip address 1.1.1.2 255.255.255.255
pim sm
#
interface LoopBack2
ip address 11.11.11.11 255.255.255.255
pim sm
#
interface GigabitEthernet3/1/1
ip address 192.168.1.1 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip binding vpn-instance customerA
ip address 192.168.2.1 255.255.255.0
pim sm
#
multicast routing
#
multicast routing vpn-instance customerA
#
pim
c-bsr 11.11.11.11
c-rp 11.11.11.11
#
multicast-vpn vpn-instance customerA mode mdt
address-family ipv4
source LoopBack1
default-group 239.1.1.1
data-group 225.1.1.0 255.255.255.240
#
· ASBR-PE 2:
#
ip vpn-instance customerA
route-distinguisher 200:1
vpn-target 200:1 import-extcommunity
vpn-target 200:1 export-extcommunity
#
interface LoopBack1
ip address 1.1.1.3 255.255.255.255
pim sm
#
interface LoopBack2
ip address 22.22.22.22 255.255.255.255
pim sm
#
interface GigabitEthernet3/1/1
ip binding vpn-instance customerA
ip address 192.168.2.2 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip address 192.168.3.2 255.255.255.0
pim sm
#
multicast routing
#
multicast routing vpn-instance customerA
#
pim
c-bsr 22.22.22.22
c-rp 22.22.22.22
#
multicast-vpn vpn-instance customerA mode mdt
address-family ipv4
source LoopBack1
default-group 239.1.1.1
data-group 225.1.1.0 255.255.255.240
#
· CE a1:
#
interface LoopBack0
ip address 2.2.2.2 255.255.255.255
pim sm
#
interface GigabitEthernet3/1/1
ip address 10.11.3.1 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip address 10.11.1.2 255.255.255.0
pim sm
#
multicast routing
#
pim
c-bsr 2.2.2.2
c-rp 2.2.2.2
#
· CE a2:
#
interface GigabitEthernet3/1/1
ip address 10.11.2.2 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip address 10.11.4.1 255.255.255.0
igmp enable
#
multicast routing
#
Example: Configuring inter-AS option C MDT-based MVPN
Network configuration
As shown in Figure 3:
· Customer A has two branches that separately connect to AS 100 and AS 200.
· ASBR-PE 1 and ASBR-PE 2 are interconnected by using the inter-AS option C solution.
· PIM-SM runs within the two branches.
· The multicast source and the receiver host are in different branches.
Configure inter-AS option C MDT-based MVPN so that the receiver host can receive the multicast data from the source.
Table 3 Interface and IP address assignment
|
Device |
Interface |
IP address |
Device |
Interface |
IP address |
|
S 1 |
— |
10.11.3.2/24 |
R 1 |
— |
10.11.4.2/24 |
|
PE 1 |
GE3/1/1 |
192.168.1.2/24 |
ASBR-PE2 |
GE3/1/1 |
192.168.2.2/24 |
|
PE 1 |
GE3/1/2 |
10.11.1.1/24 |
ASBR-PE2 |
GE3/1/2 |
192.168.3.2/24 |
|
PE 1 |
Loop1 |
1.1.1.1/32 |
ASBR-PE2 |
Loop1 |
1.1.1.3/32 |
|
ASBR-PE1 |
GE3/1/1 |
192.168.1.1/24 |
ASBR-PE2 |
Loop2 |
22.22.22.22/32 |
|
ASBR-PE1 |
GE3/1/2 |
192.168.2.1/24 |
PE 2 |
GE3/1/1 |
192.168.3.1/24 |
|
ASBR-PE1 |
Loop1 |
1.1.1.2/32 |
PE 2 |
GE3/1/2 |
10.11.2.1/24 |
|
ASBR-PE1 |
Loop2 |
11.11.11.11/32 |
PE 2 |
Loop1 |
1.1.1.4/32 |
|
CE a1 |
GE3/1/1 |
10.11.3.1/24 |
CE a2 |
GE3/1/1 |
10.11.2.2/24 |
|
CE a1 |
GE3/1/2 |
10.11.1.2/24 |
CE a2 |
GE3/1/2 |
10.11.4.1/24 |
|
CE a1 |
Loop0 |
2.2.2.2/32 |
|
|
|
Analysis
To meet the network requirement, you must perform the following tasks:
· Create the same MDT-based MVPN for each AS.
· Establish MSDP peering relationships between the RPs in the ASs to share the multicast source information in different PIM-SM domains.
Procedures
Assigning IP addresses to interfaces
# Assign an IP address and subnet mask to each interface on CE a1, as shown in Table 3.
<CEa1> system-view
[CEa1] interface gigabitethernet 3/1/1
[CEa1-GigabitEthernet3/1/1] ip address 10.11.3.1 24
[CEa1-GigabitEthernet3/1/1] quit
[CEa1] interface loopback 0
[CEa1-LoopBack0] ip address 2.2.2.2 32
[CEa1-LoopBack0] quit
[CEa1] interface gigabitethernet 3/1/2
[CEa1-GigabitEthernet3/1/2] ip address 10.11.1.2 24
[CEa1-GigabitEthernet3/1/2] quit
# Configure PE 1, ASBR-PE 1, ASBR-PE 2, PE 2, and CE a2 in the same way CE a1 is configured. (Details not shown.)
Configuring routing and basic MPLS L3VPN
# Configure a unicast routing protocol and basic MPLS VPN on all devices so that all devices are interoperable at the network layer. (Details not shown) For more information about configuring basic MPLS VPN, see H3C CR16000-F Routers MPLS Configuration Guide.
Configuring multicast routing and inter-AS option A MDT-based MVPN
1. Enable IP multicast routing on the public network in each AS, enable PIM-SM on the public network interfaces (including Loopback interfaces), and configure PIM-SM domain boarders.
# On PE 1, enable IP multicast routing, and enable PIM-SM on the public network interfaces.
<PE1> system-view
[PE1] multicast routing
[PE1-mrib] quit
[PE1] interface gigabitethernet 3/1/1
[PE1-GigabitEthernet3/1/1] pim sm
[PE1-GigabitEthernet3/1/1] quit
[PE1] interface loopback 1
[PE1-LoopBack1] pim sm
[PE1-LoopBack1] quit
# On ASBR-PE 1, enable IP multicast routing, and enable PIM-SM on the public network interfaces.
<ASBR-PE1> system-view
[ASBR-PE1] multicast routing
[ASBR-PE1-mrib] quit
[ASBR-PE1] interface gigabitethernet 3/1/1
[ASBR-PE1-GigabitEthernet3/1/1] pim sm
[ASBR-PE1-GigabitEthernet3/1/1] quit
[ASBR-PE1] interface gigabitethernet 3/1/2
[ASBR-PE1-GigabitEthernet3/1/2] pim sm
[ASBR-PE1-GigabitEthernet3/1/2] quit
[ASBR-PE1] interface loopback 1
[ASBR-PE1-LoopBack1] pim sm
[ASBR-PE1-LoopBack1] quit
[ASBR-PE1] interface loopback 2
[ASBR-PE1-LoopBack2] pim sm
[ASBR-PE1-LoopBack2] quit
[ASBR-PE1] pim
# Configure Loopback 2 as a C-BSR and a C-RP.
[ASBR-PE1] pim
[ASBR-PE1-pim] c-bsr 11.11.11.11
[ASBR-PE1-pim] c-rp 11.11.11.11
[ASBR-PE1-pim] quit
# Configure GigabitEthernet 3/1/2 as a PIM-SM domain boarder.
[ASBR-PE1] interface gigabitethernet 3/1/2
[ASBR-PE1-GigabitEthernet3/1/2] pim bsr-boundary
[ASBR-PE1-GigabitEthernet3/1/2] quit
# On PE 2, enable IP multicast routing, and enable PIM-SM on the public network interfaces.
<PE2> system-view
[PE2] multicast routing
[PE2-mrib] quit
[PE2] interface gigabitethernet 3/1/1
[PE2-GigabitEthernet3/1/1] pim sm
[PE2-GigabitEthernet3/1/1] quit
[PE2] interface loopback 1
[PE2-LoopBack1] pim sm
[PE2-LoopBack1] quit
# On ASBR-PE 2, enable IP multicast routing, and enable PIM-SM on the public network interfaces.
<ASBR-PE2> system-view
[ASBR-PE2] multicast routing
[ASBR-PE2-mrib] quit
[ASBR-PE2] interface gigabitethernet 3/1/1
[ASBR-PE2-GigabitEthernet3/1/1] pim sm
[ASBR-PE2-GigabitEthernet3/1/1] quit
[ASBR-PE2] interface gigabitethernet 3/1/2
[ASBR-PE2-GigabitEthernet3/1/2] pim sm
[ASBR-PE2-GigabitEthernet3/1/2] quit
[ASBR-PE2] interface loopback 1
[ASBR-PE2-LoopBack1] pim sm
[ASBR-PE2-LoopBack1] quit
[ASBR-PE2] interface loopback 2
[ASBR-PE2-LoopBack2] pim sm
[ASBR-PE2-LoopBack2] quit
# Configure Loopback 2 as a C-BSR and a C-RP.
[ASBR-PE2] pim
[ASBR-PE2-pim] c-bsr 22.22.22.22
[ASBR-PE2-pim] c-rp 22.22.22.22
[ASBR-PE2-pim] quit
# Configure GigabitEthernet 3/1/1 as a PIM-SM domain boarder.
[ASBR-PE2] interface gigabitethernet 3/1/1
[ASBR-PE2-GigabitEthernet3/1/1] pim bsr-boundary
[ASBR-PE2-GigabitEthernet3/1/1] quit
2. Establish MSDP peering relationships between the RPs on the public network in the ASs:
# On ASBR-PE 1, specify an MSDP peer.
[ASBR-PE1] msdp
[ASBR-PE1-msdp] encap-data-enable
[ASBR-PE1-msdp] peer 192.168.2.2 connect-interface gigabitethernet 3/1/2
# On ASBR-PE 2, specify an MSDP peer.
[ASBR-PE2] msdp
[ASBR-PE2-msdp] encap-data-enable
[ASBR-PE2-msdp] peer 192.168.2.1 connect-interface gigabitethernet 3/1/1
3. Enable IP multicast routing for the VPN instance, enable PIM-SM on the private network interfaces, and enable IGMP on the interfaces that have receiver hosts attached:
|
|
NOTE: The route targets for the same VPN instance on the ASBRs and PEs within the same AS must match. Those within different ASs do not need to match. |
# On CE a1, enable IP multicast routing, and enable PIM-SM on each interface.
<CEa1> system-view
[CEa1] multicast routing
[CEa1-mrib] quit
[CEa1] interface gigabitethernet 3/1/1
[CEa1-GigabitEthernet3/1/1] pim sm
[CEa1-GigabitEthernet3/1/1] quit
[CEa1] interface gigabitethernet 3/1/2
[CEa1-GigabitEthernet3/1/2] pim sm
[CEa1-GigabitEthernet3/1/2] quit
[CEa1] interface loopback 0
[CEa1-LoopBack0] pim sm
[CEa1-LoopBack0] quit
# Configure Loopback 0 as a C-BSR and a C-RP.
[CEa1] pim
[CEa1-pim] c-bsr 2.2.2.2
[CEa1-pim] c-rp 2.2.2.2
[CEa1-pim] quit
# On CE a2, enable IP multicast routing, enable PIM-SM on GigabitEthernet 3/1/1, and enable IGMP on GigabitEthernet 3/1/2.
<CEa2> system-view
[CEa2] multicast routing
[CEa2-mrib] quit
[CEa2] interface gigabitethernet 3/1/1
[CEa2-GigabitEthernet3/1/1] pim sm
[CEa2-GigabitEthernet3/1/1] quit
[CEa2] interface gigabitethernet 3/1/2
[CEa2-GigabitEthernet3/1/2] igmp enable
[CEa2-GigabitEthernet3/1/2] quit
# On PE 1, create a VPN instance named customerA.
[PE1] ip vpn-instance customerA
[PE1-vpn-instance-customerA] route-distinguisher 11:11
[PE1-vpn-instance-customerA] vpn-target 3:3 import-extcommunity
[PE1-vpn-instance-customerA] vpn-target 3:3 export-extcommunity
[PE1-vpn-instance-customerA] quit
# Associate GigabitEthernet 3/1/2 with VPN instance customerA.
[PE1] interface gigabitethernet 3/1/2
[PE1-GigabitEthernet3/1/2] ip binding vpn-instance customerA
[PE1-GigabitEthernet3/1/2] quit
# Enable IP multicast routing for VPN instance customerA, and enable PIM-SM on GigabitEthernet 3/1/2.
[PE1] multicast routing vpn-instance customerA
[PE1-mrib-customerA] quit
[PE1] interface gigabitethernet 3/1/2
[PE1-GigabitEthernet3/1/2] pim sm
[PE1-GigabitEthernet3/1/2] quit
# On PE 2, create a VPN instance named customerA.
[PE2] ip vpn-instance customerA
[PE2-vpn-instance-customerA] route-distinguisher 12:12
[PE2-vpn-instance-customerA] vpn-target 3:3 import-extcommunity
[PE2-vpn-instance-customerA] vpn-target 3:3 export-extcommunity
[PE2-vpn-instance] quit
# Associate GigabitEthernet 3/1/2 with VPN instance customerA.
[PE2] interface gigabitethernet 3/1/2
[PE2-GigabitEthernet3/1/2] ip binding vpn-instance customerA
[PE2-GigabitEthernet3/1/2] quit
# Enable IP multicast routing for VPN instance customerA, and enable PIM-SM on GigabitEthernet 3/1/2.
[PE2] multicast routing vpn-instance customerA
[PE2-mrib-customerA] quit
[PE2] interface gigabitethernet 3/1/2
[PE2-GigabitEthernet3/1/2] pim sm
[PE2-GigabitEthernet3/1/2] quit
4. Create the same MDT-based MVPN for the ASs, and specify the default-group, MVPN source interface, and data-group for the MVPN:
# On PE 1, create an MDT-based MVPN for VPN instance customerA.
[PE1] multicast-vpn vpn-instance customerA mode mdt
# Create an MVPN IPv4 address family for VPN instance customerA.
[PE1-mvpn-customerA] address-family ipv4
# Specify the default group, MVPN source interface, and data group range for VPN instance customerA.
[PE1-mvpn-customerA-ipv4] default-group 239.1.1.1
[PE1-mvpn-customerA-ipv4] source loopback 1
[PE1-mvpn-customerA-ipv4] data-group 225.2.2.0 28
[PE2-mvpn-customerA-ipv4] quit
[PE1-mvpn-customerA] quit
# On PE 2, create an MDT-based MVPN for VPN instance customerA.
[PE2] multicast-vpn vpn-instance customerA mode mdt
# Create an MVPN IPv4 address family for VPN instance customerA.
[PE2-mvpn-customerA] address-family ipv4
# Specify the default group, MVPN source interface, and data group range for VPN instance customerA.
[PE2-mvpn-customerA-ipv4] default-group 239.1.1.1
[PE2-mvpn-customerA-ipv4] source loopback 1
[PE2-mvpn-customerA-ipv4] data-group 225.2.2.0 28
[PE2-mvpn-customerA-ipv4] quit
[PE2-mvpn-customerA] quit
Verifying the configuration
# Verify that the default-MDT has been established on the public network in each AS on PEs and ASBR-PEs. The following example shows PIM routing table for the public network on ASBR-PE 1.
[ASBR-PE1] display pim routing-table
Total 1 (*, G) entry; 2 (S, G) entry
(*, 239.1.1.1)
RP: 3.3.3.3 (local)
Protocol: pim-sm, Flag: SPT LOC ACT
UpTime: 02:54:43
Upstream interface: Register
Upstream neighbor: NULL
RPF prime neighbor: NULL
Downstream interface(s) information:
Total number of downstreams: 1
1: GigabitEthernet3/1/1
Protocol: pim-sm, UpTime: 02:54:43, Expires: -
(1.1.1.1, 239.1.1.1)
RP: 3.3.3.3 (local)
Protocol: pim-sm, Flag: SPT LOC ACT
UpTime: 01:57:13
Upstream interface: GigabitEthernet3/1/1
Upstream neighbor: 192.168.1.2
RPF prime neighbor: 192.168.1.2
Downstream interface(s) information: None
(1.1.1.4, 239.1.1.1)
RP: 3.3.3.3 (local)
Protocol: pim-sm, Flag: SPT LOC ACT
UpTime: 01:57:13
Upstream interface: GigabitEthernet3/1/2
Upstream neighbor: 192.168.2.2
RPF prime neighbor: 192.168.2.2
Downstream interface(s) information: None
The output shows that an RPT for (*, 239.1.1.1), an SPT for (1.1.1.1, 239.1.1.1), and an SPT for (1.1.1.4, 239.1.1.1) have been established on the public network. The RPT and SPTs constitute the default-MDT for the public network.
Configuration files
· PE 1:
#
ip vpn-instance customerA
route-distinguisher 100:1
vpn-target 100:1 import-extcommunity
vpn-target 100:1 export-extcommunity
#
interface LoopBack1
ip address 1.1.1.1 255.255.255.255
pim sm
#
interface GigabitEthernet3/1/1
ip address 192.168.1.2 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip binding vpn-instance customerA
ip address 10.11.1.1 255.255.255.0
pim sm
#
multicast routing
#
multicast routing vpn-instance customerA
#
multicast-vpn vpn-instance customerA mode mdt
address-family ipv4
source LoopBack1
default-group 239.1.1.1
data-group 225.1.1.0 255.255.255.240
#
· PE 2:
#
ip vpn-instance customerA
route-distinguisher 200:1
vpn-target 100:1 import-extcommunity
vpn-target 100:1 export-extcommunity
#
interface LoopBack1
ip address 1.1.1.4 255.255.255.255
pim sm
#
interface GigabitEthernet3/1/1
ip address 192.168.3.1 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip binding vpn-instance customerA
ip address 10.11.2.1 255.255.255.0
pim sm
#
multicast routing
#
multicast routing vpn-instance customerA
#
multicast-vpn vpn-instance customerA mode mdt
address-family ipv4
source LoopBack1
default-group 239.1.1.1
data-group 225.1.1.0 255.255.255.240
#
· ASBR-PE 1:
#
interface LoopBack1
ip address 1.1.1.2 255.255.255.255
pim sm
#
interface LoopBack2
ip address 11.11.11.11 255.255.255.255
pim sm
#
interface GigabitEthernet3/1/1
ip address 192.168.1.1 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip address 192.168.2.1 255.255.255.0
pim sm
pim bsr-boundary
#
multicast routing
#
pim
c-bsr 11.11.11.11
c-rp 11.11.11.11
#
msdp
encap-data-enable
peer 192.168.2.2 connect-interface GigabitEthernet3/1/2
#
· ASBR-PE 2:
#
interface LoopBack1
ip address 1.1.1.3 255.255.255.255
pim sm
#
interface LoopBack2
ip address 22.22.22.22 255.255.255.255
pim sm
#
interface GigabitEthernet3/1/1
ip address 192.168.2.2 255.255.255.0
pim sm
pim bsr-boundary
#
interface GigabitEthernet3/1/2
ip address 192.168.3.2 255.255.255.0
pim sm
#
multicast routing
#
pim
c-bsr 22.22.22.22
c-rp 22.22.22.22
#
msdp
encap-data-enable
peer 192.168.2.1 connect-interface GigabitEthernet3/1/1
#
· CE a1:
#
interface LoopBack0
ip address 2.2.2.2 255.255.255.255
pim sm
#
interface GigabitEthernet3/1/1
ip address 10.11.3.1 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip address 10.11.1.2 255.255.255.0
pim sm
#
multicast routing
#
pim
c-bsr 2.2.2.2
c-rp 2.2.2.2
#
· CE a2:
#
interface GigabitEthernet3/1/1
ip address 10.11.2.2 255.255.255.0
pim sm
#
interface GigabitEthernet3/1/2
ip address 10.11.4.1 255.255.255.0
igmp enable
#
multicast routing
#
Related documentation
· H3C CR16000-F Routers IP Multicast Command Reference-R7951P01
· H3C CR16000-F Routers IP Multicast Configuration Guide-R7951P01
· H3C CR16000-F Routers Layer 2—LAN Switching Command Reference-R7951P01
· H3C CR16000-F Routers Layer 2—LAN Switching Configuration Guide-R7951P01
· H3C CR16000-F Routers MPLS Command Reference-R7951P01
· H3C CR16000-F Routers MPLS Configuration Guide-R7951P01
