Video Screencast Help

Unable to display enclosure name under the enclosure in VEA for array FUJITSU ETERNUS4000

Created: 28 Apr 2013 • Updated: 10 May 2013 | 5 comments
peteryang73's picture
This issue has been solved. See solution.

Customer has installed SFWHA6.0.1 on Windows2008 R2 Standard version.It has only one array E4000. MPIO looks fine.Harddisk1 and Harddisk2 appear within the default enclosure which is displayed as Disks@Hostname.

Who knows the meaning of err 1005 within vdid_get() failed err(1005) according to vxisis.log. Any comments are really appreciated!

 

Snipping of vxisis.log

-----------------------------------------------------------------------------

2013/4/27 16:22:38:1860:LoadProvider: loading provider ddlprov from location C:\Program Files\Veritas\Veritas Volume Manager\providers\ddlprov.dll
2013/4/27 16:22:38:1860:CDdlprov:Initialize gDMPSA=FALSE
2013/4/27 16:22:38:1860:ddlprov:CreateEncAliasKey - No enclosurealias key.  Creating...
2013/4/27 16:22:38:1860:CDdlprov::EnumerateDisks - Enter
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - newDevName \\?\PhysicalDrive1
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - vdid_get() er=(1005).
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - In VDID_MAY_NOT_BE_UNIQUE case.
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - vdid_get() failed err(1005).
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - Internal Disk. Device name used as Disk vdid \\?\PhysicalDrive1@domain.hostname.
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - it is a internal array.
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - With fullname of Computer, Enclosure vdid DISKS@domain.hostname.
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - CreateEnclousreObject
2013/4/27 16:22:38:1860:CDdlprov:CreateEnclosureObject entered - vdid DISKS@domain.hostname, internal 1, correlatable 0.
2013/4/27 16:22:38:1860:CDdlprov:Exiting GetVdid(). return(0)
2013/4/27 16:22:38:1860:CDdlprov:GetDevInfo - newDevName \\?\PhysicalDrive1
2013/4/27 16:22:38:1860:CDdlprov:GetUdid gDMPSA=FALSE
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - newDevName \\?\PhysicalDrive2
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - vdid_get() er=(1005).
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - In VDID_MAY_NOT_BE_UNIQUE case.
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - vdid_get() failed err(1005).
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - Internal Disk. Device name used as Disk vdid \\?\PhysicalDrive2@domain.hostname.
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - it is a internal array.
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - With fullname of Computer, Enclosure vdid DISKS@domain.hostname.
2013/4/27 16:22:38:1860:CDdlprov:GetVdid - CreateEnclousreObject
2013/4/27 16:22:38:1860:CDdlprov:CreateEnclosureObject entered - vdid DISKS@domain.hostname, internal 1, correlatable 0.
2013/4/27 16:22:38:1860:CDdlprov:CreateEnclosureObject enclosure is found with given vdid
2013/4/27 16:22:38:1860:CDdlprov:Exiting GetVdid(). return(0)
2013/4/27 16:22:38:1860:CDdlprov:GetDevInfo - newDevName \\?\PhysicalDrive2

-----------------------------------------------------------------------------

MPIO_DISK_INFO

-----------------------------------------------------------------------------
    InstanceName* = "Root\MPIO\0000_0"
    NumberDrives = 0x2
    DriveInfo =
      instance of MPIO_DRIVE_INFO {
        NumberPaths = 0x2
        Name = "MPIO Disk0"
        SerialNumber = "FUJITSU E4000C7D0094"
        DsmName = "Veritas FUJITSU ACTIVE/ACTIVE DSM - VFUJITSUAA"
       }
      instance of MPIO_DRIVE_INFO {
        NumberPaths = 0x2
        Name = "MPIO Disk1"
        SerialNumber = "FUJITSU E4000C7D0095"
        DsmName = "Veritas FUJITSU ACTIVE/ACTIVE DSM - VFUJITSUAA"
       }

-----------------------------------------------------------------------------

Operating Systems:

Comments 5 CommentsJump to latest comment

peteryang73's picture

Don't know if the following message in vdid.log file helps.

-----------------------------------------------------------------------------

04/27/13 16:22:38 :1860:vdid_main.c:E_ vdid_initialize_with_paths

04/27/13 16:22:38 :1860:hp.c:E_vendor_init

04/27/13 16:22:38 :1860:hp.c: PID LOGICAL VOLUME is not Supported by VDID yet.

04/27/13 16:22:38 :1860:hp.c:Failed to Collect Extended attributes. vdid_err 1903

04/27/13 16:22:38 :1860:hp.c: PID LOGICAL VOLUME is not Supported by VDID yet.

04/27/13 16:22:38 :1860:hp.c:Failed to Collect Extended attributes. vdid_err 1903

Marianne's picture

Have you added the Fujitsu DMP Device SpecificModule (DSM) during SFW installation?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

peteryang73's picture

Hi Marianne,

Yes, we have added the Fujitsu DMP Device SpecificModule (DSM) during SFW installation. Thus DsmName displays "Veritas FUJITSU ACTIVE/ACTIVE DSM - VFUJITSUAA".

 

 

peteryang73's picture

vdid_get() failed err(1005)

1005 = VDID_ERR_LIB_SYMBOL_FAILED

vdid_err 1903

1903 VDID_ERR_NOT_SUFFICIENT_SCSI_INFO

 

 

peteryang73's picture

Symantec engineering answered that we don’t have support for Fujistu arrays in VDID libraries, it is expected to gather all Fujitsu disks under common enclosure named Disks@Hostname.

Other thing is the meaning of err 1005 within vdid_get() failed err(1005) is VDID library for given array disk is not supported.

Anyway, It will not affect TP if supported.

SOLUTION