WEBVTT

1
00:00.000 --> 00:04.120
So now that we have a couple of segments connected to this tier one gateway,

2
00:04.120 --> 00:07.060
let's go ahead and add a VM to each of those.

3
00:07.060 --> 00:08.460
So here in the vSphere client,

4
00:08.460 --> 00:10.500
let's go ahead and click on the VM and templates view,

5
00:10.500 --> 00:12.460
and let's go down to VMs for testing,

6
00:12.460 --> 00:15.360
and these guys are D should be client.

7
00:15.360 --> 00:17.040
So Mint 10, let's take that one,

8
00:17.040 --> 00:19.180
we'll right-click, click on Edit Settings,

9
00:19.180 --> 00:21.860
and let's place that over on segment 10.

10
00:21.860 --> 00:23.880
So we'll browse for the network adapter placement,

11
00:23.880 --> 00:26.900
and let's place that on segment 10, click on OK,

12
00:26.900 --> 00:29.680
click on OK, and then we'll go ahead and power that up.

13
00:29.680 --> 00:31.560
And let's do the same thing for Mint 20,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:29.680 --> 00:31.560
And let's do the same thing for Mint 20,

14
00:31.560 --> 00:33.000
but we'll put it on segment 20.

15
00:33.000 --> 00:35.960
So we'll right-click on Mint 20, click on Edit Settings,

16
00:35.960 --> 00:38.920
from the details for the network adapter, we use the dropdown,

17
00:38.920 --> 00:40.440
we'll browse for the port group to use,

18
00:40.440 --> 00:44.800
we'll choose Blue Segment 20, click on OK, click on OK,

19
00:44.800 --> 00:46.680
and then power that up as well.

20
00:46.680 --> 00:49.000
And then we'll also open up remote consoles to each of those.

21
00:49.000 --> 00:52.320
So let me go ahead and launch a remote console to Mint 10,

22
00:52.320 --> 00:55.600
and also open up a remote console to Mint 20.

23
00:55.600 --> 00:57.400
So if we go back to our topology view here,

24
00:57.400 --> 01:00.720
and we click on Refresh right there in the NSX Manager,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
00:57.400 --> 01:00.720
and we click on Refresh right there in the NSX Manager,

25
01:00.720 --> 01:02.880
this should now show us that we have those two VMs

26
01:02.880 --> 01:04.240
right there, which we do.

27
01:04.240 --> 01:07.400
We've got Mint 10 right here on segment 10,

28
01:07.400 --> 01:10.960
and we have Mint 20 sitting here on segment 20.

29
01:10.960 --> 01:12.840
And because we have DHCP services enabled

30
01:12.840 --> 01:14.880
on both of those segments, both of these clients

31
01:14.880 --> 01:17.800
should be able to get IP addresses in the correct submits.

32
01:17.800 --> 01:19.040
So let's verify that together.

33
01:19.040 --> 01:20.520
Here is Mint 10.

34
01:20.520 --> 01:21.960
Let me just confirm I'm on the right VM.

35
01:21.960 --> 01:23.280
I am, there's Mint 10.

36
01:23.280 --> 01:26.240
We'll go to a command prompt, and we'll do an IF config,

37
01:26.240 --> 01:29.360
and it has the IP address of 10.0.183.

38
01:29.360 --> 01:31.880
Fantastic, let me move that over to the right a little bit,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:29.360 --> 01:31.880
Fantastic, let me move that over to the right a little bit,

39
01:31.880 --> 01:34.000
and let's bring in Mint 20.

40
01:34.000 --> 01:36.120
So here's Mint 20, and so on Mint 20,

41
01:36.120 --> 01:38.960
let's go to a command prompt to do an IF config,

42
01:38.960 --> 01:42.920
and we are at 10.20.0.165, that looks great.

43
01:42.920 --> 01:47.920
So Mint 10 is at 10.10.0.183, Mint 20 is at 10.20.0.165,

44
01:47.920 --> 01:50.400
and let's verify they can get out to the internet.

45
01:50.400 --> 01:54.760
So I ping to www.google.com press enter.

46
01:54.760 --> 01:56.360
(laughs)

47
01:56.360 --> 01:59.040
And now we start the troubleshooting portion of our show.

