WEBVTT 1 00:00.000 --> 00:08.640 So our SD lab as we've built it so far is perfect if we're going to do 2 00:08.640 --> 00:09.740 something like 3 00:09.740 --> 00:15.450 just play with SD-WAN in an isolated environment or something along those lines 4 00:15.450 --> 00:15.620 . 5 00:15.620 --> 00:20.760 However, as soon as we need to talk to the real world, in other words, really 6 00:20.760 --> 00:21.240 connect 7 00:21.240 --> 00:27.490 it out to AWS and Microsoft Azure and Google Cloud, well, we're going to have 8 00:27.490 --> 00:28.280 to change 9 00:28.280 --> 00:30.600 things around just a little bit. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 9 00:28.280 --> 00:30.600 things around just a little bit. 10 00:30.600 --> 00:37.900 For one thing, VManage or SD-WAN Manager is going to need DNS name resolution 11 00:37.900 --> 00:38.400 because 12 00:38.400 --> 00:43.020 that's how Cloud on-ramp is going to find the providers, just as a small 13 00:43.020 --> 00:43.960 example. 14 00:43.960 --> 00:48.730 Plus, we're going to have some rather interesting NAT issues or network address 15 00:48.730 --> 00:50.880 translation issues. 16 00:50.880 --> 00:52.760 These are going to have to be addressed. 17 00:52.760 --> 00:56.880 Now we're not going to address those specifically in this video. 18 00:56.880 --> 01:01.360 We have an upcoming video on how to deal with those NAT issues, but it is going WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 18 00:56.880 --> 01:01.360 We have an upcoming video on how to deal with those NAT issues, but it is going 19 01:01.360 --> 01:02.080 to require 20 01:02.080 --> 01:04.360 some changes to our environment. 21 01:04.360 --> 01:07.660 So let's go ahead and jump in and take a look at what we've changed in our 22 01:07.660 --> 01:08.480 environment 23 01:08.480 --> 01:16.620 from previous videos where we were using SD-WAN and this same basic topology in 24 01:16.620 --> 01:17.960 general. 25 01:17.960 --> 01:22.470 So here's a look at the basic topology that we've been using for a good portion 26 01:22.470 --> 01:23.000 of this 27 01:23.000 --> 01:26.840 course, particularly the SD-WAN section. 28 01:26.840 --> 01:32.480 However, we have made a few changes here that are needed for SD-WAN. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 28 01:26.840 --> 01:32.480 However, we have made a few changes here that are needed for SD-WAN. 29 01:32.480 --> 01:37.560 So first, let's talk about some of the changes in VLAN 100. 30 01:37.560 --> 01:42.700 So the first change in VLAN 100 is that we're only going to be using one 31 01:42.700 --> 01:44.200 controller for 32 01:44.200 --> 01:46.640 most of these demonstrations. 33 01:46.640 --> 01:52.340 The reason behind this is we will have some issues, as I mentioned earlier, 34 01:52.340 --> 01:53.280 with network 35 01:53.280 --> 01:58.970 address translation, which in my environment is happening over here on this 36 01:58.970 --> 02:00.560 internet router. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 36 01:58.970 --> 02:00.560 internet router. 37 02:00.560 --> 02:05.860 Now that being the case, it's just far simpler to try to get this working with 38 02:05.860 --> 02:07.280 the one controller 39 02:07.280 --> 02:12.760 and our SD-WAN manager running here in VLAN 100. 40 02:12.760 --> 02:18.020 The other thing that sort of changed here from a topology setup is that VLAN 10 41 02:18.020 --> 02:18.400 over 42 02:18.400 --> 02:27.890 here is now behind R1 and R2 with R1 and R2's outside interfaces now being in V 43 02:27.890 --> 02:29.720 LAN 100. 44 02:29.720 --> 02:32.920 So that's acting as the transport. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 44 02:29.720 --> 02:32.920 So that's acting as the transport. 45 02:32.920 --> 02:37.010 Now of course, one other big thing you might notice here is that does mean we 46 02:37.010 --> 02:37.760 've brought 47 02:37.760 --> 02:39.640 in another switch. 48 02:39.640 --> 02:43.400 This switch is just doing plain routing. 49 02:43.400 --> 02:46.240 Nothing fancy going on on that switch. 50 02:46.240 --> 02:53.630 And our validator is no longer shown on this diagram because it's out here on 51 02:53.630 --> 02:55.040 the internet 52 02:55.040 --> 02:57.960 behind a separate public address. 53 02:57.960 --> 03:03.090 This is again done because of the NAT, which we'll be discussing more in an WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 53 02:57.960 --> 03:03.090 This is again done because of the NAT, which we'll be discussing more in an 54 03:03.090 --> 03:04.600 upcoming video. 55 03:04.600 --> 03:07.880 But validator 1 has been moved off of this network. 56 03:07.880 --> 03:14.320 Again, we have just manager 1 and controller 1 in our VLAN 100. 57 03:14.320 --> 03:22.130 And then we have our VLAN 10 or VPN 10 behind R1 and R2 with the original head 58 03:22.130 --> 03:23.880 quarter switch 59 03:23.880 --> 03:25.680 and our workstation. 60 03:25.680 --> 03:28.040 So again, just some minor adjustments. 61 03:28.040 --> 03:33.340 All of this information of course is in the topology diagrams and such provided WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 61 03:28.040 --> 03:33.340 All of this information of course is in the topology diagrams and such provided 62 03:33.340 --> 03:33.680 with 63 03:33.680 --> 03:35.360 this skill. 64 03:35.360 --> 03:41.300 Now also note, as I mentioned before, we had to update manager 1 here to also 65 03:41.300 --> 03:41.880 point to 66 03:41.880 --> 03:43.800 a DNS server. 67 03:43.800 --> 03:51.470 In addition, we also configured a port offset of 10 on controller 1 to 8 with 68 03:51.470 --> 03:53.120 the NAT issue. 69 03:53.120 --> 03:58.050 These are just some minor changes and I have them outlined in the code windows 70 03:58.050 --> 03:58.440 directly 71 03:58.440 --> 04:00.880 below this video. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 71 03:58.440 --> 04:00.880 below this video. 72 04:00.880 --> 04:05.690 So in this video, we wanted to just take a look at some of these minor changes 73 04:05.690 --> 04:06.080 that 74 04:06.080 --> 04:10.860 we had to make to the topology to really make our SD WAN environment properly 75 04:10.860 --> 04:11.760 communicate 76 04:11.760 --> 04:14.240 with the outside world. 77 04:14.240 --> 04:18.800 Now this does bring us to some very specific NAT issues that need to be 78 04:18.800 --> 04:20.000 discussed and that's 79 04:20.000 --> 04:22.560 exactly what we're going to do in the next video.