{"id":235,"date":"2015-12-13T00:48:32","date_gmt":"2015-12-12T16:48:32","guid":{"rendered":"https:\/\/networkingnotesblog.wordpress.com\/?p=235"},"modified":"2015-12-13T00:48:32","modified_gmt":"2015-12-12T16:48:32","slug":"playing-with-multicast-part-2","status":"publish","type":"post","link":"http:\/\/notes4it.com\/?p=235","title":{"rendered":"Playing with Multicast &#8211; Part 2."},"content":{"rendered":"<p>The part 1 of multicast was simply doing the streaming within a local area network. This time, I will put my multicast lab to a level higher and put a router between the sender and receiver.<br \/>\nThe test bed for this time will involve a simple routings. Please refer to the topology below.<br \/>\nTo keep the multicast lab simple, it will be running on Sparse mode and using static RP instead of dynamic.<br \/>\n<strong>TOPOLOGY:<\/strong><br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-242\" src=\"https:\/\/networkingnotesblog.files.wordpress.com\/2015\/12\/mcast_topo_with_1_router.jpeg\" alt=\"Mcast_topo_with_1_router\" width=\"625\" height=\"428\" srcset=\"http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/mcast_topo_with_1_router.jpeg 625w, http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/mcast_topo_with_1_router-300x205.jpeg 300w\" sizes=\"auto, (max-width: 625px) 100vw, 625px\" \/><br \/>\n<strong>Components:<\/strong><br \/>\n1x Ubuntus as sender<br \/>\n1x Windows XP as receiver.<br \/>\n1x Junos router<!--more--><br \/>\n<strong>Installation:<br \/>\n<\/strong>The software for both sender and receiver are remain the same from part 1. Please refer to multicast &#8211; part 1 for detail:<\/p>\n<blockquote class=\"wp-embedded-content\" data-secret=\"a56EVYJFem\"><p><a href=\"https:\/\/networkingnotesblog.wordpress.com\/2015\/12\/12\/playing-with-multicast-part-1\/\">Playing with Multicast &#8211; Part&nbsp;1.<\/a><\/p><\/blockquote>\n<p><iframe loading=\"lazy\" class=\"wp-embedded-content\" sandbox=\"allow-scripts\" security=\"restricted\" style=\"position: absolute; clip: rect(1px, 1px, 1px, 1px);\" title=\"&#8220;Playing with Multicast &#8211; Part&nbsp;1.&#8221; &#8212; networking notes blog\" src=\"https:\/\/networkingnotesblog.wordpress.com\/2015\/12\/12\/playing-with-multicast-part-1\/embed\/#?secret=nxN4Ctpj3k#?secret=a56EVYJFem\" data-secret=\"a56EVYJFem\" width=\"600\" height=\"338\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\"><\/iframe><br \/>\n<strong>Configuration:<\/strong><br \/>\n&#8211; Router:<br \/>\nThe router for this test bed is a virtual MX. It configures with minimum configuration to keep the multicast running, and it has the interface and PIM configured.<br \/>\nThe interface of ge-0\/0\/0.101 is connecting to the sender, and ge-0\/0\/0.102 is connecting to receiver. Both connections are separated by VLANs.<br \/>\nThe lt-0\/0\/0 are the interfaces to inter connect to other virtual routers. It is not required for this test bed.<br \/>\nPIM (Protocol Independent Multicast) are enabled and assigned the upstream and downstream interfaces to multicast transfer. The PIM mode is configured as spare-dense, since it allows me to switch between 2 different mode with couple more commands. But we are running sparse mode for this lab. The Rendezvous Point is set as static and the address is pointing at the sender.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-243\" src=\"https:\/\/networkingnotesblog.files.wordpress.com\/2015\/12\/00-junos-configuration.png\" alt=\"00-junos-configuration\" width=\"684\" height=\"325\" srcset=\"http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/00-junos-configuration.png 684w, http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/00-junos-configuration-300x143.png 300w\" sizes=\"auto, (max-width: 684px) 100vw, 684px\" \/><br \/>\n<strong>Testing:<\/strong><br \/>\nWe will be testing the connectivity to ensure both sender and receiver can reach to each other.<br \/>\n&#8211; Windows XP:<br \/>\nThe IP address of XP is set as 192.168.102.15\/24. Based on the traceroute result to Ubuntu, it routes via the Junos router and reach to the destination on the second hop as expected. In this case, we can ensure the sender is able to reach the receiver in both direction.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-245\" src=\"https:\/\/networkingnotesblog.files.wordpress.com\/2015\/12\/01-xp-ip_n_tracert.png\" alt=\"01-XP-IP_n_tracert\" width=\"718\" height=\"322\" srcset=\"http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/01-xp-ip_n_tracert.png 718w, http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/01-xp-ip_n_tracert-300x135.png 300w\" sizes=\"auto, (max-width: 718px) 100vw, 718px\" \/><br \/>\n&#8211; On router:<br \/>\nThis is the output of &#8220;show interface terse&#8221; and we can ensure the first hop of receiver was routed via this router.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-237\" src=\"https:\/\/networkingnotesblog.files.wordpress.com\/2015\/12\/02-junos-interfaces.png\" alt=\"02-junos-interfaces\" width=\"554\" height=\"87\" srcset=\"http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/02-junos-interfaces.png 554w, http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/02-junos-interfaces-300x47.png 300w\" sizes=\"auto, (max-width: 554px) 100vw, 554px\" \/><br \/>\n*If we do not input the command of &#8220;set protocol pim rp static &#8230;&#8230;&#8221; the &#8220;show pim join&#8221; does not have any result, and the streaming of multicast won&#8217;t work without the &#8220;set protocol pim rp static &#8230;&#8230;&#8221;.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-239\" src=\"https:\/\/networkingnotesblog.files.wordpress.com\/2015\/12\/03-junos-show_pim_join.png\" alt=\"03-junos-show_pim_join\" width=\"479\" height=\"112\" srcset=\"http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/03-junos-show_pim_join.png 479w, http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/03-junos-show_pim_join-300x70.png 300w\" sizes=\"auto, (max-width: 479px) 100vw, 479px\" \/><br \/>\nTherefore, the following is the expected result.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-244\" src=\"https:\/\/networkingnotesblog.files.wordpress.com\/2015\/12\/04-junos-show_pim_join_with_rp.png\" alt=\"04-junos-show_pim_join_with_rp\" width=\"513\" height=\"204\" srcset=\"http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/04-junos-show_pim_join_with_rp.png 513w, http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/04-junos-show_pim_join_with_rp-300x119.png 300w\" sizes=\"auto, (max-width: 513px) 100vw, 513px\" \/><br \/>\n<em><strong>Testing different behaviours:<\/strong><\/em><br \/>\n&#8211; If we turn on the streaming on the Ubuntu streaming server only and keep the receiver VLC shut, the router has the following information. It means there is a traffic sending to the group of 224.0.1.40 from the source of 192.168.101.10. It ensures there are active multicast data sending out.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-236\" src=\"https:\/\/networkingnotesblog.files.wordpress.com\/2015\/12\/04-junos-show_pim_join_with_source.png\" alt=\"04-junos-show_pim_join_with_source\" width=\"520\" height=\"191\" srcset=\"http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/04-junos-show_pim_join_with_source.png 520w, http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/04-junos-show_pim_join_with_source-300x110.png 300w\" sizes=\"auto, (max-width: 520px) 100vw, 520px\" \/><br \/>\n&#8211; If the receiver has the VLC player activated and sending the request for steaming single, and the Ubuntu server is not sending out any multicast traffic, the router will result with the following.<br \/>\nThe router will have an entry with a requested group IP shown and with a * as source. When we see this message, we can definately ensure there is a receiver waiting for the single but out multicast traffic shows up.<br \/>\n<img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-241\" src=\"https:\/\/networkingnotesblog.files.wordpress.com\/2015\/12\/05-junos-show_pim_join_w_rp_n_member_report.png\" alt=\"05-junos-show_pim_join_w_rp_n_member_report\" width=\"525\" height=\"321\" srcset=\"http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/05-junos-show_pim_join_w_rp_n_member_report.png 525w, http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/05-junos-show_pim_join_w_rp_n_member_report-300x183.png 300w\" sizes=\"auto, (max-width: 525px) 100vw, 525px\" \/><br \/>\nOnce the VLC player on XP is waiting for the multicast stream and the Ubuntu server is sending out multicast traffic, the router will have the output of following. The first entry from the receivers and the second entry from the sender will be listed out as expected. <span style=\"color:#ff0000;\">If we are looking for a successful multicast streaming, we are expected to have both entries shows up<\/span>.<br \/>\n<a href=\"https:\/\/networkingnotesblog.files.wordpress.com\/2015\/12\/06-junos-show_pim_join_w_s_n_r.png\" rel=\"attachment wp-att-240\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-240 alignleft\" src=\"https:\/\/networkingnotesblog.files.wordpress.com\/2015\/12\/06-junos-show_pim_join_w_s_n_r.png\" alt=\"06-junos-show_pim_join_w_S_n_R\" width=\"509\" height=\"374\" srcset=\"http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/06-junos-show_pim_join_w_s_n_r.png 509w, http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/06-junos-show_pim_join_w_s_n_r-300x220.png 300w\" sizes=\"auto, (max-width: 509px) 100vw, 509px\" \/><\/a><br \/>\n&nbsp;<br \/>\n&nbsp;<br \/>\n&nbsp;<br \/>\n&nbsp;<br \/>\n&nbsp;<br \/>\n&nbsp;<br \/>\n&nbsp;<br \/>\n&nbsp;<br \/>\n&nbsp;<br \/>\nThe snapshot below is from Windows XP and receiving the multicast data stream from Ubuntu that is 1 hops from the router.<br \/>\n<a href=\"https:\/\/networkingnotesblog.files.wordpress.com\/2015\/12\/07-xp-receive_mcast_traffic.png\" rel=\"attachment wp-att-246\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-246 size-medium\" src=\"https:\/\/networkingnotesblog.files.wordpress.com\/2015\/12\/07-xp-receive_mcast_traffic.png?w=300\" alt=\"07-XP-receive_MCast_traffic\" width=\"300\" height=\"190\" srcset=\"http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/07-xp-receive_mcast_traffic.png 714w, http:\/\/notes4it.com\/wp-content\/uploads\/2015\/12\/07-xp-receive_mcast_traffic-300x190.png 300w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><br \/>\n&nbsp;<br \/>\n&nbsp;<br \/>\n&nbsp;<br \/>\n&nbsp;<br \/>\n&nbsp;<br \/>\n&nbsp;<br \/>\nPart 1 of the multicast post starts with 1x receiver and 1x sender in a local area network.<\/p>\n<blockquote class=\"wp-embedded-content\" data-secret=\"a56EVYJFem\"><p><a href=\"https:\/\/networkingnotesblog.wordpress.com\/2015\/12\/12\/playing-with-multicast-part-1\/\">Playing with Multicast &#8211; Part&nbsp;1.<\/a><\/p><\/blockquote>\n<p><iframe loading=\"lazy\" class=\"wp-embedded-content\" sandbox=\"allow-scripts\" security=\"restricted\" style=\"position: absolute; clip: rect(1px, 1px, 1px, 1px);\" title=\"&#8220;Playing with Multicast &#8211; Part&nbsp;1.&#8221; &#8212; networking notes blog\" src=\"https:\/\/networkingnotesblog.wordpress.com\/2015\/12\/12\/playing-with-multicast-part-1\/embed\/#?secret=nxN4Ctpj3k#?secret=a56EVYJFem\" data-secret=\"a56EVYJFem\" width=\"600\" height=\"338\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\"><\/iframe><br \/>\nPart 3 of the multicast post is describes the lab with 3 routers and one for each sender and receiver.<br \/>\n(still organizing the information)<br \/>\nPart 4 of the multicast post is putting the lab from part 2 onto a MPLS VPN platform.<br \/>\n(still organizing the information)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The part 1 of multicast was simply doing the streaming within a local area network. This time, I will put my multicast lab to a level higher and put a router between the sender and receiver. The test bed for this time will involve a simple routings. Please refer to the topology below. To keep [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":242,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,3],"tags":[94,205],"class_list":["post-235","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-networking","category-virtualization","tag-junos-en","tag-vmx-en"],"_links":{"self":[{"href":"http:\/\/notes4it.com\/index.php?rest_route=\/wp\/v2\/posts\/235","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/notes4it.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/notes4it.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/notes4it.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/notes4it.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=235"}],"version-history":[{"count":0,"href":"http:\/\/notes4it.com\/index.php?rest_route=\/wp\/v2\/posts\/235\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/notes4it.com\/index.php?rest_route=\/wp\/v2\/media\/242"}],"wp:attachment":[{"href":"http:\/\/notes4it.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=235"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/notes4it.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=235"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/notes4it.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=235"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}