similar to: anaconda/kickstart: bonding device not created as expected

On 18/04/2017 15:54, Frank Thommen wrote: > Hi, > > I am currently struggling with the right way to configure a bonding > device via kickstart (via PXE). > > I am installing servers which have "eno" network interfaces. Instead of > the expected bonding device with two active slaves (bonding mode is > balance-alb), I get a bonding device with only one active slave

Hi, kickstarting fails due to problems with host resolution, even though the network seems to be properly configured through DHCP. eno1 and eno2 are both attached to the network, but only eno1 gets an IP via DHCP. Still `curl` cannot resolve the mirror host and the kickstart host during dracut-initqueue: rdsosreport.txt ------------------------------------------------ [...] [ 14.780428]

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, some months ago I ran into a hassle with following, quite simple config that works on CentOS 6 and CentOS 5 extremeley well, for years. However, I have problems getting it running on CentOS 7. ,-- bond0.100 -- brbond0.100 -> (VMs) eth0 (eno1 on C7) --. | |--- bond0 ----|--

Dear Simon, > And can you diff the config of eno1 and eno4. # pwd /etc/sysconfig/network-scripts # diff -u ifcfg-eno1 ifcfg-eno4 --- ifcfg-eno1??? 2020-09-21 17:23:25.576672703 +0200 +++ ifcfg-eno4??? 2020-09-22 07:18:43.160532532 +0200 @@ -3,15 +3,20 @@ ?BROWSER_ONLY=no ?BOOTPROTO=none ?DEFROUTE=no -IPV4_FAILURE_FATAL=yes -IPV6INIT=no -IPV6_AUTOCONF=no +IPV4_FAILURE_FATAL=no

Dear Simon, every second IP-address is unwanted. We restarted? eno4: nmcli con down eno4; nmcli con up eno4 and the second address vanishes. Then after a few ours, the second ip address reappears. This is the config-file of eno2: # cat ifcfg-eno2 TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes

Hi all, Someone played with kickstart bonding with centos 6.4 ? CentOS 6.4, as upstream now support ifcae bonding in kickstart network section. I've an issue with configuring a second bonding iface in kicstart on CentOS 6.4. The first bonding (bond0) works as espected but the second is not configured during installation. I've a 6 nic server (two for "puclic" network, two for

On Thu, 16 Jan 2020 15:34:43 +0100, Stephen John Smoogen <smooge at gmail.com> wrote: > On Thu, 16 Jan 2020 at 07:58, Asle Ommundsen <aommundsen at gmail.com> > wrote: >> >> Hi, >> >> Tonight I upgraded two CentOS 8 boxes to CentOS 8.1 (1911). Then after a >> reboot of the first server the network was unavailable. In IPMI console >>

Hello All, I seem to have run into a bug with the new --bridgeslaves=<INTERFACE> option. It would seem that if I tell the bridge device to use a virtual interface (like bond0) rather than a physical interface (em1/em2) that kickstart completely barfs on it. I have provided my network section below which works fine as long as i don't enable all the bridge content. When the

This does not look bad, pretty ok. But im do have a question here. > ipaddress: 10.103.1.6 X.X.103.1 This indicated that the primary interface is eno2 > 2: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP > ??? inet 10.103.1.6/24 brd 10.103.1.255 scope global eno2 > 3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP > ??? inet

This is my system info: Debian Release: 10.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.60-1-pve (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh

Dear CentOS-Community, we are facing the following issue: A secondary ip address seems to be automatically added to a nic which causes several issues in our setup. This server is equipped with four nics which are currently in use: # nmcli con show NAME????? UUID????????????????????????????????? TYPE????? DEVICE eno2????? cb6fcb54-be52-4ab6-8324-88091a0ea1a0? ethernet? eno2 eno4?????

> -----Original Message----- > From: Gordon Messmer > Sent: Monday, August 31, 2015 12:15 PM > > On 08/31/2015 03:51 AM, Jason Pyeron wrote: > > I feel like this is an issue of libvirt starting before networking, > > but I am a fish out of water with systemd. > > Are you using the "network" or "NetworkManager" service to > configure your

Two onboard nics, Intel, eno1 and eno2 If either of them is set to onboot then network won't start. one error message says :bad vendor preset disabled Another error message (in red) says Failed to start LSB If I can find a USB key there is an updated kmod-wl src.rpm that *may* bring up my wifi, but I am not sure I have access to a USB key at the moment. The motherboard is supermicro and

Here is the relevant log snippet: journal: libvirt version: 1.2.8, package: 16.el7_1.3 (CentOS BuildSystem <http://bugs.centos.org>, 2015-05-12-20:12:58, worker1.bsys.centos.org) journal: failed to connect to monitor socket: No such process journal: internal error: process exited while connecting to monitor: ((null):1937): Spice-Warning **: reds.c:3036:reds_init_socket:

Dear list, we use debian stretch with Louis's 4.10.5 packages and bind9_dlz backend. There are two AD DCs with redundant ISC DHCP servers on them. The DHCP servers are updating the DNS along the lines of https://wiki.samba.org/index.php/Configure_DHCP_to_update_DNS_records_with_BIND9 but with nsupdate commands replaced by suitable calls to "samba-tool" (I had problems getting the

This should be easy to answer (I hope).? We routinely kickstart boxes to use for managing our customers RADIUS/DHCP configurations (along with other things).? We've had a C7 kickstart in place since I built one in May and are finally starting to roll it out for new installations.? But, I'm curious as to what ksdevice= actually does. With the C6 we routinely used ksdevice=eth0 since we

Hi, Tonight I upgraded two CentOS 8 boxes to CentOS 8.1 (1911). Then after a reboot of the first server the network was unavailable. In IPMI console everything except the network was looking good. Network was unreachable. No errors in NetworkManager. I also restarted NetworkManager, but it did not help. Then I discovered that the default gateway suddenly was missing. Then I rebooted the

Hi, I'm wondering about the impact of using both dom0 and domU's on a server at the same time. I'm worried about the performance impact of running a Mysql server in a domU and now I'm thinking about moving the Mysql part of a LAMP setup into dom0 and running a few Apache guests as domUs. Since the Apaches will serve mostly from an NFS share they won't have much impact on

Nux! wrote: > Hello, > > ksdevice specifies which NIC to be used during the network install. > > The new naming conventions indeed make this more complicated than it needs > to be. To go back to the old naming scheme (eth0, eth1 ...) just add this > to boot parameters (kernel cmdline): > biosdevname=0 net.ifnames=0 Yes! Actually, the other admin I work with and I were just

someone recommended that i should give br0 the same hardware address as eno2. I did that, and restarted the vm, and it still does not work. Here is my current host interface config: ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft