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

2
00:00:02,415 --> 00:00:07,730

3
00:00:07,730 --> 00:00:12,890
So now, it's time to join our
two domains together with BGP.

4
00:00:12,890 --> 00:00:17,210
And get our environment ready
to support traffic engineering,

5
00:00:17,210 --> 00:00:19,890
both tunnels and policies.

6
00:00:19,890 --> 00:00:25,620
So we're going to set up
BGP and PCEP in this video.

7
00:00:25,620 --> 00:00:27,170
So we're definitely
going to have

8
00:00:27,170 --> 00:00:29,570
to take a look at the
diagram this time.

9
00:00:29,570 --> 00:00:31,190
Talk about what
we're going to build.

10
00:00:31,190 --> 00:00:33,740
This is going to be involving
our route reflector,

11
00:00:33,740 --> 00:00:35,330
different address
families that we're

12
00:00:35,330 --> 00:00:37,200
going to be running
two different devices.

13
00:00:37,200 --> 00:00:39,650
So let's go ahead and take
a look at that topology.

14
00:00:39,650 --> 00:00:42,150
Talk about what it is
we're going to be building.

15
00:00:42,150 --> 00:00:45,020
And then, of course, we're going
to jump onto the command line,

16
00:00:45,020 --> 00:00:50,730
get this all set up and working,
and do some verification.

17
00:00:50,730 --> 00:00:53,720
So we're still on
MPLS topology 5,

18
00:00:53,720 --> 00:00:57,200
since we're building on what
we've done in previous videos.

19
00:00:57,200 --> 00:01:04,340
Also, note as we jump in
here, routers 2, 6, and 8

20
00:01:04,340 --> 00:01:06,500
have been pre-configured
just so we

21
00:01:06,500 --> 00:01:09,410
don't have to configure
all of the devices.

22
00:01:09,410 --> 00:01:13,770
And routers 3 and 4 don't
need any configuration.

23
00:01:13,770 --> 00:01:16,020
So we don't have to
configure those either.

24
00:01:16,020 --> 00:01:20,630
But what we are going to be
configuring is BGP on route

25
00:01:20,630 --> 00:01:25,160
reflector 1, it's going to be
running address family link

26
00:01:25,160 --> 00:01:30,110
state with routers
1, 2, 5, and 6.

27
00:01:30,110 --> 00:01:33,080
And it's going to be
running address family IPv4

28
00:01:33,080 --> 00:01:37,280
unicast on routers
7 and 8 to exchange

29
00:01:37,280 --> 00:01:39,830
the routes between the
two different domains.

30
00:01:39,830 --> 00:01:44,180
And then of course, we'll
also be setting up PCEP.

31
00:01:44,180 --> 00:01:47,070
So let's go ahead and
jump in and get started.

32
00:01:47,070 --> 00:01:49,620
We'll start on
route reflector 1.

33
00:01:49,620 --> 00:01:52,140
And keep in mind, as
we're configuring it,

34
00:01:52,140 --> 00:01:55,710
we should see routers
2, 6, and 8 come up

35
00:01:55,710 --> 00:01:58,230
as we configure the
route reflector side.

36
00:01:58,230 --> 00:02:02,050
Because again, those devices
are already configured.

37
00:02:02,050 --> 00:02:06,740
So let's go ahead and jump
in to the route reflector.

38
00:02:06,740 --> 00:02:09,880
So actually, before we jump
right into the route reflector,

39
00:02:09,880 --> 00:02:14,410
let's start on the PE routers
and verify that we don't have

40
00:02:14,410 --> 00:02:16,940
any routes to the other domain.

41
00:02:16,940 --> 00:02:21,820
So for example, we'll do a show
IP route here for 100.8.8.8.

42
00:02:21,820 --> 00:02:23,320
This is a network
that we're going

43
00:02:23,320 --> 00:02:28,480
to make available from the OSPF
domain, obviously, on router 8.

