WEBVTT

1
00:00.000 --> 00:03.800
When we left off, we had configured R4 for multicast routing.

2
00:03.800 --> 00:09.000
We also did a ping to the multicast group, 224.67 to 83.

3
00:09.000 --> 00:11.300
And because we sourced it from gig two zero,

4
00:11.300 --> 00:15.200
that's why it's showing the source to us like a server at 23.1.2.4,

5
00:15.200 --> 00:16.500
generating that content.

6
00:16.500 --> 00:18.600
And because R2 is our rendezvous point,

7
00:18.600 --> 00:21.100
R4 forwarded that traffic over to R2.

8
00:21.100 --> 00:22.700
And that's where we're going to pick up.

9
00:22.700 --> 00:23.700
Now at the moment,

10
00:23.700 --> 00:26.200
in fact, let me just do it the upper key into a refresh here.

11
00:26.200 --> 00:27.200
At the moment,

12
00:27.200 --> 00:31.900
this router R2 is not bothering forwarding that group
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:27.200 --> 00:31.900
this router R2 is not bothering forwarding that group

13
00:31.900 --> 00:35.700
224.67 to 83 out any outgoing interface list.

14
00:35.700 --> 00:37.400
That's because in sparse mode,

15
00:37.400 --> 00:38.800
no one's requested it.

16
00:38.800 --> 00:39.900
So to change that,

17
00:39.900 --> 00:43.800
let's go down to R1 and let's simulate a client.

18
00:43.800 --> 00:47.000
In fact, we can just do this on gig two zero of R1.

19
00:47.000 --> 00:49.000
And let's join that group.

20
00:49.000 --> 00:51.900
When we join that group here on R1's gig two zero,

21
00:51.900 --> 00:55.300
that'll cause R1 send a request up to the rendezvous point saying,

22
00:55.300 --> 00:55.900
you know what?

23
00:55.900 --> 00:57.000
I need that traffic.

24
00:57.000 --> 00:58.500
I need that forwarded down to me.

25
00:58.500 --> 01:01.800
Also, if the switch is doing I GMP snooping,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
00:58.500 --> 01:01.800
Also, if the switch is doing I GMP snooping,

26
01:01.800 --> 01:06.700
it's also going to include in the forwarding table for I GMP snooping

27
01:06.700 --> 01:10.000
that multicast group out the switches gig zero one,

28
01:10.000 --> 01:11.500
which leads to gig zero zero.

29
01:11.500 --> 01:11.800
In fact,

30
01:11.800 --> 01:14.400
let's go to the switch for a moment and confirm that as well.

31
01:14.400 --> 01:15.200
So here on the switch,

32
01:15.200 --> 01:16.200
let's do a show IP,

33
01:16.200 --> 01:19.900
I GMP snooping press center and sure enough,

34
01:19.900 --> 01:22.900
it's enabled and it's enabled for VLAN one,

35
01:22.900 --> 01:25.400
which is great and supporting version two.

36
01:25.400 --> 01:26.000
That's great.

37
01:26.000 --> 01:28.700
Let's do a show interface status press center.

38
01:28.700 --> 01:32.800
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

38
01:28.700 --> 01:32.800
So our one is currently connected off of the switches gig zero slash one.

39
01:32.800 --> 01:35.100
Our two is connected off gig zero slash two.

40
01:35.100 --> 01:37.000
Also, if we go back to our two for a moment,

41
01:37.000 --> 01:39.500
which is the root or tree and let's hit the up here.

42
01:39.500 --> 01:40.600
Can do the show IP,

43
01:40.600 --> 01:42.000
Emrout one more time.

44
01:42.000 --> 01:46.090
It also looks like it has timed out because there's no other traffic being

45
01:46.090 --> 01:46.500
forwarded.

46
01:46.500 --> 01:51.300
So let's go ahead back to our four and let's simulate more traffic with a ping

47
01:51.300 --> 01:53.100
to that multicast group again.

48
01:53.100 --> 01:56.200
And we'll source it from gig two zero and let's also do this.

49
01:56.200 --> 01:58.500
Let's go ahead and do a repeat count.

50
01:58.500 --> 02:02.650
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

50
01:58.500 --> 02:02.650
Let's say 1000 that'll keep it going for a while and there's a timeout involved

51
02:02.650 --> 02:02.800
.

52
02:02.800 --> 02:04.900
So that's like 2000 seconds.

53
02:04.900 --> 02:05.600
That'd be great.

54
02:05.600 --> 02:08.100
So let's go back to our two and back at our two,

55
02:08.100 --> 02:11.300
hit the up arrow key for show IP Emrout and here we go.

