[Veritas-vx] Drive type unknown Solaris 10

2007-09-04 Thread James Kelty
Hey there,

I'm running Veritas Storage Foundation HA Standard, v4.1 on Solaris 10 (x64), 
and I'm having a bit of an issue with 'drive type unknown' coming up on the 
Solaris format command.

I have two Qlogic QLE220 (PCI Express 4Gb HBA) hooked up to an HDS WMS100 with 
the latest ASL/APM installed. 

bash-3.00# pkginfo | grep VRTS
system  VRTSHDS-DF600-apmArray Policy Module for HITACHI 
DF600(9500 and AMS-WMS) Arrays.
system  VRTSHDS-DF600-aslArray Support Library for HITACHI 
DF600(9500 and AMS-WMS) Arrays.

vxddladm is showing the supported share object:
bash-3.00# vxddladm listsupport | grep vxhdsasl
libvxhdsasl.so   HITACHIDF600, DF600-V, DF600F  


vxdmpadm is showing the two active paths I would expect to see:
bash-3.00# vxdmpadm getdmpnode enclosure=AMS_WMS0
NAME STATE ENCLR-TYPE   PATHS  ENBL  DSBL  ENCLR-NAME
=
c4t0d5s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d2s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d6s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d1s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d4s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d7s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d0s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d3s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d8s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d11s2ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d10s2ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d9s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d12s2ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d13s2ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d14s2ENABLED  AMS_WMS  2  2 0 AMS_WMS0

vxdisk show the disks as online in the correct group (the last three are the 
I/O fencing disks):
bash-3.00# vxdisk list
DEVICE   TYPEDISK GROUPSTATUS
c2t0d0s2 auto:none   --online invalid
c3t0d0s2 auto:none   --online invalid
c4t0d0s2 auto:cdsdiskd400 mucho_grponline
c4t0d1s2 auto:cdsdiskd401 mucho_grponline
c4t0d2s2 auto:cdsdiskd402 mucho_grponline
c4t0d3s2 auto:cdsdiskd403 mucho_grponline
c4t0d4s2 auto:cdsdiskd404 mucho_grponline
c4t0d5s2 auto:cdsdiskd405 mucho_grponline
c4t0d6s2 auto:cdsdiskd406 mucho_grponline
c4t0d7s2 auto:cdsdiskd407 mucho_grponline
c4t0d8s2 auto:cdsdiskd408 mucho_grponline
c4t0d9s2 auto:cdsdiskd409 mucho_grponline
c4t0d10s2auto:cdsdiskd410 mucho_grponline
c4t0d11s2auto:cdsdiskd411 mucho_grponline
c4t0d12s2auto:cdsdisk--online
c4t0d13s2auto:cdsdisk--online
c4t0d14s2auto:cdsdisk--online


I'm not having any I/O issues to the drives so far, but for some reason the 
format command is giving me grief about 'drive type unknown' for _some_ of the 
drives:
AVAILABLE DISK SELECTIONS:
   0. c2d0 DEFAULT cyl 30391 alt 2 hd 255 sec 63
  /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL 
PROTECTED],0
   1. c3d0 DEFAULT cyl 30397 alt 2 hd 255 sec 63
  /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL 
