Multicasting in Intra and Inter Domain Networks

Size: px
Start display at page:

Download "Multicasting in Intra and Inter Domain Networks"

Transcription

1 Technical Report, IDE1106, February 2011 Multicasting in Intra and Inter Domain Networks Master s Thesis in Computer Network Engineering Shahzad Hayat Khan and Jehan Badshah School of Information Science, Computer and Electrical Engineering Halmstad University i

2 Multicasting in Intra and Inter Domain Networks Master s Thesis in Computer Network Engineering School of Information Science, Computer and Electrical Engineering Halmstad University Box 823, S Halmstad, Sweden ii

3 Multicasting in intra and inter Domain networks Preface We really thank our supervisor Professor Tony Larsson for his support, encouragement guidance and suggestions. We would also like to thank the staff at the Department of Computer and Electrical Engineering, University of Halmstad for their assistance and positive attitude. Finally, we want to express our thanks to our family and friends who have supported and encouraged us during our study period. Shahzad Hayat Khan & Jehan Badshah Halmstad University, February iii

4 iv

5 Introduction Abstract Multicasting in a network improves the efficiency to deliver an IP packet to multiple clients at the same time. Small to medium sized organizations implement this technology to enhance their network capability, which is otherwise not possible just with normal routing. However, to use this technology, it requires proper network design with tidy resource implementation. Network administrators prefer automatic deployment of multicast technology because it reduces the potential risk of prolonged down time during network troubleshooting. On the other hand, choosing an auto deployment technology could cause malfunctioning in the network. To avoid such malfunctioning, we used two technologies: Auto-RP (Auto- Rendezvous Point) [1] and Bootstrap [2] in our network. A problem that occurs here is that if different domains with similar or different technologies want to share their resources with each other, then regular multicasting cannot connect them for successful communication. Also, if an administrator wishes to provide short and redundant paths within a domain, then these two technologies do not possess the ability to do so. The thesis presents issues in intra-domain and inter-domain multicast networks; it also focuses on Auto-RP (Auto Rendezvous Point) and BSR (Bootstrap Router) which are technologies related to multicasting. This project highlights the importance of multicasting security and will brief the problems associated with these two technologies. It will offer a better solution with a properly implemented design guide. The study uses MSDP (Multicast Source Discovery Protocol) [3] which connects two domains with multicasting capabilities for exchanging the source and providing redundancy in intradomain. The work implements MBGP (Multicast Border Gateway Protocol) [4] to avoid a situation in which there is no multicast support on one of the service provider(s) end. Keywords: Auto-RP (Auto-Rendezvous Point), BSR (Bootstrap Router), MSDP (Multicast Source Discovery Protocol), MBGP (Multicast Border Gateway Protocol) v

6 Multicasting in intra and inter Domain networks vi

7 Introduction 1 INTRODUCTION PROBLEM MOTIVATION APPROACH OBJECTIVES BACKGROUND WORK THE EVOLUTION OF MULTICAST DESIGN OF SCALABLE INTER-DOMAIN IP MULTICAST ARCHITECTURE INTER-DOMAIN MULTICAST ROUTING WITH IPV MULTICAST ROUTING PROTOCOLS IN A MULTIPLE DOMAIN NETWORK INTRA DOMAIN MULTICAST ROUTING PROTOCOLS INTER DOMAIN MULTICAST ROUTING PROTOCOLS MULTICASTING TECHNOLOGY EXPLANATION MULTICASTING OVERVIEW PIM AUTOMATIC DEPLOYMENT OF RPS Auto-RP Bootstrap MSDP MBGP MULTICAST OPERATION: INTRA-DOMAIN NETWORK SETUP BASIC NETWORK CONNECTIVITY AND SETUP RPF CHECKS AND TROUBLESHOOTING BOOTSTRAP IMPLEMENTATION IN DOMAIN B IMPLEMENTING ANY-CAST OPERATION SIMULATION RESULTS MULTICAST OPERATION: INTER-DOMAIN RP CONFLICT DOMAIN SECURITY AND FILTERING CONNECTING DOMAINS SOURCE SECURITY AND RATE LIMIT MBGP EXTENSION TO MULTICASTING SIMULATION RESULTS CONCLUSION AND FUTURE WORK ABBREVIATIONS REFERENCES APPENDIX APPENDIX A APPENDIX B APPENDIX C vii

8 APPENDIX D APPENDIX E APPENDIX F APPENDIX G APPENDIX H APPENDIX I APPENDIX J APPENDIX K APPENDIX L APPENDIX M viii

9 Introduction ix

