Winit
03-04-2009, 19:16

Your ticket has been assigned with an incident number #234.
Network Connection 100M/s - 1 G/s switch problems one
summons EG servers - inquest in progress
We will inform you shortly regarding the resolution of the
incident.
You said you will inform me shortly, another 4 days has
passed by
Hi,
do you know that 1 G/s between is only foor OVH Server to
OVH Server and that this option is not guaranteed.
So you are attached on this
Network Connection 100M/s - 1 G/s switch problems one
summons EG servers - inquest in progress
And you will receive an message when we found an solution
for this.
Best regards,
Angie
Please let this ticket on your side and wait that the
system will update this.
If you need talk about this problem you can contact
customer support in ovh.co.uk.
Best regards,
Angie
Hi,
no you will not be compensated for this because the fact to
not have 1 G /s between your OVH Server and another OVH
Server made no loss in the usage of your server.
Your server is UP and the SLA for this server is only
provided for the connection to internet:
OVH to Internet 100 Mbps
SLA Premium
( on all infrastructure )
and you have 100M/s to internet.
OVH to OVH 1 Gbps <= this one have no SLA and this
will not influence the usage of your server.
So as sayd in the bugtracker: we research why you not can
do 1 G/s between ovh and ovh server.
Now you have closed SSH and we can no more longer do tests
to solve this.
Best regards,
Angie
But you have only 1 G/s between OVH and OVH.
Between Internet & your server: you have 1 G/s ( if the
server who was external on ovh can made 1 G )
Only in SLA is: your server to internet : 100 M/bs and this
will work.
The other problem: as say a lot of times now -> you're
attached on
incident number #234.
and research is in progress.
Best regards,
Angie
As your 1G /s OVH -> OVH has no SLA -> has no delay to
been solved.
Best regards,
Angie
when it have works before, it will works now.
We have not changed you switch, we have not made
deplacement of server or other manipulation on your network
connexion.
So when you need that I check and find out an problem or an
solution:
I need an file on your server that I can get to another
server
when it have works before, it will works now.
We have not changed you switch, we have not made
deplacement of server or other manipulation on your network
connexion.
So when you need that I check and find out an problem or an
solution:
I need an file on your server that I can get to another
server
It is connected at 100MB/s which means the max throughput
it can ever get is 100MB/s.
When the machine was first provided it was connecting at
gigabit but it was on and off, the syslog log files show it
going from 1000MB/s to 100MB/s.
It finally stabilized at 100MB/s.
This could be switch/port error/config.
Cable problems/kinks/wrong cable type.
Adapter Hardware Failing
Something to do with your compiled Kernels.
Below are some details
Note: When trying to force to 1000MB/s with ethtool the
link fails to estabilish and must be hard restarted to
resume connections.
-----------------------------------------------------------
-----------------------------------------
List (Network) Hardware
-----------------------------------------------------------
-----------------------------------------
ns206304:~# lshw -C network
*-network
description: Ethernet interface
product: 82566DC Gigabit Network Connection
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eth0
version: 02
serial: 00:1c:c0:a7:68:04
size: 100MB/s
capacity: 1GB/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet
physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd
autonegotiation
configuration: autonegotiation=on broadcast=yes
driver=e1000e driverversion=0.3.3.3-k6 duplex=full
firmware=1.1-0 ip=94.23.45.198 latency=0 link=yes
multicast=yes port=twisted pair speed=100MB/s
*-network DISABLED
description: Ethernet interface
physical id: 3
logical name: dummy0
serial: c2:fd:51:ac:fe:2b
capabilities: ethernet physical
configuration: broadcast=yes
-----------------------------------------------------------
-----------------------------------------
ethtool - Display or change ethernet card settings
Note: When trying to force to 1000MB/s with ethtool or
mii-tool the link fails to estabilish and must be hard
restarted to resume connections.
Note: Mii-tool is not compatible with this adapter and
configuration reports invalid data and bad io.
-----------------------------------------------------------
-----------------------------------------
ns206304:~# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbag
Wake-on: g
Current message level: 0x00000001 (1)
Link detected: yes
-----------------------------------------------------------
-----------------------------------------
System log looking for link speeds over all recorded logs
(logs gunzipped)
Note: Look used to be gigabit and started flip flopping the
first 2 days of having it.
Since then it has been 100Mbps
-----------------------------------------------------------
-----------------------------------------
ns206304:~# grep "Link is Up" syslog*
syslog.6: Mar 12 00:43:40 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 1000 Mbps Full Duplex Flow Control: None
syslog.5: Mar 12 02:02:04 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 1000 Mbps Full Duplex Flow Control: None
syslog.5: Mar 12 02:50:59 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 1000 Mbps Full Duplex Flow Control: None
syslog.5: Mar 12 03:58:33 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 1000 Mbps Full Duplex Flow Control: None
syslog.5: Mar 12 04:14:46 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 100 Mbps Full Duplex Flow Control: None
syslog.5: Mar 12 04:52:30 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 100 Mbps Full Duplex Flow Control: None
syslog.5: Mar 13 05:15:47 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 100 Mbps Full Duplex Flow Control: None
syslog.4: Mar 13 23:07:51 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 1000 Mbps Full Duplex Flow Control: None
syslog.4: Mar 13 23:08:00 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 100 Mbps Full Duplex Flow Control: None
syslog.4: Mar 13 23:08:45 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 1000 Mbps Full Duplex Flow Control: None
syslog.4: Mar 13 23:08:48 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 1000 Mbps Full Duplex Flow Control: None
syslog.4: Mar 13 23:08:58 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 100 Mbps Full Duplex Flow Control: None
syslog.4: Mar 13 23:10:10 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 1000 Mbps Full Duplex Flow Control: None
syslog.4: Mar 13 23:10:29 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 1000 Mbps Full Duplex Flow Control: None
syslog.4: Mar 13 23:10:45 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 1000 Mbps Full Duplex Flow Control: None
syslog.4: Mar 13 23:10:49 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 1000 Mbps Full Duplex Flow Control: None
syslog.4: Mar 13 23:32:22 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 100 Mbps Full Duplex Flow Control: None
syslog.2: Mar 15 22:43:12 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 100 Mbps Full Duplex Flow Control: None
syslog.2: Mar 16 04:05:52 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 100 Mbps Full Duplex Flow Control: None
syslog.1: Mar 16 21:06:03 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 100 Mbps Full Duplex Flow Control: None
syslog.1: Mar 16 22:53:15 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 100 Mbps Full Duplex Flow Control: None
syslog.1: Mar 17 00:57:17 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 100 Mbps Full Duplex Flow Control: None
syslog.1: Mar 17 02:09:24 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 100 Mbps Full Duplex Flow Control: None
syslog: Mar 18 20:46:58 ns206304 kernel: 0000:00:19.0:
eth0: Link is Up 100 Mbps Full Duplex Flow Control: None
-----------------------------------------------------------
-----------------------------------------
Speed test from your server using wget (Average 10.89 MB/s)
Note: download speed tests were performed after disabling
anything that would be using bandwidth
-----------------------------------------------------------
-----------------------------------------
ns206304:~# wget ftp://ns201352.ovh.net/test.bin
--19:59:47-- ftp://ns201352.ovh.net/test.bin
=> `test.bin.2'
Resolving ns201352.ovh.net... 91.121.118.183
Connecting to ns201352.ovh.net|91.121.118.183|:21...
connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD not needed.
==> PASV ... done. ==> RETR test.bin ... done.
Length: 104,857,600 (100M) (unauthoritative)
100%[====================================>] 104,857,600
11.21M/s ETA 00:00
19:59:56 (10.89 MB/s) - `test.bin.2' saved [104857600]
-----------------------------------------------------------
-----------------------------------------
Speed test from your server using latest compiled aria2c
and patches 32 segments(Average 7.7 MB/s)
Note: download speed tests were performed after disabling
anything that would be using bandwidth
-----------------------------------------------------------
-----------------------------------------
ns206304:~# aria2c -s32 ftp://ns201352.ovh.net/test.bin
2009-03-19 20:00:18.015089 NOTICE - File already exists.
Renamed to ./test.bin.3.
[#1 SIZE:96.8MiB/100.0MiB(96%) CN:8 SPD:6426.65KiB/s]
2009-03-19 20:00:33.842787 NOTICE - Download complete:
./test.bin.3
Download Results:
gid|stat|avg speed |path/URI
===+====+===========+============================= =========
====================
1| OK| 7.7MiB/s|./test.bin.3
Status Legend:
(OK):download completed.