Adam, Great response. I will confirm that what you say is correct, instead of just believe.
Matt, I am sorry we didn't respond sooner. I had read the message formulated my response but then got distracted with something else and forgot to respond. Regards, Tyson Scott - CCIE #13513 R&S, Security, and SP Managing Partner / Sr. Instructor - IPexpert, Inc. Mailto: [email protected] Telephone: +1.810.326.1444, ext. 208 Live Assistance, Please visit: www.ipexpert.com/chat eFax: +1.810.454.0130 IPexpert is a premier provider of Self-Study Workbooks, Video on Demand, Audio Tools, Online Hardware Rental and Classroom Training for the Cisco CCIE (R&S, Voice, Security & Service Provider) certification(s) with training locations throughout the United States, Europe, South Asia and Australia. Be sure to visit our online communities at www.ipexpert.com/communities and our public website at www.ipexpert.com -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Vitkovsky, Adam Sent: Monday, August 30, 2010 12:10 PM To: [email protected] Subject: Re: [OSL | CCIE_SP] CCIE_SP Digest, Vol 41, Issue 4 Hi Matt, I believe that to have mcast traffic running between R6 and R9 The bottom line is that all routers in both ASNs except R2 and R4 need to believe that the preferred route for the mcast sources is via the R6 and R9 Than: PIM has to be enabled between R6 and R9 MSDP peering would need to be established between R2 and R4 And to have the SourceActive(SA) messages RPF checked successfully -the route for the SA originator (BSR ip address in your case) would need to be known via Multicast BGP For this purpose R2-R4 bgp session would need to be enabled for AFI1/SAFI2 -which is ipv4 multicast address family And BSR ip addresses would need to be advertised under the mcast safi -this would help to pass the first mcast packet from the source to the receiver -after that the igmp designated router will issue the join towards the source following the shortest path building up the source-tree -this path would need to be via R6 and R9 link adam -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, August 26, 2010 6:00 PM To: [email protected] Subject: CCIE_SP Digest, Vol 41, Issue 4 Send CCIE_SP mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://onlinestudylist.com/mailman/listinfo/ccie_sp or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of CCIE_SP digest..." Today's Topics: 1. InterAS Multicast w/MSDP (matt reath) ---------------------------------------------------------------------- Message: 1 Date: Wed, 25 Aug 2010 18:27:50 -0500 From: matt reath <[email protected]> To: ccie_sp <[email protected]> Subject: [OSL | CCIE_SP] InterAS Multicast w/MSDP Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 If I have the following scenario: R4 ------ R6 | | R2 ------ R9 | | R8 ------ R7 R4 and R6 are in one AS R2, R7, R8, and R9 are in another AS I've enabled iBGP ipv4 throughout the two ASs and advertised all loopbacks in ipv4. There is end-to-end IPv4 connectivity between loopbacks. Each AS runs ip pim sparse-mode with BSR, filtered between R2-R4 and R9-R6. R2 and R4 are RPs. What configuration would be required to have multicast between the two ASs? What configuration would be required to have multicast only flow between AS's through R6-R9 and not R4-R2? Is it required to configure pim on the R6-R9 link? -Matt End of CCIE_SP Digest, Vol 41, Issue 4 ************************************** _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
