OVHcloud Bare Metal Cloud Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
FS#9326 — 5.39.74.0/24
Incident Report for Bare Metal Cloud
Resolved
We have an issue on a FEX of this network.

We're investigating.

Update(s):

Date: 2013-09-12 12:52:10 UTC
The infrastructure is now stable.

Date: 2013-09-12 12:51:57 UTC
Done.

The FEX is back up on the n5s.

Date: 2013-09-12 12:39:59 UTC
We're reloading the 2 n5s, one after the other.

Date: 2013-09-12 12:38:29 UTC
The problem will be internal at n5.

2013 Sep 12 12:18:55 sw %ETHPORT-5-IF_SEQ_ERROR: Error (\"sequence timeout\") communicating with MTS_SAP_IPQOS_MGR for opcode MTS_OPC_ETHPM_BUNDLE_MEMBER_BRINGUP (RID_PORT: Ethernet
1/3) - Ethpm didn't receive a Link UP from the driver on time or had an internal error, check Port Client and Ethpm logs and d
2013 Sep 12 12:19:36 sw %ACLMGR-3-ACLMGR_VERIFY_FAIL: Verify failed: Operation timed out
2013 Sep 12 12:20:01 sw %IM-3-IM_SEQ_ERROR: Error (sequence timeout) while communicating with component opcode:N/A (for:RID_MODULE: 33)
2013 Sep 12 12:20:01 sw %IM-3-IM_RESP_ERROR: Component MTS_SAP_VMM opcode:MTS_OPC_NULL in vdc:1 returned error:sequence timeout
2013 Sep 12 12:20:01 sw %IM-3-IM_SEQ_ERROR: Error (sequence timeout) while communicating with component opcode:N/A (for:RID_MODULE: 33)
2013 Sep 12 12:22:48 sw %VMM-2-VMM_TIMEOUT: VDC1: Service SAP 175 for slot 33 timed out in removal sequence

Date: 2013-09-12 12:37:58 UTC
We're changing the defective FEX.
Posted Sep 12, 2013 - 12:37 UTC