Please help me on a side-note.... I've been wondering, what makes ssm ssm? I mean here's what I was seeing....
I have several mcast groups in my network currently...all 239.x.x.x Thus far my mcast network was simply ... Mcast xmitter------>asr9k----------------asr9k----------mcast rcvr That's it. Just a 2 router network with asr9k's directly connected in the middle with the source and destination of mcast traffic directly connected to both the respective asr9k's. I now want to virtualize that traffic from source to destination in a L3VPN (mcast enabled of course, which I believe makes it a mvpn by definition) but before proceeding just want to understand what I have currently. If I type "sh pim gr" I see all of the groups as "SM". Interestingly I have *NO* rp defined in my 2 mcast routers currently. Isn't it a well know fact that you can not accomplish pim sm without an rp ??! (that's why I have my doubts that "sh pim gr" is telling me the truth, but please tell me if I'm wrong) I did a test sending mcast to 239.0.6.1, I added a third mcast router to join that 239.0.6.1 group. It showed up as pim sm in "sh pim gr". I then changed ONLY that third router's config to have a new ssm range of 239.0.6.0/24 and then now "sh pim gr" shows that as a SSM group. The p and xmitting pe routers still show that group as SM. So which is it SM or SSM ? Here's what I saw on the third router that I'm joining 239.0.6.1 on. conf router igmp interface bvI 2 static-group 239.0.6.1 192.168.107.204 commit ...shows as SM. (192.168.107.204,239.0.6.1)SPT SM Up: 00:00:50 JP: Join(now) RPF: Bundle-Ether1,10.101.1.49 Flags: Up: MT clr (00:00:00) MDT: JoinSend N, Cache N/N, Misc (0x0,0/0) Cache: Add 00:00:00, Rem 00:00:00. MT Cnt: Set 0, Unset 0. Joins sent 0 MDT-ifh 0x0/0x0 MT Slot none/ none RPF Table: IPv4-Unicast-default BVI2 00:00:50 fwd LI AS(self,00:02:54) LH 224.0.1.39/32* DM perm 0 0.0.0.0 224.0.1.40/32* DM perm 1 0.0.0.0 224.0.0.0/24* NO perm 0 0.0.0.0 232.0.0.0/8* SSM config 0 0.0.0.0 224.0.0.0/4* SM static 1 0.0.0.0 RPF: Null,0.0.0.0 delete static join... then.... ssm range testssm239.0.6 ipv4 access-list testssm239.0.6 10 permit ipv4 239.0.6.0 0.0.0.255 any multicast-routing address-family ipv4 ssm range testssm239.0.6 commi re-added static join... ....shows as SSM. Transit p and source pe still show this group as SM. (192.168.107.204,239.0.6.1)SPT SSM Up: 00:00:51 JP: Join(now) RPF: Bundle-Ether1,10.101.1.49 Flags: Up: MT clr (00:00:00) MDT: JoinSend N, Cache N/N, Misc (0x0,0/0) Cache: Add 00:00:00, Rem 00:00:00. MT Cnt: Set 0, Unset 0. Joins sent 0 MDT-ifh 0x0/0x0 MT Slot none/ none RPF Table: IPv4-Unicast-default BVI2 00:00:51 fwd LI AS(self,00:02:54) LH 224.0.1.39/32* DM perm 0 0.0.0.0 224.0.1.40/32* DM perm 1 0.0.0.0 224.0.0.0/24* NO perm 0 0.0.0.0 239.0.6.0/24* SSM config 1 0.0.0.0 224.0.0.0/4* SM static 0 0.0.0.0 RPF: Null,0.0.0.0 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Phil Mayers Sent: Tuesday, May 29, 2012 10:11 AM To: [email protected] Subject: Re: [c-nsp] m-vpn On 29/05/12 15:55, Aaron wrote: > Hi all, > > > > I've read through Chapter 7 of "MPLS and VPN Architectures Volume II" > regarding Multicast VPN. > > > > I never saw any mention of enabling the ipv4 mdt address family under bgp. > Is this ipv4 mdt af something altogether different than what is spoken > of in the book ? .or did I totally miss something in that chapter > about the ipv4 mdt af being implicitly enable somehow. > > > > I'm just trying to accomplish mcast over my mpls L3VPN. This will be > for my draft-rosen, yes? > high capacity mcast for catv for all my catv subscribers. 2-3 gbps > sustained 24x7. A couple different pe/ce will xmit and a couple > different pe/ce will rcv. I'd prefer to use ssm cause I don't wanna > mess with rp's In that case, you want the "mdt" SAFI under the BGP stanza, appropriately route-reflected. The "mdt" SAFI basically lets you discover other PEs in the MVPN. This is not necessary with ASM MVPN groups as the *,g tree allows discover. This was accomplished in earlier versions of IOS using so-called type-2 RDs, but the MDT SAFI replaces that (and is in turn replaced in NG-MVPN) > and sup-optimal routing to and from rp and single point of failure on > rp (so I don't wanna mess with redundant rp either if I can simply do > ssm) SSM works fine. Just enable the "mft" SAFI. I only holds one route per PE/MVPN combo. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
