1
00:00:00,000 --> 00:00:00,966

2
00:00:00,966 --> 00:00:02,898
[AUDIO LOGO]

3
00:00:02,898 --> 00:00:08,420

4
00:00:08,420 --> 00:00:12,600
So now it's finally time
to jump in and set up SSM.

5
00:00:12,600 --> 00:00:15,570
Now, this is going to
be incredibly easy.

6
00:00:15,570 --> 00:00:18,240
But before we get
that far, let's just

7
00:00:18,240 --> 00:00:20,640
have a reminder
that we have already

8
00:00:20,640 --> 00:00:23,580
enabled multicast
routing on our devices,

9
00:00:23,580 --> 00:00:26,640
and we have already
enabled PIM sparse mode

10
00:00:26,640 --> 00:00:28,630
on all of our interfaces.

11
00:00:28,630 --> 00:00:30,930
So, that does have
to be done first.

12
00:00:30,930 --> 00:00:33,300
That, of course,
is a prerequisite,

13
00:00:33,300 --> 00:00:38,250
but all we have to do now is
specify either the default

14
00:00:38,250 --> 00:00:42,810
group or another group that
we want to use for SSM,

15
00:00:42,810 --> 00:00:45,600
enable the feature
on the devices

16
00:00:45,600 --> 00:00:49,060
and then just start up our
source and our receiver.

17
00:00:49,060 --> 00:00:51,210
So, let's go ahead and jump in.

18
00:00:51,210 --> 00:00:53,400
Look at the topology
just so we have an idea

19
00:00:53,400 --> 00:00:54,880
of what's going to happen.

20
00:00:54,880 --> 00:00:57,210
And then, of course, we'll
jump into the command line

21
00:00:57,210 --> 00:00:58,545
and make all of this happen.

22
00:00:58,545 --> 00:01:01,190

23
00:01:01,190 --> 00:01:05,740
So we are still on Multicast
Topology 2, and let's talk

24
00:01:05,740 --> 00:01:07,420
about what's going to change.

25
00:01:07,420 --> 00:01:12,070
The first part is router
2 is no longer going

26
00:01:12,070 --> 00:01:15,550
to be a rendezvous
point, and router 5

27
00:01:15,550 --> 00:01:18,670
is no longer going to be a BSR.

28
00:01:18,670 --> 00:01:22,000
Now, this part I've
already configured just

29
00:01:22,000 --> 00:01:23,480
in the interest of time.

30
00:01:23,480 --> 00:01:26,470
So, the rendezvous
point and the BSR

31
00:01:26,470 --> 00:01:29,930
have already been completely
removed from the environment.

32
00:01:29,930 --> 00:01:32,350
The next thing we're
going to do is simply

33
00:01:32,350 --> 00:01:37,690
look at what happens when
router 8 joins our group using

34
00:01:37,690 --> 00:01:39,460
a specific source.

35
00:01:39,460 --> 00:01:42,490
Now remember that
router 10 up here is

36
00:01:42,490 --> 00:01:46,510
our source going to 224.1.1.1.

37
00:01:46,510 --> 00:01:49,360
So when router 8
specifies the source,

38
00:01:49,360 --> 00:01:54,140
it's going to be router
10's address on this subnet.

39
00:01:54,140 --> 00:01:57,760
So it's going to
be the 50.2.61.10

40
00:01:57,760 --> 00:02:00,800
because that's where
router 10 is actually

41
00:02:00,800 --> 00:02:02,520
sourcing its traffic from.

42
00:02:02,520 --> 00:02:05,330
So that's what we'll be
specifying as the source

43
00:02:05,330 --> 00:02:06,360
address.

44
00:02:06,360 --> 00:02:11,240
And since we're still
using our group, 224.1.1.1.

45
00:02:11,240 --> 00:02:18,230
This means that we are not using
the default group 232.0.0.0/8.

46
00:02:18,230 --> 00:02:22,070
So we'll have to use an
access list to specify

47
00:02:22,070 --> 00:02:24,300
the group that we're using.

48
00:02:24,300 --> 00:02:27,020
So that's going to make it a
little bit more complicated,

49
00:02:27,020 --> 00:02:29,460
but you'll see not very much.

50
00:02:29,460 --> 00:02:31,730
Let's go ahead and jump
into the command line,

51
00:02:31,730 --> 00:02:35,210
and get all this up and running.

52
00:02:35,210 --> 00:02:35,710
OK.

