similar to: gigE -> 100Mb problems

On 10/10/2016 5:33 PM, John R Pierce wrote: > I've got a pair of identical CentOS 6.7 servers, with SuperMicro > X8DTE-F motherboards, these have 2 each Intel 82574L ethernet ports. > The eth0 ports are plugged in with 10' runs of brand new cat 5e cable > to a Cisco Nexxus 9000 switch (provided by the data center). > > These servers keep coming up at 100baseT rather

Hi, On Tue, Oct 11, 2016 at 6:03 AM, John R Pierce <pierce at hogranch.com> wrote: > I've got a pair of identical CentOS 6.7 servers, with SuperMicro X8DTE-F > motherboards, these have 2 each Intel 82574L ethernet ports. The eth0 > ports are plugged in with 10' runs of brand new cat 5e cable to a Cisco > Nexxus 9000 switch (provided by the data center). > >

On 10/11/2016 9:03 PM, Ashish Yadav wrote: > Please test that if both the server are communicating with each other at > 1Gbps or not via "iperf" tool. > > If above gives result of 1Gbps then it will eliminate the NICs problem then > you know that it is a problem with cisco switch only. after they forced the cisco ports to gigE, I was seeing 200-400Mbps in iPerf, which

On 10/10/2016 09:31 PM, John R Pierce wrote: > > oh. Yeah, the entire "net-tools" package is deprecated. I tend to forget which of the two (ethtool or mii-tool) is in that set. # Avoid using any of these: $ rpm -ql net-tools

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: [

On 10/10/2016 11:21 PM, Gordon Messmer wrote: > On 10/10/2016 09:31 PM, John R Pierce wrote: >> >> oh. > > Yeah, the entire "net-tools" package is deprecated. I tend to forget > which of the two (ethtool or mii-tool) is in that set. > > # Avoid using any of these: > $ rpm -ql net-tools /bin/dnsdomainname /bin/domainname /bin/hostname /bin/netstat

anyone know how to force network cards talk at gig speeds when all it wants to do is establish a connection at 100mbits root at host1 [/backup/cpbackup/daily]# mii-tool eth0: negotiated 100baseTx-FD, link ok eth1: negotiated 100baseTx-FD flow-control, link ok 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11) Subsystem: Broadcom

Hi! Maybe, I found a bug of xen. My system: - domain0 - gentoo - xen-devel-3.0, kernel 2.6.12.5-r1 - domain1 - debian - kernel 2.6.12.5-r1 (2 interface: vif1.1 = eth0 (0.0.0.0), vif1.2 = eth1 (10.0.1.1 + gw 10.0.1.2)) Bridge: xen-br0 (config as 10.0.1.2) include (vif1.2, vif0.0) xen-br1 (config as 0.0.0.0) include (vif1.1, peth0) On server domain1 I use a pppoe server. If a send a pppoe request

in dom0, how does one get and set the link information for a NIC? In a non-xen kernel, we could get this info by simply running: # ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes:

Hi List, I am running a x86_64 Centos server, after a reboot the network has decided to not work.. this particular machine has 8 eth ports eth0-7. eth0 and eth3 were bonded (mode 1 ) after reboot the bond did not work. It came up OK but no data was passing through it. all other interfaces on the machine were working. I decided to remove the bond, so after removing the bond i was left with eth0

I want to check the speed like features of my Ethernet in dom0 and domUs. But in virtualized environment it gives strange output why is that so? how to check it otherwise? Non-virtualized FC11 [root@fasiha home]# ethtool eth0 Settings for eth0:     Supported ports: [ TP ]     Supported link modes:   10baseT/Half 10baseT/Full                             100baseT/Half 100baseT/Full    

I want to check the speed like features of my Ethernet in dom0 and domUs. But in virtualized environment it gives strange output why is that so? how to check it otherwise? Non-virtualized FC11 [root@fasiha home]# ethtool eth0 Settings for eth0:     Supported ports: [ TP ]     Supported link modes:   10baseT/Half 10baseT/Full                             100baseT/Half 100baseT/Full    

I''m trying to build out a test cloud using XCP 1.0.0 beta with 3 machines of 18 cores total (Phenom II 1090s). I''ve built three machines, installed XCP 1.0.0 beta on them and they all three have the same problem - the Realtek network cards don''t work. The following is the output from lspci 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI

My system is: Intel CC820 motherboard (which supports PME# wake up for wake on LAN) 3com 3C905C which also supports wake on LAN via PME# Linux 5.5 The motherboard BIOS is later than one that reports an issue with WOL and this particular network card was fixed. But when I turn off the PC (shutdown or poweroff commands or front panel button), it cannot be restarted via WOL. The network light on

Hi, I'm having lots of difficulties with BCM5719, which is the default network card of HP Proliant DL 360 G8 servers. I can get a few ping replies before I get a couple of these: bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting Then everything hangs. Can not log in using ssh.

Hi. I got this on today's RELENG_6 with Broadcom BCM5722 A0, ASIC rev. 0xa200. >From dmesg (bge related): bge0: <Broadcom BCM5722 A0, ASIC rev. 0xa200> mem 0xe8400000-0xe840ffff irq 16 at device 0.0 on pci2 bge0: firmware handshake timed out, found 0x4b657654 bge0: firmware handshake timed out, found 0x4b657654 bge0: EEPROM read timed out bge0: failed to read EEPROM device_attach:

I'm experiencing similar problems with a 3C996-T under 4.8-REL. In particular, connecting a 4.8-REL machine to a 5.1-REL machine leads to some interesting situations: I can do simple pings across the link, but ssh fails, and heavy pings crash the 4.8 machine. Similarly changing the interface configuration with ifconfig tends to crash the 4.8 machine (mtu, link0, up/down, etc). The

Hello, Just did a fresh install of xen-4.0 and using the 2.6.31.13 dom0 kernel. I have 6 linux debian guests running, and on my host console i am getting these errors rolling pretty constantly. "Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet" I tried doing the ethtool -K eth0 tx off and same thing on peth0, using bridged mode for network config. Any tips?

Hello, Just did a fresh install of xen-4.0 and using the 2.6.31.13 dom0 kernel. I have 6 linux debian guests running, and on my host console i am getting these errors rolling pretty constantly. "Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet" I tried doing the ethtool -K eth0 tx off and same thing on peth0, using bridged mode for network config. Any tips?

Dear colleagues, experimenting with new amd64-based router we found strange re(4) behaviour when working in autoselect media mode: whenever promisc mode turned on, renegotiating occurs, leading to 3 to 45 (depending on STP settings on the switch) network unavailability. Moreover, some other re(4) setting changes seem to disturb link state unneededly (such as ifconfig re0 -vlanhwtag) The most