ViPR & SRDF Limitations

I guess the below mentioned doc will talk about ViPR limitations:

System Error

Page no 8

There are a number of limitations using SRDF protected volumes with ViPR regardless of version (i.e. ViPR 1.1: first release supporting SRDF, and upcoming ViPR 2.0).

These limitations include:

Ingestion of  SRDF Asynchronous (SRDF/A) volumes

1. SRDF/A volumes created by a user manually cannot be brought under ViPR management
2. ViPR does ingest SRDF/S volumes, however
3. Currently there is no plan to change this in the near future

SRDF is a complex business continuance solution with numerous complex operations associated with it.  ViPR does
not support every operation; this fact does not mean that users are prevented from invoking these operations manually via Unisphere or CLI, however.  ViPR supports co-existence in SRDF. For example, if an SRDF split is done outside of ViPR, ViPR will detect this and update its database.

Other SRDF features not supported by ViPR include:

1. Split
2. Restore
3. Sync
4. ReSync
5. Swap one half
6. Explicitly flushing data from source to target

The reason these features are not supported is the underlying SMI-S Provider, which is used by ViPR to communicate with the VMAXarrays, does not support these functions. Additionally, ViPR is not intended to replace element managers like Unisphere but rather to augment and centralize common provisioning tasks and the presentation of storage to users.

EMC customers can refer to the EMC Solutions Enabler Symmetrix Array Controls CLI 7.6 Product Guide
if they need to run these SRDF functions’ manually.