OVHcloud Network Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
FS#12485 — sw.142.4.216.249
Scheduled Maintenance
Report for Network & Infrastructure
Completed
Some errors occurred on a link of this switch, we cut the faulty interface and we are doing what is necessary to correct this imperfection.
Update(s):
Date: 2015-02-03 17:28:26 UTC
The replacement of FEX109 solved the problem.
It was responsible for many errors on uplinks.
Date: 2015-02-03 13:58:52 UTC
CEST time
2015 Feb 3 13:38:46 sw.142.4.216: FEX-109 Off-line
2015 Feb 3 13:52:46 sw.142.4.216: FEX-109 On-line
At 14:00 CEST, all interfaces were back to their original state.
Date: 2015-02-03 13:58:01 UTC
We've replaced the FEX. Downtime was longer than expected because it's a different model. All servers are now up an reachable on this pair of switches.
So far we've not noticed any errors on the uplinks.
Date: 2015-02-03 12:49:59 UTC
We're going to begin the intervention by replacing the FEX on this pair of N5.
Date: 2015-02-03 12:49:13 UTC
We will change the FEX at 7:30 EST / 13:30 CEST. We hope this will patch the errors.
Date: 2015-01-29 16:11:30 UTC
The change of the uplink has reduced the number of errors, but the has not definitively corrected the issue.
We are planning to change the FEX.
Date: 2015-01-29 16:10:09 UTC
The transfer of the switch port changed nothing, We are moving the uplink of the FEX before planning a FEX replacement.
Date: 2015-01-29 13:31:03 UTC
The errors continue and are worse after the replacement of the optics. We are cutting redundancy on one of the FEX to make verification that only
one FEX is responsible before changing the FEX.
Date: 2015-01-28 17:59:58 UTC
New errors have occurred. We are replacing the optics again.
Date: 2015-01-28 17:54:15 UTC
The interface has been restarted and the optical has been changed, we are monitoring the Rcv-Err on the switch in the uplink.
Date: 2015-01-28 16:35:54 UTC
The source has been found on a FEX uplink. The port remains down until the optics are changed.
Date: 2015-01-28 13:21:56 UTC
We are cutting the link to determine the source of malfunction.
Date: 2015-01-27 17:53:23 UTC
Despite cleaning the optics, the errors persist. We are seeking the origin.
Update(s):
Date: 2015-02-03 17:28:26 UTC
The replacement of FEX109 solved the problem.
It was responsible for many errors on uplinks.
Date: 2015-02-03 13:58:52 UTC
CEST time
2015 Feb 3 13:38:46 sw.142.4.216: FEX-109 Off-line
2015 Feb 3 13:52:46 sw.142.4.216: FEX-109 On-line
At 14:00 CEST, all interfaces were back to their original state.
Date: 2015-02-03 13:58:01 UTC
We've replaced the FEX. Downtime was longer than expected because it's a different model. All servers are now up an reachable on this pair of switches.
So far we've not noticed any errors on the uplinks.
Date: 2015-02-03 12:49:59 UTC
We're going to begin the intervention by replacing the FEX on this pair of N5.
Date: 2015-02-03 12:49:13 UTC
We will change the FEX at 7:30 EST / 13:30 CEST. We hope this will patch the errors.
Date: 2015-01-29 16:11:30 UTC
The change of the uplink has reduced the number of errors, but the has not definitively corrected the issue.
We are planning to change the FEX.
Date: 2015-01-29 16:10:09 UTC
The transfer of the switch port changed nothing, We are moving the uplink of the FEX before planning a FEX replacement.
Date: 2015-01-29 13:31:03 UTC
The errors continue and are worse after the replacement of the optics. We are cutting redundancy on one of the FEX to make verification that only
one FEX is responsible before changing the FEX.
Date: 2015-01-28 17:59:58 UTC
New errors have occurred. We are replacing the optics again.
Date: 2015-01-28 17:54:15 UTC
The interface has been restarted and the optical has been changed, we are monitoring the Rcv-Err on the switch in the uplink.
Date: 2015-01-28 16:35:54 UTC
The source has been found on a FEX uplink. The port remains down until the optics are changed.
Date: 2015-01-28 13:21:56 UTC
We are cutting the link to determine the source of malfunction.
Date: 2015-01-27 17:53:23 UTC
Despite cleaning the optics, the errors persist. We are seeking the origin.