WEBVTT

1
00:00.000 --> 00:03.120
In this video, you and I get to put a game plan together.

2
00:03.120 --> 00:06.800
So the first game plan is going to be for DHCP relay services.

3
00:06.800 --> 00:11.280
So for DHCP relay, we need an existing DHCP server in our topology.

4
00:11.280 --> 00:12.800
So I currently have one.

5
00:12.800 --> 00:14.680
It's kind of sneaky, but it's right here.

6
00:14.680 --> 00:19.360
This device right here, which is acting as our gateway at 23.1.2.1

7
00:19.360 --> 00:24.400
to the outside world, this device is also acting as a DHCP server.

8
00:24.400 --> 00:28.480
So if this device is acting as our DHCP server for the 1010 network

9
00:28.480 --> 00:32.560
down here in the 1020 network, we need to have a pool or a scope or range of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:28.480 --> 00:32.560
down here in the 1020 network, we need to have a pool or a scope or range of

10
00:32.560 --> 00:33.040
addresses

11
00:33.040 --> 00:35.040
available for each of those subnets.

12
00:35.040 --> 00:37.280
So currently I already have that in place.

13
00:37.280 --> 00:40.290
And we'll double check at this device just to make sure it does have those

14
00:40.290 --> 00:40.800
pools.

15
00:40.800 --> 00:45.360
And it's got another pool or scope of IP addresses for the 10.20 network as

16
00:45.360 --> 00:45.840
well.

17
00:45.840 --> 00:49.440
And then for both of those, the default gateway on each of those respective

18
00:49.440 --> 00:50.080
networks

19
00:50.080 --> 00:52.080
that it's going to be handing out is .1.

20
00:52.080 --> 00:55.810
Also, this device acting as a DHCP server, I believe, and we'll verify that as

21
00:55.810 --> 00:56.160
well.

22
00:56.160 --> 01:00.560
I believe it's also handing out information regarding which DNS server to use.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:56.160 --> 01:00.560
I believe it's also handing out information regarding which DNS server to use.

23
01:00.560 --> 01:04.480
And so we'll verify that that's in place before we start relaying requests up

24
01:04.480 --> 01:04.960
to it.

25
01:04.960 --> 01:10.320
So for DHCP server, the actual real server is at 23.1.2.1.

26
01:10.320 --> 01:14.320
And again, that's this device that's acting as a gateway and also a firewall.

27
01:14.320 --> 01:17.200
And it also is acting as a DHCP server.

28
01:17.200 --> 01:20.080
So as part of our configuration, we'll create a profile that says,

29
01:20.080 --> 01:22.720
hey, the real server is at this IP address.

30
01:22.720 --> 01:26.240
And then we can verify that that works by bringing up clients on these network

31
01:26.240 --> 01:26.640
segments

32
01:26.640 --> 01:31.680
and verify that they're getting IP addresses from that pool up here on our DHCP
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:26.640 --> 01:31.680
and verify that they're getting IP addresses from that pool up here on our DHCP

33
01:31.680 --> 01:32.480
server.

34
01:32.480 --> 01:35.680
And then once we have that in place, we can go ahead and test and verify

35
01:35.680 --> 01:39.040
from clients in either of these subnets to make sure they can dynamically get

36
01:39.040 --> 01:39.920
an IP address,

37
01:39.920 --> 01:44.160
leveraging the actual DHCP server that's in my existing network.

38
01:44.160 --> 01:48.000
So once that's done, I'm going to go ahead and tear that down, remove all the

39
01:48.000 --> 01:49.120
DHCP configuration.

40
01:49.120 --> 01:52.280
And then the next thing I'd like to walk through the configuration and

41
01:52.280 --> 01:53.280
verification of

42
01:53.280 --> 01:56.480
is setting up a segment-based DHCP server.

43
01:56.480 --> 02:00.000
And the use case for this is if we have a segment, let me go ahead and let me
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
02:00.000 --> 02:00.560
use blue here.

45
02:00.560 --> 02:02.400
Let me go ahead and put a segment here.

46
02:02.400 --> 02:05.280
And let's create segment 30, which currently doesn't exist.

47
02:05.280 --> 02:06.640
We'll create it from scratch.

48
02:06.640 --> 02:07.840
It'll be an overlay segment.

49
02:07.840 --> 02:12.160
And then as part of that, we'll configure DHCP services for the segment.

50
02:12.160 --> 02:16.050
And as part of setting up DHCP services for a specific segment with segment-

51
02:16.050 --> 02:17.200
based DHCP services,

52
02:17.200 --> 02:21.120
we're also going to be referring to an IP address for a DHCP server.

53
02:21.120 --> 02:25.760
But this time, it's just going to be a logical DHCP service that lives in the

54
02:25.760 --> 02:26.880
mind of NSX.

55
02:26.880 --> 02:29.120
So we could use any IP address that we wanted to.

56
02:29.120 --> 02:32.240
In fact, if you don't put it in an IP address as part of the profile, it'll
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

56
02:29.120 --> 02:32.240
In fact, if you don't put it in an IP address as part of the profile, it'll

57
02:32.240 --> 02:32.880
just go ahead and

