On Tue, Jun 12, 2012 at 08:00:40PM +0000, Andy Smith wrote:
There is no expectation that the problem will return,
but there will
be more information to come as to the actual cause.
More info from Jump:
I'm afraid we had a period of network instability leading to
packet loss last night, starting sometime between 19:19 BST and
19:25 BST, and finishing at 20:34 BST.
The root cause was a faulty pair on an ethernet cable between
sw-tfm4-b and sw-tfm8-a, tdr on the cable from each end shows a
problem towards the sw-tfm8-a end of Pair D:
Interface Speed Local pair Pair length Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi0/46 auto Pair A N/A N/A Normal
Pair B N/A N/A Normal
Pair C N/A N/A Normal
Pair D 11 +/- 2 meters N/A Impedance Mismatched
Interface Speed Local pair Pair length Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi0/3 auto Pair A 96 +/- 4 meters N/A Normal
Pair B 94 +/- 4 meters N/A Normal
Pair C 95 +/- 4 meters N/A Normal
Pair D 81 +/- 4 meters N/A Short
The pair fault wasn't enough to bring the link down, just induce
packet loss, which was sufficient to disrupt normal spanning
tree operation and cause instability as a result of
reconvergence.
Once the link was manually shutdown the network returned to its
normal state.
I'll investigate in the morning potential ways to automatically
error disable links that are suffering from errors like this, as
clearly if the link had failed completely the outcome would have
been a lot better.
Apologies for the delay in fixing this.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting