WEBVTT 1 00:00.000 --> 00:09.120 So our next step here is going to be to configure our VPN 512 for out of band 2 00:09.120 --> 00:10.520 management. 3 00:10.520 --> 00:14.700 Now this is going to be a fairly simple template, but let's go ahead and jump 4 00:14.700 --> 00:15.520 in and configure 5 00:15.520 --> 00:16.520 it. 6 00:16.520 --> 00:21.750 And then we'll go ahead and apply this device template to both router one and 7 00:21.750 --> 00:22.760 router two, 8 00:22.760 --> 00:26.840 put in the appropriate values for the stuff that needs to be filled in. 9 00:26.840 --> 00:33.320 And then we'll push the configuration out and verify that it's been applied. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 9 00:26.840 --> 00:33.320 And then we'll push the configuration out and verify that it's been applied. 10 00:33.320 --> 00:38.710 So once again, we'll start off on our templates page and we'll go into edit 11 00:38.710 --> 00:40.120 mode on our device 12 00:40.120 --> 00:41.640 template. 13 00:41.640 --> 00:46.640 Here we'll scroll down to VPN 512 this time. 14 00:46.640 --> 00:51.440 So the first thing we'll do is create our VPN 512 template. 15 00:51.440 --> 00:53.520 So let's click our drop down. 16 00:53.520 --> 00:57.600 We'll go to create template for our template name. 17 00:57.600 --> 01:04.120 Let's call this VPN 512 for the description. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 17 00:57.600 --> 01:04.120 Let's call this VPN 512 for the description. 18 01:04.120 --> 01:06.560 Also VPN 512. 19 01:06.560 --> 01:11.440 Notice that Cisco has once again filled in our VPN for us. 20 01:11.440 --> 01:13.600 It's already set to 512. 21 01:13.600 --> 01:18.120 However, one thing we need to do here that's a little bit different than what 22 01:18.120 --> 01:18.840 we did in 23 01:18.840 --> 01:23.040 VPN zero, at least again in my environment. 24 01:23.040 --> 01:27.920 My out of band management actually needs a default gateway. 25 01:27.920 --> 01:30.760 So we need to go to IPV four routes. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 25 01:27.920 --> 01:30.760 So we need to go to IPV four routes. 26 01:30.760 --> 01:35.000 We can either scroll down to that, or there are of course tabs up here across 27 01:35.000 --> 01:35.880 the top, 28 01:35.880 --> 01:39.280 where we can just jump down to that section of the page. 29 01:39.280 --> 01:45.720 We'll say new IPV four route for the prefix zero dot zero dot zero dot zero 30 01:45.720 --> 01:48.080 slash zero. 31 01:48.080 --> 01:51.200 We can then choose what the gateway is going to be. 32 01:51.200 --> 01:55.200 Now we can see here the default of course is to use a next hop. 33 01:55.200 --> 02:01.480 We could also point it to null zero to a VPN or to DHCP. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 33 01:55.200 --> 02:01.480 We could also point it to null zero to a VPN or to DHCP. 34 02:01.480 --> 02:05.520 We're of course going to use a next hop, but that means we also have to add a 35 02:05.520 --> 02:06.920 next hop. 36 02:06.920 --> 02:11.520 So our next step is to click here on add next hop. 37 02:11.520 --> 02:14.320 And we put in the address in my environment. 38 02:14.320 --> 02:18.120 That's 192 dot 168 dot 1 dot 1. 39 02:18.120 --> 02:21.730 You can change the administrative distance here if you want the default 40 02:21.730 --> 02:22.640 administrative 41 02:22.640 --> 02:25.200 distance for a static route is one. 42 02:25.200 --> 02:28.440 And in this case, that's perfectly fine. 43 02:28.440 --> 02:33.960 If you wanted more than one next hop, you could click here on add next hop. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 43 02:28.440 --> 02:33.960 If you wanted more than one next hop, you could click here on add next hop. 44 02:33.960 --> 02:35.760 It'll add a second field. 45 02:35.760 --> 02:38.920 And of course, you could then do some load sharing. 46 02:38.920 --> 02:42.400 In my case, I don't have an additional gateway. 47 02:42.400 --> 02:45.360 So all this removed the one I just added. 48 02:45.360 --> 02:47.080 And we'll just hit add. 49 02:47.080 --> 02:52.460 Now just like OSPF did with the interfaces, notice that under next hop here now 50 02:52.460 --> 02:53.000 says we 51 02:53.000 --> 02:58.640 have one next hop, but we still have not added the IPV4 route. 52 02:58.640 --> 03:01.360 Now what we have to do is hit add. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 52 02:58.640 --> 03:01.360 Now what we have to do is hit add. 53 03:01.360 --> 03:04.200 Now the static route is in place. 54 03:04.200 --> 03:08.080 So we can see that it's a static route pointing to a next hop. 55 03:08.080 --> 03:11.640 The selected gateway has one next hop with it. 56 03:11.640 --> 03:17.160 So that takes care of the configuration of this VPN 512 template. 57 03:17.160 --> 03:22.320 We can now just hit save, scroll back down to VPN 512. 58 03:22.320 --> 03:28.720 But at this point, we don't have any interfaces in VPN 512. 59 03:28.720 --> 03:34.180 So now we need to go over here to Cisco VPN interface ethernet and add that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 59 03:28.720 --> 03:34.180 So now we need to go over here to Cisco VPN interface ethernet and add that 60 03:34.180 --> 03:35.160 additional 61 03:35.160 --> 03:36.520 template. 62 03:36.520 --> 03:42.000 And on our dropdown, we'll choose to create a new template for this one. 63 03:42.000 --> 03:45.400 It's gigabit ethernet five in my environment. 64 03:45.400 --> 03:48.600 So let's click up here on the template name. 65 03:48.600 --> 03:52.760 We'll just name it gigabit ethernet five for the description. 66 03:52.760 --> 03:57.480 We'll just call it GE five configuration. 67 03:57.480 --> 03:59.880 Of course, we need to bring this interface up. 68 03:59.880 --> 04:06.480 So under shutdown, we'll globally say no for the interface name. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 68 03:59.880 --> 04:06.480 So under shutdown, we'll globally say no for the interface name. 69 04:06.480 --> 04:09.080 It's gigabit ethernet five. 70 04:09.080 --> 04:18.200 Once again, the description is optional, but we'll set it. 71 04:18.200 --> 04:21.040 And once again, it's going to be a static address. 72 04:21.040 --> 04:24.760 So we're going to change this to device specific. 73 04:24.760 --> 04:27.920 We're going to change our key and we'll add the interface to it. 74 04:27.920 --> 04:31.720 So we'll just call this GE five for gigabit five. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 74 04:27.920 --> 04:31.720 So we'll just call this GE five for gigabit five. 75 04:31.720 --> 04:35.400 And we can see once again, that updates the key. 76 04:35.400 --> 04:39.980 Now, since this is not going to be used for control tunnels, we do not need to 77 04:39.980 --> 04:40.320 turn on 78 04:40.320 --> 04:41.320 the tunnel here. 79 04:41.320 --> 04:43.200 We can leave this off. 80 04:43.200 --> 04:46.280 Everything else here is going to be configured as we need it. 81 04:46.280 --> 04:48.600 So let's just hit save. 82 04:48.600 --> 04:51.320 And then we'll hit update. 83 04:51.320 --> 04:55.960 So at this point, we should have pretty much what's already configured on 84 04:55.960 --> 04:56.760 router one and 85 04:56.760 --> 05:03.260 router two now configured in our device template, meaning it should have VPN WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 85 04:56.760 --> 05:03.260 router two now configured in our device template, meaning it should have VPN 86 05:03.260 --> 05:03.980 zero. 87 05:03.980 --> 05:07.700 That interface should be configured as it is right now. 88 05:07.700 --> 05:13.060 And we should have our VPN 512, which we actually did not have configured 89 05:13.060 --> 05:14.600 before, but we will 90 05:14.600 --> 05:15.600 now. 91 05:15.600 --> 05:20.100 So let's go ahead and roll this template out to both of our routers. 92 05:20.100 --> 05:26.340 So our first step is to click on the extended menu and choose attached devices. 93 05:26.340 --> 05:31.310 When we choose this, it's going to list all of our devices over here on the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 93 05:26.340 --> 05:31.310 When we choose this, it's going to list all of our devices over here on the 94 05:31.310 --> 05:32.060 left. 95 05:32.060 --> 05:36.990 So what we're going to do is scroll down to the ones that have actually been 96 05:36.990 --> 05:37.300 added. 97 05:37.300 --> 05:42.610 So for on-prem router one and on-prem router two, we're going to add these to 98 05:42.610 --> 05:43.340 the selected 99 05:43.340 --> 05:45.200 devices list. 100 05:45.200 --> 05:47.100 Then we're going to hit attach. 101 05:47.100 --> 05:53.900 The next step is to fill in the information that we had set to device specific. 102 05:53.900 --> 05:59.420 Also, it's going to need some things that it hasn't asked us yet, because again 103 05:59.420 --> 06:00.580 , remember, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 103 05:59.420 --> 06:00.580 , remember, 104 06:00.580 --> 06:04.360 this is completely putting a new configuration on the device. 105 06:04.360 --> 06:07.990 So if we look over here to the far right, notice that it's going to ask us for 106 06:07.990 --> 06:09.180 the host name 107 06:09.180 --> 06:14.070 and the system IP, even though it sort of already has them over here on the 108 06:14.070 --> 06:15.220 left, because 109 06:15.220 --> 06:17.980 you may want to be changing those. 110 06:17.980 --> 06:22.040 And one other thing to note before we start filling in these fields over here 111 06:22.040 --> 06:22.620 on the far 112 06:22.620 --> 06:26.260 left, there is a grayed out X. 113 06:26.260 --> 06:30.680 This indicating that these devices are not ready to be deployed because there WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 113 06:26.260 --> 06:30.680 This indicating that these devices are not ready to be deployed because there 114 06:30.680 --> 06:31.300 are still 115 06:31.300 --> 06:35.060 variable fields that have not been filled in. 116 06:35.060 --> 06:37.420 So let's start with the host names. 117 06:37.420 --> 06:41.460 Since we can already see what they are, we can easily just type this in. 118 06:41.460 --> 06:44.900 This is going to be on-prem R1. 119 06:44.900 --> 06:49.380 This one, of course, is on-prem R2. 120 06:49.380 --> 06:52.970 And by the way, just one other quick note as we're going here, make sure you 121 06:52.970 --> 06:53.740 watch the 122 06:53.740 --> 06:56.420 order in which these are listed. 123 06:56.420 --> 07:01.660 They won't necessarily be listed by system IP or by host name. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 123 06:56.420 --> 07:01.660 They won't necessarily be listed by system IP or by host name. 124 07:01.660 --> 07:03.260 So just be aware of that. 125 07:03.260 --> 07:07.080 These did happen to come up this time in the correct order, but I've also had 126 07:07.080 --> 07:07.580 them come 127 07:07.580 --> 07:09.860 up not in the correct order. 128 07:09.860 --> 07:13.070 So be sure to watch the order that they are in this list as you're filling in 129 07:13.070 --> 07:14.980 the variables. 130 07:14.980 --> 07:25.780 Next is the system IP 10.255.255.1, 10.255.255.2. 131 07:25.780 --> 07:29.940 So then we get to the fields that we actually told it to create. 132 07:29.940 --> 07:34.560 So notice up at the top, these are named and you see now, hopefully, why it was WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 132 07:29.940 --> 07:34.560 So notice up at the top, these are named and you see now, hopefully, why it was 133 07:34.560 --> 07:35.900 so important 134 07:35.900 --> 07:40.820 that we put that key in there with the correct interface. 135 07:40.820 --> 07:47.150 If both of these keys simply said VPN underscore IF underscore IPV4 underscore 136 07:47.150 --> 07:48.300 address, how would 137 07:48.300 --> 07:51.060 we know which of these two fields is for which interface? 138 07:51.060 --> 07:54.580 That's why it's very important that we set the keys. 139 07:54.580 --> 07:57.060 So let's go ahead and put in our addresses. 140 07:57.060 --> 08:02.410 So the address for IPV4 for gigabit five, for router one, this is the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 140 07:57.060 --> 08:02.410 So the address for IPV4 for gigabit five, for router one, this is the 141 08:02.410 --> 08:04.000 management network 142 08:04.000 --> 08:09.300 is 192.168.1.201. 143 08:09.300 --> 08:11.180 This is a slash 24. 144 08:11.180 --> 08:14.060 Again, this is simply what they are in my environment. 145 08:14.060 --> 08:18.100 You may have used different addresses for router two. 146 08:18.100 --> 08:22.740 It's 192.168.1.202. 147 08:22.740 --> 08:28.180 Also a slash 24 for our VPN zero address. 148 08:28.180 --> 08:42.860 This is on the 100 network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 148 08:28.180 --> 08:42.860 This is on the 100 network. 149 08:42.860 --> 08:48.520 So this is what happens when we actually tell it that it's device specific when 150 08:48.520 --> 08:49.380 we're making 151 08:49.380 --> 08:50.980 our template. 152 08:50.980 --> 08:55.270 Now if we click off of here, notice that we still have gray X's at the 153 08:55.270 --> 08:56.620 beginning, which 154 08:56.620 --> 09:00.500 indicates that there might be more things we have to fill in. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 154 08:56.620 --> 09:00.500 indicates that there might be more things we have to fill in. 155 09:00.500 --> 09:07.380 If we scroll over, notice it still wants the site ID, which was off screen. 156 09:07.380 --> 09:09.820 These are site ID 100. 157 09:09.820 --> 09:15.220 Notice as soon as I click off router one now, notice it now has a green check 158 09:15.220 --> 09:15.860 box at the 159 09:15.860 --> 09:21.170 beginning, meaning, okay, you have filled in all the required fields and it's 160 09:21.170 --> 09:21.580 ready 161 09:21.580 --> 09:23.180 to deploy. 162 09:23.180 --> 09:25.860 Does that necessarily mean it's correct? 163 09:25.860 --> 09:27.620 No, no, not necessarily. 164 09:27.620 --> 09:29.260 We could of course made a mistake here. 165 09:29.260 --> 09:32.960 There could be something wrong with our template, but as far as the fields that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 165 09:29.260 --> 09:32.960 There could be something wrong with our template, but as far as the fields that 166 09:32.960 --> 09:33.860 need to be filled 167 09:33.860 --> 09:38.100 in for deployment, this is now ready to go. 168 09:38.100 --> 09:40.460 So now we can hit next. 169 09:40.460 --> 09:44.260 Now sort of one of the really cool features that we can do here is we can click 170 09:44.260 --> 09:44.660 on one 171 09:44.660 --> 09:47.420 of our routers now over here on the left. 172 09:47.420 --> 09:49.580 We'll pick on router one. 173 09:49.580 --> 09:55.250 And what it's going to do is load the configuration that it's going to deploy 174 09:55.250 --> 09:56.580 to that device. 175 09:56.580 --> 10:02.270 And the other really neat feature here is you can also then click on config WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 175 09:56.580 --> 10:02.270 And the other really neat feature here is you can also then click on config 176 10:02.270 --> 10:02.620 diff and 177 10:02.620 --> 10:09.200 it'll show you the lines that are either going to be the same, added or changed 178 10:09.200 --> 10:09.420 when 179 10:09.420 --> 10:11.340 this is deployed. 180 10:11.340 --> 10:13.700 So we can scroll down this list. 181 10:13.700 --> 10:17.020 We can see the things that are going to be changed. 182 10:17.020 --> 10:20.980 Now there's nothing here that's going to cause us any kind of a problem. 183 10:20.980 --> 10:24.460 So everything here looks like it should be good. 184 10:24.460 --> 10:26.820 And of course you could verify router two as well. 185 10:26.820 --> 10:31.700 If you wanted to, we'll just go ahead and click on configure devices. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 185 10:26.820 --> 10:31.700 If you wanted to, we'll just go ahead and click on configure devices. 186 10:31.700 --> 10:35.020 It's going to say, are you sure you want to change these two devices? 187 10:35.020 --> 10:38.380 We'll confirm it and we'll hit OK. 188 10:38.380 --> 10:43.090 This will now go through and push out the templates and hopefully our status 189 10:43.090 --> 10:43.660 will go 190 10:43.660 --> 10:45.260 to success. 191 10:45.260 --> 10:50.540 So now we can see that this was successfully pushed out to both devices. 192 10:50.540 --> 10:55.200 If anything went wrong, you can click on this little drop down arrow over here 193 10:55.200 --> 10:55.860 on the far 194 10:55.860 --> 11:01.260 left and it will give you information as far as what went wrong. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 194 10:55.860 --> 11:01.260 left and it will give you information as far as what went wrong. 195 11:01.260 --> 11:04.860 Now here, of course, everything went OK, so there's no errors. 196 11:04.860 --> 11:09.030 But if there were, this is where it would be displayed and you would have to go 197 11:09.030 --> 11:09.580 correct 198 11:09.580 --> 11:12.140 whatever was wrong. 199 11:12.140 --> 11:15.580 Now that this has been deployed, let's go ahead and hit back. 200 11:15.580 --> 11:18.620 This will take us back to our device templates page. 201 11:18.620 --> 11:25.380 And of course, the most important thing to note here is devices attached is now 202 11:25.380 --> 11:25.460 two. 203 11:25.460 --> 11:30.300 And a few things we can do here, notice that that too is a hyperlink. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 203 11:25.460 --> 11:30.300 And a few things we can do here, notice that that too is a hyperlink. 204 11:30.300 --> 11:35.230 If we click on the two, it'll actually bring up this window telling us exactly 205 11:35.230 --> 11:36.220 which devices 206 11:36.220 --> 11:37.420 are attached. 207 11:37.420 --> 11:40.140 Their site ID, their system IP. 208 11:40.140 --> 11:44.780 So this is giving us, of course, more information on the devices involved. 209 11:44.780 --> 11:51.010 And if any of the values that we just pushed in the template are incorrect, we 210 11:51.010 --> 11:51.940 can close 211 11:51.940 --> 11:53.700 out of this. 212 11:53.700 --> 12:00.700 And on this extended menu, the bottom choice is the change device values. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 212 11:53.700 --> 12:00.700 And on this extended menu, the bottom choice is the change device values. 213 12:00.700 --> 12:05.540 This will take us back to that same page where we filled these values in to 214 12:05.540 --> 12:06.620 begin with. 215 12:06.620 --> 12:10.960 Now if any of these were wrong, maybe I put the wrong system IP or I messed up 216 12:10.960 --> 12:11.540 the host 217 12:11.540 --> 12:13.140 name, something like that. 218 12:13.140 --> 12:16.620 If any of these were wrong, I could correct it here. 219 12:16.620 --> 12:20.740 And then of course, I could hit next and proceed through rolling out the 220 12:20.740 --> 12:21.540 changes. 221 12:21.540 --> 12:23.180 But everything we did is okay. 222 12:23.180 --> 12:25.620 So let's go ahead and cancel. 223 12:25.620 --> 12:30.060 And let's verify that these routers are still reachable. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 223 12:25.620 --> 12:30.060 And let's verify that these routers are still reachable. 224 12:30.060 --> 12:35.820 So here you can see that I have now SSH'd into on-prem router one. 225 12:35.820 --> 12:40.040 And this indicates that our management network seems to be working rather well, 226 12:40.040 --> 12:40.620 although 227 12:40.620 --> 12:43.980 we will fully test that in just a moment. 228 12:43.980 --> 12:49.430 Also note that my automatic login that I have saved worked, which means that 229 12:49.430 --> 12:50.340 the password 230 12:50.340 --> 12:54.100 change that we did also took effect. 231 12:54.100 --> 12:57.900 Another good indicator is we have some banners. 232 12:57.900 --> 13:03.700 We have an unauthorized logins tracked and a restricted use banner. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 232 12:57.900 --> 13:03.700 We have an unauthorized logins tracked and a restricted use banner. 233 13:03.700 --> 13:08.340 These are just default banners that SD WAN pushes out to the devices. 234 13:08.340 --> 13:12.420 But these are two good indicators that our configuration was pushed out 235 13:12.420 --> 13:13.300 properly. 236 13:13.300 --> 13:16.300 Of course, we still want to verify everything. 237 13:16.300 --> 13:19.100 So let's do a show IP interface brief. 238 13:19.100 --> 13:23.830 Here we can see that our gigabit ethernet 2.100 was created and it has the 239 13:23.830 --> 13:24.620 correct IP 240 13:24.620 --> 13:25.620 address. 241 13:25.620 --> 13:29.780 Gigabit ethernet 5 also has the correct IP address. 242 13:29.780 --> 13:36.340 And of course, it has some other interfaces created for the use of SD WAN. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 242 13:29.780 --> 13:36.340 And of course, it has some other interfaces created for the use of SD WAN. 243 13:36.340 --> 13:40.140 If everything's working, we should be able to do some connectivity checks. 244 13:40.140 --> 13:43.220 Let's try pinging 10.100.10.2. 245 13:43.220 --> 13:46.060 That would actually be on-prem router two. 246 13:46.060 --> 13:47.700 That's successful. 247 13:47.700 --> 13:57.530 Let's try 215, which is VManage, 216, which is VBond, 217, which is VSmart1, 248 13:57.530 --> 13:59.100 and 218, which 249 13:59.100 --> 14:01.180 is VSmart2. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 249 13:59.100 --> 14:01.180 is VSmart2. 250 14:01.180 --> 14:05.660 So we have full reachability on VPN zero. 251 14:05.660 --> 14:09.220 We also want to check VPN 512. 252 14:09.220 --> 14:16.830 Now what's sort of interesting about VPN 512 is if I do a show VRF here on 253 14:16.830 --> 14:18.780 router one, 254 14:18.780 --> 14:26.380 VRFs are how VPNs are implemented on the catalyst 8000V. 255 14:26.380 --> 14:35.380 So notice we have this 512 as a default route, it's one colon 512. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 255 14:26.380 --> 14:35.380 So notice we have this 512 as a default route, it's one colon 512. 256 14:35.380 --> 14:43.040 We can also see that it's gigabit five, but notice the name of the VRF is not 257 14:43.040 --> 14:44.580 512. 258 14:44.580 --> 14:48.420 It's management, intif, or interface, of course. 259 14:48.420 --> 14:54.270 So if we want to check things from that VRF, of course, one way we can do that 260 14:54.270 --> 14:54.700 is we could 261 14:54.700 --> 15:01.400 say to ping from the VRF management, intif, and let's just ping the default WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 261 14:54.700 --> 15:01.400 say to ping from the VRF management, intif, and let's just ping the default 262 15:01.400 --> 15:06.500 gateway 192.168.1.1. 263 15:06.500 --> 15:08.900 We can see this is successful. 264 15:08.900 --> 15:13.640 Of course, if I tried to ping that without the VRF, it would not be successful 265 15:13.640 --> 15:14.180 because 266 15:14.180 --> 15:18.700 it would be trying it by default from VPN zero. 267 15:18.700 --> 15:21.020 So this is not going to work. 268 15:21.020 --> 15:26.520 Now one trick that can be very, very useful when working with VRFs is rather 269 15:26.520 --> 15:27.540 than having 270 15:27.540 --> 15:34.140 to type VRF in every command you work with, you can actually change your WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 270 15:27.540 --> 15:34.140 to type VRF in every command you work with, you can actually change your 271 15:34.140 --> 15:35.860 routing context. 272 15:35.860 --> 15:40.660 By default, we're in, well, the default VRF. 273 15:40.660 --> 15:49.180 However, you can say routing context, VRF management, intif. 274 15:49.180 --> 15:53.380 Now essentially, we're going to go in to that VRF. 275 15:53.380 --> 15:59.600 Notice our command prompt changes to indicate that we're inside the management 276 15:59.600 --> 16:00.220 VRF. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 276 15:59.600 --> 16:00.220 VRF. 277 16:00.220 --> 16:01.220 What does that change? 278 16:01.220 --> 16:02.780 Well, it changes. 279 16:02.780 --> 16:07.850 For example, if I try to ping this address again, it'll simply work because now 280 16:07.850 --> 16:08.260 it's 281 16:08.260 --> 16:13.990 automatically doing it from inside this management VRF, which also means I 282 16:13.990 --> 16:15.140 should be able to 283 16:15.140 --> 16:18.220 ping other things on my management network. 284 16:18.220 --> 16:23.300 For example, 202, which is router two's management interface. 285 16:23.300 --> 16:27.460 Of course, it has to art for it, but it's then successful. 286 16:27.460 --> 16:31.850 And since I have a default gateway in this VRF, I should actually be able to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 286 16:27.460 --> 16:31.850 And since I have a default gateway in this VRF, I should actually be able to 287 16:31.850 --> 16:32.460 ping out 288 16:32.460 --> 16:39.260 to the internet such as 8.8.8.8 and we can see that's successful too. 289 16:39.260 --> 16:43.340 So we have full connectivity here on router one. 290 16:43.340 --> 16:48.480 Let's go ahead and exit out of that VRF because we do want to look at our OSPF 291 16:48.480 --> 16:49.300 process and 292 16:49.300 --> 16:51.740 that was only in VPN zero. 293 16:51.740 --> 16:57.620 So let's also say show IP OSPF interface. 294 16:57.620 --> 17:01.610 Now the main thing we want to look at here is that we are running OSPF on our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 294 16:57.620 --> 17:01.610 Now the main thing we want to look at here is that we are running OSPF on our 295 17:01.610 --> 17:02.220 gigabit 296 17:02.220 --> 17:03.220 2.100. 297 17:03.220 --> 17:08.140 It is up, but let's look at the things we changed. 298 17:08.140 --> 17:13.110 Here we can see the network type is configured to point to point as we told it 299 17:13.110 --> 17:13.740 to be. 300 17:13.740 --> 17:18.370 And if we look down here, we can see the hello interval has been set to one and 301 17:18.370 --> 17:18.580 the 302 17:18.580 --> 17:22.060 dead interval has been set to four. 303 17:22.060 --> 17:25.600 Also we can look down here at the bottom and we can see we currently have a 304 17:25.600 --> 17:26.100 neighbor 305 17:26.100 --> 17:27.700 count of one. 306 17:27.700 --> 17:34.730 We are currently adjacent with the neighbor 10.100.10.2, which of course is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 306 17:27.700 --> 17:34.730 We are currently adjacent with the neighbor 10.100.10.2, which of course is 307 17:34.730 --> 17:35.740 router two. 308 17:35.740 --> 17:39.780 You can also of course see this on a show IP OSPF neighbors. 309 17:39.780 --> 17:43.320 We actually get a little bit more information on this output because we see the 310 17:43.320 --> 17:43.860 neighbor's 311 17:43.860 --> 17:50.060 router ID as well as their state, their dead time, their address and what 312 17:50.060 --> 17:51.180 interface they're 313 17:51.180 --> 17:52.520 out. 314 17:52.520 --> 17:56.620 Now the fact that we have a neighborhood with router two is a pretty good 315 17:56.620 --> 17:57.280 indicator 316 17:57.280 --> 17:59.500 that router two was up and working. 317 17:59.500 --> 18:05.390 But if we switch over to it, just a few things, of course we are SSH in and we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 317 17:59.500 --> 18:05.390 But if we switch over to it, just a few things, of course we are SSH in and we 318 18:05.390 --> 18:06.900 have our banners, 319 18:06.900 --> 18:08.340 which is a pretty good indicator. 320 18:08.340 --> 18:11.340 The configuration got pushed properly. 321 18:11.340 --> 18:13.820 We should probably at least do a show IP interface brief. 322 18:13.820 --> 18:17.500 However, and make sure our interfaces are correct. 323 18:17.500 --> 18:21.790 We see that our two dot one hundred is up and correct and we see that gigabit 324 18:21.790 --> 18:22.440 ethernet 325 18:22.440 --> 18:23.800 five is correct. 326 18:23.800 --> 18:28.220 So everything at this point is functioning properly. 327 18:28.220 --> 18:33.560 So in this video, we pushed out our device template to router one and router WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 327 18:28.220 --> 18:33.560 So in this video, we pushed out our device template to router one and router 328 18:33.560 --> 18:35.020 two, configuring 329 18:35.020 --> 18:41.500 among other things the VPN zero and the VPN 512 interfaces. 330 18:41.500 --> 18:46.030 We verified that all of that is working and we did not cut the devices off from 331 18:46.030 --> 18:46.860 communicating 332 18:46.860 --> 18:50.780 with V Manage, which is a pretty important thing. 333 18:50.780 --> 18:55.140 The next thing we want to do of course is set this up to actually forward 334 18:55.140 --> 18:56.180 traffic for our 335 18:56.180 --> 18:58.020 service VPN. 336 18:58.020 --> 19:04.380 We've done nothing for V land 10 or our outside interfaces at this point. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 336 18:58.020 --> 19:04.380 We've done nothing for V land 10 or our outside interfaces at this point. 337 19:04.380 --> 19:06.740 So that's exactly what we're going to do next.