Centos 7: failed to bring up/down networking: configure interface for a trunk interfa
hi guys,
The switch configured on the server (Centos 7) is configured as trunk for VLAN#115,2014. I have loaded Code:
# lsmod | grep 8021q ifcfg-em1 Code:
TYPE=Ethernet Code:
TYPE=Ethernet Code:
Failed to start LSB: Bring up/down networking. |
I think you need "BOOTPROTO=none" to be changed to "BOOTPROTO=static" for ifcfg-em1.115
I know "none" used to work for static IP numbers, but that use was being changed to "static" in CenOS 6 though both worked. I believe there is a plan to be able to add other methods in the future, and using static makes it clear what is being done. I'm not sure about whether the base interface can remain uninitialized (never tried that). If it doesn't start (and since there is no IP numbers there, it can't be initialized), you might try "onboot=no" for ifcfg-em1. |
thanks jpollard. your comment made sense. i just tried. but with no luck.
with ONBOOT=yes "journalctl -xn" says "Unit network.service has failed." with ONBOOT=no "journalctl -xn" says "(warn) Activation failed for connection em1" |
the following did the trick:
Code:
systemctl stop NetworkManager |
Quote:
enabling networks in addition would allow it to work. |
Quote:
After a yum update all, I had centos-release-7-4.1708.el7.centos.x86_64 and kernel-3.10.0-693.2.2.el7.x86_64. Network.services failed to load during boot: "Failed to start LSB: Bring up/down networking." The reason for that failure was that "Determining IP information for eth0... failed." And the reason that IP information for eth0 failed was that something mangled the addresses for my server, gateway, and DNS servers in /etc/sysconfig/network-scripts/ifcfg-eth0. The definition of BOOTPROTO was changed from "static" to "dhcp", and all of the IP addresses were stripped out of ifcfg-eth0. In my case, I chose to work with NetworkManager rather than network.services (or a combination of both). I disabled cloud-init, which kept rewriting /etc/sysconfig/network-scripts/ifcfg-eth0 on each boot by creating /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with this single line in it: network: {config: disabled} Because I turned off network.services, I set "NM_CONTROLLED=yes" for both ifcfg-eth0 and ifcfg-eth1. The Apache daemon still failed to start. It seemed to be a timing issue during the boot process. I created /etc/NetworkManager/dispatcher.d/22-httpd as shown below. The system calls it when NetworkManager thinks it is open for business. Code:
#!/bin/sh |
All times are GMT -5. The time now is 08:53 PM. |