WEBVTT

1
00:00.180 --> 00:01.800
So now that we have one edge

2
00:01.800 --> 00:04.170
that's already fully deployed and ready to go,

3
00:04.170 --> 00:05.580
and the other one that's still baking

4
00:05.580 --> 00:07.860
and that'll take again like 45 more minutes,

5
00:07.860 --> 00:09.750
let's take a look at how we can verify

6
00:09.750 --> 00:11.850
once we do have an edge fully deployed,

7
00:11.850 --> 00:13.710
what we can look at to help confirm

8
00:13.710 --> 00:15.240
that it's implemented correctly.

9
00:15.240 --> 00:18.060
So we're gonna focus our attention right here on edge-1,

10
00:18.060 --> 00:20.460
which is running on ESXi Host A.

11
00:20.460 --> 00:23.130
So regarding edge-1, we could go to the vSphere client,

12
00:23.130 --> 00:24.300
take a look at it from here.

13
00:24.300 --> 00:26.940
So here in my folder called NSX Edge Node VMs,

14
00:26.940 --> 00:30.180
I have edge-1, and if we go to the summary here
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:26.940 --> 00:30.180
I have edge-1, and if we go to the summary here

15
00:30.180 --> 00:33.420
that can confirm for us it's IP address of 191.

16
00:33.420 --> 00:34.260
If we scroll down a bit,

17
00:34.260 --> 00:36.780
it can confirm the details about that VM,

18
00:36.780 --> 00:39.085
including which ESXI host it's running on,

19
00:39.085 --> 00:41.250
so it's running on ESXi-A.

20
00:41.250 --> 00:43.710
Now, if we were to Right Click on this edge node

21
00:43.710 --> 00:46.410
and then go to edit settings from the dropdown,

22
00:46.410 --> 00:48.870
notice here it has five network adapters.

23
00:48.870 --> 00:50.430
So the first network adapter

24
00:50.430 --> 00:52.260
is the network adapter that we configured

25
00:52.260 --> 00:53.430
with the management IP address,

26
00:53.430 --> 00:55.710
we connected it to the port group called management,

27
00:55.710 --> 00:57.150
and that's how the NSX Manager

28
00:57.150 --> 00:58.740
is able to communicate and interact

29
00:58.740 --> 01:01.170
with this edge transport node.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

29
00:58.740 --> 01:01.170
with this edge transport node.

30
01:01.170 --> 01:02.970
And then because we specified an uplink profile

31
01:02.970 --> 01:03.900
with one VMNIC,

32
01:03.900 --> 01:06.210
it then asked us to go ahead and do the mapping.

33
01:06.210 --> 01:09.060
So we mapped the name inside of NSX,

34
01:09.060 --> 01:10.650
of the uplink we wanted to use

35
01:10.650 --> 01:13.110
with the name of the uplink on the distributed switch,

36
01:13.110 --> 01:15.030
and that's what's being shown right here.

37
01:15.030 --> 01:17.250
And then it has three additional interfaces.

38
01:17.250 --> 01:19.470
So we could use additional uplinks, if we wanted to.

39
01:19.470 --> 01:21.810
So if we wanted to use additional uplinks, we would not,

40
01:21.810 --> 01:25.050
I repeat, not just come in here as properties of this VM

41
01:25.050 --> 01:27.780
but rather we'd go back to the NSX Manager

42
01:27.780 --> 01:31.842
and reconfigure this edge VM with a new uplink profile
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:27.780 --> 01:31.842
and reconfigure this edge VM with a new uplink profile

43
01:31.842 --> 01:34.290
that had two or more interfaces.

44
01:34.290 --> 01:36.630
And then from there, we could map those interfaces

45
01:36.630 --> 01:38.190
to the appropriate port groups.

46
01:38.190 --> 01:40.230
On the other hand, for the management connection,

47
01:40.230 --> 01:41.940
we could go ahead and manipulate that

48
01:41.940 --> 01:43.740
because that was only implemented

49
01:43.740 --> 01:45.510
as part of deploying the VM

50
01:45.510 --> 01:48.330
while the other uplink related interfaces

51
01:48.330 --> 01:51.420
should be controlled and managed through NSX Manager.

52
01:51.420 --> 01:53.520
So let's go ahead and cancel out of that.

53
01:53.520 --> 01:55.470
And let's go over to the NSX Manager.

54
01:55.470 --> 01:57.600
So here in this current flavor of NSX Manager,

55
01:57.600 --> 02:00.330
if we click on system on the left, in the fabric section,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
01:57.600 --> 02:00.330
if we click on system on the left, in the fabric section,

56
02:00.330 --> 02:03.360
if we go down to nodes, it can also show us details here.

