[c-nsp] Partitioned-MDT MP2MP with BGP-AD/mLDP in XR 4.3
Adam Vitkovsky
adam.vitkovsky at swan.sk
Tue Nov 26 04:41:47 EST 2013
Hi Jason,
I'd love to see the working config as the Partitioned-MDT MP2MP with
BGP-AD/mLDP is what I plan to roll out once me3600 will support that as
well.
I don't understand how come pim rpf topol is not the attach point for
"c-multicast-routing" command where else would I use a policy-map with this
parameter?
And regarding the "mdt default mldp ipv4
Thinking about it again the mp2mp LSP for the default tree can be build
towards any PE(s) if it'll be mp2mp it has the same effect as if there was a
central point(s).
adam
-----Original Message-----
From: Jason Lixfeld [mailto:jason at lixfeld.ca]
Sent: Monday, November 25, 2013 4:12 PM
To: Adam Vitkovsky
Cc: <cisco-nsp at puck.nether.net>
Subject: Re: [c-nsp] Partitioned-MDT MP2MP with BGP-AD/mLDP in XR 4.3
Hi Adam,
I saw the same slide deck. I based some of my configs off of it initially.
I tried those two options previously and neither passed the commit. There
seems to be so much conflicting information on what's supported in what mode
and what's not that I can't really get a firm grasp. My brain doesn't
absorb all the info in the RFCs well enough to really be able to determine
what's what either. I've reached out to TAC and my SE anyway, but I thought
I'd check here to see what's going on in the real world.
In any event, here are the errors associated with both commands:
RP/0/RSP0/CPU0:bfr01.905KingStW01.YYZ(config)#show configuration failed Mon
Nov 25 09:21:40.899 EST !! SEMANTIC ERRORS: This configuration was rejected
by !! the system due to semantic errors. The individual !! errors with each
failed configuration command can be !! found below.
!
route-policy MLDP-TV
set core-tree mldp-partitioned-p2mp
set c-multicast-routing bgp
end-policy
!
!!% Policy [MLDP-TV] uses the 'c-multicast-routing' attribute. There is no
'c-multicast-routing' attribute at the pim rpf-topology attach point.
end
..
RP/0/RSP0/CPU0:bfr01.905KingStW01.YYZ(config)#show configuration failed Mon
Nov 25 09:22:57.235 EST !! SEMANTIC ERRORS: This configuration was rejected
by !! the system due to semantic errors. The individual !! errors with each
failed configuration command can be !! found below.
multicast-routing
vrf tv
address-family ipv4
mdt default mldp ipv4 172.16.0.32
!!% Invalid MLDP MDT type: MDT Default MLDP (Rosen MLDP) cannot co-exist
with In-Band MLDP, Partitioned MDT MLDP, or MDT Default MLDP P2MP
!
!
!
end
On Nov 25, 2013, at 4:22 AM, Adam Vitkovsky <adam.vitkovsky at swan.sk> wrote:
> Hi Jason,
> Just shooting in the dark,
> I'd try adding these:
>
> route-policy MLDP-TV
> set c-multicast-routing bgp
>
>
> multicast-routing
> vrf tv
> address-family ipv4
> interface TenGigE0/0/0/15
> enable
> !
> mdt default mldp ipv4 x.x.x.x
> mdt data 100
>
>
> I find this presentation useful:
> NG (Next Gen) MVPN Webinar -I have found it on slideshare, it has 90
slides.
>
>
> adam
>
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf
> Of Jason Lixfeld
> Sent: Friday, November 22, 2013 8:35 PM
> To: <cisco-nsp at puck.nether.net>
> Subject: [c-nsp] Partitioned-MDT MP2MP with BGP-AD/mLDP in XR 4.3
>
> Hi all,
>
> I've been working on trying to get LSM working between a couple of
> A9Ks to support a SSM based IPTV application.
>
> After ingesting a bunch of content on the subject, I think what I want
> is Partitioned MDT, MP2MP with BGP-AD/mLDP (PIM-free core). I'm
> wondering if anyone has any links to working configuration examples
> for this type of MVPN or some good troubleshooting guides for this type of
MVPN specifically.
>
> The XR 4.3 configuration guide seems to provide either a broken or an
> incomplete example, so what I've managed to work out from it, doesn't
> seem to work.
>
> By 'doesn't seem to work', I mean I have a SSM based join-group
> configured on a CE with a PIM adjacency to XR PE1. XR PE1 sees the
> (S,G) from the CE, but the adjacent XR PE2 (config below) doesn't see it.
>
> Thanks in advance for any pointers.
>
> !
> interface Loopback0
> ipv4 address 72.15.48.4 255.255.255.255 !
> interface Loopback2022
> vrf tv
> ipv4 address 172.16.0.32 255.255.255.255 !
> interface TenGigE0/0/0/15
> description Facing Source
> vrf tv
> ipv4 address 172.16.1.1 255.255.255.0
> !
> interface TenGigE0/0/0/0
> description Facing Core
> cdp
> mtu 9216
> ipv4 address 72.15.49.80 255.255.255.254 carrier-delay up 0 down 0
> dampening !
> router bgp 21949
> address-family ipv4 unicast
> !
> address-family vpnv4 unicast
> !
> address-family ipv4 mvpn
> !
> neighbor-group P-MVPN
> remote-as 21949
> update-source Loopback0
> address-family vpnv4 unicast
> !
> address-family vpnv6 unicast
> !
> address-family ipv4 mvpn
> !
> neighbor 72.15.48.10
> use neighbor-group P-MVPN
> !
> vrf tv
> rd 21949:2022
> address-family ipv4 unicast
> redistribute connected route-policy SOURCE--INTERNAL-CONNECTED
> redistribute static route-policy SOURCE--INTERNAL-STATIC !
> address-family ipv4 mvpn
> !
> !
> !
> multicast-routing
> address-family ipv4
> interface TenGigE0/0/0/0
> enable
> !
> nsf
> mdt source Loopback0
> rate-per-route
> accounting per-prefix
> !
> vrf tv
> address-family ipv4
> mdt source Loopback2022
> mdt partitioned mldp ipv4 mp2mp
> rate-per-route
> interface all enable
> bgp auto-discovery mldp
> !
> accounting per-prefix
> !
> !
> !
> mpls ldp
> router-id Loopback0
> graceful-restart
> session protection
> log
> neighbor
> graceful-restart
> session-protection
> !
> mldp
> logging notifications
> !
> interface TenGigE0/0/0/0
> !
> !
> router pim
> vrf tv
> address-family ipv4
> rpf topology route-policy MLDP-TV
> interface TenGigE0/0/0/15
> enable
> !
> !
> !
> !
> route-policy MLDP-TV
> set core-tree mldp-partitioned-mp2mp
> end-policy
> !
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list