Example for Configuring Intra-AS Segmented Tunnel Transport (Through mLDP and RSVP-TE P2MP Tunnel Stitching)

This section provides an example for configuring intra-AS segmented tunnel transport (through mLDP and RSVP-TE P2MP tunnel stitching).

Networking Requirements

NG MVPN is deployed on the service provider's backbone network to solve multicast service issues that arise due to traffic congestion, transmission reliability, and data security. On the backbone network shown in Figure 1, an LDP LSP is deployed in one area and an RSVP-TE tunnel is deployed in another area to carry BGP/MPLS IP VPN services. The customer requires that MVPN services be provided using the existing network. To meet the preceding requirements, deploy segmented NG MVPN over an mLDP and RSVP-TE P2MP stitching tunnel.

Figure 1 Configuring intra-AS segmented tunnel transport (through mLDP and RSVP-TE P2MP tunnel stitching)

Interfaces 1 and 2 in this example represent GE 0/1/1 and GE 0/1/2, respectively.

Configuration Roadmap

The configuration roadmap is as follows:

Configure BGP/MPLS IP VPN and ensure that unicast VPN services are properly transmitted.
Establish a BGP MVPN peer relationship between the PEs so that the PEs can use BGP to exchange A-D and C-multicast routes.
Configure NG MVPN to support intra-AS inter-area segmented tunnels.
Configure PE1 to use mLDP to establish an I-PMSI tunnel so that an mLDP P2MP tunnel from PE1 to the ABR is established.
Configure the ABR to use RSVP-TE to establish a stitching tunnel to PE2 so that an RSVP-TE P2MP tunnel is established.
Bind the VPN instance to each PE's interface through which a CE accesses and configure PIM on the interfaces connecting PEs and CEs so that VPN multicast routing entries are generated for multicast traffic forwarding.
Configure IGMP on CE2's interface connected to the multicast receiver so that CE2 manages the receiver (multicast group member).

Data Preparation

To complete the configuration, you need the following data:

ID (2) of the IS-IS process running between PE1 and the ABR System ID (45.0005.0005.0006.00) of PE2, and system ID (45.0005.0005.0005.00) of the ABR
OSPF process ID (10) on PE2 and the ABR
On PE1 and PE2: VPN instance name (vpn1), VPN target (100:100), RD (100:1) of PE1, and RD (200:1) of PE2
AS number (100) for the BGP peers on the public network
ID (2) of the OSPF process, through which CE1 interworks with PE1, and CE2 interworks with PE2

Procedure

Configure BGP/MPLS IP VPN.

Assign an IP address to each interface according to Figure 1. For configuration details, see Configuration Files in this section.
Configure IGPs to interconnect devices on the BGP/MPLS IP VPN backbone network. IS-IS and OSPF are used as the IGPs in this example. For configuration details, see Configuration Files in this section.

Configure basic MPLS functions and MPLS TE on the MPLS backbone network to establish MPLS TE tunnels.

# Configure PE1.

[~PE1] mpls lsr-id 1.1.1.1
[*PE1] mpls
[*PE1-mpls] quit
[*PE1] mpls ldp
[*PE1-mpls-ldp] quit
[*PE1] interface gigabitethernet0/1/2
[*PE1-GigabitEthernet0/1/2] mpls
[*PE1-GigabitEthernet0/1/2] mpls ldp
[*PE1-GigabitEthernet0/1/2] quit
[*PE1] commit

Configure PE2.

[~PE2] mpls lsr-id 3.3.3.3
[*PE2] mpls
[*PE2-mpls] mpls te
[*PE2-mpls] mpls rsvp-te
[*PE2-mpls] mpls te cspf
[*PE2-mpls] quit
[*PE2] interface gigabitethernet0/1/2
[*PE2-GigabitEthernet0/1/2] mpls
[*PE2-GigabitEthernet0/1/2] mpls te
[*PE2-GigabitEthernet0/1/2] mpls rsvp-te
[*PE2-GigabitEthernet0/1/2] quit
[*PE2] interface Tunnel10
[*PE2-Tunnel10] ip address unnumbered interface LoopBack1
[*PE2-Tunnel10] tunnel-protocol mpls te
[*PE2-Tunnel10] destination 2.2.2.2
[*PE2-Tunnel10] mpls te tunnel-id 100
[*PE2-Tunnel10] quit
[*PE2] commit

