SRM5/SRA Command 'discoverArrays' didn't return a response.

[micx]

Hello,

We are having an issue with VMware SRM 5 deployment and hopefully the community can shed some light for us.  We installed SRM5/NetApp SRA 2.0 on both of the vCenter 5 servers in our protected & DR sites and added the two array managers (two FAS3240s) in the protected site with no issues; however, when trying to add the array managers (FAS3210/single enclosure HA) in the DR site, we kept getting the error in the subject line for one of the filers (interestingly the other array manager was added successfully).  Saw a similar issue on this thread (http://communities.vmware.com/thread/335304) but our error code was a bit different, not sure if this is a SRA issue or something else.

The SRM5 servers in both protected & DR sites run on Windows Server 2008 R2 Standard with firewall turned off.

Unfortunately we are stuck with the SRM5 deployment until this issue is resolved.  Do you have any suggestions?  Anyway, I opened a ticket with NetApp Support on this but I'm still waiting to hear back.  Thanks for your time.

Michael

2012-02-20T12:05:57.399-08:00 [06624 verbose 'Storage' opID=3E37610A-0000005B] Executing array discovery for new array manager 'SacCorp1'

2012-02-20T12:05:57.399-08:00 [06624 info 'DrTask' opID=3E37610A-0000005B] Starting task 'dr.storage.StorageManager.createArrayManager8'

2012-02-20T12:05:57.399-08:00 [06632 verbose 'DrTask' opID=3E37610A-0000005B] Starting VC task 'com.vmware.vcDr.dr.storage.StorageManager.createArrayManager'

2012-02-20T12:05:57.399-08:00 [06616 info 'SraCommand' opID=3E37610A-0000005B] Command line for discoverArrays: "C:\Program Files (x86)\VMware\VMware vCenter Site Recovery Manager\external\perl-5.8.8\bin\perl.exe" "C:/Program Files (x86)/VMware/VMware vCenter Site Recovery Manager/storage/sra/ONTAP/command.pl"

2012-02-20T12:05:57.399-08:00 [06616 verbose 'SraCommand' opID=3E37610A-0000005B] Input for discoverArrays:

--> <?xml version="1.0" encoding="UTF-8"?>

--> <Command xmlns="http://www.vmware.com/srm/sra/v2">

-->   <Name>discoverArrays</Name>

-->   <OutputFile>C:\Windows\TEMP\vmware-SYSTEM\sra-output-22-144</OutputFile>

-->   <StatusFile>C:\Windows\TEMP\vmware-SYSTEM\sra-status-23-0</StatusFile>

-->   <LogLevel>verbose</LogLevel>

-->   <LogDirectory>C:\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs\SRAs\ONTAP</LogDirectory>

-->   <Connections>

-->     <Connection id="primary">

-->       <Addresses>

-->         <Address id="arrayIp">x.x.x.x</Address>

-->       </Addresses>

-->       <Username>***</Username>

-->       <Password>***</Password>

-->       <Opaques>

-->         <Opaque id="NFS IP">x.x.x.x</Opaque>

-->       </Opaques>

-->     </Connection>

-->   </Connections>

--> </Command>

2012-02-20T12:05:57.399-08:00 [06616 info 'AsyncJump' opID=3E37610A-0000005B] '11' ==> ...

2012-02-20T12:05:57.399-08:00 [06616 verbose 'SysCommandLineWin32' opID=3E37610A-0000005B] Starting process: "C:\\Program Files (x86)\\VMware\\VMware vCenter Site Recovery Manager\\external\\perl-5.8.8\\bin\\perl.exe" "C:/Program Files (x86)/VMware/VMware vCenter Site Recovery Manager/storage/sra/ONTAP/command.pl"

2012-02-20T12:05:57.399-08:00 [06616 verbose 'SraCommand' opID=3E37610A-0000005B] Listening for updates to file 'C:\Windows\TEMP\vmware-SYSTEM\sra-status-23-0'

2012-02-20T12:05:57.399-08:00 [06616 verbose 'PropertyProvider' opID=3E37610A-0000005B] RecordOp ASSIGN: info.progress, dr.storage.StorageManager.createArrayManager8

2012-02-20T12:05:57.415-08:00 [06632 verbose 'DrTask' opID=3E37610A-0000005B] Created VC task 'com.vmware.vcDr.dr.storage.StorageManager.createArrayManager:task-854'

2012-02-20T12:06:18.646-08:00 [06616 info 'AsyncJump'] (21.247s) ==> '11'

2012-02-20T12:06:18.646-08:00 [06616 info 'SraCommand' opID=3E37610A-0000005B] discoverArrays's stdout:

-->

--> 20-02-2012T12:05:57  NetApp FAS/V-Series Storage Replication Adapter Version 2.0.0.0 Build Date 01-08-2011

--> 20-02-2012T12:05:57  Discover Arrays Started

--> 20-02-2012T12:05:57  1

--> 20-02-2012T12:06:18  in Zapi::invoke, cannot connect to socket

--> 20-02-2012T12:06:18  Discover Arrays completed with errors

2012-02-20T12:06:18.646-08:00 [06616 verbose 'SraCommand' opID=3E37610A-0000005B] Stopped listening for updates to file 'C:\Windows\TEMP\vmware-SYSTEM\sra-status-23-0'

2012-02-20T12:06:18.646-08:00 [06616 info 'SraCommand' opID=3E37610A-0000005B] discoverArrays exited with exit code 0

2012-02-20T12:06:18.646-08:00 [06616 verbose 'SraCommand' opID=3E37610A-0000005B] discoverArrays responded with:

--> <?xml version="1.0" encoding="UTF-8"?>

-->   <Response xmlns="http://www.vmware.com/srm/sra/v2">

-->     <Error code="1002" />

-->   </Response>

-->

2012-02-20T12:06:18.646-08:00 [06616 verbose 'PropertyProvider' opID=3E37610A-0000005B] RecordOp ASSIGN: info.progress, dr.storage.StorageManager.createArrayManager8

2012-02-20T12:06:18.646-08:00 [06616 verbose 'Storage' opID=3E37610A-0000005B] XML validation succeeded

2012-02-20T12:06:18.646-08:00 [06616 error 'Storage' opID=3E37610A-0000005B] SRA command discoverArrays failed: (dr.storage.fault.LocalizableAdapterFault) {

-->    dynamicType = <unset>,

-->    faultCause = (vmodl.MethodFault) null,

-->    code = "c3554d24-7713-4086-88c8-39f20443c8c5.1002",

-->    msg = "",

--> }

2012-02-20T12:06:18.646-08:00 [06616 info 'DrTask' opID=3E37610A-0000005B] Task 'dr.storage.StorageManager.createArrayManager8' failed with error: (dr.storage.fault.CommandFailed) {

-->    dynamicType = <unset>,

-->    faultCause = (dr.storage.fault.LocalizableAdapterFault) {

-->       dynamicType = <unset>,

-->       faultCause = (vmodl.MethodFault) null,

-->       code = "c3554d24-7713-4086-88c8-39f20443c8c5.1002",

-->       msg = "",

-->    },

-->    commandName = "discoverArrays",

-->    msg = "",

--> }

[mcowger]

Looks like maybe the IP address is wrong for the array, or there is a firewall:

--> 20-02-2012T12:06:18  in Zapi::invoke, cannot connect to socket

Cannot connect to socket often indicates there is something blocking a connection (firewall or switch rules, perhaps)?

[micx]

Thanks for your quick reply, Matt.  I double-checked the storage filer IP (along with the NFS IP) and they are all correct.  There is no firewall between the SRM5 server (the firewall on the server is disabled) and the storage filers and there is no ACL or rules setup on the switch either).  What I don't understand is why one of the storage filers was added (as array manager) successfully in SRM5 while the other one failed.  I just can't seem to figure out what is blocking the connection (I can ping/ssh to this particular filer with no issues).

[davej201110141]

I had similar problems but with an IBM storage box. Wasn't solved until the SRA server (also my VC server) and the storage were on the same subnet. *Should* have worked between subnets. Are yours on the same subnet?

[micx]

Thanks for your reply, Dave.  Our vCenter 5/SRM5 server is on the same subnet as the storage filers (I can ping both filers from the SRM server and vice versa with no problem).  I also checked the httpd.admin.access and httpd.admin.enable options on both of our filers (they are currently set as legacy and on, respectively) as suggested in this thread (http://communities.vmware.com/thread/318270) but they all look OK.  I just don't know what to check next.  This is very frustrating.

[micx]

I figured the problem out today.  Since we use HP servers, it turned out that it was the HP NIC Teaming (part of HP's ProLiant Support Pack suite) software that was somehow blocking network access from the vCenter/SRM server to the NetApp storage filers (don't know why it happened in our DR site since NIC teaming is working fine on the SRM server in protected site).  Once I disabled a NIC (that's part of the team) on the SRM server, I was able to add the problematic storage filer as array manager in SRM with no problem.