About watan

watan · ‎2010-04-06

You noted SSL is configured but are using http as the transport. Does it work with HTTPS or RPC? May want to take a OntapWinDC to review the errors.

watan · ‎2010-04-06

Check out these KB's https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb1368 https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb1350

watan · ‎2010-04-06

There are 90 day evaluation licenses available and can be renewed up to 3x's. http://now.netapp.com/eservice/evallicense

watan · ‎2010-03-16

I'm sure there will be others running into the same problem. Thanks for posting the fix.

watan · ‎2010-03-01

Dedupe will not cause this behavior with quotas. Quotas check how much logical data is being stored, and not how much physical space the data is taking. To see what is going on from the NetApp perspective, you can use the ‘df –s’ command. Output will show used (the amount of physical space used to store the data in the deduped volume), and saved (the amount of space that has been freed as a results of using deduplication). To get the total logical data that is being storage in the deduped volume, you add values of used + saved.

watan · ‎2010-02-19

Hi Marc, 1) Steps to configure the ESX SW iSCSI Software Initiator using VI-Client * Enable ESX iSCSI SW initiator in ESX server. * Check License under Licensed Features of Configuration Tab. * Add the VMKernel Port under the Networking configuration option. Enable VMotion. * Under Security Profile select the port for the Software iSCSI client. * Select the ESX SW iSCSI initiator and click the "Enabled" checkbox. Add ESX SW iSCSI targets to discovery list using VI-Client. * Navigate to the Properties of the iSCSI adapter and click on the Dynamic Discovery tab. * Choose to Add new Target. * Enter the IP address & port of the target server and click OK. 2) If you're not having any specific problems with using MS iSCSI then I personally don't see any reason to change it. If its not broken... Also refer to the following docs as they may have more on performance or general best practices. The performance best practices : For ESX 3.5: http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_iscsi_san_cfg.pdf For ESX 4 : http://www.vmware.com/pdf/vsphere4/r40/vsp_40_iscsi_san_cfg.pdf NetApp and VMware VI3 best practice Guide : http://media.netapp.com/documents/tr-3428.pd

watan · ‎2010-02-11

SDW 6.1 had support for FCP HBA in ESX server and MS iSCSI initiator in GuestOS for its operations. Now with SDW 6.2 we support ESX iSCSI and iSCSI HBA initiators in SnapDrive. SnapDrive will perform LUN provisioning and snapshot management operations using ESX iSCSI and iSCSI HBA initiators. The kb from VMware does point out an issue with the configuration you pointed out but there are workarounds in place which hopefully will resolve any issues.

watan · ‎2010-02-10

Try setting the swsvc service to depend on the clussvc service so SnapDrive doesn't start before the cluster service.

watan · ‎2010-02-01

Both scenarios look to accomplish the same thing , except scenario 1 is reserving the volume space in the aggregate as opposed to scenario 2 is not reserving any space. In Scenario 2, you have the potential of running out of space in the volume if the aggr gets full. It's probably set this way in Provisioning manager because of the toolset it has to manage its storage space.

watan · ‎2010-01-29

Will forward your question to the Storage Management Software team.

watan · ‎2010-01-27

Hi Chao, 1) why SDW report "Failed to enumerate virtual disks, error code 0x800703f0"? May want to look at the host side logs to see if there are any other errors. iScsi network errors could cause some problems. 2) Is it necessary that SDW service must be up when do MSCS failover? SDW service needs to be up and running for snapdrive to work and not for MSCS failover. 3) is it the root cause that 16 LUNs is too much for SDW? 16 luns should be fine. 4) Any workaround? Found a KB article that may help https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb34470

watan · ‎2010-01-05

Hi Philip, I was able to confirm with the engineering team that they are aware of this issue. They have linked this issue with another burt 313750 and will work to get this resolved in a patch or the next release. This will be decided in the weeks to come.

watan · ‎2009-12-29

Hi Kelvin, Did you check the IMT for supported configuration? I'm showing RHEL 5.3 supported in various versions and protocols. I took a look at the BURT db and got a few hits with similar issues but most were on versions prior to 3.0. Check out Burt 228115 which had a similar issue but on the SUSE platform. If you're still having problems, check out the config checker http://now.netapp.com/NOW/download/tools/snapdrive_config_checker_unix/ and post a snapdc for the problem node. http://now.netapp.com/NOW/download/tools/snapdrive_data_collector_unix/ Thanks, Allan

