WEBVTT 1 00:00.000 --> 00:03.560 So at this part of our journey, we're going to go and create the tier one 2 00:03.560 --> 00:04.640 stretch gateway 3 00:04.640 --> 00:07.200 and make it available to both site one and site two. 4 00:07.200 --> 00:08.800 We'll link it to the tier zero gateway. 5 00:08.800 --> 00:12.480 We'll also tell the tier one gateway that we wanted to share any of its 6 00:12.480 --> 00:13.240 directly connected 7 00:13.240 --> 00:16.750 networks like the segment 10 that we'll be adding to make sure we share that up 8 00:16.750 --> 00:16.920 to the 9 00:16.920 --> 00:18.440 tier zero as well. 10 00:18.440 --> 00:22.360 And then we'll create segment 10 and associate it with the tier one gateway. 11 00:22.360 --> 00:25.160 And we'll use the IP dressing space of 10, 10, 0, 0. 12 00:25.160 --> 00:29.840 And we'll give the tier one gateway the address of dot one on that segment. 13 00:29.840 --> 00:31.920 So once again, we'll head up to the global manager. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:29.840 --> 00:31.920 So once again, we'll head up to the global manager. 14 00:31.920 --> 00:35.640 We'll let our tier one gateway and connect the segment to it. 15 00:35.640 --> 00:39.530 So back at the global manager, verifying we're on the right device, we are 16 00:39.530 --> 00:40.480 fantastic. 17 00:40.480 --> 00:44.890 And with the networking tab selected on the left hand side, we'll go down to 18 00:44.890 --> 00:45.720 tier one 19 00:45.720 --> 00:46.720 gateways. 20 00:46.720 --> 00:49.120 So currently we have no tier one gateways anywhere. 21 00:49.120 --> 00:51.640 So we'll click on add tier one gateway. 22 00:51.640 --> 00:55.880 Let's call the stretched tier one and we'll use active standby. 23 00:55.880 --> 00:59.290 And then we'll associate this tier one gateway with our tier zero right above 24 00:59.290 --> 01:00.000 it, which is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 25 01:00.000 --> 01:01.680 the tier zero we created earlier. 26 01:01.680 --> 01:03.120 So we'll associate it there. 27 01:03.120 --> 01:07.200 And then I'm also going to set this up to be preemptive like I did on the tier 28 01:07.200 --> 01:07.280 zero. 29 01:07.280 --> 01:08.680 And then we scroll down. 30 01:08.680 --> 01:13.470 It's already presuming that because site one and site two are already 31 01:13.470 --> 01:14.440 associated with 32 01:14.440 --> 01:17.860 and able to use the tier zero gateway, this tier one gateway that we just 33 01:17.860 --> 01:18.640 connected that 34 01:18.640 --> 01:21.960 tier zero gateway, it also assumes we want to available at both sites. 35 01:21.960 --> 01:25.970 But we could click on a little trash can here and remove it from one or both 36 01:25.970 --> 01:26.600 sites. 37 01:26.600 --> 01:30.600 We don't have to have this new T one gateway available at both sites. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 37 01:26.600 --> 01:30.600 We don't have to have this new T one gateway available at both sites. 38 01:30.600 --> 01:32.960 So because we do want it, we'll leave that in place. 39 01:32.960 --> 01:36.490 Now we also get to choose who gets to be the primary and who gets to be the 40 01:36.490 --> 01:37.480 secondary site 41 01:37.480 --> 01:38.640 one or site two. 42 01:38.640 --> 01:43.460 So to make this consistent with the actual T zero, let me go ahead and set the 43 01:43.460 --> 01:44.240 site one 44 01:44.240 --> 01:47.640 as the primary and set site two as the secondary. 45 01:47.640 --> 01:50.580 And then if you have multiple edge cluster nodes, you can select the one you 46 01:50.580 --> 01:51.480 want to use. 47 01:51.480 --> 01:54.440 So at each site, I only have one edge cluster. 48 01:54.440 --> 01:58.110 So I'll choose that edge cluster for site two and I'll use the respective edge 49 01:58.110 --> 01:58.640 cluster 50 01:58.640 --> 02:02.240 at site one and it'll automatically allocate the edges for that. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 50 01:58.640 --> 02:02.240 at site one and it'll automatically allocate the edges for that. 51 02:02.240 --> 02:06.760 So if you want to specify specific edge nodes within a cluster to go ahead and 52 02:06.760 --> 02:07.440 use, you 53 02:07.440 --> 02:08.920 can go ahead and specify it. 54 02:08.920 --> 02:12.220 So I'm going to say go ahead and auto allocate the edges and then also under 55 02:12.220 --> 02:13.240 route advertisement 56 02:13.240 --> 02:17.900 right here, which simply says, please Mr tier one gateway, please advertise up 57 02:17.900 --> 02:18.240 to your 58 02:18.240 --> 02:22.080 tier zero, any directly connected segments that may come along. 59 02:22.080 --> 02:26.190 So when we start adding segments like the 10 10 network and the 10 20 network, 60 02:26.190 --> 02:26.360 that 61 02:26.360 --> 02:29.890 routing information can be advertised up to the tier zero gateway, which is a 62 02:29.890 --> 02:30.760 good idea. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 62 02:29.890 --> 02:30.760 good idea. 63 02:30.760 --> 02:32.880 So we'll go ahead and set that as well. 64 02:32.880 --> 02:34.420 And let's click on save. 65 02:34.420 --> 02:38.880 So let's click on yes to continue editing and we could further set up the D HCP 66 02:38.880 --> 02:38.880 . 67 02:38.880 --> 02:42.440 However, there's a few additional steps that we need for the D HCP services 68 02:42.440 --> 02:42.680 with D H P 69 02:42.680 --> 02:46.280 relay, including sitting up an additional external interface up at the tier 70 02:46.280 --> 02:46.720 zero. 71 02:46.720 --> 02:48.320 So we'll do that in a separate step. 72 02:48.320 --> 02:50.120 So let me just check our work real quick. 73 02:50.120 --> 02:54.390 So we got site one site to site one primary site to secondary that all looks 74 02:54.390 --> 02:54.960 good. 75 02:54.960 --> 02:56.680 So we'll go ahead and click on close there. 76 02:56.680 --> 02:59.930 And just for a moment, I'm going to go back up to the tier zero gateways and 77 02:59.930 --> 03:01.120 just to confirm WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 77 02:59.930 --> 03:01.120 just to confirm 78 03:01.120 --> 03:04.200 to see which of our two sites is going to be the primary. 79 03:04.200 --> 03:06.800 So I'll click on edit and scroll down. 80 03:06.800 --> 03:11.090 And so for the tier zero gateway as well site one is primary and site two is 81 03:11.090 --> 03:12.040 secondary. 82 03:12.040 --> 03:13.640 So I'll go ahead and close that. 83 03:13.640 --> 03:17.040 And our last piece here was to go ahead and create a segment. 84 03:17.040 --> 03:21.010 So we'll click on segments again here at the NSX global manager and we'll click 85 03:21.010 --> 03:21.480 on add 86 03:21.480 --> 03:22.480 segment. 87 03:22.480 --> 03:25.550 Let's go ahead and call this stretched sag 10 and we'll go ahead and connect 88 03:25.550 --> 03:25.920 this to 89 03:25.920 --> 03:29.320 our tier one gateway right there from the drop down. 90 03:29.320 --> 03:34.040 And then we'll give the logical interface address for the segment of 10 dot 10 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 90 03:29.320 --> 03:34.040 And then we'll give the logical interface address for the segment of 10 dot 10 91 03:34.040 --> 03:34.600 dot zero 92 03:34.600 --> 03:39.270 dot one with a 24 bit mask and for our two sites, it took the overlay transport 93 03:39.270 --> 03:39.640 zone that 94 03:39.640 --> 03:43.940 was identified as the default transport zone and this new segment, which is 95 03:43.940 --> 03:44.680 connected to 96 03:44.680 --> 03:47.880 the tier one gateway, which is being used by both sites. 97 03:47.880 --> 03:51.020 This new segment is going to be associated with those respective transport 98 03:51.020 --> 03:51.480 zones. 99 03:51.480 --> 03:53.840 So we'll scroll down and that looks good. 100 03:53.840 --> 03:56.480 So we'll click on save and then click on no. 101 03:56.480 --> 04:01.070 So now if we were to pop over to the local manager at site one or site two, we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 101 03:56.480 --> 04:01.070 So now if we were to pop over to the local manager at site one or site two, we 102 04:01.070 --> 04:01.400 can get 103 04:01.400 --> 04:03.560 a nice beautiful picture of the topologies. 104 04:03.560 --> 04:05.320 Let's jump over to site two. 105 04:05.320 --> 04:08.520 So from global manager, we use the drop down to site two. 106 04:08.520 --> 04:12.450 Let's go to the networking tab here at the local manager at site two and click 107 04:12.450 --> 04:13.080 on network 108 04:13.080 --> 04:14.000 topology. 109 04:14.000 --> 04:16.440 So from site two's perspective, here is the topology. 110 04:16.440 --> 04:20.800 We have our two external interfaces 24, one, two, sixty one and sixty two. 111 04:20.800 --> 04:23.440 We have our stretch tier zero gateway. 112 04:23.440 --> 04:27.530 If we scroll down, then we have our tier one gateway and that's connected to 113 04:27.530 --> 04:28.240 this segment 114 04:28.240 --> 04:29.520 right here, 10, 10, zero. 115 04:29.520 --> 04:34.070 Now before we start attaching clients here at site one or site two to this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 115 04:29.520 --> 04:34.070 Now before we start attaching clients here at site one or site two to this 116 04:34.070 --> 04:35.040 stretch segment 117 04:35.040 --> 04:38.000 10, I also want to set up DHCP services. 118 04:38.000 --> 04:41.970 So join me in the next video as we implement DHCP services in our NSX 119 04:41.970 --> 04:42.840 federation.