# Configure the ABR.

[~ABR] mpls lsr-id 2.2.2.2
[*ABR] mpls
[*ABR-mpls] mpls te
[*ABR-mpls] mpls rsvp-te
[*ABR-mpls] mpls te cspf
[*ABR-mpls] quit
[*ABR] mpls ldp
[*ABR-mpls-ldp] quit
[*ABR] interface gigabitethernet0/1/1
[*ABR-GigabitEthernet0/1/1] mpls
[*ABR-GigabitEthernet0/1/1] mpls ldp
[*ABR-GigabitEthernet0/1/1] quit
[*ABR] interface gigabitethernet0/1/2
[*ABR-GigabitEthernet0/1/2] mpls
[*ABR-GigabitEthernet0/1/2] mpls te
[*ABR-GigabitEthernet0/1/2] mpls rsvp-te
[*ABR-GigabitEthernet0/1/2] quit
[*ABR] interface Tunnel10
[*ABR-Tunnel10] ip address unnumbered interface LoopBack1
[*ABR-Tunnel10] tunnel-protocol mpls te
[*ABR-Tunnel10] destination 3.3.3.3
[*ABR-Tunnel10] mpls te tunnel-id 100
[*ABR-Tunnel10] quit
[*ABR] commit

Establish an MP-IBGP peer relationship between each PE and the ABR, and configure the ABR as the RR for PE1 and PE2.

# Configure PE1.

[~PE1] bgp 100
[*PE1-bgp] peer 2.2.2.2 as-number 100
[*PE1-bgp] peer 2.2.2.2 connect-interface LoopBack1
[*PE1-bgp] ipv4-family vpnv4
[*PE1-bgp-af-vpnv4] peer 2.2.2.2 enable
[*PE1-bgp-af-vpnv4] quit
[*PE1-bgp] quit
[*PE1] commit

# Configure PE2.

[~PE2] bgp 100
[*PE2-bgp] peer 2.2.2.2 as-number 100
[*PE2-bgp] peer 2.2.2.2 connect-interface LoopBack1
[*PE2-bgp] ipv4-family vpnv4
[*PE2-bgp-af-vpnv4] peer 2.2.2.2 enable
[*PE2-bgp-af-vpnv4] quit
[*PE2-bgp] quit
[*PE2] commit

# Prevent the ABR from filtering VPN routes, configure it to set the next hop of the routes to be advertised to the PEs to itself, and configure a tunnel selector in the VPNv4 address family so that it preferentially selects an RSVP-TE tunnel.

[~ABR] tunnel-policy test
[*ABR-tunnel-policy-test] tunnel select-seq te ldp load-balance-number 4 
[*ABR-tunnel-policy-test] quit
[*ABR]tunnel-selector test permit  node 10  
[*ABR-tunnel-selector] apply tunnel-policy test
[*ABR-tunnel-selector] quit
[*ABR] bgp 100
[*ABR-bgp] tunnel-selector test         //By default, an LDP LSP is preferentially selected. This configuration allows an RSVP-TE tunnel to be preferentially selected over an LDP LSP.
[*ABR-bgp] peer 1.1.1.1 as-number 100
[*ABR-bgp] peer 1.1.1.1 connect-interface LoopBack1
[*ABR-bgp] peer 3.3.3.3 as-number 100
[*ABR-bgp] peer 3.3.3.3 connect-interface LoopBack1
[*ABR-bgp] ipv4-family vpnv4
[*ABR-bgp-af-vpnv4] undo policy vpn-target     //This command prevents the ABR from filtering received VPN routes based on VPN targets so that it accepts all VPN routes. By default, an ABR is not bound to any VPN instance, and therefore, it rejects all received VPN routes.
[*ABR-bgp-af-vpnv4] peer 1.1.1.1 enable
[*ABR-bgp-af-vpnv4] peer 1.1.1.1 reflect-client  
[*ABR-bgp-af-vpnv4] peer 1.1.1.1 next-hop-local
[*ABR-bgp-af-vpnv4] peer 3.3.3.3 enable
[*ABR-bgp-af-vpnv4] peer 3.3.3.3 reflect-client
[*ABR-bgp-af-vpnv4] peer 3.3.3.3 next-hop-local
[*ABR-bgp-af-vpnv4] quit
[*ABR-bgp] quit
[*ABR] commit

Configure a VPN instance on each PE and bind the VPN instance on each PE to its interface connecting to a CE.

# Configure PE1.

[~PE1] ip vpn-instance vpn1
[*PE1-vpn-instance-vpn1] ipv4-family
[*PE1-vpn-instance-vpn1-af-ipv4] route-distinguisher 100:1
[*PE1-vpn-instance-vpn1-af-ipv4] vpn-target 100:100
[*PE1-vpn-instance-vpn1-af-ipv4] quit
[*PE1-vpn-instance-vpn1] quit
[*PE1] interface gigabitethernet0/1/1
[*PE1-GigabitEthernet0/1/1] ip binding vpn-instance vpn1
[*PE1-GigabitEthernet0/1/1] ip address 192.168.1.2 24
[*PE1-GigabitEthernet0/1/1] quit
[*PE1] commit

# Configure PE2. Note that the type of tunnel used to carry VPN services must be set to TE in the VPN instance.

[~PE2] tunnel-policy p1
[*PE2-tunnel-policy-p1] tunnel select-seq cr-lsp load-balance-number 4  
[*PE2-tunnel-policy-p1] quit
[*PE2] ip vpn-instance vpn1
[*PE2-vpn-instance-vpn1] ipv4-family
[*PE2-vpn-instance-vpn1-af-ipv4] route-distinguisher 200:1
[*PE2-vpn-instance-vpn1-af-ipv4] tnl-policy p1
[*PE2-vpn-instance-vpn1-af-ipv4] vpn-target 100:100
[*PE2-vpn-instance-vpn1-af-ipv4] quit
[*PE2-vpn-instance-vpn1] quit
[*PE2] interface gigabitethernet0/1/1
[*PE2-GigabitEthernet0/1/1] ip binding vpn-instance vpn1
[*PE2-GigabitEthernet0/1/1] ip address 192.168.2.1 24
[*PE2-GigabitEthernet0/1/1] quit
[*PE2] commit

Configure OSPF multi-instance on each PE to import VPN routes.

# Configure PE1.

[~PE1] ospf 2 vpn-instance vpn1
[*PE1-ospf-2] import-route bgp
[*PE1-ospf-2] area 0.0.0.0
[*PE1-ospf-2-area-0.0.0.0] network 192.168.1.0 0.0.0.255
[*PE1-ospf-2-area-0.0.0.0] quit
[*PE1-ospf-2] quit
[*PE1] bgp 100
[*PE1-bgp] ipv4-family vpn-instance vpn1
[*PE1-bgp-vpn1] import-route ospf 2
[*PE1-bgp-vpn1] quit
[*PE1-bgp] quit
[*PE1] commit

Repeat this step for PE2. For configuration details, see Configuration Files in this section.

Configure OSPF on each CE.

# Configure CE1.

[~CE1] ospf 2
[*CE1-ospf-2] area 0.0.0.0
[*CE1-ospf-2] network 172.16.1.0 0.0.0.255
[*CE1-ospf-2] network 192.168.1.0 0.0.0.255
[*CE1-ospf-2] quit
[*CE1] commit

Repeat this step for CE2. For configuration details, see Configuration Files in this section.

Establish a BGP MVPN peer relationship between each PE and the ABR, and configure the ABR as the RR for PE1 and PE2.

# Configure PE1.

[~PE1] bgp 100
[*PE1-bgp] ipv4-family mvpn
[*PE1-bgp-af-mvpn] peer 2.2.2.2 enable
[*PE1-bgp-af-mvpn] quit
[*PE1-bgp] quit
[*PE1] commit

# Configure PE2.

[~PE2] bgp 100
[*PE2-bgp] ipv4-family mvpn
[*PE2-bgp-af-mvpn] peer 2.2.2.2 enable
[*PE2-bgp-af-mvpn] quit
[*PE2-bgp] quit
[*PE2] commit

# Configure the ABR.

[~ABR] bgp 100
[*ABR-bgp] ipv4-family mvpn
[*ABR-bgp-af-mvpn] undo policy vpn-target
[*ABR-bgp-af-mvpn] peer 1.1.1.1 enable
[*ABR-bgp-af-mvpn] peer 1.1.1.1 reflect-client
[*ABR-bgp-af-mvpn] peer 3.3.3.3 enable
[*ABR-bgp-af-mvpn] peer 3.3.3.3 reflect-client
[*ABR-bgp-af-mvpn] quit
[*ABR-bgp] quit
[*ABR] commit