44
00:02:28,480 --> 00:02:31,760
And we see that this subnet
is currently not in our table.

45
00:02:31,760 --> 00:02:34,390
And if we go to
router 8, here, we

46
00:02:34,390 --> 00:02:37,720
do a show IP route
for 100.7.7.7.

47
00:02:37,720 --> 00:02:40,670
And this is in the
same situation.

48
00:02:40,670 --> 00:02:42,670
So before we start
joining these together,

49
00:02:42,670 --> 00:02:46,300
I just want to make sure we
understand that as we start,

50
00:02:46,300 --> 00:02:49,310
we have no reachability
between domains.

51
00:02:49,310 --> 00:02:53,470
So that said, let's go ahead
and start our configuration up

52
00:02:53,470 --> 00:02:55,010
on the route reflector.

53
00:02:55,010 --> 00:02:57,460
So let's begin by
creating router BGP.

54
00:02:57,460 --> 00:02:59,680
And we'll just use AS-100.

55
00:02:59,680 --> 00:03:01,990
We'll set our router ID.

56
00:03:01,990 --> 00:03:03,820
This router is
effectively acting

57
00:03:03,820 --> 00:03:06,740
like router 11 in our topology.

58
00:03:06,740 --> 00:03:09,560
And then let's activate
our address families.

59
00:03:09,560 --> 00:03:13,360
So we need address family,
link-state, link-state

60
00:03:13,360 --> 00:03:16,960
and address family IPv4 unicast.

61
00:03:16,960 --> 00:03:19,420
Next, let's set up
a neighbor group

62
00:03:19,420 --> 00:03:22,243
for our link-state
neighbors just because we're

63
00:03:22,243 --> 00:03:23,410
going to have a few of them.

64
00:03:23,410 --> 00:03:25,630
And it'll simplify
the configuration.

65
00:03:25,630 --> 00:03:27,160
This is, of course, optional.

66
00:03:27,160 --> 00:03:29,560
We could just configure
the neighbors individually.

67
00:03:29,560 --> 00:03:32,500
But again, this simplifies
the configuration

68
00:03:32,500 --> 00:03:33,860
just a little bit.

69
00:03:33,860 --> 00:03:35,470
So we'll create
our neighbor group.

70
00:03:35,470 --> 00:03:38,050
We'll call it ls_peers.

71
00:03:38,050 --> 00:03:40,810
And the things we want
to configure in here.

72
00:03:40,810 --> 00:03:43,390
Let's configure the
remote AS to be 100.

73
00:03:43,390 --> 00:03:45,700
We're just going to use iBGP.

74
00:03:45,700 --> 00:03:48,880
We'll set our update
source to be loopback zero.

75
00:03:48,880 --> 00:03:53,840
And we'll activate the address
family, link-state, link-state.

76
00:03:53,840 --> 00:03:56,660
So next, let's
configure our neighbors.

77
00:03:56,660 --> 00:03:59,410
So we'll say neighbor 10.1.1.1.

78
00:03:59,410 --> 00:04:05,830
And tell it to use the
neighbor group ls_peers.

79
00:04:05,830 --> 00:04:10,220
We'll do the same thing for
neighbor two, neighbor five,

80
00:04:10,220 --> 00:04:11,930
and neighbor six.

81
00:04:11,930 --> 00:04:15,420
Next, let's configure
our IPv4 neighbors.

82
00:04:15,420 --> 00:04:17,540
So that's going to
be routers 7 and 8.

83
00:04:17,540 --> 00:04:20,390
We could, of course, use
a neighbor group for those

84
00:04:20,390 --> 00:04:21,180
as well.

85
00:04:21,180 --> 00:04:23,580
But this is going to be
a simpler configuration.

86
00:04:23,580 --> 00:04:26,672
So we'll just go right
into neighbor 10.7.7.7.

87
00:04:26,672 --> 00:04:30,050
And here, we'll simply say
that it's a remote AS-100.

88
00:04:30,050 --> 00:04:32,960
The update source
is loopback zero.

89
00:04:32,960 --> 00:04:36,380
And the address family
is IPv4 unicast.

90
00:04:36,380 --> 00:04:38,630
Then under the
address family, we

91
00:04:38,630 --> 00:04:41,670
do want to set these up to
be route reflector clients.

92
00:04:41,670 --> 00:04:44,180
So next, we'll do the same
thing, but for router 8.

93
00:04:44,180 --> 00:04:48,600

94
00:04:48,600 --> 00:04:49,990
That should be everything.

95
00:04:49,990 --> 00:04:51,580
So let's commit our changes.

96
00:04:51,580 --> 00:04:54,780
So we see here, we're
getting a failure to commit.

97
00:04:54,780 --> 00:04:57,450
And if we do a
show config failed,

98
00:04:57,450 --> 00:05:02,250
it's telling us that neighbor
10.8.8.8 is not a neighbor.

99
00:05:02,250 --> 00:05:04,960
It says, we have no
remote AS defined.

100
00:05:04,960 --> 00:05:07,720
So let's scroll up
here just a minute.

101
00:05:07,720 --> 00:05:09,760
And what we see is
that, yes, in fact,

102
00:05:09,760 --> 00:05:12,450
when we typed
neighbor 10.8.8.8, we

103
00:05:12,450 --> 00:05:15,240
went right to update
source loopback zero, right

104
00:05:15,240 --> 00:05:18,120
into the address family, and
configured the route reflector

105
00:05:18,120 --> 00:05:18,780
client.

106
00:05:18,780 --> 00:05:21,720
But we missed putting
in the remote AS.

107
00:05:21,720 --> 00:05:24,160
So let's go ahead
and correct that.

108
00:05:24,160 --> 00:05:26,380
And let's try our commit again.

109
00:05:26,380 --> 00:05:27,900
So that's looking a lot better.

110
00:05:27,900 --> 00:05:29,010
It took the commit.

111
00:05:29,010 --> 00:05:32,220
And we see some of those
neighbors starting to come up.

112
00:05:32,220 --> 00:05:36,270
We said that routers 2, 6, and
8 are already pre-configured.

113
00:05:36,270 --> 00:05:39,400
And we see that all
of those have come up.

114
00:05:39,400 --> 00:05:41,650
So this looks like
a good configuration

115
00:05:41,650 --> 00:05:43,500
now on the route reflector.

116
00:05:43,500 --> 00:05:46,830
Let's go ahead and move
on then to router 1.

117
00:05:46,830 --> 00:05:50,110
So router 1 is going to be
running the link-state address

118
00:05:50,110 --> 00:05:50,890
family.

119
00:05:50,890 --> 00:05:53,350
And we need to get the
link-state information

120
00:05:53,350 --> 00:05:56,540
from ISIS into BGP.

121
00:05:56,540 --> 00:05:58,930
So let's configure that first.

122
00:05:58,930 --> 00:06:02,860
To do that, we simply
go into router ISIS 1.

123
00:06:02,860 --> 00:06:05,860
And we tell it to
distribute its information

124
00:06:05,860 --> 00:06:08,500
into BGP link-state.

125
00:06:08,500 --> 00:06:11,780
That's all we should have
to do on the ISIS side.

126
00:06:11,780 --> 00:06:14,860
So now, let's go
into router BGP 100.

127
00:06:14,860 --> 00:06:20,020
We'll set our BGP router ID and
configure our address family.

128
00:06:20,020 --> 00:06:24,040
Again, the only one we need
is link-state, link-state.

129
00:06:24,040 --> 00:06:25,870
Next, let's configure
our neighbor.

130
00:06:25,870 --> 00:06:28,000
This is going to be the
route reflector, which

131
00:06:28,000 --> 00:06:30,610
is 10.11.11.11.

