WEBVTT

1
00:00.000 --> 00:04.000
So in our topology, I currently have these four VMs that are currently running

2
00:04.000 --> 00:04.320
and ready.

3
00:04.320 --> 00:08.240
I'd like to deploy a couple more. One is the server or device that we can place

4
00:08.240 --> 00:09.280
here on

5
00:09.280 --> 00:12.720
segment 10 that we can use for additional testing. I'm also going to place one

6
00:12.720 --> 00:13.760
additional VM right

7
00:13.760 --> 00:18.650
here up on VLAN 23. Again, that we can also use for testing. So to do that, we

8
00:18.650 --> 00:19.440
'll use the vSphere

9
00:19.440 --> 00:22.620
client. I'll right click on the data center. And then from the dropdown, click

10
00:22.620 --> 00:23.520
here and deploy

11
00:23.520 --> 00:28.120
OVF template, click on local files, then I'll click here on upload files. I've

12
00:28.120 --> 00:29.920
got a little DSL OVA

13
00:29.920 --> 00:33.360
now. I don't know whether or not this has VMware tools on it. So we'll just pay
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:29.920 --> 00:33.360
now. I don't know whether or not this has VMware tools on it. So we'll just pay

14
00:33.360 --> 00:33.920
attention that as

15
00:33.920 --> 00:38.130
we deploy it regarding how we bring it up or bring it down. So with this dls O

16
00:38.130 --> 00:39.520
VA selected, we'll click

17
00:39.520 --> 00:43.600
on next and I'm going to name this little VM server on segment 10. And then I'm

18
00:43.600 --> 00:44.720
going to go ahead

19
00:44.720 --> 00:48.770
and place that in the folder called VMs for testing. Click on next. As far as

20
00:48.770 --> 00:49.680
who's going to host

21
00:49.680 --> 00:53.520
this, I want it to be one of our host transport nodes. Let's put this on ESXIA,

22
00:53.520 --> 00:55.200
click on next.

23
00:55.200 --> 00:58.800
And here's the description for it. It's a really tiny DSL. And this is the

24
00:58.800 --> 00:59.760
entity or person who

25
00:59.760 --> 01:03.670
created it. Fantastic. So I'll go ahead and click on next. And then I'll put it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
00:59.760 --> 01:03.670
created it. Fantastic. So I'll go ahead and click on next. And then I'll put it

26
01:03.670 --> 01:05.040
on a local data store,

27
01:05.040 --> 01:09.000
click on next. And then I want to make sure I put this guy on the right segment

28
01:09.000 --> 01:09.760
. So we'll click on

29
01:09.760 --> 01:13.950
browse for its network interface. And let's go ahead and put it on segment 10

30
01:13.950 --> 01:14.880
yellow. Perfect.

31
01:14.880 --> 01:18.340
We'll click on OK. And then click on next. And we'll confirm our work. So it's

32
01:18.340 --> 01:20.080
going to go on ESXIA

33
01:20.080 --> 01:24.000
on the local data store. It's being connected to segment 10. Fantastic. And we

34
01:24.000 --> 01:25.120
'll click on finish.

35
01:25.120 --> 01:29.600
So that is in the process of deploying fantastic. We'll let that finish in the

36
01:29.600 --> 01:30.880
background. And while
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:29.600 --> 01:30.880
background. And while

37
01:30.880 --> 01:34.960
we're waiting for that, let's go ahead and create one more VM. And let's put it

38
01:34.960 --> 01:36.480
up on the VLAN 23.

39
01:36.480 --> 01:39.280
So I'm going to take one of these VMs. Let's just grab that one right here,

40
01:39.280 --> 01:40.240
which is running

41
01:40.240 --> 01:43.540
right click and say, let's just clone it. That's one of the benefits of vSphere

42
01:43.540 --> 01:44.560
. So we'll go ahead

43
01:44.560 --> 01:49.520
and click on clone and then clone to a virtual machine. And we'll call this VM

44
01:49.520 --> 01:51.120
dash 23 meeting.

