1
00:00:00,000 --> 00:00:02,964
[AUDIO LOGO]

2
00:00:02,964 --> 00:00:07,910

3
00:00:07,910 --> 00:00:11,090
So we now have everything
working in our environment

4
00:00:11,090 --> 00:00:14,480
exactly as we
designed it, except we

5
00:00:14,480 --> 00:00:18,380
don't have redundancy
for router 1, our route

6
00:00:18,380 --> 00:00:21,410
reflector in 65001.

7
00:00:21,410 --> 00:00:23,300
So in this video,
we're going to set up

8
00:00:23,300 --> 00:00:26,450
router 2 as a redundant
route reflector.

9
00:00:26,450 --> 00:00:29,250
Let's bring up our
topology real quickly just

10
00:00:29,250 --> 00:00:30,985
to remember exactly
what we're doing.

11
00:00:30,985 --> 00:00:33,110
And then we're going to
jump into the command line,

12
00:00:33,110 --> 00:00:36,450
get router 2 up and running as
a redundant route reflector,

13
00:00:36,450 --> 00:00:39,650
and then verify that
it's actually working

14
00:00:39,650 --> 00:00:44,690
and that we have multiple paths
to get to our destinations.

15
00:00:44,690 --> 00:00:47,980
So this was our original
design from back when

16
00:00:47,980 --> 00:00:49,930
we were making our game plan.

17
00:00:49,930 --> 00:00:52,060
And if we take a
look at this, we've

18
00:00:52,060 --> 00:00:56,260
accomplished everything on
here that we set out to do.

19
00:00:56,260 --> 00:00:58,570
The only thing we
haven't configured yet

20
00:00:58,570 --> 00:01:02,380
is this route reflector
over here on router 2

21
00:01:02,380 --> 00:01:06,070
and, therefore, all of
these other neighborships

22
00:01:06,070 --> 00:01:09,620
that we're going to need in
order for this to function.

23
00:01:09,620 --> 00:01:15,130
We also need to reconfigure
this neighborship between router

24
00:01:15,130 --> 00:01:17,740
1 and router 2
because we don't want

25
00:01:17,740 --> 00:01:22,660
router 2 to be a route reflector
client of its peer route

26
00:01:22,660 --> 00:01:23,870
reflector.

27
00:01:23,870 --> 00:01:27,550
So all of that said, let's
jump into the command line.

28
00:01:27,550 --> 00:01:31,270
First, we'll reconfigure router
1 to fix that neighborship

29
00:01:31,270 --> 00:01:32,530
to router 2.

30
00:01:32,530 --> 00:01:37,690
And then we'll do the full
configuration on router 2.

31
00:01:37,690 --> 00:01:39,700
So we're not
configuring anything we

32
00:01:39,700 --> 00:01:41,780
haven't seen many times before.

33
00:01:41,780 --> 00:01:45,250
So we'll just go ahead and paste
the configuration in and then

34
00:01:45,250 --> 00:01:46,690
just talk about it.

35
00:01:46,690 --> 00:01:50,140
What we're doing here is
removing our neighborship

36
00:01:50,140 --> 00:01:51,580
to router 2.

37
00:01:51,580 --> 00:01:54,670
Then we're reinstalling our
neighborship to router 2,

38
00:01:54,670 --> 00:01:57,400
putting in its remote
AS, the update source,

39
00:01:57,400 --> 00:01:59,800
and activating the
address family.

40
00:01:59,800 --> 00:02:03,190
The key thing we're
doing here is removing it

41
00:02:03,190 --> 00:02:06,680
from our iBGP peers
neighbor group

42
00:02:06,680 --> 00:02:10,280
so that it is no longer
a route reflector client.

43
00:02:10,280 --> 00:02:13,840
So now we're just configuring
it like a traditional BGP

44
00:02:13,840 --> 00:02:15,250
neighborship.

45
00:02:15,250 --> 00:02:17,800
Now let's go configure router 2.

46
00:02:17,800 --> 00:02:20,110
We see here on router
2 where router 1

47
00:02:20,110 --> 00:02:22,240
bounced that relationship.