48
01:59.040 --> 02:02.880
That is not flying, so DNS resolution is failing,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
01:59.040 --> 02:02.880
That is not flying, so DNS resolution is failing,

49
02:02.880 --> 02:07.880
and let's just do a ping out to 8888, and that's failing.

50
02:07.880 --> 02:09.880
Now let's do a trace path, we'll do a dash M

51
02:09.880 --> 02:12.960
for no name resolution out to 8888,

52
02:12.960 --> 02:13.960
and let's see how far we get.

53
02:13.960 --> 02:16.720
Okay, so we're making it to our default gateway,

54
02:16.720 --> 02:18.720
and then we're forwarding it up over the router

55
02:18.720 --> 02:21.280
to router link between our tier one gateway

56
02:21.280 --> 02:23.600
and the blue VRF, but it looks like past that.

57
02:23.600 --> 02:25.800
We are not getting to the external network,

58
02:25.800 --> 02:27.280
and I don't think it's a routing problem

59
02:27.280 --> 02:28.960
because we have a default route.

60
02:28.960 --> 02:30.440
Let's just double check real quick.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
02:28.960 --> 02:30.440
Let's just double check real quick.

61
02:30.440 --> 02:32.680
So here on edge one, let's do a gate gateways,

62
02:32.680 --> 02:34.960
just to verify the VRF number for a blue VRF,

63
02:34.960 --> 02:38.440
so it's 11, let's do a VRF space 11,

64
02:38.440 --> 02:40.480
the prop changes to represent where we are,

65
02:40.480 --> 02:42.640
and we'll type in get route and press enter,

66
02:42.640 --> 02:45.300
and we do have a default, so that part looks good.

67
02:45.300 --> 02:47.600
Oh, I know what we don't have, we don't have NAT.

68
02:47.600 --> 02:48.680
(laughs)

69
02:48.680 --> 02:50.160
Let's take a look at our topology.

70
02:50.160 --> 02:52.840
So in our topology, if this is Mint 10 right here,

71
02:52.840 --> 02:55.440
and it's forwarding traffic to its default gateway,

72
02:55.440 --> 02:57.400
and then it forwards it to the blue VRF,

73
02:57.400 --> 03:00.000
this blue VRF does have a default route
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
03:00.000 --> 03:02.040
with the next top of 23.1.2.1,

75
03:02.040 --> 03:05.160
however, what it doesn't have is NAT configures.

76
03:05.160 --> 03:07.040
So this external router right here,

77
03:07.040 --> 03:10.280
when it's receiving a packet from 10.10 anything,

78
03:10.280 --> 03:12.160
it has no clue on how to reach it,

79
03:12.160 --> 03:14.200
because we haven't set up dynamic routing, first of all,

80
03:14.200 --> 03:17.360
between this VRF and the external network.

81
03:17.360 --> 03:19.120
So if we wanted to, we could do BGP.

82
03:19.120 --> 03:20.720
So we could set up BGP

83
03:20.720 --> 03:23.120
between each of the tier zero VRF devices

84
03:23.120 --> 03:25.040
and an external BGP router,

85
03:25.040 --> 03:26.560
and that way we could dynamically exchange

86
03:26.560 --> 03:27.720
routing information.

87
03:27.720 --> 03:30.360
And currently as of NSX version 4.1,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
03:27.720 --> 03:30.360
And currently as of NSX version 4.1,

88
03:30.360 --> 03:33.240
if we are using a VRF tier zero gateway,

89
03:33.240 --> 03:35.300
it does support BGP, and that's great,

90
03:35.300 --> 03:37.160
but it doesn't support OSPF.

91
03:37.160 --> 03:38.560
However, from a routing perspective,

92
03:38.560 --> 03:40.840
we do have a default route that goes out this way,

93
03:40.840 --> 03:42.120
but the problem here is this device

94
03:42.120 --> 03:44.000
has no idea how to forward the traffic back.

95
03:44.000 --> 03:45.280
So let's do this.

96
03:45.280 --> 03:48.080
On this tier zero blue VRF,

97
03:48.080 --> 03:49.840
let's specify that we want to do NAT,

98
03:49.840 --> 03:51.400
and that way when we try to ping

99
03:51.400 --> 03:53.040
or reach this device right here,

100
03:53.040 --> 03:54.080
the external router,

101
03:54.080 --> 03:56.720
it'll look like we're coming from 23.1.2.

