WEBVTT 1 00:00.000 --> 00:07.080 So the next step to get the catalyst 8,000 V operational is we have to put some 2 00:07.080 --> 00:07.600 baseline 3 00:07.600 --> 00:08.800 configuration on it. 4 00:08.800 --> 00:12.120 Now, a lot of what I'm going to put on here is sort of optional. 5 00:12.120 --> 00:16.470 We're going to turn on some date and time stamping for our logs and debug and 6 00:16.470 --> 00:17.120 such. 7 00:17.120 --> 00:21.000 But the main thing we need to do is configure all of the other interfaces. 8 00:21.000 --> 00:26.520 Remember, only Gigabit 1 is configured automatically by the deployment manager. 9 00:26.520 --> 00:30.080 So we have to configure in our case, just Gigabit 2. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 9 00:26.520 --> 00:30.080 So we have to configure in our case, just Gigabit 2. 10 00:30.080 --> 00:33.580 But if you would deploy more interfaces, you would have to configure those as 11 00:33.580 --> 00:34.040 well. 12 00:34.040 --> 00:39.280 So let's go ahead and jump in to the command line on GCP R1 and get our 13 00:39.280 --> 00:40.960 baseline configuration 14 00:40.960 --> 00:44.200 on that router. 15 00:44.200 --> 00:47.720 So first, let's just paste in a base configuration here. 16 00:47.720 --> 00:50.190 What we're going to do is we're going to set the host name to what we really 17 00:50.190 --> 00:50.560 wanted 18 00:50.560 --> 00:51.560 it to be. 19 00:51.560 --> 00:55.810 We're a little bit restricted in the cloud environment as to what we can name 20 00:55.810 --> 00:56.440 this. 21 00:56.440 --> 01:00.880 But once we get into the actual iOS, we can change it to what we want. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 21 00:56.440 --> 01:00.880 But once we get into the actual iOS, we can change it to what we want. 22 01:00.880 --> 01:03.600 So we're going to make it GCP underscore R1. 23 01:03.600 --> 01:09.540 Then of course, we configure our Gigabit 2 interface to get its IP address from 24 01:09.540 --> 01:09.960 DHCP and then 25 01:09.960 --> 01:11.480 bring it online. 26 01:11.480 --> 01:15.920 If this has been successful, we should be able to do a show IP interface brief. 27 01:15.920 --> 01:21.860 And we see that our Gigabit 2 interface is in fact up, pulled the address from 28 01:21.860 --> 01:22.560 DHCP. 29 01:22.560 --> 01:27.590 Now in this case, both our Gigabit 1 and Gigabit 2 interfaces have been given a 30 01:27.590 --> 01:29.200 dot 2 on their 31 01:29.200 --> 01:31.160 respective subnets. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 31 01:29.200 --> 01:31.160 respective subnets. 32 01:31.160 --> 01:34.930 So if this is actually functioning properly, we should now be able to have 33 01:34.930 --> 01:36.200 internet access 34 01:36.200 --> 01:38.000 from R1. 35 01:38.000 --> 01:43.760 We should have name resolution. 36 01:43.760 --> 01:47.000 So we see that both of those things are working as they should. 37 01:47.000 --> 01:50.040 So now let's put the rest of our baseline on here. 38 01:50.040 --> 01:53.040 Again, this is really just sort of my baseline. 39 01:53.040 --> 01:56.440 You can of course add or remove anything from here that you want. 40 01:56.440 --> 01:59.440 This is a very, very simple baseline in production. 41 01:59.440 --> 02:01.080 I have a much larger one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 41 01:59.440 --> 02:01.080 I have a much larger one. 42 02:01.080 --> 02:02.960 But for the lab, this is fine. 43 02:02.960 --> 02:06.090 We're just setting some timestamps on our debugs and logs in case we need to 44 02:06.090 --> 02:07.320 look at them. 45 02:07.320 --> 02:11.360 We're setting up our clock so those date and timestamps are correct. 46 02:11.360 --> 02:14.880 We're turning off the log in on success log. 47 02:14.880 --> 02:18.800 Again, in production, that's probably something you'd want to leave on. 48 02:18.800 --> 02:21.880 It's good to know when people log onto the device. 49 02:21.880 --> 02:25.350 But in a lab environment like this, it can sometimes get in the way and be a 50 02:25.350 --> 02:26.880 little confusing. 51 02:26.880 --> 02:28.680 So that's why I'm turning that off. 52 02:28.680 --> 02:32.400 Then of course, we're doing a little bit of configuration on our VTY lines. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 52 02:28.680 --> 02:32.400 Then of course, we're doing a little bit of configuration on our VTY lines. 53 02:32.400 --> 02:35.640 We're just setting the exact time out, logging synchronous. 54 02:35.640 --> 02:38.880 So any logging doesn't interrupt our output. 55 02:38.880 --> 02:41.160 And we're changing the history size. 56 02:41.160 --> 02:45.840 We're also, of course, configuring an NTP server to synchronize the clock. 57 02:45.840 --> 02:49.440 Most of this, as you can see, is about making sure the clock and date and 58 02:49.440 --> 02:51.000 timestamps are correct 59 02:51.000 --> 02:53.880 on our debugs and logs. 60 02:53.880 --> 02:58.580 So in this video, we just put a real simple baseline configuration on this 61 02:58.580 --> 02:59.360 router. 62 02:59.360 --> 03:01.840 It's going to be enough for what we need here in the lab. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 62 02:59.360 --> 03:01.840 It's going to be enough for what we need here in the lab. 63 03:01.840 --> 03:06.560 The most important thing, of course, is configuring that gigabit to interface, 64 03:06.560 --> 03:07.080 which is now 65 03:07.080 --> 03:08.360 correct. 66 03:08.360 --> 03:12.850 Our next step, which we're going to tackle in the next video, is to make sure 67 03:12.850 --> 03:14.000 that our subnet 68 03:14.000 --> 03:20.520 10, or in this case, our gigabit 2 interface has internet access just like gig 69 03:20.520 --> 03:21.880 abit 1 does, 70 03:21.880 --> 03:23.880 which is what we've tested so far. 71 03:23.880 --> 03:26.680 So we'll be testing gigabit 2 in the next video. 72 03:26.680 --> 03:36.680 [BLANK_AUDIO]