mVPN Core Multicast group addresing

[chintan-shah]

Hi,

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 - 239.192.0.0/16 range.

where 239.192.1.1 - default mdt, 239.192.2.0/24 - DATA MDT per customer

same way second customer 239.192.1.2 - default , 239.192.3.0/24 - DATA MDT

2. PIM-SSM : 239.232.0.0/16

customer -1

239.232.1.1 - default mdt

239.232.2.0/24 - data mdt

customer-2

239.232.1.2 - default mdt

293.232.3.0/24- data mdt ..so on.

With this, I have following configuation :

ip pim rp-address 1.1.1.1 SM-RANGE

ip pim ssm range SSM-RANGE

ip access-list standard SSM-RANGE

permit 239.232.0.0 0.0.255.255

ip access-list standard SM-RANGE

permit 239.192.0.0 0.0.255.255

ip vrf VPN-A

description A Customer using MVPN SM

rd 65000:65003

route-target both 65000:65000

mdt default 239.192.1.1

mdt data 239.192.2.0 0.0.0.15 threshold 1

ip vrf VPN-B

description A Customer using MVPN SSM

rd 65000:65011

route-target both 65000:65000

mdt default 239.232.1.1

mdt data 239.232.2.0 0.0.0.15 threshold

ip multicast-routing

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 !!

Regards,

Chintan

Regards,

Chitnan

[Laurent Aubert]

My pleasure ;-)

What you can do is :

239.192.0.0/16 for default-MDT

239.232.0.0/16 for Data-MDT.

For each Default-MDT group, you create a pool of 256 addresses from 239.232.0.0/16

This way you can have up to 256 mVPN

HTH

Laurent.

[chintan-shah]

Thanks agian for your suggestion.

I just had slight modification in terms of allocation while configuring.

1. PIM-SM Default

239.192.0.0/16 - Default MDT

2. PIM-SSM Default

239.232.0.0/24 - Default MDT

3. PIM-SSM DATA

239.232.1.0/24.....so on..

So, I use same 239.232.0.0/16 in SSM ACL used for Default and DATA MDT both but defined proper addressing schema during allocation for customer.

Does it make sense ?

Regards,

Chintan

[Laurent Aubert]

Why do you use PIM-SSM for default-MDT ?

Just use PIM-SM for all your default-MDT.

Laurent.

[chintan-shah]

I had a same in mind but i have been told that PIM-SSM for Default provides better convergance speically where tight SLA is involved so I prefer to use this only when that specific high SLA customer comes. The driver was speically Fast convergance ( sub-second kind of).

Regards,

Chintan

[Laurent Aubert]

Most of the multicast convergence time relies on the convergence time of your IGP so if you are using anycast RP to provide RP redundancy, there should be not difference with PIM-SSM (i'm assuming you are not switching to the SPT)

HTH

Laurent.

[chintan-shah]

Ok, Thanks for you feedback.

I wil plan to test this and SSM both and see the difference. will keep in mind i will have swidtching to SPT when using PIM-SM.

But Does MSDP not involved in convergance imaing two MSDP peer isloadted in core for some time and SA referesh is 60 seconds ?

I will have setup in late June/July start, will keep updating on this.

Regards,

Chintan