48
00:02:22,240 --> 00:02:25,490
And we'll paste this
configuration in as well.

49
00:02:25,490 --> 00:02:28,240
This is going to be almost
the exact same configuration

50
00:02:28,240 --> 00:02:30,970
as router 1 had when
we configured it

51
00:02:30,970 --> 00:02:32,620
as a route reflector.

52
00:02:32,620 --> 00:02:35,740
Once again, we're creating
our neighbor group.

53
00:02:35,740 --> 00:02:39,160
We're setting up the remote
AS, the update source,

54
00:02:39,160 --> 00:02:42,880
and the address family with
a route-reflector-client

55
00:02:42,880 --> 00:02:46,660
and next-hop-self under
that neighbor group.

56
00:02:46,660 --> 00:02:49,150
And then we're simply
applying the neighbor group

57
00:02:49,150 --> 00:02:51,640
to the routers that are
going to be our new peers--

58
00:02:51,640 --> 00:02:54,850
routers 3, 4, and 5.

59
00:02:54,850 --> 00:02:58,930
Of course, we still have to
configure routers 3, 4, and 5

60
00:02:58,930 --> 00:03:01,110
to neighbor with router 2.

61
00:03:01,110 --> 00:03:03,610
Once again, that's just going
to be a standard neighborship.

62
00:03:03,610 --> 00:03:06,800
We'll paste the config in
on those routers as well.

63
00:03:06,800 --> 00:03:10,333
So router 3 and 4 are going
to be the same configuration.

64
00:03:10,333 --> 00:03:12,250
So this is just going
to be a new neighborship

65
00:03:12,250 --> 00:03:15,920
with the remote-as, the
update-source, and of course

66
00:03:15,920 --> 00:03:18,290
the next-hop-self.

67
00:03:18,290 --> 00:03:21,230
Router 4 is the
same configuration.

68
00:03:21,230 --> 00:03:23,690
Router 5 of course
is slightly different

69
00:03:23,690 --> 00:03:26,180
just because it's IOS XE.

70
00:03:26,180 --> 00:03:28,790
However, it's the
same basic properties.

71
00:03:28,790 --> 00:03:30,360
If we've done all
this correctly,

72
00:03:30,360 --> 00:03:33,070
we should be able to
go up to router 2.

73
00:03:33,070 --> 00:03:35,210
We'll do a show bgp summary.

74
00:03:35,210 --> 00:03:37,900
And we see that we are
in fact now neighbors

75
00:03:37,900 --> 00:03:43,450
with routers 3, 4, and 5,
which we weren't previously.

76
00:03:43,450 --> 00:03:46,670
Now, of course, the whole point
of this was to have redundancy.

77
00:03:46,670 --> 00:03:48,710
So let's make sure
that's worked.

78
00:03:48,710 --> 00:03:51,010
Let's go over to router 5.

79
00:03:51,010 --> 00:03:54,280
If we do a show ip
bgp, we see that we now

80
00:03:54,280 --> 00:03:57,790
have two paths to each
destination, one learned

81
00:03:57,790 --> 00:04:00,250
from each route reflector.

82
00:04:00,250 --> 00:04:03,100
Now, one final thing we
need to configure here--

83
00:04:03,100 --> 00:04:06,160
when you have route
reflectors that

84
00:04:06,160 --> 00:04:09,310
are acting as a
redundant cluster rather

85
00:04:09,310 --> 00:04:13,030
than hierarchical, you
need to set the cluster ID

86
00:04:13,030 --> 00:04:15,320
to be the same number.

87
00:04:15,320 --> 00:04:17,709
The reason we do
this is to prevent

88
00:04:17,709 --> 00:04:20,769
suboptimal routing in
the BGP environment

89
00:04:20,769 --> 00:04:23,345
where you could possibly have
one route reflector telling

90
00:04:23,345 --> 00:04:25,720
the other route reflector
about an update, who then tells

91
00:04:25,720 --> 00:04:27,520
the route reflector clients.

92
00:04:27,520 --> 00:04:30,250
It generally doesn't
work out too well.

93
00:04:30,250 --> 00:04:33,830
Again, it could lead to
suboptimal path selection.

