Symptoms

Unable to remove an SDC which is disconnected. scli --query_all_sdc SDC ID: xxxxxx00000000 Name: N/A IP: x.x.x.111 State: Disconnected GUID: XXXX-XXXX-XXXX-XXXX Read bandwidth: 0 IOPS 0 Bytes per-second Write bandwidth: 0 IOPS 0 Bytes per-second SDC ID: xxxxxx000000001 Name: N/A IP: x.x.x.114 State: Connected GUID: XXXX-XXXX-XXXX-XXXX Read bandwidth: 18 IOPS 24.0 KB (24576 Bytes) per-second Write bandwidth: 13 IOPS 13.0 KB (13312 Bytes) per-second scli --unmap_volume_from_sdc --volume_id <vol_id> --sdc_id YYYYYY Error : MDM failed command. Status: SDC has mapped volume(s)

Cause

Several reasons can cause an SDC Disconnected state. Some of these reasons are: A change in the SDC IP. The new IP would get a new SDC ID, which causes the old SDC IP to go into a Disconnected state.Rejoining of SDC to ScaleIO may change the SDC ID if another network IP gets used.

Resolution

A Disconnected SDC cannot be deleted with volumes mapped.To remove an SDC from the ScaleIO Cluster, you must unmap volumes from the Disconnected SDC and then remove them.1. To find the Disconnected SDC name, ip and id: # scli --query_all_sdc Example output: SDC ID: YYYYYY Name: XXXXXXX IP: XXX.XXX.XXX.XXX State: Disconnected GUID: XX-XX-XX-XX 2. To see which volumes are mapped to the Disconnected SDC: # scli --query_sdc --sdc_id YYYYYY 3. Unmap volumes from the Disconnected SDC: # scli --unmap_volume_from_sdc --volume_id <ID got from Step 2> --sdc_id YYYYYY 4. Remove the Disconnected SDC: # scli --remove_sdc --sdc_id YYYYYY 5. Verify that the SDC has been removed: # scli --query_all_sdc

Support Cases