cancel
Showing results for 
Search instead for 
Did you mean: 

I see the new LUNs single path in the VEA

Hello everyone
I have a little problem with the microsoft cluster (windows server 2008 sp2 x32)  with SFW 5.1 SP2.

When they are assigned to the new LUN (emc VMax), I see the LUNs a single path in the VEA , but with the SUNSurfer, I see them properly with the dual path.

To show the dual paths are forced to restart the cluster nodes.
After rebooting, I see the correct the dual path, and log in I get this error:
The Virtual Storage Filter Driver is disabled through the registry. It is inactive for all disk drives.
 
The device, \ Device \ Harddisk1 \ DR9, is not ready for access yet

searching the web, I saw this technote from Microsoft,
http://www.techbind.org/post/2010/03/24/The-Virtual-Storage-Filter-Driver-is-disabled-through-the-re...

but it is not applicable to my problem when I do not have Hyper-V Server.

DMP problem? is there anyone can help me?

thanks in advance

jako

1 Solution

Accepted Solutions
Accepted Solution!

Actually, no 'native' DMP

Actually, no 'native' DMP software with SFW - it has to be explicitely selected during the installation process, provided that you have entered the appropriate license key(s):

DMP Device Specific Modules (DSMs):

■ 3PARDATA (V3PARAA)
■ Dell EqualLogic array (VEQLOGIC)
■ EMC Symmetrix/DMX (VEMCSYMM)
■ EMC Clarion (VEMCCLAR)
■ Hitachi TagmaStore/HP XP (VHDSAA)
■ Hitachi 95xx-AMS-WM (VHDSAP)
■ HP 2000 array (VHPMSA2)
■ HP EVA-MSA (VHPEVA)
■ IBM DS8000/ESS (VIBMAADS)
■ IBM DS6000 (VIBMAP)
■ IBM DS4000/SUN 6000 (VENGAP)
■ IBM DS AP (VIBMAPDS)
■ IBM XiV Storage System (VXIV)
■ HUAWEI S5300/S2300 array (VHUAWEIAP)
■ FUJITSU ETERNUS 2000 array (VFUJITSUAA)
■ NETAPP (VNETAPP)
■ PILLAR (VPILLAR)
■ WindowsStorage Server 2003R2iSCSI (VITARGET)
■ XioTech Array (VXIOTECH)
■ Compellent array (VCOMPLNT)
■ Promise Array (VPROMISE)
■ SUN Array (VSUN)

 

If you expand 'StorageAgent' -> DMP DSMs, which module(s) do you see?

View solution in original post

9 Replies

Which Multipathing

Which Multipathing software?

EMC PowerPath or MPIO with DSM modules?

If Powerpath, SF won't know about the paths.

the software of multipaht

the software of multipaht native SFW

 

br

jako

Accepted Solution!

Actually, no 'native' DMP

Actually, no 'native' DMP software with SFW - it has to be explicitely selected during the installation process, provided that you have entered the appropriate license key(s):

DMP Device Specific Modules (DSMs):

■ 3PARDATA (V3PARAA)
■ Dell EqualLogic array (VEQLOGIC)
■ EMC Symmetrix/DMX (VEMCSYMM)
■ EMC Clarion (VEMCCLAR)
■ Hitachi TagmaStore/HP XP (VHDSAA)
■ Hitachi 95xx-AMS-WM (VHDSAP)
■ HP 2000 array (VHPMSA2)
■ HP EVA-MSA (VHPEVA)
■ IBM DS8000/ESS (VIBMAADS)
■ IBM DS6000 (VIBMAP)
■ IBM DS4000/SUN 6000 (VENGAP)
■ IBM DS AP (VIBMAPDS)
■ IBM XiV Storage System (VXIV)
■ HUAWEI S5300/S2300 array (VHUAWEIAP)
■ FUJITSU ETERNUS 2000 array (VFUJITSUAA)
■ NETAPP (VNETAPP)
■ PILLAR (VPILLAR)
■ WindowsStorage Server 2003R2iSCSI (VITARGET)
■ XioTech Array (VXIOTECH)
■ Compellent array (VCOMPLNT)
■ Promise Array (VPROMISE)
■ SUN Array (VSUN)

 

