RSS for all categories
FS#605 — FS#4652 — var-1-6k/PLIX
Attached to Project— Network
| Incident | |
| Whole Network | |
| CLOSED | |
 |
We have got a problem on the port-channel Amsterdam<>Warsaw and that towards PLIX. Probably, these problems are caused by a hardware problem on the card #3 of our network at Warsaw. We will restart this card.
Date: Thursday, 07 October 2010, 00:14AMReason for closing: Done
The traffic is well balanced again. We will keep an eye on this card.
If the problem starts again, we will change it.
The problem continues. We will reload the card. If this continues,
we will change it.
We have deactivated the card #3 awaiting to receive
the new one. We have diminished the BGP weight of
PLIX and we rerouted the AS via DECIX or AMSIX.
We will proceed to the replacement of the card in about 15min.
The replacement was done. The service is again optimal.
We remark the same problem on the card #3 even after
the card change.
We have cut off the card #3.
We will update the router.
It seems that there are errors in the PLIX on the reception of packets
coming from OVH . We actually don't see any errors.
Well , we're on the good track ...
Port Rx Error Monitor Sun Oct 3
16:32:49 2010
Port Link Rx Rx Rx Rx Rx Rx
Rx
State Crc Over Under Frag Jabber Align
Lost
================================================================================
PLIX-OVH> A 482794159 4953587 0 0 0 0
0
Port Tx Error Monitor Sun Oct 3
16:33:26 2010
Port Link Tx Tx Tx Tx Tx
Tx
State Coll Late coll Deferred Errors Lost
Parity
================================================================================
PLIX-OVH> A 0 0 0 0 0
0
--------------------------------------
The PLIX team has changed the Xenpack on our server.
The problem is not fixed but there is less errors
We are going to remove the second 10G from production
in order to fix the problem.
The fiber was cleaned and the fiber connections were verified. We will reinstate the 2nd port.
We re-pass the PLIX to a normal priority.