132
00:06:30,610 --> 00:06:33,380
Let's not forget our
remote AS this time.

133
00:06:33,380 --> 00:06:35,710
So remote AS-100.

134
00:06:35,710 --> 00:06:37,840
We'll set our update source.

135
00:06:37,840 --> 00:06:41,350
And we'll activate that address
family for this neighbor.

136
00:06:41,350 --> 00:06:42,290
That should be it.

137
00:06:42,290 --> 00:06:44,230
Let's commit our changes.

138
00:06:44,230 --> 00:06:46,220
Exit configuration.

139
00:06:46,220 --> 00:06:49,270
And here, we see that
neighbor 11 has come up.

140
00:06:49,270 --> 00:06:51,140
So far this is looking good.

141
00:06:51,140 --> 00:06:53,650
Let's go configure
router 5 next.

142
00:06:53,650 --> 00:06:57,190
Now, remember router
5 is running OSPF.

143
00:06:57,190 --> 00:07:01,170
So for this one, we have
to go into router OSPF 1

144
00:07:01,170 --> 00:07:03,580
and say distribute link-state.

145
00:07:03,580 --> 00:07:06,420
So slightly different
command, but the same idea.

146
00:07:06,420 --> 00:07:09,570
We need to take the OSPF
link-state information

147
00:07:09,570 --> 00:07:12,240
and send it into BGP.

148
00:07:12,240 --> 00:07:15,600
Now, we'll configure
our router BGP 100.

149
00:07:15,600 --> 00:07:18,580
Of course, set our router ID.

150
00:07:18,580 --> 00:07:22,410
Now, since we don't need it, we
can turn off the IPv4 address

151
00:07:22,410 --> 00:07:23,220
family.

152
00:07:23,220 --> 00:07:24,607
This is, of course, optional.

153
00:07:24,607 --> 00:07:25,690
You don't have to do this.

154
00:07:25,690 --> 00:07:31,080
But we can say no BGP,
default IPv4 unicast.

155
00:07:31,080 --> 00:07:35,100
That just turns off the default
IPv4 unicast address family,

156
00:07:35,100 --> 00:07:38,640
since we're not going to be
using it here on router 5.

157
00:07:38,640 --> 00:07:42,750
Then we'll configure our
neighbor 10.11.11.11.

158
00:07:42,750 --> 00:07:46,110
And we'll do that remote AS-100.

159
00:07:46,110 --> 00:07:49,290
We'll set the update source
to our loopback zero.

160
00:07:49,290 --> 00:07:54,030
Then we'll go into the address
family, link-state, link-state.

161
00:07:54,030 --> 00:07:57,090
And we'll activate this
neighborship for that address

162
00:07:57,090 --> 00:07:58,020
family.

163
00:07:58,020 --> 00:08:02,630
We see here that our neighbor
10.11.11.11 has come up.

164
00:08:02,630 --> 00:08:05,330
So once again, this is
looking pretty good.

165
00:08:05,330 --> 00:08:08,170
Let's go ahead and
verify this information

166
00:08:08,170 --> 00:08:10,630
on each of our routers
to make sure everything's

167
00:08:10,630 --> 00:08:11,960
up and running.

168
00:08:11,960 --> 00:08:14,110
We'll just start on
router 1, so that we're

169
00:08:14,110 --> 00:08:16,040
going in a logical order.

170
00:08:16,040 --> 00:08:18,340
So the command we're going
to use for verification

171
00:08:18,340 --> 00:08:21,430
is show BGP link-state,
link-state summary.

172
00:08:21,430 --> 00:08:24,700
And what we're looking for
is each of these devices

173
00:08:24,700 --> 00:08:27,160
should be up with
the route reflector.

174
00:08:27,160 --> 00:08:30,510
We can see here
that router 1 is up.

175
00:08:30,510 --> 00:08:35,340
If we look at router
2, router 2 is also up.

176
00:08:35,340 --> 00:08:38,340
Router 5 also up.

