- Lab
-
Libraries: If you want this lab, consider one of these libraries.
- Cloud

Enabling Kernel Modules and Modifying Parameters
In this hands-on lab, you will view the current command-line kernel parameters using `/proc/cmdline` or `dmesg`. With the current configuration noted, next check for a couple of runtime kernel parameters using `sysctl`, followed by using `lsmod` to check the status of specific kernel modules. Based on the status of each, you will used `modprobe` to enable/disable kernel modules and make kernel parameter changes by using `sysctl` and creating configuration files in the appropriate directory locations. The final task will be to reboot the system and confirm the changes. *This course is not approved or sponsored by Red Hat.*

Lab Info
Table of Contents
-
Challenge
Review the Current Kernel Command Line Parameters
- Review the appropriate file or execute the proper command to view the current kernel command line parameters.
- Confirm the
crashkernel
option is set toauto
.
-
Challenge
Confirm the Status of Specific Kernel Runtime Parameters
- Determine if the kernel runtime parameters
net.ipv4.ip_forward
andnet.ipv6.conf.default.forwarding
are enabled. - If either parameter is disabled, immediately enable it using the appropriate command.
- If either parameter is disabled, use
vim
to create a configuration file called/etc/sysctl.d/10-network.conf
. - Add any disabled kernel parameters from the previous step to the
10-network.conf
file and save the changes.
- Determine if the kernel runtime parameters
-
Challenge
Determine the Status of Specific Kernel Modules
- Using the appropriate command, determine the status of the
bluetooth
,bridge
, andcdrom
kernel modules. The status should be set as the following:bluetooth
= inactivebridge
= activecdrom
= active
- If any of the of the modules are incorrectly configured, make the following changes
- If
bluetooth
is enabled, use the appropriate process to ensure the module will not start after a reboot and cannot be manually started. - If
bridge
is disabled, use the appropriate process to enable the command and ensure it will start after a reboot. - If
cdrom
is disabled, use the appropriate process to enable the command and ensure it will start after a reboot.
- If
- Using the appropriate command, determine the status of the
-
Challenge
Validate System Changes
- Reboot the server to ensure changes are applied.
- Log back in after the reboot has completed.
- Confirm the following configuration changes:
- Kernel runtime parameters
- Confirm net.ipv4.ip_forward is enabled.
- Confirm net.ipv6.conf.default.forwarding is enabled.
- Kernel modules
- Confirm
bluetooth
is not active. Check the exclusion list and attempt to manually enable the module. - Confirm
bridge
is active. - Confirm
cdrom
is active
- Confirm
- Kernel runtime parameters
About the author
Real skill practice before real-world application
Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.
Learn by doing
Engage hands-on with the tools and technologies you’re learning. You pick the skill, we provide the credentials and environment.
Follow your guide
All labs have detailed instructions and objectives, guiding you through the learning process and ensuring you understand every step.
Turn time into mastery
On average, you retain 75% more of your learning if you take time to practice. Hands-on labs set you up for success to make those skills stick.