Configure NG MVPN to support intra-AS inter-area segmented tunnels.

Configure PE1.

[~PE1] ip vpn-instance vpn1
[*PE1-vpn-instance-vpn1] ipv4-family
[*PE1-vpn-instance-vpn1-af-ipv4] multicast routing-enable
[*PE1-vpn-instance-vpn1-af-ipv4] mvpn
[*PE1-vpn-instance-vpn1-af-ipv4-mvpn] inter-area-segmented enable
[*PE1-vpn-instance-vpn1-af-ipv4-mvpn] quit
[*PE1-vpn-instance-vpn1-af-ipv4] quit
[*PE1-vpn-instance-vpn1] quit
[*PE1] commit

Configure the ABR.

[~ABR] multicast mvpn inter-area-segmented enable
[*ABR] commit

Configure PE1 to use mLDP to establish an I-PMSI tunnel to the ABR, and configure the ABR to use RSVP-TE P2MP to establish a stitching PMSI tunnel to PE2.

# Configure PE1.

[~PE1] mpls ldp
[*PE1-mpls-ldp] mldp p2mp
[*PE1-mpls-ldp] quit
[*PE1] multicast mvpn 1.1.1.1
[*PE1] ip vpn-instance vpn1
[*PE1-vpn-instance-vpn1] ipv4-family
[*PE1-vpn-instance-vpn1-af-ipv4] mvpn
[*PE1-vpn-instance-vpn1-af-ipv4-mvpn] sender-enable
[*PE1-vpn-instance-vpn1-af-ipv4-mvpn] c-multicast signaling bgp
[*PE1-vpn-instance-vpn1-af-ipv4-mvpn] ipmsi-tunnel
[*PE1-vpn-instance-vpn1-af-ipv4-mvpn-ipmsi] mldp 
[*PE1-vpn-instance-vpn1-af-ipv4-mvpn-ipmsi] quit
[*PE1-vpn-instance-vpn1-af-ipv4-mvpn] quit
[*PE1-vpn-instance-vpn1-af-ipv4] quit
[*PE1-vpn-instance-vpn1] quit
[*PE1] commit

# Configure the ABR. Note that an RSVP-TE P2MP template and a stitching policy need to be configured on the ABR.

[~ABR] mpls ldp
[*ABR-mpls-ldp] mldp p2mp
[*ABR-mpls-ldp] quit
[*ABR] mpls
[*ABR-mpls] mpls te p2mp-te
[*ABR-mpls] quit
[*ABR] mpls te p2mp-template t1
[*ABR-te-p2mp-template-t1] quit
[*ABR] route-policy rp1 permit node 1
[*ABR-route-policy-rp1] apply stitch-pmsi rsvp-te p2mp-template t1
[*ABR-route-policy-rp1] quit
[*ABR] multicast mvpn 2.2.2.2
[*ABR] bgp 100
[*ABR-bgp] ipv4-family mvpn
[*ABR-bgp-af-mvpn] reflect change-path-attribute             //Enable the RR to modify path attributes of BGP MVPN routes based on an export policy.
[*ABR-bgp-af-mvpn] peer 3.3.3.3 route-policy rp1 export
[*ABR-bgp-af-mvpn] quit
[*ABR-bgp] quit
[*ABR] commit

# Configure PE2.

[~PE2] mpls
[*PE2-mpls] mpls te p2mp-te
[*PE2-mpls] quit
[*PE2] multicast mvpn 3.3.3.3
[*PE2] ip vpn-instance vpn1
[*PE2-vpn-instance-vpn1] ipv4-family
[*PE2-vpn-instance-vpn1-af-ipv4] multicast routing-enable 
[*PE2-vpn-instance-vpn1-af-ipv4] mvpn
[*PE2-vpn-instance-vpn1-af-ipv4-mvpn] c-multicast signaling bgp
[*PE2-vpn-instance-vpn1-af-ipv4-mvpn] quit
[*PE2-vpn-instance-vpn1-af-ipv4] quit
[*PE2-vpn-instance-vpn1] quit
[*PE2] commit