177
00:08:38,340 --> 00:08:40,880
And finally, router 6.

178
00:08:40,880 --> 00:08:43,860
We see router 6 is up as well.

179
00:08:43,860 --> 00:08:46,443
It also wouldn't hurt to
verify on the route reflector,

180
00:08:46,443 --> 00:08:48,110
just so we can see
what that looks like.

181
00:08:48,110 --> 00:08:49,640
Of course, we know
if one side's up,

182
00:08:49,640 --> 00:08:51,330
the other side's up as well.

183
00:08:51,330 --> 00:08:55,610
But just to see what
the command looks like,

184
00:08:55,610 --> 00:08:57,650
we see that here on
the route reflector.

185
00:08:57,650 --> 00:09:00,410
It has neighborships for
the link-state address

186
00:09:00,410 --> 00:09:04,220
family to routers 1,
2, 5, and 6, which is

187
00:09:04,220 --> 00:09:06,000
exactly what we're looking for.

188
00:09:06,000 --> 00:09:08,000
We can also see
that it's already

189
00:09:08,000 --> 00:09:12,120
received some prefixes from
each of these devices as well.

190
00:09:12,120 --> 00:09:14,840
We'll get to that
in a little bit.

191
00:09:14,840 --> 00:09:18,580
Now, what we haven't done yet
is configure our address family

192
00:09:18,580 --> 00:09:21,430
IPv4 on router 7.

193
00:09:21,430 --> 00:09:23,740
So let's go configure
router 7 to just be

194
00:09:23,740 --> 00:09:27,530
a standard IPv4 client for BGP.

195
00:09:27,530 --> 00:09:30,430
So again, we'll
do router BGP 100.

196
00:09:30,430 --> 00:09:32,830
We'll set our router ID.

197
00:09:32,830 --> 00:09:34,720
We'll configure our neighbor.

198
00:09:34,720 --> 00:09:36,850
So we put in the remote AS.

199
00:09:36,850 --> 00:09:40,240
And we'll say, update
source loopback zero.

200
00:09:40,240 --> 00:09:42,850
We can see that neighborship
already came up.

201
00:09:42,850 --> 00:09:47,230
So is the update source loopback
zero strictly necessary?

202
00:09:47,230 --> 00:09:50,270
No, but that's a whole
other conversation.

203
00:09:50,270 --> 00:09:52,450
So let's just put it
in for good measure,

204
00:09:52,450 --> 00:09:55,340
even though we see the
neighborship was already up.

205
00:09:55,340 --> 00:09:58,180
So let's go ahead and
exit configuration.

206
00:09:58,180 --> 00:10:00,960
So now that we have
BGP up and running,

207
00:10:00,960 --> 00:10:04,060
where we need it with the
correct address families.

208
00:10:04,060 --> 00:10:06,840
So we have link-state
address family running

209
00:10:06,840 --> 00:10:10,890
towards routers 1, 2, 5, and 6.

210
00:10:10,890 --> 00:10:16,950
And we have IPv4 address family
running with routers 7 and 8.

211
00:10:16,950 --> 00:10:20,370
Now, let's go ahead
and configure PCEP.

212
00:10:20,370 --> 00:10:23,190
Once again, we'll start
on the route reflector,

213
00:10:23,190 --> 00:10:25,950
since that's going
to be the PCE.

214
00:10:25,950 --> 00:10:29,130
So this is actually a
very simple configuration.

215
00:10:29,130 --> 00:10:33,900
All we do is type PCE to
go into PCE configuration.

216
00:10:33,900 --> 00:10:37,350
Tell it what address
to actually run on.

217
00:10:37,350 --> 00:10:40,120
We want it to run on
its loopback interface.

218
00:10:40,120 --> 00:10:43,230
So it's going to be 10.11.11.11.

219
00:10:43,230 --> 00:10:45,550
And simply commit the changes.

