Red Hat System Administration I

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

serverb login: student
Password: student
[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               System eth0
   eth1    ethernet  connected               System eth1
   lo      loopback  connected (externally)  lo

   In this example, eth0 is the Ethernet interface name. The connection profile name is System eth0. 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:

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.

1. 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

2. 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.

1. 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'

2. Activate the new IP address.

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

3. 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 "System eth0"
   ...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 ~]$