me4024 swap controller from another me4024

Lokgen4ik,

Yes you can, but you will need to offline the controller that is to move,  and also make sure the system with the working controller is up and running, then hot insert the donor controller. Now of course we would want them to be updated to latest or at least matching FW, but it is not required

Now on a side note, we do not support changing controllers between protocols like SAS to iSCSI, etc.

Let me know if this helps.

Hey @DELL-Chris H,

Can you confirm if the same is true with the ME5?

The_LostIT_Guy,

I can confirm it is the same for the ME5, the thing I don't know if I got across previously is that the "donor" controller should be reset prior to installing in the new,

Let me know if this helps.

@DELL-Chris H,

Thanks for confirming.

I should have also led with this . . . What I'm most interested in, is if it's possible to keep a "spare" controller on stand-by that has been "synched" at least once with the system.

For example, let's say we have a dual controller system, and we swap that spare with controller B for the purpose of initial provisioning/copying the config. Then we swap the original back and shelf the spare. Assuming we don't make any changes to the system, can that controller be ready to go without resetting it if its needed, either in the current system or in a 2nd system where we also physically move over all the drives from the 1st system? I know you mentioned that a reset of the "donor" should be done, but is that a suggestion or a requirement? :P

Thats a real janky disaster recovery scenario, but its cheaper to try pulling that off vs;

Buying another dual controller ME5 + the required amount of disk space to enable replication.

Currently, even if we matched the amount of storage space we have on a second system, we wouldn't have enough free space to confidently enable replication according to what the documentation recommends. 

Hi,

Your idea of this approach is unique. Perhaps doable but it isn't documented that it would work. Theoretically, it should work but there isn't a guarantee. After thinking back about the structure and technology with used cases, I may suggest having a 'new' blank standy controller, not used on any storage nor has any metadata in it's embedded SD storage. If you have issues with both controller, you can insert the new replacement controller and the metadata stored in the drives can sync with the controller. This would be rather a safer way than to sync upfront. Also, I tried to find instruction on how to reset a controller to new, but there isn't any. 

I may suggest having a 'new' blank standby controller, not used on any storage nor has any metadata in it's embedded SD storage. If you have issues with both controllers, you can insert the new replacement controller and the metadata stored in the drives can sync with the controller.

This aligns with what our manager expected is possible based on his past experiences in the field. However, this seems to be counter to what we've recently been told. We've been hunting for a clear answer, but now we have different statements from separate Dell representatives. See the response below from technical support.

If the chassis was to be replaced, the Controllers would need to be swapped also. The Controllers hold the parity combination that was established when RAID set was created.   Drives without the parity mapping, would show as Leftover, with the only option would be to clear.  There is not an import option with the ME5.

What I understand from this is that the controllers present when the RAID was established contain vital information (the parity combination). Without this information, the drives cannot be mapped properly and will need to be cleared when new controllers are introduced.

Maybe we are not understanding what is actually be said here. Can you clarify?