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

2
00:00:03,465 --> 00:00:08,130

3
00:00:08,130 --> 00:00:10,210
So now that we've
taken a close look

4
00:00:10,210 --> 00:00:14,020
at Cisco's proprietary
Auto-RP solution

5
00:00:14,020 --> 00:00:16,810
for dynamically finding
the rendezvous point.

6
00:00:16,810 --> 00:00:19,450
It's time to look at
the industry standard

7
00:00:19,450 --> 00:00:23,900
equivalent, which is
BSR, or Bootstrap Router.

8
00:00:23,900 --> 00:00:27,760
Now, since BSR is an
industry standard,

9
00:00:27,760 --> 00:00:31,690
they had the ability to
actually update PIM in order

10
00:00:31,690 --> 00:00:33,470
to support this solution.

11
00:00:33,470 --> 00:00:38,710
Therefore, BSR actually
requires PIM version 2.

12
00:00:38,710 --> 00:00:42,940
Auto-RP was, of course,
available in PIM version 1,

13
00:00:42,940 --> 00:00:47,930
but PIM version 2 was updated
to carry BSR's information.

14
00:00:47,930 --> 00:00:51,730
Now, like auto-RP,
it's another way

15
00:00:51,730 --> 00:00:54,070
to automatically find
the rendezvous point,

16
00:00:54,070 --> 00:00:57,980
but the messaging is
built into PIM itself.

17
00:00:57,980 --> 00:01:00,820
Now, it does still
have two moving parts--

18
00:01:00,820 --> 00:01:04,430
we still have the candidate
RPs, which are, of course,

19
00:01:04,430 --> 00:01:06,310
the routers that
are willing to be

20
00:01:06,310 --> 00:01:10,100
the RPs for either all
of the multicast groups,

21
00:01:10,100 --> 00:01:12,680
or a subset of those groups.

22
00:01:12,680 --> 00:01:16,460
Then we have the equivalent
of the mapping agent,

23
00:01:16,460 --> 00:01:19,640
but in this case, it's the BSR.

24
00:01:19,640 --> 00:01:23,570
The protocol itself is
named after the router

25
00:01:23,570 --> 00:01:26,810
that's sort of acting
like the mapping agent.

26
00:01:26,810 --> 00:01:29,750
Now, the reason I say sort
of acting like the mapping

27
00:01:29,750 --> 00:01:32,570
agent is here is where
the functionality really

28
00:01:32,570 --> 00:01:33,800
gets different.

29
00:01:33,800 --> 00:01:39,230
In BSR, well, the
BSR doesn't actually

30
00:01:39,230 --> 00:01:42,200
choose the winning
rendezvous point.

31
00:01:42,200 --> 00:01:47,540
Now, we'll see this more when
we get to redundant RPs in BSR,

32
00:01:47,540 --> 00:01:49,880
but for now, let's
just go ahead and get

33
00:01:49,880 --> 00:01:52,110
BSR set up and configured.

34
00:01:52,110 --> 00:01:54,410
We're going to be
configuring this the same way

35
00:01:54,410 --> 00:01:55,940
we did auto-RP.

36
00:01:55,940 --> 00:01:59,210
So let's just jump into
our topology real quick,

37
00:01:59,210 --> 00:02:01,350
take a look at what we're
going to be setting up,

38
00:02:01,350 --> 00:02:03,140
and then jump into
the command line,

39
00:02:03,140 --> 00:02:07,370
and get BSR working exactly the
same way that we did auto-RP.

40
00:02:07,370 --> 00:02:10,139

41
00:02:10,139 --> 00:02:13,920
So we are still on
multicast topology 1,

42
00:02:13,920 --> 00:02:16,620
but here's what's
going to change.

43
00:02:16,620 --> 00:02:20,430
Router 2 is still going
to be a candidate RP,

44
00:02:20,430 --> 00:02:23,400
but this time for BSR.

45
00:02:23,400 --> 00:02:27,750
And that means that router 5
is no longer a mapping agent,

46
00:02:27,750 --> 00:02:31,620
it is now the BSR, or
the Bootstrap Router.

47
00:02:31,620 --> 00:02:35,400
So at the end of this, this
should be functioning exactly

48
00:02:35,400 --> 00:02:38,330
the same as auto-RP did.

49
00:02:38,330 --> 00:02:41,600
Now, in the interest of
time, just so you're aware,

50
00:02:41,600 --> 00:02:45,650
I have already removed
auto-RP from the environment.

51
00:02:45,650 --> 00:02:48,500
We'll start by
verifying that, but none

52
00:02:48,500 --> 00:02:52,530
of the routers at this point
have any RP configured at all.

53
00:02:52,530 --> 00:02:56,430
Therefore, our data plane is
also currently not working.

54
00:02:56,430 --> 00:02:58,770
So as we go through
this demonstration,

55
00:02:58,770 --> 00:03:02,600
we are going to have to start up
router 10 as the source again,

56
00:03:02,600 --> 00:03:04,610
and have that start
sending traffic

57
00:03:04,610 --> 00:03:08,300
and rebuild the data plane
once everybody has learned

58
00:03:08,300 --> 00:03:11,480
what the new is through BSR.

59
00:03:11,480 --> 00:03:14,930
So that said, let's go ahead
and jump into the command line

60
00:03:14,930 --> 00:03:18,470
and get this configured.

61
00:03:18,470 --> 00:03:22,690
So let's begin with
our show IP PIM RP map.

62
00:03:22,690 --> 00:03:25,250
We'll send that to
all of the routers.

63
00:03:25,250 --> 00:03:28,060
And as we can see
here on router 1,

64
00:03:28,060 --> 00:03:32,590
there are currently no
Group-to-RP Mappings.

65
00:03:32,590 --> 00:03:35,980
We should see this on
all of the routers.

66
00:03:35,980 --> 00:03:39,230
Router 2 also has
no information,

67
00:03:39,230 --> 00:03:46,630
neither does router 3,
router 4, router 5, router 6,

68
00:03:46,630 --> 00:03:48,700
and router 7.

69
00:03:48,700 --> 00:03:52,150
8, 9, and 10, of course,
are not running PIM,

70
00:03:52,150 --> 00:03:54,610
so they wouldn't have any
information at this point

71
00:03:54,610 --> 00:03:55,540
anyway.

72
00:03:55,540 --> 00:03:59,650
So none of the devices have
any information about the RP

73
00:03:59,650 --> 00:04:00,880
at this point.

74
00:04:00,880 --> 00:04:03,640
Let's go ahead and
go on to router 2

75
00:04:03,640 --> 00:04:08,500
and configure it to be
a candidate RP for BSR.

76
00:04:08,500 --> 00:04:11,900
So once again, if we do
a show pim interface,

77
00:04:11,900 --> 00:04:15,550
notice that our loopback is
still enabled for multicast.

78
00:04:15,550 --> 00:04:19,480
I only removed auto-RP,
I didn't unconfigure

79
00:04:19,480 --> 00:04:21,110
any of our interfaces.

80
00:04:21,110 --> 00:04:23,260
So the loopback
is good to go, all

81
00:04:23,260 --> 00:04:25,990
we have to do is go
into configuration mode,

82
00:04:25,990 --> 00:04:31,720
enter router pim for ipv4, then
we configure bsr candidate.

83
00:04:31,720 --> 00:04:34,090
And notice if we hit
the question mark,

84
00:04:34,090 --> 00:04:37,300
we can either set this
to be a candidate-bsr

85
00:04:37,300 --> 00:04:39,670
or a candidate-rp.

86
00:04:39,670 --> 00:04:42,130
But we're going for
the candidate-rp.

87
00:04:42,130 --> 00:04:46,900
As you can see here,
unlike auto-RP on IOS XR,

88
00:04:46,900 --> 00:04:49,510
this is not looking
for an interface.

89
00:04:49,510 --> 00:04:53,150
This actually wants us to
simply put in an IP address.

90
00:04:53,150 --> 00:04:56,080
So we'll simply put in the
address for the loopback

91
00:04:56,080 --> 00:04:57,160
interface.

92
00:04:57,160 --> 00:04:59,230
There are some
other choices here

93
00:04:59,230 --> 00:05:03,220
much like what we had on
our autoconfiguration.

94
00:05:03,220 --> 00:05:06,260
Again, we could configure
this for bidirectional.

95
00:05:06,260 --> 00:05:09,280
We could filter this using
a group so that it's only

96
00:05:09,280 --> 00:05:11,720
an RP for certain groups.

97
00:05:11,720 --> 00:05:13,300
We could change the interval.

98
00:05:13,300 --> 00:05:17,020
And something else that we can
do here is set the priority.

99
00:05:17,020 --> 00:05:20,180
We'll look at that
actually in our next video

100
00:05:20,180 --> 00:05:21,810
when we do redundancy.

101
00:05:21,810 --> 00:05:26,390
So for now, let's just hit
Enter, commit those changes,

102
00:05:26,390 --> 00:05:28,710
and exit configuration.

