This means the Redhat kernel hasn't loaded any of the Linux kernel firewall modules, and then the kernel locked itself (which is a security measure in Redhat to prevent the kernel from being modified).
This can only happen for a few reasons:
1) the kernel modules are missing from Redhat
2) the network (or firewall) was started after the kernel was locked (by default we dont apply that until everything else has started, but third party products or modifications may do this earlier, if anything like has been done to the system remove it)
#2 can happen if you're running the desktop GUI, and it doesn't start the network until someone logs into the GUI, or if someone has disabled the network or firewall services to start on boot.
The resolution for this (assuming the kernel modules from Redhat are installed on the system) would be to first:
1) remove any third security software or changes that have been applied to the system since the last time it was working properly
2) make sure the network is configured to start on boot, if you are using the Redhat/Centos GUI as they do not start the network on boot
systemctl enable network
3) make sure the firewall is configured to start on boot
systemctl enable asl-firewall
service asl-firewall
4) reboot the system to unlock the kernel (Redhat does not let you unlock a running kernel) to apply these changes
Or, disable the kernel security measures by setting this to allow kernel module loading.
https://wiki.atomicorp.com/wiki/index.php/ASL_Configuration#ALLOW_kmod_loading
(9901) ASLWCommon::cmd_exec - ERROR: '(1) sudo iptables-save
