How to Disable Network Manager Prior to CPanel DNS Only Install

VPS Dedicated Servers > Applications - Linux Servers > CPanel - DNS Only
 
Skip to end of metadata
 
Go to start of metadata
 

 

 

Overview

This document describes how to disable the Network Manager service. The Network Manager service automates the network's settings and disrupts connections to the IP addresses that reside in the ipaliases module.

Note:

We recommend that you disable the Network Manager service and enable the network.service service before you install cPanel & WHM.

For more information about how to disable the Network Manager service, read RedHat's Disabling Network Manager documentation.

Warnings:

  • cPanel, Inc. does not support the Network Manager service.
  • Exercise extreme caution when you disable the Network Manager. Your server may lose its network services if you do not disable Network Manager correctly. 

Disable the Network Manager service

To disable the Network Manager service, perform the following steps:

Important:

Perform these steps from the server's console in order to prevent any interruption to network connectivity.

  1. Disable Network Manager with the following commands: 

     Disable NetworkManager on CentOS 6, CloudLinux 6, Red Hat Enterprise Linux 6 (RHEL), or Amazon Linux...
    1
    2
    service NetworkManager stop
    chkconfig NetworkManager off
     Disable NetworkManager on CentOS 7, CloudLinux 7, or RHEL 7...
    1
    2
    systemctl stop NetworkManager.service
    systemctl disable NetworkManager.service

  2. Change to the /etc/sysconfig/network-scripts directory.

  3. Open the ifcfg-eth0 and ifcfg-lo files with your preferred text editor and, if they exist, set the following keys' values:

    1
    2
    NM_CONTROLLED=no
    ONBOOT=yes

    Important:

    If either of these keys does not exist in your ifcfg-eth0 and ifcfg-lo files, do not add it. Instead, proceed to Step 4.

  4. Run the following commands to restart the network:

     Restart the network on CentOS 6, CloudLinux 6, RHEL 6, or Amazon Linux...
    1
    2
    chkconfig network on
    service network start
     Restart the network on CentOS 7, CloudLinux 7, or RHEL 7...
    1
    2
    systemctl enable network.service
    systemctl start network.service
     
 
 
 
Source: Another Way
 

How To Uninstall, Disable, and Remove NetworkManager from RHEL6 and CentOS6

Article Views: 1,388

The default install of Red Hat Enterprise Linux 6 (RHEL6 and CentOS6) automatically includes the NetworkManager service which was optional in previous versions. The purpose for NetworkManager is to make RHEL6 more portable which is great for a notebook computer or perhaps a desktop. Portability is not a major concern for a server. Usually servers are fairly fixed and configuration of network settings is done statically using manual tools. NetworkManager also does not support many advanced networking features like IP forwarding.

Textbooks and forum posts tell us to simply use yum to uninstall NetworkManager and then go about setting up our server manually as we have in the past. Unfortunately it is not that easy. RHEL6 also includes the new udev system that is great for removeable devices, but presents problems for server network configuration. In my humble opinion, there is no simple way to reverse these changes in RHEL6.

After researching on the Internet, and a little trial and error, here are my suggestions on how to uninstall, disable, and remove NetworkManager from a RHEL6 server:

  1. Turn off the service, uninstall it, and make sure you do not try to run it after a reboot: 
    service NetworkManager stop
chkconfig NetworkManager off
yum erase NetworkManager
  2. Find and remove 70-persistent-net.rules and 75-persistent-net-generator.rules: 
    rm -f /etc/udev/rules.d/70-persistent-net.rules
rm -f /lib/udev/rules.d/75-persistent-net-generator.rules
  3. Manually configure your network interfaces and DNS, and then restart the network service. Here is an example /etc/sysconfig/network-scripts/ifcfg-eth0 file from one of our VMware virtual servers that has been successfully cloned many times: 
    DEVICE=eth0
NM_CONTROLLED=no     
ONBOOT=yes
BOOTPROTO=dhcp       # DHCP client; dynamic address assignment
TYPE=Ethernet
DNS1=192.168.10.254  # Insert your nameserver address in this directive
USERCTL=no
PEERDNS=yes
IPV6INIT=no

    Check your interfaces and DNS, then restart the network service:

    system-config-network
service network restart

At this point you should have total manual control of your network interfaces similar to the way we did it back in the days of RHEL4 and 5. If you receive an error message informing you that your interface does not exist, try rebooting your server. You may have to manually edit the /etc/sysconfig/network-scripts/ifcfg-ethx  file to remove unneeded lines created by NetworkManager. If all else fails, create a new /etc/sysconfig/network-scripts/ifcfg-ethx  file from scratch and start the network service.

Article ID: 278, , Modified: January 3, 2019 at 8:55 AM

Add Feedback

Was this article helpful?

Share this article

FacebookGoogle+TwitterOther Social NetworksPrint