10 List of Figures Figure 1 : Unicast based network... 7 Figure 2: Multicast Network Diagram...11 Figure 3 : RPF Failure Figure 4 : MSDP(Any-cast Operation Figure 5: MBGP (Example) x

11 11

12 Multicasting in Intra and Inter Domain Networks 1 Introduction Most organizations use multicasting for audio announcements, video conferencing or news feed etc. from distant locations. It is important to bear in mind that subscribing to the same server from multiple clients can create problems related to performance and availability of the multicast network. It is possible that many clients could face performance issues because they have to travel through a longest path for getting announcements and joining the server. The problem that arises in the routing world is that if multiple clients are interested to get the same data from a server then individual data packet must be generated for each client at the source. In other words, each client is served individually at the server end. This approach of data delivery to multiple clients is not efficient and puts burden over the network resources. Multicasting provides the capability to send a single IP packet down the path from a source towards multiple destinations. At a transit point, an individual copy for each client is generated and delivered to all interested clients. Thus, the traffic burden is minimized at the source. This way of data delivery is more efficient, scalable and enhances the network performance significantly. The major problem area in multicasting is that redundancy and inter-domain connectivity are not direct features of multicast configuration. Each time when a client joins a server to receive multicast traffic, it has to consult the Rendezvous Point (RP). If there are multiple clients and they wish to join or leave the server, they have to ask this RP for their multicast operation. There is a possibility that the RP could fail due to the heavy multicast load. If RP failure occurs, multicast will cease to function. To avoid such failure, it is important to provide redundancy and load balancing inside the domain. An interesting fact about multicasting is that two separate domains cannot share their sources information directly. For enforcing security, multicast boundary must be created between different domains. If two domains do not deploy boundaries, then these domains with similar or different RP operations will start overlapping. The reason for this fluctuation is that whichever RP that learns the source information first will flood it to the rest of the network. If there is no source subscriber associated with the RP, it will prune the information. Whereas in another request, it may be possible that another RP floods the data. This could cause source information leakage and may inject false information in the network. In order to avoid such a situation, multicast boundaries are essential to prevent the network from malfunctioning. However, creating multicast boundaries will stop sources from announcing information between each other and will cause isolation of two domains. Another issue which influences multicasting is Service Level Agreement (SLA). In some cases the ISP does not provide the facility of multicasting and MBGP is used to eradicate this problem and provide alternate backup link. 1

13 1.1 Problem If too many clients ask the same RP for information then the possibility may exist that this RP becomes unavailable or becomes unresponsive. In such circumstances, there is a potential risk that the multicast network will collapse. It is feasible to implement two RPs in the network, but such design will require a larger amount of administrative input in order to control different RPs for different announcements. This however, is not a recommended approach. If two different domains have an agreement to connect with each other, there are possible loop holes of technologies overlapping or a multicasting disagreement with the service provider. 1.2 Motivation The study provides complete end to end solution for an administrator to setup a successful multicasting network. Performance of the network will be improved by providing single packet transmission to multiple hosts. Various applications for example Citrix, Terminal Servers Clusters, and Microsoft Media Servers etc can be easily operated on this network. This project is a good motivation for a domain to enterprise based administrator. It is not only restricted to just one domain or one technology but can also be used as a guideline for deploying and troubleshooting multicasting between the ISP. 1.3 Approach In this project the aim is to provide a design and solution guide for intra and inter-domain multicast routing. The focus is on the problems associated with in domains. This report and implementation is important for design consideration for configuring automatic deployment of intra and inter-domain multicasting. This project tests the network s functionality through IGMP. In real world networks IGMP can be replaced with end servers. This network is ready to carry the unicast as well as multicast based traffic. 1.4 Objectives The main objectives of this thesis are: To tell what multicasting is and ways for how to implement it. To achieve load balancing and path redundancy in Intra- domain networks. To prevent information leakage between domains and achieve Inter-domain connectivity. To implement multicast security and to address the SLA problem. The structure of this thesis is as follows: Chapter 2: Related Work, Chapter 3: Multicasting technology explained, Chapter 4: Multicast Operation: Intra-domain Chapter 5: Multicast Operation: Inter-domain and Chapter 6: Conclusion and future work. 2

14 Multicasting in Intra and Inter Domain Networks 2 Background work Although multicasting is a broad subject area, there is very little practical work relating to its configuration in the network. Several of the articles pay greater attention to the architecture and technologies used for multicasting whereas the work in this thesis is more concerned with the practical implementation of these technologies. 2.1 The evolution of multicast In this study [5], a brief description about the standard IP multicast model, its requirements and the way clients send/ receive multicast packets is presented. The model motivated the use of multicast on the internet and created the Multicast Backbone (MBone). Distance Vector Multicast Routing Protocol (DVMRP) was the original protocol used for multicast routing on the MBone. In order to fulfil the requirements for inter-domain routing and hierarchical infrastructure, the available protocols at that time were sorted out as intra-domain protocols. Work started on interdomain solution s standardization. Multicast Extension to Open Shortest Path First (MOSPF), Protocol Independent Multicast-Dense Mode (PIM-DM), Protocol Independent Multicast- Sparse Mode (PIM-SM) and Core Based Trees (CBT) are the protocols developed and used for multicast. MBone has grown over time and problems such as scalability and manageability have increased alongside it. In order to provide internet-wide, hierarchical and scalable multicast, inter-domain multicast has been evolved. The required protocols and their desired functionality for this purpose has been developed and considered by the Internet Engineering Task Force (IETF) but they are still in the early stages of development. There is a lack of scalability and elegance which as a result requires long-term solutions from a future perspective. Multicast Source Discovery Protocol (MSDP), PIM-SM and Multicast Border Gateway Protocol (MBGP) protocols are considered as near-term solutions for multicast whilst Border Gateway Protocol (BGMP), Multicast Address-set Claim (MASC) and GLOP are the long-term proposals for inter-domain multicasting and work is underway on the development of these protocols. In order to avoid the complexity of MBGP, MSDP, PIM-SM and BGMP and other multicast issues (billing, security and management) several fundamental changes are offered in the multicast model. Route Address Multicast Architecture (RAMA) is one of the proposals stating that multicast applications must be a single source or primary source with easy identification. Express multicast and Simple multicast are the two styles that RAMA provides for multicasting. 2.2 Design of scalable inter-domain IP multicast architecture The author in [6] has proposed scalable architecture for IP multicasting by reducing the routing information of multicast traffic. This is to address the problem of large routing information which makes IP multicasting less scalable on the internet. 3

15 Two types of multicast addresses have been implemented in this architecture: Virtual Multicast Address (VMA) which specifies multicast group within a certain domain (intra-domain) and Multicast Address for Routing (MAR) which forwards multicast traffic between different domains (inter-domain). With these address types, the multicast address allocation becomes more flexible and also reduces the routing information by address aggregation. 2.3 Inter-domain multicast routing with IPV6 PIM-SM is a commonly used multicast routing protocol both in IPv4 and IPv6 [7]. It builds a unidirectional distribution tree between hosts and Rendezvous Point (RP) for multicast packet forwarding. To deploy PIM-SM, source and destination must use the same RP. This is a suitable solution in intra-domain but not as much in inter-domain due to policy reasons. IPv4 inter-domain multicast uses MSDP that enables RPs to exchange their source information which alternatively provides different networks to implement their own global RPs. In comparison, IPv6 doesn t provide such protocols because this mechanism leads to another prune and unstable broadcast protocol. Embedded-RP with IPv6 addressing capabilities is an alternate solution in which the RP address is embedded into the group address. This makes it easier for the router to know immediately the group address. By using embedded-rp, a common RP is required for a certain group because RPs have no way to exchange information. In addition to this, embedded-rp enables small organizations to use their own RPs for sessions which they are hosting. 2.4 Multicast Routing Protocols in a Multiple Domain Network In this paper [8], the authors discussed different protocols needed for routing between multiple domains. PIM-SM is a suitable protocol used for Multicast routing within a single domain (intradomain multicast). In order to enable multiple PIM-SM domains for multicasting, another protocol Multicast Source Discovery Protocol MSDP is implemented. This protocol is used to establish and maintain different routing policies for multicast and Unicast traffic. Even though standards for multicasting are not yet finalized, IP multicast technology is still being adopted by major networks. Source Specific Multicast (SSM) is another suitable solution for intra-domain multicasting, mostly for IP multimedia services whereas MSDP along with MBGP are solutions for interdomain multicasting. Apart from these solutions, research on QoS in the IP multicast is still needed. 2.5 Intra Domain Multicast Routing Protocols Multicast protocols should use minimal network overhead, must be scalable, consume less memory resources and must be able to operate with other multicast routing protocols in the network and most importantly, be easy to implement. The technique used for managing the 4

16 participants, for example, joining and leaving a multicast group is an important factor when designing a multicast protocol. Other factors that need to be focused on during the design of multicast protocols depend on the participants that distribute over the routing domain, their role in the group, the number of groups and maximum participant in each group [9]. Distance Vector Multicast Routing Protocol (DVMRP), DVMRPv3, Multicast Open Shortest Path First (MOSPF), Core Base Tree (CBT), PIM-DM, PIM-SM and Multicast Internet Protocol (MIP) are classified as intra-domain multicast protocols by IETF. 2.6 Inter Domain Multicast Routing Protocols Inter-domain multicast routing protocols are required for successful communication across multiple domains between clients and server. Many things have to be considered while designing these protocols. Most importantly such protocols must be scalable with low overhead and work well with other protocols [9]. Yet-Another Multicast (YAM), Quality of Service-Sensitive Multicast Routing Protocol (QoSMIC), Policy Tree Multicast Routing (PTMR), Multicast Source Discovery Protocol (MSDP), MASC/BGMP, Distance Vector Multicast Routing Protocol (HDVMRP), Hierarchical Protocol Independent Mode (HPIM), OCBT, Hierarchical Multicast Routing (HIP), Centralized Multicast, Static Multicast and Distributed Core Multicast (DCM) are being used for Interdomain Multicast routing. 5

17 Background work 6

18 Multicasting in Intra and Inter Domain Networks 3 Multicasting Technology Explanation This section explores multicasting technology and the necessary components for creating a stable multicast network. 3.1 Multicasting Overview A router by default does not allow broadcasting and multicasting. However, it is still possible to configure a router to allow broadcasting over PPP or Frame relay network. Unlike Ethernet, this broadcast over WAN technology is from a specific source to a specific destination. If multiple destinations have to transit a router to reach a certain server then in return the router has to replicate the same packet multiple times for each individual host. The diagram below illustrates a unicast based network data flow. Figure 1 : Unicast based network Nine clients want to collect data from the server. In response, the server has to replicate nine different packets for each destination client. Let us suppose that this is a video streaming server and the total speed of the link is Mbps. Here, a total of 4.6 Mbps bandwidth is required to deliver this video streaming to all the clients simultaneously. In this case, since we have only Mbps link, unicast routing cannot serve the simultaneous transmission of streaming to all these nine clients. On the other hand, if multicasting is implemented in the above network then only 512 Kbps of bandwidth will be sufficient to deliver successfully the video streaming to all the clients at the same time. 7

19 Multicasting requires a fully functional network before serving the clients in the network. There are three ways to implement multicasting in the network: MOSPF, DVMVPN or PIM [4]. OSPF and DVMVPN are out of the scope of this thesis and Cisco routers do not support them. 3.2 PIM Protocol Independent Multicast (PIM) is known as the routing protocol of multicasting and it builds its own routing table to keep states of multicast sources. It is a requirement of PIM that it should be enabled on all links from source to destination. It can be implemented in two ways: PIM Dense mode and PIM Sparse mode [10]. PIM dense mode is an obsolete technology because it consumes most of the bandwidth due to its nature of operation. Sparse mode is better in the sense that it does not flood the network with unnecessary traffic but in fact, it forwards packets when required. As discussed earlier, when a client wants to request data from a server, it cannot do it directly. The reason behind this is if a large number of clients request server at the same time, sever may experience a bottleneck situation. In order to solve this problem, one router in the network is chosen as a master for flooding multicast traffic. This router is called RP and is usually a middle router in the network. In a large enterprise, some clients are further apart from this RP whilst others are closer to it. This may cause longer response time by RP and longer connection time to the server. Similarly, another issue might be that if this RP fails to deliver its operation properly, then the whole multicast network will suffer. We will configure redundant RPs in our multicast network with the consideration of possible switch failovers. It will provide pre-emption of original RP to the clients with shortest path. 3.3 Automatic deployment of RPs There are two ways to implement automatic deployment: Auto-RP Auto-RP [1] is a standalone Cisco propriety protocol and works on Cisco routers. It has the capability of automatic distribution of group-to-rp mappings in a PIM [10]. Auto-RP makes it easier to have multiple RPs within a domain and serves a range of different groups. It provides load balancing among many RPs and redundancy and tedious manual configuration. Auto-RP allows us to create multiple RPs as backups for each other Bootstrap The Bootstrap Router (BSR) [2] was first introduced in PIM version 2. BSR is IETF standard track protocol while Auto RP is Cisco proprietary. This means that BSR will work with routers from multiple vendors, including Cisco routers. In a PIM domain one has to configure multiple Candidate BSRs in order to avoid a single point of failure. Candidate BSR will automatically elect a BSR by sending bootstrap messages. The router with the highest priority is elected as BSR. After selection, BSR will announce itself to all domains and will be responsible for queries related to multicasting. All Candidate BSRs will report to the BSR. 8

20 3.4 MSDP Multicast Source Discovery Protocol (MSDP) [3] explains how to connect two independent domains using PIM-SIM protocols. With MSDP, it is possible for both domains to use their own RP and they do not have to rely on each other s RP whilst in their domains. In PIM-SIM model it is necessary for source and receiver to be registered with the local RP. However, a point to consider here is that the local RP only has information about sources and receivers within a local domain. The issue faced is that RP does not have information about sources and receivers from other domains. MSDP allows us to solve this issue by maintaining an independent RP in each domain which enables RPs to forward traffic between different domains. The other benefit of MSDP is that the end receivers obtain data locally within the domain without globally advertising their group membership. 3.5 MBGP Multicast Protocol Gateway Protocol (MBGP) is based on RFC 2283[11] and 2858[4], these are Multiprotocol Extensions for BGP-4. It provides scalable, policy-based Inter-domain routing which can be used to support non-congruent unicast and multicast forwarding. It offers a way to differentiate which prefixes will be used for performing multicast reverse path forwarding (RPF) checks. The RPF check is essential in creating multicast forwarding trees and moving multicast content successfully from source to receiver(s). Two path attributes are introduced to BGP+ as described in Internet Draft draft-ieft-idr-bgp4-mutiprotocol-01.txt are MP_REACH_NLRI and MP_UNREACH_NLRI. For carrying two set of routes MBGP is an efficient technique. One set is used for unicast routing and one for multicast routing. The route links to multicast routing are used by multicast routing protocols to build data distribution trees. 9

21 Multicasting in Intra and Inter Domain Networks 10

22 Multicasting in Intra and Inter Domain Networks 4 Multicast Operation: Intra-domain The first part of this project focuses on the issues and implementation of multi-casting inside a domain. A domain is a set of network and server components under single administrative control. Therefore, an administrator has the authority to control the entire multicast and unicast based capabilities in accordance to his preferences. As discussed earlier, automatic rendezvous point is the best choice for automatic deployment of multicast announcements. Auto-RP and BSR are two technologies that exist for such a purpose and the thesis implements both in each domain. 4.1 Network setup The diagram below is a visual representation of the network: Figure 2: Multicast Network Diagram In the diagram, two multicast domains are represented. Domain A has two servers with multicast address of and respectively. Similarly, Domain B has two servers with multicast address of and Domain A is capable of running Auto-RP, whereas Domain B is running BSR. The verification of redundancy in each domain will be checked by running multiple RP and connecting them via MSDP. The clients generate multicast traffic in their domain and the response time is checked in comparison with SPT (Shortest Path Tree). This section focuses on multicast functionality inside the domain only. The inter-domain connectivity and features will be discussed in detail in chapter five. 11

23 4.2 Basic Network Connectivity and setup As discussed earlier, multicasting requires a functional network to work properly. Different types of protocols can be run in the network for multicast routing. It does not matter whether a static or dynamic route has been chosen; the key point is that every network interface should be reachable. Before configuring a multicasting network, the following criteria should be met: Enable PIM on all the interfaces from servers to clients. Use static mcast to solve problems with links that are not multicast enabled. If OSPF and EIGRP are on two ends and they are both redistributing then OSPF stub network may cause connectivity issues. CR and CA should be kept separate. Implement all security features before implementing multicasting on the network. Check that the network is functioning properly. Ping all devices and addresses used within the network. Configure the basic network setup on both sides [Appendix A]. Do not run any routing protocol between the domains yet. The interconnection between the two sites will be discussed in the next chapter. The basic network setup has been performed, it is important to check that each and every link is up and functional. There are various ways to check the reachability; tcl script [Appendix B] is used on each router to send ping requests to all interfaces. If at any stage, tcl script reports an unreachable destination then troubleshooting is required. 4.3 RPF Checks and Troubleshooting When building a multicast based network, it is necessary to setup all the links with PIM. As discussed in chapter 3, there are three ways to enable multicasting. However, two of these options-mospf and DMVPN are deprecated and are no longer supported by Cisco. This means that PIM is the only suitable option and works perfectly well. An explanation of RPF [12] (Reverse Path Forwarding) is illustrated in the diagram below. 12

24 Figure 3: RPF Failure In the figure the shortest path from client to server is via N2 N3. When the client wants to send the request it will be a unicast request. The server will reply via multicast. The reply will always follow the shortest path defined by the routing protocol. In the exhibit above, PIM is not enabled between link N2 N3; as a result the client will never get the data back from the server. This problem is called reverse path forwarding failure. There are four ways to tackle this problem: Enable PIM between N2 N3. Configure a static mroute from N2 to N4, so that multicast traffic can be redirected. Use the GRE tunnel to provide another multicast enabled link. Use MBGP. MBGP implementation is explained in detail in the next chapter. RPF checks and verification is a sensitive piece of information and it can break the whole network. To demonstrate RPF check and its recovery, enable PIM on all the interfaces [Appendix C] but do not enable PIM on the link between R1 and R2. Ping the multicast address from Client 1 to the server and check the output. ping repeat 10 Type escape sequence to abort. Sending 10, 100-byte ICMP Echos to , timeout is 2 seconds:... 13

25 According to the above output the ping failure is caused by RPF failure. This can be verified on R2. R2#show ip rpf RPF information for? ( ) failed, no route exists R2# RPF information shows that there is no route to the server. Confirm that RPF information is accurate on other routers. R3#show ip rpf RPF information for? ( ) RPF interface: FastEthernet0/1 RPF neighbor:? ( ) RPF route/mask: /24 RPF type: unicast (eigrp 1) RPF recursion count: 0 Doing distance-preferred lookups across tables R3# Since R3 has PIM enabled across all links, RPF information exists on R3. To correct RPF failure on R1 and R2, static mroute is used. R1 is configured for static mroute [Appendix D]. Ping the sever again. ping repeat 10 Type escape sequence to abort. Sending 10, 100-byte ICMP Echos to , timeout is 2 seconds: Reply to request 0 from , 32 ms Reply to request 0 from , 32 ms Reply to request 1 from , 12 ms Reply to request 1 from , 52 ms 14

26 Reply to request 2 from , 4 ms Reply to request 2 from , 20 ms The reply from server to R2 is successful according to the output. However, the RPF check on R2 will still be unsuccessful because this path is not the shortest path according to the routing protocol. Confirm the reachability between both servers from both clients. 4.4 Bootstrap implementation in Domain B Bootstrap implementation is similar to Auto-RP but the difference is that Bootstrap only works in sparse mode. According to Appendix C, all the links have been configured in spare-dense mode. Auto-RP cannot work without this because the information from server to RP is always in dense mode, whereas the real traffic flows in sparse mode. Two groups will always be created in this way on all routers for dense mode operation. R2#show ip mroute (*, ), 00:34:09/00:02:13, RP , flags: DCL Incoming interface: Null, RPF nbr Outgoing interface list: Loopback1, Forward/Sparse-Dense, 00:34:09/00:00:00 FastEthernet0/1, Forward/Sparse-Dense, 00:34:09/00:00:00 (*, ), 00:36:32/00:02:14, RP , flags: DCL Incoming interface: Null, RPF nbr Outgoing interface list: FastEthernet0/1, Forward/Sparse-Dense, 00:33:01/00:00:00 Loopback1, Forward/Sparse-Dense, 00:34:09/00:00:00 R2# The above output shows two groups and which are used by Auto-RP operation. The bootstrap operation works in a different way in the sense that the information is 15

27 learned on a hop by hop basis. In Auto-RP the information is directly passed from server to RP. Consequently, the server needs dense mode to push its information to RP. As bootstrap passes information on a hop by hop basis dense mode operation is not required. Configure Domain B with BSR operation [Appendix E]. Verify the connectivity and troubleshoot RPF checks, if necessary. 4.5 Implementing Any-cast Operation Any-cast operation helps a domain in providing multiple paths in the network. In a larger network, clients are normally connected far away from the RP. It is difficult for clients to choose a nearest RP for multicast flow. To give an example, ping Server 1 from Client 1 and check the response time. ping repeat 10 Type escape sequence to abort. Sending 10, 100-byte ICMP Echos to , timeout is 2 seconds: Reply to request 0 from , 32 ms Reply to request 0 from , 32 ms Reply to request 1 from , 12 ms Reply to request 1 from , 52 ms Reply to request 2 from , 4 ms Reply to request 2 from , 20 ms The output shows different response times because currently Client 1 is learning source information from two places. There are two RPs at the moment in each domain and they both have information about the sources. When Client 1 initiates the joint request, both sources flood information to the client. In the above results, the longest delay is the information fed by the second RP, whereas the shortest delay is the information fed by the current RP. On a busy network, this can be a major issue for delay sensitive traffic like VoIP. At the moment, there is no other traffic flowing through the network and the delay transition is smoother. If more and more clients join the network however, it could cause problems for some traffic. In the case of one server stopping operation, Any-cast will provide multiple and redundant paths. The illustration of Any-cast operation is given in the figure below: 16

28 Figure 4: MSDP (Any-cast operation) In the figure, two RPs exist in the current domain. In order to provide redundant paths, a similar configuration is required on both Auto-RP routers. In this case, one extra loop back on each router is setup and advertised via IGP. Now, each router will reach this loop back according to its current IGP (Interior Gateway Protocol) metric and in the case of the nearest loopback failing, then another will take place. Appendix F carries out a similar configuration in the network advertised via IGP. Firstly, it is important to confirm whether or not the goal for creating the loopbacks has been achieved so far. Verify the routing table on R1 and check that both loopbacks exist in the routing table. R1#show ip route C /24 is directly connected, FastEthernet0/0 C /24 is directly connected, FastEthernet0/1 D /24 [90/307200] via , 00:02:06, FastEthernet0/ /24 is subnetted, 4 subnets D [90/435200] via , 00:02:06, FastEthernet0/1 [90/435200] via , 00:02:06, FastEthernet0/0 D [90/409600] via , 00:02:11, FastEthernet0/1 17

29 D C [90/409600] via , 00:02:19, FastEthernet0/ is directly connected, Loopback /32 is subnetted, 1 subnets D [90/409600] via , 00:00:01, FastEthernet0/1 [90/409600] via , 00:00:01, FastEthernet0/0 D /24 [90/307200] via , 00:02:07, FastEthernet0/1 R1# R1 reports two paths to the same ip address. Telnet to and check which path it prefers. R1#telnet Trying Open User Access Verification Password: R3> R1 telnet was redirected to R3 because R3 had the highest interface IP address. The router always preferred the path with highest IP address. To validate the configuration, shutdown the loopback on R3 and telnet again to the same address. R1#telnet Trying Open User Access Verification 18

30 Password: R2> R2> The telnet from R1 was directed to R2 because R3 s loop back address was in shutdown state. The following points should be considered before implementing Any-cast operation: If the IGP protocol is OSPF, make sure that this loop back interface is not the router-id for OSPF. Also maintain the same practice for BGP. If OSPF or BGP has chosen this loop-back as the router-id, make sure to hard code the router's ID for OSPF and BGP. When building MPLS LDP protocol via loop back interface, make sure that the connected source is not this loop back interface. Configure R2 and R3 [Appendix G], so that the sources for multicast operation become the loop back interfaces. Verify that current RP candidate is the new loop back interface. R4#show ip mroute IP Multicast Routing Table (*, ), 00:05:25/stopped, RP , flags: D Incoming interface: Null, RPF nbr Outgoing interface list: FastEthernet0/1, Forward/Sparse-Dense, 00:05:25/00:00:00 FastEthernet0/0, Forward/Sparse-Dense, 00:05:25/00:00:00 ( , ), 00:02:28/00:00:32, flags: Incoming interface: FastEthernet0/0, RPF nbr Outgoing interface list: FastEthernet0/1, Forward/Sparse-Dense, 00:02:28/00:00:00 19

31 The output from R4 reveals that RP for is and the information is fed by R3 ( ). Since R4 has the same equal path to R3 and R2, the tie breaker in deciding the best possible path is the highest interface IP address and in this case it is the IP address of R3. The purpose of configuring Any-cast was to overcome the problem caused in the previous section. When Client 1 initiated the request to join the multicast group it caused a flood of information from multiple RPs. With Any-cast configuration, the client will get the information from its nearest RP due to the MSDP configuration. Ping again and check the response time. ping repeat 10 Type escape sequence to abort. Sending 10, 100-byte ICMP Echos to , timeout is 2 seconds: Reply to request 0 from , 32 ms Reply to request 0 from , 32 ms Reply to request 1 from , 30 ms Reply to request 1 from , 32 ms Reply to request 2 from , 31 ms Reply to request 2 from , 32 ms The output above indicates the constant RTT (Round Trip Time) from the nearest RP. At the moment, IGP reports the nearest RP through R2 and therefore the smallest SPT (Shortest Path Tree) is built through R2. The last part of this chapter is to confirm the reachability of the current RP in case it becomes unavailable. Shutdown the loop back interfaces on R2 and ping the source again from Client 1. R2#ping Type escape sequence to abort. Sending 1, 100-byte ICMP Echos to , timeout is 2 seconds: Reply to request 0 from , 44 ms R2# The output displays the RTT of 44ms and that is because R3 is the RP for current communication. This outcome can be validated with the configuration below: #show ip mroute 20

32 IP Multicast Routing Table (*, ), 00:05:25/stopped, RP , flags: D Incoming interface: Null, RPF nbr Outgoing interface list: FastEthernet0/1, Forward/Sparse-Dense, 00:05:25/00:00:00 FastEthernet0/0, Forward/Sparse-Dense, 00:05:25/00:00:00 ( , ), 00:02:28/00:00:32, flags: Incoming interface: FastEthernet0/0, RPF nbr Outgoing interface list: FastEthernet0/1, Forward/Sparse-Dense, 00:02:28/00:00:00 The output reveals that R3 is the current RP ( ) and that is the IP address of R3 interface. 4.6 Simulation Results Multicasting requires a fully functional network. Implementation of Bootstrap is similar to Auto- RP but difference is in their way of working. In Auto-RP information from server to RP is in dense mode, whereas the real traffic is in sparse mode. On the other hand, Bootstrap works in sparse mode. It passes information hop by hop basis and thus does not require dense mode operation. In a larger network, it could be a problem for clients to communicate with the server with multiple RPs. As the information is fed by two sources there is a potential risk of network instability with its deployment. Any-cast operation ties two or more RPs with the same set of instructions, the client chooses the one reported by shortest IGP metric. In the configuration above, the response time on Client 1 from Server 1 was fluctuating. With Any-cast operation, the RTT became stable due to the SPT built by one RP. If the current RP goes down, clients can still reach the network through another RP. Any-cast operation is designed to work best in a larger network because it not only keeps the RP information uniform, but also provides fail over recovery and redundant paths. 21

33 22

34 Multicasting in Intra and Inter Domain Networks 5 Multicast Operation: Inter-domain The last section of this thesis addresses multicast operation between domains. In our network, there are two domains. It is totally up to the administrator whether he runs static RP assignments, Auto-RP or BSR in each domain or Auto-RP or BSR operation in both. The main purpose of Inter-domain multicasting is as follows: Creating multicast boundaries for stopping information leakage. Dynamic multicast routing through MBGP, if the shortest path is not in SLA agreement Multicast security When two domains agree to link and share multicast information, certain challenges arrive. The main problem is the Service Level Agreement. If two domains are located far away and are connected through a service provider, it is possible that ISP has no SLA for multicast routing. In this case, MBGP is the solution to provide an alternate multicast enabled path for multicast packet flow. The illustration of MBGP is explained in the figure below: Figure 5: MBGP Example N1 and N2 have no SLA to route multicast data. In such cases, these two domains can never route multicast traffic. The reason is that N1 and N2 will follow the shortest path defined by IGP and the same rule will be followed by PIM. In order to override such a problem, MBGP is the desired solution. MBGP will catch the multicast traffic and will route it through N3 and N4. MBGP scenario along with its configuration will be explained in detail later in this section. 23

35 5.1 RP Conflict Domain A and Domain B were configured in the previous chapter for Auto-RP and BSR operation. Configure the links between domain A and domain B [Appendix H]. As soon as the links are enabled for multicasting, both domains will start flooding multicast sources to each other. The problem that arises when implementing multicasting between the domains is the conflict between Auto-RP and BSR. The reason for this is that any RP, either Auto or BSR will try to inject its information when clients wish to join the multicast session. In this process, whoever reaches the client first will deliver its information first. To demonstrate this, ping the multicast server from client 1 and check the RP on the client. #show ip mroute ( , ), 00:02:28/00:00:32, flags: Incoming interface: FastEthernet0/0, RPF nbr Outgoing interface list: FastEthernet0/1, Forward/Sparse-Dense, 00:02:28/00:00:00 In the output above, router 2 has been chosen as an RP because it was the first one to inject the RP information. In order to check the fluctuating RP, shut down the loop back interface on R2, so that it never becomes an RP candidate. Clear the current mroute table on R2 and confirm that R2 has no source information. Router2#clear ip mroute * 24

36 Generate ping from client 1 to server 1 and check the mroute table entry again. #show ip mroute ( , ), 00:02:28/00:00:32, flags: Incoming interface: FastEthernet0/0, RPF nbr Outgoing interface list: FastEthernet0/1, Forward/Sparse-Dense, 00:02:28/00:00:00 In the output is chosen as current RP for Server 1. The problem is that both domains are now suffering from information leakage and RP conflict. Two problems can be faced in such a design. Firstly, RPF failure due to SLA terms and secondly multicast security. For example, the network configured has two servers each, if the information from one server needed to be stopped then it might not possible. This could be achieved by mapping agent filtering through local RP but this will stop agent from advertising it to local as well as remote domain. TTL security can also help in restricting source advertisement to certain hops but this solution is not scalable for future deployment. 5.2 Domain Security and Filtering The previous section highlighted the conflict between two domains. This part discusses filtering two domains at certain boundaries, and provides some level of security in order to stop advertising certain servers. Before implementing these features, confirm that Client 1 can reach a server in Domain B. Ping repeat 10 Type escape sequence to abort. Sending 10, 100-byte ICMP Echos to , timeout is 2 seconds: Reply to request 0 from , 32 ms Reply to request 0 from , 32 ms Reply to request 1 from , 12 ms Reply to request 1 from , 52 ms Reply to request 2 from , 4 ms 25

37 The above output indicates that two domains are sharing information without any central agreement. This is potentially a major threat to security because there is no way to stop advertising them. The configuration of Appendix I show multicast boundaries between Domain A and Domain B. The main purpose of implementing multicast boundaries is to isolate two domains completely. As a result they cannot share any information about each other. To verify, ping server in Domain B again and check the response. Ping repeat 10 Type escape sequence to abort. Sending 10, 100-byte ICMP Echos to , timeout is 2 seconds:... Now the ping is unsuccessful because the two domains stopped advertising their source(s) information about each other. Bear in mind that these boundaries will only affect multicast traffic. This configuration has no effect on unicast routing. Also verify that Client 3 cannot reach Server A in Domain A. Ping repeat 10 Type escape sequence to abort. Sending 10, 100-byte ICMP Echos to , timeout is 2 seconds:... The above output indicates that Client 3 cannot reach any server in Domain A. It is now clear from these results that both domains are completely isolated from each other. 5.3 Connecting Domains The previous section created multicast boundaries in order to isolate domains. This section discusses how to connect two domains and share multicast source information. The reason for filtering and isolation was to combat the conflict problem due to multiple RPs from different technologies. The filtering helps in learning source information from their current domain only. In order to learn source information from another domain MSDP is required to do so successfully. 26

38 MSDP works regardless of MBGP configuration. In most documentation, there is confusion with regards to whether or not MBGP is needed for proper MSDP operation. MSDP can work independently but if sources are subject to RPF failure, then MBGP is required to divert source information to another path in conjunction with MSDP. MSDP for inter-domain multicasting can also work between indirectly connected neighbours. The arguments require remote site interface IP, thus it could be a physical or loop back interface. The important thing to note here is that it must be reachable through underlying routing protocol. Configure Domain A and Domain B according to Appendix J. Ping the Sever in Domain B. Ping repeat 10 Type escape sequence to abort. Sending 10, 100-byte ICMP Echos to , timeout is 2 seconds: Reply to request 0 from , 32 ms Reply to request 0 from , 32 ms Reply to request 1 from , 12 ms Reply to request 1 from , 52 ms Reply to request 2 from , 4 ms Now Client 1 is able to reach server in Domain B through MSDP. Check the current RP information on Client 1. #show ip mroute ( , ), 00:02:28/00:00:32, flags: Incoming interface: FastEthernet0/0, RPF nbr Outgoing interface list: FastEthernet0/1, Forward/Sparse-Dense, 00:02:28/00:00:00 The above output indicates that the current RP is R3. Also ping server in Domain A from Domain B and check the RP information. #show ip mroute ( , ), 00:02:28/00:00:32, flags: Incoming interface: FastEthernet0/0, RPF nbr

39 Outgoing interface list: FastEthernet0/1, Forward/Sparse-Dense, 00:02:28/00:00:00 The output shows that the RP for current multicast source is R 5 ( is the IP of R5 in Domain B). 5.4 Source Security and rate limit After creating boundaries to isolate domains, it is also possible to filter certain sources to reach another domain. MSDP was configured to connect two sites and by doing so all the source(s) information was advertised to each other. There are two ways to accomplish this task. It can either be blocking the source information completely or limiting it to certain bandwidth. For example, Server B from Domain A can be blocked from advertisement to domain B or it can be restricted to certain bandwidth. Configure both domains [Appendix K] to stop advertising Server B to Domain B and Server D to Domain A. Generate ping from client 1 to Server D. Ping repeat 10 Type escape sequence to abort. Sending 10, 100-byte ICMP Echos to , timeout is 2 seconds:... Check the access-list counters on R 3. R3# show access-list deny (54 matches) permit any (114 matches) Also confirm that Client 3 cannot ping Server B in Domain A. Ping repeat 10 Type escape sequence to abort. Sending 10, 100-byte ICMP Echos to , timeout is 2 seconds:... The output demonstrates the reachability failure to servers located in another domain. Also interface-counter about the access-list confirms the number of hits. This is one solution. It is also possible to rate-limit certain servers. Configure Domain A [Appendix L] to limit domain at maximum of 128 Kbps for Server B. 28

40 In the configuration above, any time clients from Domain B trying to join a server in Domain A would be given a total of 128 Kbps of bandwidth. It is also possible to restrict certain clients for rate-limiting, whereas allowing others to use unlimited bandwidth. For such a configuration, modify Appendix L access-list to extended access-list. Generate join request from Client 3 to Server B and check the show ip mroute for verification. Show ip mroute ip mutlicast routing table ( , ), 00:02:28/00:00:32, flags: Incoming interface: FastEthernet0/0, RPF nbr Outgoing interface list: FastEthernet0/1, Forward/Sparse-Dense, 00:02:28/00:00:00, limit 128Kbps In the output, multicast server has been rate-limited to 128 Kbps total. It is a good design strategy for the server connected to slower links. 5.5 MBGP extension to Multicasting The last section of this chapter focuses on the discussion of MBGP extension to multicasting. From the previous chapter it is clear that RPF failure will occur if the return path of a multicast packet is not the shortest path. One method of solving this problem was configuring a static mroute to route multicast packets to another link. The function of static mroute is similar to the static route used in unicast routing. If RPF failure is occurring at different locations, the mroute will need to be configured at multiple places. The main reason of using MBGP for dynamic routing is the problem caused by Service Level Agreement. Multicasting will always prefer the shortest path if there are multiple routes to reach a destination from the source. If the shortest path is not supported by ISP for multicasting, then two domains can never share multicast information. To illustrate this, consider the primary link in the network. Both links have already been configured for multicasting and are connected via MSDP. The entire traffic passing between the domains is utilizing the primary link according to the shortest path rule. To verify this, generate mtrace from Client 1 to Server C in Domain B. 29

IP Multicast Technology Overview

IP Multicast Technology Overview IP multicast is a bandwidth-conserving technology that reduces traffic by delivering a single stream of information simultaneously to potentially thousands of businesses and homes. Applications that take

More information

Configuring IP Multicast Routing

Configuring IP Multicast Routing 34 CHAPTER This chapter describes how to configure IP multicast routing on the Cisco ME 3400 Ethernet Access switch. IP multicasting is a more efficient way to use network resources, especially for bandwidth-intensive

More information

Multicast Technology White Paper

Multicast Technology White Paper Multicast Technology White Paper Keywords: Multicast, IGMP, IGMP Snooping, PIM, MBGP, MSDP, and SSM Mapping Abstract: The multicast technology implements high-efficiency point-to-multipoint data transmission

More information

IP Multicast Technology Overview

IP Multicast Technology Overview IP multicast is a bandwidth-conserving technology that reduces traffic by delivering a single stream of information simultaneously to potentially thousands of businesses and homes. Applications that take

More information

Configuring IP Multicast Routing

Configuring IP Multicast Routing 39 CHAPTER This chapter describes how to configure IP multicast routing on the Catalyst 3560 switch. IP multicasting is a more efficient way to use network resources, especially for bandwidth-intensive

More information

Lab 7-3 Routing IP Multicast with PIM Sparse Mode

Lab 7-3 Routing IP Multicast with PIM Sparse Mode Lab 7-3 Routing IP Multicast with PIM Sparse Mode Learning Objectives Implement and verify PIM-SM operation and adjacencies Implement and verify the use of a static rendezvous point Observe the shared

More information

Configuring a Rendezvous Point

Configuring a Rendezvous Point Version History Version Number Date Notes 1 03/15/2002 This document was created. The purpose of this document is to outline four recommended methods for configuring a rendezvous point (RP) in a Protocol

More information

Multicast Quick Start Configuration Guide

Multicast Quick Start Configuration Guide Multicast Quick Start Configuration Guide Document ID: 9356 Contents Introduction Prerequisites Requirements Components Used Conventions Dense Mode Sparse Mode with one RP Sparse Mode with Multiple RPs

More information

Configuring IP Multicast Routing

Configuring IP Multicast Routing CHAPTER 45 This chapter describes how to configure IP multicast routing on the Catalyst 3750 Metro switch. IP multicasting is a more efficient way to use network resources, especially for bandwidth-intensive

More information

Configuring IP Multicast Routing

Configuring IP Multicast Routing CHAPTER 46 This chapter describes how to configure IP multicast routing on the Catalyst 3750-E or 3560-E switch. IP multicasting is a more efficient way to use network resources, especially for bandwidth-intensive

More information

Module 7 Implementing Multicast

Module 7 Implementing Multicast Module 7 Implementing Multicast Lesson 1 Explaining Multicast Why Multicast? Used when sending same data to multiple receivers Better bandwidth utilization Less host/router processing Used when addresses

More information

IP Multicast Load Splitting across Equal-Cost Paths

IP Multicast Load Splitting across Equal-Cost Paths IP Multicast Load Splitting across Equal-Cost Paths This module describes how to load split IP multicast traffic from different sources, or from different sources and groups, over Equal Cost Multipath

More information

Multicast VPN C H A P T E R. Introduction to IP Multicast

Multicast VPN C H A P T E R. Introduction to IP Multicast C H A P T E R 7 Multicast VPN Multicast is a popular feature used mainly by IP-networks of Enterprise customers. Multicast allows the efficient distribution of information between a single multicast source

More information

Developing IP Muiticast Networks

Developing IP Muiticast Networks Developing IP Muiticast Networks Volume I Beau Williamson Cisco SYSTEMS CISCO PRESS Cisco Press 201 West 103rd Street Indianapolis, IN 46290 USA Table of Contents Introduction xviii Part I Fundamentals

More information

IPv6 PIM. Based on the forwarding mechanism, IPv6 PIM falls into two modes:

IPv6 PIM. Based on the forwarding mechanism, IPv6 PIM falls into two modes: Overview Protocol Independent Multicast for IPv6 () provides IPv6 multicast forwarding by leveraging static routes or IPv6 unicast routing tables generated by any IPv6 unicast routing protocol, such as

More information

Multicast overview. Introduction to multicast. Information transmission techniques. Unicast

Multicast overview. Introduction to multicast. Information transmission techniques. Unicast Contents Multicast overview 1 Introduction to multicast 1 Information transmission techniques 1 Multicast features 3 Common notations in multicast 4 Multicast advantages and applications 4 Multicast models

More information

Configuring PIM. Information About PIM. Send document comments to CHAPTER

Configuring PIM. Information About PIM. Send document comments to CHAPTER CHAPTER 3 This chapter describes how to configure the Protocol Independent Multicast (PIM) features on Cisco NX-OS switches in your IPv4 networks. This chapter includes the following sections: Information

More information

Internet2 Multicast Workshop

Internet2 Multicast Workshop Internet2 Multicast Workshop University of British Columbia Vancouver, BC May, 2004 Acknowledgements Greg Shepherd Beau Williamson Marshall Eubanks Bill Nickless Caren Litvanyi Patrick Dorn Leonard Giuliano

More information

LISP Multicast. Finding Feature Information. Prerequisites for LISP Multicast

LISP Multicast. Finding Feature Information. Prerequisites for LISP Multicast The feature introduces support for carrying multicast traffic over a Locator ID Separation Protocol (LISP) overlay. This support currently allows for unicast transport of multicast traffic with head-end

More information

Configuring Basic IP Multicast

Configuring Basic IP Multicast IP multicast is a bandwidth-conserving technology that reduces traffic by delivering a single stream of information simultaneously to potentially thousands of corporate businesses and homes. Applications

More information

Multicast overview. Introduction to multicast. Information transmission techniques. Unicast

Multicast overview. Introduction to multicast. Information transmission techniques. Unicast Contents Multicast overview 1 Introduction to multicast 1 Information transmission techniques 1 Multicast features 3 Common notations in multicast 4 Multicast benefits and applications 4 Multicast models

More information

Table of Contents 1 PIM Configuration 1-1

Table of Contents 1 PIM Configuration 1-1 Table of Contents 1 PIM Configuration 1-1 PIM Overview 1-1 Introduction to PIM-DM 1-2 How PIM-DM Works 1-2 Introduction to PIM-SM 1-4 How PIM-SM Works 1-5 Introduction to Administrative Scoping in PIM-SM

More information

BASIC MULTICAST TROUBLESHOOTING. Piotr Wojciechowski (CCIE #25543)

BASIC MULTICAST TROUBLESHOOTING. Piotr Wojciechowski (CCIE #25543) BASIC MULTICAST TROUBLESHOOTING Piotr Wojciechowski (CCIE #25543) ABOUT ME Senior Network Engineer MSO at VeriFone Inc. Previously Network Solutions Architect at one of top polish IT integrators CCIE #25543

More information

Multicast as an ISP service

Multicast as an ISP service Multicast as an ISP service Lecture slides for S-38.3192 15.2.2007 Mika Ilvesmäki Networking laboratory Goals of this lecture After this lecture you will be able to Give an overall technical view of multicast

More information

Advanced Network Training Multicast

Advanced Network Training Multicast Division of Brocade Advanced Network Training Multicast Larry Mathews Systems Engineer lmathews@brocade.com Training Objectives Session will concentrate on Multicast with emphasis on Protocol Independent

More information

Copyright 2009 Internetwork Expert i

Copyright 2009 Internetwork Expert i Copyright Information, Inc. All rights reserved. The following publication, CCIE R&S Lab Workbook Volume I Version 5.0, was developed by Internetwork Expert, Inc. All rights reserved. No part of this publication

More information

Viewing IP and MPLS Multicast Configurations

Viewing IP and MPLS Multicast Configurations CHAPTER 19 These topics provide an overview of the IP Multicast technology and describe how to view IP and multicast configurations in Prime Network Vision: IP and MPLS Multicast Configuration: Overview,

More information

Configuring Basic IP Multicast

Configuring Basic IP Multicast IP multicast is a bandwidth-conserving technology that reduces traffic by delivering a single stream of information simultaneously to potentially thousands of corporate businesses and homes. Applications

More information

Configuring Bidirectional PIM

Configuring Bidirectional PIM Configuring Bidirectional PIM This chapter describes how to configure the Bidirectional PIM (bidir-pim) feature. Bidir-PIM is a variant of the Protocol Independent Multicast (PIM) suite of routing protocols

More information

Table of Contents 1 MSDP Configuration 1-1

Table of Contents 1 MSDP Configuration 1-1 Table of Contents 1 MSDP Configuration 1-1 MSDP Overview 1-1 Introduction to MSDP 1-1 How MSDP Works 1-2 Protocols and Standards 1-7 MSDP Configuration Task List 1-7 Configuring Basic Functions of MSDP

More information

Table of Contents Chapter 1 Multicast Routing and Forwarding Configuration

Table of Contents Chapter 1 Multicast Routing and Forwarding Configuration Table of Contents Table of Contents... 1-1 1.1 Multicast Routing and Forwarding Overview... 1-1 1.1.1 Introduction to Multicast Routing and Forwarding... 1-1 1.1.2 RPF Mechanism... 1-2 1.1.3 Multicast

More information

ITEC310 Computer Networks II

ITEC310 Computer Networks II ITEC310 Computer Networks II Chapter 22 Network Layer:, and Routing Department of Information Technology Eastern Mediterranean University Objectives 2/131 After completing this chapter you should be able

More information

IP Multicast: PIM Configuration Guide, Cisco IOS Release 12.4T

IP Multicast: PIM Configuration Guide, Cisco IOS Release 12.4T IP Multicast: PIM Configuration Guide, Cisco IOS Release 12.4T Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS

More information

IP Multicasting: Explaining Multicast Cisco Systems, Inc. All rights reserved. Cisco Academy

IP Multicasting: Explaining Multicast Cisco Systems, Inc. All rights reserved. Cisco Academy IP Multicasting: Explaining Multicast 2008 Cisco Systems, Inc. All rights reserved. Cisco Academy 1 IP Multicast Distribute information to large audiences over an IP network 2008 Cisco Systems, Inc. All

More information

IP Multicast: PIM Configuration Guide, Cisco IOS Release 15S

IP Multicast: PIM Configuration Guide, Cisco IOS Release 15S First Published: November 05, 2012 Last Modified: July 30, 2013 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS

More information

IP Multicast. What is multicast?

IP Multicast. What is multicast? IP Multicast 1 What is multicast? IP(v4) allows a host to send packets to a single host (unicast), or to all hosts (broadcast). Multicast allows a host to send packets to a subset of all host called a

More information

Load Splitting IP Multicast Traffic over ECMP

Load Splitting IP Multicast Traffic over ECMP Load Splitting IP Multicast Traffic over ECMP Last Updated: August 24, 2012 This module describes how to load split IP multicast traffic over Equal Cost Multipath (ECMP). Multicast traffic from different

More information

Why multicast? The concept of multicast Multicast groups Multicast addressing Multicast routing protocols MBONE Multicast applications Conclusions

Why multicast? The concept of multicast Multicast groups Multicast addressing Multicast routing protocols MBONE Multicast applications Conclusions Tuomo Karhapää tuomo.karhapaa@otaverkko.fi Otaverkko Oy Why multicast? The concept of multicast Multicast groups Multicast addressing Multicast routing protocols MBONE Multicast applications Conclusions

More information

Implementing Multicast Service Reflection

Implementing Multicast Service Reflection Implementing Multicast Service Reflection First Published: September 22, 2006 Last Updated: June 4, 2010 The Cisco Multicast Service Reflection feature provides the capability for users to translate externally

More information

Configuring Multicast VPN Extranet Support

Configuring Multicast VPN Extranet Support Configuring Multicast VPN Extranet Support First Published: December 4, 2006 Last Updated: June 10, 2011 The Multicast VPN Extranet Support feature (sometimes referred to as the MVPN Extranet Support feature)

More information

Multicast H3C Low-End Ethernet Switches Configuration Examples. Table of Contents

Multicast H3C Low-End Ethernet Switches Configuration Examples. Table of Contents Table of Contents Table of Contents Chapter 1 Protocol Overview... 1-1 1.1 Overview... 1-1 1.2 Support of Features... 1-2 1.3 Configuration Guidance... 1-3 1.3.1 Configuring IGMP Snooping... 1-3 1.3.2

More information

Table of Contents 1 MSDP Configuration 1-1

Table of Contents 1 MSDP Configuration 1-1 Table of Contents 1 MSDP Configuration 1-1 MSDP Overview 1-1 Introduction to MSDP 1-1 How MSDP Works 1-2 Multi-Instance MSDP 1-7 Protocols and Standards 1-7 MSDP Configuration Task List 1-7 Configuring

More information

Monitoring and Maintaining IP Multicast

Monitoring and Maintaining IP Multicast This module describes many ways to monitor and maintain an IP multicast network, such as displaying which neighboring multicast routers are peering with the local router displaying multicast packet rates

More information

Financial Services Design for High Availability

Financial Services Design for High Availability Financial Services Design for High Availability Version History Version Number Date Notes 1 March 28, 2003 This document was created. This document describes the best practice for building a multicast

More information

Multicast Communications

Multicast Communications Multicast Communications Multicast communications refers to one-to-many or many-tomany communications. Unicast Broadcast Multicast Dragkedja IP Multicasting refers to the implementation of multicast communication

More information

MPLS VPN--Inter-AS Option AB

MPLS VPN--Inter-AS Option AB The feature combines the best functionality of an Inter-AS Option (10) A and Inter-AS Option (10) B network to allow a Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) service provider

More information

This chapter describes how to configure the Cisco ASA to use the multicast routing protocol.

This chapter describes how to configure the Cisco ASA to use the multicast routing protocol. This chapter describes how to configure the Cisco ASA to use the multicast routing protocol. About, page 1 Guidelines for, page 4 Enable, page 4 Customize, page 5 Monitoring for PIM, page 16 Example for,

More information

Using MSDP to Interconnect Multiple PIM-SM Domains

Using MSDP to Interconnect Multiple PIM-SM Domains Using MSDP to Interconnect Multiple PIM-SM Domains This module describes the tasks associated with using Multicast Source Discovery Protocol (MSDP) to interconnect multiple Protocol Independent Multicast

More information

ASM. Engineering Workshops

ASM. Engineering Workshops 1 ASM 2 ASM Allows SPTs and RPTs RP: Matches senders with receivers Provides network source discovery Typically uses RPT to bootstrap SPT RPs can be learned via: Static configuration recommended Anycast-RP

More information

Exercises to Communication Systems

Exercises to Communication Systems Exercises to Communication Systems IP Multicast Additional Slides Dr.-Ing. Falko Dressler Department of Computer Science 7 University of Erlangen ÜKS, WS 05/06 1 IP Multicast Introduction Internet Group

More information

Configuring MSDP. MSDP overview. How MSDP works. MSDP peers

Configuring MSDP. MSDP overview. How MSDP works. MSDP peers Contents Configuring MSDP 1 MSDP overview 1 How MSDP works 1 MSDP support for VPNs 6 Protocols and standards 6 MSDP configuration task list 6 Configuring basic MSDP functions 7 Configuration prerequisites

More information

IP Multicast: PIM Configuration Guide, Cisco IOS Release 15M&T

IP Multicast: PIM Configuration Guide, Cisco IOS Release 15M&T First Published: 2012-11-21 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE

More information

IP Multicast: PIM Configuration Guide

IP Multicast: PIM Configuration Guide Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION

More information

IP Multicast: PIM Configuration Guide, Cisco IOS Release 15SY

IP Multicast: PIM Configuration Guide, Cisco IOS Release 15SY First Published: October 15, 2012 Last Modified: February 12, 2013 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800

More information

MPLS VPN Inter-AS Option AB

MPLS VPN Inter-AS Option AB First Published: December 17, 2007 Last Updated: September 21, 2011 The feature combines the best functionality of an Inter-AS Option (10) A and Inter-AS Option (10) B network to allow a Multiprotocol

More information

IP Multicast: PIM Configuration Guide, Cisco IOS XE Release 3S

IP Multicast: PIM Configuration Guide, Cisco IOS XE Release 3S First Published: 2012-11-05 Last Modified: 2018-01-10 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387)

More information

What is IPv4 multicast? Deference between Unicast & Multicast Simulate Multicast Streaming using one Machine

What is IPv4 multicast? Deference between Unicast & Multicast Simulate Multicast Streaming using one Machine What is IPv4 multicast? It is a bandwidth-conserving technology delivering a single stream of information simultaneously to a large or small number of endpoints within the network. such as video/audio

More information

Configuring SSM. Finding Feature Information. Prerequisites for Configuring SSM

Configuring SSM. Finding Feature Information. Prerequisites for Configuring SSM Finding Feature Information, page 1 Prerequisites for, page 1 Restrictions for, page 2 Information About SSM, page 3 How to Configure SSM, page 7 Monitoring SSM, page 15 Configuration Examples for Source

More information

Configuring MSDP. Overview. How MSDP operates. MSDP peers

Configuring MSDP. Overview. How MSDP operates. MSDP peers Contents Configuring MSDP 1 Overview 1 How MSDP operates 1 MSDP support for VPNs 6 Protocols and standards 6 MSDP configuration task list 7 Configuring basic MSDP functions 7 Configuration prerequisites

More information

Lab 7-1 Implementing IGMP and IGMP Snooping

Lab 7-1 Implementing IGMP and IGMP Snooping Lab 7-1 Implementing IGMP and IGMP Snooping Learning Objectives Configure IGMP to join interfaces to a multicast group Verify the operation of IGMP at Layer 3 Analyze IGMP packets and packets sent to multicast

More information

PIM Allow RP. Finding Feature Information. Restrictions for PIM Allow RP

PIM Allow RP. Finding Feature Information. Restrictions for PIM Allow RP This module describes how to configure the feature in IPv4 or IPv6 networks for inter-connecting Protocol Independent Multicast (PIM) Sparse Mode (SM) domains with different rendezvous points (RPs). enables

More information

Introduction to Multicast Routing View PDF

Introduction to Multicast Routing View PDF Introduction to Multicast Routing Riverstone Networks Advanced Technical Documentation Support Home Documentation Home Introduction to Multicast Routing View PDF Michael Gibbs, Riverstone Networks ABSTRACT

More information

Implementing IPv6 Multicast

Implementing IPv6 Multicast Finding Feature Information, page 1 Information About Routing, page 1, page 8 Finding Feature Information Your software release may not support all the features documented in this module. For the latest

More information

IP Multicast. Overview. Casts. Tarik Čičić University of Oslo December 2001

IP Multicast. Overview. Casts. Tarik Čičić University of Oslo December 2001 IP Multicast Tarik Čičić University of Oslo December 00 Overview One-to-many communication, why and how Algorithmic approach (IP) multicast protocols: host-router intra-domain (router-router) inter-domain

More information

Advanced Networking. Multicast

Advanced Networking. Multicast Advanced Networking Multicast Renato Lo Cigno Renato.LoCigno@dit.unitn.it Homepage: disi.unitn.it/locigno/index.php/teaching-duties/advanced-networking Multicasting Addresses that refer to group of hosts

More information

Configuring IP Multicast

Configuring IP Multicast CHAPTER 27 This chapter describes IP multicast routing on the Catalyst 4500 series switch. It also provides procedures and examples to configure IP multicast routing. Note For complete syntax and usage

More information

Chapter 19 Network Layer: Logical Addressing

Chapter 19 Network Layer: Logical Addressing Chapter 19 Network Layer: Logical Addressing 19.1 Copyright The McGraw-Hill Companies, Inc. Permission required for reproduction or display. 19.2 19-1 IPv4 ADDRESSES An IPv4 address is a 32-bit address

More information

Rendezvous Point Engineering

Rendezvous Point Engineering Rendezvous Point Engineering Last updated: November 2008 Introduction A Rendezvous Point (RP) is a router in a multicast network domain that acts as a shared root for a multicast shared tree. Any number

More information

IP Multicast: PIM Configuration Guide

IP Multicast: PIM Configuration Guide Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION

More information

Layer 3 Routing (UI 2.0) User s Manual

Layer 3 Routing (UI 2.0) User s Manual User s Manual Edition 3.3, November 2018 www.moxa.com/product Models covered by this manual: IKS-G6824A, ICS-G7826A, ICS-G7828A, ICS-G7848A, ICS-G7850A, ICS-G7852A, PT-G7828 Series 2018 Moxa Inc. All rights

More information

Table of Contents Chapter 1 IPv6 PIM Configuration

Table of Contents Chapter 1 IPv6 PIM Configuration Table of Contents Table of Contents... 1-1 1.1 IPv6 PIM Overview... 1-1 1.1.1 Introduction to IPv6 PIM-DM... 1-2 1.1.2 How IPv6 PIM-DM Works... 1-2 1.1.3 Introduction to IPv6 PIM-SM... 1-5 1.1.4 How IPv6

More information

Multicast Communications. Slide Set were original prepared by Dr. Tatsuya Susa

Multicast Communications. Slide Set were original prepared by Dr. Tatsuya Susa Multicast Communications Slide Set were original prepared by Dr. Tatsuya Susa Outline 1. Advantages of multicast 2. Multicast addressing 3. Multicast Routing Protocols 4. Multicast in the Internet 5. IGMP

More information

HP 6125G & 6125G/XG Blade Switches

HP 6125G & 6125G/XG Blade Switches HP 6125G & 6125G/XG Blade Switches IP Multicast Configuration Guide Part number: 5998-3158a Software version: Release 2103 and later Document version: 6W102-20141218 Legal and notice information Copyright

More information

Configuring VRF-lite CHAPTER

Configuring VRF-lite CHAPTER CHAPTER 36 Virtual Private Networks (VPNs) provide a secure way for customers to share bandwidth over an ISP backbone network. A VPN is a collection of sites sharing a common routing table. A customer

More information

Connecting to a Service Provider Using External BGP

Connecting to a Service Provider Using External BGP Connecting to a Service Provider Using External BGP First Published: May 2, 2005 Last Updated: August 21, 2007 This module describes configuration tasks that will enable your Border Gateway Protocol (BGP)

More information

Configuring multicast VPN

Configuring multicast VPN Contents Configuring multicast VPN 1 Multicast VPN overview 1 Multicast VPN overview 1 MD-VPN overview 3 Protocols and standards 6 How MD-VPN works 6 Share-MDT establishment 6 Share-MDT-based delivery

More information

Chapter 24 PIM Commands

Chapter 24 PIM Commands Chapter 24 PIM Commands bsr-candidate Configures the Routing Switch as a candidate PIM Sparse Bootstrap Router (BSR). To configure the Routing Switch as a candidate BSR, enter a command such as the following:

More information

Verifying IPv4 Multicast Forwarding Using the MFIB

Verifying IPv4 Multicast Forwarding Using the MFIB Verifying IPv4 Multicast Forwarding Using the MFIB This module describes how to verify IPv4 multicast forwarding using the Multicast Forwarding Information Base (MFIB) in multicast networks operating in

More information

Configuring basic MBGP

Configuring basic MBGP Contents Configuring MBGP 1 MBGP overview 1 Protocols and standards 1 MBGP configuration task list 1 Configuring basic MBGP 2 Controlling route advertisement and reception 2 Configuration prerequisites

More information

What is Multicasting? Multicasting Fundamentals. Unicast Transmission. Agenda. L70 - Multicasting Fundamentals. L70 - Multicasting Fundamentals

What is Multicasting? Multicasting Fundamentals. Unicast Transmission. Agenda. L70 - Multicasting Fundamentals. L70 - Multicasting Fundamentals What is Multicasting? Multicasting Fundamentals Unicast transmission transmitting a packet to one receiver point-to-point transmission used by most applications today Multicast transmission transmitting

More information

IP Multicast. Falko Dressler Regionales Rechenzentrum Grundzüge der Datenkommunikation IP Multicast

IP Multicast. Falko Dressler Regionales Rechenzentrum Grundzüge der Datenkommunikation IP Multicast Falko Dressler Regionales Rechenzentrum falko.dressler@rrze.uni-erlangen.de 1 Agenda Basics Principles of IP multicast, addressing, TTL Internet Group Management Protocol (IGMP) IGMPv1, v2, v3 Layer-2

More information

HP 5920 & 5900 Switch Series

HP 5920 & 5900 Switch Series HP 5920 & 5900 Switch Series IP Multicast Configuration Guide Part number: 5998-3373 Software version: Release2207 Document version: 6W100-20121130 Legal and notice information Copyright 2012 Hewlett-Packard

More information

CCIE Service Provider v3.0 Sample Lab

CCIE Service Provider v3.0 Sample Lab CCIE Service Provider v3.0 Sample Lab Part 6/7 Vincent Jun Ling Zhou CCIE Service Provider Product Manager Cisco Systems SP Sample Lab Main Topology R13 S2/1.135.13/24 Backbone Carrier SP AS 1002 S2/1

More information

IGMP Static Group Range Support

IGMP Static Group Range Support This module describes how you can simplify the administration of networks with devices that require static group membership entries on many interfaces by configuring IGMP static group range support to

More information

Implementing IPv6 Multicast

Implementing IPv6 Multicast Implementing IPv6 Multicast Last Updated: November 14, 2011 Traditional IP communication allows a host to send packets to a single host (unicast transmission) or to all hosts (broadcast transmission).

More information

How did IP Multicast get so complicated?

How did IP Multicast get so complicated? How did IP Multicast get so complicated? Mark Handley ACIRI mjh@aciri.org Overview IP Multicast Service Model Multicast Addresses DVMRP (1988-1993) Broadcast and Prune PIM-DM (~1993) DVMRP for "real" routers

More information

Building the Routing Table. Introducing the Routing Table Directly Connected Networks Static Routing Dynamic Routing Routing Table Principles

Building the Routing Table. Introducing the Routing Table Directly Connected Networks Static Routing Dynamic Routing Routing Table Principles Building the Routing Table Introducing the Routing Table Directly Connected Networks Static Routing Dynamic Routing Routing Table Principles Introducing the Routing Table R1# show ip route Codes: C - connected,

More information

Configuring Multicast Routing

Configuring Multicast Routing CHAPTER 24 This chapter describes how to configure the ASA to use the multicast routing protocol and includes the following sections: Information About Multicast Routing, page 24-17 Licensing Requirements

More information

IPv6 Multicast: PIM Sparse Mode

IPv6 Multicast: PIM Sparse Mode IPv6 multicast provides support for intradomain multicast routing using PIM sparse mode (PIM-SM). PIM-SM uses unicast routing to provide reverse-path information for multicast tree building, but it is

More information

HP 5500 HI Switch Series

HP 5500 HI Switch Series HP 5500 HI Switch Series IP Multicast Configuration Guide Part number: 5998-2380 Software version: Release 5203 and Release 5206 Document version: 6W102-20140228 Legal and notice information Copyright

More information

Contents. Configuring MSDP 1

Contents. Configuring MSDP 1 Contents Configuring MSDP 1 Overview 1 How MSDP works 1 MSDP support for VPNs 6 Protocols and standards 6 MSDP configuration task list 7 Configuring basic MSDP features 7 Configuration prerequisites 7

More information

IPv6 Multicast: PIM Sparse Mode

IPv6 Multicast: PIM Sparse Mode Finding Feature Information, page 1 Information About IPv6 Multicast PIM Sparse Mode, page 1 How to Configure IPv6 Multicast PIM Sparse Mode, page 6 Configuration Examples for IPv6 Multicast PIM Sparse

More information

ICS 351: Today's plan. routing protocol comparison encapsulation network dynamics multicasting in general IP multicasting IGMP PIM

ICS 351: Today's plan. routing protocol comparison encapsulation network dynamics multicasting in general IP multicasting IGMP PIM ICS 351: Today's plan routing protocol comparison encapsulation network dynamics multicasting in general IP multicasting IGMP PIM what routing is not: Ethernet switching does not use IP addresses in any

More information

ETSF10 Internet Protocols Routing on the Internet

ETSF10 Internet Protocols Routing on the Internet ETSF10 Internet Protocols Routing on the Internet 2012, Part 2, Lecture 1.2 Kaan Bür, Jens Andersson Routing on the Internet Unicast routing protocols (part 2) [ed.4 ch.22.4] [ed.5 ch.20.3] Forwarding

More information

Multicast Source Discovery Protocol (MSDP)

Multicast Source Discovery Protocol (MSDP) Multicast Source Discovery Protocol (MSDP) Module 6 2000, Cisco Systems, Inc. 1 Copyright 1998-2000, Cisco Systems, Inc. Module6.ppt 1 Module Objectives Understand the issues relating to Interdomain IP

More information

IPv6 PIM-DM configuration example 36 IPv6 PIM-SM non-scoped zone configuration example 39 IPv6 PIM-SM admin-scoped zone configuration example 42 IPv6

IPv6 PIM-DM configuration example 36 IPv6 PIM-SM non-scoped zone configuration example 39 IPv6 PIM-SM admin-scoped zone configuration example 42 IPv6 Contents Configuring IPv6 PIM 1 Overview 1 IPv6 PIM-DM overview 1 IPv6 PIM-SM overview 3 IPv6 BIDIR-PIM overview 8 IPv6 administrative scoping overview 11 IPv6 PIM-SSM overview 13 Relationship among IPv6

More information

Chapter 4 Lab 4-2, Redistribution Between EIGRP and OSPF

Chapter 4 Lab 4-2, Redistribution Between EIGRP and OSPF Chapter 4 Lab 4-2, Redistribution Between EIGRP and OSPF Topology Objectives Review EIGRP and OSPF configuration. Redistribute into EIGRP. Redistribute into OSPF. Summarize routes in EIGRP. Filter routes

More information

Implementing Cisco IP Routing

Implementing Cisco IP Routing ROUTE Implementing Cisco IP Routing Volume 3 Version 1.0 Student Guide Text Part Number: 97-2816-02 DISCLAIMER WARRANTY: THIS CONTENT IS BEING PROVIDED AS IS. CISCO MAKES AND YOU RECEIVE NO WARRANTIES

More information

Advanced IP Multicast Routing

Advanced IP Multicast Routing 1 Advanced IP Multicast Routing Session 2 Other Related Presentations Multicast Sessions Session # Title 2214 Introduction to IP Multicast 2215 PIM Multicast Routing 2216 Deploying IP Multicast Advanced

More information

Basic Multicast Troubleshooting Tools

Basic Multicast Troubleshooting Tools Basic Multicast Troubleshooting Tools Document ID: 13726 Contents Introduction Prerequisites Requirements Components Used Conventions Troubleshooting Strategies Check Source Packet Flow Check Network Signaling

More information