I have to run PIM-SM and PIM-SSM based both in Core. This is purely due to multivendor enviroment.
When I have all customer sites on cisco, i will run PIM-SSM ( default +data) and when i have multivendor in picture will run PIM-SM ( default) for specific customer. This will purely product team driven.
Now, I have to make sure that i use proper different Multicast group for both.
I have in mind that
1. PIM-SM - 18.104.22.168/16 range.
where 22.214.171.124 - default mdt, 126.96.36.199/24 - DATA MDT per customer
same way second customer 188.8.131.52 - default , 184.108.40.206/24 - DATA MDT
2. PIM-SSM : 220.127.116.11/16
18.104.22.168 - default mdt
22.214.171.124/24 - data mdt
126.96.36.199 - default mdt
2188.8.131.52/24- data mdt ..so on.
With this, I have following configuation :
ip pim rp-address 184.108.40.206 SM-RANGE
ip pim ssm range SSM-RANGE
ip access-list standard SSM-RANGE
permit 220.127.116.11 0.0.255.255
ip access-list standard SM-RANGE
permit 18.104.22.168 0.0.255.255
ip vrf VPN-A
description A Customer using MVPN SM
route-target both 65000:65000
mdt default 22.214.171.124
mdt data 126.96.36.199 0.0.0.15 threshold 1
ip vrf VPN-B
description A Customer using MVPN SSM
route-target both 65000:65000
mdt default 188.8.131.52
mdt data 184.108.40.206 0.0.0.15 threshold
ip multicast-routing vrf VPN-A
ip multicast-routing vrf VPN-B
Is this looking corect ? I have one doubt is, the DATA MDT range used for PIM-SM based solution should be in SM ACL or SSM ACL ??
Any suggestion on Multicast addressing for my requirment ? I would apprcieate the help !!
Let's say you use PIM-SM for the Data-MDT and you have the same pool configured for the same Multicast Domain or mVPN.
If two PEs connected to two different customer sources using different groups choose the same Data-MDT group, each PE joining this Data-MDT will receive both traffic even if their receivers are interested only with one customer group.
If you let the PEs to switchover to the SPT, they could also choose the wrong source PE.
Here is an extract from Rozen draft about this issue:
7.3. Use of SSM for Data MDTs
The use of Data MDTs requires that a set of multicast P-addresses be
pre-allocated and dedicated for use as the destination addresses for
the Data MDTs.
If SSM is used to set up the Data MDTs, then each MD needs to be
assigned a set of these of multicast P-addresses. Each VRF in the MD
needs to be configured with this set (i.e., all VRFs in the MD are
configured with the same set). If there are n addresses in this set,
then each PE in the MD can be the source of n Data MDTs in that MD.
If SSM is not used for setting up Data MDTs, then each VRF needs to
be configured with a unique set of multicast P-addresses; two VRFs in
the same MD cannot be configured with the same set of addresses.
This requires the pre-allocation of many more multicast P-addresses,
and the need to configure a different set for each VRF greatly
complicates the operations and management. Therefore the use of SSM
for Data MDTs is very strongly recommended.
So the best design in your case is to have PIM-SM (without switchover to the SPT) for the default-MDT and PIM-SSM for the Data-MDT as already explained by Harold. This should be supported by all vendors.
Regarding your SLA, if you are using anycast RP, your convergence time is the same as for PIM-SSM, it relies only on the speed of your IGP to converge.
Assuming you will always use PIM SSM for the DATA MDT, you can use the same pool on all PEs as PIM SSM uses both the multicast address and the source address to identify a given multicast stream. So using the same pool on a all PEs is not an issue as long as the pool is unique on the PE.