WEBVTT

1
00:00.000 --> 00:04.360
All right, so our first step is just to confirm our existing NSX topology.

2
00:04.360 --> 00:08.000
And what we're going for is the topology that looks like this.

3
00:08.000 --> 00:13.800
All right, so here in the NSX manager, which is at .21, here on my management

4
00:13.800 --> 00:16.000
network 192.168.1,

5
00:16.000 --> 00:17.800
let's check out our topology.

6
00:17.800 --> 00:21.200
Let's go ahead and make sure all of our nodes are up so we click here on system

7
00:21.200 --> 00:21.200
.

8
00:21.200 --> 00:24.800
And then if we expand fabric on the left and go down to hosts,

9
00:24.800 --> 00:26.200
and let me collapse the left-hand side.

10
00:26.200 --> 00:29.200
Here, it gives us a little more room and here is our cluster.

11
00:29.200 --> 00:32.600
So those two nodes, ESX I1 and 2 look like they are up.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:29.200 --> 00:32.600
So those two nodes, ESX I1 and 2 look like they are up.

12
00:32.600 --> 00:35.000
Here it shows for NSX configuration mismatched,

13
00:35.000 --> 00:38.400
just because they are both using a custom static IP address.

14
00:38.400 --> 00:42.100
And they're not actually using the template that's applied for the whole

15
00:42.100 --> 00:42.600
cluster.

16
00:42.600 --> 00:44.400
But they do show us up, so that's good.

17
00:44.400 --> 00:48.200
Also, let me go ahead and select both of them and click here on actions.

18
00:48.200 --> 00:52.210
I just want to confirm they are both supporting all the transport zones that we

19
00:52.210 --> 00:52.600
're using.

20
00:52.600 --> 00:56.400
So click here on manage transport zones for ESX I1 and 2.

21
00:56.400 --> 00:59.400
And currently it's just supporting the red overlay transport zone.

22
00:59.400 --> 01:04.000
So I'm going to go ahead and add the VLAN backed transport zone as well,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:59.400 --> 01:04.000
So I'm going to go ahead and add the VLAN backed transport zone as well,

23
01:04.000 --> 01:07.340
because when I was setting this up earlier, the advanced load balancer had a

24
01:07.340 --> 01:08.400
huge problem

25
01:08.400 --> 01:12.690
because the hosts in the cluster didn't support all the transport zones

26
01:12.690 --> 01:13.400
involved.

27
01:13.400 --> 01:18.280
So I'm going to make sure that the edge nodes and the host transport nodes both

28
01:18.280 --> 01:20.000
support these two transport zones.

29
01:20.000 --> 01:24.200
The VLAN transport zone and the overlay transport zone for lab 3 red.

30
01:24.200 --> 01:27.200
So these are the two hosts. We'll click on save there.

31
01:27.200 --> 01:28.200
That looks good.

32
01:28.200 --> 01:32.200
And then we'll go back on the left-hand side, go down to nodes for edge nodes.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:28.200 --> 01:32.200
And then we'll go back on the left-hand side, go down to nodes for edge nodes.

33
01:32.200 --> 01:35.000
And here for the edge nodes, I'll go ahead and select both of them,

34
01:35.000 --> 01:38.800
click on actions and from the dropdown, click on manage transport zones,

35
01:38.800 --> 01:40.600
and they currently support both of them.

36
01:40.600 --> 01:41.600
Okay, that looks great.

37
01:41.600 --> 01:43.800
So we'll click on cancel there, no changes.

38
01:43.800 --> 01:47.350
So we've just confirmed that the two host transport nodes and the two edge

39
01:47.350 --> 01:48.400
nodes are up and active

40
01:48.400 --> 01:51.200
and ready to go inside of our NSX environment.

41
01:51.200 --> 01:56.270
So next, let me check on the network address translation here off the T1 right

42
01:56.270 --> 01:56.800
gateway