102
03:56.720 --> 03:59.800
So let's use .60 as a mapped address

103
03:59.800 --> 04:00.920
that we can use for any traffic
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
03:59.800 --> 04:00.920
that we can use for any traffic

104
04:00.920 --> 04:02.640
that's sourced from 10 anything.

105
04:02.640 --> 04:04.720
And that way when we try to ping this gateway,

106
04:04.720 --> 04:06.800
or when this gateway tries to return packets to us,

107
04:06.800 --> 04:08.880
it'll believe that the traffic is coming

108
04:08.880 --> 04:10.480
from the 23.12 network,

109
04:10.480 --> 04:13.240
and it can forward it down to our blue VRF tier zero gateway,

110
04:13.240 --> 04:14.480
who can then untranslate it,

111
04:14.480 --> 04:16.000
and then forward it back to our client.

112
04:16.000 --> 04:18.960
So let's implement NAT right here on our blue VRF.

113
04:18.960 --> 04:21.160
And for more details on configuring source

114
04:21.160 --> 04:22.440
or destination NAT,

115
04:22.440 --> 04:25.400
please check out our skill dedicated to that concept

116
04:25.400 --> 04:26.840
as part of NSX.

117
04:26.840 --> 04:28.600
So for now we're gonna reinforce that skill

118
04:28.600 --> 04:31.280
by simply adding network address translation right here
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
04:28.600 --> 04:31.280
by simply adding network address translation right here

119
04:31.280 --> 04:33.360
on our blue VRF tier zero gateway.

120
04:33.360 --> 04:35.480
So to implement network address translation

121
04:35.480 --> 04:37.880
for our blue VRF tier zero gateway,

122
04:37.880 --> 04:39.520
we're gonna click here on networking,

123
04:39.520 --> 04:41.680
and on the left under network services,

124
04:41.680 --> 04:42.840
we're gonna click on NAT.

125
04:42.840 --> 04:44.320
So with NAT selected,

126
04:44.320 --> 04:45.680
we're gonna click on add NAT roll,

127
04:45.680 --> 04:48.400
but I wanna make sure that we're on the right gateway.

128
04:48.400 --> 04:50.640
So we wanna do NAT on our blue VRF.

129
04:50.640 --> 04:52.120
So that is currently selected.

130
04:52.120 --> 04:53.880
I'll click on add NAT roll,

131
04:53.880 --> 04:57.440
and let's call this blue NAT.

132
04:57.440 --> 05:00.080
And for the type of NAT, we wanna do source NAT,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

132
04:57.440 --> 05:00.080
And for the type of NAT, we wanna do source NAT,

133
05:00.080 --> 05:02.520
and any traffic source from 10, anything.

134
05:02.520 --> 05:05.160
So I'll put 10.0.0.0/8.

135
05:05.160 --> 05:08.040
So any source IP addresses to be in with 10,

136
05:08.040 --> 05:10.160
we're gonna go ahead and translate them over to,

137
05:10.160 --> 05:12.680
let's use 23.1.2.60.

138
05:12.680 --> 05:13.520
And then furthermore,

139
05:13.520 --> 05:14.640
even though it's not required,

140
05:14.640 --> 05:17.040
we can specifically say which interfaces

141
05:17.040 --> 05:18.280
we wanna do the NAT on.

142
05:18.280 --> 05:20.800
So if we want to perform this on either edge,

143
05:20.800 --> 05:21.920
we can select all of them here,

144
05:21.920 --> 05:23.440
or you can actually leave it blank,

145
05:23.440 --> 05:25.640
and it would automatically do that by default,

146
05:25.640 --> 05:27.480
without selecting the specific interfaces.

147
05:27.480 --> 05:29.000
But to make it nice and tight and clean,

148
05:29.000 --> 05:31.080
I'm gonna go ahead and choose both those interfaces
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

148
05:29.000 --> 05:31.080
I'm gonna go ahead and choose both those interfaces

149
05:31.080 --> 05:34.360
for the NAT rule, click on apply, and let's check our work.

150
05:34.360 --> 05:37.920
So if traffic is coming in from the 10, anything,

151
05:37.920 --> 05:40.840
and it's being routed out of those two interfaces,

152
05:40.840 --> 05:41.880
we're gonna use source NAT,

