WEBVTT

1
00:00.000 --> 00:03.160
So for our OSPF game plan, let's do the following.

2
00:03.160 --> 00:07.200
So the first thing we had to do is let's go ahead and confirm existing routing.

3
00:07.200 --> 00:11.240
Because by default, when we link a tier 1 to a tier 0 gateway,

4
00:11.240 --> 00:14.400
we should have a default route going that way and the same here.

5
00:14.400 --> 00:17.760
And also, I believe in the previous skill, we actually did a default route that

6
00:17.760 --> 00:20.000
went this way on our tier 0 gateway.

7
00:20.000 --> 00:22.520
So I'd like to confirm that existing routing first.

8
00:22.520 --> 00:26.360
I'd also like to confirm from our tier 0 gateway that we can ping this IP

9
00:26.360 --> 00:28.600
address right here on this external router,

10
00:28.600 --> 00:30.920
and that's at 192.1 state 1.1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:28.600 --> 00:30.920
and that's at 192.1 state 1.1.

11
00:30.920 --> 00:35.510
That just verifies that we have connectivity from the tier 0 gateway to that

12
00:35.510 --> 00:37.720
external interface on our external router.

13
00:37.720 --> 00:42.840
So I'll put here confirm T0 to gateway at .1.

14
00:42.840 --> 00:47.240
And that should be leveraging the external segment we have to the 192 network.

15
00:47.240 --> 00:49.970
So I'll make a little note there that that's the external segment that we

16
00:49.970 --> 00:50.680
should be using.

17
00:50.680 --> 00:54.200
And as part of that connectivity to that external network, we're using the

18
00:54.200 --> 00:56.120
virtual IP address of .60.

19
00:56.120 --> 00:59.960
And then on edge 1 and edge 2, which are providing that edge connectivity,

20
00:59.960 --> 01:02.280
on edge 1, we're using .61.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:59.960 --> 01:02.280
on edge 1, we're using .61.

21
01:02.280 --> 01:04.360
And on edge 2, we're using .62.

22
01:04.360 --> 01:07.960
So as a group, these guys are providing that external connectivity

23
01:07.960 --> 01:11.480
from our logical tier 0 gateway to the external segment here.

24
01:11.480 --> 01:14.560
So before we begin setting up routing, I just want to verify we have that basic

25
01:14.560 --> 01:15.720
connectivity right there.

26
01:15.720 --> 01:18.680
So for our OSPF area, let's use area 0.0.

27
01:18.680 --> 01:23.560
So in an NSX environment, it's referred to as area 0.0.0.

28
01:23.560 --> 01:24.760
It's 32 bits long.

29
01:24.760 --> 01:26.920
So in some vendors, they'll let you just put a 0 there.

30
01:26.920 --> 01:29.080
Other vendors may require all four zeros.

31
01:29.080 --> 01:31.400
But the area number is a 32-bit address.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:29.080 --> 01:31.400
But the area number is a 32-bit address.

32
01:31.400 --> 01:34.120
And so it kind of looks like it could be an IPv4 address,

33
01:34.120 --> 01:37.640
but it's really just four octets separated by three periods.

34
01:37.640 --> 01:41.090
Unless your vendor allows you to put a 0 right there, which represents area 0

35
01:41.090 --> 01:41.720
as well.

36
01:41.720 --> 01:44.280
So to do one area, it'll be our backbone area.

37
01:44.280 --> 01:47.800
And then once we establish that neighborhood between our tier 0 gateway,

38
01:47.800 --> 01:51.560
which in the background would be using our edge nodes and the services router

39
01:51.560 --> 01:52.600
function for that.

40
01:52.600 --> 01:55.900
Once we verify that we have the neighborhood, the next step I'd like to take is

41
01:55.900 --> 01:57.160
to advertise routes.

42
01:57.160 --> 02:00.280
So in the tier 0 gateway, I'd like to advertise, I'll call our code these.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:57.160 --> 02:00.280
So in the tier 0 gateway, I'd like to advertise, I'll call our code these.

43
02:00.280 --> 02:05.240
I'd like to advertise the 10, that 10 network and also the 1020 network and

44
02:05.240 --> 02:07.800
advertise them up to the peer.

