WEBVTT 1 00:00.000 --> 00:07.600 So now that our catalyst 8000 V is deployed, let's jump in, just put some 2 00:07.600 --> 00:08.980 baseline configuration 3 00:08.980 --> 00:09.980 on there. 4 00:09.980 --> 00:14.850 Remember, at bare minimum, we have to configure that second interface gigabit 2 5 00:14.850 --> 00:15.820 that we added 6 00:15.820 --> 00:17.740 after we did our deployment. 7 00:17.740 --> 00:21.610 So let's jump in, put some baseline configuration on here, test some 8 00:21.610 --> 00:23.140 connectivity, make sure everything's 9 00:23.140 --> 00:24.900 working the way it should. 10 00:24.900 --> 00:28.140 Let's go ahead and jump into the command line of Azure R1. 11 00:28.240 --> 00:33.550 So let's begin, of course, by going into configuration mode, and then we're WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:28.240 --> 00:33.550 So let's begin, of course, by going into configuration mode, and then we're 12 00:33.550 --> 00:34.280 just going 13 00:34.280 --> 00:37.600 to paste in our baseline configuration. 14 00:37.600 --> 00:40.800 The things we're doing here, we're just setting the host name, we're going to 15 00:40.800 --> 00:41.120 set up 16 00:41.120 --> 00:45.690 some date and time stamps on our logging and our debugs, we'll set our clock to 17 00:45.690 --> 00:46.520 the correct 18 00:46.520 --> 00:47.520 time zone. 19 00:47.520 --> 00:51.040 Again, you would want to set this according to your environment. 20 00:51.040 --> 00:54.420 We're going to turn on no logging on success log. 21 00:54.420 --> 00:58.280 This just stops it from logging every time somebody logs in in a production 22 00:58.280 --> 00:59.140 environment. 23 00:59.140 --> 01:01.740 Of course, you might want that in the lab. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 00:59.140 --> 01:01.740 Of course, you might want that in the lab. 24 01:01.740 --> 01:03.840 It can get a little bit annoying and get in the way. 25 01:03.840 --> 01:05.860 So that's why I'm turning it off. 26 01:05.860 --> 01:09.760 Then of course, the most important thing we're doing here is setting the gigab 27 01:09.760 --> 01:10.660 it 2 interface 28 01:10.660 --> 01:15.000 to get its address from DHCP and bringing it online. 29 01:15.000 --> 01:19.730 Then we're just doing some configuration on our VTY lines as far as timing out, 30 01:19.730 --> 01:20.020 logging 31 01:20.020 --> 01:26.020 synchronous and setting up a history size and we're configuring an NTP server. 32 01:26.020 --> 01:30.050 Once all of this is done, let's go ahead and exit out and let's do some WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 32 01:26.020 --> 01:30.050 Once all of this is done, let's go ahead and exit out and let's do some 33 01:30.050 --> 01:31.220 verification. 34 01:31.220 --> 01:33.500 Let's do a show IP interface brief. 35 01:33.500 --> 01:37.890 We see here that now our gigabit 2 interface is configured the way it should be 36 01:37.890 --> 01:38.020 . 37 01:38.020 --> 01:40.860 It's getting the correct address from Azure. 38 01:40.860 --> 01:43.260 So everything here looks good. 39 01:43.260 --> 01:45.300 We do a show IP route. 40 01:45.300 --> 01:49.900 What I'm specifically looking for here is our gateway of last resort is set. 41 01:49.900 --> 01:56.780 We have a static default route pointing to 10.30.1.1, which is the Azure 42 01:56.780 --> 01:58.220 default gateway for 43 01:58.220 --> 01:59.420 the internet. 44 01:59.420 --> 02:03.660 So that means that I should be able to say ping 8.8.8.8. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 44 01:59.420 --> 02:03.660 So that means that I should be able to say ping 8.8.8.8. 45 02:03.660 --> 02:06.060 We can see that successful. 46 02:06.060 --> 02:08.260 We can also go ahead and ping Cisco. 47 02:08.260 --> 02:09.620 We see that works as well. 48 02:09.620 --> 02:13.300 So our name resolution is working properly also. 49 02:13.300 --> 02:17.420 So now we have our baseline configuration and we verify the connectivity out to 50 02:17.420 --> 02:17.540 the 51 02:17.540 --> 02:20.820 internet is working properly. 52 02:20.820 --> 02:25.660 So in this video, we just jumped in through a baseline configuration on our 53 02:25.660 --> 02:26.460 router. 54 02:26.460 --> 02:30.560 Of course, you could add or remove anything here that meets or doesn't meet WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 54 02:26.460 --> 02:30.560 Of course, you could add or remove anything here that meets or doesn't meet 55 02:30.560 --> 02:31.700 your environment's 56 02:31.700 --> 02:32.700 requirements. 57 02:32.700 --> 02:37.400 However, we have a baseline configuration on here and we have verified reach 58 02:37.400 --> 02:37.980 ability 59 02:37.980 --> 02:39.780 out to the internet. 60 02:39.780 --> 02:44.900 Let's see how our subnet 10 is doing, which is our inside interface.