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

2
00:00:03,451 --> 00:00:07,890

3
00:00:07,890 --> 00:00:10,140
So now that all of
the other components

4
00:00:10,140 --> 00:00:13,200
have been configured
and verified,

5
00:00:13,200 --> 00:00:16,290
it's now finally time
to actually configure

6
00:00:16,290 --> 00:00:20,160
our segment routing TE
policies and tunnels.

7
00:00:20,160 --> 00:00:21,960
That's, of course,
what we're going to be

8
00:00:21,960 --> 00:00:24,220
doing in this demonstration.

9
00:00:24,220 --> 00:00:28,110
So that said, let's take a
look at our topology, just

10
00:00:28,110 --> 00:00:31,020
so we know what we're going to
be building on which devices.

11
00:00:31,020 --> 00:00:34,020
And then, of course, we'll
jump into the command line

12
00:00:34,020 --> 00:00:39,390
and get all of this
configured and operational.

13
00:00:39,390 --> 00:00:41,490
So of course, one
final reminder,

14
00:00:41,490 --> 00:00:45,350
we will, of course, be finishing
up here on MPLS Topology 5

15
00:00:45,350 --> 00:00:47,420
because this is where
everything is configured.

16
00:00:47,420 --> 00:00:48,837
But specifically,
what we're going

17
00:00:48,837 --> 00:00:51,710
to be doing in this
demonstration is

18
00:00:51,710 --> 00:00:56,570
we have a network on router
7 and a network on router 8.

19
00:00:56,570 --> 00:01:04,129
Their IP addresses are hundreds
100.7.7.7 and 100.8.8.8.

20
00:01:04,129 --> 00:01:06,050
And we'll be
configuring our segment

21
00:01:06,050 --> 00:01:08,750
routing TE tunnel
so that these two

22
00:01:08,750 --> 00:01:11,940
networks are reachable
through our environment.

23
00:01:11,940 --> 00:01:14,760
So let's go ahead and
jump in and get started.

24
00:01:14,760 --> 00:01:19,030
We'll just begin our
configuration on router 7.

25
00:01:19,030 --> 00:01:21,850
So let's begin our
configuration by setting

26
00:01:21,850 --> 00:01:24,530
a few of our parameters
for the tunnel.

27
00:01:24,530 --> 00:01:28,720
So we'll start with MPLS
traffic engineering.

28
00:01:28,720 --> 00:01:31,810
And we're going to build
this as an auto-tunnel.

29
00:01:31,810 --> 00:01:33,640
It's going to be point to point.

30
00:01:33,640 --> 00:01:36,520
And we're going to set a
configuration parameter here,

31
00:01:36,520 --> 00:01:38,860
where it's going to
be unnumbered off

32
00:01:38,860 --> 00:01:41,710
of the interface loopback 0.

33
00:01:41,710 --> 00:01:44,680
So it's going to pull the
address for the tunnel off

34
00:01:44,680 --> 00:01:46,300
of loopback 0.

35
00:01:46,300 --> 00:01:50,210
The other thing we want to
configure is the tunnel number.

36
00:01:50,210 --> 00:01:53,320
So we'll set the minimum
number to, say, 1,000.

37
00:01:53,320 --> 00:01:55,390
That should be the
one it uses first.

38
00:01:55,390 --> 00:01:57,700
And then we'll say
the max is like 1,900.

39
00:01:57,700 --> 00:01:58,450
It doesn't matter.

40
00:01:58,450 --> 00:02:01,370
Of course, we're going to
get nowhere near that number.

41
00:02:01,370 --> 00:02:05,290
So that configures some of
the parameters for our tunnel.

42
00:02:05,290 --> 00:02:09,800
The next thing we want to do
is create a list of attributes.

43
00:02:09,800 --> 00:02:16,810
So we do this by saying mpls
traffic engineering lsp.

44
00:02:16,810 --> 00:02:19,370
And then we're going to
create an attribute list.

45
00:02:19,370 --> 00:02:23,880
And we'll call this LL_TRAFFIC.

46
00:02:23,880 --> 00:02:25,920
Now, what do we want
to configure here?

47
00:02:25,920 --> 00:02:28,190
Well, let's first tell
it how much bandwidth

48
00:02:28,190 --> 00:02:29,280
it's going to use.

49
00:02:29,280 --> 00:02:31,790
So we'll say the
bandwidth is 1,000.