45
02:07.800 --> 02:10.120
So I'll put a little adv there for advertise.

46
02:10.120 --> 02:13.480
And that way, this external router will know how to forward in the direction of

47
02:13.480 --> 02:15.800
1010-0 or 1020-0

48
02:15.800 --> 02:18.040
if it ever needs to forward a packet in that direction.

49
02:18.040 --> 02:23.160
So if this VM right here did a ping to the IP address of 192.168.1.1,

50
02:23.160 --> 02:26.440
if we wanted to get a reply, this router right here, we need to have routing

51
02:26.440 --> 02:27.080
information

52
02:27.080 --> 02:29.400
on how to forward it back in this direction.

53
02:29.400 --> 02:32.830
Also as part of our game plan, although we did a static default route in our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
02:29.400 --> 02:32.830
Also as part of our game plan, although we did a static default route in our

54
02:32.830 --> 02:33.800
previous skill

55
02:33.800 --> 02:38.120
here on the tier 0 gateway, I'd like to go ahead and dynamically learn a

56
02:38.120 --> 02:39.480
default route from the

57
02:39.480 --> 02:43.420
external router. So for our game plan, let's go ahead and specify this part as

58
02:43.420 --> 02:45.320
the T0 learning,

59
02:45.320 --> 02:51.000
the default route for IPv4 from the external router.

60
02:51.000 --> 02:53.880
So that would imply we're going to need to configure this device or some other

61
02:53.880 --> 02:54.280
device that

62
02:54.280 --> 02:59.200
we put up here on this common segment to dynamically advertise a default route

63
02:59.200 --> 03:00.120
so that tier 0 can
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:59.200 --> 03:00.120
so that tier 0 can

64
03:00.120 --> 03:03.840
learn that via OSPF. And then once it's all in place, we'd also want to do a

65
03:03.840 --> 03:04.760
quick verification

66
03:04.760 --> 03:08.620
that it all works. So I'll put verify routing right here. Now as far as

67
03:08.620 --> 03:10.360
verification, just the heads

68
03:10.360 --> 03:14.460
up, we should not. If from this VM right here, we should not be able to access

69
03:14.460 --> 03:15.320
the internet yet

70
03:15.320 --> 03:20.130
because we are using private RFC 1918 addresses and we need to do network

71
03:20.130 --> 03:21.800
address translation at some

72
03:21.800 --> 03:26.360
point, hand tent on a services router here before that packet is sent out to

73
03:26.360 --> 03:27.880
the internet. But for

74
03:27.880 --> 03:31.230
my test, what we should be able to do is we should be able to ping from any of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
03:27.880 --> 03:31.230
my test, what we should be able to do is we should be able to ping from any of

75
03:31.230 --> 03:31.960
these VMs

76
03:31.960 --> 03:35.470
once it's all set up, we should be able to ping this IP address. And if this

77
03:35.470 --> 03:36.360
has the routes,

78
03:36.360 --> 03:40.460
it should be able to respond back. Or if we create a loopback interface here on

79
03:40.460 --> 03:41.320
this router,

80
03:41.320 --> 03:44.840
then we could attempt to ping that loopback address from any of these VMs. And

81
03:44.840 --> 03:45.240
if we have a

82
03:45.240 --> 03:48.500
default route that's been learned here at our tier 0 gateway, it should be able

83
03:48.500 --> 03:49.400
to forward. And as

84
03:49.400 --> 03:52.670
a result, this single router right here should be able to respond back. So we

85
03:52.670 --> 03:53.240
'll put that all

86
03:53.240 --> 03:56.460
into the category of verifying routing and just knowing ahead of time that we

87
03:56.460 --> 03:57.560
're not yet ready

88
03:57.560 --> 04:00.620
to go out to the internet because we're going to need to implement NAT, which
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

88
03:57.560 --> 04:00.620
to go out to the internet because we're going to need to implement NAT, which

89
04:00.620 --> 04:01.400
will be in a separate

90
04:01.400 --> 04:05.040
skill. So with this game, plan in mind, I'll see you in the next video as we

91
04:05.040 --> 04:06.200
start our first step and

92
04:06.200 --> 04:10.760
this to confirm our existing routing. So I'll see you there in just a moment.