Please provide command for below exercies:Lab: Manage Networks

Note

If you plan to take the RHCSA exam, then use the following approach to maximize the benefit of this Comprehensive Review: attempt each lab without viewing the solution buttons or referring to the course content. Use the grading scripts to gauge your progress as you complete each lab.

In this review, you configure and test network connectivity.

Outcomes

Configure network settings.

Test network connectivity.

Set a static hostname.

Use locally resolvable canonical hostnames to connect to systems.

If you did not reset your workstation and server machines at the end of the last chapter, then save any work that you want to keep from earlier exercises on those machines, and reset them now.

As the student user on the workstation machine, use the lab command to prepare your system for this exercise.

This command prepares your environment and ensures that all required resources are available.

$[$student@workstation ~$]$$ lab start rhcsa$-$rh$124-$review$4$

Important

When you use the ssh command to adjust networking settings, an incorrect command might hang or lock out your session. You are then disconnected from the server, and thus the server becomes inaccessible. You must adjust the network configuration through the server console, locally or through a remote console.

In this review, open the serverb machine console to adjust the networking settings.

Specifications

On serverb, determine the name of the Ethernet interface and its active connection profile.

On serverb, create and activate a static connection profile for the available Ethernet interface. The static profile statically sets network settings and does not use DHCP$.$ Configure the static profile to use the network settings in the following table:

Parameter Setting

IPv$4$ address $172\mathrm{.}25\mathrm{.}250\mathrm{.}111$

Netmask $255\mathrm{.}255\mathrm{.}255\mathrm{.}0$

Gateway $172\mathrm{.}25\mathrm{.}250\mathrm{.}254$

DNS Server $172\mathrm{.}25\mathrm{.}250\mathrm{.}254$

Set the serverb hostname to server$-$review$4.$lab$4.$example.com.

On serverb, set client$-$review$4$ as the canonical hostname for the servera $172\mathrm{.}25\mathrm{.}250\mathrm{.}10$ IPv$4$ address.

Configure the static connection profile with an additional IPv$4$ address of $172\mathrm{.}25\mathrm{.}250\mathrm{.}211$ with a netmask of $255\mathrm{.}255\mathrm{.}255\mathrm{.}0.$ Do not remove the existing IPv$4$ address. Ensure that serverb responds to all addresses when the static connection is active.

On serverb, restore the original network settings by activating the original network connection profile.

Use the system console to log in as the student user on the serverb machine, and switch to the root user.

$[$student@serverb ~$]$$ sudo $-$i

$[$sudo$]$ password for student: student

$[$root@serverb ~$]$#

On serverb, determine the Ethernet interface name and the connection profile name that it uses.

Display the network connection information.

$[$root@serverb ~$]$# nmcli device status

DEVICE TYPE STATE CONNECTION

eth$0$ ethernet connected Wired connection $1$

lo loopback unmanaged $--$

In this example, eth$0$ is the Ethernet interface name. The connection profile name is Wired connection $1.$ Create the static connection profile for this interface.

Note

The network interface and connection profile names might differ from the previous output. Use the name that your system shows to replace the ethX placeholder name in subsequent steps.

On serverb, create the static connection profile for the ethX interface. Set the network settings statically so that it does not use DHCP$.$ When done, activate that connection profile. Base the settings on the following table:

IPv$4$ address $172\mathrm{.}25\mathrm{.}250\mathrm{.}111$

Netmask $255\mathrm{.}255\mathrm{.}255\mathrm{.}0$

Gateway $172\mathrm{.}25\mathrm{.}250\mathrm{.}254$

DNS server $172\mathrm{.}25\mathrm{.}250\mathrm{.}254$

Create the static connection profile with the provided network settings.

$[$root@serverb ~$]$# nmcli connection add con$-$name static type ethernet $\backslash$

ifname ethX ipv$4.$addresses $\text{'}172\mathrm{.}25\mathrm{.}250\mathrm{.}111/24\text{'}$ ipv$4.$gateway $\text{'}172\mathrm{.}25\mathrm{.}250\mathrm{.}254\text{'}\backslash$

ipv$4.$dns $\text{'}172\mathrm{.}25\mathrm{.}250\mathrm{.}254\text{'}$ ipv$4.$method manual

Connection 'static' $($ac$8620$e$6-$b$77$e$-499$f$-9931-118$b$8$b$015807)$ successfully added.

Activate the new connection profile.

$[$root@serverb ~$]$# nmcli connection up static

Set the serverb hostname to server$-$review$4.$lab$4.$example.com. Verify the new hostname.

Configure server$-$review$4.$lab$4.$example.com as the new hostname.

$[$root@serverb ~$]$# hostnamectl hostname server$-$review$4.$lab$4.$example.com

$[$root@serverb ~$]$# hostname

server$-$review$4.$lab$4.$example.com

On serverb, set client$-$review$4$ as the canonical hostname for the servera $172\mathrm{.}25\mathrm{.}250\mathrm{.}10$ IPv$4$ address.

Edit the $/$etc$/$hosts file and add client$-$review$4$ as a name for the $172\mathrm{.}25\mathrm{.}250\mathrm{.}10$ IPv$4$ address.

$172\mathrm{.}25\mathrm{.}250\mathrm{.}10$ client$-$review$4$

Verify that you can reach the servera $172\mathrm{.}25\mathrm{.}250\mathrm{.}10$ IPv$4$ address by using the canonical client$-$review$4$ hostname.

$[$root@serverb ~$]$# ping $-$c$2$ client$-$review$4$

PING client$-$review$4(172\mathrm{.}25\mathrm{.}250\mathrm{.}10)56(84)$ bytes of data.

$64$ bytes from client$-$review$4(172\mathrm{.}25\mathrm{.}250\mathrm{.}10)$: icmp$\_$seq$=1$ ttl$=64$ time$=0\mathrm{.}259$ ms

$64$ bytes from client$-$review$4(172\mathrm{.}25\mathrm{.}250\mathrm{.}10)$: icmp$\_$seq$=2$ ttl$=64$ time$=0\mathrm{.}391$ ms

$---$ client$-$review$4$ ping stati