Symptoms

Silver/Gold Service Plan for Unity fails with the following error:The Service Plan Events show: Application mapping,ecfd6c39-8fe9-486c-9644-ecd784037058,UNITY_000075,xxxxxx,One or more source luns do not have a remote target specified/mapped The AppSync Server log shows: 10-23-2022 10:50:19.968 ERROR [Thread-301 (ActiveMQ-client-global-threads)] [com.emc.archway.commands.serviceplan.affinity.VNXAffinityModuleCommandBean] [xxxxxxxxxxx] [] 9f1e28e9-d76e-4e3f-9752-4335b1970e08->>> Failed to find any remote devices for the supplied source luns. Remote replication cannot proceed. 10-23-2022 10:50:19.969 INFO [Thread-301 (ActiveMQ-client-global-threads)] [com.emc.archway.service.eventservice.EventServiceBean] [xxxxxxxxxxx] [] 9f1e28e9-d76e-4e3f-9752-4335b1970e08->>> EVENT [UNITY_000075]: One or more source luns do not have a remote target specified/mapped.(METADATA: TYPE-ERROR, TIME-2022-10-23 10:50:19.969+0900NATIVETIME-2022-10-23 10:50:19.969+0900, HOST-win2019-117, PHASE-Application mapping, THREAD=Thread-301 (ActiveMQ-client-global-threads), USER-admin, CATEGORY-GENERIC, SESSIONID-) 10-23-2022 10:50:19.969 ERROR [Thread-301 (ActiveMQ-client-global-threads)] [com.emc.archway.commands.serviceplan.workflow.WorkflowDeployPhaseCommandBean] [xxxxxxxxxxx] [] 9f1e28e9-d76e-4e3f-9752-4335b1970e08->>> service call deployPhase threw an exception 10-23-2022 10:50:19.969 ERROR [Thread-301 (ActiveMQ-client-global-threads)] [com.emc.archway.commands.serviceplan.workflow.WorkflowDeployPhaseCommandBean] [xxxxxxxxxxx] [] 9f1e28e9-d76e-4e3f-9752-4335b1970e08->>> Exception Occurred: VNXeOperationFailedException, Message: One or more source luns do not have a remote target specified/mapped. 10-23-2022 10:50:19.969 ERROR [Thread-301 (ActiveMQ-client-global-threads)] [com.emc.archway.commands.serviceplan.workflow.WorkflowDeployPhaseCommandBean] [xxxxxxxxxxx] [] 9f1e28e9-d76e-4e3f-9752-4335b1970e08->>> +++The following stack trace is abbreviated.+++

Cause

Software bug in AppSync 4.6.0.1, 4.6.0.0, 4.5.0.0, 4.4.1.0, 4.4.0.0. This issue may occur if Unity bi-directional replication is configured.Bi-directional Two-system topology in which each system acts as a replication destination for the peer’s production data. The systems may exist in both local and remote locations. When this replication topology is used, production I/O from each system is mirrored to the peer system. If there is an outage, one of the systems can be promoted as the primary production system, and all production I/O can be sent to it. Once the outage is complete, the replication configuration can be changed back to its original configuration. This replication topology ensures that both systems are in use by production I/O always. At Application mapping phase, AppSync calls the REST request to the Local Unity and filters the replication sessions by using the "source resource ID" of the local LUN to find the same for the target LUN. However, as the same source resource ID is also used on the remote Unity, there are two replication sessions which have the same source resource ID. Eventually AppSync fetches the incorrect source resource ID of the target LUN. The source array is also a target for different set of LUNs. In this case, AppSync must check for the "source system ID"along with "source resource ID" but the source system ID is not there in the REST output.

Resolution

A hotfix for AppSync 4.4.1.0 and 4.6.0.1 exists to address this issue. Call in support quoting this KB article to obtain the hotfix.For versions post AppSync 4.6.0.1, refer to the release notes to determine if the fix is included.

Support Cases