153
05:41.880 --> 05:44.840
and swap out the source address of whatever it was coming in,

154
05:44.840 --> 05:47.520
with this source address 23.1.2.60,

155
05:47.520 --> 05:50.000
which is in the same subnet out there on the 23 network.

156
05:50.000 --> 05:51.840
So with that in place, let's scroll down,

157
05:51.840 --> 05:54.440
click on save, and make sure it's implemented,

158
05:54.440 --> 05:56.360
we'll click on refresh there, that looks great.

159
05:56.360 --> 05:58.640
Let's click on the stats icon right there.

160
05:58.640 --> 06:01.640
And look at that, I have active sessions already in place,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

160
05:58.640 --> 06:01.640
And look at that, I have active sessions already in place,

161
06:01.640 --> 06:03.080
that could be DNS requests,

162
06:03.080 --> 06:05.200
or other things that those clients are doing.

163
06:05.200 --> 06:07.400
So now that we have NAT in place right here,

164
06:07.400 --> 06:09.480
let's go back to our VM and test.

165
06:09.480 --> 06:11.840
So here is Mint 10, so a moment ago,

166
06:11.840 --> 06:14.040
it didn't complete the trace path, let's do it again,

167
06:14.040 --> 06:15.120
I announced going out there.

168
06:15.120 --> 06:17.520
So we'll do a control C, and let's also do a ping

169
06:17.520 --> 06:20.560
to www.google.com press enter,

170
06:20.560 --> 06:23.400
and that also verifies that name resolution is working as well.

171
06:23.400 --> 06:27.640
So that's for VM Mint 10, let's also try it from Mint 20,

172
06:27.640 --> 06:29.680
play a movement 10 over to the left here a little bit,

173
06:29.680 --> 06:31.400
and let's bring in Mint 20.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

173
06:29.680 --> 06:31.400
and let's bring in Mint 20.

174
06:31.400 --> 06:36.400
So here is Mint 20, and let's try a ping out to www.vmware.com,

175
06:36.400 --> 06:38.240
and that's working as well.

176
06:38.240 --> 06:39.480
So name resolution is working,

177
06:39.480 --> 06:42.120
connectivity after the unit is working, that looks great.

178
06:42.120 --> 06:44.320
And if we wanted to configure border gateway protocol

179
06:44.320 --> 06:47.720
for a specific VRF, it's pretty simple to do.

180
06:47.720 --> 06:50.560
So with networking selected, we go to Tier Zero Gigways,

181
06:50.560 --> 06:53.040
we go to our blue VRF, click on the three dots,

182
06:53.040 --> 06:54.240
and then click on edit.

183
06:54.240 --> 06:55.600
And then from here, we scroll down,

184
06:55.600 --> 06:58.280
we go into the BGP section, enable it,

185
06:58.280 --> 07:01.880
and then furthermore specify the details for BGP.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

185
06:58.280 --> 07:01.880
and then furthermore specify the details for BGP.

186
07:01.880 --> 07:03.600
Also since we're right here, let's just go ahead

187
07:03.600 --> 07:04.800
and do it as an example.

188
07:04.800 --> 07:07.520
We've also had a previous skill on setting up BGP

189
07:07.520 --> 07:11.080
and dynamic routing, so for more details on setting up BGP,

190
07:11.080 --> 07:12.960
check out that previous skill as well.

191
07:12.960 --> 07:16.000
So for a demo right here for our T0 gateway,

192
07:16.000 --> 07:17.920
this is our blue VRF.

193
07:17.920 --> 07:20.120
Let's go ahead and use the local autonomous system

194
07:20.120 --> 07:23.360
at 6783, and for BGP neighbors right here,

195
07:23.360 --> 07:26.760
we'll click on set, and let's click on add BGP neighbor,

196
07:26.760 --> 07:31.200
and I can set up a little external router at 23.1.2.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

196
07:26.760 --> 07:31.200
and I can set up a little external router at 23.1.2.

197
07:31.200 --> 07:33.360
And let's use .11.

198
07:33.360 --> 07:35.800
And for that remote AS, let's use 3560,

199
07:35.800 --> 07:37.960
and then scroll down and click on save.

200
07:37.960 --> 07:39.880
And then we'll click on refresh here,

201
07:39.880 --> 07:42.760
and then we'll click on close, and then we'll click on save.

