NetApp Technology Network : Thread List - Host Side Data Management

Sun Branded Emulex HBA's

community@netapp.com — Tue, 10 Nov 2009 17:15:17 GMT

All,

IHAC who has Solaris 9 u9 and wants to install SDU 4.1.1/SMO 3.0.2. I can't find any HBA's that have a Sun part number that are certified for SDU. I found some that are SAN supported, but not SDU supported. If an HBA is SAN supported it it SDU supported?

Here is the HBA info:

Assembled 04 August 2005 LP10000-S

fcode-version 1.50a9

(Emulex-S s9-64 sparc v1.20g

Thanks,

Bethel

AIX MPIO / offline LUN has most (not ALL) of paths Failed?!

community@netapp.com — Mon, 09 Nov 2009 16:10:44 GMT

Hello all,

I'm seeking guidance/answers. AIX 6.1TL3 here, with MPIO NetApp installed, NO ALUA, versions below:

root@x:/oracle/TPM/sapdata1# lslpp -cl|grep -i netapp
/usr/lib/objrepos:NetApp.SAN_toolkit.sanlun:5.0.0.0::COMMITTED:I:Network Appliance AN Toolkit sanlun:
/usr/lib/objrepos:NetApp.SAN_toolkit.scripts:5.0.0.0::COMMITTED:I:Network Appliance SAN Toolkit Scripts:
/usr/lib/objrepos:NetApp.mpio_attach_kit.config:5.0.0.0::COMMITTED:I:Network Applia ce MPIO PCM Kit Path Config Tool:
/usr/lib/objrepos:NetApp.mpio_attach_kit.fcp:5.0.0.0::COMMITTED:I:Network Appliance MPIO PCM Kit FCP Disk ODM Stanzas:
/usr/lib/objrepos:NetApp.mpio_attach_kit.iscsi:5.0.0.0::COMMITTED:I:Network Applian e MPIO PCM Kit iSCSI Disk ODM Stanzas:
/usr/lib/objrepos:NetApp.mpio_attach_kit.pcmodm:5.0.0.0::COMMITTED:I:Network Applia ce MPIO PCM Kit PCM Friend ODM Stanzas:
/usr/lib/objrepos:NetApp.snapdrive:4.1.0.0::COMMITTED:I:Network Appliance SnapDrive

@FAS3140C offlined LUN for hdisk7:

root@x:/oracle/TPM/sapdata1# lspath -F"name parent path_id connection status"|grep ^hdisk7
hdisk7 fscsi0 0 500a0982995ad101,6000000000000 Failed
hdisk7 fscsi0 1 500a0981895ad101,6000000000000 Failed
hdisk7 fscsi1 2 500a0982895ad101,6000000000000 Failed
hdisk7 fscsi1 3 500a0981995ad101,6000000000000 Enabled

root@x:/oracle/TPM/sapdata1#

root@x:~# sanlun lun show|grep hdisk7

root@x:~#

Onlined LUN for hdisk7:

root@x:/oracle/TPM/sapdata1# lspath -F"name parent path_id connection status"|grep ^hdisk7
hdisk7 fscsi0 0 500a0982995ad101,6000000000000 Enabled
hdisk7 fscsi0 1 500a0981895ad101,6000000000000 Enabled
hdisk7 fscsi1 2 500a0982895ad101,6000000000000 Enabled
hdisk7 fscsi1 3 500a0981995ad101,6000000000000 Enabled
root@x:/oracle/TPM/sapdata1#

root@x:~# sanlun lun show|grep hdisk7
kopdslab04d: /vol/y/sapdata2/sapdata02.lun hdisk7 fcs1 FCP 150g (161061273600) GOOD
root@x:~#

Questions:

1) why not all paths are Failed?! (isn't this bug?)

2) if LUN is offline, but device is present (hdisk7 is Available , reported by "lsdev -Cc disk |grep hdisk7"), why sanlun reports nothing at all for that hdisk7? Shouldn't it report FAULT/etc? (is this bug too?)