45
01:51.120 --> 01:55.260
It's going to be a VM sitting up. Once it's all set up, VLAN 23 on the 23.1.2

46
01:55.260 --> 01:56.000
network.

47
01:56.000 --> 01:58.330
So as far as where we're going to place this in our folders, we'll place it

48
01:58.330 --> 01:58.960
also in the VMs

49
01:58.960 --> 02:03.190
for testing folder, click on next. And as far as the compute resource, this one
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
01:58.960 --> 02:03.190
for testing folder, click on next. And as far as the compute resource, this one

50
02:03.190 --> 02:04.480
doesn't actually need

51
02:04.480 --> 02:10.090
host transport notes. We could put it on ESXIA or ESXIB or we could go ahead

52
02:10.090 --> 02:11.440
and put it on a host

53
02:11.440 --> 02:15.120
in our management cluster. Let's go ahead and click on ESXID. So because we're

54
02:15.120 --> 02:15.680
not going to be

55
02:15.680 --> 02:19.940
putting this VM on an overlay segment as part of NSX, it won't matter too much.

56
02:19.940 --> 02:20.560
So we'll ignore

57
02:20.560 --> 02:24.320
that click on next and we'll put on the local data store click on next, then we

58
02:24.320 --> 02:24.960
'll customize

59
02:24.960 --> 02:27.990
the network configuration. And we'll click these two checkboxes to give us the

60
02:27.990 --> 02:29.120
opportunity to

61
02:29.120 --> 02:33.680
put this VM on the correct subnet in this case, the VLAN 23 network and then go
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
02:29.120 --> 02:33.680
put this VM on the correct subnet in this case, the VLAN 23 network and then go

62
02:33.680 --> 02:34.560
ahead and power it

63
02:34.560 --> 02:39.250
on. So we'll click on next and for the network adapter and browse. Oh, I just

64
02:39.250 --> 02:41.600
realized. I don't

65
02:41.600 --> 02:44.650
know a port group that goes to VLAN 23. So let me go ahead just for a moment

66
02:44.650 --> 02:45.440
and put this on the

67
02:45.440 --> 02:50.490
management port group. Click OK, click on next, click on finish. And let's also

68
02:50.490 --> 02:51.360
create a port

69
02:51.360 --> 02:54.700
group where I can move that to for VLAN 23. And then for this distributed

70
02:54.700 --> 02:55.440
switch called

71
02:55.440 --> 02:59.040
DS for NSX, that'll work. We'll go ahead and right click. Then we'll click on

72
02:59.040 --> 02:59.680
distributed port

73
02:59.680 --> 03:03.460
group and then we'll click on new distributed port group. And I'm just going to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
02:59.680 --> 03:03.460
group and then we'll click on new distributed port group. And I'm just going to

74
03:03.460 --> 03:05.680
name this VLAN 23.

75
03:05.680 --> 03:09.360
And then click on next. And then I want to see all the details. So I'm going to

76
03:09.360 --> 03:09.760
go ahead and say

77
03:09.760 --> 03:13.880
this is belonging to VLAN 23. That way I'll be trunked down to my physical

78
03:13.880 --> 03:15.040
network. So it can

79
03:15.040 --> 03:20.650
work and click on next and then next and then next. And I'm only going to use

80
03:20.650 --> 03:21.680
VM NIC 2. So I'm

81
03:21.680 --> 03:25.570
going to take VM NIC 3 out of the picture here for this specific port group,

82
03:25.570 --> 03:26.560
click on next and

83
03:26.560 --> 03:31.400
finish and boom. We now have that new port group which is right there. And if
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

83
03:26.560 --> 03:31.400
finish and boom. We now have that new port group which is right there. And if

84
03:31.400 --> 03:31.840
we look at the

85
03:31.840 --> 03:36.280
topology here for the actual switch by going to configure and topology, here's

86
03:36.280 --> 03:36.880
our port group,

87
03:36.880 --> 03:41.010
VLAN 23, associated with VLAN 23. So we'll do is we'll modify that VM and move

88
03:41.010 --> 03:41.520
it over to that

