RH124 - ch12s06

From workstation, run the lab net-configure start command. The command runs a start script that determine if the host, servera, is reachable on the network.

[student@workstation ~]$ lab net-configure start

Note

If prompted by the sudo command for student's password, enter student as the password.

Use the ssh command to log in to servera as the student user. The systems are configured to use SSH keys for authentication, so a password is not required to log in to servera.
```
[student@workstation ~]$ ssh student@servera
...output omitted...
[student@servera ~]$ 
```
Locate network interface names.
Important
Network interface names are determined by their bus type and the detection order of devices during boot. Your network interface names will vary according to the course platform and hardware in use.
On your system now, locate the interface name (such as ens06 or en1p2) associated with the Ethernet address 52:54:00:00:fa:0a. Use this interface name to replace the enX placeholder used throughout this exercise.
Locate the network interface name associated with the Ethernet address 52:54:00:00:fa:0a. Record or remember this name and use it to replace the enX placeholder in subsequent commands.
```
[student@servera ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enX: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 52:54:00:00:fa:0a brd ff:ff:ff:ff:ff:ff
```

View network settings using nmcli.

Show all connections.

[student@servera ~]$ nmcli con show
NAME                UUID                                  TYPE      DEVICE
Wired connection 1  03da038a-3257-4722-a478-53055cc90128  ethernet  enX

Display only the active connection.
Your network interface name should appear under DEVICE, and the name of the connection active for that device is listed on the same line under NAME. This exercise assumes that the active connection is Wired connection 1.
If the name of the active connection is different, use that instead of Wired connection 1 for the rest of this exercise.
```
[student@servera ~]$ nmcli con show --active
NAME                UUID                                  TYPE      DEVICE
Wired connection 1  03da038a-3257-4722-a478-53055cc90128  ethernet  enX
```

Display all configuration settings for the active connection.

[student@servera ~]$ nmcli con show "Wired connection 1"
connection.id:               Wired connection 1
connection.uuid:             03da038a-3257-4722-a478-53055cc90128
connection.stable-id:        --
connection.type:             802-3-ethernet
connection.interface-name:   --
connection.autoconnect:      yes
...output omitted...
ipv4.method:                 manual
ipv4.dns:                    172.25.250.254
ipv4.dns-search:             lab.example.com,example.com
ipv4.dns-options:            ""
ipv4.dns-priority:           0
ipv4.addresses:              172.25.250.10/24
ipv4.gateway:                172.25.250.254
...output omitted...
GENERAL.NAME:                Wired connection 1
GENERAL.UUID:                03da038a-3257-4722-a478-53055cc90128
GENERAL.DEVICES:             enX
GENERAL.STATE:               activated
GENERAL.DEFAULT:             yes
GENERAL.DEFAULT6:            no
GENERAL.SPEC-OBJECT:         --
GENERAL.VPN:                 no
GENERAL.DBUS-PATH:           /org/freedesktop/NetworkManager/ActiveConnection/1
GENERAL.CON-PATH:            /org/freedesktop/NetworkManager/Settings/1
GENERAL.ZONE:                --
GENERAL.MASTER-PATH:         --
IP4.ADDRESS[1]:              172.25.250.10/24
IP4.GATEWAY:                 172.25.250.254
IP4.ROUTE[1]:                dst = 172.25.250.0/24, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]:                dst = 0.0.0.0/0, nh = 172.25.250.254, mt = 100
IP4.DNS[1]:                  172.25.250.254
IP6.ADDRESS[1]:              fe80::3059:5462:198:58b2/64
IP6.GATEWAY:                 --
IP6.ROUTE[1]:                dst = fe80::/64, nh = ::, mt = 100
IP6.ROUTE[2]:                dst = ff00::/8, nh = ::, mt = 256, table=255

Press q to exit the command.

Show device status.

[student@servera ~]$ nmcli dev status
DEVICE  TYPE      STATE      CONNECTION
enX     ethernet  connected  Wired connection 1
lo      loopback  unmanaged  --

Display the settings for the enX device.

