Shulou(Shulou.com)06/01 Report--

This article will explain in detail what to do about Failed to start LSB: Bring up/down networking errors caused by vmware centos7 clone mac addresses. The editor thinks it is very practical, so I share it with you as a reference. I hope you can get something after reading this article.

[root@localhost] # ip addr1: lo: link/loopback 0012 scope host valid_lft forever preferred_lft forever2: eno16777736: link/ether 00:0f:19:10:12:f1 brd ff:ff:ff:ff:ff:ff inet 127.0.0.1 8 scope host lo valid_lft forever preferred_lft forever inet6:: 1 scope host lo valid_lft forever preferred_lft forever inet6 128. 168.38.135/24 brd 192.168.38.255 scope global dynamic eno16777736 valid_lft 1681sec preferred_lft 1681sec inet6 fe80::20c:11aa:ae11:4fe4/64 scope link valid_lft forever preferred_lft forever

1. The following error occurred when executing service network restart

Restarting network (via systemctl): Job for network.service failed. See 'systemctl status network.service' and' journalctl-xn' for details.

2. According to the above prompt, execute "systemctl status network.service" to output similar information as follows:

[root@localhost] # systemctl status network.servicenetwork.service-LSB: Bring up/down networking Loaded: loaded (/ etc/rc.d/init.d/network) Active: failed (Result: exit-code) since three 2014-11-05 15:30:10 CST 1min 5s ago November 05 15:30:10 localhost.localdomain network [2920]: RTNETLINK answers: File exists11 05 15:30:10 localhost.localdomain network [2920]: RTNETLINK answers: File exists11 05 15:30:10 localhost.localdomain network [2920]: RTNETLINK answers: File exists11 05 15:30:10 localhost.localdomain network [2920]: RTNETLINK answers: File exists11 05 15:30:10 localhost.localdomain network [2920]: RTNETLINK answers: File exists11 05 15:30:10 localhost.localdomain network [2920]: RTNETLINK Answers: File exists11 05 15:30:10 localhost.localdomain network [2920]: RTNETLINK answers: File exists11 05 15:30:10 localhost.localdomain systemd [1]: network.service: control process exited Code=exited status=111 05 15:30:10 localhost.localdomain systemd [1]: Failed to start LSB: Bring up/down networking.11 05 15:30:10 localhost.localdomain systemd [1]: Unit network.service entered failed state.

3, for the above tips, how to correct, followed by a series of searches (omitting 2000 words + countless despair + countless tears), and finally google (other searches are a waste of time), finding a solution is actually very simple (because there is no 70-persistent-net.rules file in centos7, the copied virtual machine (vmware) needs to modify the mac address), that is, to modify the mac address.

4. How to check the mac address of the virtual machine copied by centos7, you need to execute "ip addr" and output similar information as follows:

Notice the bold and red words above, this is the new mac address.

All that's left is to modify the ifcfg-XXX file, just modify the HWADDR. Next, it is normal to execute service network restart.

This is the end of the article on "vmware centos7 clone mac address causes Failed to start LSB: what to do with Bring up/down networking errors". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.