94
00:04:33,830 --> 00:04:36,910
So it's a best practice to
set these to the same number.

95
00:04:36,910 --> 00:04:41,020
That is, of course, assuming
that your redundant route

96
00:04:41,020 --> 00:04:44,540
reflectors are actually
peered with each other.

97
00:04:44,540 --> 00:04:47,060
There's no requirement
to actually do that.

98
00:04:47,060 --> 00:04:49,840
However, here in
our lab environment,

99
00:04:49,840 --> 00:04:51,530
they are peered together.

100
00:04:51,530 --> 00:04:54,250
So we'll go ahead and
set that cluster ID

101
00:04:54,250 --> 00:04:57,670
to be the same on
router 1 and router 2.

102
00:04:57,670 --> 00:05:00,850
Before we do that, just to see
that they're not the same now,

103
00:05:00,850 --> 00:05:03,940
let's do a show ip bgp for
one of the prefixes here.

104
00:05:03,940 --> 00:05:06,760
We'll pick on the 100.4.4.0.

105
00:05:06,760 --> 00:05:10,480
And we see here that they
are in fact coming from two

106
00:05:10,480 --> 00:05:12,610
different cluster lists--

107
00:05:12,610 --> 00:05:18,460
10.2.2.2 and
10.1.1.1, each cluster

108
00:05:18,460 --> 00:05:22,600
being represented by the
route reflector's router ID.

109
00:05:22,600 --> 00:05:24,200
That's what we want to change.

110
00:05:24,200 --> 00:05:26,170
So let's go up to router 1.

111
00:05:26,170 --> 00:05:29,320
And since this is going
between router 1 and router 2,

112
00:05:29,320 --> 00:05:32,230
we'll effectively
just set this to 12.

113
00:05:32,230 --> 00:05:35,230
So again, we'll just paste
this configuration in.

114
00:05:35,230 --> 00:05:37,570
The only thing new
here is this bgp

115
00:05:37,570 --> 00:05:39,700
cluster-id that we pasted in.

116
00:05:39,700 --> 00:05:43,930
And also notice the
route reflector clients

117
00:05:43,930 --> 00:05:47,000
again going down
and coming back up.

118
00:05:47,000 --> 00:05:48,820
So again, this
should be done either

119
00:05:48,820 --> 00:05:52,990
during initial deployment or
during a maintenance window.

120
00:05:52,990 --> 00:05:55,480
We'll do the same
thing on Router 2.

121
00:05:55,480 --> 00:05:58,480
It's exactly the same
config because we're setting

122
00:05:58,480 --> 00:06:00,640
the cluster-id to match.

123
00:06:00,640 --> 00:06:02,350
Once the neighborships
come back up,

124
00:06:02,350 --> 00:06:04,750
let's go back over to router 5.

125
00:06:04,750 --> 00:06:07,810
We'll do our show ip bgp
again for the prefix.

126
00:06:07,810 --> 00:06:10,030
And we can see that
now the cluster list

127
00:06:10,030 --> 00:06:12,770
is the same on both of them.

128
00:06:12,770 --> 00:06:15,490
So now we have our
cluster-id set properly,

129
00:06:15,490 --> 00:06:19,250
and we have our redundancy.

130
00:06:19,250 --> 00:06:22,820
In this video, we saw
how to configure a device

131
00:06:22,820 --> 00:06:26,090
as a redundant route
reflector and how

132
00:06:26,090 --> 00:06:29,660
to set the cluster-id to
match when they're supposed

133
00:06:29,660 --> 00:06:32,450
to be in a redundant cluster.

134
00:06:32,450 --> 00:06:34,460
Again, this wouldn't
be necessary

135
00:06:34,460 --> 00:06:37,400
if you were doing
hierarchical route reflectors.

136
00:06:37,400 --> 00:06:40,490
But for a redundant
cluster, the cluster-id

137
00:06:40,490 --> 00:06:43,370
should be set to be the same.

138
00:06:43,370 --> 00:06:45,680
I hope this has been
informative for you,

139
00:06:45,680 --> 00:06:48,730
and I'd like to thank
you for viewing.

140
00:06:48,730 --> 00:06:52,032