Profile 21

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 unicast ingress replication in the core.

• You cannot use PIM or mLDP in the core.

• Use BGP for auto-discovery of participating PEs.

• Configure support for SSM in the C-PIM.

• Use BGP as the overlay - PEs are not allowed to form C-PIM adjacencies with each other.

NOTE: Profile 21 is not in the v5.1 blueprint.

See answer below (scroll down).

Answer

This is the same as profile 19, but we use BGP as the overlay instead of C-PIM.

#PE1, PE2
vrf def CUSTOMER
 add ipv4
  mdt default ingress-rep
  mdt auto-discovery ingress-rep
  mdt overlay use-bgp
!
router bgp 100
 add ipv4 mvpn
  neighbor 10.10.10.10 activate

#P1
router bgp 100
 add ipv4 mvpn
 neighbor-group IBGP
  add ipv4 mvpn
   route-reflector-client

#PE3
router bgp 100
 add ipv4 mvpn
 neighbor-group IBGP
  add ipv4 mvpn
   route-reflector-client
 vrf CUSTOMER
  add ipv4 mvpn
!
route-policy USE_IR_DEFAULT
 set core-tree ingress-replication-default
end-policy
!
router pim vrf CUSTOMER add ipv4
 rpf top route-policy USE_IR_DEFAULT
 mdt c-multicast-routing bgp
!
multicast-routing add ipv4 int lo0 en
multicast-routing vrf CUSTOMER add ipv4
 mdt so lo0
 mdt default ingress-rep
 bgp auto-discovery ingress-rep

Verification

BSR again does not seem to be supported in the C-PIM. Instead I join a group on C2 again for (C1, G).

Verify that the PIM Join converts to a BGP route type 7:

These type 7 routes on PE1, received from PE2, are converted back into a PIM Join towards CE1 as we have seen before.

If desired, test S-PMSI as well. This works the same as we saw with profile 19 using type 3 and type 4 routes.