1 00:00:00,900 --> 00:00:06,150 In the solution video, we will explore the network configuration for our communities, Kluster. 2 00:00:07,700 --> 00:00:12,590 And for the first question, we have to identify the number of nodes part of the cluster, including 3 00:00:12,590 --> 00:00:13,590 master and worker. 4 00:00:14,510 --> 00:00:17,960 So let's run the command capacity to get nodes. 5 00:00:18,560 --> 00:00:21,980 And here we can see that we have two nodes and total. 6 00:00:26,850 --> 00:00:32,070 What is the network interface configured for cluster connectivity on the Senate and this is what is 7 00:00:32,070 --> 00:00:34,020 used for node to note communication? 8 00:00:35,310 --> 00:00:42,630 And for this, let's go back to the terminal and we'll run if config dash here, which will show all 9 00:00:42,630 --> 00:00:44,100 the network interfaces used. 10 00:00:46,230 --> 00:00:52,230 So the social you all the interface is including the loop back, the actual physical interface used 11 00:00:52,230 --> 00:00:55,130 by the cluster, etc., There's another way to do this in the winter. 12 00:00:55,440 --> 00:00:56,700 So let's truncate it. 13 00:00:56,700 --> 00:01:03,480 Is it network interfaces file, which will open up this file and show us the physical interface used. 14 00:01:03,900 --> 00:01:10,770 So here we can see that besides the loop back interface, the other physical interface available to 15 00:01:10,770 --> 00:01:12,930 the system is called in three. 16 00:01:14,680 --> 00:01:16,710 So let's select that as our answer. 17 00:01:18,650 --> 00:01:25,760 But before we do that, we can also run IP link to show all the physical links on this system and here 18 00:01:25,760 --> 00:01:26,900 you can see in a three. 19 00:01:27,900 --> 00:01:30,110 So let's select that as our answer. 20 00:01:33,990 --> 00:01:38,910 What is the IP address assigned to the most, not on this interface, so for those we can go back to 21 00:01:38,910 --> 00:01:43,110 RF config command so we can run Iev config. 22 00:01:44,220 --> 00:01:49,470 And it's sort of dash, if we can just specify the interface here and here, we have the IP, which 23 00:01:49,470 --> 00:01:51,990 is 172, 17 zero dot for. 24 00:01:56,320 --> 00:01:58,750 All right, so what is the Mac address of the interface? 25 00:01:58,780 --> 00:02:01,690 And he wants to know so again, we can make use of the exact same. 26 00:02:01,690 --> 00:02:04,060 Come on, it is available and if config. 27 00:02:05,460 --> 00:02:12,330 As you can see under the of for the field called eater, there is the Mac address, but we can also 28 00:02:12,330 --> 00:02:13,980 use Eyeblink Command. 29 00:02:16,430 --> 00:02:22,520 So I believe and look up the hardware address assigned to industry, which starts with zero two and 30 00:02:22,520 --> 00:02:28,280 ends with zero four, so let's select that as our answer, which is, are option number one here. 31 00:02:29,560 --> 00:02:35,590 What is the IP address assigned to nodes that are once we do the exact same process, but we'll run 32 00:02:35,590 --> 00:02:41,530 it on NEWSROOM one for that will run through one followed by I if config. 33 00:02:42,530 --> 00:02:43,540 In three. 34 00:02:45,120 --> 00:02:47,610 So this will fetch. 35 00:02:49,180 --> 00:02:55,180 The output of the command conflict industry and put it on the screen, so we are already on the massive 36 00:02:55,180 --> 00:03:02,260 surface of the sun, just I the newsroom one run that come on and it'll display the result on our Domhnall. 37 00:03:02,290 --> 00:03:09,490 So here we are, the IP address of industry on Ausra one, which is 172 17 zero dot seven. 38 00:03:17,160 --> 00:03:19,440 What is the Mac address assigned to the nodes or what? 39 00:03:19,440 --> 00:03:25,320 So, yeah, let's use the same command and we have the Mac address in the same command as well. 40 00:03:25,320 --> 00:03:26,730 So it ends with 07. 41 00:03:27,740 --> 00:03:30,280 So let's select that as our answer. 42 00:03:31,840 --> 00:03:39,040 We use Docker as a container on time, what is the interface or bridge created by Docker on this host? 43 00:03:41,450 --> 00:03:48,370 So let's run if config dashi again, and that list all the different interfaces, including the Docker 44 00:03:48,380 --> 00:03:52,100 Bridge, which in this case is named Docker Zero. 45 00:04:00,740 --> 00:04:02,180 What is the state of the interface? 46 00:04:02,780 --> 00:04:07,370 So let's run IP link, it will not be available in the config. 47 00:04:07,400 --> 00:04:07,900 Come on. 48 00:04:08,570 --> 00:04:12,050 So let us run IP link for docos zero. 49 00:04:17,540 --> 00:04:23,090 And here, if you look up the status of the Khosro interface, it is said to down. 50 00:04:27,280 --> 00:04:33,040 If we were to think Google from the Senate, which route does it take, what is the IP address of the 51 00:04:33,040 --> 00:04:33,910 default gateway? 52 00:04:35,580 --> 00:04:43,260 So this can be found not using a single command called IP Route or IP space are, and what we have to 53 00:04:43,260 --> 00:04:47,570 do is look up the default route, which in this case is the very first line. 54 00:04:48,300 --> 00:04:54,390 So the default route goes through the default gateway, which is 172 dots, 17 not zero, not one for 55 00:04:54,660 --> 00:04:59,130 our physical interface industry to select that as the answer. 56 00:05:00,360 --> 00:05:07,680 What is reportedly scheduler is listening on in the master node, so there are multiple ways we can 57 00:05:07,680 --> 00:05:08,060 do that. 58 00:05:08,070 --> 00:05:12,570 We can look up at the configuration of a cube scheduler, which is a static pod. 59 00:05:12,870 --> 00:05:19,050 But that's another way to look at the live board, which the cube Schiller is listening on. 60 00:05:19,320 --> 00:05:28,920 And for that, we'll use that and we'll use these additional flags and add up for process grep for cube 61 00:05:28,920 --> 00:05:29,670 scheduler. 62 00:05:31,710 --> 00:05:38,730 And this will print the process used by Kube scheduler, along with reports that it's listening also, 63 00:05:38,730 --> 00:05:47,700 and I can see that in the very bottom of the screen of the output, the power that is used as one zero 64 00:05:47,700 --> 00:05:51,410 two five one, which is used for my computer. 65 00:05:53,220 --> 00:06:00,150 So look for the listen session and hear the report that is being used as one zero two five one, so 66 00:06:00,150 --> 00:06:01,440 that's our answer. 67 00:06:06,570 --> 00:06:12,030 Notice that a city is listening on two ports, which of these have more plane connections established, 68 00:06:12,040 --> 00:06:18,570 so let's run the same command as before, which is Neistat, but this time we will search for it instead 69 00:06:18,960 --> 00:06:23,670 and we'll look at the different connections on different ports used by the city port. 70 00:06:28,860 --> 00:06:36,940 So here we can see four different listening sessions, and if you observe closely, two, three, seven, 71 00:06:36,940 --> 00:06:38,500 nine used the most. 72 00:06:38,910 --> 00:06:41,310 We also have two three eight zero. 73 00:06:41,970 --> 00:06:47,640 And there is also another four two three eight one, which is also used by each city, but the one that 74 00:06:47,640 --> 00:06:49,890 is used most as two three seven nine. 75 00:06:52,320 --> 00:06:57,330 So that's because two three seven nine is the Port of Exelis, to which all controlled plane components 76 00:06:57,330 --> 00:07:00,690 connect to three, ADRO is used for Peer-to-peer connectivity. 77 00:07:00,690 --> 00:07:02,630 In this case, we do not have additional months. 78 00:07:02,640 --> 00:07:03,540 Not so. 79 00:07:03,540 --> 00:07:09,030 We don't have multiple sessions for that specific port policy. 80 00:07:09,040 --> 00:07:09,780 Last question. 81 00:07:09,990 --> 00:07:11,970 Thank you for joining me in this video. 82 00:07:12,340 --> 00:07:13,580 I'll see you in the next one.