Multicast VPN/VRF

[bjberginz]

I have a l3vpn with vrfs and MPLS transport using 3600Xs.  I'm trying to setup Multicast VPN, and I believe that I have the config right.  I've turned on mcast for the vrf, turned on pim-ssm, I have a default mdt for the vrf etc.  The problem is I can't seem to get multicast to travel from PE to PE.  One quirk is that there are no CEs, the layer 3 gateways for the customer equipment are on the 3600Xs, so there is no PIM from a CE, there would just be streams coming into the PEs and IGMP joins.  Is that setup problematic for multicast vpns?

[Luc De Ghein]

Hi,

Multicast in VPN will work, PE-to-PE, without CE routers.

You mention that the Default MDT is up. Do you see the other PE routers as PIM neighbors across the Default MDT (tunnel interface)?

Make sure to enable PIM for the loopback interface on the PE routers.

Otherwise, some output will be needed:

-show ip pim vrf <> neighbor

-show ip mroute vrf <>

-show ip mroute

and the related configuration

Best regards,

Luc

[bjberginz]

That you for the reply Luc, that reminds me I had noted but forgot to mention the lack of PIM neighborship through the tunnel interface.  Both 3600s have tunnel interfaces, both have ip pime sparse-mode configured on their loopbacks. 

show ip mroute vrf

Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.0.1.40), 2d23h/00:02:15, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Tunnel0, Forward/Sparse-Dense, 2d21h/stopped

Looks similar on both.

Show mroute on switch1:

(10.10.10.1, 239.232.0.0), 2d22h/00:02:49, flags: sT
  Incoming interface: Loopback0, RPF nbr 0.0.0.0
  Outgoing interface list:
    TenGigabitEthernet0/2, Forward/Sparse, 1d00h/00:02:49

(10.10.10.4, 239.232.0.0), 2d22h/stopped, flags: sTIZ
  Incoming interface: TenGigabitEthernet0/2, RPF nbr 172.16.0.6
  Outgoing interface list:
    MVRF signals, Forward/Sparse, 2d22h/00:00:17

(*, 224.0.1.40), 2d23h/00:02:57, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Loopback0, Forward/Sparse, 2d00h/00:02:57

On switch 2

(10.10.10.4, 239.232.0.0), 2d22h/00:02:37, flags: sT
  Incoming interface: Loopback0, RPF nbr 0.0.0.0
  Outgoing interface list:
    TenGigabitEthernet0/2, Forward/Sparse, 1d00h/00:02:37

(10.10.10.1, 239.232.0.0), 2d22h/stopped, flags: sTIZ
  Incoming interface: TenGigabitEthernet0/2, RPF nbr 172.16.0.13
  Outgoing interface list:
    MVRF signals, Forward/Sparse, 2d22h/00:01:16

(*, 224.0.1.40), 2d23h/00:02:41, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    TenGigabitEthernet0/2, Forward/Sparse, 1d00h/00:02:41
    TenGigabitEthernet0/1, Forward/Sparse, 2d23h/00:02:07

vrf config, looks the same on both switches:

rd 1.1.1.1:111
mdt default 239.232.0.0
route-target export 1.1.1.1:111
route-target import 1.1.1.1:111

[bjberginz]

I also jsut noticed when I configure the mdt default group I get this error message:

IP MTU not supported on interface Tunnel0

I imaigine that is the source of at least some of the problem, I'll have to try to see why that message is popping up.

[shivjain]

Hi

I can see the S,G entries created. Just for testing purpose, create a loopback and add that loopback in MVPN vrf with IGMP join group.

http://www.mplsvpn.info/2009/05/deploying-testing-of-ssm-in-service.html

regards

shivlu jain

[daniel.dib · Accepted solution]

Check your SDM template. It needs to be sdm prefer video or applications if I remember correctly. It used to be a hidden command. Don't ask me why.

Daniel Dib
CCIE #37149

Please rate helpful posts.

[bjberginz]

sdm prefer applications worked, thanks daniel.