<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Topic &#x27;Multicast&#x27; in forum &#x27;Cisco&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Multicast-22674133</link>
<description></description>
<language>en</language>
<pubDate>Fri, 10 Feb 2012 06:11:48 EDT</pubDate>
<lastBuildDate>Fri, 10 Feb 2012 06:11:48 EDT</lastBuildDate>

<item>
<title>Re: Multicast</title>
<link>http://www.dslreports.com/forum/Re-Multicast-22687074</link>
<description><![CDATA[aryoba posted : Without seeing the configuration of all related devices, it would be hard to say what is what :)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Multicast-22687074</guid>
<pubDate>Fri, 10 Jul 2009 14:57:06 EDT</pubDate>
</item>

<item>
<title>Re: Multicast</title>
<link>http://www.dslreports.com/forum/Re-Multicast-22685623</link>
<description><![CDATA[anon posted : all of them? because I have around 16 devices that this is going over. 4 at each site, with duplicate devices for failover. <br><br>I'm mainly concerned with this ASA right now because according to this cisco <A HREF="http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807631d2.shtml">tutorial</a> (scroll towards the bottom) you can capture multicast both outgoing and incoming. When I setup capturing on my asa I only see the incoming, and it's getting dropped before it gets sent out for some reason.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Multicast-22685623</guid>
<pubDate>Fri, 10 Jul 2009 11:30:17 EDT</pubDate>
</item>

<item>
<title>Re: Multicast</title>
<link>http://www.dslreports.com/forum/Re-Multicast-22685550</link>
<description><![CDATA[aryoba posted : Can you also post full configuration of other devices (routers and switches)? This is to make sure that everything is in place.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Multicast-22685550</guid>
<pubDate>Fri, 10 Jul 2009 11:18:16 EDT</pubDate>
</item>

<item>
<title>Re: Multicast</title>
<link>http://www.dslreports.com/forum/Re-Multicast-22684689</link>
<description><![CDATA[anon posted : rolande, you would think that you would have to setup PIM on the interfaces just like a switch or router, right? Well the ASA doesn't really have that option<br><br>ex:<br><br><pre class="brush: text">asa1(config-if)# pim ?&#012; &#012;interface mode commands/options:&#012;  bidir-neighbor-filter  PIM bidir capable peering filter&#012;  dr-priority            PIM Hello DR priority&#012;  hello-interval         PIM neighbor Hello announcement interval&#012;  join-prune-interval    PIM periodic Join-Prune announcement interval&#012;  neighbor-filter        PIM peering filter&#012;  &lt;cr&gt;&#012; &#012;configure mode commands/options:&#012;  accept-register        Register accept filter&#012;  old-register-checksum  Generate registers compatible with older IOS versions&#012;  rp-address             Configure Sparse-Mode Rendezvous Point&#012;  spt-threshold          Configure threshold for SPT switchover on last-hop&#012; &#012;</pre><!--end code block--><br>here's most of the ASA config (omitted certain parts because it is lengthy)<br><br><pre class="brush: text">ASA Version 8.0(2)&#012;!&#012;hostname asa1&#012;domain-name mapcommunications.com&#012;enable password xxxxxxxxx  encrypted&#012;multicast-routing&#012;no names&#012;dns-guard&#012;!&#012;interface GigabitEthernet0/0&#012; nameif Outside&#012; security-level 0&#012; ip address 192.168.22.1 255.255.255.0 standby 192.168.22.2&#012;!&#012;interface GigabitEthernet0/1&#012; nameif Inside&#012; security-level 100&#012; ip address 192.168.21.1 255.255.255.248 standby 192.168.21.2&#012;!&#012;interface GigabitEthernet0/2&#012; description LAN/STATE Failover Interface&#012;!&#012;interface GigabitEthernet0/3&#012; nameif DMZ&#012; security-level 50&#012; ip address 192.168.26.1 255.255.255.0&#012;!&#012;interface Management0/0&#012; nameif Management&#012; security-level 100&#012; ip address 192.168.2.75 255.255.255.0 standby 192.168.2.76&#012;!&#012;pim rp-address 192.168.22.4&#012;!&#012;time-range AfterHours&#012; absolute start 15:00 13 May 2008&#012; periodic daily 0:00 to 8:59&#012; periodic daily 11:30 to 23:59&#012;boot system disk0:/asa802-k8.bin&#012;ftp mode passive&#012;clock timezone EST -5&#012;clock summer-time EDT recurring&#012;dns server-group DefaultDNS&#012; domain-name mapcommunications.com&#012;same-security-traffic permit inter-interface&#012;same-security-traffic permit intra-interface&#012;access-list outside_access_in extended permit ip any 192.168.26.0 255.255.255.0&#012;access-list outside_access_in extended permit icmp any any&#012;access-list outside_access_in extended permit ip any host 225.0.0.1&#012;access-list outside_access_in extended permit ip any host 225.0.0.2&#012;access-list outside_access_in extended permit ip any host 224.0.0.39&#012;access-list outside_access_in extended permit ip any host 224.0.0.40&#012;access-list outside_access_in extended deny ip any any&#012;access-list DMZ_access_in extended permit ip any any&#012;access-list Inside_access_in extended permit ip any 192.168.26.0 255.255.255.0&#012;access-list Inside_access_in extended permit ip any host 225.0.0.1&#012;access-list Inside_access_in extended permit ip any any&#012;access-list DefaultRAGroup_splitTunnelAcl standard permit any&#012;access-list DMZ_nat_static extended permit ip host 192.168.26.145 any&#012;access-list DMZ_nat_static_1 extended permit ip host 192.168.26.143 any&#012;access-list syslog extended permit udp any host 172.16.16.254 eq syslog&#012;access-list tac extended permit ip any host 172.16.25.23&#012;access-list tac extended permit ip host 172.16.25.23 any&#012;access-list tac1 extended permit igmp any any&#012;access-list capture extended permit ip any host 225.0.0.1&#012;access-list capture extended permit ip any host 225.0.0.2&#012;access-list split_tunnel extended permit ip 192.168.36.0 255.255.255.128 any&#012;pager lines 24&#012;logging enable&#012;logging buffer-size 65536&#012;logging asdm-buffer-size 512&#012;logging monitor warnings&#012;logging buffered warnings&#012;logging trap errors&#012;logging asdm notifications&#012;logging host Inside 172.16.0.254&#012;logging class rip trap debugging&#012;logging rate-limit 1 60 level 0&#012;logging rate-limit 1 60 level 1&#012;logging rate-limit 1 60 level 2&#012;logging rate-limit 1 60 level 3&#012;logging rate-limit 1 60 level 4&#012;logging rate-limit 1 60 level 5&#012;logging rate-limit 1 60 level 6&#012;logging rate-limit 1 60 level 7&#012;logging rate-limit 1 10800 message 410001&#012;logging rate-limit 1 10800 message 313005&#012;logging rate-limit 1 10800 message 106023&#012;logging rate-limit 1 10800 message 106100&#012;logging rate-limit 1 10800 message 733100&#012;mtu Outside 1500&#012;mtu Inside 1500&#012;mtu DMZ 1500&#012;mtu Management 1500&#012;ip local pool RemoteAccess 192.168.36.2-192.168.36.127 mask 255.255.255.128&#012;failover&#012;failover lan unit primary&#012;failover lan interface Failover GigabitEthernet0/2&#012;failover link Failover GigabitEthernet0/2&#012;icmp unreachable rate-limit 1 burst-size 1&#012;asdm image disk0:/asdm-602.bin&#012;asdm history enable&#012;arp timeout 14400&#012;nat (Inside) 0 access-list any&#012;static (DMZ,Inside) x.x.x.x  access-list DMZ_nat_static_2&#012;static (DMZ,Inside) x.x.x.x  access-list DMZ_nat_static&#012;static (DMZ,Inside) x.x.x.x  access-list DMZ_nat_static_1&#012;access-group outside_access_in in interface Outside&#012;access-group Inside_access_in in interface Inside&#012;access-group DMZ_access_in in interface DMZ&#012;access-group Management_access_in in interface Management&#012;!&#012;router rip&#012; network 192.168.21.0&#012; network 192.168.22.0&#012; network 192.168.26.0&#012; network 192.168.36.0&#012; passive-interface DMZ&#012; passive-interface Management&#012; version 2&#012; no auto-summary&#012;!&#012;route Inside 10.100.200.0 255.255.255.0 192.168.21.3 1&#012;timeout xlate 3:00:00&#012;timeout conn 24:12:00 half-closed 24:12:00 udp 0:10:00 icmp 0:00:05&#012;timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00&#012;timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00&#012;timeout uauth 0:05:00 absolute&#012;dynamic-access-policy-record DfltAccessPolicy&#012;aaa-server vpn protocol ldap&#012;aaa authentication telnet console LOCAL&#012;aaa authentication ssh console LOCAL&#012;http server enable&#012;http 10.100.200.0 255.255.255.0 DMZ&#012;http 172.16.16.0 255.255.240.0 Inside&#012;http 192.168.2.69 255.255.255.255 Management&#012;http 172.16.25.23 255.255.255.255 Inside&#012;http 172.16.25.3 255.255.255.255 Inside&#012;http 172.16.0.0 255.255.128.0 Outside&#012;http 10.100.200.0 255.255.255.0 Inside&#012;snmp-server host Inside 172.16.0.254 community nonpublic version 2c&#012;snmp-server host Inside 172.16.16.254 community nonpublic version 2c&#012;no snmp-server location&#012;no snmp-server contact&#012;crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac&#012;crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac&#012;crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac&#012;crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac&#012;crypto ipsec transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac&#012;crypto ipsec transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac&#012;crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac&#012;crypto ipsec transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac&#012;crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set pfs&#012;crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5 TRANS_ESP_AES-256_SHA&#012;crypto map Outside_map 1 match address Outside_cryptomap_1&#012;crypto map Outside_map 1 set peer 192.168.37.1&#012;crypto map Outside_map 1 set transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5&#012;crypto map Outside_map 2 match address Outside_cryptomap_2&#012;crypto map Outside_map 2 set peer 192.168.57.2&#012;crypto map Outside_map 2 set transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5&#012;crypto map Outside_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP&#012;crypto isakmp enable Outside&#012;crypto isakmp enable Inside&#012;crypto isakmp enable DMZ&#012;crypto isakmp policy 10&#012; authentication pre-share&#012; encryption des&#012; hash sha&#012; group 2&#012; lifetime 86400&#012;crypto isakmp policy 30&#012; authentication pre-share&#012; encryption 3des&#012; hash sha&#012; group 2&#012; lifetime 86400&#012;crypto isakmp policy 40&#012; authentication pre-share&#012; encryption 3des&#012; hash md5&#012; group 2&#012; lifetime 43200&#012;no crypto isakmp nat-traversal&#012;client-update enable&#012;telnet 172.16.25.4 255.255.255.255 Inside&#012;telnet timeout 60&#012;ssh 172.16.25.23 255.255.255.255 Inside&#012;ssh 172.16.25.4 255.255.255.255 Inside&#012;ssh timeout 15&#012;console timeout 0&#012;management-access Management&#012;vpn load-balancing&#012; interface lbpublic DMZ&#012; interface lbprivate DMZ&#012;threat-detection basic-threat&#012;threat-detection statistics&#012;!&#012;class-map inspection_default&#012; match default-inspection-traffic&#012;!&#012;!&#012;policy-map type inspect ipsec-pass-thru Pass-Through&#012; description IPSEC Pass-Through inspection map&#012; parameters&#012;  esp timeout 0:45:00&#012;  ah timeout 0:45:00&#012;policy-map type inspect dns migrated_dns_map_1&#012; parameters&#012;  message-length maximum 556&#012;policy-map global_policy&#012; class inspection_default&#012;  inspect dns migrated_dns_map_1&#012;  inspect ftp&#012;  inspect h323 h225&#012;  inspect h323 ras&#012;  inspect netbios&#012;  inspect rsh&#012;  inspect rtsp&#012;  inspect skinny&#012;  inspect esmtp&#012;  inspect sqlnet&#012;  inspect sunrpc&#012;  inspect tftp&#012;  inspect sip&#012;  inspect xdmcp&#012;  inspect ipsec-pass-thru Pass-Through&#012;  inspect pptp&#012;!&#012;service-policy global_policy global&#012;tftp-server Inside 172.16.17.58 /&#012;group-policy DefaultRAGroup attributes&#012; vpn-tunnel-protocol l2tp-ipsec&#012; split-tunnel-policy tunnelspecified&#012; split-tunnel-network-list value DefaultRAGroup_splitTunnelAcl&#012;group-policy DfltGrpPolicy attributes&#012;group-policy vpn_client internal&#012;group-policy vpn_client attributes&#012; dns-server value 172.16.17.55 172.16.17.56&#012; vpn-tunnel-protocol IPSec&#012; split-tunnel-policy tunnelspecified&#012; split-tunnel-network-list value split_tunnel&#012; address-pools value RemoteAccess&#012;tunnel-group DefaultRAGroup general-attributes&#012; address-pool RemoteAccess&#012; default-group-policy DefaultRAGroup&#012;tunnel-group DefaultRAGroup ipsec-attributes&#012; pre-shared-key *&#012;tunnel-group 192.168.37.1 type ipsec-l2l&#012;tunnel-group 192.168.37.1 ipsec-attributes&#012; pre-shared-key *&#012;tunnel-group 192.168.57.2 type ipsec-l2l&#012;tunnel-group 192.168.57.2 ipsec-attributes&#012; pre-shared-key *&#012;tunnel-group vpn_client type remote-access&#012;tunnel-group vpn_client general-attributes&#012; default-group-policy vpn_client&#012;tunnel-group vpn_client ipsec-attributes&#012; pre-shared-key *&#012;prompt hostname context&#012;Cryptochecksum:5dd0ec8785525ef2360bba4f853e301f&#012;: end&#012; &#012;</pre><!--end code block-->]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Multicast-22684689</guid>
<pubDate>Fri, 10 Jul 2009 09:18:55 EDT</pubDate>
</item>

<item>
<title>Re: Multicast</title>
<link>http://www.dslreports.com/forum/Re-Multicast-22683413</link>
<description><![CDATA[rolande posted : I would be most interested to see the full ASA config as that is where the packets seem to disappear. I don't believe you should have to statically join groups on the ASA interfaces to make it work if it is properly participating in PIM. You have enabled multicast-routing but don't you have to enable PIM on each interface you want to participate in the multicast path?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Multicast-22683413</guid>
<pubDate>Thu, 09 Jul 2009 23:10:18 EDT</pubDate>
</item>

<item>
<title>Re: Multicast</title>
<link>http://www.dslreports.com/forum/Re-Multicast-22678972</link>
<description><![CDATA[aryoba posted : Please post configuration of ALL devices (routers, switches, and ASA).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Multicast-22678972</guid>
<pubDate>Thu, 09 Jul 2009 10:50:52 EDT</pubDate>
</item>

<item>
<title>Re: Multicast</title>
<link>http://www.dslreports.com/forum/Re-Multicast-22678396</link>
<description><![CDATA[anon posted : #sh capture capin<br>18 packets captured<br>   1: 09:28:39.808857 172.16.32.52.1853 > 225.0.0.1.6110:  udp 136<br>   2: 09:28:39.878860 172.16.32.52.1854 > 225.0.0.1.6100:  udp 136<br>   3: 09:28:40.178915 172.16.32.52.1852 > 225.0.0.1.6080:  udp 100<br>   4: 09:28:40.808918 172.16.32.52.1856 > 225.0.0.1.6120:  udp 82<br>   5: 09:28:40.808918 172.16.32.52.1855 > 225.0.0.1.6130:  udp 82<br>   6: 09:28:40.868927 172.16.32.52.1847 > 225.0.0.1.6070:  udp 1112<br>   7: 09:28:41.808994 172.16.32.52.1849 > 225.0.0.1.6030:  udp 1164<br><br>#sh capture capout <br>capture capout type raw-data access-list capture interface outside [Capturing - 0 bytes]<br><br>#sh run | grep multi<br>multicast-routing<br><br>asa1-suff-va(config)# sh run interface g0/0<br>!<br>interface GigabitEthernet0/0<br> nameif outside<br> security-level 0<br> ip address 192.168.x.x 255.255.255.0<br> igmp join-group 225.0.0.1<br><br>asa1-suff-va(config)# sh run interface g0/1<br>!<br>interface GigabitEthernet0/1<br> nameif inside<br> security-level 100<br> ip address 192.168.x.x 255.255.255.248 standby 192.168.x.x<br> igmp join-group 225.0.0.1<br><br>asa1-suff-va(config)# sh run | grep pim<br>pim rp-address 192.168.x.x<br><br>So I'm pretty much stumped. Multicast is running, everything looks like it should work, but as you can see none of the multicast packets are exiting the ASA's interface.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Multicast-22678396</guid>
<pubDate>Thu, 09 Jul 2009 09:45:43 EDT</pubDate>
</item>

<item>
<title>Re: Multicast</title>
<link>http://www.dslreports.com/forum/Re-Multicast-22675194</link>
<description><![CDATA[anon posted : I joined my ASA to the igmp group 225.0.0.1 on both inside and outside interface. I captured all data destined for 225.0.0.1 on my outside interface and this is all that shows<br><br>3 packets captured<br>   1: 18:22:26.279129 ASA_IP > 225.0.0.1:  ip-proto-2, length 8<br>   2: 18:24:20.036268 ASA_IP > 225.0.0.1:  ip-proto-2, length 8<br>   3: 18:24:23.786458 ASA_IP > 225.0.0.1:  ip-proto-2, length 8<br>3 packets shown<br><br>those are just because I joined the IGMP group on the outside interface, so obviously the multicast is not getting through, but again, i have no clue why.<br><br>I don't have any bidi filters, or neighbor filters on. When I do a sh pim neighb everything looks right. It shows the neighbors both outside and in.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Multicast-22675194</guid>
<pubDate>Wed, 08 Jul 2009 17:26:30 EDT</pubDate>
</item>

<item>
<title>Re: Multicast</title>
<link>http://www.dslreports.com/forum/Re-Multicast-22674731</link>
<description><![CDATA[anon posted : I think I've isolated the problem to the ASA. PIM is enabled, and so is multicast routing, and they're pointed to the rp. But it doesn't look like the 225.0.0.1 traffic is passing through.<br><br>I've also ensured that 225.0.0.1 traffic is allowed through the firewall.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Multicast-22674731</guid>
<pubDate>Wed, 08 Jul 2009 16:13:30 EDT</pubDate>
</item>

<item>
<title>Re: Multicast</title>
<link>http://www.dslreports.com/forum/Re-Multicast-22674506</link>
<description><![CDATA[anon posted : let me add a couple mroutes<br><br>on the right side of the MPLS (next to the rp) :<br><br>sh ip mroute | in 225.<br>(*, 225.0.0.1), 14w5d/stopped, RP 192.168.22.10, flags: SPF<br>(172.16.32.52, 225.0.0.1), 00:07:08/00:02:02, flags: PR<br><br>which is good, 172.16.32.52 is the source of the multicast. Here is what i get on my RP:<br><br>(*, 225.0.0.1), 00:03:58/stopped, RP 192.168.22.10, flags: SP<br>(2811 IP, 225.0.0.1), 00:00:25/00:02:34, flags: PT<br>(2811 IP, 225.0.0.1), 00:00:37/00:02:34, flags: PT]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Multicast-22674506</guid>
<pubDate>Wed, 08 Jul 2009 15:20:02 EDT</pubDate>
</item>

<item>
<title>Multicast</title>
<link>http://www.dslreports.com/forum/Multicast-22674133</link>
<description><![CDATA[anon posted : Hello all,<br><br>I'm having some multicast issues. I have PIM-SD mode setup, and I'm manually pointing all the devices to a specific RP. Here's my setup:<br><br>source-[3750]-[asa]-[3560]-[2811]-{MPLS}-[2811]-[3560(RP)]-[asa]-[3750]-receiver<br><br>Now, everyone is pointed to the RP and that looks good, and all their PIM neighbor relationships look good too. But the multicast stuff still isn't working and i'm not too sure why. Any ideas?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Multicast-22674133</guid>
<pubDate>Wed, 08 Jul 2009 14:11:33 EDT</pubDate>
</item>

</channel>
</rss>