56
02:11.300 --> 02:13.600
So there's our star comma G.

57
02:13.600 --> 02:16.800
If you hear that term that's referring to source comma and then the group.

58
02:16.800 --> 02:19.600
So the source is 23124.

59
02:19.600 --> 02:24.200
The destination is the multicast group of two 2467 eight dot three and the

60
02:24.200 --> 02:25.500
outgoing interface is null,

61
02:25.500 --> 02:28.680
but we're going to change that because we're going to go down and simulate a

62
02:28.680 --> 02:31.100
client down here off of the gig two zero interface,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
02:28.680 --> 02:31.100
client down here off of the gig two zero interface,

63
02:31.100 --> 02:33.300
making an I GMP joining request.

64
02:33.300 --> 02:36.100
We can also do that right here from the router interface in our one,

65
02:36.100 --> 02:39.300
which from a network perspective is easier to test with.

66
02:39.300 --> 02:43.300
So if we go to our one and we do a config T and we'll go to interface.

67
02:43.300 --> 02:45.100
Let's go to the right interface here together.

68
02:45.100 --> 02:47.100
So we want to go to interface gig two zero.

69
02:47.100 --> 02:50.400
So we'll get into face gig two zero and then from here we'll do an IP,

70
02:50.400 --> 02:54.900
I GMP and space question mark and what we want to do is this one right here.

71
02:54.900 --> 02:58.100
We want to go ahead and do a joint group to join a multicast group on that

72
02:58.100 --> 03:02.000
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

72
02:58.100 --> 03:02.000
interface and we'll go ahead and put that same group of two 24 dot one.

73
03:02.000 --> 03:05.600
Nope two 24 dot 67 dot eight dot three.

74
03:05.600 --> 03:09.100
That's our group and then we do a show IP,

75
03:09.100 --> 03:13.370
I GMP space question mark and let's go ahead and type in groups and press

76
03:13.370 --> 03:13.900
center.

77
03:13.900 --> 03:17.260
So besides the ones that automatically happen, here's the one that we just

78
03:17.260 --> 03:20.300
manually joined two 24 67 dot eight dot three.

79
03:20.300 --> 03:24.720
Now what that should do is that should have caused our one to send a message up

80
03:24.720 --> 03:25.700
to our two indicating,

81
03:25.700 --> 03:26.200
you know what?

82
03:26.200 --> 03:30.700
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

82
03:26.200 --> 03:30.700
I need information or I need that group stream sent down to me and as a result,

83
03:30.700 --> 03:34.530
our two, which a moment ago we looked at that group said the outgoing interface

84
03:34.530 --> 03:35.300
is null,

85
03:35.300 --> 03:37.300
meaning I'm not sitting anywhere.

86
03:37.300 --> 03:41.000
It should now have gig one zero as an outgoing interface.

87
03:41.000 --> 03:45.630
So let's verify that as well by going back to our two and hitting the up arrow

88
03:45.630 --> 03:46.600
key for show IP,

89
03:46.600 --> 03:50.000
Emra out once again and scroll down a little bit and sure enough,

90
03:50.000 --> 03:50.500
check it out.

91
03:50.500 --> 03:53.100
There's our star, the source,

92
03:53.100 --> 03:57.300
group information, the source of the content and the multicast group identifier

93
03:57.300 --> 03:57.800
there.

94
03:57.800 --> 03:59.700
But now for the outgoing interface, check it out.

95
03:59.700 --> 04:03.500
It's now forwarding it out gig one slash zero.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

95
03:59.700 --> 04:03.500
It's now forwarding it out gig one slash zero.

96
04:03.500 --> 04:06.200
Also now that traffic is actually being forwarded down.

97
04:06.200 --> 04:10.800
The actual request was a ping. So it's going down to our one who's receiving

98
04:10.800 --> 04:12.000
that and because

99
04:12.000 --> 04:13.600
a ping request, check it out.

100
04:13.600 --> 04:15.500
Our one is responding to that as well.

101
04:15.500 --> 04:18.750
If we go back to our four, we can notice here that we have a reply to each

102
04:18.750 --> 04:19.700
other requests coming

103
04:19.700 --> 04:23.900
back from the I GMB joined interface of 10 10 0 1 and again,

104
04:23.900 --> 04:27.500
that is our ones gig two slash zero interface.

105
04:27.500 --> 04:31.100
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

105
04:27.500 --> 04:31.100
And just for grands, if we did a control shift six here and stop that pinging

106
04:31.100 --> 04:32.000
on our four,

107
04:32.000 --> 04:36.700
if we tried to sort of ping to a different address, different multicast group,