220
00:10:45,550 --> 00:10:52,080
Now, we can do a show PCE
IPv4 peers or rather peer.

221
00:10:52,080 --> 00:10:54,310
And we can see that
as of right now,

222
00:10:54,310 --> 00:10:56,890
there are no neighborships,
which, of course, makes sense.

223
00:10:56,890 --> 00:10:59,240
We haven't configured
the other routers yet.

224
00:10:59,240 --> 00:11:02,890
So the PE routers are
going to be the PCCs.

225
00:11:02,890 --> 00:11:05,890
So let's go over and
configure router 7.

226
00:11:05,890 --> 00:11:11,740
So our first command is going
to be MPLS traffic engineering

227
00:11:11,740 --> 00:11:14,530
PCC to tell it it's a client.

228
00:11:14,530 --> 00:11:18,110
And then tell it its peer
or its server, if you will,

229
00:11:18,110 --> 00:11:20,860
is 10.11.11.11.

230
00:11:20,860 --> 00:11:23,380
Then we have to tell
it what to report.

231
00:11:23,380 --> 00:11:30,970
So we'll say MPLS traffic
engineering PCC report all.

232
00:11:30,970 --> 00:11:33,260
We'll exit our configuration.

233
00:11:33,260 --> 00:11:36,010
And let's take a look
at some show commands.

234
00:11:36,010 --> 00:11:39,130
Let's do a show PCE client peer.

235
00:11:39,130 --> 00:11:43,990
We see that as of right
now, our peer 10.11.11.11

236
00:11:43,990 --> 00:11:45,530
is currently up.

237
00:11:45,530 --> 00:11:47,260
So this looks good.

238
00:11:47,260 --> 00:11:49,420
If we wanted some more
detail, you can simply

239
00:11:49,420 --> 00:11:51,130
add detail to the end of this.

240
00:11:51,130 --> 00:11:53,270
As you can see,
this takes a moment.

241
00:11:53,270 --> 00:11:57,590
But it'll give us a lot more
information about that server.

242
00:11:57,590 --> 00:11:59,770
So again, we see
our peer address,

243
00:11:59,770 --> 00:12:02,590
that it's chosen
it as the best PCE.

244
00:12:02,590 --> 00:12:04,210
It is currently up.

245
00:12:04,210 --> 00:12:06,740
Of course, we see how
long it's been up for.

246
00:12:06,740 --> 00:12:10,660
And again, a bunch of statistics
as far as peer keepalives.

247
00:12:10,660 --> 00:12:13,660
And statistics as far
as types of messages

248
00:12:13,660 --> 00:12:15,910
that have been
sent and received.

249
00:12:15,910 --> 00:12:20,620
Show PCE client LSP is another
good command to look at.

250
00:12:20,620 --> 00:12:24,850
Although, as of right now, we
don't have any LSPs or label

251
00:12:24,850 --> 00:12:27,020
switch paths up and running.

252
00:12:27,020 --> 00:12:29,680
So we'll review this,
again, once we've

253
00:12:29,680 --> 00:12:31,850
done some policies and tunnels.

254
00:12:31,850 --> 00:12:35,362
So next up would be
to configure router 8.

255
00:12:35,362 --> 00:12:37,450
Router 8 is the
same configuration.

256
00:12:37,450 --> 00:12:39,000
So we'll just paste it in.

257
00:12:39,000 --> 00:12:41,640
And of course, we see
the console message

258
00:12:41,640 --> 00:12:43,050
that the server came up.

259
00:12:43,050 --> 00:12:45,510
But let's verify it anyway.

260
00:12:45,510 --> 00:12:48,030
We'll just do a show
PCE client peer.

261
00:12:48,030 --> 00:12:53,460
And yes, we see the
10.11.11.11 is, in fact, up.

262
00:12:53,460 --> 00:12:55,980
Of course, we can
also do verification

263
00:12:55,980 --> 00:12:59,400
from the route
reflector or the PCE.

