In the solution video, we will explore the network configuration for our communities, Kluster.
And for the first question, we have to identify the number of nodes part of the cluster, including
master and worker.
So let's run the command capacity to get nodes.
And here we can see that we have two nodes and total.
What is the network interface configured for cluster connectivity on the Senate and this is what is
used for node to note communication?
And for this, let's go back to the terminal and we'll run if config dash here, which will show all
the network interfaces used.
So the social you all the interface is including the loop back, the actual physical interface used
by the cluster, etc., There's another way to do this in the winter.
So let's truncate it.
Is it network interfaces file, which will open up this file and show us the physical interface used.
So here we can see that besides the loop back interface, the other physical interface available to
the system is called in three.
So let's select that as our answer.
But before we do that, we can also run IP link to show all the physical links on this system and here
you can see in a three.
So let's select that as our answer.
What is the IP address assigned to the most, not on this interface, so for those we can go back to
RF config command so we can run Iev config.
And it's sort of dash, if we can just specify the interface here and here, we have the IP, which
is 172, 17 zero dot for.
All right, so what is the Mac address of the interface?
And he wants to know so again, we can make use of the exact same.
Come on, it is available and if config.
As you can see under the of for the field called eater, there is the Mac address, but we can also
use Eyeblink Command.
So I believe and look up the hardware address assigned to industry, which starts with zero two and
ends with zero four, so let's select that as our answer, which is, are option number one here.
What is the IP address assigned to nodes that are once we do the exact same process, but we'll run
it on NEWSROOM one for that will run through one followed by I if config.
In three.
So this will fetch.
The output of the command conflict industry and put it on the screen, so we are already on the massive
surface of the sun, just I the newsroom one run that come on and it'll display the result on our Domhnall.
So here we are, the IP address of industry on Ausra one, which is 172 17 zero dot seven.
What is the Mac address assigned to the nodes or what?
So, yeah, let's use the same command and we have the Mac address in the same command as well.
So it ends with 07.
So let's select that as our answer.
We use Docker as a container on time, what is the interface or bridge created by Docker on this host?
So let's run if config dashi again, and that list all the different interfaces, including the Docker
Bridge, which in this case is named Docker Zero.
What is the state of the interface?
So let's run IP link, it will not be available in the config.
Come on.
So let us run IP link for docos zero.
And here, if you look up the status of the Khosro interface, it is said to down.
If we were to think Google from the Senate, which route does it take, what is the IP address of the
default gateway?
So this can be found not using a single command called IP Route or IP space are, and what we have to
do is look up the default route, which in this case is the very first line.
So the default route goes through the default gateway, which is 172 dots, 17 not zero, not one for
our physical interface industry to select that as the answer.
What is reportedly scheduler is listening on in the master node, so there are multiple ways we can
do that.
We can look up at the configuration of a cube scheduler, which is a static pod.
But that's another way to look at the live board, which the cube Schiller is listening on.
And for that, we'll use that and we'll use these additional flags and add up for process grep for cube
scheduler.
And this will print the process used by Kube scheduler, along with reports that it's listening also,
and I can see that in the very bottom of the screen of the output, the power that is used as one zero
two five one, which is used for my computer.
So look for the listen session and hear the report that is being used as one zero two five one, so
that's our answer.
Notice that a city is listening on two ports, which of these have more plane connections established,
so let's run the same command as before, which is Neistat, but this time we will search for it instead
and we'll look at the different connections on different ports used by the city port.
So here we can see four different listening sessions, and if you observe closely, two, three, seven,
nine used the most.
We also have two three eight zero.
And there is also another four two three eight one, which is also used by each city, but the one that
is used most as two three seven nine.
So that's because two three seven nine is the Port of Exelis, to which all controlled plane components
connect to three, ADRO is used for Peer-to-peer connectivity.
In this case, we do not have additional months.
Not so.
We don't have multiple sessions for that specific port policy.
Last question.
Thank you for joining me in this video.
I'll see you in the next one.