43
01:56.800 --> 02:01.400
between the 10-103 network and the 192-168-1 network.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
01:56.800 --> 02:01.400
between the 10-103 network and the 192-168-1 network.

44
02:01.400 --> 02:03.700
Because I want to make sure that when the advanced load balancer is

45
02:03.700 --> 02:06.000
communicating with the vCenter

46
02:06.000 --> 02:10.010
or the NSX manager, I want to make sure that these two devices have a proper

47
02:10.010 --> 02:11.000
route getting back.

48
02:11.000 --> 02:15.050
And so if I make this device look like it's coming from the 192-168-1 network

49
02:15.050 --> 02:16.800
address base with the NAT,

50
02:16.800 --> 02:18.000
that'll solve that problem.

51
02:18.000 --> 02:20.800
So let's check out NAT for the tier 1 right gateway.

52
02:20.800 --> 02:25.090
So to do that, we'll go to the networking tab here in the NSX manager on the

53
02:25.090 --> 02:26.000
left-hand side.

54
02:26.000 --> 02:28.400
We'll click on NAT under network services.

55
02:28.400 --> 02:33.760
And then from the dropdown, we'll go ahead and choose our tier 1 right gateway,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:28.400 --> 02:33.760
And then from the dropdown, we'll go ahead and choose our tier 1 right gateway,

56
02:33.760 --> 02:34.400
that one right there.

57
02:34.400 --> 02:39.350
So as far as the NAT is concerned, it's set up as reflexive NAT between 10-10-

58
02:39.350 --> 02:40.000
3015,

59
02:40.000 --> 02:45.290
which will be the IP address for our load balancer and mapped out to 192-168-1

60
02:45.290 --> 02:47.000
15 on the other side there.

61
02:47.000 --> 02:47.600
Fantastic.

62
02:47.600 --> 02:51.530
So the NAT is in place just for the benefit of communicating between the

63
02:51.530 --> 02:52.400
advanced load balancer

64
02:52.400 --> 02:54.800
and the vCenter and the NSX manager.

65
02:54.800 --> 02:58.560
So next, let's confirm that we have both of the gateways in place, the tier 1

66
02:58.560 --> 02:59.600
left and the tier 1 right.

67
02:59.600 --> 03:03.370
So one way of doing that would be to go to the networking tab up on top and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
02:59.600 --> 03:03.370
So one way of doing that would be to go to the networking tab up on top and

68
03:03.370 --> 03:04.600
then go to network topology.

69
03:04.600 --> 03:06.600
And that would be a quick way of seeing it.

70
03:06.600 --> 03:07.800
So here I zoomed in a little bit.

71
03:07.800 --> 03:09.800
Here's T1 left, this one right here.

72
03:09.800 --> 03:14.800
And it has a connection to external VLAN 5 and also external VLAN 6.

73
03:14.800 --> 03:19.610
And it also has an overlay segment connected to the 101 right here, the SEG 101

74
03:19.610 --> 03:19.800
.

75
03:19.800 --> 03:24.800
And also not shown on my diagram, but it also has a connection here to SEG 102,

76
03:24.800 --> 03:27.800
which we won't be using for the demo, but it's there if we need it.

77
03:27.800 --> 03:29.800
So that looks good for T1 left.

78
03:29.800 --> 03:32.800
Let's also just take a look at T1 right.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
03:29.800 --> 03:32.800
Let's also just take a look at T1 right.

79
03:32.800 --> 03:36.380
So here is the T1 right, which is connected to the 192-168-1 network, which it

80
03:36.380 --> 03:36.800
is.

81
03:36.800 --> 03:40.800
So I'm using .22 on the interface on this tier 1 right gateway.

82
03:40.800 --> 03:47.100
And then it's also connected to the SEG 103 ALB management right here using the

83
03:47.100 --> 03:48.800
IP address 10.103.0.1.

84
03:48.800 --> 03:49.300
at 1.

85
03:49.300 --> 03:59.300
[BLANK_AUDIO]