53
00:02:35,710 --> 00:02:38,650
So the first thing we
want to do is verify

54
00:02:38,650 --> 00:02:41,600
that we have no RP
in the environment.

55
00:02:41,600 --> 00:02:43,570
So we'll just use
our chat window here.

56
00:02:43,570 --> 00:02:47,380
We'll do a show ip pim rp map.

57
00:02:47,380 --> 00:02:51,590
And all of the devices should
be showing this as empty.

58
00:02:51,590 --> 00:02:55,120
So we can see here that
router 1 has no RP.

59
00:02:55,120 --> 00:02:57,070
Router 2 doesn't.

60
00:02:57,070 --> 00:03:04,210
Nothing on router 3, router
4, router 5, router 6,

61
00:03:04,210 --> 00:03:06,190
and router 7.

62
00:03:06,190 --> 00:03:08,020
None of these have an RP.

63
00:03:08,020 --> 00:03:10,700
There's no in the environment.

64
00:03:10,700 --> 00:03:13,420
The next thing we want to
do is go ahead and start up

65
00:03:13,420 --> 00:03:14,390
our source.

66
00:03:14,390 --> 00:03:17,930
So let's jump over to router
10 and get our source running.

67
00:03:17,930 --> 00:03:20,600
So we'll go ahead and
start up our ping.

68
00:03:20,600 --> 00:03:22,990
So now, we have
our source running.

69
00:03:22,990 --> 00:03:26,260
And then let's look at what
happens on the first hop

70
00:03:26,260 --> 00:03:26,920
router.

71
00:03:26,920 --> 00:03:28,990
Remember the job of
the first hop router

72
00:03:28,990 --> 00:03:33,290
is to register a source
with the rendezvous point,

73
00:03:33,290 --> 00:03:35,040
but there's no rendezvous point.

74
00:03:35,040 --> 00:03:37,190
So let's jump over to router 6.

75
00:03:37,190 --> 00:03:39,740
And let's do a show ip mroute.

76
00:03:39,740 --> 00:03:44,030
Notice that it has nothing
accept the default entry

77
00:03:44,030 --> 00:03:47,720
for auto RP, which is
always going to be there.

78
00:03:47,720 --> 00:03:52,760
With no RP, PIM Sparse mode
has no idea what to do.

79
00:03:52,760 --> 00:03:56,120
This isn't going to make it
past the first hop router

80
00:03:56,120 --> 00:03:58,470
even though the source
is up and running.

81
00:03:58,470 --> 00:04:02,270
But that's OK because we're
here to configure SSM.

82
00:04:02,270 --> 00:04:06,710
Now, we are configuring SSM
without using the default group

83
00:04:06,710 --> 00:04:09,770
range, so we have to
take one extra step

84
00:04:09,770 --> 00:04:11,930
that we wouldn't
normally have to do if we

85
00:04:11,930 --> 00:04:13,730
were using the default range.

86
00:04:13,730 --> 00:04:16,670
We're going to have to
create an access list so

87
00:04:16,670 --> 00:04:21,260
that all of the devices know
which groups are using SSM,

88
00:04:21,260 --> 00:04:23,960
and therefore, not to
try to use a rendezvous

89
00:04:23,960 --> 00:04:25,910
point for those groups.

90
00:04:25,910 --> 00:04:29,360
That's why we have to tell the
routers which ones are SSM.

91
00:04:29,360 --> 00:04:31,880
So let's start over
on router 1 since we

92
00:04:31,880 --> 00:04:34,320
have to configure this access
list on all of the routers

93
00:04:34,320 --> 00:04:35,550
anyway.

94
00:04:35,550 --> 00:04:38,340
We'll simply go into
configuration mode.

95
00:04:38,340 --> 00:04:40,560
We'll make an IP access list.

96
00:04:40,560 --> 00:04:42,870
All we need is a
standard access list.

97
00:04:42,870 --> 00:04:47,490
Let's call it ACL_SSM_GROUPS.

98
00:04:47,490 --> 00:04:50,490
And all we have to do here
is permit whatever groups

99
00:04:50,490 --> 00:04:53,310
that we want to be part of SSM.

100
00:04:53,310 --> 00:04:59,160
So we'll just do for
example 224.1.1.0/24.

101
00:04:59,160 --> 00:05:02,230
So we'll just use a
wildcard mask like this.

102
00:05:02,230 --> 00:05:08,670
And now, all of the
groups, 224.1.1.0/24,

103
00:05:08,670 --> 00:05:11,490
will be SSM members.

104
00:05:11,490 --> 00:05:15,000
Now what we have to
do is enable SSM.

105
00:05:15,000 --> 00:05:18,060
So we say, ip pim ssm.

106
00:05:18,060 --> 00:05:20,610
And then we have two choices.

107
00:05:20,610 --> 00:05:25,020
As you can see, if we
were using the 232/8,

108
00:05:25,020 --> 00:05:28,510
we would literally
just type default here.

109
00:05:28,510 --> 00:05:31,530
And then you can see all at
once is for us to hit Enter.

110
00:05:31,530 --> 00:05:33,670
See, we wouldn't
need the access list.

111
00:05:33,670 --> 00:05:36,810
We would just type, ip
pim ssm default. Enter.

112
00:05:36,810 --> 00:05:38,920
Done that's it.

113
00:05:38,920 --> 00:05:42,150
But since we're not
using the default range,

114
00:05:42,150 --> 00:05:47,230
we have to say range and then
we have to specify our ACL.

115
00:05:47,230 --> 00:05:51,360
So ACL_SSM_GROUPS.

116
00:05:51,360 --> 00:05:55,980
All we have to do is put
our ACL and that command

117
00:05:55,980 --> 00:05:58,260
on all of our routers.

118
00:05:58,260 --> 00:06:01,260
Since it's going to be
standard on all of the devices,

119
00:06:01,260 --> 00:06:03,730
we'll just copy and paste it in.

120
00:06:03,730 --> 00:06:11,190
So we'll put it on router 2,
router 3, router 4, router 5,

121
00:06:11,190 --> 00:06:14,400
router 6, and router 7.

122
00:06:14,400 --> 00:06:15,730
That's it.

123
00:06:15,730 --> 00:06:18,390
That's all we have to
do to configure SSM

124
00:06:18,390 --> 00:06:20,740
except on the client side.

125
00:06:20,740 --> 00:06:23,580
On the client side here
on the last hop router,

126
00:06:23,580 --> 00:06:26,370
there is one more thing
we're going to have to do.

127
00:06:26,370 --> 00:06:30,660
If we say, do sh
ip igmp interface,

128
00:06:30,660 --> 00:06:32,550
we'll specify gigabit 3.

129
00:06:32,550 --> 00:06:34,710
That's what's facing router 8.

130
00:06:34,710 --> 00:06:40,740
Notice that the current IGMP
host version is version 2.

131
00:06:40,740 --> 00:06:43,890
And as we've said,
we want version 3

132
00:06:43,890 --> 00:06:45,900
to be able to support SSL.

133
00:06:45,900 --> 00:06:48,660
So we have to go into
Interface Gigabit 3.

134
00:06:48,660 --> 00:06:51,990
And again, this would be all
interfaces facing clients.

135
00:06:51,990 --> 00:06:57,420
And we simply have to
say, ip igmp version 3.

136
00:06:57,420 --> 00:06:59,580
If we look at our
interface again,

137
00:06:59,580 --> 00:07:05,370
notice that now the current IGMP
host version is now version 3.

138
00:07:05,370 --> 00:07:07,810
We can exit configuration here.

139
00:07:07,810 --> 00:07:10,750
But remember that our client
will need that as well.

140
00:07:10,750 --> 00:07:12,930
So over to router 8.

141
00:07:12,930 --> 00:07:15,270
So we'll simply go
into configuration mode

142
00:07:15,270 --> 00:07:21,880
into Interface Gigabit 1
and say, ip igmp version 3.

143
00:07:21,880 --> 00:07:24,260
So now we've created our ACL.

144
00:07:24,260 --> 00:07:28,240
We've enabled PIM Sparse
mode for that group range.

145
00:07:28,240 --> 00:07:32,770
And now, we've configured IGMP
version 3 between the client

146
00:07:32,770 --> 00:07:35,300
and the last hop router.

147
00:07:35,300 --> 00:07:37,760
That means we're
ready to fire up SSM.

148
00:07:37,760 --> 00:07:42,050
So all we have to do is join
the group on the receiver

149
00:07:42,050 --> 00:07:44,060
with the correct source.

150
00:07:44,060 --> 00:07:47,750
Let's go ahead and do
that and see if it works.

151
00:07:47,750 --> 00:07:53,290
So we simply say,
ip igmp join-group.

