<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Multicast Routing Protocol (Part 2)</title>
	<atom:link href="http://blog.michaelfmcnamara.com/2008/04/multicast-routing-protocol-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.michaelfmcnamara.com/2008/04/multicast-routing-protocol-part-2/</link>
	<description>technology, networking and IP telephony</description>
	<lastBuildDate>Tue, 07 Feb 2012 12:06:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Laurent</title>
		<link>http://blog.michaelfmcnamara.com/2008/04/multicast-routing-protocol-part-2/#comment-5822</link>
		<dc:creator>Laurent</dc:creator>
		<pubDate>Mon, 26 Dec 2011 12:22:13 +0000</pubDate>
		<guid isPermaLink="false">http://maddog.mlhs.org/blog/2008/04/multicast-routing-protocol-part-2/#comment-5822</guid>
		<description>Thanks Michael !</description>
		<content:encoded><![CDATA[<p>Thanks Michael !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/04/multicast-routing-protocol-part-2/#comment-5794</link>
		<dc:creator>Michael McNamara</dc:creator>
		<pubDate>Wed, 21 Dec 2011 20:16:35 +0000</pubDate>
		<guid isPermaLink="false">http://maddog.mlhs.org/blog/2008/04/multicast-routing-protocol-part-2/#comment-5794</guid>
		<description>Hi Laurent,

If you don&#039;t want the Multicast traffic flooding your network then you need to enable IGMP on all Layer 2 switches involved in the traffic between the two Multicast endpoints.

It&#039;s supported, refer to page 22 of the following document - http://support.avaya.com/css/P8/documents/100123708

Cheers!</description>
		<content:encoded><![CDATA[<p>Hi Laurent,</p>
<p>If you don&#8217;t want the Multicast traffic flooding your network then you need to enable IGMP on all Layer 2 switches involved in the traffic between the two Multicast endpoints.</p>
<p>It&#8217;s supported, refer to page 22 of the following document &#8211; <a href="http://support.avaya.com/css/P8/documents/100123708" rel="nofollow">http://support.avaya.com/css/P8/documents/100123708</a></p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laurent</title>
		<link>http://blog.michaelfmcnamara.com/2008/04/multicast-routing-protocol-part-2/#comment-5784</link>
		<dc:creator>Laurent</dc:creator>
		<pubDate>Tue, 20 Dec 2011 10:50:03 +0000</pubDate>
		<guid isPermaLink="false">http://maddog.mlhs.org/blog/2008/04/multicast-routing-protocol-part-2/#comment-5784</guid>
		<description>Thanks a lot !

Concerning IGMP on edge switches, I don&#039;t really understand ...

Do I have to enable IGMP on all layer 2 switches to connect both Multicast receivers and transmitters ? Anf thay said that IGMP traffic is not transported over SMLT ... hum ....

Thanks again !</description>
		<content:encoded><![CDATA[<p>Thanks a lot !</p>
<p>Concerning IGMP on edge switches, I don&#8217;t really understand &#8230;</p>
<p>Do I have to enable IGMP on all layer 2 switches to connect both Multicast receivers and transmitters ? Anf thay said that IGMP traffic is not transported over SMLT &#8230; hum &#8230;.</p>
<p>Thanks again !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laurent</title>
		<link>http://blog.michaelfmcnamara.com/2008/04/multicast-routing-protocol-part-2/#comment-5782</link>
		<dc:creator>Laurent</dc:creator>
		<pubDate>Tue, 20 Dec 2011 10:38:10 +0000</pubDate>
		<guid isPermaLink="false">http://maddog.mlhs.org/blog/2008/04/multicast-routing-protocol-part-2/#comment-5782</guid>
		<description>Thanks a lot !</description>
		<content:encoded><![CDATA[<p>Thanks a lot !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/04/multicast-routing-protocol-part-2/#comment-5754</link>
		<dc:creator>Michael McNamara</dc:creator>
		<pubDate>Fri, 16 Dec 2011 00:00:07 +0000</pubDate>
		<guid isPermaLink="false">http://maddog.mlhs.org/blog/2008/04/multicast-routing-protocol-part-2/#comment-5754</guid>
		<description>You should use a CLIP so your not tied to any single physical interface. If you use say VLAN 1 in your OSPF or PIM configuration and say VLAN 1 goes down you&#039;ll be in trouble. If you use a CLIP then your entire switch would need to go down before you&#039;d have issues with either OSPF or PIM.

You should use BSR preference/priority in combination with a CLIP address.

Just remember you could have multiple Multicast applications running from a single server, so it&#039;s really the application/data stream that you are assigning the Multicast IP address.

Good Luck!</description>
		<content:encoded><![CDATA[<p>You should use a CLIP so your not tied to any single physical interface. If you use say VLAN 1 in your OSPF or PIM configuration and say VLAN 1 goes down you&#8217;ll be in trouble. If you use a CLIP then your entire switch would need to go down before you&#8217;d have issues with either OSPF or PIM.</p>
<p>You should use BSR preference/priority in combination with a CLIP address.</p>
<p>Just remember you could have multiple Multicast applications running from a single server, so it&#8217;s really the application/data stream that you are assigning the Multicast IP address.</p>
<p>Good Luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laurent</title>
		<link>http://blog.michaelfmcnamara.com/2008/04/multicast-routing-protocol-part-2/#comment-5740</link>
		<dc:creator>Laurent</dc:creator>
		<pubDate>Tue, 13 Dec 2011 11:06:41 +0000</pubDate>
		<guid isPermaLink="false">http://maddog.mlhs.org/blog/2008/04/multicast-routing-protocol-part-2/#comment-5740</guid>
		<description>And I have more questions ! :)

If VRRP IP addresses are configured for each VLAN between Edge (5xxx series) and Core (88xx series), should I configure something special concerning CLIP addresses ? Or cbsrpreference can be enough ?

And if I use multiple Multicast servers, should they communicate with a single Multicast address for each of them  (in 239.0.0.0/8 range) ?

Thanks !
Laurent.</description>
		<content:encoded><![CDATA[<p>And I have more questions ! :)</p>
<p>If VRRP IP addresses are configured for each VLAN between Edge (5xxx series) and Core (88xx series), should I configure something special concerning CLIP addresses ? Or cbsrpreference can be enough ?</p>
<p>And if I use multiple Multicast servers, should they communicate with a single Multicast address for each of them  (in 239.0.0.0/8 range) ?</p>
<p>Thanks !<br />
Laurent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laurent</title>
		<link>http://blog.michaelfmcnamara.com/2008/04/multicast-routing-protocol-part-2/#comment-5739</link>
		<dc:creator>Laurent</dc:creator>
		<pubDate>Tue, 13 Dec 2011 10:40:05 +0000</pubDate>
		<guid isPermaLink="false">http://maddog.mlhs.org/blog/2008/04/multicast-routing-protocol-part-2/#comment-5739</guid>
		<description>Hi Michael,

thanks a lot for all your great explanations !

Regarding your example of Multicast Routing, and after hearing of this guide (http://support.avaya.com/css/P8/documents/100123715), I have a question !

They say : &quot;The ERS 5000 does not support IGMP over SMLT/SLT at this time&quot; ... and you said &quot;You could enable IGMP (generally disabled by default) to filter the multicast traffic from ports that are not subscribing to any multicast groups&quot; ...

So, what is the best practice ? I think we have to enable IGMP on all layer 2 switches to connect both Multicast receivers and transmitters ... but if IGMP traffic is not transported over SMLT, how can we do ?

Am I wrong ?

Thanks a lot !

Cheers !
Laurent.</description>
		<content:encoded><![CDATA[<p>Hi Michael,</p>
<p>thanks a lot for all your great explanations !</p>
<p>Regarding your example of Multicast Routing, and after hearing of this guide (<a href="http://support.avaya.com/css/P8/documents/100123715" rel="nofollow">http://support.avaya.com/css/P8/documents/100123715</a>), I have a question !</p>
<p>They say : &#8220;The ERS 5000 does not support IGMP over SMLT/SLT at this time&#8221; &#8230; and you said &#8220;You could enable IGMP (generally disabled by default) to filter the multicast traffic from ports that are not subscribing to any multicast groups&#8221; &#8230;</p>
<p>So, what is the best practice ? I think we have to enable IGMP on all layer 2 switches to connect both Multicast receivers and transmitters &#8230; but if IGMP traffic is not transported over SMLT, how can we do ?</p>
<p>Am I wrong ?</p>
<p>Thanks a lot !</p>
<p>Cheers !<br />
Laurent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PIM-SM on Avaya Ethernet Routing Switch 5000 &#124; Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/04/multicast-routing-protocol-part-2/#comment-4430</link>
		<dc:creator>PIM-SM on Avaya Ethernet Routing Switch 5000 &#124; Michael McNamara</dc:creator>
		<pubDate>Fri, 24 Jun 2011 10:01:32 +0000</pubDate>
		<guid isPermaLink="false">http://maddog.mlhs.org/blog/2008/04/multicast-routing-protocol-part-2/#comment-4430</guid>
		<description>[...] the Avaya Ethernet Routing Switch 5000 series. While I&#8217;ve written in the past about DVMRP and PIM-SM on the Ethernet Routing Switch 8600 in I&#8217;ve never written about running PIM-SM on any of the [...]</description>
		<content:encoded><![CDATA[<p>[...] the Avaya Ethernet Routing Switch 5000 series. While I&#8217;ve written in the past about DVMRP and PIM-SM on the Ethernet Routing Switch 8600 in I&#8217;ve never written about running PIM-SM on any of the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael McNamara</title>
		<link>http://blog.michaelfmcnamara.com/2008/04/multicast-routing-protocol-part-2/#comment-3434</link>
		<dc:creator>Michael McNamara</dc:creator>
		<pubDate>Fri, 14 Jan 2011 19:42:15 +0000</pubDate>
		<guid isPermaLink="false">http://maddog.mlhs.org/blog/2008/04/multicast-routing-protocol-part-2/#comment-3434</guid>
		<description>Hi Wyllen,

As I replied on the forums I don&#039;t believe v3.2.x software for the ERS 8600 support circuitless IP interfaces (CLIPs).

Cheers!</description>
		<content:encoded><![CDATA[<p>Hi Wyllen,</p>
<p>As I replied on the forums I don&#8217;t believe v3.2.x software for the ERS 8600 support circuitless IP interfaces (CLIPs).</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wyllen</title>
		<link>http://blog.michaelfmcnamara.com/2008/04/multicast-routing-protocol-part-2/#comment-3432</link>
		<dc:creator>Wyllen</dc:creator>
		<pubDate>Fri, 14 Jan 2011 14:31:21 +0000</pubDate>
		<guid isPermaLink="false">http://maddog.mlhs.org/blog/2008/04/multicast-routing-protocol-part-2/#comment-3432</guid>
		<description>Hello,

Is it possible to know what 8600&#039;s  version software did you used, because I try to add CLIP interface as you, but it told me :  &quot; config ip &quot;circuitless-ip-int&quot; not found in path /PP8606:6/config/ip</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>Is it possible to know what 8600&#8242;s  version software did you used, because I try to add CLIP interface as you, but it told me :  &#8221; config ip &#8220;circuitless-ip-int&#8221; not found in path /PP8606:6/config/ip</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Served from: blog.michaelfmcnamara.com @ 2012-02-08 17:38:10 by W3 Total Cache -->
