![]() R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT This command examines the multicast route (mroute) for the group address 10.224.1.1: 75a#show ip mroute 10.224.1.1įlags: D - Dense, S - Sparse, C - Connected, L - Local, P - Pruned First, enter the show ip mroute 224.1.1.1 command in order to check activity on Router 75a. Hosts directly connected to Router 75a receive the multicast feed, but hosts directly connected to Router 72a do not. In this figure, multicast packets come into E0/0 of Router 75a from a server whose IP address is 10.1.1.1 and sends to group 10.224.1.1. Network Diagram Example of Multicast RPF Failure This network diagram is used as an example. This section provides a solution to the common problem of an IP multicast RPF failure. Router Does Not Forward Multicast Packets to Host Due to RPF Failure The case studies listed here are generic across the protocols, except where noted. You can see which commands are used in order to quickly pinpoint the problem and learn how to resolve it. The case studies in this document walk you through the process to troubleshoot various problems. Like unicast routing, multicast routing has several available protocols, such as Protocol Independent Multicast dense mode (PIM-DM), PIM sparse mode (PIM-SM), Distance Vector Multicast Routing Protocol (DVMRP), Multicast Border Gateway Protocol (MBGP), and Multicast Source Discovery Protocol (MSDP). Once a packet passes this RPF check, multicast routing forwards the packet based only upon the destination address. Multicast routing does not forward a packet unless the source of the packet passes a RPF check. When a multicast packet arrives on an interface, the RPF process checks to ensure that this incoming interface is the outgoing interface used by unicast routing in order to reach the source of the multicast packet. Multicast has a concept of Reverse Path Forwarding (RPF) check. When you troubleshoot multicast routing, the primary concern is the source address. If your network is live, ensure that you understand the potential impact of any command. ![]() All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment. This document is not restricted to specific software and hardware versions. ![]() There are no specific requirements for this document. This document describes common problems and solutions for IP multicast. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |