1
00:00:00,000 --> 00:00:03,920
[AUDIO LOGO]

2
00:00:03,920 --> 00:00:07,850

3
00:00:07,850 --> 00:00:12,020
Our first option to look
at for discovering the RP

4
00:00:12,020 --> 00:00:14,480
is simply to
statically configure

5
00:00:14,480 --> 00:00:17,910
the RP on each router
in the environment,

6
00:00:17,910 --> 00:00:20,160
including the RP itself.

7
00:00:20,160 --> 00:00:23,420
Now, static
configuration is often

8
00:00:23,420 --> 00:00:25,520
looked down upon as
something we don't really

9
00:00:25,520 --> 00:00:26,820
want to have to do.

10
00:00:26,820 --> 00:00:30,110
And it certainly does have
advantages and disadvantages

11
00:00:30,110 --> 00:00:31,890
like most other things.

12
00:00:31,890 --> 00:00:36,260
However, this can actually
be a fairly viable solution

13
00:00:36,260 --> 00:00:39,140
in a lot of environments,
particularly

14
00:00:39,140 --> 00:00:41,480
if we combine this
with something

15
00:00:41,480 --> 00:00:44,390
called Anycast RP
that we'll be looking

16
00:00:44,390 --> 00:00:46,620
at in just a few videos.

17
00:00:46,620 --> 00:00:50,720
So although static
RP by itself probably

18
00:00:50,720 --> 00:00:53,660
isn't a great choice in
a lot of environments,

19
00:00:53,660 --> 00:00:57,630
it can be when combined
with other features.

20
00:00:57,630 --> 00:01:00,140
So let's go ahead and
jump in and take a look

21
00:01:00,140 --> 00:01:02,510
at some of those advantages
and disadvantages.

22
00:01:02,510 --> 00:01:04,940
And then we'll look
at how to configure it

23
00:01:04,940 --> 00:01:05,990
on the command line.

24
00:01:05,990 --> 00:01:08,950

25
00:01:08,950 --> 00:01:11,640
So looking at static
RP configuration,

26
00:01:11,640 --> 00:01:15,460
let's go over some of its
advantages and disadvantages.

27
00:01:15,460 --> 00:01:19,020
So one of its advantages
is this is actually

28
00:01:19,020 --> 00:01:21,660
going to be very, very
simple configuration.

29
00:01:21,660 --> 00:01:25,410
We simply have to enter
one command on each device,

30
00:01:25,410 --> 00:01:29,290
telling it where the
RP is, and that's it.

31
00:01:29,290 --> 00:01:32,190
That's all there is to
configuring static RP.

32
00:01:32,190 --> 00:01:35,050
It really doesn't get
any easier than that.

33
00:01:35,050 --> 00:01:39,390
Now, a downside is
we can actually only

34
00:01:39,390 --> 00:01:43,540
have one RP
configured at a time.

35
00:01:43,540 --> 00:01:46,680
Now, as I said during
the introduction,

36
00:01:46,680 --> 00:01:50,610
there are other ways
to provide redundancy.

37
00:01:50,610 --> 00:01:54,810
But static RP itself
does not have a method

38
00:01:54,810 --> 00:01:56,970
built in for redundancy.

39
00:01:56,970 --> 00:01:59,190
We can configure one RP.

40
00:01:59,190 --> 00:02:00,370
That's it.

41
00:02:00,370 --> 00:02:01,990
That's the one it uses.

42
00:02:01,990 --> 00:02:06,570
And if that RP is not available,
well, then sparse mode

43
00:02:06,570 --> 00:02:08,979
is not going to function.

44
00:02:08,979 --> 00:02:12,760
Another downside
here is this can

45
00:02:12,760 --> 00:02:17,260
be rather tedious to
configure on all the routers.

46
00:02:17,260 --> 00:02:20,470
Clearly, that depends on how
large your environment is.

47
00:02:20,470 --> 00:02:23,710
But the good news
here is in most

48
00:02:23,710 --> 00:02:28,090
larger environments where this
would become a problem, well,

49
00:02:28,090 --> 00:02:30,820
usually, we're going to
have some sort of management

50
00:02:30,820 --> 00:02:34,750
software that actually
can ease the deployment

51
00:02:34,750 --> 00:02:37,090
of these commands
by sending it out

52
00:02:37,090 --> 00:02:40,010
to multiple devices
at the same time.

53
00:02:40,010 --> 00:02:42,220
So a small environment,
this isn't really

54
00:02:42,220 --> 00:02:44,140
going to be that tedious anyway.

55
00:02:44,140 --> 00:02:45,970
A large environment,
you're going

56
00:02:45,970 --> 00:02:48,790
to have some sort of
network management software.

57
00:02:48,790 --> 00:02:50,890
It's really the
networks in the middle

58
00:02:50,890 --> 00:02:53,470
where this can be a
little bit tedious.

59
00:02:53,470 --> 00:02:59,470
And along with that, if the
RP address ever changes,

60
00:02:59,470 --> 00:03:03,220
all those routers are going
to have to be reconfigured,

61
00:03:03,220 --> 00:03:06,730
which could take us right
back up to this problem

62
00:03:06,730 --> 00:03:08,560
where it might be tedious.

63
00:03:08,560 --> 00:03:12,430
But, hopefully, we have some
of that management software

64
00:03:12,430 --> 00:03:14,680
to help take care
of this for us.

65
00:03:14,680 --> 00:03:17,320
And one last point,
as we mentioned

66
00:03:17,320 --> 00:03:21,190
during the introduction,
we can combine this

67
00:03:21,190 --> 00:03:23,890
with something called
Anycast RP, which

68
00:03:23,890 --> 00:03:25,850
we'll be looking at shortly.

69
00:03:25,850 --> 00:03:30,730
But this can be used to
add redundancy, mobility,

70
00:03:30,730 --> 00:03:32,830
geographic load sharing.

71
00:03:32,830 --> 00:03:35,410
We'll talk about
all those in detail

72
00:03:35,410 --> 00:03:37,930
when we get to Anycast RP.

73
00:03:37,930 --> 00:03:40,930
But the idea behind
Anycast is we

74
00:03:40,930 --> 00:03:44,800
have just one
address that provides

75
00:03:44,800 --> 00:03:47,530
all of these services
we just talked about.

76
00:03:47,530 --> 00:03:52,270
Then our static RP
configuration can simply

77
00:03:52,270 --> 00:03:54,820
point to that one address.

78
00:03:54,820 --> 00:03:57,340
That address can
have redundancy.

79
00:03:57,340 --> 00:04:01,100
It can be moved, and it can
do geographic load sharing.

80
00:04:01,100 --> 00:04:02,620
So that's the idea here.

81
00:04:02,620 --> 00:04:04,960
We use this one Anycast address.

82
00:04:04,960 --> 00:04:07,540
And then our static
RP configuration

83
00:04:07,540 --> 00:04:10,420
points to that one
Anycast address.

84
00:04:10,420 --> 00:04:12,830
And it works together
quite nicely.

85
00:04:12,830 --> 00:04:15,880
So with all of these advantages
and disadvantages out

86
00:04:15,880 --> 00:04:19,240
of the way, let's actually
just jump into the command line

87
00:04:19,240 --> 00:04:23,170
and see how we would
configure static RP.

88
00:04:23,170 --> 00:04:24,910
So for this
demonstration, we're just

89
00:04:24,910 --> 00:04:27,580
going to use a single
router here, router 1.

90
00:04:27,580 --> 00:04:31,870
And let's start with
a show IP pim rp map.

91
00:04:31,870 --> 00:04:36,040
As we can see, we currently
have no rendezvous points

92
00:04:36,040 --> 00:04:40,220
mapped to any multicast
groups, which by the way,

93
00:04:40,220 --> 00:04:42,700
is because router 1 is
currently unconfigured.

94
00:04:42,700 --> 00:04:45,190
This, of course, is what
we're here to configure.

95
00:04:45,190 --> 00:04:48,220
Let's also do a show IP pim rp.

96
00:04:48,220 --> 00:04:50,290
And what we see here
is there are currently

97
00:04:50,290 --> 00:04:51,950
no RPs configured.

98
00:04:51,950 --> 00:04:54,070
So this is what we
would be expecting

99
00:04:54,070 --> 00:04:56,660
from a nonconfigured device.

100
00:04:56,660 --> 00:04:59,240
So let's go into
configuration mode.

101
00:04:59,240 --> 00:05:01,990
First thing we want to
do is enable multicast

102
00:05:01,990 --> 00:05:03,890
routing on this device.

103
00:05:03,890 --> 00:05:06,460
This device is running IOS XE.

104
00:05:06,460 --> 00:05:12,470
So the way we do that is we
say ip multicast-routing.

105
00:05:12,470 --> 00:05:16,030
And then we can either enable
it for a particular VRF,

106
00:05:16,030 --> 00:05:18,520
or we can just say
distributed, and it

107
00:05:18,520 --> 00:05:21,910
will enable the multicast
routing for the whole platform.

108
00:05:21,910 --> 00:05:24,210
Next, we'll configure
an interface.

109
00:05:24,210 --> 00:05:26,630
So let's just do
interface gigabit 1.

110
00:05:26,630 --> 00:05:28,430
It's going to need
an IP address.

111
00:05:28,430 --> 00:05:32,570
We'll just give it
something like 192.168.12.1.

