"Failed to create snapshots of replica devices. Failed to present device to ESX host"

Products

• VMware Site Recovery Manager 8.x

Issue/Introduction

Symptoms:

"During the recovery process using SRM, an error occurs with the message: 'Failed to create snapshots of replica devices. Failed to present device to ESX host. Ensure that the ESX host specified in the request has the correct configuration and is properly set up on the controller.'"

vmware-dr.log

--> sraPollOnTask COMPLETED with an error
--> 2024-10-16 07:47:25 Logging In TestFailoverStartCommand
--> 2024-10-16 07:47:25 NetApp Storage Replication Adapter for ONTAP
--> 2024-10-16 07:47:35 Discovered a recovery site
--> 2024-10-16 07:47:35 System Model: AFF-A300
--> 2024-10-16 07:47:35 Vendor Name: NETAPP
--> 2024-10-16 07:47:35 Controller Version: 76406
--> 2024-10-16 07:47:35 Replication Software: snapmirror
--> 2024-10-16 07:47:35 Storage Object Type: C-mode
--> 2024-10-16 07:47:35 Cluster Admin or SVM Admin Hostname: 10.69.XX.XX
--> 2024-10-16 07:47:35 SVM: drsansvm01
--> 2024-10-16 07:48:44 Unable to online/map LUN. Failed with exception Caused by: AbstractController: id: 823e6dc9-69db-11e6-b7e2-00a098a21a67name: drsansXXXip address: 10.6.XX.XX failed to add initiator 14:96:70:79:XX:XX:XX:XX to the igroup testfailover_igroup_domain-c37127, specifically com.netapp.offtap3.ontap.ApiFailedException: Invalid initiator "14:96:70:79:XX:XX:XX:XX". An example of a valid WWN is "01:02:03:04:0a:XX:XX:XX". Examples of valid iSCSI names are "iqn.1995-08.com.xx:string" and "eui.01234XXXXXXXX". (errno=13001)
--> 2024-10-16 07:48:44 Failed to present SAN device to ESX host; no matching

This issue occurs because incorrect WWN information is passed by SRM to the SRA, which causes the VM failover task to time out.

Environment

Site Recovery Manager 8.x, 9.x

Cause

 SRM incorrectly inserts a colon after every two characters in the string '01:49:67:07:95:XX:XX:XX'. This issue occurs because the data structure used to store the portWorldWideName is a long integer instead of a string, causing SRM to ignore the leading zero in the WWN.

Resolution

"There is currently no workaround for this issue. A fix will be provided in future SRM releases."