Profile 17

Load basic.startup.config.with.cpim.cfg

#IOS-XE
config replace flash:basic.startup.config.with.cpim.cfg
Y

#IOS-XR
configure
load bootflash:basic.startup.config.with.cpim.cfg
commit replace
y

The basic IP addresses, L3VPN, and C-PIM between the PEs and CEs is pre-configured.

• Configure multicast VPN using mLDP in the core using only P2MP trees.

• You cannot use PIM in the core.

• CE1 is predefined as the RP in the C-PIM via BSR.

• PEs must form C-PIM adjacencies between each other.

NOTE: Profile 17 is not in the v5.1 blue print, however it is simply like profile 12 but with C-PIM adjacencies instead of BGP overlay.

See answer below (scroll down).

Answer

This uses a mix of features we have seen previously:

• default MDT = P2MP mLDP

• Auto-discovery = BGP for mLDP

• C-multicast-routing = C-PIM in the overlay

#PE1, PE2
vrf def CUSTOMER
 add ipv4
  mdt default mpls mldp p2mp
  mdt auto-discovery mldp
!
router bgp 100 
 add ipv4 mvpn
  neighbor 10.10.10.10 activate

#P1
mpls ldp mldp add ipv4
!
router bgp 100
 add ipv4 mvpn
 neighbor-group IBGP
  add ipv4 mvpn
   route-reflector-client

#P2
mpls ldp mldp add ipv4

#PE3
mpls ldp mldp add ipv4
!
router bgp 100
 add ipv4 mvpn
 neighbor 10.10.10.10
  add ipv4 mvpn
 vrf CUSTOMER
  add ipv4 mvpn
!
multicast-routing add ipv4 int lo0 en
multicast-routing vrf CUSTOMER add ipv4
 mdt so lo0
 mdt default mldp p2mp
 bgp auto-discovery mldp
!
route-policy USE_MLDP_DEFAULT
 set core-tree mldp-default
end-policy
!
router pim vrf CUSTOMER add ipv4 rpf top route-policy USE_MLDP_DEFAULT

Verification

Verify that PEs are all adjacent in the C-PIM. This happens because we did not use BGP for the overlay (mdt overlay use-bgp or router pim vrf CUSTOMER add ipv4 c-multicast-routing bgp).

Test joining a multicast group on a customer router and pinging it from another customer router. There should be no BGP routes other than the type 1s from each PE. Customer PIM uses C-PIM overlayed over the mLDP default P2MP trees.