Centos 7: failed to bring up/down networking: configure interface for a trunk interface
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.
Could you please advise ? What am doing wrong ?
centos networking vlan
add a comment |
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.
Could you please advise ? What am doing wrong ?
centos networking vlan
add a comment |
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.
Could you please advise ? What am doing wrong ?
centos networking vlan
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.
Could you please advise ? What am doing wrong ?
centos networking vlan
centos networking vlan
edited Aug 7 '15 at 10:56
onedreamcloser
asked Aug 7 '15 at 10:51
onedreamcloseronedreamcloser
383239
383239
add a comment |
add a comment |
13 Answers
13
active
oldest
votes
it seems that disabling NetworkManager did the trick :)
systemctl stop NetworkManager
systemctl disable NetworkManager
Restarting it worked for me (didn't tryrestart
, but usingstart
instead ofdisable
).
– Skippy le Grand Gourou
Dec 1 '15 at 10:31
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
1
@iamsterdam it worked for me, but could you please elaborate why it works after disablingNetworkManager
– Vishrant
Jul 2 '17 at 17:13
add a comment |
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.
add a comment |
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
.
add a comment |
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.
add a comment |
IPV4_FAILURE_FATAL=no
IPV6INIT=yes"
Toggle the value-
IPV4_FAILURE_FATAL=yes
IPV6INIT=no # (if IPV6 not require)
add a comment |
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.
add a comment |
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.
add a comment |
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.
add a comment |
Just comment #UUID
##UUID=XXXXX-XXXX-XXX-XXXXX
Restart network
sudo systemctl restart network
add a comment |
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.
add a comment |
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
add a comment |
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)
add a comment |
Just stop and disable NetworkManager
And once again restart services it will be work
#systemctl stop NetworkManager
#systemctl disable NetworkManager
#service network restart
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
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f220750%2fcentos-7-failed-to-bring-up-down-networking-configure-interface-for-a-trunk-in%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
13 Answers
13
active
oldest
votes
13 Answers
13
active
oldest
votes
active
oldest
votes
active
oldest
votes
it seems that disabling NetworkManager did the trick :)
systemctl stop NetworkManager
systemctl disable NetworkManager
Restarting it worked for me (didn't tryrestart
, but usingstart
instead ofdisable
).
– Skippy le Grand Gourou
Dec 1 '15 at 10:31
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
1
@iamsterdam it worked for me, but could you please elaborate why it works after disablingNetworkManager
– Vishrant
Jul 2 '17 at 17:13
add a comment |
it seems that disabling NetworkManager did the trick :)
systemctl stop NetworkManager
systemctl disable NetworkManager
Restarting it worked for me (didn't tryrestart
, but usingstart
instead ofdisable
).
– Skippy le Grand Gourou
Dec 1 '15 at 10:31
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
1
@iamsterdam it worked for me, but could you please elaborate why it works after disablingNetworkManager
– Vishrant
Jul 2 '17 at 17:13
add a comment |
it seems that disabling NetworkManager did the trick :)
systemctl stop NetworkManager
systemctl disable NetworkManager
it seems that disabling NetworkManager did the trick :)
systemctl stop NetworkManager
systemctl disable NetworkManager
answered Aug 8 '15 at 13:04
onedreamcloseronedreamcloser
383239
383239
Restarting it worked for me (didn't tryrestart
, but usingstart
instead ofdisable
).
– Skippy le Grand Gourou
Dec 1 '15 at 10:31
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
1
@iamsterdam it worked for me, but could you please elaborate why it works after disablingNetworkManager
– Vishrant
Jul 2 '17 at 17:13
add a comment |
Restarting it worked for me (didn't tryrestart
, but usingstart
instead ofdisable
).
– Skippy le Grand Gourou
Dec 1 '15 at 10:31
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
1
@iamsterdam it worked for me, but could you please elaborate why it works after disablingNetworkManager
– Vishrant
Jul 2 '17 at 17:13
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
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
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
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
1
1
@iamsterdam it worked for me, but could you please elaborate why it works after disabling
NetworkManager
– Vishrant
Jul 2 '17 at 17:13
@iamsterdam it worked for me, but could you please elaborate why it works after disabling
NetworkManager
– Vishrant
Jul 2 '17 at 17:13
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
edited Feb 6 '17 at 10:01
Zanna
2,5561023
2,5561023
answered Feb 6 '17 at 9:28
SlyeSlye
6112
6112
add a comment |
add a comment |
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
.
add a comment |
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
.
add a comment |
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
.
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
.
edited Apr 14 '16 at 9:00
techraf
4,183102139
4,183102139
answered Apr 14 '16 at 8:36
gaurav parashargaurav parashar
1111
1111
add a comment |
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
answered Mar 5 '16 at 3:43
zaheerzaheer
1
1
add a comment |
add a comment |
IPV4_FAILURE_FATAL=no
IPV6INIT=yes"
Toggle the value-
IPV4_FAILURE_FATAL=yes
IPV6INIT=no # (if IPV6 not require)
add a comment |
IPV4_FAILURE_FATAL=no
IPV6INIT=yes"
Toggle the value-
IPV4_FAILURE_FATAL=yes
IPV6INIT=no # (if IPV6 not require)
add a comment |
IPV4_FAILURE_FATAL=no
IPV6INIT=yes"
Toggle the value-
IPV4_FAILURE_FATAL=yes
IPV6INIT=no # (if IPV6 not require)
IPV4_FAILURE_FATAL=no
IPV6INIT=yes"
Toggle the value-
IPV4_FAILURE_FATAL=yes
IPV6INIT=no # (if IPV6 not require)
edited Mar 31 '16 at 4:41
MelBurslan
5,29011533
5,29011533
answered Mar 31 '16 at 4:36
Rajeev RahmanRajeev Rahman
12
12
add a comment |
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
edited Feb 7 '17 at 16:22
Jeff Schaller
39.6k1054126
39.6k1054126
answered Feb 7 '17 at 16:00
Prem-Cloud-labPrem-Cloud-lab
1
1
add a comment |
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
answered May 11 '17 at 10:29
AbdullahAbdullah
1
1
add a comment |
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
edited Aug 18 '17 at 5:10
αғsнιη
16.7k102865
16.7k102865
answered Aug 18 '17 at 4:44
kali dosskali doss
1
1
add a comment |
add a comment |
Just comment #UUID
##UUID=XXXXX-XXXX-XXX-XXXXX
Restart network
sudo systemctl restart network
add a comment |
Just comment #UUID
##UUID=XXXXX-XXXX-XXX-XXXXX
Restart network
sudo systemctl restart network
add a comment |
Just comment #UUID
##UUID=XXXXX-XXXX-XXX-XXXXX
Restart network
sudo systemctl restart network
Just comment #UUID
##UUID=XXXXX-XXXX-XXX-XXXXX
Restart network
sudo systemctl restart network
edited Oct 26 '17 at 5:23
G-Man
13k93365
13k93365
answered Oct 26 '17 at 5:11
user257466user257466
1
1
add a comment |
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
answered Dec 6 '17 at 17:19
Franco CorreaFranco Correa
1
1
add a comment |
add a comment |
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
add a comment |
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
add a comment |
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
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
answered Jun 12 '18 at 19:39
Christian AchilliChristian Achilli
1012
1012
add a comment |
add a comment |
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)
add a comment |
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)
add a comment |
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)
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)
answered Jan 14 at 12:23
OneKOneK
893
893
add a comment |
add a comment |
Just stop and disable NetworkManager
And once again restart services it will be work
#systemctl stop NetworkManager
#systemctl disable NetworkManager
#service network restart
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
add a comment |
Just stop and disable NetworkManager
And once again restart services it will be work
#systemctl stop NetworkManager
#systemctl disable NetworkManager
#service network restart
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
add a comment |
Just stop and disable NetworkManager
And once again restart services it will be work
#systemctl stop NetworkManager
#systemctl disable NetworkManager
#service network restart
Just stop and disable NetworkManager
And once again restart services it will be work
#systemctl stop NetworkManager
#systemctl disable NetworkManager
#service network restart
edited Jun 15 '17 at 11:31
Archemar
19.8k93570
19.8k93570
answered Jun 15 '17 at 5:23
Rana ChatterjeeRana Chatterjee
1
1
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
add a comment |
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
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
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
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f220750%2fcentos-7-failed-to-bring-up-down-networking-configure-interface-for-a-trunk-in%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown