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 gr
> 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. 'forma
Ok, and since I am directly attached to the array thusly:
HBA1->SPA
HBA2->SPB
with the luns configured in: a,b,a,b,a,b type of LUN ownership, the ASL/APM and
DMP are doing their job accordingly.
Does this make the 'format' command output more of an aesthetic 'issue'. A red
herring, in ot
> 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
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 S
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 install
