WEBVTT 1 00:00.000 --> 00:05.260 All right, so based on our game plan, I want to use VLAN 23 as my edge segment 2 00:05.260 --> 00:06.000 and connect 3 00:06.000 --> 00:09.830 over here to this external router, which is also on VLAN 23, and change my 4 00:09.830 --> 00:10.360 addressing 5 00:10.360 --> 00:16.100 scheme on that external segment to be 2312 and .61 for edge one and .62 for 6 00:16.100 --> 00:17.120 edge two. 7 00:17.120 --> 00:20.810 So let's head over to the NSX manager and update our configuration regarding 8 00:20.810 --> 00:21.600 our topology 9 00:21.600 --> 00:23.200 and gateway zero. 10 00:23.200 --> 00:26.930 So we'll start off by going to networking, going down to our tier zero gateway 11 00:26.930 --> 00:27.440 here in 12 00:27.440 --> 00:32.090 the NSX manager, and I currently over here have a status of down and that's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 12 00:27.440 --> 00:32.090 the NSX manager, and I currently over here have a status of down and that's 13 00:32.090 --> 00:32.560 probably 14 00:32.560 --> 00:34.160 because I made a few changes in the background. 15 00:34.160 --> 00:38.920 So let's clean this all up and get the new external segment from VLAN 23. 16 00:38.920 --> 00:42.760 So to do that, we're going to click on the three dots for our tier zero, click 17 00:42.760 --> 00:43.520 on edit, 18 00:43.520 --> 00:47.420 and first of all, I'm going to take off this HA virtual IP address because it's 19 00:47.420 --> 00:48.060 currently 20 00:48.060 --> 00:51.590 using the address of 192.1 state 160, which is not going to be correct for our 21 00:51.590 --> 00:52.280 new subnet. 22 00:52.280 --> 00:55.880 So I go ahead and delete that and then click on apply. 23 00:55.880 --> 00:57.720 And now let's go through the step by step. 24 00:57.720 --> 01:00.200 So let me click on save before we continue. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 00:57.720 --> 01:00.200 So let me click on save before we continue. 25 01:00.200 --> 01:01.640 So here I've got two interfaces. 26 01:01.640 --> 01:05.760 We'll go ahead and click on to there and these two are on the wrong subnets. 27 01:05.760 --> 01:07.720 And so we'll go ahead and let's go ahead and delete both of those. 28 01:07.720 --> 01:11.160 So delete that first one, click on delete, then I'll go ahead and click on 29 01:11.160 --> 01:11.640 refresh, 30 01:11.640 --> 01:13.160 give me a nice clean view. 31 01:13.160 --> 01:17.290 We'll delete the second interface there, delete perfect, and then we'll click 32 01:17.290 --> 01:18.160 on refresh. 33 01:18.160 --> 01:19.160 Great, great, great. 34 01:19.160 --> 01:22.520 It'll click on close and scroll down, click on close. 35 01:22.520 --> 01:26.770 And now we no longer have a virtual interface address in the wrong subnet and 36 01:26.770 --> 01:27.560 we also have 37 01:27.560 --> 01:28.720 no interfaces. 38 01:28.720 --> 01:32.690 So if we want to connect this gateway to the 23 subnet for its external WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 38 01:28.720 --> 01:32.690 So if we want to connect this gateway to the 23 subnet for its external 39 01:32.690 --> 01:33.520 connection to the 40 01:33.520 --> 01:35.760 next hop router, we need to have that segment. 41 01:35.760 --> 01:37.100 So let's go to segments. 42 01:37.100 --> 01:41.210 So under networking and segments, and there's our current segment, if we expand 43 01:41.210 --> 01:41.400 that, it's 44 01:41.400 --> 01:44.240 currently using VLAN zero, no tagging at all. 45 01:44.240 --> 01:47.650 So we could just edit this or we could just create a new, in fact, let's just 46 01:47.650 --> 01:47.960 delete the 47 01:47.960 --> 01:51.520 old one, we'll click on delete, get rid of it, we're not using it anymore. 48 01:51.520 --> 01:52.880 And let's create a new one. 49 01:52.880 --> 01:56.040 So we'll click refresh there and there's our two existing segments. 50 01:56.040 --> 01:59.160 Let's create a VLAN back segment for VLAN 23. 51 01:59.160 --> 02:00.160 So we'll click on add segment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 51 01:59.160 --> 02:00.160 So we'll click on add segment. 52 02:00.160 --> 02:04.120 I'm going to call this VLAN 23 and then just for grands, put 23.1.2. 53 02:04.120 --> 02:07.600 So when I see it, I'll not exactly where that segment goes and the IP address 54 02:07.600 --> 02:08.240 associated 55 02:08.240 --> 02:09.240 with it. 56 02:09.240 --> 02:11.900 And then I'm not going to specify right here a connected gateway because once 57 02:11.900 --> 02:12.320 we create 58 02:12.320 --> 02:16.360 the segment and we specify the transport zone, which is going to be our VLAN 59 02:16.360 --> 02:17.320 backed transport 60 02:17.320 --> 02:18.320 zone. 61 02:18.320 --> 02:21.810 And also right here with a little asterisk says, hey, specify which VLAN this 62 02:21.810 --> 02:22.480 is going to 63 02:22.480 --> 02:23.480 support. 64 02:23.480 --> 02:25.560 So I'm going to go ahead and support just the VLAN 23. 65 02:25.560 --> 02:29.180 And so now that we have this new VLAN backed segment without a gateway 66 02:29.180 --> 02:30.200 connected, we'll WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 66 02:29.180 --> 02:30.200 connected, we'll 67 02:30.200 --> 02:33.810 scroll down, we'll click on save and then click on no because we're done config 68 02:33.810 --> 02:34.160 uring 69 02:34.160 --> 02:35.160 right here that segment. 70 02:35.160 --> 02:38.930 Then we'll go to our gateway zero and say, hey, let's go ahead and have you 71 02:38.930 --> 02:39.560 connect to 72 02:39.560 --> 02:44.480 this segment, VLAN 23, and we'll connect via edge one and edge two. 73 02:44.480 --> 02:48.080 So to do that, we'll click here on our tier zero gateways, expand this. 74 02:48.080 --> 02:52.310 And we'll click on the three dots here, click on edit and let's scroll down and 75 02:52.310 --> 02:52.680 let's go 76 02:52.680 --> 02:54.160 down to interfaces. 77 02:54.160 --> 02:58.190 So for external and service interfaces, we'll click on set and we'll click on 78 02:58.190 --> 02:59.280 add interface. 79 02:59.280 --> 03:04.910 And for the first one, I'll say it's dot 61 edge one VLAN 23 just to remind WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 79 02:59.280 --> 03:04.910 And for the first one, I'll say it's dot 61 edge one VLAN 23 just to remind 80 03:04.910 --> 03:05.840 myself of 81 03:05.840 --> 03:06.840 what it's for. 82 03:06.840 --> 03:08.800 So that's going to be this logical interface. 83 03:08.800 --> 03:11.680 I'm going to copy that because we're going to use that very similar syntax 84 03:11.680 --> 03:12.080 again. 85 03:12.080 --> 03:15.900 And then for the actual address of this logical interface, it's going to be 23. 86 03:15.900 --> 03:17.400 1.2.61 based 87 03:17.400 --> 03:20.080 on our plan with a 24-bit mask. 88 03:20.080 --> 03:23.700 And then the segment we're going to connect to is our VLAN 23 segment we just 89 03:23.700 --> 03:24.320 created. 90 03:24.320 --> 03:27.790 And then for the edge node, we'll go ahead and choose edge one and that looks 91 03:27.790 --> 03:28.280 good. 92 03:28.280 --> 03:32.340 So we'll go ahead and scroll down, click on save, and then we'll click on add WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 92 03:28.280 --> 03:32.340 So we'll go ahead and scroll down, click on save, and then we'll click on add 93 03:32.340 --> 03:33.080 interface. 94 03:33.080 --> 03:34.080 We'll do it again. 95 03:34.080 --> 03:39.240 I'll paste in that name, but this one will be dot 62 and it'll be on edge two. 96 03:39.240 --> 03:44.510 So then I'll specify for this IP address, we're going to be 23.1.2.62 with a 24 97 03:44.510 --> 03:44.880 -bit 98 03:44.880 --> 03:48.510 mask, and for the segment we're connecting to is that same external segment V 99 03:48.510 --> 03:49.200 LAN 23. 100 03:49.200 --> 03:51.280 And then for the edge node, we're going to use for that. 101 03:51.280 --> 03:54.040 We're going to go ahead and use edge two just like that. 102 03:54.040 --> 03:55.040 That all looks good. 103 03:55.040 --> 03:58.280 We'll scroll down, click on save, and click on close. 104 03:58.280 --> 04:01.630 And then before we're done here, while we're sitting here at Gateway Zero, let WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 104 03:58.280 --> 04:01.630 And then before we're done here, while we're sitting here at Gateway Zero, let 105 04:01.630 --> 04:02.240 's also make 106 04:02.240 --> 04:04.560 sure our OSPF is configured correctly. 107 04:04.560 --> 04:07.430 So for the interfaces that are set for OSPF, we have none because we deleted 108 04:07.430 --> 04:07.880 the other 109 04:07.880 --> 04:10.240 two interfaces on that 192 network. 110 04:10.240 --> 04:14.400 So let's click on set here and let's click configure interface for OSPF. 111 04:14.400 --> 04:17.440 And let's choose the interface on edge one. 112 04:17.440 --> 04:18.880 We'll put it in area zero. 113 04:18.880 --> 04:21.720 We'll leave all the other defaults, click on save. 114 04:21.720 --> 04:23.920 And then we'll do it again by clicking on configure interface. 115 04:23.920 --> 04:26.720 We'll go ahead and add that second interface. 116 04:26.720 --> 04:29.640 Also put it on area zero and click on save. 117 04:29.640 --> 04:32.720 So now we have these two interfaces enabled for OSPF. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 117 04:29.640 --> 04:32.720 So now we have these two interfaces enabled for OSPF. 118 04:32.720 --> 04:34.200 Click on refresh over there. 119 04:34.200 --> 04:37.840 Click on close, scroll down, and then we'll click on close editing. 120 04:37.840 --> 04:39.520 And then we'll just click on refresh here. 121 04:39.520 --> 04:44.080 So I've already got the OSPF configured on a little external router. 122 04:44.080 --> 04:45.600 And that's this guy right here. 123 04:45.600 --> 04:49.790 So if that is configured with OSPF and we just configured the two interfaces 124 04:49.790 --> 04:50.280 here on 125 04:50.280 --> 04:55.000 tier zero and we enabled OSPF, we should be able to see that OSPF adjacency 126 04:55.000 --> 04:55.920 right here. 127 04:55.920 --> 04:58.800 We can see that from the external router or in our case because we're right 128 04:58.800 --> 04:59.320 here at 129 04:59.320 --> 05:03.300 the tier zero device, we could go ahead and look at the OSPF neighbors here as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 129 04:59.320 --> 05:03.300 the tier zero device, we could go ahead and look at the OSPF neighbors here as 130 05:03.300 --> 05:03.840 well. 131 05:03.840 --> 05:06.680 So to do that, I also see I have a status of down over here. 132 05:06.680 --> 05:08.080 We'll take a look at that in just a moment. 133 05:08.080 --> 05:12.850 So if we expand our tier zero gateway, scroll down and then in the OSPF section 134 05:12.850 --> 05:13.520 expanded 135 05:13.520 --> 05:14.840 if it's not already expanded. 136 05:14.840 --> 05:16.600 So make sure that's expanded. 137 05:16.600 --> 05:20.480 And then down here under OSPF neighbors, we'll click on view and that looks 138 05:20.480 --> 05:21.400 pretty good. 139 05:21.400 --> 05:24.040 So this is edge one, the first two. 140 05:24.040 --> 05:26.850 First one we're pairing with the edge router and the second one here, we're 141 05:26.850 --> 05:27.480 pairing with 142 05:27.480 --> 05:30.710 edge two and then from edge two's perspective, we're pairing with the edge WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 142 05:27.480 --> 05:30.710 edge two and then from edge two's perspective, we're pairing with the edge 143 05:30.710 --> 05:31.480 router and then 144 05:31.480 --> 05:34.240 this one we're pairing over with edge one. 145 05:34.240 --> 05:37.100 So we're on the full state with the external router and we're in the two way 146 05:37.100 --> 05:37.640 state with 147 05:37.640 --> 05:41.080 each other, meaning edge one and edge two, which looks good. 148 05:41.080 --> 05:44.740 Oh, this still says down and it says I have an alarm link click on the alarm 149 05:44.740 --> 05:44.920 and this 150 05:44.920 --> 05:48.120 shows me for alarms, I have no open alarms. 151 05:48.120 --> 05:49.120 Hmm. 152 05:49.120 --> 05:50.120 All right. 153 05:50.120 --> 05:51.120 So maybe we just need the screen to refresh. 154 05:51.120 --> 05:52.120 I'll click refresh here. 155 05:52.120 --> 05:53.800 Oh, that looks better, much better. 156 05:53.800 --> 05:56.950 And then just to double check, let's go ahead and head over to one of our edge 157 05:56.950 --> 05:57.360 nodes. 158 05:57.360 --> 05:59.720 In fact, let's take a look at which one's active. 159 05:59.720 --> 06:03.250 So good in network topology, we'll double click on gateway zero and here we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 159 05:59.720 --> 06:03.250 So good in network topology, we'll double click on gateway zero and here we 160 06:03.250 --> 06:03.800 have edge 161 06:03.800 --> 06:04.800 one that's active. 162 06:04.800 --> 06:07.970 So let's head over to edge one and take a look at the routing tables for our 163 06:07.970 --> 06:08.560 distributed 164 06:08.560 --> 06:12.160 routing and service route environment from the perspective of edge one. 165 06:12.160 --> 06:14.880 So here is edge one, let's do a gate gateways. 166 06:14.880 --> 06:19.600 So here is our services router now in VRF six, so we'll type in VRF six. 167 06:19.600 --> 06:22.880 So now based on our prompt, we are in the services router specifically in VRF 168 06:22.880 --> 06:24.280 six, fantastic. 169 06:24.280 --> 06:26.320 And from here, let's do a get route and press enter. 170 06:26.320 --> 06:27.600 Oh, and this looks great. 171 06:27.600 --> 06:32.540 So we are dynamically learning a default route and that is coming in from our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 171 06:27.600 --> 06:32.540 So we are dynamically learning a default route and that is coming in from our 172 06:32.540 --> 06:33.400 edge router 173 06:33.400 --> 06:35.800 at 23.1.2.1. 174 06:35.800 --> 06:38.400 And there's the default route that it's advertising to us. 175 06:38.400 --> 06:41.080 Also, we do a get interfaces here on this router. 176 06:41.080 --> 06:44.640 In fact, let me go ahead and do that again with a pipe and a more. 177 06:44.640 --> 06:46.240 So we can do one page at a time. 178 06:46.240 --> 06:51.480 So here in VRF six, I've got some interfaces regarding black hole and CPUs. 179 06:51.480 --> 06:54.840 I've got an interface here on the back plane from the services router. 180 06:54.840 --> 06:59.420 If we press enter a few times, here is my logical interface on edge one that 181 06:59.420 --> 06:59.800 connects 182 06:59.800 --> 07:02.720 to VLAN 23 with its respective IP address. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 182 06:59.800 --> 07:02.720 to VLAN 23 with its respective IP address. 183 07:02.720 --> 07:04.560 If we press enter a few more times. 184 07:04.560 --> 07:05.920 But edge one is the active router. 185 07:05.920 --> 07:07.240 And that's why that's showing up here. 186 07:07.240 --> 07:09.600 And then I also have a loop back address. 187 07:09.600 --> 07:12.060 Now in this output, it's now moved on to VRF number one, which is the 188 07:12.060 --> 07:12.760 distributed router 189 07:12.760 --> 07:14.480 for tier zero gateway. 190 07:14.480 --> 07:17.430 So if we scroll down, here's one of our router to router connections between 191 07:17.430 --> 07:18.120 the tier zero 192 07:18.120 --> 07:20.800 and tier one, we continue to go down. 193 07:20.800 --> 07:24.210 Here's our second interface between us and based on the name here, this is 194 07:24.210 --> 07:25.000 going to gateway 195 07:25.000 --> 07:26.000 B, fantastic. 196 07:26.000 --> 07:28.950 And here we have the IP address that we're using on the subnet that 197 07:28.950 --> 07:30.120 communicates between WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 197 07:28.950 --> 07:30.120 communicates between 198 07:30.120 --> 07:33.280 us, in this case, the DR over to the SR. 199 07:33.280 --> 07:39.050 So the other address on the subnet 169.24.0.2, that was on the services router 200 07:39.050 --> 07:39.560 port. 201 07:39.560 --> 07:42.420 So whenever they need to logically communicate back and forth between each 202 07:42.420 --> 07:43.080 other, this is 203 07:43.080 --> 07:45.120 the IP subnet they're going to use to do exactly that. 204 07:45.120 --> 07:48.800 Then as we continue to scroll down, we have one regarding multicast traffic. 205 07:48.800 --> 07:49.800 And that is it. 206 07:49.800 --> 07:50.800 So I had Q2 quit. 207 07:50.800 --> 07:53.600 So once again, if we do a get route, that's going to show us our routing table. 208 07:53.600 --> 07:55.320 We get us to a get forwarding. 209 07:55.320 --> 07:58.560 And so we should be able to ping this external router from this VRF right here. 210 07:58.560 --> 08:01.120 So we type in ping to 23.1.2.1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 210 07:58.560 --> 08:01.120 So we type in ping to 23.1.2.1. 211 08:01.120 --> 08:04.080 Oh, that's a very good sign, fantastic. 212 08:04.080 --> 08:06.880 And if this is the next top address for our service provider, and if we're 213 08:06.880 --> 08:07.400 using it as 214 08:07.400 --> 08:12.010 our default route, which we are based on this right here, we should be able to 215 08:12.010 --> 08:12.920 ping resources 216 08:12.920 --> 08:14.120 out on the internet. 217 08:14.120 --> 08:16.280 Let's go into a ping 8, 8, 8, 8, 8. 218 08:16.280 --> 08:17.280 That looks great. 219 08:17.280 --> 08:19.990 And just to make sure it's not going somewhere weird, let's go into a trace 220 08:19.990 --> 08:20.640 route to 8, 8, 221 08:20.640 --> 08:22.040 8, 8, 8, and press enter. 222 08:22.040 --> 08:24.800 Let me go ahead and source it from the correct interface here. 223 08:24.800 --> 08:26.320 So let me go into a trace route space. 224 08:26.320 --> 08:29.560 I'll go into a trace route to 8, 8, 8, 8, 8, and a space question mark. 225 08:29.560 --> 08:30.560 I'll say source. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 225 08:29.560 --> 08:30.560 I'll say source. 226 08:30.560 --> 08:36.440 I want to source this from my edge one IP address, which is 23.1.2.61. 227 08:36.440 --> 08:39.190 And we'll probably get some better results by sourcing it from the correct 228 08:39.190 --> 08:39.800 interface. 229 08:39.800 --> 08:43.840 So this is showing us the path through the internet getting out to a Google 230 08:43.840 --> 08:44.520 server. 231 08:44.520 --> 08:46.800 Then we have the response coming back from 8, 8, 8, 8. 232 08:46.800 --> 08:50.290 So I just want to verify from our edge that we are really going to the internet 233 08:50.290 --> 08:50.480 . 234 08:50.480 --> 08:53.590 Also notice here on my second hop, I'm going back through my management network 235 08:53.590 --> 08:53.680 . 236 08:53.680 --> 08:56.800 And that's just for the benefit of me being able to do NAT again. 237 08:56.800 --> 09:00.080 So I can actually use the 23 address space here in my lab environment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 237 08:56.800 --> 09:00.080 So I can actually use the 23 address space here in my lab environment. 238 09:00.080 --> 09:02.960 So from the internet, it doesn't look like I'm really coming from the 23 239 09:02.960 --> 09:03.520 network. 240 09:03.520 --> 09:06.420 It looks like I'm coming from whatever I'm doing the NAT on at this hop in the 241 09:06.420 --> 09:06.920 path right 242 09:06.920 --> 09:07.920 here. 243 09:07.920 --> 09:08.920 Awesome. 244 09:08.920 --> 09:11.360 And also just for grants, let me also add to our tier zero gateway. 245 09:11.360 --> 09:14.000 Let me add the virtual IP address. 246 09:14.000 --> 09:16.840 So I'm going to edit our tier zero gateway once again by clicking on three dots 247 09:16.840 --> 09:17.080 for our 248 09:17.080 --> 09:22.070 tier zero gateway, clicking on edit, and then for the HAVAP, let's go ahead and 249 09:22.070 --> 09:22.640 click on 250 09:22.640 --> 09:26.160 add and let's use 23.1.2.60. 251 09:26.160 --> 09:30.250 Select that 24-bit mask, and then we'll select the 200 faces on edge one and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 251 09:26.160 --> 09:30.250 Select that 24-bit mask, and then we'll select the 200 faces on edge one and 252 09:30.250 --> 09:31.880 edge two respectively. 253 09:31.880 --> 09:36.280 To support that, click on add, click on apply, and click on save. 254 09:36.280 --> 09:39.000 And then finally, we'll scroll down and click on close editing. 255 09:39.000 --> 09:41.400 And then we can verify that from the command lane as well. 256 09:41.400 --> 09:45.350 So back in our VRF for our services router, and we're looking for something 257 09:45.350 --> 09:46.280 that ends in 258 09:46.280 --> 09:47.280 60. 259 09:47.280 --> 09:49.560 We can just go ahead and do a pipe and say find 60. 260 09:49.560 --> 09:52.870 And then any of the lines in the output that have the number 60 in it, those 261 09:52.870 --> 09:53.400 are the ones 262 09:53.400 --> 09:56.880 that will be shown to the screen, and there it is right there. 263 09:56.880 --> 10:01.520 So on edge one, it has this IP address 23-1-2-61, but we're also supporting WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 263 09:56.880 --> 10:01.520 So on edge one, it has this IP address 23-1-2-61, but we're also supporting 264 10:01.520 --> 10:02.320 this virtual 265 10:02.320 --> 10:04.760 IP address of 23.1.2.60. 266 10:04.760 --> 10:08.640 And again, that's on our services router, tier zero gateway. 267 10:08.640 --> 10:11.290 And the only reason that output is showing up here is because it just so 268 10:11.290 --> 10:11.840 happened in 269 10:11.840 --> 10:15.920 the UUID to also have a 60 in it, which is just the luck of the draw here. 270 10:15.920 --> 10:19.200 It wasn't actually searching for the UUID, uh, scratch set. 271 10:19.200 --> 10:24.040 So here in the output, it has a 23.1.2-60 address and this is on edge one. 272 10:24.040 --> 10:27.640 It also has the actual IP address on edge one of dot 60. 273 10:27.640 --> 10:31.050 So because edge one is the active gateway, that's why it also shows that IP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 273 10:27.640 --> 10:31.050 So because edge one is the active gateway, that's why it also shows that IP 274 10:31.050 --> 10:31.760 address right 275 10:31.760 --> 10:32.760 here as well. 276 10:32.760 --> 10:33.760 All right. 277 10:33.760 --> 10:36.920 So we are in great striking position because we've just updated our topology. 278 10:36.920 --> 10:41.480 We've also verified that the gateway zero has access to the public internet. 279 10:41.480 --> 10:42.480 Fantastic. 280 10:42.480 --> 10:46.870 So in our next video, let's deploy a couple of additional VMs that we can use 281 10:46.870 --> 10:47.720 for testing. 282 10:47.720 --> 10:49.720 I'll see you in the next video in just a minute.