VMware Cloud Community
buckmaster
Enthusiast
Enthusiast
Jump to solution

NetApp Simulate ONTAP 8.0.1 7-Mode, SRM, SRA issue

Running vSphere 4.1 up1 with SRM 4.1.1 with NetApp Simulator 8.0.1 7-Mode.  Using NFS protocol.  Have a volume replicating with snapmirror and a VM inside the VMFS volume at the protected site.  All good.  However, when I try to setup the SRA it's failing with "Failed to connect to management system address while executing discoverArrays command.  Here is a part of the log file with the error:  By the way the firewall on the SRM server where the SRA is installed is OFF.

[2011-06-20 21:49:15.012 03924 trivia 'PrimarySanProvider'] Environment windir=C:\Windows will be set for the script

[2011-06-20 21:49:15.012 03924 verbose 'SysCommandLineWin32'] 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/scripts/SAN/ONTAP/command.pl"

[2011-06-20 21:49:16.402 03924 trivia 'PrimarySanProvider'] discoverArrays's output:

[#1] <Response>

[#1]  Discover Arrays Started

[#1]  Collecting array information

[#1]  in Zapi::invoke, cannot connect to socket

[#1]  Discover Arrays completed with errors

[#1] </Response>

[2011-06-20 21:49:16.402 03924 info 'PrimarySanProvider'] discoverArrays exited with exit code 0

[2011-06-20 21:49:16.402 03924 trivia 'PrimarySanProvider'] 'discoverArrays' returned <?xml version="1.0" encoding="UTF-8"?>

[#1] <Response>

[#1]   <ReturnCode>2</ReturnCode>

[#1] </Response>

[#1]

[2011-06-20 21:49:16.402 03924 info 'PrimarySanProvider'] Return code for discoverArrays: 2

[2011-06-20 21:49:16.402 03924 error 'PrimarySanProvider'] The scripts returned an error, leaving the temporary file 'C:\Windows\TEMP\vmware-SYSTEM\dr-sanprovider3924-0'

[2011-06-20 21:49:16.402 03924 error 'PrimarySanProvider'] Invalid array management system address reported by the script

[2011-06-20 21:49:16.402 03924 info 'ArrayManagerImpl.QueryInfoTask-Task'] Work function threw MethodFault: dr.san.fault.InvalidAddressFault

[2011-06-20 21:49:16.402 03924 info 'ArrayManagerImpl.QueryInfoTask-Task'] Fault:

[#1] (dr.san.fault.InvalidAddressFault) {

[#1]    dynamicType = <unset>,

[#1]    faultCause = (vmodl.MethodFault) null,

[#1]    command = "discoverArrays",

[#1]    msg = "",

[#1] }

[2011-06-20 21:49:16.402 03924 verbose 'PropertyProvider'] RecordOp ASSIGN: info.error, ArrayManagerImpl.QueryInfoTask-68

[2011-06-20 21:49:16.402 03924 verbose 'ArrayManagerImpl.QueryInfoTask-Task'] Error set to (dr.san.fault.InvalidAddressFault) {

[#1]    dynamicType = <unset>,

[#1]    faultCause = (vmodl.MethodFault) null,

[#1]    command = "discoverArrays",

[#1]    msg = "",

I've followed the instructions from these sites to find a fix:

http://communities.vmware.com/message/1269985#1269985

https://kb.netapp.com/support/index?page=content&id=2011278

https://kb.netapp.com/support/index?page=content&id=1010829

http://www.vmwareinfo.com/2011/05/vmware-site-recovery-manager-error.html

http://www.scribd.com/doc/50714545/3/NetApp-Simulator-Network-Configuration

Also I've tried both the NFS SRA and the Unified version, both exhibit the same errors.

Your help is appreciated as I'm trying to learn NetApp, SRM before I deliver the real deal in a couple of weeks.

Thanks - Tom Miller

Tom Miller
Reply
0 Kudos
1 Solution

Accepted Solutions
LarryNTAP
Enthusiast
Enthusiast
Jump to solution

Hi Tom,   It looks like the filer is denying your request to connect.  Might be a couple things:

You do not have the options httpd.admin.access or httpd.admin.enable set appropriatly.  These may prevent api access which is http based.

If you are trying to do https connection you might have set the SRA to use ssl (in ontap_config.txt on the srm server) but you do not have ssl enabled on the netapp and have not followed the instructions at https://kb.netapp.com/support/index?page=content&id=1012531 I doubt this is your problem since you didnt mention at all that you want ssl.

This problem might come up after you get past the above, based on the errors you got you're not even connecting to the filer.  With ontap 8.0.x you MUST put an address in the NFS IP Addresses field when configuring the SRA if you are using NAS storage.  The IP addresses you put there should be the addresses you want the ESX hosts to connect to on that array when they make NFS mounts, this might be private IP addresses that are different than the administration IP address.  If you only have one IP address (common when playing with sims) then with ontap 8.0.x you have to put the admin IP in the NFS IP Addresses field too.  In ontap 8.0.x you must use the NFS IP Addresses field, even if your filer has only one IP, because this forces the SRA to ignore other local loopback addresses that exist in ontap 8 that did not exist in previous releases.

You should download and use NetApp adapter version 1.4.3P1, you can get this from the NOW site by scrolling to the end of the software download list and selecting the DRA then typing in version 1.4.3P1.  None of the issues described above are corrected for in the P1 release, but it might help you miss other issues once you get connected properly.

Larry

View solution in original post

Reply
0 Kudos
7 Replies
idle-jam
Immortal
Immortal
Jump to solution

why not have a look at this video and see if you missed out anything: http://www.youtube.com/watch?v=L_qISYjTP-g

Reply
0 Kudos
LarryNTAP
Enthusiast
Enthusiast
Jump to solution

Hi Tom,   It looks like the filer is denying your request to connect.  Might be a couple things:

You do not have the options httpd.admin.access or httpd.admin.enable set appropriatly.  These may prevent api access which is http based.

If you are trying to do https connection you might have set the SRA to use ssl (in ontap_config.txt on the srm server) but you do not have ssl enabled on the netapp and have not followed the instructions at https://kb.netapp.com/support/index?page=content&id=1012531 I doubt this is your problem since you didnt mention at all that you want ssl.

This problem might come up after you get past the above, based on the errors you got you're not even connecting to the filer.  With ontap 8.0.x you MUST put an address in the NFS IP Addresses field when configuring the SRA if you are using NAS storage.  The IP addresses you put there should be the addresses you want the ESX hosts to connect to on that array when they make NFS mounts, this might be private IP addresses that are different than the administration IP address.  If you only have one IP address (common when playing with sims) then with ontap 8.0.x you have to put the admin IP in the NFS IP Addresses field too.  In ontap 8.0.x you must use the NFS IP Addresses field, even if your filer has only one IP, because this forces the SRA to ignore other local loopback addresses that exist in ontap 8 that did not exist in previous releases.

You should download and use NetApp adapter version 1.4.3P1, you can get this from the NOW site by scrolling to the end of the software download list and selecting the DRA then typing in version 1.4.3P1.  None of the issues described above are corrected for in the P1 release, but it might help you miss other issues once you get connected properly.

Larry

Reply
0 Kudos
buckmaster
Enthusiast
Enthusiast
Jump to solution

Thanks LarryNTAP.  The httpd options did the trick!

Tom Miller
Reply
0 Kudos
buckmaster
Enthusiast
Enthusiast
Jump to solution

OK, SRA is working sort of.  When running a test plan it does not fine the NFS vol at the replicated site.  Isn't the responsibility of the SRA to handle exposing the volume at the replicated volume at the DR site?  Here is a snippit of the log.  By the way I uninstalled the SRA and installed the one you mentioned above.

2011-06-21 14:33:42.921 00816 verbose 'PropertyProvider'] RecordOp ASSIGN: info.error, RSStorageOperationList-12236-3
[2011-06-21 14:33:42.921 00816 verbose 'RSStorageOperationList-12236-Task'] Error set to (dr.san.fault.ArrayNotFound) {
[#1]    dynamicType = <unset>,
[#1]    faultCause = (vmodl.MethodFault) null,
[#1]    arrayKey = "na-dr",

na-dr is my simulator for the DR site.

Tom Miller
Reply
0 Kudos
buckmaster
Enthusiast
Enthusiast
Jump to solution

My bad.  I failed to setup the SRA appropriately in BOTH directions.

Thanks for your help.  Successfully RAN a test plan!!

Tom Miller
Reply
0 Kudos
LarryNTAP
Enthusiast
Enthusiast
Jump to solution

Cool, thanks for the feedback followup.

Larry Touchette

Technical Marketing Engineer

Data Protection

NetApp

810.441.9060 Direct

lt@netapp.com<applewebdata://1D1AF74A-550B-4584-A988-039BB609BA87/lt@netapp.com>

www.netapp.com

From: buckmaster <communities-emailer@vmware.com<mailto:communities-emailer@vmware.com>>

Reply-To: communities-emailer <communities-emailer@vmware.com<mailto:communities-emailer@vmware.com>>

Date: Tue, 21 Jun 2011 12:40:27 -0700

To: <larryet@netapp.com<mailto:larryet@netapp.com>>

Subject: New message: "NetApp Simulate ONTAP 8.0.1 7-Mode, SRM, SRA issue"

VMware Communities<http://communities.vmware.com/index.jspa>

NetApp Simulate ONTAP 8.0.1 7-Mode, SRM, SRA issue

reply from buckmaster<http://communities.vmware.com/people/buckmaster> in Site Recovery Manager - View the full discussion<http://communities.vmware.com/message/1776599#1776599

Reply
0 Kudos
WillFulmer
Enthusiast
Enthusiast
Jump to solution

Larry,

Is it possible to use a DNS alias rather than IP address for the NFS mounts from the NetApp Filers?

We're seeing an error in the logs when trying to use a datastore mapped by a FQDN vs. IP address

"SRA command 'discoverArrays' failed. sraError.c3554d24-7713-4086-88c8-39f20443c8c5.1007.desc

sraError.c3554d24-7713-4086-88c8-39f20443c8c5.1007.fixHint"

Just wondering if you know off hand if this is supported/recommended.

Thanks

-Will

Reply
0 Kudos