112
00:05:32,570 --> 00:05:34,550
We'll make it a /24.

113
00:05:34,550 --> 00:05:37,530
And let's enable sparse mode.

114
00:05:37,530 --> 00:05:40,010
So we'll say IP pim sparse.

115
00:05:40,010 --> 00:05:42,230
Let's bring that interface up.

116
00:05:42,230 --> 00:05:44,750
Then let's create a
loopback that we'll

117
00:05:44,750 --> 00:05:47,040
use for our rendezvous point.

118
00:05:47,040 --> 00:05:50,270
So we'll say
interface loopback 0.

119
00:05:50,270 --> 00:05:54,050
We'll say IP address 10.1.1.1.

120
00:05:54,050 --> 00:05:56,810
And we'll make that a /32.

121
00:05:56,810 --> 00:05:59,000
We'll enable PIM sparse mode.

122
00:05:59,000 --> 00:06:02,040
And let's exit
interface configuration.

123
00:06:02,040 --> 00:06:05,960
So now let's do our show
ip pim rp map again.

124
00:06:05,960 --> 00:06:07,880
As you can see, we,
of course, still

125
00:06:07,880 --> 00:06:10,640
don't have an rp map,
because all we've done

126
00:06:10,640 --> 00:06:14,630
is enable multicast
configure, a few interfaces,

127
00:06:14,630 --> 00:06:16,640
and enable PIM sparse mode.

128
00:06:16,640 --> 00:06:19,470
But we still need
a rendezvous point.

129
00:06:19,470 --> 00:06:24,680
The command for this is simply
to say ip pim rp address

130
00:06:24,680 --> 00:06:27,690
and then put in the
address of the device.

131
00:06:27,690 --> 00:06:29,810
So we can say 10.1.1.1.

132
00:06:29,810 --> 00:06:33,570
That's the address that we want
to be the rendezvous point.

133
00:06:33,570 --> 00:06:36,210
We can see a couple
options after this,

134
00:06:36,210 --> 00:06:38,660
where we can actually
use an access

135
00:06:38,660 --> 00:06:43,320
list to control which groups
this will be the rendezvous

136
00:06:43,320 --> 00:06:44,340
point for.

137
00:06:44,340 --> 00:06:46,410
It doesn't have to
be the rendezvous

138
00:06:46,410 --> 00:06:49,660
point for all of the groups.

139
00:06:49,660 --> 00:06:53,430
So although this doesn't
give us any form of what

140
00:06:53,430 --> 00:06:56,850
we would normally call
traditional load sharing where

141
00:06:56,850 --> 00:06:59,860
the device does its
own load sharing,

142
00:06:59,860 --> 00:07:03,000
we could do some manual
load sharing here

143
00:07:03,000 --> 00:07:06,270
by taking some of
our multicast groups,

144
00:07:06,270 --> 00:07:09,120
sending them to
one static address,

145
00:07:09,120 --> 00:07:12,240
and then take different
groups and send them

146
00:07:12,240 --> 00:07:14,470
to a different IP address.

147
00:07:14,470 --> 00:07:17,010
So, again, it won't
do load sharing

148
00:07:17,010 --> 00:07:18,450
in the traditional sense.

149
00:07:18,450 --> 00:07:20,940
But it can do it
manually if we choose

150
00:07:20,940 --> 00:07:24,810
to configure it using these
access lists to control

151
00:07:24,810 --> 00:07:26,940
which groups are
going to be controlled

152
00:07:26,940 --> 00:07:29,430
by this particular RP.

153
00:07:29,430 --> 00:07:33,930
Now, the other option to
look at here is override.

154
00:07:33,930 --> 00:07:39,090
Override can be used if we want
to use the static entry over

155
00:07:39,090 --> 00:07:41,550
automatically learned
entries that we

156
00:07:41,550 --> 00:07:44,900
learn from, say, AutoRP or BSR.

157
00:07:44,900 --> 00:07:47,630
This is actually
an odd situation

158
00:07:47,630 --> 00:07:51,500
where the dynamically
learned RPs will actually

159
00:07:51,500 --> 00:07:56,240
beat the static RP
unless you say override.

160
00:07:56,240 --> 00:07:59,220
Now, we don't need to do
that in this configuration.

161
00:07:59,220 --> 00:08:00,590
So we'll just hit Enter.

162
00:08:00,590 --> 00:08:04,490
But those are the options we
would have on the static RP

163
00:08:04,490 --> 00:08:05,930
configuration.

164
00:08:05,930 --> 00:08:08,690
We also see here these
tunnels coming up.

165
00:08:08,690 --> 00:08:11,300
These are those PIM
register tunnels

166
00:08:11,300 --> 00:08:12,770
that we were talking about.

