WEBVTT 1 00:00.000 --> 00:04.470 So now that we've had some time to consider these questions and this scenario, 2 00:04.470 --> 00:04.960 let's discuss 3 00:04.960 --> 00:09.020 together a few ideas. Now there's not just one perfect answer. There's several 4 00:09.020 --> 00:09.840 different options 5 00:09.840 --> 00:14.460 that we could use for IP addressing. And here's what I would recommend for 6 00:14.460 --> 00:15.440 various servers. 7 00:15.440 --> 00:20.210 We probably want those to have a specific IP address every single time. So for 8 00:20.210 --> 00:21.040 our servers, 9 00:21.040 --> 00:24.640 it's very likely we're going to have statically configured IP addresses. So we 10 00:24.640 --> 00:25.280 know exactly what 11 00:25.280 --> 00:30.230 they are. Maybe this guy is at dot 11 and this over here is at dot 12. And if WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:25.280 --> 00:30.230 they are. Maybe this guy is at dot 11 and this over here is at dot 12. And if 12 00:30.230 --> 00:30.880 we didn't want to 13 00:30.880 --> 00:34.620 do static addressing, we could also go through the steps of setting up static 14 00:34.620 --> 00:35.760 bindings. Where in 15 00:35.760 --> 00:39.410 our DHCP services, we gather the information on the layer two address or if 16 00:39.410 --> 00:40.240 these are VMs, 17 00:40.240 --> 00:44.870 we can hard code those layer two addresses and then associate those in the HCP 18 00:44.870 --> 00:46.000 with a certain IP 19 00:46.000 --> 00:50.080 address. And that way when they go through the door process, they would get the 20 00:50.080 --> 00:50.960 exact IP address 21 00:50.960 --> 00:54.770 that we wanted them to every single time. But most of the time devices like 22 00:54.770 --> 00:57.120 servers and printers 23 00:57.120 --> 01:02.160 and routers and firewalls, those types of devices are commonly going to have a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 00:57.120 --> 01:02.160 and routers and firewalls, those types of devices are commonly going to have a 24 01:02.160 --> 01:03.120 statically configured 25 01:03.120 --> 01:07.500 IP address. So I'd say as far as options, that is definitely one of our options 26 01:07.500 --> 01:08.320 . The other option, 27 01:08.320 --> 01:13.280 of course, is DHCP assigned addresses. And if we don't care specifically about 28 01:13.280 --> 01:14.240 what IP address 29 01:14.240 --> 01:18.080 they have on a certain subnet, we could just go ahead and just create a pool of 30 01:18.080 --> 01:18.880 addresses and 31 01:18.880 --> 01:23.440 hand out from that pool. So if this is the 10 dot 30 address space, for example 32 01:23.440 --> 01:24.560 , with a 24 bit 33 01:24.560 --> 01:28.420 mask, when we configure DHCP services, we could say, let's hand out, for 34 01:28.420 --> 01:30.080 example, let's say 11, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 34 01:28.420 --> 01:30.080 example, let's say 11, 35 01:30.080 --> 01:32.180 all the way through actually, we probably wouldn't want to do 11 because we're 36 01:32.180 --> 01:32.720 already using that 37 01:32.720 --> 01:38.100 there. So let me back that out and let's say 15 through 254. And that would 38 01:38.100 --> 01:39.120 supply lots and 39 01:39.120 --> 01:43.130 lots of room for our dynamically assigned IP address clients. It would also 40 01:43.130 --> 01:44.480 allow 14 addresses at 41 01:44.480 --> 01:48.640 the front end of that to be used as statically assigned addresses or set up as 42 01:48.640 --> 01:49.520 a reservation. 43 01:49.520 --> 01:54.320 Now also as part of implementing this in an NSX environment, we have if this is 44 01:54.320 --> 01:54.960 a segment and 45 01:54.960 --> 01:59.210 there's no gateway here, what are our options? Well, one option would be we 46 01:59.210 --> 02:00.640 could create our own WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 46 01:59.210 --> 02:00.640 could create our own 47 02:00.640 --> 02:05.030 DHCP server. So we could have a VM that we've connected to that segment. And we 48 02:05.030 --> 02:05.520 could have that 49 02:05.520 --> 02:10.460 local DHCP server hand out IP addresses. And that would not be using the NSX 50 02:10.460 --> 02:11.360 DHCP services, 51 02:11.360 --> 02:15.520 but just the DHCP services on whatever this VM is, maybe it's a Windows machine 52 02:15.520 --> 02:16.720 or Linux machine, 53 02:16.720 --> 02:20.510 or some other platform that provides DHCP services. So that would be one option 54 02:20.510 --> 02:21.680 . Now another option, 55 02:21.680 --> 02:27.040 in an NSX environment would be segment based DHCP services, which we configured 56 02:27.040 --> 02:27.680 as part of our 57 02:27.680 --> 02:30.700 demonstrations up to this point. So if we say, hey, for this segment, let's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 57 02:27.680 --> 02:30.700 demonstrations up to this point. So if we say, hey, for this segment, let's 58 02:30.700 --> 02:31.680 call it segment 30, 59 02:31.680 --> 02:36.490 that we want to use segment based DHCP services, we can logically provide DHCP 60 02:36.490 --> 02:37.600 services for this 61 02:37.600 --> 02:41.300 segment, even though it doesn't have a directly connected gateway to it. Also 62 02:41.300 --> 02:42.560 from an NSX perspective, 63 02:42.560 --> 02:48.200 one thing we could not do is we could not use the NSX flavor DHCP relay. And 64 02:48.200 --> 02:49.360 that's because we 65 02:49.360 --> 02:53.880 don't have any gateways connected to the segment. And as a result, we can't use 66 02:53.880 --> 02:54.880 NSX's flavor of 67 02:54.880 --> 02:58.920 DHCP relay. However, what we could do if we had our own logical device 68 02:58.920 --> 03:00.560 connected here, so let's say WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 68 02:58.920 --> 03:00.560 connected here, so let's say 69 03:00.560 --> 03:04.420 we have a logical router as a VM, and we wanted to implement DHCP relay 70 03:04.420 --> 03:05.920 services on this interface, 71 03:05.920 --> 03:11.180 on that VM, who can then forward the DHCP messages out to the external DHCP 72 03:11.180 --> 03:11.760 server, 73 03:11.760 --> 03:16.830 that would work. However, it also defeats the purpose of a non-routable segment 74 03:16.830 --> 03:17.600 . So if we don't 75 03:17.600 --> 03:22.230 have that router there, that pretty much eliminates any option for DHCP relay 76 03:22.230 --> 03:22.880 services, 77 03:22.880 --> 03:26.160 because we don't have a router connected to that segment. So in conclusion, 78 03:26.160 --> 03:26.880 although there isn't 79 03:26.880 --> 03:31.820 just one exactly perfect answer, I think probably a good solution would be WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 79 03:26.880 --> 03:31.820 just one exactly perfect answer, I think probably a good solution would be 80 03:31.820 --> 03:33.200 static IP addresses 81 03:33.200 --> 03:38.610 on the servers. And then for the DHCP clients in an NSX environment, we can 82 03:38.610 --> 03:40.080 simply use segment-based 83 03:40.080 --> 03:44.620 DHCP services to dynamically hand out the IP addresses to those clients. And 84 03:44.620 --> 03:45.280 based on the other 85 03:45.280 --> 03:50.240 considerations with no gateways connected and non-routable segments, we wouldn 86 03:50.240 --> 03:51.280 't be able to use 87 03:51.280 --> 03:56.320 DHCP relay nor gateway-based DHCP services. Once again, because they're simply 88 03:56.320 --> 03:57.120 not connected over 89 03:57.120 --> 04:01.890 here to the segment. I have had a lot of fun in this set of videos regarding WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 89 03:57.120 --> 04:01.890 here to the segment. I have had a lot of fun in this set of videos regarding 90 04:01.890 --> 04:03.120 DHCP services and 91 04:03.120 --> 04:07.100 an NSX environment, and I look forward to seeing you, my friend, in another set 92 04:07.100 --> 04:08.240 of videos very, 93 04:08.240 --> 04:13.440 very soon. Until then, I hope this has been informative, and I'd like to thank 94 04:13.440 --> 04:14.720 you for viewing.