50
00:02:31,790 --> 00:02:34,100
We'll also set the priority.

51
00:02:34,100 --> 00:02:39,590
We'll set the setup and the
hold priority, both, to say 5.

52
00:02:39,590 --> 00:02:42,740
For the path
selection, let's set it

53
00:02:42,740 --> 00:02:44,930
to the traffic
engineering metric.

54
00:02:44,930 --> 00:02:47,840
And we'll tell it to use PCE.

55
00:02:47,840 --> 00:02:50,570
That should take care
of our attributes.

56
00:02:50,570 --> 00:02:53,190
Now, this next
command is optional.

57
00:02:53,190 --> 00:02:54,980
But it will make some
of our show commands

58
00:02:54,980 --> 00:02:56,670
a little bit easier to look at.

59
00:02:56,670 --> 00:03:00,140
So we'll just put in ip
bgp-community new-format.

60
00:03:00,140 --> 00:03:03,650
Again, that's just a display
command for BGP communities.

61
00:03:03,650 --> 00:03:05,540
Because we're going
to use communities

62
00:03:05,540 --> 00:03:07,940
to influence which
routes we're going

63
00:03:07,940 --> 00:03:09,860
to put these attributes on.

64
00:03:09,860 --> 00:03:13,040
Now, in order to do that, we are
going to need a community list,

65
00:03:13,040 --> 00:03:15,890
standard community
list will be fine.

66
00:03:15,890 --> 00:03:20,110
We'll call this CL_LL_TRAFFIC.

67
00:03:20,110 --> 00:03:24,850
And we'll say that it's going
to permit 100 colon 10, just

68
00:03:24,850 --> 00:03:27,010
to pick a community
string to use.

69
00:03:27,010 --> 00:03:28,780
Next, we're going
to need our route

70
00:03:28,780 --> 00:03:33,650
maps for our inbound and
outbound BGP updates.

71
00:03:33,650 --> 00:03:37,690
So first, we'll create a
route map called IPv4_IN.

72
00:03:37,690 --> 00:03:41,390
We'll say to match community
and put in our community list.

73
00:03:41,390 --> 00:03:44,020
So this will only be
applied to traffic that

74
00:03:44,020 --> 00:03:46,940
has the 100 colon 10 on it.

75
00:03:46,940 --> 00:03:49,300
And what we want to
do with that traffic

76
00:03:49,300 --> 00:03:52,540
is we want to apply
the attribute set

77
00:03:52,540 --> 00:03:54,560
that we created earlier.

78
00:03:54,560 --> 00:03:57,490
So this is going to apply
those tunnel attributes

79
00:03:57,490 --> 00:04:01,870
to any routes coming in
with this community string.

80
00:04:01,870 --> 00:04:06,460
For our outbound route map,
which we'll just call OUT,

81
00:04:06,460 --> 00:04:10,060
for this one, all we want
to do is set the community

82
00:04:10,060 --> 00:04:13,510
so that this triggers the
policy when our routes get

83
00:04:13,510 --> 00:04:14,800
to the other side.

84
00:04:14,800 --> 00:04:19,459
Because router 8 is going to be
a mirror of this configuration.

85
00:04:19,459 --> 00:04:23,780
So we're going to set
community to 100 colon 10.

86
00:04:23,780 --> 00:04:27,290
Next, of course, we're going
to have to configure our BGP

87
00:04:27,290 --> 00:04:28,500
parameters.

88
00:04:28,500 --> 00:04:31,013
So we'll say router BGP 100.

89
00:04:31,013 --> 00:04:32,930
Now, the first thing
we're going to have to do

90
00:04:32,930 --> 00:04:35,820
is put our own network into BGP.

91
00:04:35,820 --> 00:04:39,290
So it's 100 colon
7 colon 7 colon 0.

92
00:04:39,290 --> 00:04:42,030
It's actually a slash 24.

93
00:04:42,030 --> 00:04:47,830
So we'll say that the
mask is 255.255.255.0.

94
00:04:47,830 --> 00:04:49,930
And we'll run this
route injection

95
00:04:49,930 --> 00:04:53,980
through the route map we created
for our outbound updates.

96
00:04:53,980 --> 00:04:56,380
Now, since we're going
to be using communities,

97
00:04:56,380 --> 00:04:59,230
we're also going to have to
configure towards the route

