WEBVTT

1
00:00.000 --> 00:03.670
So based on our game plan, we're going to create a couple real quick static

2
00:03.670 --> 00:08.300
bindings as part of DHCP services for our VM web, which is right here.

3
00:08.300 --> 00:13.190
We'll give it the IP address of 10, 10, 0, 10. And then down here VM dash DB,

4
00:13.190 --> 00:15.600
we'll give it the IP address of 10, 20, 0, 20.

5
00:15.600 --> 00:18.590
And again, because these are already DHCP clients, if we set up the

6
00:18.590 --> 00:22.160
reservations for those specific IP addresses based on their layer two Mac

7
00:22.160 --> 00:25.700
addresses, whenever they power up and ask for a DHCP address, they'll be given

8
00:25.700 --> 00:28.400
the IP address that we have set up for their static binding.

9
00:28.400 --> 00:33.200
So to set up the static DHCP bindings, because they're provided courtesy of NSX
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:28.400 --> 00:33.200
So to set up the static DHCP bindings, because they're provided courtesy of NSX

10
00:33.200 --> 00:36.400
, we're going to go to the NSX manager to configure them.

11
00:36.400 --> 00:40.400
So here in the NSX client, one of the quickest and easiest ways of verifying

12
00:40.400 --> 00:44.400
both of their Mac addresses in preparation for setting up static bindings in

13
00:44.400 --> 00:46.400
DHCP would be to use trace flow.

14
00:46.400 --> 00:49.780
So we go to plan and troubleshoot, and we'll be on the left, go down to traffic

15
00:49.780 --> 00:53.400
analysis right there, and then click on getting started with trace flow.

16
00:53.400 --> 00:57.240
From here, we can say, I want to go ahead and do a connectivity test, and I'm

17
00:57.240 --> 01:01.130
going to say from web, going over to the database server, and then showing us
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
00:57.240 --> 01:01.130
going to say from web, going over to the database server, and then showing us

18
01:01.130 --> 01:02.400
the Mac addresses right here.

19
01:02.400 --> 01:05.470
So there's a quick and easy way of getting those. I'm going to go ahead and

20
01:05.470 --> 01:09.520
just right click on the Mac address for VM web, and then copy that and then jot

21
01:09.520 --> 01:10.400
that down.

22
01:10.400 --> 01:15.020
So I've got that documented. I'm also going to go ahead and copy and paste the

23
01:15.020 --> 01:18.400
Mac address that's currently being used by VM dash DB.

24
01:18.400 --> 01:22.620
So I'll right click on it, click on copy, and save that as well. So now that I

25
01:22.620 --> 01:25.720
know what the two Mac addresses are, to set up the DHCP services, we'll go to

26
01:25.720 --> 01:28.400
the networking tab, and then we'll go to the respective segments.

27
01:28.400 --> 01:32.330
So under connectivity, we'll click on segments, and let's start off with
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:28.400 --> 01:32.330
So under connectivity, we'll click on segments, and let's start off with

28
01:32.330 --> 01:35.400
segment 10, and that's where our VM web server is.

29
01:35.400 --> 01:39.850
So we'll double click to edit the details for segment 10, and over here where

30
01:39.850 --> 01:42.400
it says edit DHCP config, that's exactly what we want to do.

31
01:42.400 --> 01:46.210
So we'll click on edit DHCP config, and then we have our tabs under IPv4 server

32
01:46.210 --> 01:50.620
for static bindings. So we'll click on static bindings, and we'll click here to

33
01:50.620 --> 01:52.400
add an IPv4 static binding.

34
01:52.400 --> 01:55.560
And for this name, I'm going to call it DB dash web, and I take that Mac

35
01:55.560 --> 01:58.400
address, which I saved earlier, paste it in right here.

36
01:58.400 --> 02:02.610
And then the IP address I want to give it is 10.10.0.10 based on our plan is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:58.400 --> 02:02.610
And then the IP address I want to give it is 10.10.0.10 based on our plan is

37
02:02.610 --> 02:08.160
default gateway should be 10.10.0.1, and that's the logical interface on our

38
02:08.160 --> 02:11.400
tier one gateway A, and for the host name, I don't need to fill that in.

39
02:11.400 --> 02:15.060
So let's go ahead and also set the lease for a little bit lower. I'll set that

40
02:15.060 --> 02:16.400
the 600 seconds.

41
02:16.400 --> 02:19.800
So even though it depends on the operating system, most DHCP clients are going

42
02:19.800 --> 02:21.400
to renew their lease halfway in.

43
02:21.400 --> 02:25.400
So that'll keep some activity going on at least every 300 seconds.

44
02:25.400 --> 02:28.680
As this client renews its IP address, it'll be given the 10.10.0.10 every

45
02:28.680 --> 02:30.400
single time, assuming this is successful.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
02:28.680 --> 02:30.400
single time, assuming this is successful.

46
02:30.400 --> 02:35.190
So we'll go ahead and click on add, and then click on apply, and scroll down

47
02:35.190 --> 02:36.400
and click on save.

48
02:36.400 --> 02:40.300
And then for the segment, we'll scroll down and click on save, and then click

49
02:40.300 --> 02:41.400
on close editing.

50
02:41.400 --> 02:46.400
And let's do the similar treatment for our database VM, which is on segment 20.

51
02:46.400 --> 02:49.980
So for segment 20, we'll click on the three dots, click on edit, then over on

52
02:49.980 --> 02:53.860
the right, we'll edit the DHCP configuration, and then we'll click on the sub

53
02:53.860 --> 02:56.400
tab here for static bindings, then we'll add a static binding.

54
02:56.400 --> 02:59.400
We'll call this one VM dash DB.

55
02:59.400 --> 03:02.720
I'll take the MAC address that I saved earlier, we'll paste that in, and the IP
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:59.400 --> 03:02.720
I'll take the MAC address that I saved earlier, we'll paste that in, and the IP

56
03:02.720 --> 03:08.040
address we want that database server to have is 10.20.0.20, and its default

57
03:08.040 --> 03:13.020
gateway is going to be the logical segment 20 interface address on gateway B,

58
03:13.020 --> 03:14.400
which is 10.20.0.1.

59
03:14.400 --> 03:19.070
So we'll put that in 10.20.0.1, and for the least time, I'm going to set that

60
03:19.070 --> 03:22.770
to a lower value there for my lab environment, and then we'll go ahead and

61
03:22.770 --> 03:26.770
scroll down and click on add, and then we'll click on apply right there, and

62
03:26.770 --> 03:28.400
then scroll down a little bit, click on save,

63
03:28.400 --> 03:31.790
regarding the segment as a whole, and then we'll scroll down and click on close
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
03:28.400 --> 03:31.790
regarding the segment as a whole, and then we'll scroll down and click on close

64
03:31.790 --> 03:32.400
editing.

65
03:32.400 --> 03:35.750
So because I only have a 600 second lease and the client should be renewing

66
03:35.750 --> 03:39.720
their lease, at least every 300 seconds, if I've waited long enough, those

67
03:39.720 --> 03:44.040
clients should automatically have their newly assigned IP addresses of 10.10.0.

68
03:44.040 --> 03:46.400
10, and 10.20.0.20.

69
03:46.400 --> 03:50.470
So one easy way to verify that is we could go once again to plan and troublesh

70
03:50.470 --> 03:54.650
oot, and go down to traffic analysis, go to trace flow, click here and get

71
03:54.650 --> 04:01.510
started, and then from here specify VM web on the left, and on the right, VMDB,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
03:54.650 --> 04:01.510
started, and then from here specify VM web on the left, and on the right, VMDB,

72
04:01.510 --> 04:03.400
and they currently have the old addresses.

73
04:03.400 --> 04:07.500
So let me power off and power on those VMs, and when they come up, they should

74
04:07.500 --> 04:09.400
get the newly assigned IP address.

75
04:09.400 --> 04:13.150
So back to the vSphere client we go, let's grab these two, and I'll right click

76
04:13.150 --> 04:17.130
, and they are both running VMware tools, so click on power, and let me shut

77
04:17.130 --> 04:20.900
them both down, gracefully click on yes, and we'll give that a moment to

78
04:20.900 --> 04:21.400
complete.

79
04:21.400 --> 04:24.660
Fantastic, they're both powered off, so I'll right click, and let's power them

80
04:24.660 --> 04:28.790
both back on, and we'll also verify that they have the IP addresses that we

81
04:28.790 --> 04:31.400
statically bound for them via DHCP services.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
04:28.790 --> 04:31.400
statically bound for them via DHCP services.

82
04:31.400 --> 04:37.840
So VM web should be 10 10 0 10, and VM dash DB should be 10 20 0 20, if that's

83
04:37.840 --> 04:39.400
how we configured it.

84
04:39.400 --> 04:41.400
So let's open up consoles for each of those.

85
04:41.400 --> 04:44.400
Let's open up a console for VM web.

86
04:44.400 --> 04:48.000
So here's VM web in the upper left hand corner just to confirm we're on the

87
04:48.000 --> 04:51.440
right device VM dash web, and if we do an I have config for Ethan at zero and

88
04:51.440 --> 04:54.400
press enter, it's got the address 10 10 0 10.

89
04:54.400 --> 04:59.620
And from here, if we did a ping over to 10 dot 20 dot 0 dot 20 and press enter,

90
04:59.620 --> 05:03.970
if that works, that also implies a little control see there's stop that, that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
04:59.620 --> 05:03.970
if that works, that also implies a little control see there's stop that, that

91
05:03.970 --> 05:09.400
also implies that VM dash DB has the IP address 10 20 0 20, but let's verify

92
05:09.400 --> 05:09.400
that as well.

93
05:09.400 --> 05:13.270
So back in the vSphere client will go to VM dash DB will open up a web console

94
05:13.270 --> 05:17.670
to that, and we'll do an I have config for ethernet zero, and sure enough it's

95
05:17.670 --> 05:23.400
10 20 20, and just for funless ping 10 dot 10 dot 10, and that looks great.

96
05:23.400 --> 05:28.570
So now we have a specific IP address on VM web of 10 10 0 10 and a specific IP

97
05:28.570 --> 05:32.400
address on VM dash DB up 10 dot 20 dot 0 dot 20.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

97
05:28.570 --> 05:32.400
address on VM dash DB up 10 dot 20 dot 0 dot 20.

98
05:32.400 --> 05:36.120
So now that we have our VMS in place and we have a couple static bindings for a

99
05:36.120 --> 05:37.400
couple of our servers.

100
05:37.400 --> 05:41.920
In the next video, let's set up our tags and assign those tags to our various V

101
05:41.920 --> 05:42.400
MS.

102
05:42.400 --> 05:45.400
So I'll see you in the next video for exactly that.