202
07:42.760 --> 07:44.800
So right now, if we went to the BGP neighbors

203
07:44.800 --> 07:46.400
and clicked on that link right there,

204
07:46.400 --> 07:47.840
currently showing that neighbor is down

205
07:47.840 --> 07:49.920
because they don't have that neighbor yet configured.

206
07:49.920 --> 07:51.320
However, I've got great news.

207
07:51.320 --> 07:54.400
Let's go ahead and configure a device at that IP address

208
07:54.400 --> 07:57.800
on the 23.1.2 network as a BGP neighbor.

209
07:57.800 --> 07:59.800
And we'll advertise a route just to confirm

210
07:59.800 --> 08:02.840
that our blue VRF is dynamically learning via BGP.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

210
07:59.800 --> 08:02.840
that our blue VRF is dynamically learning via BGP.

211
08:02.840 --> 08:04.200
So let me go ahead and close that.

212
08:04.200 --> 08:06.120
I'll scroll down and close editing.

213
08:06.120 --> 08:08.640
And what I'm gonna add right here is on this segment,

214
08:08.640 --> 08:11.240
a little Cisco device acting as a router.

215
08:11.240 --> 08:14.000
It'll be an autonomous system 3560,

216
08:14.000 --> 08:16.040
and it'll be at the IP address of .11

217
08:16.040 --> 08:18.000
on the 23.1.2 network.

218
08:18.000 --> 08:20.360
And then I'll go ahead and specify that I wanna peer

219
08:20.360 --> 08:24.120
with either .61 or .62 or both,

220
08:24.120 --> 08:27.120
because those are the two IP addresses of our edge nodes

221
08:27.120 --> 08:28.800
providing that external connectivity.

222
08:28.800 --> 08:30.760
And again, the tier zero autonomous system number
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

222
08:28.800 --> 08:30.760
And again, the tier zero autonomous system number

223
08:30.760 --> 08:33.160
I set up was 673.

224
08:33.160 --> 08:35.200
So with that in mind, let's make a quick road trip

225
08:35.200 --> 08:36.640
out to this device right here,

226
08:36.640 --> 08:39.040
which is a Cisco catalyst multi-layer switch,

227
08:39.040 --> 08:40.920
and we'll configure its IP address

228
08:40.920 --> 08:43.720
and do a quick configuration of BGP and advertise route

229
08:43.720 --> 08:46.080
just to verify that the BGP is working

230
08:46.080 --> 08:47.640
with this specific VRF.

231
08:47.640 --> 08:50.440
So here on the external 3560 multi-layer switch

232
08:50.440 --> 08:53.320
is to a quick, go IP interface brief.

233
08:53.320 --> 08:57.040
And we'll also say include any output that has 23 in the line.

234
08:57.040 --> 09:01.800
So there is our logical VLAN 23 interface at 23.1.2.11.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

234
08:57.040 --> 09:01.800
So there is our logical VLAN 23 interface at 23.1.2.11.

235
09:01.800 --> 09:05.920
Let's also verify that we can ping 23.1.2.61

236
09:05.920 --> 09:08.360
just to make sure we're on the same network, which we are.

237
09:08.360 --> 09:10.080
And let's do show IP protocols.

238
09:10.080 --> 09:12.840
So a show IP protocol shows there's no dynamic routing protocols,

239
09:12.840 --> 09:14.200
including no BGP.

240
09:14.200 --> 09:15.600
So we'll go into configuration mode

241
09:15.600 --> 09:18.800
on this multi-layer switch from Cisco and we'll type in router,

242
09:18.800 --> 09:23.560
BGP, and we want to use autonomous system 3560, enter.

243
09:23.560 --> 09:25.440
So that's our ton of system number.

244
09:25.440 --> 09:28.280
And we want to set the neighbor at 23.1.2.61.

245
09:28.280 --> 09:29.480
That's edge one.

246
09:29.480 --> 09:31.400
And that's the neighbor remote autonomous system
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

246
09:29.480 --> 09:31.400
And that's the neighbor remote autonomous system

247
09:31.400 --> 09:34.320
of 673, we'll press enter.

248
09:34.320 --> 09:37.600
And with any luck, we should have a neighborhood.

249
09:37.600 --> 09:38.880
There it is, that's fantastic.