98
00:04:59,230 --> 00:05:02,990
reflector to actually
send communities.

99
00:05:02,990 --> 00:05:04,420
And we'll turn on both.

100
00:05:04,420 --> 00:05:07,960
I normally turn on both standard
and extended communities,

101
00:05:07,960 --> 00:05:09,940
if I'm going to
enable this feature.

102
00:05:09,940 --> 00:05:13,480
Although right now, we're only
using standard communities.

103
00:05:13,480 --> 00:05:16,970
Also, towards
neighbor 10.11.11.11,

104
00:05:16,970 --> 00:05:20,470
we need to apply our
inbound route map.

105
00:05:20,470 --> 00:05:24,790
So we'll say route map IPv4_IN.

106
00:05:24,790 --> 00:05:28,490
And again, we're going to apply
that in the inbound direction.

107
00:05:28,490 --> 00:05:31,730
Let's exit configuration.

108
00:05:31,730 --> 00:05:34,300
So now, we have to configure
essentially the same things

109
00:05:34,300 --> 00:05:35,560
over on router 8.

110
00:05:35,560 --> 00:05:38,490
So let's jump over there.

111
00:05:38,490 --> 00:05:40,830
So let's go into
configuration mode.

112
00:05:40,830 --> 00:05:43,320
Now, these are a lot
of commands to put in,

113
00:05:43,320 --> 00:05:45,080
so we will copy and paste them.

114
00:05:45,080 --> 00:05:47,600
But we will do it piece
by piece so we can talk

115
00:05:47,600 --> 00:05:49,410
about what we're putting in.

116
00:05:49,410 --> 00:05:52,820
So the first piece are the
two commands that set up

117
00:05:52,820 --> 00:05:55,430
the parameters for the tunnels.

118
00:05:55,430 --> 00:05:59,420
The next piece is to
define the attributes.

119
00:05:59,420 --> 00:06:01,960
Next, we'll configure
our new format

120
00:06:01,960 --> 00:06:04,630
and configure our
community list.

121
00:06:04,630 --> 00:06:07,830
Next, we'll create
both of our route maps.

122
00:06:07,830 --> 00:06:10,750
And then finally,
we'll configure BGP.

123
00:06:10,750 --> 00:06:13,230
So now that both sides
are configured, let's

124
00:06:13,230 --> 00:06:14,760
do some verification.

125
00:06:14,760 --> 00:06:21,030
Let's do a show mpls
traffic engineering tunnels.

126
00:06:21,030 --> 00:06:24,780
And we can see that we have
a point-to-point tunnel going

127
00:06:24,780 --> 00:06:30,540
from router 8 to the
destination of 10.7.7.7.

128
00:06:30,540 --> 00:06:32,940
This is tunnel 1,000.

129
00:06:32,940 --> 00:06:34,920
Status is admin up.

130
00:06:34,920 --> 00:06:36,420
It's operationally up.

131
00:06:36,420 --> 00:06:37,830
The path is valid.

132
00:06:37,830 --> 00:06:39,570
The signaling is connected.

133
00:06:39,570 --> 00:06:43,410
And it's using path
option 1 segment routing,

134
00:06:43,410 --> 00:06:45,690
coming from PCE.

135
00:06:45,690 --> 00:06:47,940
So these are, of
course, good indicators

136
00:06:47,940 --> 00:06:51,490
that our PCE is working, our
segment routing is working.

137
00:06:51,490 --> 00:06:54,490
And if we look under our
configuration parameters,

138
00:06:54,490 --> 00:06:57,240
notice that it has all of those
things that we configured.

139
00:06:57,240 --> 00:06:59,640
It's got our bandwidth
in kilobits per second.

140
00:06:59,640 --> 00:07:01,080
It's got our priorities.

141
00:07:01,080 --> 00:07:04,600
It's using the metric type
of TE from the interface.

142
00:07:04,600 --> 00:07:06,940
So all of this looks good.

143
00:07:06,940 --> 00:07:14,410
We can also, by the way, add
the command tunnel 1000 detail.

144
00:07:14,410 --> 00:07:18,100
And this would give us a way
to look at a specific tunnel.

145
00:07:18,100 --> 00:07:20,380
And again, there's a
lot more information

146
00:07:20,380 --> 00:07:22,600
here when you do detail.

147
00:07:22,600 --> 00:07:25,690
We, of course, don't have to
look at all of this right now.

