WEBVTT

1
00:00.000 --> 00:04.440
So our next step is to go ahead and deploy the global manager and that's this

2
00:04.440 --> 00:05.280
guy right here.

3
00:05.280 --> 00:10.050
And we're going to use .12 as the IP address here on my management network for

4
00:10.050 --> 00:10.880
this global manager.

5
00:10.880 --> 00:15.360
Now the actual host resource that we deploy this on doesn't have to be one of

6
00:15.360 --> 00:16.880
our ES6I hosts at

7
00:16.880 --> 00:22.240
site one or site two. It just needs to be some compute resource, some ES6I host

8
00:22.240 --> 00:22.720
that can support

9
00:22.720 --> 00:27.520
that VM. And the initial process for deploying a global manager is exactly the

10
00:27.520 --> 00:28.560
same as the initial

11
00:28.560 --> 00:33.200
process for deploying the initial local manager here at site one or site two.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:28.560 --> 00:33.200
process for deploying the initial local manager here at site one or site two.

12
00:33.200 --> 00:33.760
And that's using the

13
00:33.760 --> 00:37.500
deploy template option inside of the vSphere client. So I have downloaded to my

14
00:37.500 --> 00:38.160
management

15
00:38.160 --> 00:43.570
computer the OVF template for the unified NSX manager. And here the vSphere

16
00:43.570 --> 00:44.640
client will simply

17
00:44.640 --> 00:49.140
right click on our data center and say we want to deploy an OVF template. It's

18
00:49.140 --> 00:49.760
going to ask me

19
00:49.760 --> 00:53.940
for the files. We'll say local file. Click here to upload the files. I've

20
00:53.940 --> 00:55.040
selected the NSX

21
00:55.040 --> 01:00.620
unified appliance, same version that I used to deploy the local NSX manager at
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
00:55.040 --> 01:00.620
unified appliance, same version that I used to deploy the local NSX manager at

22
01:00.620 --> 01:02.080
site one and site

23
01:02.080 --> 01:05.580
two originally. And so with that selected, we'll click on next. I'm going to

24
01:05.580 --> 01:06.400
call the name of this

25
01:06.400 --> 01:11.710
VM NSX dash global. I'll also specify that I want to keep it in a folder called

26
01:11.710 --> 01:12.320
NSX VMs.

27
01:12.320 --> 01:16.890
Click on next and also be selected ESXI host as a compute resource for this to

28
01:16.890 --> 01:17.360
run on.

29
01:17.360 --> 01:22.480
And let me go ahead and pick ESXIC. Click on next, then I'll click on next to

30
01:22.480 --> 01:23.200
continue.

31
01:23.200 --> 01:27.040
And then the size of our deployment, extra small, small, medium or large, I'll

32
01:27.040 --> 01:27.520
go ahead and pick

33
01:27.520 --> 01:31.240
medium. It's going to use this many CPUs and that much RAM. We'll click on next
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
01:27.520 --> 01:31.240
medium. It's going to use this many CPUs and that much RAM. We'll click on next

34
01:31.240 --> 01:32.240
. I'll specify the

35
01:32.240 --> 01:35.910
data store I want to use and I'm going to choose in my lab thin provisioning

36
01:35.910 --> 01:37.280
and then click on next.

37
01:37.280 --> 01:40.250
For its management network, I'm going to specify a port group that goes up to

38
01:40.250 --> 01:41.120
my management network

39
01:41.120 --> 01:44.780
and that is this one right here. So we'll click on OK. We're going to be using

40
01:44.780 --> 01:45.600
IPv4. So we'll leave

41
01:45.600 --> 01:48.960
that alone. Click on next. And that wants us to fill in details for the

42
01:48.960 --> 01:50.000
passwords that we want

43
01:50.000 --> 01:55.430
to use, including for the grab a root user. If we scroll down for the admin, if

44
01:55.430 --> 01:56.080
we scroll down for

45
01:56.080 --> 02:00.250
the audit user and so forth. So I'll go ahead and supply all those passwords.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
01:56.080 --> 02:00.250
the audit user and so forth. So I'll go ahead and supply all those passwords.

46
02:00.250 --> 02:00.880
So I've filled in

47
02:00.880 --> 02:05.050
those passwords and confirmed those passwords. If we scroll down, I'll leave

48
02:05.050 --> 02:05.920
the default user

49
02:05.920 --> 02:09.530
names for admin and audit as they are. Then there are optional parameters. This

50
02:09.530 --> 02:10.320
says for internal

51
02:10.320 --> 02:13.520
use only, I'll leave those blank and these little red indicators here for my

52
02:13.520 --> 02:14.560
local password manager.

53
02:14.560 --> 02:19.720
They're not part of the native interface for NSX and we'll scroll down. I'll go

54
02:19.720 --> 02:20.960
ahead and call this NSX

55
02:20.960 --> 02:25.150
dash global. We'll scroll down and it's here under the role name where we're

56
02:25.150 --> 02:26.320
going to specify the

57
02:26.320 --> 02:30.720
role we want this NSX manager to have. So the default is NSX manager. That's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:26.320 --> 02:30.720
role we want this NSX manager to have. So the default is NSX manager. That's

58
02:30.720 --> 02:31.520
what I have at site

59
02:31.520 --> 02:36.300
one and site two. And from the drop down, we would here select NSX global

60
02:36.300 --> 02:38.240
manager, which is effectively

61
02:38.240 --> 02:42.160
going to give it the ability to be the global manager and then start to manage

62
02:42.160 --> 02:42.960
and work with

63
02:42.960 --> 02:47.000
the local managers, including those at site one and site two. And then we'll

64
02:47.000 --> 02:47.440
specify the

65
02:47.440 --> 02:51.300
management network IPV forward rest. So I'll specify that. So on the management

66
02:51.300 --> 02:51.840
network, I'm

67
02:51.840 --> 02:54.960
going to use dot 12 based on our plan. In fact, let me just confirm that real

68
02:54.960 --> 02:56.080
quick. So sure enough,

69
02:56.080 --> 03:00.100
as a confirmation, we want to use dot 12 fantastic. And we're using a 24 bit
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
02:56.080 --> 03:00.100
as a confirmation, we want to use dot 12 fantastic. And we're using a 24 bit

70
03:00.100 --> 03:01.120
mask. So I'll put that

71
03:01.120 --> 03:04.930
in and dot a decimal. And then the default gateway on that management network

72
03:04.930 --> 03:07.680
is 192.168.1.1. And

73
03:07.680 --> 03:11.080
I'm not using IPV six. So I'll leave that part blank. And as we continue to go

74
03:11.080 --> 03:11.840
down, we'll tell

75
03:11.840 --> 03:15.970
it what DNS server to use. And in my lab environment, I have this server that's

76
03:15.970 --> 03:17.360
providing DNS services.

77
03:17.360 --> 03:21.260
So I'll supply that as the DNS server that this global manager should use. And

78
03:21.260 --> 03:21.920
then for the search

79
03:21.920 --> 03:26.010
list, I'll put in O G I T dot lab, which is the domain that all my devices are

80
03:26.010 --> 03:26.960
in, and we'll scroll

81
03:26.960 --> 03:30.820
down. And then I'll specify the NTP server to use. And in my lab, I'm also
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
03:26.960 --> 03:30.820
down. And then I'll specify the NTP server to use. And in my lab, I'm also

82
03:30.820 --> 03:33.840
using 192.168.1.100.

83
03:33.840 --> 03:37.460
So it's doubling up as my DNS server and also my time server. And I'll also

84
03:37.460 --> 03:39.280
enable SSH and root

85
03:39.280 --> 03:44.240
SSH logins to this new NSX manager. And then we'll scroll down and all the rest

86
03:44.240 --> 03:45.200
here for internal

87
03:45.200 --> 03:48.710
use. So I'll leave those blank. And then after a few more clicks on next and

88
03:48.710 --> 03:49.840
finish, it would then

89
03:49.840 --> 03:55.230
begin the deployment of this new NSX global manager on that ESX I host that we

90
03:55.230 --> 03:56.000
specified

91
03:56.000 --> 03:59.250
as part of the deployment of this OV F now I'm going to go ahead and click on

92
03:59.250 --> 04:00.320
cancel right here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

92
03:59.250 --> 04:00.320
cancel right here.

93
04:00.320 --> 04:05.080
And the reason for that is because I already have that NSX manager running. And

94
04:05.080 --> 04:05.600
that is right

95
04:05.600 --> 04:10.160
here. So I open up a new browser tab going to the dot 12 address, and then we

96
04:10.160 --> 04:11.200
'll log in. So then

97
04:11.200 --> 04:14.920
the login will specify admin and then the password we configured as part of the

98
04:14.920 --> 04:15.840
deployment of that

99
04:15.840 --> 04:20.200
OV F and we'll click login. So here in the interface for this NSX global

100
04:20.200 --> 04:22.240
manager, it looks very similar

101
04:22.240 --> 04:26.930
to what we have in our local NSX managers. However, we click here on system and

102
04:26.930 --> 04:28.000
then open up fabric

103
04:28.000 --> 04:32.160
over on the left, it doesn't have all the options beneath here that a local NSX
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
04:28.000 --> 04:32.160
over on the left, it doesn't have all the options beneath here that a local NSX

104
04:32.160 --> 04:32.880
manager would

105
04:32.880 --> 04:36.720
normally have. However, it is on the system overview section right here. It is

106
04:36.720 --> 04:37.760
telling us that the

107
04:37.760 --> 04:42.020
global manager is not available. Why is that? That's because we also need to

108
04:42.020 --> 04:43.200
specify that this

109
04:43.200 --> 04:47.760
NSX global manager is active. And if we go back to our game plan, that's what

110
04:47.760 --> 04:48.160
we're going to do

111
04:48.160 --> 04:50.980
right now is we're going to tell this global manager that we're now in the

112
04:50.980 --> 04:51.840
interface of that

113
04:51.840 --> 04:55.530
it is the active manager. It also is begging us right here the system overview

114
04:55.530 --> 04:56.400
to do that. So if

115
04:56.400 --> 04:59.770
we click here on location manager, or we could just click on system on the top

116
04:59.770 --> 05:00.800
and then left,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

116
04:59.770 --> 05:00.800
and then left,

117
05:00.800 --> 05:04.780
go to location manager, we're just going to click on this tile right here, make

118
05:04.780 --> 05:05.440
active. And that

119
05:05.440 --> 05:09.070
makes it the active manager. So I'm going to give this global manager the name

120
05:09.070 --> 05:10.240
of NSX-global,

121
05:10.240 --> 05:15.120
click on save. And in a few moments, this is now the active manager. It's also

122
05:15.120 --> 05:16.080
encouraging us

123
05:16.080 --> 05:20.630
for the benefit of fault tolerance to add an additional global manager as part

124
05:20.630 --> 05:21.680
of this cluster.

125
05:21.680 --> 05:25.040
In a production environment, that would be a great idea in my lab environment.

126
05:25.040 --> 05:25.760
I'm going to use a

127
05:25.760 --> 05:30.230
single NSX VM acting as the global manager. And this also confirms the address
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

127
05:25.760 --> 05:30.230
single NSX VM acting as the global manager. And this also confirms the address

128
05:30.230 --> 05:31.040
that we're currently

129
05:31.040 --> 05:34.940
using, which is .12 for this global manager. If you want to add some fault

130
05:34.940 --> 05:35.840
tolerance there,

131
05:35.840 --> 05:40.240
we go to global manager appliances. And very similar to the process of adding

132
05:40.240 --> 05:41.600
additional NSX

133
05:41.600 --> 05:45.820
managers to a local manager, if you want to add a second or third NSX appliance

134
05:45.820 --> 05:46.560
here for fault

135
05:46.560 --> 05:50.060
tolerance, we're also going to need to take the step of going into fabric and

136
05:50.060 --> 05:51.120
specifying a compute

137
05:51.120 --> 05:55.370
manager. And by specifying a compute manager effectively a vCenter is then

138
05:55.370 --> 05:56.000
getting us the

139
05:56.000 --> 05:59.940
opportunity to choose from the host that are being managed by that vCenter,

140
05:59.940 --> 06:01.120
which ESXi host can be
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

140
05:59.940 --> 06:01.120
which ESXi host can be

141
06:01.120 --> 06:05.070
the home for these additional NSX appliances. So for my lab environment, I'm

142
06:05.070 --> 06:06.080
just going to use the

143
06:06.080 --> 06:12.270
one single NSX manager right here at .12, which is acting as our NSX global

144
06:12.270 --> 06:13.920
manager. So based in

145
06:13.920 --> 06:18.240
our game plan, we have now deployed our global manager. We sit it as active,

146
06:18.240 --> 06:18.960
and that leads us

147
06:18.960 --> 06:24.460
to the next step is to onboard site one and site two, including importing the

148
06:24.460 --> 06:25.760
configurations

149
06:25.760 --> 06:29.970
from those local managers. So we'll continue our journey in the next video. I

150
06:29.970 --> 06:30.720
'll see you there
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

150
06:29.970 --> 06:30.720
'll see you there

151
06:30.720 --> 06:31.920
in just a moment.