bond/bridge can only brought up manually

Issues related to configuring your network
Post Reply
mixmegapol
Posts: 6
Joined: 2015/08/17 04:05:30

bond/bridge can only brought up manually

Post by mixmegapol » 2021/07/16 09:49:52

Hello all,

CentOS 8.3

I got stuck with my network-configuration.
I have:
-ens1f1np1
-ens1f0np0

- bond0 -> existing of ens1f1np1 and ens1f0np0
- br0 -> on top of bond0

When I boot my server, the interfaces aren't coming up,
when I do an if up in the order as above, it works.

What do I have to do, so it starts automatically?

NetworkManager is activated; but I created the ifcfg-files manually.

Any help is appreciated
Regards
Daniel

User avatar
TrevorH
Site Admin
Posts: 33191
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: bond/bridge can only brought up manually

Post by TrevorH » 2021/07/16 10:02:35

Do all the ifcfg files contain ONBOOT=yes ?
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

tunk
Posts: 1204
Joined: 2017/02/22 15:08:17

Re: bond/bridge can only brought up manually

Post by tunk » 2021/07/16 10:08:19

How do your config files look like, i.e. do they have this:
NM_CONTROLLED=no
ONBOOT=yes
Also run yum update to get 8.4.

mixmegapol
Posts: 6
Joined: 2015/08/17 04:05:30

Re: bond/bridge can only brought up manually

Post by mixmegapol » 2021/07/16 11:35:46

Hello all

It's a customer system, so I can't update to 8.4.

The config shows the following:


ifcfg-bond0:
--------------
BONDING_OPTS="mode=active-backup miimon=100"
TYPE=Bond
BONDING_MASTER=yes
BOOTPROTO=none
NAME=bond0
#UUID (yes, I didn't define it)
DEVICE=bond0
ONBOOT=yes
#NM_CONTROLLED=yes
BRIDGE=br0

ifcfg-br0:
-----------
DEVICE=br0
TYPE=Bridge
BOOTPROTO=none
NAME=br0
ONBOOT=yes
DELAY=0 # what is delay doing? Can I put DELAY on bond0 as well?
IPADDR=x
PREFIX=24
GATEWAY=x
DNS1=x
DNS2=y


ifcfg-ens1f0np0 (ifcfg-ens1f1np1):
----------------------
TYPE=Ethernet
NAME=ens1f0np0 # ens1f1np1
UUID=fc.. # here I have an UUID
DEVICE=ens1f0np0 # ens1f1np1
ONBOOT=yes
ETHTOOL_OPTS="autoneg off speed 10000 duplex full"
MASTER=bond0
SLAVE=yes
BOOTPROTO=none
IPV6INIT=no
NM_CONTROLLED=yes



nmcli conn show

NAME : UUID : TYPE : DEVICE
br0 : x : bridge : br0
virbr0 : x : bridge : virbr0
bond0 : x : bond : bond0
ens1f0np0 : x : ethernet : ens1f0np0
ens1f1np1 : x : ethernet : ens1f1np1


any hints?

Do I need some nmcli commands?
What meands DELAY parameter in ifcfg-files?

thank you so much
Daniel

User avatar
jlehtone
Posts: 4523
Joined: 2007/12/11 08:17:33
Location: Finland

Re: bond/bridge can only brought up manually

Post by jlehtone » 2021/07/16 12:11:38

mixmegapol wrote:
2021/07/16 09:49:52
NetworkManager is activated; but I created the ifcfg-files manually.
mixmegapol wrote:
2021/07/16 11:35:46
Do I need some nmcli commands?
What meands DELAY parameter in ifcfg-files?
If we write configuration files manually, then we have to ensure that they are logically and syntactically valid.
If we use the tools (like nmcli, nmtui, GUI applet), then we just have to supply the logically correct data and the tool ensures the correctness of syntax.

Red Hat has some examples: https://access.redhat.com/documentation ... networking


Bridge is a switch. Switches send broadcasts out from every port. If you connect two switches with more than one link, i.e. create a loop, you will get broadcast storms. Bridge uses guards against broadcast storms. (There is also Tree Spanning Protocol that switches use to learn topology.)
Red Hat wrote:An extra directive, DELAY=0, is added to prevent the bridge from waiting while it monitors traffic, learns where hosts are located, and builds a table of MAC addresses on which to base its filtering decisions. The default delay of 15 seconds is not needed if no routing loops are possible.



mixmegapol wrote:
2021/07/16 11:35:46
It's a customer system, so I can't update to 8.4.
Your job is to get the network working? A system with known security issues for which fixes do exists is not "working properly".

User avatar
TrevorH
Site Admin
Posts: 33191
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: bond/bridge can only brought up manually

Post by TrevorH » 2021/07/16 12:18:50

It's a customer system, so I can't update to 8.4.
I'd say that makes it doubly your job. The customer doesn't know about securioty updates, you do. You should be encouraging them to put them on in a timely manner.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

mixmegapol
Posts: 6
Joined: 2015/08/17 04:05:30

Re: bond/bridge can only brought up manually

Post by mixmegapol » 2021/07/16 13:18:16

Hi all

Ok, I will discuss that with the customer.
Thank you for the Link to the RedHat-access page.

Does that mean I shouldn't do anything anymore directly in the config file?
Aren't there both possibilities to do it?

If ifcfg-files, then NM_CONTROLLED should be no?

Does somebody know what the DELAY-parameter means? Can I delay the bridge-ifup for some seconds, so the ens-interfaces have time to come up first?

Regards
Daniel

User avatar
jlehtone
Posts: 4523
Joined: 2007/12/11 08:17:33
Location: Finland

Re: bond/bridge can only brought up manually

Post by jlehtone » 2021/07/16 14:11:39

The DELAY is used to set bridge forward delay.

I have Bridge -> VLAN -> Bond -> NIC setups and they come up nice without delays.
Consider also Team as replacement for Bond.
mixmegapol wrote:
2021/07/16 13:18:16
Does that mean I shouldn't do anything anymore directly in the config file?
Aren't there both possibilities to do it?

If ifcfg-files, then NM_CONTROLLED should be no?
When a program writes a file, then there are two possibilities:
A) Program assumes that nobody else modifies the file. Manual edits are undefined behaviour
B) It is still possible to manually edit -- program can reread -- but you have to know the syntax

Since you ask for the meaning of DELAY, you don't know the syntax through and through.


There was a service, network.service, that did configure network interfaces on boot.
The NetworkManager.service configures network interfaces on boot.
Only one service can configure (aka "manage") any given interface. These services are mutually exclusive.

The NM_CONTROLLED=no was a flag for both services that (A) NetworkManager.service is not allowed to manage this interface, and (B) network.service may manage this interface.

The network.service is deprecated. It is not installed. It is still possible to install network.service.

If you add the "NM_CONTROLLED=no", if the NetworkManager still honors that flag, and if the network.service is not installed and enabled, then nothing will use the config files that you have written.

mixmegapol
Posts: 6
Joined: 2015/08/17 04:05:30

Re: bond/bridge can only brought up manually

Post by mixmegapol » 2021/07/16 15:17:36

Hello

Thank you for your explanation.
I will catch up with this topic over the weekend.

I will tell you as soon as it works.

Thank you for your help.
Regards
Daniel

Post Reply