250
09:38.880 --> 09:41.760
We can also set up a pairing with edge two as well.

251
09:41.760 --> 09:44.680
And we'll do that by putting in a neighbor statement for edge two.

252
09:44.680 --> 09:46.920
And that should pop up as well here in a moment.

253
09:46.920 --> 09:48.640
And there it is, that's fantastic.

254
09:48.640 --> 09:50.880
And let's go ahead and advertise the network.

255
09:50.880 --> 09:53.560
So here in BGP configuration mode on this device,

256
09:53.560 --> 10:01.800
let's type in network 888880 with a mask of 255.255.255.0.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

256
09:53.560 --> 10:01.800
let's type in network 888880 with a mask of 255.255.255.0.

257
10:01.800 --> 10:04.960
And BGP is only going to advertise that network if it exists.

258
10:04.960 --> 10:07.600
So let's also create a loopback interface here on the Cisco device

259
10:07.600 --> 10:10.760
by typing an interface loopback and let's use 88.

260
10:10.760 --> 10:14.480
And we'll give it the IP address of 88.88.88.something.

261
10:14.480 --> 10:17.120
Let's go ahead and use 88 there with a 24-bit mask.

262
10:17.120 --> 10:19.480
So now that we have that network ended and exist,

263
10:19.480 --> 10:24.480
that network should now be advertised over to our blue VRF.

264
10:24.480 --> 10:26.400
And we can verify that right here as well

265
10:26.400 --> 10:29.120
by going to one of our edge nodes, let's go to edge one.

266
10:29.120 --> 10:31.240
And here at edge one, let's do a gateways.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

266
10:29.120 --> 10:31.240
And here at edge one, let's do a gateways.

267
10:31.240 --> 10:34.600
So for this VRF right here, the services router for VRF blue,

268
10:34.600 --> 10:36.920
which at the moment is using our VRF 11.

269
10:36.920 --> 10:40.200
So let's type in VRF 11 to go into that VRF.

270
10:40.200 --> 10:42.160
Let's do a gate route, press enter.

271
10:42.160 --> 10:45.120
And sure enough, there is our BGP learned route right there.

272
10:45.120 --> 10:48.800
So the B indicates we're learning it via BGP, fantastic.

273
10:48.800 --> 10:51.840
And we are learning about the 888888 network.

274
10:51.840 --> 10:56.760
And the next top is our BGP neighbor over at 23.1.2.11.

275
10:56.760 --> 11:00.200
We can also do a gate, BGP space question mark.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

275
10:56.760 --> 11:00.200
We can also do a gate, BGP space question mark.

276
11:00.200 --> 11:03.080
And let's go ahead and type in neighbor and press enter.

277
11:03.080 --> 11:04.960
And that's going to show us our BGP neighbors.

278
11:04.960 --> 11:08.200
So here's our BGP neighbor at 23.1.2.11.

279
11:08.200 --> 11:10.520
And the remote AS of 3560.

280
11:10.520 --> 11:13.960
And if we do a get a little question mark BGP and a question mark.

281
11:13.960 --> 11:16.640
And we type in IPV4 and a question mark and press enter.

282
11:16.640 --> 11:19.720
That'll show us our IPV4 routes that we've learned via BGP.

283
11:19.720 --> 11:21.360
Once again, there's the 88 network.

284
11:21.360 --> 11:23.960
Just confirming that we have our BGP neighborship set up

285
11:23.960 --> 11:27.560
between VRF blue, that tier zero gateway,

286
11:27.560 --> 11:29.520
and the external BGP neighbor.

287
11:29.520 --> 11:32.720
So the cool thing is that from a BGP routing perspective,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

287
11:29.520 --> 11:32.720
So the cool thing is that from a BGP routing perspective,

288
11:32.720 --> 11:37.440
we can have the blue VRF tier zero gateway pair with one BGP neighbor.

289
11:37.440 --> 11:41.720
And we can have our other VRFs pairing with yet different BGP neighbors.

290
11:41.720 --> 11:43.560
Again, keeping all the routes separate.

291
11:43.560 --> 11:47.040
So any of the routes in the blue VRF are going to stay in the blue VRF.

292
11:47.040 --> 11:50.000
And any routes over here in the green VRF are going to stay in the green VRF.

293
11:50.000 --> 12:00.000
[BLANK_AUDIO]