When we left off, we had configured R4 for multicast routing.
We also did a ping to the multicast group, 224.67 to 83.
And because we sourced it from gig two zero,
that's why it's showing the source to us like a server at 23.1.2.4,
generating that content.
And because R2 is our rendezvous point,
R4 forwarded that traffic over to R2.
And that's where we're going to pick up.
Now at the moment,
in fact, let me just do it the upper key into a refresh here.
At the moment,
this router R2 is not bothering forwarding that group WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
this router R2 is not bothering forwarding that group
224.67 to 83 out any outgoing interface list.
That's because in sparse mode,
no one's requested it.
So to change that,
let's go down to R1 and let's simulate a client.
In fact, we can just do this on gig two zero of R1.
And let's join that group.
When we join that group here on R1's gig two zero,
that'll cause R1 send a request up to the rendezvous point saying,
you know what?
I need that traffic.
I need that forwarded down to me.
Also, if the switch is doing I GMP snooping, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Also, if the switch is doing I GMP snooping,
it's also going to include in the forwarding table for I GMP snooping
that multicast group out the switches gig zero one,
which leads to gig zero zero.
In fact,
let's go to the switch for a moment and confirm that as well.
So here on the switch,
let's do a show IP,
I GMP snooping press center and sure enough,
it's enabled and it's enabled for VLAN one,
which is great and supporting version two.
That's great.
Let's do a show interface status press center.
So our one is currently connected off of the switches gig zero slash one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So our one is currently connected off of the switches gig zero slash one.
Our two is connected off gig zero slash two.
Also, if we go back to our two for a moment,
which is the root or tree and let's hit the up here.
Can do the show IP,
Emrout one more time.
It also looks like it has timed out because there's no other traffic being
forwarded.
So let's go ahead back to our four and let's simulate more traffic with a ping
to that multicast group again.
And we'll source it from gig two zero and let's also do this.
Let's go ahead and do a repeat count.
Let's say 1000 that'll keep it going for a while and there's a timeout involved WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's say 1000 that'll keep it going for a while and there's a timeout involved
.
So that's like 2000 seconds.
That'd be great.
So let's go back to our two and back at our two,
hit the up arrow key for show IP Emrout and here we go.
So there's our star comma G.
If you hear that term that's referring to source comma and then the group.
So the source is 23124.
The destination is the multicast group of two 2467 eight dot three and the
outgoing interface is null,
but we're going to change that because we're going to go down and simulate a
client down here off of the gig two zero interface, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
client down here off of the gig two zero interface,
making an I GMP joining request.
We can also do that right here from the router interface in our one,
which from a network perspective is easier to test with.
So if we go to our one and we do a config T and we'll go to interface.
Let's go to the right interface here together.
So we want to go to interface gig two zero.
So we'll get into face gig two zero and then from here we'll do an IP,
I GMP and space question mark and what we want to do is this one right here.
We want to go ahead and do a joint group to join a multicast group on that
interface and we'll go ahead and put that same group of two 24 dot one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
interface and we'll go ahead and put that same group of two 24 dot one.
Nope two 24 dot 67 dot eight dot three.
That's our group and then we do a show IP,
I GMP space question mark and let's go ahead and type in groups and press
center.
So besides the ones that automatically happen, here's the one that we just
manually joined two 24 67 dot eight dot three.
Now what that should do is that should have caused our one to send a message up
to our two indicating,
you know what?
I need information or I need that group stream sent down to me and as a result, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I need information or I need that group stream sent down to me and as a result,
our two, which a moment ago we looked at that group said the outgoing interface
is null,
meaning I'm not sitting anywhere.
It should now have gig one zero as an outgoing interface.
So let's verify that as well by going back to our two and hitting the up arrow
key for show IP,
Emra out once again and scroll down a little bit and sure enough,
check it out.
There's our star, the source,
group information, the source of the content and the multicast group identifier
there.
But now for the outgoing interface, check it out.
It's now forwarding it out gig one slash zero. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
It's now forwarding it out gig one slash zero.
Also now that traffic is actually being forwarded down.
The actual request was a ping. So it's going down to our one who's receiving
that and because
a ping request, check it out.
Our one is responding to that as well.
If we go back to our four, we can notice here that we have a reply to each
other requests coming
back from the I GMB joined interface of 10 10 0 1 and again,
that is our ones gig two slash zero interface.
And just for grands, if we did a control shift six here and stop that pinging WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And just for grands, if we did a control shift six here and stop that pinging
on our four,
if we tried to sort of ping to a different address, different multicast group,
let's go ahead and do 225 5.5.5 and we'll go ahead and I don't need to repeat
that 1000 times because
we have nobody who's joined that group yet.
In fact, let's do 1000 times and we'll repeat the process that we did earlier.
So now this multicast traffic is being generated on our two.
If we now do a show IP Emra out press enter.
Now it has this new group 225.5.5.5 coming from the source 23.1.2.4 and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now it has this new group 225.5.5.5 coming from the source 23.1.2.4 and
currently there's
nobody responding to it because nobody's joined that group.
So if we went to another router, in fact, let's go to how about our three?
Let's go to our three on its gig one zero and join that group.
So if we go to our three and we go to config T interface,
let's confirm the interface gig one zero and we join that group with an IP.
I GMP join group and the group is 225.5.5.5.5 percenter and now that we've
joined that group,
our four because that traffic is now being delivered down to our three is now WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
our four because that traffic is now being delivered down to our three is now
able to receive
those ping requests and then it does a unicast response back.
So that 10 23.03 address is this interface address right here of gig one zero.
Another thing to be aware is that there's also a cut over process in the event
that the content
in this case coming from our four and these be delivered to our three because
the actual
optimized path is from our fourth R three.
It's going to cut over from the shared tree to the shortest path tree.
So we went back to, for example, our two knows that traffic is not being WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we went back to, for example, our two knows that traffic is not being
forwarded
out any interfaces on the rendezvous point because it did a cut over and is
directly
forwarding traffic from our four here where the content is coming from down to
our three.
So if we generate that traffic from somewhere else,
they say, for example, from our two and we did a ping to 225.5.5.5 and our two
is the
rendezvous point.
And that's now we're going to responses and that's because our three is joined
that also
if we do a show IP em route press enter.
There's the S comma G or the source comma group information for this em route WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
There's the S comma G or the source comma group information for this em route
entry source
from 10 12 02.
That's on our two going to the group 225 005 and the outgoing interface is gig
zero
zero going from the root down to our three.
So now that we've had a little bit of fun in configuring and verifying multic
ast routing
including focusing on me the concepts involved with it like PIM, I GMP and the
concept of
an RPF check in the next video, I'd like to put you on a hands on labs.
You can get up close and personal with multiprotical routing in a Cisco
environment.
So if you're ready, I'll see you in the next video. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if you're ready, I'll see you in the next video. www.technet24.ir