152
00:07:53,290 --> 00:07:56,920
Of course, we're still
joining the 224.1.1.1.

153
00:07:56,920 --> 00:08:00,070
However, here's, of
course, the big change.

154
00:08:00,070 --> 00:08:02,750
We're going to
specify the source.

155
00:08:02,750 --> 00:08:04,640
The source is router 10.

156
00:08:04,640 --> 00:08:10,150
So that's 50.2.61.10.

157
00:08:10,150 --> 00:08:13,240
We'll go ahead and hit
Enter, and let's see

158
00:08:13,240 --> 00:08:14,960
if this is working.

159
00:08:14,960 --> 00:08:18,820
If it worked, we should have
mroutes on our devices now.

160
00:08:18,820 --> 00:08:21,580
So let's go see what's
going on router 7.

161
00:08:21,580 --> 00:08:25,360
We'll do our, sh ip
mroute, and look at that.

162
00:08:25,360 --> 00:08:28,390
Right there is an
S comma G entry.

163
00:08:28,390 --> 00:08:31,930
The flags on it are S, T and I.

164
00:08:31,930 --> 00:08:35,620
The S indicates that
it's an SSM group.

165
00:08:35,620 --> 00:08:39,340
The T, of course, means that
it's the SPT or the Shortest

166
00:08:39,340 --> 00:08:40,720
Path Tree.

167
00:08:40,720 --> 00:08:44,740
And the I means that we
received this source information

168
00:08:44,740 --> 00:08:47,660
from a source
specific host report.

169
00:08:47,660 --> 00:08:50,360
Meaning, IGMP version 3.

170
00:08:50,360 --> 00:08:52,970
If we do this again
with our count,

171
00:08:52,970 --> 00:08:56,790
we can see that it's currently
forwarded 14 packets.

172
00:08:56,790 --> 00:09:02,160
And if we hit up again, we can
see that now it's forwarded 19.

173
00:09:02,160 --> 00:09:04,350
So it's definitely
forwarding traffic.

174
00:09:04,350 --> 00:09:07,610
And our source specific
multicast is working correctly.

175
00:09:07,610 --> 00:09:10,340
Just to look on a few
more routers, if we

176
00:09:10,340 --> 00:09:14,150
were to say hop over and
look at router 1, notice,

177
00:09:14,150 --> 00:09:17,750
it is also aware that
this is an SSM group

178
00:09:17,750 --> 00:09:20,040
with that lowercase s flag.

179
00:09:20,040 --> 00:09:22,910
And of course, it's
the Shortest Path Tree.

180
00:09:22,910 --> 00:09:25,820
So no star comma G entries.

181
00:09:25,820 --> 00:09:27,980
Only S comma G entries.

182
00:09:27,980 --> 00:09:30,710
And just like that,
we have SSM up

183
00:09:30,710 --> 00:09:33,340
and working in our environment.

184
00:09:33,340 --> 00:09:36,480
So in this video,
we saw just how easy

185
00:09:36,480 --> 00:09:42,450
it is to configure SSM even when
we're using a non-default group

186
00:09:42,450 --> 00:09:43,260
range.

187
00:09:43,260 --> 00:09:48,180
All we had to do was create
an ACL to identify the groups

188
00:09:48,180 --> 00:09:51,000
that we want to be source
specific multicast,

189
00:09:51,000 --> 00:09:53,610
enable the feature
on all the routers,

190
00:09:53,610 --> 00:09:57,280
enable IGMP version
3 at the edge,

191
00:09:57,280 --> 00:10:00,510
and then start up our
source and receiver.

192
00:10:00,510 --> 00:10:01,620
That's it.

193
00:10:01,620 --> 00:10:05,340
Just like that, SSM
comes up and works,

194
00:10:05,340 --> 00:10:08,670
but there is one more scenario
that we need to look at.

195
00:10:08,670 --> 00:10:12,510
What if the client, in
this case, router 8,

196
00:10:12,510 --> 00:10:16,590
doesn't actually
support IGMP version 3?

197
00:10:16,590 --> 00:10:19,320
Well, there's a way
we can fix that too,

198
00:10:19,320 --> 00:10:22,110
and that's exactly what
we're going to look at next.

199
00:10:22,110 --> 00:10:25,530
Till then, I hope this has
been informative for you,

200
00:10:25,530 --> 00:10:28,730
and I'd like to thank
you for viewing.

201
00:10:28,730 --> 00:10:32,000