Thanks.

-Jakub Wartak

SD6.2 with pass through FCP RDM LUN in vShere4

community@netapp.com — Fri, 06 Nov 2009 22:23:05 GMT

Hello All,

We are trying to use SnapDrive 6.2 to create a RDM LUN within a Windows2003 guest VM within Vsphere4. I have looked through the IAG and I can't seem to find out how to accomplish this. As we go through the process, everything is working as normal except when we go to add an initiator. There are no initiators in the guest OS so it will not allow us to move past this point..

Is there a way that you make the HBA's from the ESX server show up as a device within the Guest OS? I am definitely missing something...

Thanks,
Chris

SnapDrive 6.1 "not designated for thin provisioning"

community@netapp.com — Thu, 05 Nov 2009 08:35:24 GMT

I can not find any reference to this message. I know it is only classed as “info” but the message suggest something is miss-configured.

filer104> Sat Oct 31 19:27:05 GMT [app.log.info:info]: WIN2003-SNAPDRI: SnapDrive 6.1: (373) Service execution status: Found non-space reserved LUN(s) on volume '/vol/win2003_sd_01'. This volume is not designated for thin provisioning.

The volume on the filer has a guarantee of “none” and the LUN does not have space reserve enabled (by using storacl.exe).

Thanks

Philip

SnapDrive 6.1 Invalid Host License Error

community@netapp.com — Thu, 05 Nov 2009 08:41:20 GMT

I believe there is a bug in the install process of SnapDrive for Windows 6.1. If you select the host license and enter a valid key it says it is invalid and will not continue with the install. If you then select the filer license it will then install ok. Once installed I have found I can then add the host license using either the CLI or SnapDrive GUI.

Has anyone else found this?

Thanks

Philip

OSSV Evaluation Key

community@netapp.com — Mon, 19 Oct 2009 20:26:50 GMT

Can someone advise as to how evaluation license keys are obtained for OSSV?

Snapdrive 6.1 keeps stopping corrupt WMI

community@netapp.com — Mon, 02 Nov 2009 10:12:54 GMT

Hi,

We have an issue with the snapdrive 6.1 service stopping on Windows 2008 builds running Microsoft Exchange 2007

Every time snapdrive fails due to broken WMI. Only snapdrive fails other Applications using WMI work.

This can be fixed using winmgmt /salvagereposity

But whay does this keep happening? Is this a bug with Snapdrive 6.1?

Micky

SnapDrive on HPUX fails

community@netapp.com — Thu, 22 Oct 2009 11:46:18 GMT

I’m trying to get snapdrive working a HPUX 11.31 Itanium. I using running SnapDrive 4.1.1 and fcp host utilities 4.3. I have other luns on this host to the same filer not though SnapDrive working working fine. I am using ALUA as the multipathing and I did enable it ALUA on the igroup.

I also sent the multipathing in the SnapDrive.conf as PVLINKS is this correct?

uxwpeng8:/opt/NetApp/snapdrive# snapdrive storage create -lun 54.18.108.6:/vol/oradb1/test -lunsize 10m

LUN 54.18.108.6:/vol/oradb1/test ... created

mapping new lun(s) ... done
discovering new lun(s) ... *failed*

Cleaning up ...
- LUN 54.18.108.6:/vol/oradb1/test ... deleted
0001-476 Admin error: Unable to discover the device associated with 54.18.108.6:/vol/oradb1/test. If multipathing in use, there may be a possible multipathing configuration error.
Please verify the configuration and then retry

sanlun lun show -p