167
00:08:12,770 --> 00:08:16,490
It's getting these tunnels
ready for other routers

168
00:08:16,490 --> 00:08:21,410
to be able to register their
multicast sources with the RP

169
00:08:21,410 --> 00:08:23,270
address.

170
00:08:23,270 --> 00:08:26,840
So if we do our show
IP pim rp map again,

171
00:08:26,840 --> 00:08:31,000
what we see is that for the
entire multicast group range,

172
00:08:31,000 --> 00:08:33,850
because we didn't
specify a group range,

173
00:08:33,850 --> 00:08:39,159
we have a static entry
that the RP is 10.1.1.1.

174
00:08:39,159 --> 00:08:42,159
Now, you might have noticed
there was a slight pause

175
00:08:42,159 --> 00:08:44,080
while this command was running.

176
00:08:44,080 --> 00:08:48,620
And notice in these parentheses
we have a question mark.

177
00:08:48,620 --> 00:08:51,100
The reason for
this is the router

178
00:08:51,100 --> 00:08:56,500
is trying to do a reverse
DNS lookup on the 10.1.1.1

179
00:08:56,500 --> 00:08:59,590
to come back with a
friendly hostname.

180
00:08:59,590 --> 00:09:02,170
Well, we could give it
a friendly host name

181
00:09:02,170 --> 00:09:04,120
and see what that looks like.

182
00:09:04,120 --> 00:09:10,030
We'll just say ip
host R1 is 10.1.1.1.

183
00:09:10,030 --> 00:09:13,030
So if we give it this
information-- now, of course,

184
00:09:13,030 --> 00:09:15,460
normally, in an environment,
we would probably

185
00:09:15,460 --> 00:09:17,980
want to point this
to a DNS server.

186
00:09:17,980 --> 00:09:21,880
But just to show you how it
works, if we do our show ip pim

187
00:09:21,880 --> 00:09:27,020
rp map again, notice, first,
no pause because, well, it's

188
00:09:27,020 --> 00:09:27,990
local information.

189
00:09:27,990 --> 00:09:30,080
It looked it up
pretty much instantly.

190
00:09:30,080 --> 00:09:34,520
But notice it's now putting the
host name in the parentheses.

191
00:09:34,520 --> 00:09:37,910
We'll see this a lot as
we go through multicast.

192
00:09:37,910 --> 00:09:42,080
A lot of these outputs will
try to put the hostname along

193
00:09:42,080 --> 00:09:44,310
with IP entries.

194
00:09:44,310 --> 00:09:49,600
So that's really all there
is to configuring static IP.

195
00:09:49,600 --> 00:09:53,350
In this video, we took
a look at configuring

196
00:09:53,350 --> 00:09:56,240
static RP on the Cisco routers.

197
00:09:56,240 --> 00:09:59,950
Now, we also talked about some
advantages and disadvantages.

198
00:09:59,950 --> 00:10:02,800
Again, this is fairly
simple to configure.

199
00:10:02,800 --> 00:10:06,310
I mean, we, again, put in
one command on this router

200
00:10:06,310 --> 00:10:08,320
aside from configuring
some interfaces that

201
00:10:08,320 --> 00:10:09,520
needed to be configured.

202
00:10:09,520 --> 00:10:13,270
But there's not really anything
to configuring this unless you

203
00:10:13,270 --> 00:10:15,050
get into a large environment.

204
00:10:15,050 --> 00:10:17,650
And then, of course, it
could be a little bit tedious

205
00:10:17,650 --> 00:10:20,560
to have to put this
on all the routers.

206
00:10:20,560 --> 00:10:24,040
Hopefully, we have some
form of network management

207
00:10:24,040 --> 00:10:27,790
to be able to handle that and
help us with that project.

208
00:10:27,790 --> 00:10:31,810
But other than that, static
RP is a very simple option.

209
00:10:31,810 --> 00:10:36,190
And combined with things
like Anycast RP that we'll

210
00:10:36,190 --> 00:10:38,350
be looking at later,
this can actually

211
00:10:38,350 --> 00:10:42,170
be a really good solution
in the right environment.

212
00:10:42,170 --> 00:10:47,140
Now, other choices are
dynamically learning the RP.

213
00:10:47,140 --> 00:10:50,570
And the first choice for
dynamically learning the RP

214
00:10:50,570 --> 00:10:53,450
is Cisco's AutoRP.

215
00:10:53,450 --> 00:10:56,940
And that's exactly what we're
going to take a look at next.

216
00:10:56,940 --> 00:11:00,380
Until then, I hope this has
been informative for you.

217
00:11:00,380 --> 00:11:03,580
And I'd like to thank
you for viewing.

218
00:11:03,580 --> 00:11:07,000