After the configuration is complete, run the display mvpn inter-region-segmented ipmsi command on the ABR to check I-PMSI tunnel information.

[~ABR] display mvpn inter-region-segmented  ipmsi
Inter-region-segmented I-PMSI routes: total 1       
I-PMSI(RD:OrigIP): 100:100: 1.1.1.1 
Received Upstream I-PMSI: Tunnel type: mLDP P2MP LSP, Root-IP: 1.1.1.1, Opaque value: 0x01000400008041      
Leaf:       
  1: 2.2.2.2 (local)
Advertised Downstream I-PMSI(Policy: rp1): Tunnel type: RSVP-TE P2MP LSP, P2MP-ID: 0x02020202, Tunnel ID: 49153, Extended Tunnel ID:
 2.2.2.2    
Leaf:       
  1: 3.3.3.3

The command output shows that an mLDP P2MP tunnel has been established, with PE1 as the root and the ABR as a leaf. In addition, an RSVP-TE P2MP stitching tunnel has been established, with the ABR as the root and PE2 as a leaf.

Configure PIM.

# Configure PE1.

[~PE1] interface gigabitethernet0/1/1
[~PE1-GigabitEthernet0/1/1] pim sm
[*PE1-GigabitEthernet0/1/1] quit
[*PE1] commit

# Configure CE1.

[~CE1] multicast routing-enable
[*CE1] interface gigabitethernet0/1/1
[*CE1-GigabitEthernet0/1/1] pim sm
[*CE1-GigabitEthernet0/1/1] quit
[*CE1] interface gigabitethernet0/1/2
[*CE1-GigabitEthernet0/1/2] pim sm
[*CE1-GigabitEthernet0/1/2] quit
[*CE1] commit

# Configure PE2.

[~PE2] interface gigabitethernet0/1/1
[~PE2-GigabitEthernet0/1/1] pim sm
[*PE2-GigabitEthernet0/1/1] quit
[*PE2] commit

# Configure CE2.

[~CE2] multicast routing-enable
[*CE2] interface gigabitethernet0/1/1
[*CE2-GigabitEthernet0/1/1] pim sm
[*CE2-GigabitEthernet0/1/1] quit
[*CE2] interface gigabitethernet0/1/2
[*CE2-GigabitEthernet0/1/2] pim sm
[*CE2-GigabitEthernet0/1/2] quit
[*CE2] commit

Configure IGMP.

# Configure CE2.

[~CE2] interface gigabitethernet0/1/1
[*CE2-GigabitEthernet0/1/1] igmp enable
[*CE2-GigabitEthernet0/1/1] quit
[*CE2] commit

Verify the configuration.

After the configurations are complete, segmented NG MVPN functions are configured. If CE2 has access users, CE1 can use the BGP/MPLS IP VPN to forward multicast data to the users. In this example, the user connected to CE2 sends an IGMP Report message to CE2, and the multicast source 172.16.1.2 sends multicast data. A check on multicast routing entries can determine whether the segmented NG MVPN is configured successfully.

Run the display pim routing-table command on CE2 to view its PIM routing table. Run the display pim vpn-instance vpn1 routing-table command on PE2 to check the PIM routing entries of vpn1.

[~CE2] display pim routing-table
 VPN-Instance: public net
 Total 0 (*, G) entry; 1 (S, G) entry

 (172.16.1.2, 239.1.1.1)
     RP: NULL
     Protocol: pim-sm, Flag: SPT SG_RCVR ACT
     UpTime: 08:48:25
     Upstream interface: GigabitEthernet0/1/2, Refresh time: 08:48:25
         Upstream neighbor: 192.168.2.1
         RPF prime neighbor: 192.168.2.1
     Downstream interface(s) information:
     Total number of downstreams: 1
        1: GigabitEthernet0/1/1
             Protocol: igmp, UpTime: 08:48:25, Expires: - 
[~PE2] display pim vpn-instance vpn1 routing-table
 VPN-Instance: vpn1
 Total 0 (*, G) entry; 1 (S, G) entry

 (172.16.1.2, 239.1.1.1)
     RP: NULL
     Protocol: pim-sm, Flag: SPT ACT
     UpTime: 00:05:16
     Upstream interface: through-BGP, Refresh time: 00:05:16
         Upstream neighbor: 2.2.2.2
         RPF prime neighbor: 2.2.2.2
     Downstream interface(s) information:
     Total number of downstreams: 1
        1: GigabitEthernet0/1/1
             Protocol: pim-sm, UpTime: 00:05:16, Expires: 00:03:16

