WEBVTT

1
00:00.240 --> 00:01.440
So as a first stop,

2
00:01.440 --> 00:04.290
we are going to verify our current infrastructure

3
00:04.290 --> 00:07.020
and let's go ahead and start off with the DNS

4
00:07.020 --> 00:10.080
regarding the IP addresses and the names we intend on using

5
00:10.080 --> 00:12.390
just to verify that's all in place right here

6
00:12.390 --> 00:13.650
at our DNS server.

7
00:13.650 --> 00:15.510
So a quick way of verifying the DNS

8
00:15.510 --> 00:17.040
is from a command prompt.

9
00:17.040 --> 00:18.720
So this is a little command prompt

10
00:18.720 --> 00:20.010
on my management computer.

11
00:20.010 --> 00:21.660
I'm running Windows 11

12
00:21.660 --> 00:24.900
and let's type in nslookup as a DNS tool here.

13
00:24.900 --> 00:26.670
This puts us into interactive mode

14
00:26.670 --> 00:29.040
and I'm currently using that same DNS server

15
00:29.040 --> 00:31.320
at 192.168.1.100.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

15
00:29.040 --> 00:31.320
at 192.168.1.100.

16
00:31.320 --> 00:34.740
So let me check for nsx-mgr-11

17
00:34.740 --> 00:36.210
and that says can't find it.

18
00:36.210 --> 00:37.860
My local computer isn't looking

19
00:37.860 --> 00:39.720
for the same fully qualified domains.

20
00:39.720 --> 00:43.860
So let me go ahead and do nsx-mgr-11.ogat.local

21
00:43.860 --> 00:44.730
and press Enter.

22
00:44.730 --> 00:48.450
Sure enough, that resolves and that's at 192.168.1.11.

23
00:48.450 --> 00:52.410
Let's do the same thing for nsx-mgr-12

24
00:52.410 --> 00:53.820
and that's .12.

25
00:53.820 --> 00:57.960
Let's do 13 and that's resolving to .13.

26
00:57.960 --> 01:00.330
We can also verify the reverse lookups as well
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
00:57.960 --> 01:00.330
We can also verify the reverse lookups as well

27
01:00.330 --> 01:04.020
with doing a 192.168.1.11

28
01:04.020 --> 01:06.960
and that should resolve to the name nsx-mgr-11.

29
01:06.960 --> 01:08.010
I also have a DNS entry

30
01:08.010 --> 01:10.980
for the virtual IP address of .10.

31
01:10.980 --> 01:13.140
I forget what that is, but we can find out real quick

32
01:13.140 --> 01:18.140
by just doing a nslookup for 192.168.1.10, press Enter,

33
01:18.210 --> 01:20.430
and there's the name of that right there.

34
01:20.430 --> 01:22.020
So I currently have A records in place

35
01:22.020 --> 01:24.060
for the three NSX managers,

36
01:24.060 --> 01:26.280
as well as the virtual IP address.

37
01:26.280 --> 01:28.110
I also have pointer records set up

38
01:28.110 --> 01:30.360
for the reverse lookup functionality as well.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:28.110 --> 01:30.360
for the reverse lookup functionality as well.

39
01:30.360 --> 01:31.770
Also because we're currently interacting

40
01:31.770 --> 01:34.440
with this DNS server, I know that's reachable

41
01:34.440 --> 01:35.700
and that's also the same server

42
01:35.700 --> 01:38.340
that's providing NTP services as well.

43
01:38.340 --> 01:41.400
So we'll use the Windows Server at that IP address

44
01:41.400 --> 01:44.040
for both network time protocol, NTP,

45
01:44.040 --> 01:45.900
as well as DNS services.

46
01:45.900 --> 01:47.400
So let me exit out of that.

47
01:47.400 --> 01:49.650
Also, let's verify the management IP address here

48
01:49.650 --> 01:52.170
of our vCenter at .185.

49
01:52.170 --> 01:53.940
And while we're there and verifying that,

50
01:53.940 --> 01:56.970
we can also verify the port groups involved

51
01:56.970 --> 01:58.980
that we'll be using for connectivity

52
01:58.980 --> 02:01.920
of the new NSX manager to our management network.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
01:58.980 --> 02:01.920
of the new NSX manager to our management network.

53
02:01.920 --> 02:04.140
So here on the vSphere Client, we are currently logged on

54
02:04.140 --> 02:06.270
as administrator at vsphere.local.

55
02:06.270 --> 02:07.890
That's the single sign-on domain.

56
02:07.890 --> 02:10.620
And let's go to the VM and templates view here.

57
02:10.620 --> 02:12.660
Let's go down to vCenter Server Appliance.

58
02:12.660 --> 02:14.040
There it is right there.

59
02:14.040 --> 02:15.480
We'll click on the Summary tab

60
02:15.480 --> 02:19.350
and its IP address is 192.168.1.185.

61
02:19.350 --> 02:22.470
So we've just confirmed the IP address of vCenter.

62
02:22.470 --> 02:25.680
We also confirm the user that we can log in as

63
02:25.680 --> 02:26.520
which will be important

64
02:26.520 --> 02:30.390
as part of integrating the NSX over with vCenter.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
02:26.520 --> 02:30.390
as part of integrating the NSX over with vCenter.

65
02:30.390 --> 02:32.130
Let's also verify some capacity.

66
02:32.130 --> 02:33.780
Our intention is to go ahead

67
02:33.780 --> 02:38.040
and put the new NSX manager on one of our ESXi hosts.

68
02:38.040 --> 02:39.270
And I think based on our plan,

69
02:39.270 --> 02:40.800
in fact, I'm sure based on our plan,

70
02:40.800 --> 02:43.320
we are looking at esxi-c.

71
02:43.320 --> 02:45.450
So if we open up the management cluster here,

72
02:45.450 --> 02:47.280
here is esxi-c.

73
02:47.280 --> 02:50.610
And at the moment, esxi-c has plenty of CPU available

74
02:50.610 --> 02:53.430
and not so much memory, it has like 21 gigs free,

75
02:53.430 --> 02:56.520
and that'll be fine for our first NSX appliance.

76
02:56.520 --> 02:58.590
As far as the port group for the management network,

77
02:58.590 --> 03:00.840
let's just go to networking for a moment here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
02:58.590 --> 03:00.840
let's just go to networking for a moment here.

78
03:00.840 --> 03:05.070
And here is a distributed switch called VDS for MGMT.

79
03:05.070 --> 03:08.520
And if we click on Configure and then click on Topology,

80
03:08.520 --> 03:10.470
it has a port group called MGMT.

81
03:10.470 --> 03:12.960
There's VM kernel adapters associated with it.

82
03:12.960 --> 03:14.427
There's a few VMs associated with it.

83
03:14.427 --> 03:17.130
And that leads out to a couple of NICs.

84
03:17.130 --> 03:19.557
We have vmnic0 and vmnic6.

85
03:19.557 --> 03:21.960
And I just wanna take a look at the teaming here

86
03:21.960 --> 03:24.330
for the management distributed port group.

87
03:24.330 --> 03:27.060
So here for the port group, if we click on Configure

88
03:27.060 --> 03:29.880
and we click on Policies and scroll down a little bit,

89
03:29.880 --> 03:33.810
here it shows us that it's using as the active uplink vmnic0
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
03:29.880 --> 03:33.810
here it shows us that it's using as the active uplink vmnic0

90
03:33.810 --> 03:37.440
with a standby link of vmnic6, which is perfectly fine.

91
03:37.440 --> 03:41.370
So both those interfaces lead to my VLAN one here

92
03:41.370 --> 03:42.810
in my Home Office Studio

93
03:42.810 --> 03:46.560
and that is the 192.168.1 management network.

94
03:46.560 --> 03:49.170
So when we deploy the first NSX manager,

95
03:49.170 --> 03:50.820
we're gonna tell it that for its port group

96
03:50.820 --> 03:51.990
for the management interface,

97
03:51.990 --> 03:54.240
we want it to use this management port group.