WEBVTT

1
00:00.000 --> 00:03.360
Hello and welcome. My name is Keith Barker.

2
00:03.360 --> 00:07.680
And in a previous skill, we went through the steps of connecting our NSX routed

3
00:07.680 --> 00:08.160
environment

4
00:08.160 --> 00:12.320
with our Tier 0 and Tier 1 gateways and connecting those to an external network

5
00:12.320 --> 00:12.880
segment.

6
00:12.880 --> 00:15.630
And as part of that, we threw in a default route just for some basic

7
00:15.630 --> 00:16.240
connectivity.

8
00:16.240 --> 00:19.980
However, in a production environment, we're going to need a lot more than just

9
00:19.980 --> 00:21.040
a default route going

10
00:21.040 --> 00:24.190
outbound. We need to have the external network to know how to reach our

11
00:24.190 --> 00:25.120
internal networks.

12
00:25.120 --> 00:28.670
And we may want to advertise some of those detailed networks to the outside

13
00:28.670 --> 00:29.200
world.

14
00:29.200 --> 00:32.720
Now, regarding routing between our internal NSX routed environment and the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:29.200 --> 00:32.720
Now, regarding routing between our internal NSX routed environment and the

15
00:32.720 --> 00:33.520
external networks

16
00:33.520 --> 00:37.550
and external world, we have a few options. One is we could go ahead and create

17
00:37.550 --> 00:38.400
static routes

18
00:38.400 --> 00:41.600
everywhere. For any network that needs to be reached, we could on the external

19
00:41.600 --> 00:42.640
and also on the NSX

20
00:42.640 --> 00:46.760
environment configure static routes. However, that's pretty tedious. So most of

21
00:46.760 --> 00:47.120
the time,

22
00:47.120 --> 00:50.770
we're going to be using some kind of a dynamic method for learning how to reach

23
00:50.770 --> 00:51.680
remote networks.

24
00:51.680 --> 00:55.030
And in the world of NSX, we want to connect to and dynamically exchange routing

25
00:55.030 --> 00:55.760
information

26
00:55.760 --> 01:00.300
with external routers. We have two options for those dynamic updates. One is to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
00:55.760 --> 01:00.300
with external routers. We have two options for those dynamic updates. One is to

27
01:00.300 --> 01:01.360
use border gateway

28
01:01.360 --> 01:05.730
protocol, which is perfectly fine. It'll work great. The other option is use O

29
01:05.730 --> 01:07.040
SPF, open shortest path

30
01:07.040 --> 01:11.230
first. And in this skill, you and I get to focus our attention on using OSPF to

31
01:11.230 --> 01:12.240
dynamically share

32
01:12.240 --> 01:16.560
information back and forth regarding reachability for networks between our NSX

33
01:16.560 --> 01:17.120
environment and the

34
01:17.120 --> 01:21.870
Tier 0 services router and the external world. And we'll do BGP in a separate

35
01:21.870 --> 01:23.040
skill. So if you're

36
01:23.040 --> 01:25.990
ready, I'll see you in the next video as we take a big picture look at the

37
01:25.990 --> 01:27.520
concept screen in OSPF.

38
01:27.520 --> 01:31.000
We'll follow it up with the game plan and then we'll implement it and verify it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:27.520 --> 01:31.000
We'll follow it up with the game plan and then we'll implement it and verify it

39
01:31.000 --> 01:31.680
together.