similar to: NIC bonding - missing eth0?

I have nic bonding (mode=802.3ad) setup on 2 servers, both running Centos 5.5 In the "Active Aggregator Info", on one reports 4 ports - which is correct - but the other only reports 3 ports. It's always eth0 that shows a different aggregator ID. Changing the cables around so it hits a different port on the switch makes no difference. The switch is correctly configured for the port

I am using the linux bonding, and on my new Centos-4 box I noticed that the ifconfig is slightly different. Now the slave interfaces report that they have an ip address, but the same config files in CentOS 3.5 showed that the slave interfaces were up, but not assigned an interface. Boinding is working, but I am just puzzled to see the address assigned i.e [root at proj proj]# ifconfig bond0

Hi all, I just noticed that my two nics that are bonded via mode 0 are showing the same mac addy in ifconfig. Is this normal? In syslog I keep getting; kernel: pbond0: received packet with own address as source address Some guidance is appreciated before I dive in and troubleshoot. If I don't list the mac addy in my ifcfg-th# files, only one of the 2 nic comes up during boot.

Guys, good afternoon I'm using in my bond interfaces as active backup, in theory, should assume an interface (or work) only when another interface is down. But I'm just lost packets on the interface that is not being used and is generating packet loss on bond. What can that be? Follow my settings bond [root at xxxxx ~]# ifconfig bond0 ; ifconfig eth0 ; ifconfig eth1 bond0

I am using ttylinux-xen file system image a a loopback device for the domain. I am mostly using the default configuration. I am not able to get networking on the domU. Are kernel "vmlinuz-2.6-xenU" as well as "2.6.11.12-xen0" both compiled w/o loadable module support? I guess it fails when it tries to initialize the iptables on the domU when it tries to do "modprobe".

Hi All, We have a single Centos 5.11 server running a xen hypervisor that went down hard after an extended power outage this weekend. I'm mostly familiar for KVM as that is the majority of what our guests run under and have tried getting up to speed on xen bridging to no avail. The problem is that after the xen server spun back up, the previously defined xen bridges were lost. I've

I''ve setup Xen 3.0.2-2 (binary install) on Ubuntu 6.06, got my domUs up and running, got them connected to the Internet but I can''t even ping to any of these VMs. Now I''m not linux/xen genious but could the problem be that xen-br0 doesn''t have an IPv4 address? (it''s got an IPv6 address) Since I don''t use IPv6 on my network this seems a

Well where do I start...I have a domU (ubuntu) booting and appears well but I don''t have an eth0 listed at all, dom) looks good. DomU: eth0 Link encap:Ethernet HWaddr 00:06:5B:15:C5:0B inet addr:10.99.99.5 Bcast:10.99.99.7 Mask:255.255.255.248 inet6 addr: fe80::206:5bff:fe15:c50b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

greetings, following are command line problems as user using virtual terminals. ]$ ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1419 errors:0 dropped:0

Hello, Please CC replies I'm not subscribed. Performance with samba and only samba degrades terribly when we use the bonding driver to aggregate two ethernet cards. Instead of a steady file copy it seems to go in spurts. If I pull out one of the network cables (doesn't matter which) performance resumes to full speed. I can pull the cable in the middle of a transfer and it will go

CentOS 5.5 Xen "standard" Xen Installation. I have two nics. I just put the second one to DHCP and modified the ifcfg-et01 and so far I am holding, but I am not confident. Prior they were sequential IP Addrs on same subnet. arpwatch has indicated flip flips. I can find no rhyme or reason to predict them. I know I missed I must have missed a step somewhere. I want to keep the

Has anyone ran into this issue before? 2 physical nics: eth0 hooked up to 10.175.8.0/21 eth1 hooked up to 10.150.8.0/24 Ifconfig -a looks like this: [root@mgixen1 ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:19:B9:F2:1B:C3 inet addr:10.175.8.158 Bcast:10.175.15.255 Mask:255.255.248.0 inet6 addr: fe80::219:b9ff:fef2:1bc3/64 Scope:Link UP

XenServer build date: 2010-11-30 XenServer build number: 39265p XenServer version: 5.6 Feature Pack 1 Guest OS: CentOS 5.6 Guest Kernel: 2.6.18-238.9.1.el5xen Hi everyone, we have set up several Xen servers with the version mentioned above. The version is the same on all servers, the kernel is the default one, not patches or self compiled versions. Each Xen server has 6 network interfaces (eth0

I have a server running Centos 5.2 as a Xen host. A problem that's shown up recently is that at boot, the dom0 interface eth0 doesn't come up properly, with the result that the host is only accessible via remote console. If I execute 'service network restart', eth0 comes up normally, with an IP address and the correct routing. Three guests have been created via virt-manager

Hi I'm very new with Xen (/Debian) I have 2 VMs running Windows: "Arch" and "Sql" -- static IPs VM Arch: is ok, accessible thru VNC, Remote Desktop, see the network, etc VM Sql : - just accessible thru VNC             - once I log in, I don't see the network             - pings don't reach peer             - appear 4 network ports on Windows the server has 4

Hi all, Has anyone seen this before? I''m running a CentOS 5.3 with xen 3.0 and the server has been running fine for a long time. In fact, it was up for 186 days before I had to reboot after the "network died", and I couldn''t fix it. The server has multiple domU''s on it, which all still works when the host node (dom0)''s network dies with these

Hi, we''re running 4 xen servers on our network with multiple network cards. During HighLoad we experince degeneration of inbound network traffic through our loadbalancer. I might found a reason for it, in Dom0 dmesg output looks as follows: [1157421.975910] eth0: received packet with own address as source address [1157421.975957] eth0: received packet with own address as source

Hello, A bit of history ================ 1) I''ve got a normal 2.6.20 x64 Fedora 6 Linux server running several things 2) I''ve downloaded and installed the XenSource Administrator Console for Windows 3) I''ve added 2.6.20-1.2962.fc6xen kernel, xen and vnc packages on my Linux server 4) I rebooted the Linux server, and started xend as per user guide Configuration

Dear Xen-Users, I use Xen 3.1.0_15042 on my OpenSuSE-10.3-computer. Without starting the xen-kernel I can connect my second computer via my native computer to the internet. After starting the xen-kernel the xen-bridge came automatically up. How can I configure the xen-bridge or the xen-devices? I get routing problems: Feb 20 18:31:36 intel6550 kernel: martian source 217.237.149.142 from

Hi all, Our intranet's WAN interface just stopped working yesterday, and I can't figure it out. The machine has a Gigabyte motherboard, with on-board RTL-8110SC/8169SC Gigabit Ethernet and D-Link PCI NIC for the LAN side. I can get into the LAN side without an issue, but can't see the WAN side at all. [root at intranet ~]# ifconfig eth0 up eth0: unknown interface: No such device