uswsnssan1b:/vol/oradb2/lun36 (LUN 31)
Agile Filename: /dev/rdisk/disk204
17.0g (18254659584)    lun state: GOOD
Filer_CF_State: Cluster Enabled Filer Partner: uswsnssan1a
Multipath_Policy: None
Multipath_Provider: None
-------- --------- -------------------- ------ ------- --------
host     filer                                 primary partner
path     path                  /dev/dsk host   filer   filer
state    type                  filename HBA    port    port
-------- --------- -------------------- ------ ------- --------
up       primary       /dev/dsk/c23t3d7 td0    0a
up       primary       /dev/dsk/c21t3d7 td1    0b
up       secondary     /dev/dsk/c25t3d7 td2            0b
up       secondary     /dev/dsk/c27t3d7 td3            0a

SDU 4.1.1 help

community@netapp.com — Fri, 16 Oct 2009 19:18:29 GMT

IHAC who is running 64 bit RHAS 4 u6 with 32 bit emulation installed. I have a problem that looks like the typical HTTPS/SSL being the default setting of snapdrive.conf. HTTPS/SSL is turned on on the filer. "snapdrive snap list -filer filername" works. "snapdrive config access list filername" shows:

Commands allowed:

snap create

snap restore

snap delete

snap rename

storage create

storage resize

snap connect

storage connect

storage delete

snap disconnect

storage disconnect

When I do a "snapdrive storage show -all", I receive:

0001-185 Command error: storage show failed: no NETAPP devices to show or add the host to the trusted hosts (options trusted.hosts) and enable SSL on the storage system or retry after changing snapdrive.conf to use http for storage system communication and restarting snapdrive daemon.

I'm confused. Why would the first 2 commands succeed and the last one fail.

Thanks

SnapDrive 6.1 Windows with FC RDM LUNs

community@netapp.com — Wed, 09 Sep 2009 20:38:45 GMT

I'm working on an implementation where several SnapManager (SME/SMSQL) products will be running on Windows Virtual Machines. The ESX servers are all FC connected and I've successfully used SnapDrive to create and connect to RDM LUNs inside the guests. Since we'll probably end up with 50 or so RDM LUNs when this thing is all said and done, the customer would like to be able to easily identify the RDM LUNs vs the straight VMWare datastore LUNs. We decided to reserve LUN IDs 0-19 for VMWare datastore formatted LUNs and use 20 and higher for the RDM LUNs. The problem is when using SnapDrive to connect to a LUN, there is no way I've found to change the LUN ID. It automatically just picks the next LUN ID available, which throws a wrench into our naming scheme. What I've been doing instead is creating and attaching the LUN using SnapDrive, then I disconnect and manually remap it on the filer so I can put in my own custom LUN ID. So I have two questions really.

1. Does anyone know of a way to tell SnapDrive either a starting LUN ID or provide it a customized LUN ID when connecting to a LUN?

2. As long as I create and connect the LUN initially using SnapDrive, is there any type of problem with disconnecting it and then doing a manual lun map to that same LUN again? I just don't know if SnapDrive is doing anything special when it connects and mounts a LUN, different than what a normal Windows server would do with a manual rescan and drive mount. I thought as long as I initially create the LUN using SnapDrive I'll have the formatting and alignment issues covered, but I'm not sure if I'm missing anything else that would differentate a SnapDrive mounted LUN vs a manually mounted one.

Thanks in advance

Using sdcli on remote Windows 2008 host

community@netapp.com — Tue, 06 Oct 2009 07:41:02 GMT

I have build a SpaceReclaimer script that starts the SpaceReclaimer once a week on all selected hosts using the sdcli command. The script runs on a Windows 2003 x64 host. Thusfar, we used it with other Windows 2003 hosts without any problem. Recently, we installed a couple of Windows 2008 x64 hosts with NetApp LUNs attached to them. Unfortunatelly, the script fails on these hosts with the message: "Error: The RPC server is unavailable."

I've tried running the sdcli command on one of these Windows 2008 x64 hosts. Locally it worked perfectly, but connection to another Windows 2008 x64 host fails with the same error.

I've also tried disabling the WIndows Firewall on these hosts, but with no effect. As suggested in the SnapDrive 6.1 for Windows Installation and Administration Guide, I also tried running the script as Administrator, but also with no luck...

Can anyone help me?

Bjorn