103
00:05:28,710 --> 00:05:31,520
Now, let's go configure the BSR.

104
00:05:31,520 --> 00:05:34,580
So this is going to
be, again, on router 5.

105
00:05:34,580 --> 00:05:37,410
We'll simply go into
configuration mode.

106
00:05:37,410 --> 00:05:42,260
And the command here is
ip pim bsr-candidate.

107
00:05:42,260 --> 00:05:46,230
Now, on this device, it
does want an interface.

108
00:05:46,230 --> 00:05:48,950
So again, it's going
to be loopback 0.

109
00:05:48,950 --> 00:05:51,440
However, notice that
the only other thing

110
00:05:51,440 --> 00:05:55,640
to put after this is
the hash mask length.

111
00:05:55,640 --> 00:05:59,490
Notice that it says that
this is for RP selection.

112
00:05:59,490 --> 00:06:01,400
This is going to come
into play when we have

113
00:06:01,400 --> 00:06:04,040
more than one candidate-rp.

114
00:06:04,040 --> 00:06:07,520
So again, our next
section is going

115
00:06:07,520 --> 00:06:10,460
to be on redundancy with BSR.

116
00:06:10,460 --> 00:06:12,230
We'll cover this then.

117
00:06:12,230 --> 00:06:17,370
For now, we're just going to hit
Enter and exit configuration.

118
00:06:17,370 --> 00:06:19,100
Notice that we
almost immediately

119
00:06:19,100 --> 00:06:24,530
see that line protocol come up
on tunnel 0, indicating we've

120
00:06:24,530 --> 00:06:26,540
learned an RP.

121
00:06:26,540 --> 00:06:31,370
We can, of course, verify that
with a show ip pim rp map,

122
00:06:31,370 --> 00:06:35,600
and what we see here is for the
entire multicast group range,

123
00:06:35,600 --> 00:06:40,850
the RP has been configured
as 10.2.2.2, the info

124
00:06:40,850 --> 00:06:45,440
source for that is, again,
router 2 because we're

125
00:06:45,440 --> 00:06:46,610
on the BSR.

126
00:06:46,610 --> 00:06:49,280
Notice it says right up
here that this system

127
00:06:49,280 --> 00:06:51,560
is the bootstrap router.

128
00:06:51,560 --> 00:06:54,740
We learned it via
bootstrap, it currently

129
00:06:54,740 --> 00:06:58,070
has a priority of 192,
and, of course, we

130
00:06:58,070 --> 00:07:03,050
see the whole time of 150 there
that could also be configured.

131
00:07:03,050 --> 00:07:07,700
Of course, if we look at this on
any router that's not the BSR,

132
00:07:07,700 --> 00:07:14,530
so again, let's say
router 6, we see

133
00:07:14,530 --> 00:07:19,840
that, again, it knows the RP,
but notice the info source now.

134
00:07:19,840 --> 00:07:25,330
The info source is now
router 5, which is the BSR.

135
00:07:25,330 --> 00:07:27,010
Now, the rest of
this information

136
00:07:27,010 --> 00:07:30,400
is fairly similar, of
course, to what router 5 had,

137
00:07:30,400 --> 00:07:34,690
and let's use our command
window again to verify this

138
00:07:34,690 --> 00:07:36,890
on all of the routers.

139
00:07:36,890 --> 00:07:40,540
So we'll just redo our
show ip pim rp map.

140
00:07:40,540 --> 00:07:43,000
Again, we've already
seen it here on router 6,

141
00:07:43,000 --> 00:07:47,050
but let's go over and start
looking at these from router 1.

142
00:07:47,050 --> 00:07:51,250
So router 1, we see that it's
now properly learned the RP.

143
00:07:51,250 --> 00:07:53,780
Router 2 has as well.

144
00:07:53,780 --> 00:07:55,720
So has router 3.

145
00:07:55,720 --> 00:07:57,970
So has router 4.

146
00:07:57,970 --> 00:08:00,340
We already looked at 5 and 6.

147
00:08:00,340 --> 00:08:03,950
So if we jump over to 7, we
see that 7 has it as well.

148
00:08:03,950 --> 00:08:07,780
And of course, 8, 9, and 10
won't because they're not

149
00:08:07,780 --> 00:08:10,580
participating in PIM itself.

150
00:08:10,580 --> 00:08:13,270
So now that everybody's
learned the RP,

151
00:08:13,270 --> 00:08:17,120
we should be able to start
our data plane again and have

152
00:08:17,120 --> 00:08:18,060
this work.

153
00:08:18,060 --> 00:08:21,660
So let's go start up our
ping again on router 10.

