WEBVTT 1 00:00.210 --> 00:01.440 So, list together, 2 00:01.440 --> 00:03.060 now that we had a moment to think about it, 3 00:03.060 --> 00:06.900 let's list out a few of the benefits of VMware's software 4 00:06.900 --> 00:09.450 to find networking with their product called NSX. 5 00:09.450 --> 00:11.760 One of the benefits is the ability 6 00:11.760 --> 00:15.360 to have a common layer two segment. 7 00:15.360 --> 00:16.590 And if we told that to the customer 8 00:16.590 --> 00:18.270 and they said, "Well, we have layer two segments already. 9 00:18.270 --> 00:19.890 We have, you know, distribute a switch, 10 00:19.890 --> 00:22.890 we have four or five VMs, all the same port group, 11 00:22.890 --> 00:23.940 and they're in the same segment." 12 00:23.940 --> 00:25.980 But that's if, on our transport 13 00:25.980 --> 00:28.980 or underlay networks, we have those two ESXI hosts 14 00:28.980 --> 00:30.565 that are hosting the VMs, able to reach WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 14 00:28.980 --> 00:30.565 that are hosting the VMs, able to reach 15 00:30.565 --> 00:33.270 that same layer two broadcast domains. 16 00:33.270 --> 00:35.850 So with NSX, even if we have two ESXI hosts, 17 00:35.850 --> 00:38.580 we have one over here at this end of the data center 18 00:38.580 --> 00:41.370 in a rack, we have one over here in a different rack, 19 00:41.370 --> 00:43.530 and we have lots of routing between them. 20 00:43.530 --> 00:45.360 So here's a router, there's a router. 21 00:45.360 --> 00:48.270 We can still have a common layer two segment, 22 00:48.270 --> 00:49.500 an overlay segment 23 00:49.500 --> 00:51.840 that those VMs can go ahead and connect to. 24 00:51.840 --> 00:54.960 And then behind the scenes, these two ESXI hosts can tunnel 25 00:54.960 --> 00:56.640 that traffic back and forth. 26 00:56.640 --> 00:58.798 So we have a tunnel endpoint over on the host on the left, 27 00:58.798 --> 01:01.620 and a tunnel endpoint over on the host on the right. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 27 00:58.798 --> 01:01.620 and a tunnel endpoint over on the host on the right. 28 01:01.620 --> 01:03.930 So this is host A and this is host B. 29 01:03.930 --> 01:06.960 And even though they're not on the transport network 30 01:06.960 --> 01:09.210 directly connected to the same layer two broadcast demand 31 01:09.210 --> 01:11.224 or the same vlan, the little VMs who are connected 32 01:11.224 --> 01:13.819 to the overlay segment can look and feel 33 01:13.819 --> 01:16.890 like they're on the same layer two broadcast domain. 34 01:16.890 --> 01:20.580 So this could be 10.10.0.10 over here, 35 01:20.580 --> 01:24.960 and we have 10.10.0.11 here on the same IP subnet 36 01:24.960 --> 01:28.560 because they're also on the same layer two broadcast domain 37 01:28.560 --> 01:32.340 courtesy of this logical segment provided by NSX. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 37 01:28.560 --> 01:32.340 courtesy of this logical segment provided by NSX. 38 01:32.340 --> 01:35.070 So I would say that would be one of the benefits. 39 01:35.070 --> 01:37.170 We can have logical layer two segments 40 01:37.170 --> 01:40.050 across the entire data center wherever we need them to be, 41 01:40.050 --> 01:42.570 without having to have the actual underlay network. 42 01:42.570 --> 01:43.740 And the ESXI hosts 43 01:43.740 --> 01:46.860 connected to that underlay network in the same exact VLAN. 44 01:46.860 --> 01:48.390 So I'll make a little note up here. 45 01:48.390 --> 01:51.600 Layer two segments across routed networks. 46 01:51.600 --> 01:54.300 Another big benefit that NSX can bring to the table 47 01:54.300 --> 01:55.680 is regarding security. 48 01:55.680 --> 01:59.464 So if we wanted to control what is or isn't allowed between, 49 01:59.464 --> 02:02.700 for example, this VM, we'll call it VM1 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 49 01:59.464 --> 02:02.700 for example, this VM, we'll call it VM1 50 02:02.700 --> 02:04.320 and this VM, VM2, 51 02:04.320 --> 02:06.630 even though they're on the same layer two broadcast domain 52 02:06.630 --> 02:09.523 and the same subnet, with NSX, we can now control very, 53 02:09.523 --> 02:13.454 very granularly what is allowed between those two VMs. 54 02:13.454 --> 02:17.820 For example, we wanna allow TCP traffic if it's HTTPS, 55 02:17.820 --> 02:19.230 or do we wanna allow ICMP, 56 02:19.230 --> 02:21.360 or if this is an application server, 57 02:21.360 --> 02:24.120 and this is a database server, we can specifically permit 58 02:24.120 --> 02:26.130 or deny certain types of traffic flows 59 02:26.130 --> 02:27.480 between those two VMs. 60 02:27.480 --> 02:29.277 Another big benefit is routing. 61 02:29.277 --> 02:32.776 Now, in the case of routing, if we want to implement routing WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 61 02:29.277 --> 02:32.776 Now, in the case of routing, if we want to implement routing 62 02:32.776 --> 02:34.830 within our NSX environment, 63 02:34.830 --> 02:35.940 we can do exactly that. 64 02:35.940 --> 02:38.850 We can have a router here and here and here, 65 02:38.850 --> 02:41.010 and then a network segment here, 66 02:41.010 --> 02:42.450 another network segment here, 67 02:42.450 --> 02:44.160 and a third network segment there, 68 02:44.160 --> 02:45.870 and then route everywhere between them. 69 02:45.870 --> 02:48.210 And this is all without having to touch 70 02:48.210 --> 02:51.480 a physical piece of hardware for routing. 71 02:51.480 --> 02:54.030 So all this routing, especially the east west traffic, 72 02:54.030 --> 02:57.630 can all be done inside of NSX in software. 73 02:57.630 --> 02:59.010 And in addition to routing, 74 02:59.010 --> 03:01.020 we can also provide other IP services, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 74 02:59.010 --> 03:01.020 we can also provide other IP services, 75 03:01.020 --> 03:05.460 including things like DHCP services and VPN, 76 03:05.460 --> 03:07.920 and we can set up gateway firewall services, 77 03:07.920 --> 03:10.530 and other services like network address translation. 78 03:10.530 --> 03:12.000 And all of that can be implemented right here 79 03:12.000 --> 03:14.280 inside of NSX in software. 80 03:14.280 --> 03:16.350 So the way that would play out is that you and I 81 03:16.350 --> 03:18.600 would log into the NSX manager. 82 03:18.600 --> 03:20.610 We would configure what we wanna go ahead 83 03:20.610 --> 03:22.170 and have implemented in NSX. 84 03:22.170 --> 03:23.790 And also there's various options 85 03:23.790 --> 03:25.590 for working with NSX manager. 86 03:25.590 --> 03:27.750 So here is our NSX manager, 87 03:27.750 --> 03:30.300 it's very likely we're gonna have a cluster of those WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 87 03:27.750 --> 03:30.300 it's very likely we're gonna have a cluster of those 88 03:30.300 --> 03:32.190 so that we have some fault tolerance. 89 03:32.190 --> 03:35.640 So this would be NSX Manager, one and two, and three, 90 03:35.640 --> 03:38.220 all configured as an NSX management cluster, 91 03:38.220 --> 03:39.720 as a virtual IP address. 92 03:39.720 --> 03:41.670 So you and I can connect to that virtual IP address, 93 03:41.670 --> 03:43.890 for example, that's reachable on the management network. 94 03:43.890 --> 03:45.960 So here's the computer that we're sitting at, 95 03:45.960 --> 03:47.640 we connect to that IP address to the browser, 96 03:47.640 --> 03:48.810 and then it's gonna associate that 97 03:48.810 --> 03:51.540 with one of our NSX managers, so we can go ahead 98 03:51.540 --> 03:53.190 and get the graphical user interface. 99 03:53.190 --> 03:55.110 So that's one of our options for working with 100 03:55.110 --> 03:56.340 and managing NSX. 101 03:56.340 --> 03:58.710 And now, another option also is we could get 102 03:58.710 --> 04:00.450 a plugin for vCenter. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 102 03:58.710 --> 04:00.450 a plugin for vCenter. 103 04:00.450 --> 04:02.460 So we have our vCenter server appliance, 104 04:02.460 --> 04:05.820 and within vCenter we could have a NSX plugin. 105 04:05.820 --> 04:08.160 And then that way we could just log into the vSphere client. 106 04:08.160 --> 04:09.750 And then within vSphere client, 107 04:09.750 --> 04:11.100 there's additional controls 108 04:11.100 --> 04:12.660 that we can use to implement control 109 04:12.660 --> 04:14.790 and set up our NSX world as well. 110 04:14.790 --> 04:17.040 And for most of the configuration and demonstrations 111 04:17.040 --> 04:19.020 that we're gonna use together in this course, 112 04:19.020 --> 04:21.930 we're gonna be managing the NSX GUI interface 113 04:21.930 --> 04:23.028 directly on the NSX manager 114 04:23.028 --> 04:25.860 as opposed to using the plugin inside of vCenter. 115 04:25.860 --> 04:27.630 Although at the end of the day, 116 04:27.630 --> 04:30.420 the functionality is the same whether we're configuring WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 116 04:27.630 --> 04:30.420 the functionality is the same whether we're configuring 117 04:30.420 --> 04:33.750 security, or DHCP services, or routing. 118 04:33.750 --> 04:34.740 And those are all functions 119 04:34.740 --> 04:36.690 and features that a customer can use 120 04:36.690 --> 04:39.600 by leveraging NSX in their environment. 121 04:39.600 --> 04:42.360 So thanks for taking an extra moment in this set of videos 122 04:42.360 --> 04:45.420 to pause and help reconfirm our understanding. 123 04:45.420 --> 04:46.500 And when you're ready, my friend, 124 04:46.500 --> 04:48.390 I'll see you in the very next skill. 125 04:48.390 --> 04:50.820 Until then, I hope this has been informative 126 04:50.820 --> 04:53.283 and I'd like to thank you for viewing.