Red Hat System Administration I

In the web page that controls your lab environment, click the OPEN CONSOLE button for serverb. A tab will open in your browser with the console session for serverb. Log in as user student at the prompt.

It is a useful practice to make network changes from the server console, whether locally or through remote console access hardware. When using ssh to adjust networking settings, a mistaken command can hang or lock out your session. Network configuration corrections must then be made through the console.

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

The network interface and initial connection profile names might differ on your serverb. Use the name shown by your system to replace the enX placeholder name in the steps of this solution.

Use nmcli to create the static connection with the given network settings.

[student@serverb ~]$ sudo nmcli connection add con-name static type ethernet \
ifname enX ipv4.addresses '172.25.250.111/24' ipv4.gateway '172.25.250.254' \
ipv4.dns '172.25.250.254' ipv4.method manual 
[sudo] password for student: student
Connection 'static' (ac8620e6-b77e-499f-9931-118b8b015807) successfully added.

Use the nmcli command to activate the new connection settings.

[student@serverb ~]$ sudo nmcli connection up static

[student@serverb ~]$ sudo hostnamectl set-hostname server-review4.lab4.example.com
[sudo] password for student: student
[student@serverb ~]$ hostname
server-review4.lab4.example.com

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

172.25.250.10 servera.lab.example.com servera client-review4

Use the ping command to verify that you can reach 172.25.250.10 using the canonical host name client-review4.

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

--- servera.lab.example.com 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

Use the nmcli command to add the new IP address.

[student@serverb ~]$ sudo nmcli connection modify static \
+ipv4.addresses '172.25.250.211/24'

Use the nmcli command to activate the new IP address.

[student@serverb ~]$ sudo nmcli connection up static
...output omitted...

From workstation, use the ping command to verify that the IPv4 address 172.25.250.211 can be reached.

[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

Return to the console and use the nmcli command to activate the original network profile.

[student@serverb ~]$ sudo nmcli connection up "Wired connection 1"
...output omitted...

The original connection profile name might differ on your serverb. Replace the name shown in this solution with the name from your system. Find the name with nmcli connection show.

From workstation, open an SSH session to serverb as student to verify that the original network settings are successfully activated.

[student@workstation ~]$ ssh student@serverb
...output omitted...
[student@server-review4 ~]$ 

Log out of serverb and exit all but one terminal on workstation.

[student@server-review4 ~]$ exit
logout
Connection to serverb closed.
[student@workstation ~]$