- This topic has 1 reply, 1 voice, and was last updated 2 days, 14 hours ago by .
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- You must be logged in to reply to this topic.
Home › Forums › FABRIC Announcements › FABRIC SEAT – Outage on seat-w1
Dear Experimenters,
We are having a hardware problem on the server/host “seat-w1.fabric-testbed.net” . Affected (VM) slivers and slices are as follows:
“sliver_id”: “8d51a0d7-531a-471d-ae1a-547c31bebfb7”,
“sliver_id”: “ff015bf0-288e-4dc5-a156-13cea0b2108b”,
“sliver_id”: “173b392e-fd25-40e6-8fb7-56e95effe900”,
“sliver_id”: “c5c83a46-953f-44b6-9900-1c07083a9b5d”,
“sliver_id”: “42a63c5e-f26a-4f02-9168-c3adcc1f5745”,
“sliver_id”: “84fe1b70-edfe-4352-bc17-95126077a006”,
“sliver_id”: “4574a513-7ae8-4512-9f28-a0462c23f074”,
“sliver_id”: “fee4dd6b-172b-42b0-906d-a9326a246120”,
“sliver_id”: “66581768-847a-45f3-be3b-bf44951c6e75”,
“sliver_id”: “22fca343-d99d-4c8f-859b-964f07f01c60”,
“sliver_id”: “38a6179d-bd08-4c1d-8748-120389cdddd8”,
“sliver_id”: “4c1c4cc8-3482-4a3f-9eb1-8b2f896a62b7”,
“sliver_id”: “09d690ad-a46f-4c9b-a2a9-45069c87fda6”,
“sliver_id”: “6af94a5d-2440-42aa-a77f-be0c14423e63”,
“sliver_id”: “1dae7c20-6a27-429e-bb0d-dcdfb2ddfcdd”,
“sliver_id”: “306af3a3-9d67-4960-994d-d8f77f056db0”,
“sliver_id”: “d82e68ed-e465-4c90-a7d5-24cdfaf33ca6”,“slice_id”: “4e9c77fb-8a29-4317-8808-34db7a7e9a63”, (FatTree-Rack13)
“slice_id”: “7a1efbdd-15f5-4fef-a2bb-b08f823798c0”, (HybridOSPF_BGP_InterAs_Slice_upd1)
“slice_id”: “faa95edf-c500-4931-9c35-c8591bb3c941”, (CEPH-mgr-asia)
“slice_id”: “fc322866-e44d-4873-906d-19649ac56fe3”, (CEPH_DOCA_POC2)
“slice_id”: “fd216550-6a84-4fa0-a1b1-3075e361cccf”, (CEPH-osd-asia)
We will provide updates on this thread.
Problem on the server (seat-w1) was caused by the Nvidia BlueField-3 DPU card. Currently, server is back online (active VM slivers are recovered), however we took out the DPU card for investigation. All other resources on the SEAT node are available for experiments.