<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: rp-address clarification needed in Switching</title>
    <link>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350426#M122988</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;And by traffic, you mean the traffic from the source, correct?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 18 Mar 2010 18:24:04 GMT</pubDate>
    <dc:creator>iancarder</dc:creator>
    <dc:date>2010-03-18T18:24:04Z</dc:date>
    <item>
      <title>rp-address clarification needed</title>
      <link>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350422#M122984</link>
      <description>&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying to do a basic config for multicast.&amp;nbsp; I'm configuring this on a Catalyst 4507.&amp;nbsp; I'm going with a shared tree, sparse-dense on the vlan interfaces, and configuring a single static RP.&amp;nbsp; There will be other layer 3 switches involved at some point, all on the same physical network, just with different vlans. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm looking at the software config guide for 12.2(44)SG and there is a command for setting a static rp-address(ip pim rp-address xxx.xxx.xxx.xxx).&amp;nbsp; My question is, I have no idea what that RP address is.&amp;nbsp; Since that core switch is the RP, do I config it as:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip pim rp-address 127.0.0.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If so, what about the other layer 3 switches that are routing traffic?&amp;nbsp; Do I point the RP command towards the management vlan ip for the main core switch?&amp;nbsp; The documentation isn't very clear about this. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Ian&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2019 18:12:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350422#M122984</guid>
      <dc:creator>iancarder</dc:creator>
      <dc:date>2019-03-06T18:12:36Z</dc:date>
    </item>
    <item>
      <title>Re: rp-address clarification needed</title>
      <link>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350423#M122985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The RP address has to be configured (if I remember correctly) on the RP itself as the address that the other devices are using for the RP. So, if your VLAN's SVI is 192.168.16.1, then your RP will be configured as:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip pim rp 192.168.16.1 (not the loopback of 127.0.0.1)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then all of the other devices will also point to 192.168.16.1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can have multiple rp's also, so you *might* (although I've never configured this) look into creating an RP for each of the vlans that you have so you won't have so much multicasting traffic crossing your vlan......&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Mar 2010 17:17:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350423#M122985</guid>
      <dc:creator>John Blakley</dc:creator>
      <dc:date>2010-03-18T17:17:02Z</dc:date>
    </item>
    <item>
      <title>Re: rp-address clarification needed</title>
      <link>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350424#M122986</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the response.&amp;nbsp; If I understand correctly, I can make the RP a gateway address for any vlan?&amp;nbsp; Or in other words, I have vlan 12 which is our server vlan.&amp;nbsp; That vlan has an ip-address of 192.168.12.1(the gateway).&amp;nbsp; I make the rp-address 192.168.12.1 assuming that's the vlan I want it in?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Mar 2010 17:54:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350424#M122986</guid>
      <dc:creator>iancarder</dc:creator>
      <dc:date>2010-03-18T17:54:21Z</dc:date>
    </item>
    <item>
      <title>Re: rp-address clarification needed</title>
      <link>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350425#M122987</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should configure you rp address on whatever interface your traffic will be coming in on....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Mar 2010 18:18:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350425#M122987</guid>
      <dc:creator>John Blakley</dc:creator>
      <dc:date>2010-03-18T18:18:21Z</dc:date>
    </item>
    <item>
      <title>Re: rp-address clarification needed</title>
      <link>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350426#M122988</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;And by traffic, you mean the traffic from the source, correct?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Mar 2010 18:24:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350426#M122988</guid>
      <dc:creator>iancarder</dc:creator>
      <dc:date>2010-03-18T18:24:04Z</dc:date>
    </item>
    <item>
      <title>Re: rp-address clarification needed</title>
      <link>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350427#M122989</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Ian,&lt;/P&gt;&lt;P&gt;best practice is to use a loopback address as RP address.&lt;/P&gt;&lt;P&gt;This address has to be advertised in unicast routing protocol.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Multiple RPs can exist at a given time but only one can act as RP for a given group (with only execption of anycast RP)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To be noted that an RP can act as RP for a subset of multicast address ranges with another device that acts as RP for a different multicast address group.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For redundancy the so called anycast RP can be implemented using MSDP and one between autoRP and bootstrap protocol.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your case if the network is small you can use static RP address configured on all devices.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you choice one device as primary RP and you can configure all devices with that IP address&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;see&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/ios/ipmulti/configuration/guide/imc_basic_cfg_ps6441_TSD_Products_Configuration_Guide_Chapter.html#wp1054581"&gt;http://www.cisco.com/en/US/docs/ios/ipmulti/configuration/guide/imc_basic_cfg_ps6441_TSD_Products_Configuration_Guide_Chapter.html#wp1054581&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope to help&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Mar 2010 18:30:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350427#M122989</guid>
      <dc:creator>Giuseppe Larosa</dc:creator>
      <dc:date>2010-03-18T18:30:56Z</dc:date>
    </item>
    <item>
      <title>Re: rp-address clarification needed</title>
      <link>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350428#M122990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm really struggling to get a basic config going.&amp;nbsp; I feel like I'm probabloy missing a really simple but major concept.&amp;nbsp; Here's the pertinent&amp;nbsp; multicast pieces from my config(4507):&lt;/P&gt;&lt;DIV class="bbc-block code"&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;BR /&gt;ip multicast-routing&lt;BR /&gt;&lt;BR /&gt;....&lt;BR /&gt;&lt;BR /&gt;interface Vlan10&lt;BR /&gt; description Legecy_Network&lt;BR /&gt; ip address 10.0.0.1 255.0.0.0&lt;BR /&gt; ip pim sparse-dense-mode&lt;BR /&gt;!&lt;BR /&gt;interface Vlan11&lt;BR /&gt; description Admin_Data&lt;BR /&gt; ip address 192.168.2.1 255.255.255.0&lt;BR /&gt; ip helper-address 10.1.1.36&lt;BR /&gt; ip pim sparse-dense-mode&lt;BR /&gt;!&lt;BR /&gt;interface Vlan12&lt;BR /&gt; description Admin_Servers&lt;BR /&gt; ip address 192.168.12.1 255.255.255.0&lt;BR /&gt; ip pim sparse-dense-mode&lt;BR /&gt;&lt;BR /&gt;....&lt;BR /&gt;&lt;BR /&gt;ip pim rp-address 192.168.2.1&lt;BR /&gt;ip pim send-rp-discovery scope 16&lt;BR /&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's pretty vanilla.&amp;nbsp; I tried to do a multicast using&amp;nbsp; quicktime's broadcast server on OSX server and it didn't seem to work.&amp;nbsp;&amp;nbsp; Unicast worked fine enough.&amp;nbsp; I also tried testing using tools from this&amp;nbsp; &lt;A href="http://www.29west.com/docs/TestNet/testnet.html" rel="nofollow" target="_blank"&gt;site&lt;/A&gt;.&amp;nbsp; I'm at a loss because I don't&amp;nbsp; know if I've got the initial config screwed up so I can't test anything.&amp;nbsp;&amp;nbsp; Thoughts?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Mar 2010 14:19:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350428#M122990</guid>
      <dc:creator>iancarder</dc:creator>
      <dc:date>2010-03-22T14:19:51Z</dc:date>
    </item>
    <item>
      <title>Re: rp-address clarification needed</title>
      <link>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350429#M122991</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Ian,&lt;/P&gt;&lt;P&gt;you have mixed static RP configuration with Auto RP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;! static RP setting&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;ip pim rp-address 192.168.2.1&lt;BR /&gt;! mapping agent command used by auto RP&lt;BR /&gt;ip pim send-rp-discovery scope 16&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;see&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/ios/solutions_docs/ip_multicast/White_papers/rps.html"&gt;http://www.cisco.com/en/US/docs/ios/solutions_docs/ip_multicast/White_papers/rps.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope to help&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Mar 2010 20:19:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350429#M122991</guid>
      <dc:creator>Giuseppe Larosa</dc:creator>
      <dc:date>2010-03-22T20:19:26Z</dc:date>
    </item>
    <item>
      <title>Re: rp-address clarification needed</title>
      <link>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350430#M122992</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Giuseppe,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I see what you're saying.&amp;nbsp; I need to get rid of that discovery command.&amp;nbsp; I'm thinking the most simple approach is the Anycast RP scenario:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/ios/solutions_docs/ip_multicast/White_papers/rps.html#wp1029526"&gt;http://www.cisco.com/en/US/docs/ios/solutions_docs/ip_multicast/White_papers/rps.html#wp1029526&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Mar 2010 16:18:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350430#M122992</guid>
      <dc:creator>iancarder</dc:creator>
      <dc:date>2010-03-25T16:18:20Z</dc:date>
    </item>
    <item>
      <title>Re: rp-address clarification needed</title>
      <link>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350431#M122993</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've redone my config a bit:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Core/RP multicast relevent snippets:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;ip multicast-routing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface Loopback100&lt;/P&gt;&lt;P&gt; description multicast rp address&lt;/P&gt;&lt;P&gt; ip address 192.168.199.1 255.255.255.255&lt;/P&gt;&lt;P&gt; ip pim sparse-mode&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface Vlan11&lt;BR /&gt; description Admin_Data&lt;BR /&gt; ip address 192.168.2.1 255.255.255.0&lt;BR /&gt; ip helper-address 10.1.1.36&lt;BR /&gt; ip pim sparse-mode&lt;BR /&gt; ip mrm test-sender&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip pim rp-address 192.168.199.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip mrm manager imc1&lt;BR /&gt; manager Vlan11 group 239.255.255.250&lt;BR /&gt; senders 1&lt;BR /&gt; receivers 2 sender-list 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list 1 permit 192.168.2.1&lt;/P&gt;&lt;P&gt;access-list 2 permit 192.168.96.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Remote L3 Switch &lt;/STRONG&gt;&lt;STRONG&gt;multicast relevent snippets:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip multicast-routing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;interface Vlan96&lt;BR /&gt; description MDF_Data_Vlan&lt;BR /&gt; ip address 192.168.96.1 255.255.255.0&lt;BR /&gt; ip helper-address 10.1.1.36&lt;BR /&gt; ip pim sparse-mode&lt;BR /&gt; ip mrm test-receiver&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip pim rp-address 192.168.199.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;SPAN&gt;I used the following doc for the mrm test.&amp;nbsp; &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cftools.html"&gt;http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cftools.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Running "ip mrm status-report" from the rp shows what I'm guessing is 100% percent packet loss although the column is not clear and the documentation doesn't even bother explaining how to interpret the test results.&amp;nbsp; I have no idea if the Group Address(239.255.255.250) I used is correct.&amp;nbsp; I pulled it from the list generated from the "sh ip igmp groups" command. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm extremely frustrated by this.&amp;nbsp; There seem to be tons of multicast documentation from Cisco, but nothing I have read seems to put the whole structure together.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Mar 2010 18:49:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350431#M122993</guid>
      <dc:creator>iancarder</dc:creator>
      <dc:date>2010-03-25T18:49:10Z</dc:date>
    </item>
    <item>
      <title>Re: rp-address clarification needed</title>
      <link>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350432#M122994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Make sure that you can see the loopback from the other switch. You need to be able to route to it (you probably already know this though).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Mar 2010 18:54:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350432#M122994</guid>
      <dc:creator>John Blakley</dc:creator>
      <dc:date>2010-03-25T18:54:49Z</dc:date>
    </item>
    <item>
      <title>Re: rp-address clarification needed</title>
      <link>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350433#M122995</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&amp;nbsp; I was able to ping 192.168.199.1 from the remote L3 switch.&amp;nbsp; I did a traceroute and it used the default route to find it rather than using EIGRP, but as long as I can ping the RP from it, I guess it doesn't really matter how the traffic gets there for my simple setup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As an aside, running the "sh ip igmp groups" command shows 224.0.1.111 reported by 192.168.2.1(the test-sender from the mrm test) and I can even ping that group address from the RP.&amp;nbsp; I changed the "&lt;CODE&gt;ip mrm manager imc1" group address from 239.255.255.250 to 224.0.1.111 with no change in the mrm status report.&amp;nbsp; I'm just shooting blind here now.&lt;BR /&gt;&lt;/CODE&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Mar 2010 19:16:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/rp-address-clarification-needed/m-p/1350433#M122995</guid>
      <dc:creator>iancarder</dc:creator>
      <dc:date>2010-03-25T19:16:00Z</dc:date>
    </item>
  </channel>
</rss>

