[SOLVED] Trying to change eth0 speed to 1000mbps but failing

Vernicronz · 12-28-2017, 02:03 AM

Hi ,
I am trying to change my network speed on my centos 6.4 box , but unable to change. I have tried the following , but to no avail. Appreciate some advice. Thank you.

before changing

Code:

[root@mx/]# ethtool eth0
Settings for eth0:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: Symmetric
	Supports auto-negotiation: Yes
	Advertised link modes:  1000baseT/Full 
	Advertised pause frame use: Symmetric
	Advertised auto-negotiation: Yes
	Speed: 100Mb/s
	Duplex: Full
	Port: Twisted Pair
	PHYAD: 1
	Transceiver: internal
	Auto-negotiation: on
	MDI-X: Unknown
	Supports Wake-on: pumbg
	Wake-on: g
	Current message level: 0x00000007 (7)
			       drv probe link
	Link detected: yes

After changing - lost network connectivity ( this was done inside ILO )

Code:

[root@mx/]# ethtool -s eth0 speed 1000 duplex full autoneg on
[root@mx/]# 
[root@mx/]# ethtool eth0
Settings for eth0:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: Symmetric
	Supports auto-negotiation: Yes
	Advertised link modes:  1000baseT/Full 
	Advertised pause frame use: Symmetric
	Advertised auto-negotiation: Yes
	Speed: Unknown!
	Duplex: Unknown! (255)
	Port: Twisted Pair
	PHYAD: 1
	Transceiver: internal
	Auto-negotiation: on
	MDI-X: Unknown
	Supports Wake-on: pumbg
	Wake-on: g
	Current message level: 0x00000007 (7)
			       drv probe link
	Link detected: no

to revert back , i had to restart the network . not sure what is wrong. 1st time seing this kind of issue

ferrari · 12-28-2017, 02:24 AM

Is your cabling and connected device (router?) interface capable of supporting this speed? Normally auto-negotiation should achieve the same if the connected interfaces are capable.

Vernicronz · 12-28-2017, 02:31 AM

hi ferrari ,

the server is connected to a Pro Curve switch , other servers are in the segment are having no issue. Not sure why just this server is having this issue.

ferrari · 12-28-2017, 02:52 AM

You'll need to check the switch port configuration.

Vernicronz · 12-28-2017, 03:10 AM

Hi ferrari ,

i am getting this from the nic info, this could mean the cable is not supporting the 1000mbps rite.

Code:

[root@mx/]# lshw -C network
  *-network:0             
       description: Ethernet interface
       product: I350 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: eth0
       version: 01
       serial: fc:15:b4:10:a6:84
       size: 100Mbit/s
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=4.0.1-k duplex=full firmware=1.59, 0x08d28000, 1.349.0 ip=10.0.0.119 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
       resources: irq:16 memory:fbc00000-fbcfffff ioport:5000(size=32) memory:fbbf0000-fbbf3fff memory:be100000-be17ffff(prefetchable) memory:be300000-be31ffff(prefetchable) memory:be320000-be33ffff(prefetchable)

ferrari · 12-28-2017, 03:43 AM

The cable or switch port configuration are both possibilities. Do you have an ethernet cable tester available for checking the cable parameters?

Vernicronz · 12-28-2017, 03:57 AM

Hi ferrari ,
I am away from the DC atm , will be only be able to go DC tomorrow and have the cable replaced and check again the speed
. Will update again here tomorrow. Thanks again so much...

jefro · 12-28-2017, 03:36 PM

I agree on the cable. Even so called tested ones can do this.

However every once in a while you have to fully power down systems. For some reason the nic can get locked into the auto or select one speed and refuse to change. Both server and router may need to do this and keep cable off till you manually select speeds. Remove the auto negot.

Vernicronz · 12-28-2017, 11:49 PM

hi ferrari & jefro ,

turns out to be the cable the actual culprit , did the cable change and verified the speed ..set to 1000mbps and working fine. thanks so much.
I never reboot the server , works fine with 1207 days uptime

. Happy New Year 2018 !! Thanks so much.

Code:

[root@mx / ~]# lshw -C network
  *-network:0             
       description: Ethernet interface
       product: I350 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: eth0
       version: 01
       serial: fc:15:b4:10:a6:84
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=4.0.1-k duplex=full firmware=1.59, 0x08d28000, 1.349.0 ip=10.0.0.119 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:16 memory:fbc00000-fbcfffff ioport:5000(size=32) memory:fbbf0000-fbbf3fff memory:be100000-be17ffff(prefetchable) memory:be300000-be31ffff(prefetchable) memory:be320000-be33ffff(p


[root@mx/ ~]# ethtool -s eth0 speed 1000 duplex full autoneg off
[root@mx/ ~]# ethtool eth0
Settings for eth0:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: Symmetric
	Supports auto-negotiation: Yes
	Advertised link modes:  1000baseT/Full 
	Advertised pause frame use: Symmetric
	Advertised auto-negotiation: Yes
	Speed: 1000Mb/s
	Duplex: Full
	Port: Twisted Pair
	PHYAD: 1
	Transceiver: internal
	Auto-negotiation: on
	MDI-X: Unknown
	Supports Wake-on: pumbg
	Wake-on: g
	Current message level: 0x00000007 (7)
			       drv probe link
	Link detected: yes

ferrari · 12-29-2017, 12:00 AM

Glad to read of your success with this!

jefro · 12-29-2017, 04:48 PM

Next time remove the cable for a minute or two and try. See if cable or jabber is cause.

Thanks for the update.