watan · ‎2009-12-29

Hi Phillip, Can you get me a OntapwinDC for this node? It will probably be after the New year to get this looked at by the dev team. Thanks, Allan

watan · ‎2009-12-15

Hi Philip, Got your PM and sent one right back at you. I will have the dev team take a look and will post the results here.

watan · ‎2009-12-14

This problem has not been seen by either the QA team nor the Engineering team. If you are still experiencing this problem, can you please provide a OntapWinDC from this node?

watan · ‎2009-12-14

Hi Andre, Check if the windows firewall is blocking the sdw service? The required ports are TCP ports 808,4095, and 4096. Then remove the server from mmc, restart the SDW service, then try to readd the server.

watan · ‎2009-12-10

This means that the text to display with the event was not found. Can you please provide the SDW version used?

watan · ‎2009-12-10

I was able to confirm this with the engineering team and we do not provide the FQDN. This would require a RFE for future release.

watan · ‎2009-12-10

We'll need more info to find the root of the problem and will need OntapWinDC logs to investigate further. http://now.netapp.com/NOW/download/tools/snapmanager_e2k_dct/

watan · ‎2009-12-10

Hi Abhinav, It looks like its getting denied when trying to mount the snapshot lun. Can you post a OntapWINDC? What versions of SDW and SME is this?

watan · ‎2009-11-09

You may want to look at the oplock settings of the client and Netapp array to see if this improves the performance of the database. More about Oplocks here. http://now.netapp.com/NOW/knowledge/docs/ontap/rel7311/html/ontap/filesag/accessing/task/t_oc_accs_improving_client_performance_with_oplocks.html#t_oc_accs_improving_client_performance_with_oplocks Array options - options cifs.oplocks.enable

watan · ‎2009-11-05

Hi Phillip, There may be an issue with the sdparams.conf file . Please have a look at the following KB and TR. https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb47898 http://media.netapp.com/documents/tr-3483.pdf <- check out section 7.3 which talks about the sdparams.conf file.

watan · ‎2009-11-03

You can get eval keys from the following link http://now.netapp.com/NOW/download/special/evaluation.cgi

watan · ‎2009-10-29

Hi Robert, This looks like the updated package required - FC-FCoE Driver (x86/x64/IA64) 8.02.23 http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/SearchByProduct.aspx?ProductCategory=39&Product=936&Os=65

Re: Snapdrive 6.2 unable to list storage system license

Re: Setting retention date for SnapLock files (Windows)

Re: Simulator based SnapDrive license

Re: SDU 4.1.1 - RBAC fails on storage discovery (with SMO 3.0.3)

Re: Quota hard limit is not correct enforced?

Re: SMVI - backing up VMs with iSCSI LUNS and SnapManager

Re: SMVI - backing up VMs with iSCSI LUNS and SnapManager

Re: Snapdrive issue when MSCS do failover. "Failed to enumerate virtual disks, error code 0x800703f...

Re: Provisioning Manager and Thin Provisioned LUN's

Re: Provisioning Manager and Thin Provisioned LUN's

Re: Snapdrive issue when MSCS do failover. "Failed to enumerate virtual disks, error code 0x800703f...

Re: SnapDrive 6.1 "not designated for thin provisioning"

Re: Snapdrive errors when using "-fs -nolvm" options on 4.1.1 (linux redhat 5.3)

Re: SnapDrive 6.1 "not designated for thin provisioning"

Re: SnapDrive 6.1 Invalid Host License Error

Re: SnapDrive 6.1 Invalid Host License Error

Re: Installed SnapDrive 6.02 in Windows 2008 SP2 X64

Re: what's means of SDW error code Error 0x80041033 ?

Re: SnapManager not following RFC 821/5321?

Re: Snapdrive 6.1 keeps stopping corrupt WMI

Re: [SnapDrive Error]: Access is denied.

Re: Slow access database behaviour on netapp CIFS share

Re: SnapDrive 6.1 "not designated for thin provisioning"

Re: OSSV Evaluation Key

Re: What driver needs to be installed?