[c-nsp] PIM SSM MDT doesn't come up

[Robert Kern]

Hi Munroe,

thanks very much for sharing your experiences. In our case we have BGP-free
core, but what i forgot to mentioned is that we also use MPLS TE what caused
us problems with establishing core MDT group (239.1.1.1) for particular
VPN. After disabling interfering MPLS TE with multicast traffic, core MDT
come up just fine. The customer is checking whether the data flow is correct
now.

The command te dissable MPLS TE and multicast is: (router ospf xxx) mpls
traffic-eng multicast-intact

Thanks again,

Robert


On Mon, Jan 5, 2009 at 9:59 PM, Munroe, James (DSS/MAS) <James.Munroe at gnb.ca
> wrote:

> Hi Robert,
>
> I was down this road a few months ago.  We use Cisco 7600's (RSP720-3C's
> and SUP720-3Bs) as PE's in a large MPLS Metro ring environment.  From
> Day 1 we've used PIM SSM in the Global RT on each PE which has worked
> flawlessly.  However, leveraging PIM SSM for the VRF data planes is
> something I've had little to no success with.  I had tried the TAC call
> approach which basically ended in me going back to PIM SM for the VRF
> data planes...which works well for us.
>
> A couple of things to check is to make sure you have the following in
> place:
> 1.  Each PE/RR configured with the BGP MDT address family using the new
> SAFI format.  I found on the 7k6 platform that using the legacy mVPN
> SAFI in the vpnv4 address family was causing incomplete tunnel creation.
>
> router bgp XXXXXX
> address-family vpnv4
> neighbor Core-RR send-community both
> neighbor 172.16.129.34 activate
> neighbor 172.16.129.35 activate
> exit-address-family
>  !
>  address-family ipv4 mdt
>  neighbor Core-RR send-community extended
>  neighbor 172.16.129.34 activate
>  neighbor 172.16.129.35 activate
>  exit-address-family
>
> ** vpnv4 and mdt address fams should match especially if you've tweaked
> the timers.
>
> 2.  Verify that the GRE tunnels have been created for each mVPN (sh ip
> pim mdt / sh ip pim mdt bgp)  make sure the mdt defaults match and are
> common per vrf per PE and unqiue per vrf.
>
> 3.  PIM SSM is activated for each VRF (ip pim vrf XXXX ssm range XXXX)
>
> I've attached a couple of good Cisco docs for troubleshooting mVPNs.
>
> Hope this helps...
>
> Jim
>
>
> -----Original Message-----
> From: Robert Kern [mailto:cj11st at gmail.com]
> Sent: Monday, January 05, 2009 1:01 AM
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] PIM SSM MDT doesn't come up
>
> Hi all,
>
> We would like to set up mVPN in VRF DataRetention with PIM-SSM in the
> core and in VPN's.
>
> HW setup is following:
>
> receiver----PE1(7k6)-----P1(CRS-1)-----PE2(7k6)----sender
>                           \------P2(CRS-1)----/
>
> PIM-SM is enabled on all physical interfaces and Lo on PE routers, which
> are also used for MP-BGP peering. Core is BGP-free. PIM-SSM range 239/8
> was also done in default and VPN instances. Static IGMPV2 --- IGMPV3
> mapping was done in VRF.
> What I am getting are following mroutes:
>
> C7609_PE1#sh ip mroute
>
> (10.x.x.7, 239.1.1.1), 4d23h/00:02:32, flags: sPT
>  Incoming interface: Loopback0, RPF nbr 0.0.0.0, RPF-MFD
>  Outgoing interface list: Null
>
> (10.x.x.9, 239.1.1.1), 4d23h/stopped, flags: sTIZ
>  * Incoming interface: Null, RPF nbr 0.0.0.0*
>  Outgoing interface list:
>    MVRF DataRetention, Forward/Sparse, 4d23h/00:01:27
>
> (*, 224.0.1.40), 4d23h/00:02:10, RP 0.0.0.0, flags: DCL
>  Incoming interface: Null, RPF nbr 0.0.0.0
>  Outgoing interface list:
>    Loopback0, Forward/Sparse, 4d23h/00:02:10
>
>
> RP/0/RP0/CPU0:CRS1_P1#sh mrib ipv4 route
>
> (*,224.0.0.0/24) Flags: D
>
> (*,224.0.1.39) Flags: S
>
> (*,224.0.1.40) Flags: S
>  Outgoing Interface List
>    TenGigE0/0/5/0 Flags: II LI
>
> *(*,239.0.0.0/8) Flags: D*
>
>
> RP/0/RP0/CPU0:CRS1_P2#sh mrib ipv4 route
>
> (*,224.0.0.0/24) Flags: D
>
> (*,224.0.1.39) Flags: S
>
> (*,224.0.1.40) Flags: S
>  Outgoing Interface List
>    TenGigE0/0/5/0 Flags: II LI
>
> *(*,239.0.0.0/8) Flags: D*
>
>
> C7609_PE2#sh ip mroute
> (10.x.x.9, 239.1.1.1), 5d23h/00:02:34, flags: sPT
>  Incoming interface: Loopback0, RPF nbr 0.0.0.0, RPF-MFD
>  Outgoing interface list: Null
>
> (10.x.x.7, 239.1.1.1), 5d23h/stopped, flags: sTIZ
>  * Incoming interface: Null, RPF nbr 0.0.0.0*
>  Outgoing interface list:
>    MVRF DataRetention, Forward/Sparse, 5d23h/00:00:12
>
> (*, 224.0.1.40), 6d20h/00:02:30, RP 0.0.0.0, flags: DCL
>  Incoming interface: Null, RPF nbr 0.0.0.0
>  Outgoing interface list:
>    Loopback0, Forward/Sparse, 6d20h/00:02:30
>
> What could be the reason, that MDT group 239.1.1.1 is not established
> over the core (PIM-SM on all physical interfaces, PIM-SSM range 239/8)?
>
> Thanks,
>
> Robert
>
>