148
00:07:25,690 --> 00:07:29,570
But there's a lot of information
available if we need it.

149
00:07:29,570 --> 00:07:32,890
And one really interesting
piece is down here

150
00:07:32,890 --> 00:07:34,870
at the bottom, where
we can actually

151
00:07:34,870 --> 00:07:36,760
see the segment
routing path that it's

152
00:07:36,760 --> 00:07:41,250
using, where it's going
to router 5, from 5 to 3,

153
00:07:41,250 --> 00:07:43,270
and then over to 7.

154
00:07:43,270 --> 00:07:45,130
So we can actually
see the segments

155
00:07:45,130 --> 00:07:48,640
it's using as it goes
between the domains.

156
00:07:48,640 --> 00:07:52,520
We should be able to see this
from the router 7 side as well.

157
00:07:52,520 --> 00:07:55,360
So on router 7, if we
look at just the tunnels,

158
00:07:55,360 --> 00:07:58,000
once again, we see
this same information,

159
00:07:58,000 --> 00:08:01,180
that going to the
destination 10.8.8.8

160
00:08:01,180 --> 00:08:03,730
is up, operational, and valid.

161
00:08:03,730 --> 00:08:06,440
We see all of our
parameters configured here.

162
00:08:06,440 --> 00:08:08,270
So this all looks good.

163
00:08:08,270 --> 00:08:11,390
And again, we can look at
the detail for the tunnel.

164
00:08:11,390 --> 00:08:13,000
And here, we can
see the segments

165
00:08:13,000 --> 00:08:16,390
that it's going through,
from router 7's perspective,

166
00:08:16,390 --> 00:08:18,400
to get to the destination.

167
00:08:18,400 --> 00:08:21,950
Of course, we can also verify
this on the PCE itself.

168
00:08:21,950 --> 00:08:24,140
So let's go up to
the route reflector.

169
00:08:24,140 --> 00:08:27,250
So let's do a show PCE LSP.

170
00:08:27,250 --> 00:08:29,560
First thing we see is
that we do have a tunnel

171
00:08:29,560 --> 00:08:35,230
1,000, one going from router
7 to router 8 and one going

172
00:08:35,230 --> 00:08:37,390
from router 8 to router 7.

173
00:08:37,390 --> 00:08:41,110
We can see that both of them
are admin up and operationally

174
00:08:41,110 --> 00:08:43,809
active, that they're
using segment routing.

175
00:08:43,809 --> 00:08:46,090
And we see the
binding SID that's

176
00:08:46,090 --> 00:08:49,670
being used to get traffic
to go to the other side.

177
00:08:49,670 --> 00:08:52,030
Now, we do have one
more small problem

178
00:08:52,030 --> 00:08:54,050
that we actually need to fix.

179
00:08:54,050 --> 00:08:56,170
Let's go over to router 7.

180
00:08:56,170 --> 00:08:59,470
And the problem here
is, if I do a show BGP,

181
00:08:59,470 --> 00:09:04,970
we're getting that route
to the 100.8.8.0/24.

182
00:09:04,970 --> 00:09:07,060
However, it's not valid.

183
00:09:07,060 --> 00:09:11,170
And the problem is, if I ask
for detail on that network,

184
00:09:11,170 --> 00:09:14,980
it's telling us that the
next hop is inaccessible.

185
00:09:14,980 --> 00:09:16,990
Of course, that's
because if I do a show IP

186
00:09:16,990 --> 00:09:21,130
route for 10.8.8.8, we
have no idea where it is.

187
00:09:21,130 --> 00:09:23,120
It's in another routing domain.

188
00:09:23,120 --> 00:09:24,580
I don't know where that is.

189
00:09:24,580 --> 00:09:27,850
Now, the interesting thing
is, all we need to do

190
00:09:27,850 --> 00:09:31,690
is trick the router
to actually just send

191
00:09:31,690 --> 00:09:33,790
the traffic to the tunnel.

192
00:09:33,790 --> 00:09:37,810
Because notice, it has
the binding SID on it.

193
00:09:37,810 --> 00:09:41,360
It actually knows what
to do with this traffic,

194
00:09:41,360 --> 00:09:44,620
but BGP won't do it because
it thinks the next hop is

195
00:09:44,620 --> 00:09:46,870
unreachable or inaccessible.