Configuration Files

CE1

#
sysname CE1
#
multicast routing-enable
#
interface GigabitEthernet0/1/1
 undo shutdown
 ip address 172.16.1.1 255.255.255.0
 pim sm
#
interface GigabitEthernet0/1/2 
 undo shutdown
 ip address 192.168.1.2 255.255.255.0
 pim sm
#
ospf 2
 area 0.0.0.0
  network 172.16.1.0 0.0.0.255
  network 192.168.1.0 0.0.0.255
#
return

PE1

#
sysname PE1
# 
multicast mvpn 1.1.1.1
# 
ip vpn-instance vpn1
 ipv4-family 
  route-distinguisher 100:100  
  vpn-target 100:100 export-extcommunity
  vpn-target 100:100 import-extcommunity
  multicast routing-enable   
  mvpn     
   sender-enable    
   c-multicast signaling bgp 
   inter-area-segmented enable 
   ipmsi-tunnel     
    mldp  
# 
mpls lsr-id 1.1.1.1 
# 
mpls
# 
mpls ldp   
 mldp p2mp 
 #
ipv4-family   
# 
isis 2     
 network-entity 45.0005.0005.0006.00
#
interface GigabitEthernet0/1/1      
 undo shutdown      
 ip binding vpn-instance vpn1 
 ip address 192.168.1.2 255.255.255.0 
 pim sm    
#  
interface GigabitEthernet0/1/2      
 undo shutdown      
 ip address 10.1.1.1 255.255.255.0    
 isis enable 2      
 mpls      
 mpls ldp 
#
 interface LoopBack1 
 ip address 1.1.1.1 255.255.255.255   
 isis enable 2
# 
bgp 100      
 peer 2.2.2.2 as-number 100  
 peer 2.2.2.2 connect-interface LoopBack1 
#
 ipv4-family unicast
  undo synchronization   
  peer 2.2.2.2 enable 
#
 ipv4-family mvpn   
  policy vpn-target 
  peer 2.2.2.2 enable 
# 
  ipv4-family vpnv4  
  policy vpn-target 
  peer 2.2.2.2 enable 
#
 ipv4-family vpn-instance vpn1 
  import-route ospf 2    
 # 
ospf 2 vpn-instance vpn1     
 import-route bgp   
 area 0.0.0.0
  network 192.168.1.0 0.0.0.255
#  
return

CE2

#
sysname CE2
#
multicast routing-enable
#
interface GigabitEthernet0/1/1
 undo shutdown
 ip address 172.16.2.1 255.255.255.0
 pim sm
 igmp enable
#
interface GigabitEthernet0/1/2
 undo shutdown
 ip address 192.168.2.2 255.255.255.0
 pim sm
#
ospf 2
 area 0.0.0.0
  network 172.16.2.0 0.0.0.255
  network 192.168.2.0 0.0.0.255
#
return

PE2

# 
sysname PE2 
# 
multicast mvpn 3.3.3.3
# 
ip vpn-instance vpn1  
 ipv4-family
  route-distinguisher 200:1 
  tnl-policy p1 
  vpn-target 100:100 export-extcommunity 
  vpn-target 100:100 import-extcommunity 
  multicast routing-enable  
  mvpn
   c-multicast signaling bgp
# 
mpls lsr-id 3.3.3.3
# 
mpls  
 mpls te 
 mpls te p2mp-te
 mpls rsvp-te  
 mpls te cspf  
# 
interface GigabitEthernet0/1/1  
 undo shutdown 
 ip binding vpn-instance vpn1
 ip address 192.168.2.1 255.255.255.0 
 pim sm  
 igmp enable
# 
interface GigabitEthernet0/1/2  
 undo shutdown 
 ip address 10.2.1.2 255.255.255.0 
 mpls 
 mpls te 
 mpls rsvp-te  
# 
interface LoopBack1
 ip address 3.3.3.3 255.255.255.255
