WEBVTT

1
00:00.000 --> 00:02.520
So for the host transport nodes in our nested environment,

2
00:02.520 --> 00:06.800
we're going to use ESXIA and ESXIB as the two hosts,

3
00:06.800 --> 00:10.200
which are going to have the NSX software or the NSX bits added to them.

4
00:10.200 --> 00:15.040
So from the NSX manager, we select the cluster that these two hosts are in.

5
00:15.040 --> 00:19.040
And as far as their configuration with our existing infrastructure for

6
00:19.040 --> 00:19.640
networking,

7
00:19.640 --> 00:22.880
here's what I did for ESXIA for the tunnel endpoint.

8
00:22.880 --> 00:27.920
We're going to use 11, 11, 11, 11 with a 24-bit mask and a default gateway.

9
00:28.280 --> 00:32.120
I've got one. We're also as part of that going to use VLAN 101.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:28.280 --> 00:32.120
I've got one. We're also as part of that going to use VLAN 101.

10
00:32.120 --> 00:34.440
So I want to make sure the top of rack switch supports that.

11
00:34.440 --> 00:39.200
And then for ESXIB, although it could be in the same exact subnet as ESXIA,

12
00:39.200 --> 00:42.160
for learning purposes, I want to make sure I separated them.

13
00:42.160 --> 00:48.240
So I put ESXIB with an IP address of 22, 22, 22 with a 24-bit mask

14
00:48.240 --> 00:52.760
with a default gateway of .1 on that 22.22.22 network.

15
00:52.760 --> 00:55.980
And the default gateway functionality is being provided by my top of rack

16
00:55.980 --> 00:56.440
switch,

17
00:56.560 --> 00:59.520
which is up here, which is also a really important reason to make sure we have

18
00:59.520 --> 01:01.840
those VLANs supported and have the routing in place.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:59.520 --> 01:01.840
those VLANs supported and have the routing in place.

19
01:01.840 --> 01:04.840
And then on ESXIB, I'm using VLAN 102.

20
01:04.840 --> 01:08.360
Once again, we could use the same VLAN, but to help differentiate them,

21
01:08.360 --> 01:11.440
especially in the lab environment, when you pack it captures and so forth,

22
01:11.440 --> 01:15.080
to see the distinct IP addresses and know exactly who owns those tunnel end

23
01:15.080 --> 01:16.560
points is super useful.

24
01:16.560 --> 01:22.960
Also for ESXIA, I'm using VMNIC 2 and for ESXIB, I'm going to be using VMIC 3.

25
01:23.160 --> 01:27.560
So here to draw little arrows there that would look like this ESXIA is going to

26
01:27.560 --> 01:27.640
be

27
01:27.640 --> 01:32.400
using this uplink and ESXIB is going to be using this uplink.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:27.640 --> 01:32.400
using this uplink and ESXIB is going to be using this uplink.

28
01:32.400 --> 01:36.000
Now, because they're separate hosts, we could have also chosen to use the same

29
01:36.000 --> 01:40.080
exact uplink on each of the hosts, but again, just to clarify who's going to

30
01:40.080 --> 01:40.760
using what I

31
01:40.760 --> 01:42.280
chose to implement it like this.

32
01:42.280 --> 01:46.440
So as part of the configuration for the ESXI host to become transport nodes and

33
01:46.440 --> 01:50.510
specify exactly which uplinks and VLANs we're going to use that's used as part

34
01:50.510 --> 01:51.640
of an uplink profile.

35
01:51.840 --> 01:57.000
So when I deployed ESXIA and ESXIB, I use an uplink profile that specified I

36
01:57.000 --> 01:58.480
want to use one uplink.

37
01:58.480 --> 02:02.360
And then I mapped that uplink over to the uplink I wanted them to use.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
01:58.480 --> 02:02.360
And then I mapped that uplink over to the uplink I wanted them to use.

38
02:02.360 --> 02:05.120
And as far as the lab environment, one of the first things we'd want to do

39
02:05.120 --> 02:05.520
after we

40
02:05.520 --> 02:09.600
deploy this is to verify from our top of rack switch that we can reach those

41
02:09.600 --> 02:10.280
addresses.

42
02:10.280 --> 02:14.740
So for my top of rack switch, I should be able to reach the 11, 11, 11, 11

43
02:14.740 --> 02:15.080
address

44
02:15.080 --> 02:20.440
and the 22, 22, 22, 22 address if everything is working correctly and these two

45
02:20.640 --> 02:23.320
ESXI hosts are configured as host transport nodes.

46
02:23.320 --> 02:26.320
So let me walk you through the verification of all that right now.

47
02:26.320 --> 02:29.800
So to do that, I need to bring up the NSX manager as well.

48
02:29.800 --> 02:34.280
So the NSX manager, which is running right here on my physical host, it has a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
02:29.800 --> 02:34.280
So the NSX manager, which is running right here on my physical host, it has a

49
02:34.280 --> 02:34.800
virtual

50
02:34.800 --> 02:38.080
IP address associated with it of .10 on my management network.

51
02:38.080 --> 02:38.920
So let's go there now.

52
02:38.920 --> 02:41.320
So here is the login to the NSX manager.

53
02:41.320 --> 02:44.400
I'll go ahead and log in and then here in the NSX manager, if we click on the

54
02:44.400 --> 02:44.760
system

55
02:44.760 --> 02:49.440
tab and then the left, if we expand fabric, here we have our profiles and then

56
02:49.440 --> 02:49.760
a sub

57
02:49.960 --> 02:51.240
for uplink profiles.

58
02:51.240 --> 02:57.040
And here's the uplink profile I used in combination with ESXIA, which is going

59
02:57.040 --> 02:59.960
to use VLAN 101 and uplink to.