196
00:09:46,870 --> 00:09:50,470
So yes, we can in fact trick it.

197
00:09:50,470 --> 00:09:54,730
We'll put in IP
route to 10.8.8.8.

198
00:09:54,730 --> 00:09:57,860
And we'll simply
direct that to null0.

199
00:09:57,860 --> 00:10:00,110
Now, we'll have to do the
exact same thing on router 8

200
00:10:00,110 --> 00:10:02,490
because it'll be having
the same problem.

201
00:10:02,490 --> 00:10:05,510
So again, if we do show
BGP, just so you can see it,

202
00:10:05,510 --> 00:10:08,660
again, there's the 100.7.7.0.

203
00:10:08,660 --> 00:10:11,580
And it's not selected as best.

204
00:10:11,580 --> 00:10:13,910
So we'll go into
configuration mode

205
00:10:13,910 --> 00:10:16,350
and configure our static route.

206
00:10:16,350 --> 00:10:18,830
So let's go back
over to router 7.

207
00:10:18,830 --> 00:10:21,770
Hopefully, that gave BGP
enough time to converge.

208
00:10:21,770 --> 00:10:25,340
We see that now, that
path is selected as best.

209
00:10:25,340 --> 00:10:29,430
Let's verify router 8 as well
before we test the data plane.

210
00:10:29,430 --> 00:10:33,080
We see that router 8 is also
listing the route as valid now.

211
00:10:33,080 --> 00:10:36,000
So let's test some traffic.

212
00:10:36,000 --> 00:10:38,180
So here on router 7,
let's trace to that

213
00:10:38,180 --> 00:10:43,920
100.8.8.8, sourcing it from
our loopback 100 interface.

214
00:10:43,920 --> 00:10:46,220
So here, we can see
our labels being

215
00:10:46,220 --> 00:10:48,150
applied as they should be.

216
00:10:48,150 --> 00:10:51,000
And we see that we
reached our destination.

217
00:10:51,000 --> 00:10:54,140
Now, it is OK for some
of the interim devices

218
00:10:54,140 --> 00:10:56,810
to not necessarily
respond to the trace

219
00:10:56,810 --> 00:11:00,180
because they may not know how to
get back to the source address

220
00:11:00,180 --> 00:11:02,430
that these packets
are originated from.

221
00:11:02,430 --> 00:11:04,890
But let's verify that our
tunnel the other direction

222
00:11:04,890 --> 00:11:06,870
is working as well.

223
00:11:06,870 --> 00:11:10,280
So again, we'll trace
back to router 7.

224
00:11:10,280 --> 00:11:12,600
So again, we see
that this is working.

225
00:11:12,600 --> 00:11:16,460
So now, we have our traffic
engineering tunnel operating

226
00:11:16,460 --> 00:11:20,480
in both directions, set up
between two different domains,

227
00:11:20,480 --> 00:11:23,980
using a PCE.

228
00:11:23,980 --> 00:11:27,640
In this video, we saw how
to configure our tunnel

229
00:11:27,640 --> 00:11:31,300
parameters, create
an attribute set,

230
00:11:31,300 --> 00:11:34,600
create our route maps to
apply those attributes

231
00:11:34,600 --> 00:11:36,430
to incoming routes.

232
00:11:36,430 --> 00:11:40,060
We filtered that, of course,
also using community strings.

233
00:11:40,060 --> 00:11:42,640
But then ultimately,
we saw how this

234
00:11:42,640 --> 00:11:45,610
builds the tunnel using PCE.

235
00:11:45,610 --> 00:11:49,090
And we ended up with a
fully functional data plane,

236
00:11:49,090 --> 00:11:53,330
going both directions, using
our traffic engineering tunnel.

237
00:11:53,330 --> 00:11:55,540
So that concludes
everything that we

238
00:11:55,540 --> 00:11:57,890
need to learn in this skill.

239
00:11:57,890 --> 00:12:00,430
That means that
all we have left is

240
00:12:00,430 --> 00:12:02,920
a review in the form of a quiz.

241
00:12:02,920 --> 00:12:05,810
And of course, that's what
we're going to do next.

242
00:12:05,810 --> 00:12:09,280
Until then, I hope this has
been informative for you.

243
00:12:09,280 --> 00:12:12,390
And I'd like to thank
you for viewing.

244
00:12:12,390 --> 00:12:16,000