154
00:08:21,660 --> 00:08:23,570
So we'll start our ping.

155
00:08:23,570 --> 00:08:27,690
And then let's go over to router
7 and do some verification.

156
00:08:27,690 --> 00:08:30,690
So we'll just start
with a show ip mroute.

157
00:08:30,690 --> 00:08:34,370
So first, of course, we see that
we have the star comma G entry

158
00:08:34,370 --> 00:08:41,299
with the correct RP 10.2.2.2
, and we've learned the S,G

159
00:08:41,299 --> 00:08:42,260
entry.

160
00:08:42,260 --> 00:08:46,430
Given this information, this
should indicate that the data

161
00:08:46,430 --> 00:08:49,320
plane is working
properly because, again,

162
00:08:49,320 --> 00:08:54,770
I wouldn't have an S,G entry if
the first packet hadn't gotten

163
00:08:54,770 --> 00:08:55,970
to router 7.

164
00:08:55,970 --> 00:08:59,330
So if I repeat this command
and I put the count on it,

165
00:08:59,330 --> 00:09:01,430
once again, we should
see that it has currently

166
00:09:01,430 --> 00:09:03,510
forwarded 32 packets.

167
00:09:03,510 --> 00:09:08,450
And if we give it just a
second, it's now forwarded 37.

168
00:09:08,450 --> 00:09:12,680
Just as another quick side
note here on this count output,

169
00:09:12,680 --> 00:09:15,830
if you see where it
says, packets forwarded--

170
00:09:15,830 --> 00:09:22,070
42, but yet on the source tree,
it's only forwarding 37, well,

171
00:09:22,070 --> 00:09:25,820
notice that 5 were
actually forwarded down

172
00:09:25,820 --> 00:09:28,830
the RP-tree or the
rendezvous point tree,

173
00:09:28,830 --> 00:09:30,780
meaning the shared tree.

174
00:09:30,780 --> 00:09:34,310
So what that really means
is that 5 packets came down

175
00:09:34,310 --> 00:09:37,550
the shared tree before
it did the switch over

176
00:09:37,550 --> 00:09:39,020
to the source tree.

177
00:09:39,020 --> 00:09:40,800
That's all that really means.

178
00:09:40,800 --> 00:09:43,820
But if you add up
the 37 and the 5,

179
00:09:43,820 --> 00:09:46,430
that's the total
of the 42 packets

180
00:09:46,430 --> 00:09:50,540
that have come through on
this group route as a total.

181
00:09:50,540 --> 00:09:54,230
One other thing to note, by
the way, on the show ip mroute,

182
00:09:54,230 --> 00:09:59,840
notice that yes, we are still
a member of the 224.0.1.40

183
00:09:59,840 --> 00:10:03,410
group for auto-RP, just
because that's automatically

184
00:10:03,410 --> 00:10:05,570
listened for on Cisco routers.

185
00:10:05,570 --> 00:10:08,090
But notice that no
other special groups

186
00:10:08,090 --> 00:10:11,450
have been joined because
all of this information

187
00:10:11,450 --> 00:10:15,270
actually travels
inside of PIM itself.

188
00:10:15,270 --> 00:10:18,710
So in this video, we
saw how to configure

189
00:10:18,710 --> 00:10:21,860
BSR to automatically
announce the rendezvous

190
00:10:21,860 --> 00:10:24,600
point into our environment.

191
00:10:24,600 --> 00:10:28,670
Now, as we saw, it's actually
very similar to auto-RP,

192
00:10:28,670 --> 00:10:31,940
except it doesn't need those
extra groups to function

193
00:10:31,940 --> 00:10:34,380
since it just uses PIM itself.

194
00:10:34,380 --> 00:10:37,490
Now, that does mean that
it requires PIM version 2,

195
00:10:37,490 --> 00:10:40,430
but that's really not an
issue since all of our devices

196
00:10:40,430 --> 00:10:43,530
default to PIM version 2 anyway.

197
00:10:43,530 --> 00:10:47,750
Now, just like before, BSR
is up and running and working

198
00:10:47,750 --> 00:10:50,600
and everything's
fine, however, we

199
00:10:50,600 --> 00:10:52,410
haven't looked at redundancy.

200
00:10:52,410 --> 00:10:55,040
And that's exactly what
we're going to do next.

201
00:10:55,040 --> 00:10:58,430
Till then, I hope this has
been informative for you,

202
00:10:58,430 --> 00:11:01,540
and I'd like to thank
you for viewing.

203
00:11:01,540 --> 00:11:05,000