If you expand 'StorageAgent' -> DMP DSMs, which module(s) do you see?

View solution in original post

my mistake :) during the

my mistake :)

during the installation phase, I have only enabled the DSMs of storage modules that are present in the SAN.

■ 3PARDATA (V3PARAA)
■ EMC Symmetrix/DMX (VEMCSYMM)
■ EMC Clarion (VEMCCLAR)
■ IBM DS8000/ESS (VIBMAADS)
■ IBM DS6000 (VIBMAP)
■ IBM DS4000/SUN 6000 (VENGAP)
■ IBM DS AP (VIBMAPDS)


 

excuse me for my mistake.

No need to select all DSM

No need to select all DSM modules during installation. You only need the ones required by the storage that is attached to the host.

Please post a screen shot of the GUI with 'StorageAgent' and DMP DSMs expanded.

are you showing two events here?

This looks like:

1) disk driver reporting a disk is not ready for access

2) the Virtual Storage Filter Driver logging a message

 

Issue (1) needs to be investigated if it is showing the operating system cannot access the LUN, represented as PhysicalDriveX.

From the reference to the MS KB 951007 it looks like you can ignore (2)

If the DMP DSM has claimed the device correctly you should see the paths listed in the VEA gui under the DMP DSM tab when the HarddiskX is selected.

If you can trace the same LUN via multiple paths in SanSurfer, and the same number of paths are not present in the DMP DSM tab then you may have an issue with the DSM.  The DSM you have selected should claim the VMAX.  If the DMP DSM tab is not present then SFW is not managing the paths either.

Try the output of:

a) vxdmpadm dsminfo harddiskX (where X= the harddisk number of a VMAX disk)

- this will show if a DSM has claimed the disk

b) vxdmpadm deviceinfo harddiskX

- this will show the number of paths

 

hope this helps

James.

vxdmpadm deviceinfo

hi all,

by SANsurfer, I can see the LUNs correctly with double path, below the output of the command

vxdmpadm deviceinfo

 

C:\Users\US02993>vxdmpadm deviceinfo harddisk2
=========================================================================
Device information
    Name        :   Harddisk2
    Media Name  :
    No. of Paths:   2
    LoadBalancePolicy       :   Round Robin (Active/Active)
Path information ...
Path 2-0-0:
    State       :   Healthy
    Primary     :   NO
    SCSI-3 Persistent Reservation: NO
    SCSI-3 Reserved: NO
    Port        :   2
    Channel     :   0
    Target      :   0
    LUN         :   1
    Active IO group : NO
Path 3-0-0:
    State       :   Healthy
    Primary     :   NO
    SCSI-3 Persistent Reservation: NO
    SCSI-3 Reserved: NO
    Port        :   3
    Channel     :   0
    Target      :   0
    LUN         :   1
    Active IO group : NO
 
C:\Users\US02993> vxdmpadm dsminfo harddisk2
    DSM Name                :
    Array Name              :
    Device(s) in this Array :
                                Harddisk1
                                Harddisk2
    Total # of device(s)    :   2
    Type                    :   -
    SCSI-3 Persistent Reservation: NO
    LoadBalancePolicy       :   Round Robin (Active/Active)
    TestPathRetryCount      :   0
    ScsiCmdTimeOut          :   0 second(s)
    KernelSleepTime         :   0 millisecond(s)
    FailoverRetryCount      :   0

Hi Giacompane, From your

Hi Giacompane,

From your output, we can see that there is no DSM that has claimed your disk. 

 

C:\Users\US02993> vxdmpadm dsminfo harddisk2
    DSM Name                :                                              <-- blank
    Array Name              :                                                <-- blank

 

This means that you have one of three problems.

 

1. The DSM needed to claim the device is not install.

2. The MPIO framework is not installed.

or

3. The Arrays product/vendor ID strings have been altered from what the DSM is expecting them to be to identify the array correctly.

 

Please check these items.

 

Thanks,

Wally

Can you confirm that you have

Can you confirm that you have the Microsoft MPIO Framework installed? Without this DMP will not configure paths. 

Regards

Lee