89
03:41.520 --> 03:44.880
port group. So here for VM 23, I'm going to right click and just give a nice

90
03:44.880 --> 03:45.760
fair even shake. I'm

91
03:45.760 --> 03:49.280
going to click on power, do a shutdown, the guest OS, click on yes because it's

92
03:49.280 --> 03:50.640
running VMWare tools.

93
03:50.640 --> 03:53.770
Fantastic. So we'll give that a moment to power off. And now let's power it off

94
03:53.770 --> 03:54.800
. We'll right click

95
03:54.800 --> 03:58.000
and click on edit settings. And then we'll go ahead and move the network

96
03:58.000 --> 03:59.840
adapter over to the correct

97
03:59.840 --> 04:03.250
port group. So we'll click on browse. We'll modify the network interface card,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

97
03:59.840 --> 04:03.250
port group. So we'll click on browse. We'll modify the network interface card,

98
04:03.250 --> 04:03.840
put it on the right

99
04:03.840 --> 04:08.280
port group, click on OK, confirm our work, click on OK. And then we'll power it

100
04:08.280 --> 04:09.120
back on by right

101
04:09.120 --> 04:13.110
clicking and clicking power and power on or we could use the power on button

102
04:13.110 --> 04:14.560
above. This is DRS

103
04:14.560 --> 04:18.640
saying, hey, please put it on ESX ID. We'll say great, click on OK. And the

104
04:18.640 --> 04:19.520
reason it's recommending

105
04:19.520 --> 04:24.710
that is because the data store for VM 23 is also on the local data store for ES

106
04:24.710 --> 04:25.600
X ID. All right,

107
04:25.600 --> 04:29.280
so that's powering up. And let's launch a web console here. And let's just do a

108
04:29.280 --> 04:29.840
couple quick

109
04:29.840 --> 04:34.730
tests. So do I have config? And sure enough, it has an IP address 231270.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

109
04:29.840 --> 04:34.730
tests. So do I have config? And sure enough, it has an IP address 231270.

110
04:34.730 --> 04:36.560
Fantastic. And if we do a

111
04:36.560 --> 04:40.250
route command, if I type it in right, do a route command, we also have a

112
04:40.250 --> 04:41.680
default gateway, which

113
04:41.680 --> 04:45.440
it did a reverse lookup for, but that's the IP address right there. It's 23.1.2

114
04:45.440 --> 04:46.240
.1 is our default

115
04:46.240 --> 04:49.930
gateway. And again, there's our actual IP address. So because this guy is

116
04:49.930 --> 04:51.200
sitting out on this

117
04:51.200 --> 04:56.020
pseudo public network outside of gateway zero, it should be able to go ahead

118
04:56.020 --> 04:56.880
and ping internet

119
04:56.880 --> 05:01.550
resources. So let's verify that real quick with a ping to 8888. And that looks
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

119
04:56.880 --> 05:01.550
resources. So let's verify that real quick with a ping to 8888. And that looks

120
05:01.550 --> 05:02.560
great. And we'll do

121
05:02.560 --> 05:07.400
control C, we can also do a trace route to 8888. Just to confirm we're really

122
05:07.400 --> 05:08.160
going out there,

123
05:08.160 --> 05:12.670
I'll do control C there. That looks great as well. So we verified our VM 23

124
05:12.670 --> 05:13.680
that it can get out to

125
05:13.680 --> 05:17.810
the internet. Let's also verify the server we just placed and identify what its

126
05:17.810 --> 05:18.960
IP address is.

127
05:18.960 --> 05:23.040
So prior to that, the server on segment 10, let's just verify its network

128
05:23.040 --> 05:24.000
connectivity.

129
05:24.000 --> 05:27.900
So logically, it's connected to segment 10. So let's power on that server. So

130
05:27.900 --> 05:28.960
we'll power it on.

131
05:28.960 --> 05:33.300
And then we can verify that it got an IP address via DHCP on that 10 10 zero
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

131
05:28.960 --> 05:33.300
And then we can verify that it got an IP address via DHCP on that 10 10 zero

132
05:33.300 --> 05:34.080
network.

