RH124 - ch15s05

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-rh124-review4

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
IPv4 address 172.25.250.111
Netmask 255.255.255.0
Gateway 172.25.250.254
DNS Server 172.25.250.254
Set the serverb hostname to server-review4.lab4.example.com.
On serverb, set client-review4 as the canonical hostname for the servera 172.25.250.10 IPv4 address.
Configure the static connection profile with an additional IPv4 address of 172.25.250.211 with a netmask of 255.255.255.0. Do not remove the existing IPv4 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.

Parameter	Setting
IPv4 address	172.25.250.111
Netmask	255.255.255.0
Gateway	172.25.250.254
DNS Server	172.25.250.254

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.
1. Display the network connection information.
```
[root@serverb ~]# nmcli device status
DEVICE  TYPE      STATE      CONNECTION
eth0    ethernet  connected  Wired connection 1
lo      loopback  unmanaged  --
```
  In this example, eth0 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:
IPv4 address 172.25.250.111
Netmask 255.255.255.0
Gateway 172.25.250.254
DNS server 172.25.250.254
1. Create the static connection profile with the provided network settings.
```
[root@serverb ~]# nmcli connection add con-name static type ethernet \
ifname ethX ipv4.addresses '172.25.250.111/24' ipv4.gateway '172.25.250.254' \
ipv4.dns '172.25.250.254' ipv4.method manual
Connection 'static' (ac8620e6-b77e-499f-9931-118b8b015807) successfully added.
```
2. Activate the new connection profile.
```
[root@serverb ~]# nmcli connection up static
```
Set the serverb hostname to server-review4.lab4.example.com. Verify the new hostname.
1. Configure server-review4.lab4.example.com as the new hostname.
```
[root@serverb ~]# hostnamectl hostname server-review4.lab4.example.com
[root@serverb ~]# hostname
server-review4.lab4.example.com
```

On serverb, set client-review4 as the canonical hostname for the servera 172.25.250.10 IPv4 address.

Edit the /etc/hosts file and add client-review4 as a name for the 172.25.250.10 IPv4 address.
```
172.25.250.10 client-review4
```

Verify that you can reach the servera 172.25.250.10 IPv4 address by using the canonical client-review4 hostname.

[root@serverb ~]# ping -c2 client-review4
PING client-review4 (172.25.250.10) 56(84) bytes of data.
64 bytes from client-review4 (172.25.250.10): icmp_seq=1 ttl=64 time=0.259 ms
64 bytes from client-review4 (172.25.250.10): icmp_seq=2 ttl=64 time=0.391 ms

--- client-review4 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 33ms
rtt min/avg/max/mdev = 0.259/0.325/0.391/0.066 ms

Modify the static connection profile to configure the additional 172.25.250.211 IPv4 address with the 255.255.255.0 netmask. Do not remove the existing IPv4 address. Verify that serverb responds to all addresses when the static connection profile is active.

Add the 172.25.250.211 IP address to the static connection.

[root@serverb ~]# nmcli connection modify static \
+ipv4.addresses '172.25.250.211/24'

Activate the new IP address.

[root@serverb ~]# nmcli connection up static
...output omitted...

From workstation, use the ping command to verify that the 172.25.250.211 IPv4 address is reachable.

[student@workstation ~]$ ping -c2 172.25.250.211
PING 172.25.250.211 (172.25.250.211) 56(84) bytes of data.
64 bytes from 172.25.250.211: icmp_seq=1 ttl=64 time=0.246 ms
64 bytes from 172.25.250.211: icmp_seq=2 ttl=64 time=0.296 ms

--- 172.25.250.211 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 50ms
rtt min/avg/max/mdev = 0.246/0.271/0.296/0.025 ms

On serverb, restore the original settings by activating the original network profile.
1. Return to the console and use the nmcli command to activate the original network profile.
```
[root@serverb ~]# nmcli connection up "Wired connection 1"
...output omitted...
```
  The original connection profile name might differ on serverb. Replace the name in this solution with the name from your system. Find the profile name with the nmcli connection show command.
2. From workstation, log in to serverb as the student user to verify that the original network settings are active.
```
[student@workstation ~]$ ssh student@serverb
...output omitted...
[student@server-review4 ~]$
```
3. Exit any extra terminals. Return to the workstation system as the student user.
```
[student@server-review4 ~]$ exit
logout
Connection to serverb closed.
[student@workstation ~]$
```

Evaluation

As the student user on the workstation machine, use the lab command to grade your work. Correct any reported failures and rerun the command until successful.

[student@workstation ~]$ lab grade rhcsa-rh124-review4

Finish

On the workstation machine, change to the student user home directory and use the lab command to complete this exercise. This step is important to ensure that resources from previous exercises do not impact upcoming exercises.

[student@workstation ~]$ lab finish rhcsa-rh124-review4

This concludes the section.

Discuss Red Hat System Administration I

Go to community

RH124 Chapter 15 Lab 3: Install zsh Package

VictoriaB97

16 sty 2024

Hello,I am trying to finish up Lab 3 of the Chapter 15 Comprehensive Review Labs in RH124, and when I type in sudo dnf install zsh for the 6th specification of the lab, I get an error message basically saying that it failed to download metadata for the repo 'ansible-2.9-for-rhel-9-x86_64-rpms', and that they could not download repomd.xml. It provided a 404 status code.Can someone please let me know what the problem is, and if there is a current workaround? Thanks.

377

Red Hat System Administration I | Guided Exercise: Explain and Investigate RPM Software Pack

AbeHiero

10 lis 2023

I cannot start the lab with command: lab start software-rpm. I get this error:ModuleNotFoundError: No module named 'rhcsa-classroom'Script software-rpm not in course library rhcsa-classroom Anyone else see this?

172

Red Hat System Administration I (RH124)

Haley_Ruccio

19 lip 2023

The first of two courses covering the core system administration tasks needed to manage Red Hat Enterprise Linux serversRed Hat System Administration I (RH124) is designed for IT professionals without previous Linux system administration experience. The course provides students with Linux administration competence by focusing on core administration tasks. This course also provides a foundation for students who plan to become full-time Linux system administrators by introducing key command-line concepts and enterprise-level tools. This course is the first of a two-course series that takes a computer professional without Linux system administration knowledge to become a fully capable Linux administrator. These concepts are further developed in the follow-on course, Red Hat System Administration II (RH134).This course is based on Red Hat® Enterprise Linux 9.0.Course content summaryIntroduce Linux and the Red Hat Enterprise Linux ecosystem.Run commands and view shell environments.Manage, organize, and secure files.Manage users, groups and user security policies.Control and monitor systemd services.Configure remote access using the web console and SSH.Configure network interfaces and settings.Manage software using DNFAudience for this courseThe primary persona is a technical professional with current or pending responsibilities as a Linux enterprise or cloud system administrator.This course is popular in Red Hat Academy, and is targeted at the student who is planning to become a technical professional using Linux.Prerequisites for this courseBasic technical user skills with computer applications on some operating systems are expected.Take our free assessment to gauge whether this offering is the best fit for your skills.Technology considerationsThere are no special technical requirements for this course.This course is not designed for bring your own device (BYOD).Internet access is not required but is recommended so that students can research and browse Red Hat online resources.

336

Revision: rh124-9.0-398f302