[student@servera ~]$ nmcli dev show enX
GENERAL.DEVICE:              enX
GENERAL.TYPE:                ethernet
GENERAL.HWADDR:              52:54:00:00:FA:0A
GENERAL.MTU:                 1500
GENERAL.STATE:               100 (connected)
GENERAL.CONNECTION:          Wired connection 1
GENERAL.CON-PATH:            /org/freedesktop/NetworkManager/ActiveConnection/1
WIRED-PROPERTIES.CARRIER:    on
IP4.ADDRESS[1]:              172.25.250.10/24
IP4.GATEWAY:                 172.25.250.254
IP4.ROUTE[1]:                dst = 172.25.250.0/24, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]:                dst = 0.0.0.0/0, nh = 172.25.250.254, mt = 100
IP4.DNS[1]:                  172.25.250.254
IP6.ADDRESS[1]:              fe80::3059:5462:198:58b2/64
IP6.GATEWAY:                 --
IP6.ROUTE[1]:                dst = fe80::/64, nh = ::, mt = 100
IP6.ROUTE[2]:                dst = ff00::/8, nh = ::, mt = 256, table=255

Create a static connection with the same IPv4 address, network prefix, and default gateway. Name the new connection static-addr.
Warning
Since access to your machine is provided over the primary network connection, setting incorrect values during network configuration may make your machine unreachable. If this happens, use the Reset button located above what used to be your machine's graphical display and try again.
```
[student@servera ~]$ sudo nmcli con add con-name "static-addr" ifname enX \
type ethernet ipv4.method manual \
ipv4.address 172.25.250.10/24 ipv4.gateway 172.25.250.254
Connection 'static-addr' (15aa3901-555d-40cb-94c6-cea6f9151634) successfully added.
```

Modify the new connection to add the DNS setting.

[student@servera ~]$ sudo nmcli con mod "static-addr" ipv4.dns 172.25.250.254

Display and activate the new connection.

View all connections.

[student@servera ~]$ nmcli con show
NAME                UUID                                  TYPE      DEVICE
Wired connection 1  03da038a-3257-4722-a478-53055cc90128  ethernet  enX
static-addr         15aa3901-555d-40cb-94c6-cea6f9151634  ethernet  --

View the active connection.

[student@servera ~]$ nmcli con show --active
NAME                UUID                                  TYPE      DEVICE
Wired connection 1  03da038a-3257-4722-a478-53055cc90128  ethernet  enX

Activate the new static-addr connection.

[student@servera ~]$ sudo nmcli con up "static-addr"
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2)

Verify the new active connection.

[student@servera ~]$ nmcli con show --active
NAME         UUID                                  TYPE      DEVICE
static-addr  15aa3901-555d-40cb-94c6-cea6f9151634  ethernet  enX

Configure the original connection so that it does not start at boot, and verify that the static connection is used when the system reboots.

Disable the original connection from autostarting at boot.

[student@servera ~]$ sudo nmcli con mod "Wired connection 1" \
connection.autoconnect no

Reboot the system.

[student@servera ~]$ sudo systemctl reboot
Connection to servera closed by remote host.
Connection to servera closed.
[student@workstation ~]$

View the active connection.

[student@workstation ~]$ ssh student@servera
...output omitted...
[student@servera ~]$ nmcli con show --active
NAME         UUID                                  TYPE      DEVICE
static-addr  15aa3901-555d-40cb-94c6-cea6f9151634  ethernet  enX

Test connectivity using the new network addresses.

Verify the IP address.

[student@servera ~]$ ip addr show enX
2: enX: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 52:54:00:00:fa:0a brd ff:ff:ff:ff:ff:ff
    inet 172.25.250.10/24 brd 172.25.250.255 scope global noprefixroute enX
       valid_lft forever preferred_lft forever
    inet6 fe80::6556:cdd9:ce15:1484/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

Verify the default gateway.

[student@servera ~]$ ip route
default via 172.25.250.254 dev enX proto static metric 100
172.25.250.0/24 dev enX proto kernel scope link src 172.25.250.10 metric 100

Ping the DNS address.

[student@servera ~]$ ping -c3 172.25.250.254
PING 172.25.250.254 (172.25.250.254) 56(84) bytes of data.
64 bytes from 172.25.250.254: icmp_seq=1 ttl=64 time=0.225 ms
64 bytes from 172.25.250.254: icmp_seq=2 ttl=64 time=0.314 ms
64 bytes from 172.25.250.254: icmp_seq=3 ttl=64 time=0.472 ms

--- 172.25.250.254 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 46ms
rtt min/avg/max/mdev = 0.225/0.337/0.472/0.102 ms

Exit from servera.

[student@servera ~]$ exit
logout
Connection to servera closed.
[student@workstation ~]$

Finish

On workstation, run the lab net-configure finish script to finish this exercise.

[student@workstation ~]$ lab net-configure finish

This concludes the guided exercise.

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.

378

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-8.2-df5a585

Red Hat System Administration I

Guided Exercise: Configuring Networking from the Command Line

Note

Important

Warning