PowerFlex 3.0: SDC connects to an SDS that was removed from a cluster

one or more SDCs may connect to the removed SDS After removing an SDS from a ScaleIO cluster, because of the way that the SDCs were designed.

Netstat output on the SDS shows established connections from one or more SDCs:
 

tcp 0 0 172.17.8.62:7072 172.17.8.35:49630 ESTABLISHED
tcp 0 0 172.17.8.62:7072 172.17.8.70:41582 ESTABLISHED
tcp 0 0 172.17.8.62:7072 172.17.8.36:37493 ESTABLISHED
...

SDGB output on the SDS will show current connections of the SDCs:

Screen: Net objects
0: # connections:6 # requests:0
NetConnections (6 objects) [ 0 1 2 3 4 5 ]
1: Con Id:0x9e8cf79600000003 Con Type:1
Ip addr :172.17.4.31 172.17.8.33
Owner Type: Ini State:3 #paths:4
...

When an SDC connects to a cluster, the MDM sends a list of SDSs for the SDC to connect to. The SDC creates an internal object with the data that it gets from the MDM. This object exists until the SDC is removed from a cluster or is disconnected. If the user removes an SDS from the cluster, the SDCs can still have its information within the mapping object.

This issue is resolved in version 3.5.

There is no impact and this issue can be safely ignored. This can be verified by checking the SDS trace logs to ensure that there are no MOS_RC__IO_FAULT_NOT_PRI/SEC or similar events after the SDS is removed from the cluster.

Rebooting the SDC host disconnects the SDC and clear the internal object. Once the SDC reconnects, the MDM provides new data and the SDC creates a new internal object of the SDSs that have its data.

Impacted Versions: 2.x, 3.0.x