264
00:12:59,400 --> 00:13:04,410
So let's start with a show
PCE peer, which is actually

265
00:13:04,410 --> 00:13:07,170
show PCE IPv4 peer.

266
00:13:07,170 --> 00:13:11,190
And what we see is that our
two neighbors, router 7 and 8

267
00:13:11,190 --> 00:13:13,560
are, in fact, both up.

268
00:13:13,560 --> 00:13:19,770
Let's do a show
PCE IPv4 topology.

269
00:13:19,770 --> 00:13:21,930
And let's start with a summary.

270
00:13:21,930 --> 00:13:25,200
Here, we see all the information
it's learned about the summary

271
00:13:25,200 --> 00:13:26,100
so far.

272
00:13:26,100 --> 00:13:30,210
How many nodes are in
the topologies, prefixes.

273
00:13:30,210 --> 00:13:32,640
We can see all of
this information

274
00:13:32,640 --> 00:13:35,230
that it's learning
about our environment.

275
00:13:35,230 --> 00:13:39,020
Rather than summary, we could
also ask for a particular node.

276
00:13:39,020 --> 00:13:42,220
And notice, it's learning all
of the traffic engineering

277
00:13:42,220 --> 00:13:45,820
information about
each of these nodes.

278
00:13:45,820 --> 00:13:47,530
Importantly, it's
learning things

279
00:13:47,530 --> 00:13:51,490
like the metric, the TE values,
the latency, the bandwidth,

280
00:13:51,490 --> 00:13:53,590
reservable and so on.

281
00:13:53,590 --> 00:13:57,550
All of that critical information
for traffic engineering.

282
00:13:57,550 --> 00:14:00,710
We should be getting this
from router 8 as well.

283
00:14:00,710 --> 00:14:02,930
We can see here that we are.

284
00:14:02,930 --> 00:14:05,080
And we should be getting
it from the other routers

285
00:14:05,080 --> 00:14:07,780
as well because the router
is in the middle also

286
00:14:07,780 --> 00:14:09,310
need to report information.

287
00:14:09,310 --> 00:14:11,440
And we can see that
we're getting information

288
00:14:11,440 --> 00:14:14,990
about node 10.2.2.2 as well.

289
00:14:14,990 --> 00:14:17,560
So we should have information
about all the devices

290
00:14:17,560 --> 00:14:18,910
in our topology.

291
00:14:18,910 --> 00:14:20,770
And as we can see, we do.

292
00:14:20,770 --> 00:14:23,900
So this is working as it should.

293
00:14:23,900 --> 00:14:29,510
In this video, we set up BGP
link-state address family

294
00:14:29,510 --> 00:14:35,030
between routers 1, 2, 5, and
6 and our route reflector.

295
00:14:35,030 --> 00:14:39,410
And we set up BGP for
address family IPv4

296
00:14:39,410 --> 00:14:44,030
between our PE devices,
routers 7 and 8.

297
00:14:44,030 --> 00:14:49,820
Then we set up PCEP between the
route reflector and our PEs,

298
00:14:49,820 --> 00:14:53,540
again, router 7 and 8,
to exchange the traffic

299
00:14:53,540 --> 00:14:57,080
engineering information with
the route reflector acting

300
00:14:57,080 --> 00:14:58,700
as the PCE.

301
00:14:58,700 --> 00:15:02,720
Now, all of this working
doesn't do us any good,

302
00:15:02,720 --> 00:15:06,560
unless we actually build
traffic engineering policies

303
00:15:06,560 --> 00:15:07,940
and tunnels.

304
00:15:07,940 --> 00:15:09,230
And that's right.

305
00:15:09,230 --> 00:15:11,100
That's what we're
going to do next.

306
00:15:11,100 --> 00:15:14,570
Until then, I hope this has
been informative for you.

307
00:15:14,570 --> 00:15:17,680
And I'd like to thank
you for viewing.

308
00:15:17,680 --> 00:15:21,000