133
05:34.080 --> 05:38.000
Then once we verify that, we can also document what that IP address is. So let

134
05:38.000 --> 05:38.400
me go ahead and

135
05:38.400 --> 05:43.610
right click on that little VM. And we'll click on open remote console. And here

136
05:43.610 --> 05:44.880
it is on its initial

137
05:44.880 --> 05:49.540
boot right here. And this little VM does not have VMware tools. So I'll just be

138
05:49.540 --> 05:49.840
a little bit

139
05:49.840 --> 05:54.190
careful about how I shut it down or powered off because I don't have the VMware

140
05:54.190 --> 05:55.040
tools on this little

141
05:55.040 --> 05:58.830
teeny VM. And as a result, I don't want to just crash it. So here, showing that

142
05:58.830 --> 05:59.520
the IP address is

143
05:59.520 --> 06:02.350
10 10 zero 13, let me make that a little bit bigger. There we go. There's a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

143
05:59.520 --> 06:02.350
10 10 zero 13, let me make that a little bit bigger. There we go. There's a

144
06:02.350 --> 06:03.200
little bit better

145
06:03.200 --> 06:07.740
view of that. So 10 10 zero 13, we could also confirm that by opening up a

146
06:07.740 --> 06:09.120
shell here and verifying it

147
06:09.120 --> 06:12.780
from the command line as well. So if we click down here to open up a shell, and

148
06:12.780 --> 06:13.840
we type in if can

149
06:13.840 --> 06:18.690
fake here, sure enough, our IP address is 10 10 zero 13 if we type in route

150
06:18.690 --> 06:20.000
press enter, our default

151
06:20.000 --> 06:24.470
gateway is 10 10 zero one. So at this point, we should be able to ping 23 dot 1

152
06:24.470 --> 06:25.600
dot 2 dot 60.

153
06:25.600 --> 06:30.040
That's the virtual IP address on our gateway zero. And let me go ahead and put
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

153
06:25.600 --> 06:30.040
That's the virtual IP address on our gateway zero. And let me go ahead and put

154
06:30.040 --> 06:31.360
in a pseudo ping

155
06:31.360 --> 06:36.800
to 23 dot 1 dot 2 dot 60. And that works. And because we're exchanging routing

156
06:36.800 --> 06:37.760
information

157
06:37.760 --> 06:42.500
up with our external gateway, if we try to ping that address 23 dot 1 dot 2 dot

158
06:42.500 --> 06:42.800
1,

159
06:42.800 --> 06:46.250
that should also work as well. That's also a good confirmation that we're

160
06:46.250 --> 06:47.120
advertising our

161
06:47.120 --> 06:52.380
subnets to 10 10 and 10 20 up to our external router, because if we weren't our

162
06:52.380 --> 06:52.960
external router

163
06:52.960 --> 06:55.900
would not have the knowledge of how to forward back. All right, so we can

164
06:55.900 --> 06:56.800
update our topology

165
06:56.800 --> 07:01.230
with those IP addresses, the server based on what we just saw is at dot 13 on
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

165
06:56.800 --> 07:01.230
with those IP addresses, the server based on what we just saw is at dot 13 on

166
07:01.230 --> 07:02.720
the 10 10 zero network.

167
07:02.720 --> 07:08.890
And also a little VM here on the 23 network is at 23 dot 1 dot 2 dot 70. That's

168
07:08.890 --> 07:09.680
its IP address.

169
07:09.680 --> 07:13.280
So in our game plan, we've updated our topology and we have a couple of VMs

170
07:13.280 --> 07:13.520
that we've had

171
07:13.520 --> 07:18.100
for testing. So in our next video, let's go ahead and now implement and test

172
07:18.100 --> 07:19.360
source net for traffic

173
07:19.360 --> 07:24.440
being sourced from VMs down here as they try to go out to the public internet.

174
07:24.440 --> 07:25.040
So I'll see you in

175
07:25.040 --> 07:26.720
the next video for exactly that.

176
07:26.720 --> 07:36.720
[BLANK_AUDIO]