57
02:03.360 --> 02:06.120
So edge-1 is already baked, it's already set up,

58
02:06.120 --> 02:07.710
edge-2 is still being deployed.

59
02:07.710 --> 02:09.870
And again, if we click on refresh down here, and again,

60
02:09.870 --> 02:11.370
it could take up to an hour

61
02:11.370 --> 02:13.710
for this to be fully deployed and operational

62
02:13.710 --> 02:15.030
and showing up as ready.

63
02:15.030 --> 02:15.863
So in the meantime,

64
02:15.863 --> 02:16.920
we're gonna focus still here on edge-1,

65
02:16.920 --> 02:18.210
which is completely done.

66
02:18.210 --> 02:21.630
So if we click on edge-1 on the overview subtab here,

67
02:21.630 --> 02:23.640
it has details about edge-1,

68
02:23.640 --> 02:26.790
including its ID, the management IP address,

69
02:26.790 --> 02:29.550
the host it's running on, the version of NSX it's running,

70
02:29.550 --> 02:32.340
and also shows here the controller connectivity
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
02:29.550 --> 02:32.340
and also shows here the controller connectivity

71
02:32.340 --> 02:33.720
and manager connectivity,

72
02:33.720 --> 02:36.540
as well as the transport zone or zones

73
02:36.540 --> 02:37.800
that it's currently supporting.

74
02:37.800 --> 02:39.450
So if we wanted to for example,

75
02:39.450 --> 02:42.480
include additional uplinks for this edge node,

76
02:42.480 --> 02:44.460
what we would do is simply click on edit right here

77
02:44.460 --> 02:45.990
to edit edge-1.

78
02:45.990 --> 02:46.823
And then from here,

79
02:46.823 --> 02:50.100
we could go ahead and specify a different uplink profile

80
02:50.100 --> 02:52.410
that used more than just one uplink.

81
02:52.410 --> 02:54.030
Then once we specify a new uplink profile,

82
02:54.030 --> 02:56.220
we take any uplinks identified in that profile

83
02:56.220 --> 02:58.050
and then map them over to the uplinks

84
02:58.050 --> 02:59.580
associated with our distributed switch.

85
02:59.580 --> 03:00.413
So also while we're here,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
02:59.580 --> 03:00.413
So also while we're here,

86
03:00.413 --> 03:02.640
it's showing us the IP address that's configured

87
03:02.640 --> 03:05.520
for the tunnel endpoint, so we should be able to go ahead

88
03:05.520 --> 03:07.680
and ping that from the transport network.

89
03:07.680 --> 03:08.910
So let's verify that also.

90
03:08.910 --> 03:11.130
So here is our top of rack switch.

91
03:11.130 --> 03:15.990
If we do a ping over to 33.33.33.33 and press Enter.

92
03:15.990 --> 03:18.420
If it comes back successful, that's a very good sign

93
03:18.420 --> 03:22.380
that your top of rack switch environment has reachability

94
03:22.380 --> 03:23.340
and common VLANs

95
03:23.340 --> 03:26.640
associated with that tunnel endpoint address, fantastic.

96
03:26.640 --> 03:27.810
So we'll minimize that.

97
03:27.810 --> 03:29.070
Lemme go ahead and click on cancel,

98
03:29.070 --> 03:31.140
not gonna make any changes to that edge node.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
03:29.070 --> 03:31.140
not gonna make any changes to that edge node.

99
03:31.140 --> 03:33.630
Here, if we click on monitor for our edge node,

100
03:33.630 --> 03:35.280
here's giving us details about our edge node,

101
03:35.280 --> 03:38.160
including the cores allocated, how long it's been up.

102
03:38.160 --> 03:39.300
So it was over two hours ago

103
03:39.300 --> 03:41.790
when I did the deployment of that initial edge-1.

104
03:41.790 --> 03:43.080
So as we continue to scroll down,

105
03:43.080 --> 03:44.520
it'll give us additional details

106
03:44.520 --> 03:48.210
about this edge transport node including system memory use,

107
03:48.210 --> 03:49.110
which could be very helpful,

108
03:49.110 --> 03:50.490
especially if you're troubleshooting.

109
03:50.490 --> 03:51.780
As we continue to scroll down

110
03:51.780 --> 03:52.980
and we have transport node status

111
03:52.980 --> 03:54.960
with controller connectivity showing as up.

112
03:54.960 --> 03:56.490
It's also showing us the PNIC,

113
03:56.490 --> 03:58.650
which is an acronym for physical NIC/bond status.

114
03:58.650 --> 04:00.180
So we have two interfaces that we're using,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

114
03:58.650 --> 04:00.180
So we have two interfaces that we're using,

