10

The switch configured on the server (Centos 7) is configured as trunk for VLAN#115,2014. I have loaded 

# lsmod | grep 8021q
# modprobe 8021q

I would like to configure an IP address on the server using the VLAN#115 Performing the following configuration:

ifcfg-em1

TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=em1
UUID=c0c4d851-d762-4301-8c20-d6128aee5261
DEVICE=em1
ONBOOT=yes

ifcfg-em1.115

TYPE=Ethernet
BOOTPROTO=none
IPADDR=172.31.141.242
PREFIX=24
GATEWAY=172.31.141.1
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=em1.115
UUID=c0c4d851-d762-4301-8c20-d6128aee5261
DEVICE=em1.115
VLAN=yes
ONBOOT=yes

I ended up being not able to restart the network service. The error message appearing is : 

Failed to start LSB: Bring up/down networking.

What am doing wrong ?

Improve this question

13 Answers 13

Active Oldest Votes
26

it seems that disabling NetworkManager did the trick :)

systemctl stop NetworkManager
systemctl disable NetworkManager
Improve this answer
4
  • 1
    Restarting it worked for me (didn't try restart, but using start instead of disable). – Skippy le Grand Gourou Dec 1 '15 at 10:31
  • 1
    you make my day! my VLAN and Bonding settings were not be able to start after server update and all because of the NetworkManager. – fuser Nov 25 '16 at 9:30
  • 2
    @iamsterdam it worked for me, but could you please elaborate why it works after disabling NetworkManager – Vishrant Jul 2 '17 at 17:13
  • 1
    thats was awesome... – Muthukumar Anbalagan Aug 10 '19 at 12:42
10

Maybe a little late, but the problem in my case was that the UUID field of the two interfaces was the same, and they must be unique. Disabling NetworkManager does the trick, but the real solution would be changing/deleting the field. Leaving this here for future reference.

Improve this answer
2

I was facing the same issue. Fortunately,

/etc/rc.d/init.d/network stop

gracefully stopped the network service. Then I did an:

ip addr flush dev <<dev-name>>

After that you can start the service, using either systemctl or /etc/rc.d/init.d/network start.

Improve this answer
2

I had this error after importing a VM. The solution is to fix the HW address in the /etc/sysconfig/network-scripts/ifcfg-ens32 (ens32 happened to be my interface. You can check yours using Network Manager with nmtui)file.

Type 'ip addr' and note down the HW addr of your interface, for example 00:50:56:8d:6a:9e.Look up for the interface you are interested in from the list you get from 'ip addr'.

Open to edit your /etc/sysconfig/network-scripts/ifcfg-ens32 (change ifcfg-ens32 with your interface name, as said above get it from nmtui) and modify that address next to the key HWADDR.

Now: service network restart

Improve this answer
1
  • This solved the problem I faced after deploying a Centos 7 VM using KubeVirt. – nelsonspbr Mar 16 at 7:05
1
IPV4_FAILURE_FATAL=no
IPV6INIT=yes"

Toggle the value-

IPV4_FAILURE_FATAL=yes
IPV6INIT=no # (if IPV6 not require)
Improve this answer
1

restart my machine and network service are not resolved this issue in my linux box.

I have removed the file /etc/sysconfig/network-scripts/ifcfg-eth0 and then recreated the file with different name ifcfg-eth1 with static ip details. After that I have started network service and it worked.

Improve this answer
0

you need to add following in you file HWADDR="xx:xx:xx:xx:xx:xx" where xxxx is the real or cloned mac address of your interface card you can find by issuing command ifconfig -a.

Improve this answer
0

Remove any additional ifcfg-Wiredconnection1 or -2 of the new adapters you have added on the server that are not used by the l2 or l3 network and restart. It will work.

Improve this answer
0

This will solve the problem!

# rm /etc/udev/rules.d/70-persistent-ipoib.rules 

# reboot
  • Now edit /etc/sysconfig/network-scripts/ifcfg-eth0,
  • Add new HWADDR generated or remove it
  • Remove UUID line

-Restart the networking service

 #systemctl restart network.service

NOW! Working.

Improve this answer
0

  1. Just comment #UUID

    ##UUID=XXXXX-XXXX-XXX-XXXXX

  2. Restart network

    sudo systemctl restart network
Improve this answer
0

I had same problem with LSB in Centos and Ubunto on VMware. I solved it turn off Wifi on host (real machine) and turn on, and reboot the guest.

Improve this answer
0

For me, it was a missing file/entry: /etc/sysconfig/network.

Without file and gateway:

[root@randomHost ~]# file /etc/sysconfig/network
/etc/sysconfig/network: cannot open (No such file or directory)
[root@randomHost ~]#
[root@randomHost ~]#
[root@randomHost ~]# systemctl status network.service
● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2019-01-07 10:53:38 UTC; 1 weeks 0 days ago
     Docs: man:systemd-sysv-generator(8)
Jan 07 10:53:38 randomHost systemd[1]: network.service failed.

After adding file and gateway:

[root@randomHost ~]# 
[root@randomHost ~]# echo "GATEWAY=10.XX.XX.XX" >> /etc/sysconfig/network
[root@randomHost ~]# 
[root@randomHost ~]# systemctl status network.service
● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: active (exited) since Mon 2019-01-14 12:18:28 UTC; 2s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 329008 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=0/SUCCESS)
Improve this answer
-1

Just stop and disable NetworkManager

And once again restart services it will be work

#systemctl stop NetworkManager
#systemctl disable NetworkManager

#service network restart
Improve this answer
2
  • This is no different from the accepted answer (other than being badly formatted). Your answer should add some value such as explaining why disabling Network Manager fixes the problem and perhaps mention when it makes sense to do so. – Anthony Geoghegan Jun 15 '17 at 8:53
  • Upvoting - this helped me even though the accepted answer did not. It could be that I didn't read the question properly and just quickly scrolled through the answers but restarting NetworkManager alone didn't seem to do anything. Maybe its obvious but only because I saw this did I think to try restarting network after stopping NetworkManager – ec2011 Mar 8 '19 at 12:19

Not the answer you're looking for? Browse other questions tagged or ask your own question.