60
02:59.960 --> 03:03.280
And then here is the uplink profile I created that we're going to use in
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
02:59.960 --> 03:03.280
And then here is the uplink profile I created that we're going to use in

61
03:03.280 --> 03:03.840
combination

62
03:03.840 --> 03:08.520
with ESXI B, which we're using VLAN 102 and VM Mc3.

63
03:08.520 --> 03:12.720
So I deploy the host, we'll go to fabric and hosts and we'll expand our cluster

64
03:12.720 --> 03:13.040
here.

65
03:13.040 --> 03:15.600
And let's just grab ESXIA as an example.

66
03:15.600 --> 03:18.400
We'll click on the three dots and click right here on configure NSX.

67
03:18.600 --> 03:21.800
So there's this management IP address for ESXIA.

68
03:21.800 --> 03:25.040
We'll click on next and then we'll expand the configuration here.

69
03:25.040 --> 03:28.200
So here's where I specified I want to use this uplink profile.

70
03:28.200 --> 03:32.800
And then down below, here's where I map the uplink profile over to the actual
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:28.200 --> 03:32.800
And then down below, here's where I map the uplink profile over to the actual

71
03:32.800 --> 03:33.120
name

72
03:33.120 --> 03:35.520
of the uplink on the distributed switch.

73
03:35.520 --> 03:39.320
So if we went back to this switch, the lab one NSX host, that let's do it real

74
03:39.320 --> 03:39.640
quick.

75
03:39.640 --> 03:44.160
So back in the OGAIT.lab vSphere client environment, if we go to our networking

76
03:44.160 --> 03:47.850
here, if we click on our switch right here, lab one NSX host, we right click

77
03:47.850 --> 03:48.200
and then

78
03:48.400 --> 03:51.480
we'll go to settings and edit settings and uplinks.

79
03:51.480 --> 03:54.960
And this right here, I've got my four uplinks named correctly.

80
03:54.960 --> 04:00.040
So here, this is lab VM Nick two and that's the uplink we're choosing to map
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
03:54.960 --> 04:00.040
So here, this is lab VM Nick two and that's the uplink we're choosing to map

81
04:00.040 --> 04:03.720
as part of our uplink profile for ESXIA.

82
04:03.720 --> 04:07.160
And then when we get to ESXIA B, we're going to go ahead and choose lab three

83
04:07.160 --> 04:07.400
VM

84
04:07.400 --> 04:09.960
Nick three for its mapping for its uplink profile.

85
04:09.960 --> 04:11.480
So we'll click on cancel there.

86
04:11.480 --> 04:13.200
Let's go back to the NSX manager.

87
04:13.200 --> 04:16.440
And again, we're looking at the details for ESXIA.

88
04:16.640 --> 04:20.840
So it's got this static IP address of 11 11 11 11 with the default gateway

89
04:20.840 --> 04:24.240
and in dot one with a 24 bit mask, we scroll down.

90
04:24.240 --> 04:28.640
Here's the logical uplink that we named inside of NSX and there is the name of

91
04:28.640 --> 04:30.800
the uplink on our virtual distributed switch.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
04:28.640 --> 04:30.800
the uplink on our virtual distributed switch.

92
04:30.800 --> 04:33.840
It's also showing us a visual right here as well.

93
04:33.840 --> 04:38.050
So we'll click on cancel and click on yes, we want to cancel and let's go take

94
04:38.050 --> 04:38.240
a look

95
04:38.240 --> 04:42.760
at ESXIA B on the three dots, click on configure NSX, click on next.

96
04:42.760 --> 04:44.120
Let's go ahead and expand that.

97
04:44.320 --> 04:48.160
So this is using an uplink profile called lab host V one oh two VM

98
04:48.160 --> 04:52.720
three and then we're mapping that over to lab VM three on the actual virtual

99
04:52.720 --> 04:54.960
distributed switch and if he's grown up a little bit here,

100
04:54.960 --> 04:58.200
showing us the IP address we're using there and the mask and the default

101
04:58.200 --> 04:58.560
gateway.

102
04:58.560 --> 05:03.040
So we should be able to ping the addresses for the total endpoints on both ESX
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
04:58.560 --> 05:03.040
So we should be able to ping the addresses for the total endpoints on both ESX

103
05:03.040 --> 05:03.280
IA

104
05:03.280 --> 05:05.440
and B from our top of RAC switch.

105
05:05.440 --> 05:10.800
So here at the top of RAC switch, we did a ping to 11 11 11 11 11.

106
05:10.800 --> 05:13.800
That's the total endpoint address for ESXIA.

107
05:14.000 --> 05:17.560
We should also be able to ping 22 that 22 that 22 that 22, which is the

108
05:17.560 --> 05:19.840
tunnel endpoint address for ESXIA B.

109
05:19.840 --> 05:22.600
And since they're both reachable from the top of RAC switch,

110
05:22.600 --> 05:26.200
that's a terrific indication that everything is working all the way from our

111
05:26.200 --> 05:30.520
virtualized ESXIA host down here with their tunnel endpoint addresses all the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
05:26.200 --> 05:30.520
virtualized ESXIA host down here with their tunnel endpoint addresses all the

112
05:30.520 --> 05:30.720
way

113
05:30.720 --> 05:33.880
to our top of RAC switch, which is going to the routing for the transport

114
05:33.880 --> 05:34.400
networks.

115
05:34.400 --> 05:36.440
So now that we've addressed the lab

116
05:36.440 --> 05:40.520
topology to support our two host transport nodes in the next video, let's take

117
05:40.520 --> 05:40.600
a

118
05:40.800 --> 05:44.880
look at how we're going to implement our edge nodes in our nested topology.

119
05:44.880 --> 05:47.080
So I'll see you in the next video for exactly that.