similar to: Networking just stopped working

Hello, I?m trying to configure a CentOS 7 server to act as a host for a bunch of virtual servers (KVM). I have an 802.3ad bonded Ethernet connected to the server with a bunch of tagged VLANs. I want to be able to build a bridge interface on the server for each VLAN and then attach that to the bond interface and the virtual clients. I also want to attach a host interface to one of the VLANs

I try to get working together vlan and bonding both for dom0 and domU. I lost packets sent to dom0 while domU is OK. Nightly stats for dom0: 52879 packets transmitted, 45293 received, 14% packet loss, time 52879599ms rtt min/avg/max/mdev = 0.144/0.224/717.306/5.129 ms Nightly stats for domU: 52952 packets transmitted, 52952 received, 0% packet loss, time 52952554ms rtt min/avg/max/mdev =

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

I am experiencing strange network behavior from several DomU''s. I can ssh from DomU to any host on the local lan/vlan, I can ping those hosts. However when I go to resolve a hostname DNS fails. I have verified that three other DomU''s are exhibiting the same behavior. I have also verified that Dom0 is functioning properly and can resolve hostnames and access hosts outside of the

Hello everyone I am running into some strange issues when configuring networking interfaces on my physical server running Centos 7.5. Let me give you an overview of what's going on: We have a physical server, running CentOS 7.5. This server has one 4 port NIC and one 2 port NIC and a Dell IDRAC port. The first port of the 4 port NIC, em1, is used for Management traffic. The first port of

I''m attempting to put together a Xen box, which has multiple VLANs running into it, on one bridged interface. I mostly copied the way it was done here: http://renial.net/weblog/2007/02/27/xen-vlan/ I basically have: bond0 is the bond device (composed of eth0 and eth1), vlan757 is the vlan device for vlan 757 on bond0, and "xen757" is a bridge created by the above scripts,

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

I figured I should post this because before I went to do it I searched the web for caveats etc and didn''t really find much. So anyway, I set up bonding + vlan for a project. Computer is dell powerdge 350 with 2 intel 82559 10/100 nic running stock 2.4.20. I tried both the eepro100 and the e100 drivers for the nics, both work 802.1q and bonding are modules. Switch is cisco 2924xl-en

CentOS 6.2......... Why do the physical interfaces report (correctly) that they're negotiated at 1000Mb/s, but when I `cat /proc/net/bonding/bond0` I get 100Mbps for the member interfaces, and when I ` mii-tool bond0` I get 10Mbps for the bond? ----------------------------------------------------------------------------------------- ethtool em1 Settings for em1: Supported ports: [

Hi, We have a Dell server with 4 Ethernet interface. I would to aggregate them in a bond. Everything work but the default gateway doesn?t work on the ? bond0 ? interface and I have no links. My configuration: - CentOS 7: :/etc/sysconfig/network-scripts# uname -a Linux nas-mtd2 3.10.0-957.5.1.el7.x86_64 #1 SMP Fri Feb 1 14:54:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux - NetworkManager disabled:

Hi, I try to get networking running with xen 3.2, but it seems I fail miserably. I am on sles10sp1, with xen 3.2.0, and kernel rpm''s installed from SP2. I configured in /etc/sysconfig/network the NETWORK_LIST: NETWORK_LIST="bridge,0,default,00:DE:AD:BE:EF,192.168.8.13/24,dhcp-off" but an ifconfig xenbr0 still shows the mac address of peth0 fe:ff:ff:ff:ff:ff. Initially, I

Hi, I want to switch my server into a Xen instance. Right now there are 10 vlans ending up at the server. For each service that the server provides, there is an alias IP address on each of the vlan interfaces to serve the clients. I want ot install xen, and divide the services into 4 virtual nodes. The dom0 machine has three network interfaces, eth0, eth1, eth2. eth0 and eth1 are bonded

If you'd like to extend that a little bit, here's example configs on how to do LACP and vlan tagging on c6: host network-scripts # cat ifcfg-eth0 DEVICE=eth0 ONBOOT=yes USEERCTL=no BOOTPROTO=none IPV6INIT=no MTU=1500 MASTER=bond0 SLAVE=yes host network-scripts # cat ifcfg-eth1 DEVICE=eth1 ONBOOT=yes USEERCTL=no BOOTPROTO=none IPV6INIT=no MTU=1500 MASTER=bond0 SLAVE=yes host

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

I think the diagram here: http://wiki.xensource.com/xenwiki/XenNetworking#line-474 should be more like this: http://pastebin.com/cjxbXrJW I''ve asked Stephen for edit rights on the wiki but wanted to ask for confirmation before editing it. Notes: The connections at the top are switch ports bond1 has eth2 and eth3 eth0 maps to bond0.100 and eth1 maps to bond1.200

Hi All I have two bond interfaces namely, bond0 and bond1. bond0 has two ethernet interfaces associated with it and bond1 also has two ethernet interfaces associated with it. Now i create a bridge interface namely br20 (20 being the VLAN) and assign it a IP Address , subnet mask and the default gateway. I will use this IP to reach the server. So it is like a management bridge for me.

On Jul 28, 2011, at 1:38 PM, Rose, Gregory V wrote: > >> From: Anirban Chakraborty [mailto:anirban.chakraborty at qlogic.com] >> Sent: Thursday, July 28, 2011 12:04 PM >> To: Rose, Gregory V >> Cc: David Miller; netdev; Ben Hutchings; Kirsher, Jeffrey T >> Subject: Re: [RFC net-next PATCH 3/4] ethtool: Add new set commands >> >> >> On Jul 28,

On Jul 28, 2011, at 1:38 PM, Rose, Gregory V wrote: > >> From: Anirban Chakraborty [mailto:anirban.chakraborty at qlogic.com] >> Sent: Thursday, July 28, 2011 12:04 PM >> To: Rose, Gregory V >> Cc: David Miller; netdev; Ben Hutchings; Kirsher, Jeffrey T >> Subject: Re: [RFC net-next PATCH 3/4] ethtool: Add new set commands >> >> >> On Jul 28,

You are very welcome. One thing that I am working on now involves removing the step toward the beginning: xe pif-reconfigure-ip uuid=<UUID of the bond created above> mode=static gateway=<GATEWAY> IP=<IP ADDRESS> netmask=<NETMASK> DNS=<DNS SERVER ADDRESS> I do not believe that this step is necessary since we will not use the pif directly. We will use