58
02:32.880 --> 02:33.760
make one up for you.

59
02:33.760 --> 02:37.600
So as far as our plan, let's use the IP address for the segment-based DHCP

60
02:37.600 --> 02:41.280
services of 6.7.8.3.

61
02:41.280 --> 02:44.800
And let's throw on a 29-bit mask just to make it a little bit interesting.

62
02:44.800 --> 02:49.360
And for the address based down here, let's use 10.30.0.0.

63
02:49.360 --> 02:52.490
So if we bring up a couple of clients, they should both be able to get IP

64
02:52.490 --> 02:53.920
addresses on the 1030

65
02:53.920 --> 02:58.130
subnet. And we won't have to worry about DNS resolution. And we won't have to

66
02:58.130 --> 02:58.480
worry about a

67
02:58.480 --> 03:03.100
default gateway because there is no logical layer 3 routing happening with this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
02:58.480 --> 03:03.100
default gateway because there is no logical layer 3 routing happening with this

68
03:03.100 --> 03:03.680
segment that we're

69
03:03.680 --> 03:06.940
just going to create as part of the demonstration of setting up segment-based

70
03:06.940 --> 03:07.760
DHCP services.

71
03:07.760 --> 03:11.520
So once we've tested and verified that, we'll remove that configuration.

72
03:11.520 --> 03:16.570
And the third thing I'd like to configure and verify together is gateway-based

73
03:16.570 --> 03:17.600
DHCP services.

74
03:17.600 --> 03:22.310
And that'll support the 1010 network. And we'll also set up to support the 10.

75
03:22.310 --> 03:23.200
20 network.

76
03:23.200 --> 03:26.880
So the 1020 is segment 20 and the 1010 is segment 10.

77
03:26.880 --> 03:30.030
Now, one thing you're going to notice is that when we configure these segment-
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
03:26.880 --> 03:30.030
Now, one thing you're going to notice is that when we configure these segment-

78
03:30.030 --> 03:31.280
based DHCP services

79
03:31.280 --> 03:35.600
for a network segment that has absolutely no gateways connected, we don't even

80
03:35.600 --> 03:36.480
get the option

81
03:36.480 --> 03:41.680
of using a gateway-based DHCP server. Our only option is a segment-based DHCP

82
03:41.680 --> 03:42.000
server.

83
03:42.000 --> 03:45.350
However, when we have the gateways connected to those segments like segment 10

84
03:45.350 --> 03:46.240
and segment 20,

85
03:46.240 --> 03:49.730
we're going to have all of our options available. We can set up relays for

86
03:49.730 --> 03:50.880
those subnets. We can

87
03:50.880 --> 03:54.470
set up segment-based services for those subnets or because we have a gateway

88
03:54.470 --> 03:56.000
attached, we can also

89
03:56.000 --> 03:59.680
use gateway-based DHCP services. And as part of the configuration, it also is

90
03:59.680 --> 04:00.400
going to use
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
03:59.680 --> 04:00.400
going to use

91
04:00.400 --> 04:04.480
a DHCP profile. And so we can actually double up on the profile up here. So we

92
04:04.480 --> 04:05.280
just use the same

93
04:05.280 --> 04:12.160
6.7.8.3 with a 29-bit mask. Now, that IP address is not reachable anywhere yet,

94
04:12.160 --> 04:13.200
but once we created

95
04:13.200 --> 04:17.340
DHCP profile and put it to work in combination with our segments, then that

96
04:17.340 --> 04:18.480
logical IP address

97
04:18.480 --> 04:22.370
becomes reachable and routable inside the mind of our gateways. And we'll

98
04:22.370 --> 04:23.360
verify that as we move

99
04:23.360 --> 04:26.440
forward as well. So as far as our plan as well, as far as ranges of addresses,

100
04:26.440 --> 04:28.400
let's use 150 through

101
04:28.400 --> 04:33.720
200 for the segment 30 with the segment-based DHCP services. And then for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
04:28.400 --> 04:33.720
200 for the segment 30 with the segment-based DHCP services. And then for

102
04:33.720 --> 04:35.040
segment 10, let's

103
04:35.040 --> 04:41.040
use the range of 150 through 200 there as well. And also for the 1027net, which

104
04:41.040 --> 04:41.520
is over here with

105
04:41.520 --> 04:46.670
segment 20, let's use the range of 150 through 200. Also across the board, let

106
04:46.670 --> 04:47.600
's also specify

107
04:47.600 --> 04:51.760
for the gateway-based DHCP services that we want to use for a DNS server. Let's

108
04:51.760 --> 04:52.560
use a Google server

109
04:52.560 --> 04:58.880
at 8.8.8.8. And for the default gateway, we're going to use .1 on each of these

110
04:58.880 --> 04:59.760
respective networks,

111
04:59.760 --> 05:04.630
because that's the IP address here on our gateway-a.1 here on the 1010-0
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
04:59.760 --> 05:04.630
because that's the IP address here on our gateway-a.1 here on the 1010-0

112
05:04.630 --> 05:06.800
network and .1 here over here

113
05:06.800 --> 05:08.240
on the 1020-0 network.

114
05:08.240 --> 05:17.760
[BLANK_AUDIO]