# 
interface Tunnel10  
 ip address unnumbered interface LoopBack1
 tunnel-protocol mpls te 
 destination 2.2.2.2  
 mpls te tunnel-id 100
# 
bgp 100  
 peer 2.2.2.2 as-number 100 
 peer 2.2.2.2 connect-interface LoopBack1
 #
 ipv4-family unicast  
  undo synchronization 
  peer 2.2.2.2 enable 
 #
 ipv4-family mvpn  
  policy vpn-target
  peer 2.2.2.2 enable 
 #
 ipv6-family unicast  
  undo synchronization
 #
 ipv4-family vpnv4 
  policy vpn-target
  peer 2.2.2.2 enable 
 #
 ipv4-family vpn-instance vpn1  
  import-route ospf 2
# 
ospf 10  
 opaque-capability enable
 area 0.0.0.0  
  network 3.3.3.3 0.0.0.0
  network 10.2.1.0 0.0.0.255
  mpls-te enable
#
ospf 2 vpn-instance vpn1     
 import-route bgp   
 area 0.0.0.0
  network 192.168.2.0 0.0.0.255
#     
tunnel-policy p1  
  tunnel select-seq cr-lsp load-balance-number 4  
#  
return

ABR

#
sysname ABR    
#    
multicast mvpn 2.2.2.2     
#     
multicast mvpn inter-area-segmented enable      
# 
tunnel-selector test permit node 10
 apply tunnel-policy test 
#
mpls lsr-id 2.2.2.2 
#     
mpls  
 mpls te     
 mpls te p2mp-te    
 mpls rsvp-te
 mpls te cspf
#     
mpls te p2mp-template t1     
#     
mldp-p2mp-tunnel p2mp-lsp  
#     
mpls ldp     
 mldp p2mp   
 #    
 ipv4-family    
#     
isis 2
 network-entity 45.0005.0005.0005.00     
#     
interface GigabitEthernet0/1/1    
 undo shutdown      
 ip address 10.1.1.2 255.255.255.0
 isis enable 2      
 mpls 
 mpls ldp     
#        
interface GigabitEthernet0/1/2    
 undo shutdown      
 ip address 10.2.1.1 255.255.255.0
 mpls 
 mpls te     
 mpls rsvp-te
#     
interface LoopBack1 
 ip address 2.2.2.2 255.255.255.255      
 isis enable 2      
#     
interface Tunnel10  
 ip address unnumbered interface LoopBack1      
 tunnel-protocol mpls te   
 destination 3.3.3.3
 mpls te tunnel-id 100     
#     
bgp 100      
 peer 1.1.1.1 as-number 100
 peer 1.1.1.1 connect-interface LoopBack1
 peer 3.3.3.3 as-number 100
 peer 3.3.3.3 connect-interface LoopBack1  
 #    
 ipv4-family unicast
  undo synchronization     
  peer 1.1.1.1 enable      
  peer 1.1.1.1 reflect-client     
  peer 1.1.1.1 next-hop-local     
  peer 3.3.3.3 enable      
  peer 3.3.3.3 reflect-client     
  peer 3.3.3.3 next-hop-local       
 #    
 ipv4-family mvpn   
  reflect change-path-attribute   
  undo policy vpn-target   
  peer 1.1.1.1 enable      
  peer 1.1.1.1 reflect-client     
  peer 1.1.1.1 next-hop-local     
  peer 3.3.3.3 enable      
  peer 3.3.3.3 route-policy rp1 export   
  peer 3.3.3.3 reflect-client     
  peer 3.3.3.3 next-hop-local     
 #    
 ipv4-family vpnv4  
  undo policy vpn-target   
  tunnel-selector test     
  peer 1.1.1.1 enable      
  peer 1.1.1.1 reflect-client     
  peer 1.1.1.1 next-hop-local     
  peer 3.3.3.3 enable      
  peer 3.3.3.3 reflect-client     
  peer 3.3.3.3 next-hop-local        
#      
ospf 10      
 opaque-capability enable  
 area 0.0.0.0
  network 2.2.2.2 0.0.0.0  
  network 10.2.1.0 0.0.0.255      
  mpls-te enable    
#     
route-policy rp1 permit node 1    
 apply stitch-pmsi rsvp-te p2mp-template t1     
#         
tunnel-policy test  
 tunnel select-seq cr-lsp ldp load-balance-number 4      
#     
return