PROTECTED],0
   2. c4t0d0 DEFAULT cyl 48951 alt 2 hd 255 sec 126
  /[EMAIL PROTECTED],0/pci10de,[EMAIL PROTECTED]/pci1077,[EMAIL 
PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0
   3. c4t0d1 drive type unknown
  /[EMAIL PROTECTED],0/pci10de,[EMAIL PROTECTED]/pci1077,[EMAIL 
PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],1
   4. c4t0d2 DEFAULT cyl 48951 alt 2 hd 255 sec 126
  /[EMAIL PROTECTED],0/pci10de,[EMAIL PROTECTED]/pci1077,[EMAIL 
PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],2
   5. c4t0d3 drive type unknown
  /[EMAIL PROTECTED],0/pci10de,[EMAIL PROTECTED]/pci1077,[EMAIL 
PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],3
   6. c4t0d4 DEFAULT cyl 48951 alt 2 hd 255 sec 126
  /[EMAIL PROTECTED],0/pci10de,[EMAIL PROTECTED]/pci1077,[EMAIL 
PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],4
   7. c4t0d5 drive type unknown
  /[EMAIL PROTECTED],0/pci10de,[EMAIL PROTECTED]/pci1077,[EMAIL 
PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],5
   8. c4t0d6 DEFAULT cyl 48951 alt 2 hd 255 sec 126
  /[EMAIL 

Re: [Veritas-vx] Drive type unknown Solaris 10

2007-09-04 Thread Myers, Mike
I don't know the Hitachi array, but I'll bet it's active/passive with explicit 
failover (or something similarly named from Hitachi).

We have this issue with our Clariion's.  We connect them thus:

SP = Service Processor
SW = fiber switch (actually director)
HBA = host bus adaptor

SPA   SPB
| \   / |
|  \ /  |
|   \   |
|  / \  |
| /   \ |
SW1   SW2
|   |
|   |
HBA1 HBA2

The individual LUN's are presented to one SP as primary and the other as 
fail over, thus if you have a LUN that's been assigned to SPA as primary and 
SPB as the failover, you end up with the following paths to the same LUN:

HBA1 - SW1 - SPA (primary)
HBA1 - SW1 - SPB (failover)
HBA2 - SW2 - SPA (primary)
HBA2 - SW2 - SPB (failover)

In explicit failover mode you can do some base operations to the LUN on the 
failover interface (such as answer a SCSI INQUIRY command) but more complex 
operations (such as real I/O) will fail until a special bring it over here 
command is sent (this would be an explicit request to failover the LUN -- thus 
explicit failover).  The volume manager will issue such as request when it 
has no remaining primary I/O paths to the device.

So the short answer is: if you have your ASL's and/or APM's installed for this 
model of array, you should be able to do something like vxdisk list any 
device and see that, from the VM perspective, things are working properly.  
Something like this:

Multipathing information:
numpaths:   4
c2t5006016139A02131d5s2 state=enabled   type=primary
c3t5006016839A02131d5s2 state=enabled   type=secondary
c2t5006016939A02131d5s2 state=enabled   type=secondary
c3t5006016039A02131d5s2 state=enabled   type=primary

Hope that helps -- and I hope it's your problem.  I know this took a few 
minutes to understand when we moved from parallel disconnected SAN's for 
redundancy to interconnected like this, but it's the right thing to do. (I 
think...)

Cheers,
 - Mike.Myers at nwdc.net
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Kelty
Sent: Tuesday, September 04, 2007 1:26 PM
To: veritas-vx@mailman.eng.auburn.edu
Subject: [Veritas-vx] Drive type unknown Solaris 10

Hey there,

I'm running Veritas Storage Foundation HA Standard, v4.1 on Solaris 10 (x64), 
and I'm having a bit of an issue with 'drive type unknown' coming up on the 
Solaris format command.

I have two Qlogic QLE220 (PCI Express 4Gb HBA) hooked up to an HDS WMS100 with 
the latest ASL/APM installed.

bash-3.00# pkginfo | grep VRTS
system  VRTSHDS-DF600-apmArray Policy Module for HITACHI 
DF600(9500 and AMS-WMS) Arrays.
system  VRTSHDS-DF600-aslArray Support Library for HITACHI 
DF600(9500 and AMS-WMS) Arrays.

vxddladm is showing the supported share object:
bash-3.00# vxddladm listsupport | grep vxhdsasl
libvxhdsasl.so   HITACHIDF600, DF600-V, DF600F

vxdmpadm is showing the two active paths I would expect to see:
bash-3.00# vxdmpadm getdmpnode enclosure=AMS_WMS0
NAME STATE ENCLR-TYPE   PATHS  ENBL  DSBL  ENCLR-NAME
=
c4t0d5s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d2s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d6s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d1s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d4s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d7s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d0s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d3s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d8s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d11s2ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d10s2ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d9s2 ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d12s2ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d13s2ENABLED  AMS_WMS  2  2 0 AMS_WMS0
c4t0d14s2ENABLED  AMS_WMS  2  2 0 AMS_WMS0

vxdisk show the disks as online in the correct group (the last three are the 
I/O fencing disks):
bash-3.00# vxdisk list
DEVICE   TYPEDISK GROUPSTATUS
c2t0d0s2 auto:none   --online invalid
c3t0d0s2 auto:none   --online invalid
c4t0d0s2 auto:cdsdiskd400 mucho_grponline
c4t0d1s2 auto:cdsdiskd401 mucho_grponline
c4t0d2s2 auto:cdsdiskd402 mucho_grponline
c4t0d3s2 auto:cdsdiskd403 mucho_grponline
c4t0d4s2 auto:cdsdiskd404 mucho_grponline
c4t0d5s2 auto:cdsdisk  

Re: [Veritas-vx] Drive type unknown Solaris 10

2007-09-04 Thread Darren Dunham
 HBA1 - SW1 - SPA (primary)
 HBA1 - SW1 - SPB (failover)
 HBA2 - SW2 - SPA (primary)
 HBA2 - SW2 - SPB (failover)
 
 In explicit failover mode you can do some base operations to the LUN
 on the failover interface (such as answer a SCSI INQUIRY command) but
 more complex operations (such as real I/O) will fail until a special
 bring it over here command is sent (this would be an explicit
 request to failover the LUN -- thus explicit failover).  The volume
 manager will issue such as request when it has no remaining primary
 I/O paths to the device.

Exactly.  Since the logic of this is in the ASL/APM and available only
to VxVM, 'format' and the lower layers don't get the benefit.

-- 
Darren Dunham   [EMAIL PROTECTED]
Senior Technical Consultant TAOShttp://www.taos.com/
Got some Dr Pepper?   San Francisco, CA bay area
  This line left intentionally blank to confuse you. 
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx


Re: [Veritas-vx] Drive type unknown Solaris 10

2007-09-04 Thread Darren Dunham
 Does this make the 'format' command output more of an aesthetic 'issue'. A 
 red herring, in other words?

The 'format' command is trying to read the disk label to present the
information in it to you in the list.

If the label can't be read, you'll get the 'drive type unknown'
messages.  'format' is trying to read every path, valid or not.
'vxdisk' will instead understand the topology and only try to read
through primary paths unless a failure is detected.

-- 
Darren Dunham   [EMAIL PROTECTED]
Senior Technical Consultant TAOShttp://www.taos.com/
Got some Dr Pepper?   San Francisco, CA bay area
  This line left intentionally blank to confuse you. 
___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx


Re: [Veritas-vx] SF 5.0 and iSCSI?

2007-09-04 Thread Hudes, Dana
What I'd find useful is an iSCSI target so that I can take LUNs from the
Hitachi on the FC and export them to other machines. Or even better,
take a 3500 with 4GB of RAM and 4 5200 arrays and make it export iSCSI
targets across our private LAN.

 

=

Dana Hudes

UNIX and Imaging group

NYC-HRA MIS

+1 718 510 8586

Nextel:  172*26*16684

=

-Original Message-
From: Mike Root [mailto:[EMAIL PROTECTED] 
Sent: Friday, August 31, 2007 4:04 PM
To: Hudes, Dana; vxtrouble; veritas-vx@mailman.eng.auburn.edu
Subject: RE: [Veritas-vx] SF 5.0 and iSCSI?

 

In iSCSI, the target is the place where the data is and the initiator is
the thing that wants to read/write the data. In a simple setup the OS
would have a iSCSI initiator and the storage array would have an iSCSI
target. The application could then access the storage in the array
through the iSCSI connection between the initiator and the target.

 

In Sol 10, the OS has an iSCSI initiator that can connect to iSCSI
targets and present the LUNs as SCSI devices that SF5.0 can interact
with like any other SCSI device.

 

If somebody want to flip it around and put a iSCSI target on top of a
VxVM volume. I know it has been done with an open source iSCSI target
that comes with SUSE10

Mike Root
Sr. Principal Software Engineer
Veritas Storage Foundation
Symantec Corporation
www.symantec.com

 

 


  _  


From: Hudes, Dana [mailto:[EMAIL PROTECTED] 
Sent: Friday, August 31, 2007 11:47 AM
To: Mike Root; vxtrouble; veritas-vx@mailman.eng.auburn.edu
Subject: RE: [Veritas-vx] SF 5.0 and iSCSI?

This is interesting. Would this include exporting iSCSI, I believe
that's called an initiator? Solaris 10 has some support for I believe
its iSCSI targets but not initiators.

 

=

Dana Hudes

UNIX and Imaging group

NYC-HRA MIS

+1 718 510 8586

Nextel:  172*26*16684

=

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Root
Sent: Friday, August 31, 2007 1:12 PM
To: vxtrouble; veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] SF 5.0 and iSCSI?

 

You should find that if you connect an iSCSI device then Storage
Foundation will recognize it and let you use it. You'll be able to do
all the wonderful things you can do with FC devices.

 

You can talk to your sales rep if you have an interest in a specific
array. You may have to wait until 5.0mp3 for official support.

 

Mike Root
Sr. Principal Software Engineer
Veritas Storage Foundation
Symantec Corporation
www.symantec.com

 

 


  _  


From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
vxtrouble
Sent: Friday, August 03, 2007 8:17 AM
To: veritas-vx@mailman.eng.auburn.edu
Subject: [Veritas-vx] SF 5.0 and iSCSI?

Can anyone confirm if SF 5.0 (Solaris 10) supports iSCSI.  I think the
answer is no  according to the HCL but just want to confirm.

Thanks! 


  _  


Looking for a deal? Find
http://us.rd.yahoo.com/evt=47094/*http:/farechase.yahoo.com/;_ylc=X3oDM
TFicDJoNDllBF9TAzk3NDA3NTg5BHBvcwMxMwRzZWMDZ3JvdXBzBHNsawNlbWFpbC1uY20-
great prices on flights and hotels with Yahoo! FareChase.

___
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx