WEBVTT 1 00:00.000 --> 00:04.200 Because these two segment tray are segment 10 on the left and segment 20 right 2 00:04.200 --> 00:08.000 here on the right because they both have a gateway connected to those segments. 3 00:08.000 --> 00:12.260 We have effectively the option of using any one of our three DHP services 4 00:12.260 --> 00:13.000 option. 5 00:13.000 --> 00:16.000 We could set up DHP relay, which we did a couple videos ago. 6 00:16.000 --> 00:20.100 We could set up segment based DHP services on a segment by segment basis or 7 00:20.100 --> 00:22.000 because we have the gateways connected. 8 00:22.000 --> 00:27.000 We now also have a third option and that is gateway based DHP services. 9 00:27.000 --> 00:30.510 And to implement gateway based DHP services, we're going to start off with WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 9 00:27.000 --> 00:30.510 And to implement gateway based DHP services, we're going to start off with 10 00:30.510 --> 00:34.000 network segments which are connected to gateways which we currently have. 11 00:34.000 --> 00:38.120 We're going to use a DHP server profile, which we already have in place, one 12 00:38.120 --> 00:43.000 that points to a server, a logical NSX based DHP server at 673. 13 00:43.000 --> 00:47.200 And then we'll simply use that DHP server for handing out IP addresses to these 14 00:47.200 --> 00:48.000 segments. 15 00:48.000 --> 00:52.330 So from a client's perspective on these networks, it looks like there's a local 16 00:52.330 --> 00:53.000 DHP server. 17 00:53.000 --> 00:56.200 One interesting thing, which will also confirm what they protocol analyzer is 18 00:56.200 --> 01:00.560 that when we set up gateway DHP services, it acts and feels a lot like DHP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 18 00:56.200 --> 01:00.560 that when we set up gateway DHP services, it acts and feels a lot like DHP 19 01:00.560 --> 01:05.000 relay because we're creating or pointing to this logical DHP server. 20 01:05.000 --> 01:08.490 And if we look at the traffic, the traffic is going to look like it sourced 21 01:08.490 --> 01:12.440 from the router interface, the gateway interface connected to the segment being 22 01:12.440 --> 01:17.000 forwarded over that virtual IP address where this logical DHP server lives. 23 01:17.000 --> 01:21.120 And how this differs from the DHP relay is that with DHP relay, we were 24 01:21.120 --> 01:25.730 pointing to an existing external DHP server, where in this case, we're just 25 01:25.730 --> 01:30.000 using a logical DHP server inside of our NSX architecture. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 26 01:30.000 --> 01:34.520 And from a protocol analysis perspective, it's going to look and feel a lot 27 01:34.520 --> 01:38.950 like these gateways acting as DHP relays forwarding their request for DHP 28 01:38.950 --> 01:41.000 services to this DHP server. 29 01:41.000 --> 01:44.600 And then as far as configuring the actual ranges and scopes of IP addresses to 30 01:44.600 --> 01:48.040 use on the subnets, we're going to configure those details on a segment by 31 01:48.040 --> 01:49.000 segment basis. 32 01:49.000 --> 01:52.920 So with that in mind, let's head over to the NSX manager and let's set up 33 01:52.920 --> 01:58.000 gateway based DHP services to support the 10 10 and 10 20 networks. 34 01:58.000 --> 02:01.980 So here in the NSX manager, we're going to go to the networking tab once again, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 34 01:58.000 --> 02:01.980 So here in the NSX manager, we're going to go to the networking tab once again, 35 02:01.980 --> 02:05.000 and let's scroll down and go to networking profiles. 36 02:05.000 --> 02:10.530 And let's just confirm our existing DHP server profile. So this is pointing to 37 02:10.530 --> 02:15.000 a logical DHP server at 6783 with a 29 bit mask. 38 02:15.000 --> 02:19.180 And that's the logical IP address that's going to be used by the NSX logical D 39 02:19.180 --> 02:20.000 HP server. 40 02:20.000 --> 02:24.160 And currently this profile is in use with click here on the one where it says 41 02:24.160 --> 02:27.000 where used, it shows us the segment it's applied to. 42 02:27.000 --> 02:27.840 So because we already have this profile in place, we're simply going to use it 43 02:27.840 --> 02:34.000 again as we implement gateway based DHP services. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 43 02:27.840 --> 02:34.000 again as we implement gateway based DHP services. 44 02:34.000 --> 02:37.380 Let's head over to our tier one gateways and tell them to use this specific 45 02:37.380 --> 02:42.000 profile, which uses this logical IP address for their DHP server. 46 02:42.000 --> 02:45.570 So with networking still selected on the left hand side, we'll click on our 47 02:45.570 --> 02:48.000 tier one gateways and let's edit our gateways. 48 02:48.000 --> 02:52.420 So there's gateway A, we'll click on the three dots, click on edit, and then 49 02:52.420 --> 02:56.000 here where it says DHP config, we'll simply click on set. 50 02:56.000 --> 03:00.450 And then for the type, we use the drop down and choose DHP server, and then we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 50 02:56.000 --> 03:00.450 And then for the type, we use the drop down and choose DHP server, and then we 51 03:00.450 --> 03:03.000 'll choose the DHP server profile. We only have one. 52 03:03.000 --> 03:09.830 And that's our NSX DHP server pointing to an IP address at 6783 with a default 53 03:09.830 --> 03:13.000 lease of 86,400 seconds, which is one day. 54 03:13.000 --> 03:17.550 So we'll click on apply and they'll do that same thing for gateway B once we 55 03:17.550 --> 03:22.000 click on save here and then scroll down and click on close editing. 56 03:22.000 --> 03:26.600 And we'll go ahead and collapse that and we'll modify gateway B. So we'll click 57 03:26.600 --> 03:30.000 on the three dots for gateway B, click on edit from the sub menu. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 58 03:30.000 --> 03:34.230 And then for DHP config, we'll click on set and from here, we'll say we want to 59 03:34.230 --> 03:38.670 go ahead and use the DHP server and specify the profile that points to the 60 03:38.670 --> 03:43.510 logical IP address 6783 with a slash 29 bit mask for the DHP server and click 61 03:43.510 --> 03:44.000 on apply. 62 03:44.000 --> 03:53.350 And then we'll click on save and then we'll scroll down and click on close 63 03:53.350 --> 03:55.000 editing. So now if we went to network topology on the left and we zoomed in a 64 03:55.000 --> 03:55.000 little bit, now we have on gateway A and gateway B two services. 65 03:55.000 --> 03:59.190 One of those is gateway firewall rules, which comes free of charge on these 66 03:59.190 --> 04:03.420 gateways, and then we also have DHP, which we just configured. And the same is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 66 03:59.190 --> 04:03.420 gateways, and then we also have DHP, which we just configured. And the same is 67 04:03.420 --> 04:04.000 true for gateway B. 68 04:04.000 --> 04:08.120 So now that our two gateways are willing to support gateway based DHP services, 69 04:08.120 --> 04:12.450 let's go ahead and tell segment 10 and segment 20 that we want them to go ahead 70 04:12.450 --> 04:14.000 and use those services. 71 04:14.000 --> 04:18.040 So to do that with networking still selected on the left, we'll click on 72 04:18.040 --> 04:22.500 segments and let's edit segment 10 first. So we'll click on the three dots next 73 04:22.500 --> 04:27.490 to segment 10, click on edit, and over here on the right, where it says set DHP 74 04:27.490 --> 04:29.000 config will click that. 75 04:29.000 --> 04:32.570 And then from here, we have three options. And the reason we have three options WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 75 04:29.000 --> 04:32.570 And then from here, we have three options. And the reason we have three options 76 04:32.570 --> 04:37.210 is because this segment is connected to a gateway. So we could do segment DHP 77 04:37.210 --> 04:42.340 services or set up a DHP relay, or in our case, we want to use gateway based D 78 04:42.340 --> 04:43.000 HP server. 79 04:43.000 --> 04:47.190 So we'll click on the gateway DHP server, because we already specified the 80 04:47.190 --> 04:51.960 profile of our NSX DHP server on the gateways. That's already present here is 81 04:51.960 --> 04:56.000 showing us the IP address of the logical DHP server based on our profile. 82 04:56.000 --> 04:59.800 And now it's asking us for the ranges. So we are focused here on the segment 10 83 04:59.800 --> 05:06.130 . So we use a range of 10, 10, 150 through 10.10.0.200. That'll be enough for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 83 04:59.800 --> 05:06.130 . So we use a range of 10, 10, 150 through 10.10.0.200. That'll be enough for 84 05:06.130 --> 05:09.870 the default gateway. It's already provided 10, 10, 01, because that's the IP 85 05:09.870 --> 05:13.000 address on the gateway interface connected to this segment. 86 05:13.000 --> 05:17.030 So that'll be automatically served up to the clients. And for the lease time, I 87 05:17.030 --> 05:20.000 'm going to go ahead and set up a short release of 600 seconds. 88 05:20.000 --> 05:24.170 And then the DNS server, I'm going to hand out 888, just like that. And then if 89 05:24.170 --> 05:27.820 we want to do static bindings, here's also where we would do that and click on 90 05:27.820 --> 05:31.000 static bindings, click on add IPV for static binding. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 90 05:27.820 --> 05:31.000 static bindings, click on add IPV for static binding. 91 05:31.000 --> 05:34.170 And that way you can specify a specific IP address to hand out based on a 92 05:34.170 --> 05:38.160 client specific layer to address. So I'm going to go ahead and leave that blank 93 05:38.160 --> 05:42.000 at the moment, go back to settings, confirm our work and click on apply. 94 05:42.000 --> 05:47.000 Then we'll scroll down, click on save, and click on close editing. Fantastic. 95 05:47.000 --> 05:52.820 So segment 10 now has DHCP services. If we went to network topology and we 96 05:52.820 --> 05:57.460 expanded segment 10 next to segment 20, you'll notice that segment 10 has one 97 05:57.460 --> 05:58.000 service that's DHCP 98 05:58.000 --> 06:02.480 while segment 20 doesn't yet. So let's solve that by going over to segments WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 98 05:58.000 --> 06:02.480 while segment 20 doesn't yet. So let's solve that by going over to segments 99 06:02.480 --> 06:07.230 once again, clicking on the three dots for segment 20 clicking on edit. And 100 06:07.230 --> 06:11.000 then over here on the right, we'll click on set DHCP config right there. 101 06:11.000 --> 06:14.550 Now, let's specify the type of DHP we want to use, and that is gateway based 102 06:14.550 --> 06:18.610 DHCP services, the profiles already associated with our gateways. So that's the 103 06:18.610 --> 06:23.570 one that shows up here. And then there's the DHCP server 6783. And then the 104 06:23.570 --> 06:31.280 range here for segment 20 is going to be 10.20.0.150 through 10.20.0.200. And WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 104 06:23.570 --> 06:31.280 range here for segment 20 is going to be 10.20.0.150 through 10.20.0.200. And 105 06:31.280 --> 06:34.870 then I'll go ahead and use a short release time, like 600 seconds. And then for 106 06:34.870 --> 06:37.000 DNS, we'll use 8.8.8.8. 107 06:37.000 --> 06:41.170 So you want to have multiple DNS servers, simply add multiple DNS servers. And 108 06:41.170 --> 06:44.980 for the default gateway, because this segment is connected to a gateway with a 109 06:44.980 --> 06:50.000 IP address of 10.20.1 that is pre-populated for us right there. 110 06:50.000 --> 06:53.980 And we'll be handed up to the clients as part of DHCP services. So we'll click 111 06:53.980 --> 06:58.900 on apply, scroll down, click on save, and click on close. So as we look at our 112 06:58.900 --> 07:03.000 segments over here where it says subnets, here for this segment based DHCP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 112 06:58.900 --> 07:03.000 segments over here where it says subnets, here for this segment based DHCP 113 07:03.000 --> 07:05.000 services, it says view DHCP config. 114 07:05.000 --> 07:08.020 So if we click on there, it'll show us the details we set up for segment based. 115 07:08.020 --> 07:11.040 And for the two that are gateway based on our subnets, if we click on the IP 116 07:11.040 --> 07:13.000 address here, it's a hyperlink. 117 07:13.000 --> 07:18.070 It'll show us the details for the DHCP services, including the virtual server 118 07:18.070 --> 07:22.800 address, the range involved, the lease, the DNS server, and the default gateway 119 07:22.800 --> 07:23.000 . 120 07:23.000 --> 07:27.000 So we'll click on close. And let me bring back wire shark. And let me go ahead 121 07:27.000 --> 07:31.660 and reset it and minimize that. And let's power on a couple of VMs connected to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 121 07:27.000 --> 07:31.660 and reset it and minimize that. And let's power on a couple of VMs connected to 122 07:31.660 --> 07:33.000 these two segments. 123 07:33.000 --> 07:37.560 So I propose we bring up VM one, which is being hosted on host A. And let's 124 07:37.560 --> 07:42.010 also bring up VM four on a separate subnet here on segment 20, which is being 125 07:42.010 --> 07:45.000 hosted by host B. So VM one and VM four. 126 07:45.000 --> 07:48.890 So I'll power those guys on right now. So here is VM one, I'll launch remote 127 07:48.890 --> 07:52.400 console for that. It's not powered on yet, but we'll bring up both windows, 128 07:52.400 --> 07:54.000 then we'll power them on together. 129 07:54.000 --> 07:58.810 And here is VM four, and we'll launch remote console there. Now, even though 130 07:58.810 --> 08:03.410 these have in their names, the IP addresses that they were using, those are WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 130 07:58.810 --> 08:03.410 these have in their names, the IP addresses that they were using, those are 131 08:03.410 --> 08:09.000 about to change because our gateway DHCP services ranges are from 150 up to 200 132 08:09.000 --> 08:09.000 . 133 08:09.000 --> 08:14.670 And it will no longer be a dot 10. So here is VM one, I'll put that on the left 134 08:14.670 --> 08:19.310 . And here is VM four. And then let's be power these on because they're both D H 135 08:19.310 --> 08:20.000 GP clients. 136 08:20.000 --> 08:24.870 We should see on the transport network, all that captured data. And again, the 137 08:24.870 --> 08:28.820 output's gonna look a lot like D HGP relay services with the local gateways 138 08:28.820 --> 08:32.520 logically routing the request to the server at six dot seven dot eight dot WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 138 08:28.820 --> 08:32.520 logically routing the request to the server at six dot seven dot eight dot 139 08:32.520 --> 08:33.000 three. 140 08:33.000 --> 08:38.760 So let's power on VM one, and we'll power on VM four. So those are both 141 08:38.760 --> 08:43.000 powering up as we speak. So VM one and VM four. Now, good to go. 142 08:43.000 --> 08:48.210 This is still a quick verification with an IF config. And that's at 10 10 0 50 143 08:48.210 --> 08:52.960 VM one is. And if we go over to VM four and do an IF config press center, it's 144 08:52.960 --> 08:55.000 at 10 20 0 150. 145 08:55.000 --> 08:59.780 And just to verify everything's working here on VM one list to a ping to www. 146 08:59.780 --> 09:03.970 google.com. And that's going to verify our default gateway, our routing and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 146 08:59.780 --> 09:03.970 google.com. And that's going to verify our default gateway, our routing and 147 09:03.970 --> 09:05.000 everything else. 148 09:05.000 --> 09:09.960 And just for fun, let's do a trace route to www.google.com. Press center. 149 09:09.960 --> 09:13.650 Fantastic. Just a verify our path. We'll do a control C there. And let's take a 150 09:13.650 --> 09:15.000 look at the packet captures. 151 09:15.000 --> 09:19.240 So for this first one, the source and destination address is showing us the 152 09:19.240 --> 09:23.000 deepest, the most buried IP header information that it has. 153 09:23.000 --> 09:26.750 And so that's being reflected right here. So this is a request, if you will, 154 09:26.750 --> 09:31.900 being sourced from 10 10 0 1, which is the IP address on gateway A that's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 154 09:26.750 --> 09:31.900 being sourced from 10 10 0 1, which is the IP address on gateway A that's 155 09:31.900 --> 09:34.000 connected to segment 10. 156 09:34.000 --> 09:38.670 And it's being sent to that logical IP address of the DHCP server. So we looked 157 09:38.670 --> 09:42.860 at our topology that would be from here going to six dot seven dot eight dot 158 09:42.860 --> 09:48.000 three and again that address is just the logical IP address associated with the 159 09:48.000 --> 09:49.000 NSX DHCP services. 160 09:49.000 --> 09:54.000 And for the request from VM four, that should be sourced from 10 dot 20 dot 0 1 161 09:54.000 --> 09:58.000 and be sent to the logical IP address of the DHCP server. 162 09:58.000 --> 09:58.510 Also, if we look at the transport layer IP addresses involved here, this is 163 09:58.510 --> 10:07.400 from ESXIA at 11 11, et cetera, going to edge one with his tunnel endpoint of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 163 09:58.510 --> 10:07.400 from ESXIA at 11 11, et cetera, going to edge one with his tunnel endpoint of 164 10:07.400 --> 10:10.000 33, et cetera. 165 10:10.000 --> 10:12.970 And then for the offer, notice where it's actually going on the transport 166 10:12.970 --> 10:16.070 network, this is from. And in the offer, it's going to have the information 167 10:16.070 --> 10:18.000 about what's being offered to that client. 168 10:18.000 --> 10:22.400 So there's the IP address being offered. There's the mask. Here's the default 169 10:22.400 --> 10:25.000 gateway of 10 10 0 1. 170 10:25.000 --> 10:30.470 There's the DNS server of 8 8 8 8 and our lease time is 600 seconds. The client WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 170 10:25.000 --> 10:30.470 There's the DNS server of 8 8 8 8 and our lease time is 600 seconds. The client 171 10:30.470 --> 10:34.160 followed that up with a request. That's right here saying I'll take it. So as 172 10:34.160 --> 10:37.000 far as transport goes, that was coming from ESXIA. 173 10:37.000 --> 10:41.540 And then the final acknowledgement from the server, which was from edge one 174 10:41.540 --> 10:43.000 going down to ESXIA. 175 10:43.000 --> 10:47.200 And in the details of this acknowledgement coming back from the server to the 176 10:47.200 --> 10:51.340 client, the client believes that the DHCP server is really at six seven eight 177 10:51.340 --> 10:52.000 three. 178 10:52.000 --> 10:54.810 So then if you take a look at the next discover, this is coming from a VM that 179 10:54.810 --> 10:58.550 's being hosted on ESXIA. So if we take a look at the transport network, this 180 10:58.550 --> 11:01.000 traffic was being sent from ESXIA. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 180 10:58.550 --> 11:01.000 traffic was being sent from ESXIA. 181 11:01.000 --> 11:04.820 Be up to edge one based on the tunnel endpoint addresses. So this is the 182 11:04.820 --> 11:09.000 discover, then there's the offer coming from the edge one back to ESXIA. 183 11:09.000 --> 11:12.350 Be who de encapsulates it, forwards it to the client, then the clients says, I 184 11:12.350 --> 11:16.000 'll take it. That's the request going from the client to the server. 185 11:16.000 --> 11:19.420 And then the final acknowledgement from the server to the client saying, yep, I 186 11:19.420 --> 11:22.850 know you got it. Please enjoy. And then if we wait long enough, because we have 187 11:22.850 --> 11:26.000 a very short lease, the clients are renewing their lease. 188 11:26.000 --> 11:30.100 And that's what's happening right here. So in this request, which is coming WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 188 11:26.000 --> 11:30.100 And that's what's happening right here. So in this request, which is coming 189 11:30.100 --> 11:34.620 from the client at 10 10 0 50 being sent to what it believes is six seven eight 190 11:34.620 --> 11:35.000 three. 191 11:35.000 --> 11:39.240 And behind the scenes, it's being tunneled from ESXIA up to edge one. If we 192 11:39.240 --> 11:43.290 look at the contents for that DHCP request effectively says, Hey, this is my IP 193 11:43.290 --> 11:44.000 address. 194 11:44.000 --> 11:47.340 And can I have it for a little bit longer, at which point the server responds 195 11:47.340 --> 11:50.840 back with the acknowledgement? And as part of that information, we have a lease 196 11:50.840 --> 11:54.000 time, which is set for another 600 seconds. 197 11:54.000 --> 11:58.370 So if we look at the timestamps there between the first and that renewal, that 198 11:58.370 --> 12:03.000 first one happened up here at 167. And then the renewal happened at 464. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 198 11:58.370 --> 12:03.000 first one happened up here at 167. And then the renewal happened at 464. 199 12:03.000 --> 12:07.830 So about 300 seconds. So based on these timestamps, the client did a renewal 200 12:07.830 --> 12:11.510 effectively or a request for a renewal of its IP address at about half of its 201 12:11.510 --> 12:12.000 lease. 202 12:12.000 --> 12:15.930 So the lease was set for 600 seconds. And this client did a renewal about 203 12:15.930 --> 12:20.690 halfway through that lease time. So now that we have configured and verified 204 12:20.690 --> 12:25.280 the three options for working with DHCP services as part of NSX in the next 205 12:25.280 --> 12:26.000 section. 206 12:26.000 --> 12:29.310 I'd like to walk through a few exercises to help validate what we've learned 207 12:29.310 --> 12:32.000 together. So I'll see you there in just a moment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 207 12:29.310 --> 12:32.000 together. So I'll see you there in just a moment. 208 12:32.000 --> 12:42.000 [BLANK_AUDIO]