INTRO

Hi Dr. Ida, in this video I am going to explain about Multicast IP Routing with the focus of PIM-DM.
Before we moved to PIM-DM, we need to understand the basics of Multicast IP Routing. The objective of
Multicast IP Routing protocols in this case study of mine is to distribute data. For instance, audio and
video streaming broadcasts to multiple recipients. By using multicast, a source can send a single copy of
data to a single multicast address, which is then distribute to an entire group of recipients.
Multicast group identifies a set of recipients that are interested in the particular data stream. The IPv4
address for multicast is set by IANA is 224.0.0.0 – 239.255.255.255. In this case study, I have used
224.1.1.1.
There are actually two version of PIM, which is PIM-SM and PIM-DM. PIM-SM provides efficient
routing for a group distributed sparsely across a wide area. Whilst PIM-DM provides multicast routing for
a densely populated group. A sparse network is a network with less number of links than the maximum
possible number of links within the same network. While a dense network PIM protocol called, protocol
independent because it depends on existing unicast routes to calculate the reverse path forwarding.
Although, PIM-DM requires the presence of a unicast routing protocol (OSPF) for finding routes back to
the source node, but it’s independent of the mechanism employed by any specific unicast routing
protocol; in this case OSPF. Then, PIM-DM uses RPM (Robust Point Matching) algorithm to form
delivery trees.

L = N2
NETWORK TOPOLOGY
This network topology consist of (1) Multicast Server, (3) Routers and (2) PCs. The IP address is set to
each interface(s) used at the router(s) and the end host. As shown in the network topology, the IP
addresses are set accordingly.
CONFIGURATIONS
1. IP Configurations
Enter system-view and use interface [interface-name] to enter interface view. Then configure ip address at
each interface(s) used.
2. OSPF Configuration at each router
Enter ospf 1  area 0  network id wildcard
Repeat on each router
3. Pim-dm
Use multicast routing-enable at each router. The enable pim dm at every interfaces used. For example at
RTA, we use ge 0/0/0 – 2. Then we enable pim silent on interface that connects directly to host network
segment to prevent malicious hosts from constructing pseudo PIM hello messages to attack the router.
While the IGMP is used by multicast routers to keep track of membership in a multicast group. Where
multicast group member can join the multicast group and leave the multicast group (query membership).
Multicast router will regularly multicast an IGMP query to all host in this case PC1/PC2, then PC1/2 will
respond by sending back IGMP report. Multicast router keeps a table on the multicast groups that have a
member of hosts joined the multicast group.
VERIFICATION
First, we check connectivity between router(s) and pc(s) using the ping command. For example <RTB>
ping 192.168.1.1 which is the multicast server. Repeat steps by checking connectivity to rta-rtb,rta-rtc,rtb-
rtc,pc1-msc,pc1-pc2 and pc2-msc. If there are error for instance, request time out of and host is
unreachable, we should re-track our moves during the configuration part.
Then we use “dis pim int” to view which interface(s) are using pim dm protocol on the router. Then we
use “dis pim neighbor” to view the relationship between routers. As we can see, there are total number of
neighbor in this case neighbor of RTB.
ANALYSIS
In order for us to analyze, we first have to run VLC on the multicast server to act as video server. Then,
the network should be flooded with the stream data. Which we can verify using Wireshark to see the UDP
packets. After that, we use “dis pim rout” command to observe the change of pim routing table at each
router. Then from the routing table we can construct the MDT based on the Source-based tree entries in
the pim routing table. Pim routing table should consists of core-base entries and source-base entries. The
source base entries are the one with (S,G) pair where S is source and G is multicast group. Im excluding
core base entries because the purpose of this case study is to build and manipulate the MDT, which is
multicast distribution tree. This MDT is established base on the source base entries. So if we change the
network topology to by exchanging place of multicast server with PC2/1. The resultant MDT will looks
different like this. So based on the MDT constructed we can say that the source-base tree are rooted at the
router nearest to the multicast source. And there are one tree for each source. So in this scenario Multicast
server acts as source so RTA (which is the closest router to the multicast source) will become the tree
root.
Flood and prune protocols
We can use wireshark to verify the network flooding when the multicast server is flooding the network.
When sender starts sending, the traffic is flooded out through the network. To stop the unnecessary traffic
RTB know PC1 is no longer receiving the data, so PC1 can send prune message to RTB and RTB will
remove a link/entries from multicase routing table.