Summary of network connectivity problems caused by RHEL6.1NetworkManager

Summary: The problem that RHEL61NetworkManager causes network connectivity for NICS is the second time today. The NetworkManager in rhel61 system causes network connectivity for NICs. Specifically, log on to a blade at the customer's site to confirm the Nic connection. This RHEL6.1 NetworkManager causes network disconnection of the network adapter. this is the second time today. The NetworkManager in rhel6.1 system causes network disconnection of the network adapter. Specifically, log on to a blade at the customer's site to confirm the Nic connection. The business of this database system is faulty. try to restart the network service (use/etc/init. d/network restart command). after restarting, it turns out that the IP address of the original eth0 Nic is lost. restarting the network service again is still invalid, and the original/etc/resolv. the DNS resolution parameters configured in conf do not take effect. Think of it as RHEL6.1. if NetworkManager is on a laptop or another personal device, it is actually quite good, but if it is on a physical rack server or blade server, it will affect the connection status of the network card. Open the network editing menu in the upper-right corner of the graphic interface, manually apply the "system eth0" configuration, and then re-run the network service. an IP address is displayed again. This is the cause of network information loss. Find the information and confirm that you need to add the parameter NM_CONTROLLED = "no" in the NIC configuration file to disable NetworkManager or remove the managed Nic from The NetworkManager management interface to restore the normal configuration. After the test, individuals prefer the first method, with better results.