108
04:36.700 --> 04:42.100
let's go ahead and do 225 5.5.5 and we'll go ahead and I don't need to repeat

109
04:42.100 --> 04:43.300
that 1000 times because

110
04:43.300 --> 04:44.900
we have nobody who's joined that group yet.

111
04:44.900 --> 04:48.400
In fact, let's do 1000 times and we'll repeat the process that we did earlier.

112
04:48.400 --> 04:52.000
So now this multicast traffic is being generated on our two.

113
04:52.000 --> 04:55.200
If we now do a show IP Emra out press enter.

114
04:55.200 --> 05:02.550
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

114
04:55.200 --> 05:02.550
Now it has this new group 225.5.5.5 coming from the source 23.1.2.4 and

115
05:02.550 --> 05:03.100
currently there's

116
05:03.100 --> 05:06.400
nobody responding to it because nobody's joined that group.

117
05:06.400 --> 05:10.100
So if we went to another router, in fact, let's go to how about our three?

118
05:10.100 --> 05:13.500
Let's go to our three on its gig one zero and join that group.

119
05:13.500 --> 05:16.900
So if we go to our three and we go to config T interface,

120
05:16.900 --> 05:21.200
let's confirm the interface gig one zero and we join that group with an IP.

121
05:21.200 --> 05:26.900
I GMP join group and the group is 225.5.5.5.5 percenter and now that we've

122
05:26.900 --> 05:27.900
joined that group,

123
05:27.900 --> 05:32.500
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

123
05:27.900 --> 05:32.500
our four because that traffic is now being delivered down to our three is now

124
05:32.500 --> 05:33.100
able to receive

125
05:33.100 --> 05:36.100
those ping requests and then it does a unicast response back.

126
05:36.100 --> 05:42.000
So that 10 23.03 address is this interface address right here of gig one zero.

127
05:42.000 --> 05:45.880
Another thing to be aware is that there's also a cut over process in the event

128
05:45.880 --> 05:47.000
that the content

129
05:47.000 --> 05:50.700
in this case coming from our four and these be delivered to our three because

130
05:50.700 --> 05:51.200
the actual

131
05:51.200 --> 05:53.900
optimized path is from our fourth R three.

132
05:53.900 --> 05:57.100
It's going to cut over from the shared tree to the shortest path tree.

133
05:57.100 --> 06:00.920
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

133
05:57.100 --> 06:00.920
So we went back to, for example, our two knows that traffic is not being

134
06:00.920 --> 06:01.300
forwarded

135
06:01.300 --> 06:05.600
out any interfaces on the rendezvous point because it did a cut over and is

136
06:05.600 --> 06:06.100
directly

137
06:06.100 --> 06:10.100
forwarding traffic from our four here where the content is coming from down to

138
06:10.100 --> 06:10.600
our three.

139
06:10.600 --> 06:12.600
So if we generate that traffic from somewhere else,

140
06:12.600 --> 06:18.900
they say, for example, from our two and we did a ping to 225.5.5.5 and our two

141
06:18.900 --> 06:19.100
is the

142
06:19.100 --> 06:20.100
rendezvous point.

143
06:20.100 --> 06:22.900
And that's now we're going to responses and that's because our three is joined

144
06:22.900 --> 06:23.400
that also

145
06:23.400 --> 06:26.300
if we do a show IP em route press enter.

146
06:26.300 --> 06:30.890
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

146
06:26.300 --> 06:30.890
There's the S comma G or the source comma group information for this em route

147
06:30.890 --> 06:31.900
entry source

148
06:31.900 --> 06:33.300
from 10 12 02.

149
06:33.300 --> 06:38.500
That's on our two going to the group 225 005 and the outgoing interface is gig

150
06:38.500 --> 06:38.800
zero

151
06:38.800 --> 06:41.200
zero going from the root down to our three.

152
06:41.200 --> 06:45.460
So now that we've had a little bit of fun in configuring and verifying multic

153
06:45.460 --> 06:46.100
ast routing

154
06:46.100 --> 06:51.060
including focusing on me the concepts involved with it like PIM, I GMP and the

155
06:51.060 --> 06:51.500
concept of

156
06:51.500 --> 06:55.400
an RPF check in the next video, I'd like to put you on a hands on labs.

157
06:55.400 --> 06:59.300
You can get up close and personal with multiprotical routing in a Cisco

158
06:59.300 --> 06:59.900
environment.

159
06:59.900 --> 07:02.300
So if you're ready, I'll see you in the next video.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

159
06:59.900 --> 07:02.300
So if you're ready, I'll see you in the next video. www.technet24.ir