115
04:00.180 --> 04:01.800
one is for the management

116
04:01.800 --> 04:04.530
and the management traffic going to the edge node,

117
04:04.530 --> 04:06.840
and the other one right here is for the uplink.

118
04:06.840 --> 04:08.490
And then we click here on tunnels,

119
04:08.490 --> 04:10.560
it's confirming any tunnels that we have in place.

120
04:10.560 --> 04:12.480
So at the moment we don't have any tunnels in place

121
04:12.480 --> 04:14.280
and that's because we don't need any tunnels

122
04:14.280 --> 04:16.650
because until we have some gateways configured,

123
04:16.650 --> 04:19.650
they're being supported by one or more of our edge nodes.

124
04:19.650 --> 04:21.120
There's no reason to build a tunnel

125
04:21.120 --> 04:22.860
to a device that's not providing any gateway

126
04:22.860 --> 04:24.000
or functionality.

127
04:24.000 --> 04:26.490
But that will change once we start configuring

128
04:26.490 --> 04:28.890
our tier zero and tier one gateways.

129
04:28.890 --> 04:29.910
Also, if we wanted to,

130
04:29.910 --> 04:32.580
we could go to the command line interface for edge-1
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

130
04:29.910 --> 04:32.580
we could go to the command line interface for edge-1

131
04:32.580 --> 04:34.770
and we could reach it here on my management network

132
04:34.770 --> 04:37.830
at 192.168.1.91.

133
04:37.830 --> 04:39.510
So let's test that out as well.

134
04:39.510 --> 04:43.890
So I've sshd over to the edge node at 192.168.1.91

135
04:43.890 --> 04:45.540
It's giving us some basic instruction

136
04:45.540 --> 04:49.380
in case we need to set the interface for basic connectivity

137
04:49.380 --> 04:51.120
that's already set up here on edge number one.

138
04:51.120 --> 04:52.770
And we're currently not in a failed state.

139
04:52.770 --> 04:56.550
So here at edge-1 if we did a get Space and a question mark,

140
04:56.550 --> 04:57.480
we have a lot of commands,

141
04:57.480 --> 05:00.300
very similar as we would with the NSX CLI
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

141
04:57.480 --> 05:00.300
very similar as we would with the NSX CLI

142
05:00.300 --> 05:02.640
over at the NSX Manager.

143
05:02.640 --> 05:04.260
And also very similar to the commands available

144
05:04.260 --> 05:07.380
on an ESXi host that's been enabled with NSX switches,

145
05:07.380 --> 05:11.190
now referred to as a host transport node as part of NSX.

146
05:11.190 --> 05:12.060
So here for example,

147
05:12.060 --> 05:15.600
if we did a get logical switches and pressed Enter.

148
05:15.600 --> 05:16.890
So this is the logical switching

149
05:16.890 --> 05:19.410
involved with access for the transport network.

150
05:19.410 --> 05:22.050
So if we did a get logical switch Space

151
05:22.050 --> 05:25.020
and then we take this UUID, I'll just copy and paste that,

152
05:25.020 --> 05:26.700
and do a Space and a question mark,

153
05:26.700 --> 05:28.020
let's type in vtep-table.

154
05:28.020 --> 05:29.160
So for this logical switch

155
05:29.160 --> 05:30.750
that's leveraging VLAN 103,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

155
05:29.160 --> 05:30.750
that's leveraging VLAN 103,

156
05:30.750 --> 05:33.420
meaning it's gonna be doing 802.1Q tagging

157
05:33.420 --> 05:35.310
as it sends frames out.

158
05:35.310 --> 05:39.360
And the actual interface is fp for Fastpath, ethernet zero,

159
05:39.360 --> 05:41.160
which is our logical interface

160
05:41.160 --> 05:43.230
connected to the distributed switch port group,

161
05:43.230 --> 05:46.500
which leads to VMNIC three in the case of edge-1.

162
05:46.500 --> 05:48.180
So these edge nodes at the moment,

163
05:48.180 --> 05:49.680
they're pretty much just relaxing,

164
05:49.680 --> 05:51.900
they don't have any gateway services to support.

165
05:51.900 --> 05:53.460
So lemme go ahead and minimize that.

166
05:53.460 --> 05:54.293
And then let's go ahead

167
05:54.293 --> 05:56.310
and check on the status here of edge-2.

168
05:56.310 --> 05:58.170
So I've clicked here edge-2 also,

169
05:58.170 --> 06:00.480
it was about over an hour ago that I deployed edge-2,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

169
05:58.170 --> 06:00.480
it was about over an hour ago that I deployed edge-2,

170
06:00.480 --> 06:03.030
so it looks like edge-2 is now ready.

171
06:03.030 --> 06:06.150
So the last step I'd like to take with these two edges,

172
06:06.150 --> 06:08.400
which are gonna be providing our gateway services

173
06:08.400 --> 06:09.233
once they're configured,

174
06:09.233 --> 06:12.750
is to go ahead and put these two edges into an edge cluster.

175
06:12.750 --> 06:16.140
And that's easily done by clicking here on system,

176
06:16.140 --> 06:17.280
going to nodes,

177
06:17.280 --> 06:20.670
and then clicking here on the subtab of edge clusters

178
06:20.670 --> 06:22.140
and then clicking on add.

179
06:22.140 --> 06:25.380
So we'll give it a name, we'll call it Our Edge Cluster.

180
06:25.380 --> 06:28.050
And then we'll use the default edge cluster profile.

181
06:28.050 --> 06:30.060
So it's there by default, we'll just grab that one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

181
06:28.050 --> 06:30.060
So it's there by default, we'll just grab that one.

182
06:30.060 --> 06:33.870
And then we're gonna include edge-1 and edge-2

183
06:33.870 --> 06:35.190
as part of this cluster.

184
06:35.190 --> 06:36.930
So anytime we're doing fault tolerance

185
06:36.930 --> 06:39.000
with active standby or active-active,

186
06:39.000 --> 06:40.920
we can refer to the cluster

187
06:40.920 --> 06:42.630
and then it can use the resources

188
06:42.630 --> 06:46.560
of edge-1 and/or edge-2 to implement the gateway services.

189
06:46.560 --> 06:48.030
So I'm gonna go ahead and select both of those,

190
06:48.030 --> 06:50.610
click on the arrow to bring 'em over and click on add.

191
06:50.610 --> 06:52.080
Alright, so there's our cluster,

192
06:52.080 --> 06:54.720
if we click back up here on the top subtab

193
06:54.720 --> 06:56.430
for Edge Transport Nodes,

194
06:56.430 --> 06:58.320
we can now verify the details for each of our nodes

195
06:58.320 --> 06:59.430
simply by clicking on them,

196
06:59.430 --> 07:00.780
and the details are gonna be right here,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

196
06:59.430 --> 07:00.780
and the details are gonna be right here,

197
07:00.780 --> 07:03.750
including the external ID, the IP addresses, the versions,

198
07:03.750 --> 07:05.790
and whether the controller and management connectivity

199
07:05.790 --> 07:08.430
is currently up and everything is looking good

200
07:08.430 --> 07:09.600
on both of these edges

201
07:09.600 --> 07:12.990
and they're both now included as part of an edge cluster.

202
07:12.990 --> 07:14.821
So with the system tab selected on the left,

203
07:14.821 --> 07:17.250
if we click here on system overview,

204
07:17.250 --> 07:18.750
let's check our progress.

205
07:18.750 --> 07:20.760
We now have one NSX management node

206
07:20.760 --> 07:24.090
as part of our NSX management cluster for fault tolerance,

207
07:24.090 --> 07:25.050
it wouldn't be a bad idea

208
07:25.050 --> 07:27.150
to implement two or three of those.

209
07:27.150 --> 07:28.470
For host transport nodes,

210
07:28.470 --> 07:32.677
we have ESXi-A and ESXi-B, which have been enabled for NSX.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

210
07:28.470 --> 07:32.677
we have ESXi-A and ESXi-B, which have been enabled for NSX.

211
07:32.677 --> 07:34.530
And as a result they're now referred

212
07:34.530 --> 07:36.330
to as host transport nodes.

213
07:36.330 --> 07:40.140
And we just got done deploying ESXi-2 as an edge

214
07:40.140 --> 07:41.494
and I previously put ESXi-1 in.

215
07:41.494 --> 07:44.220
So we now have two edge transport nodes,

216
07:44.220 --> 07:45.360
and these are hyperlinks as well,

217
07:45.360 --> 07:47.640
so if we clicked here on edge transport nodes,

218
07:47.640 --> 07:50.250
it takes us back to system and nodes.

219
07:50.250 --> 07:52.320
And if we click once again on system overview

220
07:52.320 --> 07:54.240
and clicked here on host transport nodes,

221
07:54.240 --> 07:57.540
it's also a hyperlink that would take us to hosts,

222
07:57.540 --> 07:59.310
at which point we could see our clusters,

223
07:59.310 --> 08:02.370
then drill in to see which ones are enabled for NSX,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

223
07:59.310 --> 08:02.370
then drill in to see which ones are enabled for NSX,

224
08:02.370 --> 08:05.133
which include ESXi-A and ESXi-B.