veritas confidential storage foundation disk support work in progress
Post on 22-Dec-2015
239 views
TRANSCRIPT
VERITAS Confidential
Storage Foundationdisk support
Work in progressWork in progress
VERITAS Confidential
VERITAS Confidential and Proprietary Information
2
VERITAS contacts
VERITAS Confidential
VERITAS Confidential and Proprietary Information
3
Agenda
• Review– disk array capabilities and roadmaps– host multipathing co-existence– device support methodology– communication vehicles
• Establish common device support priorities– DMP requirements
• Develop action plan to address issues
VERITAS Confidential
Review
Disk array capabilities and roadmaps
VERITAS Confidential
VERITAS Confidential and Proprietary Information
5
DMX Roadmap CX Roadmap
VERITAS Confidential
VERITAS Confidential and Proprietary Information
6IBM Storage Roadmap
VERITAS Confidential
VERITAS Confidential and Proprietary Information
7Hitachi Storage Roadmap
VERITAS Confidential
VERITAS Confidential and Proprietary Information
8
Hitachi resellers
Hitachi RAID300 RAID400 RAID401 RAID450 RAID451 RAID600
HDS 7700E 9960 9910 9980V 9970V TagmaStore USP
HP XP256 XP512 XP48 XP1024 XP128 XP12000
Sun na SE 9960 SE 9910 SE 9980 SE 9970 SE 9990
SANRise 2800 2200 9980V 9970V
Nihon UnisysSANARENA
2800 2200
Hitachi DF350 DF400 DF500 DF600 DF700
HDS 5700 5800 9200 9500V TagmaStore DF700
SANRise 9500VNihon UnisysSANARENA
1100, 1200 1500
WFM/EOL
Ligh
tnin
gT
hund
er
VERITAS Confidential
VERITAS Confidential and Proprietary Information
9HP Storage Roadmap
VERITAS Confidential
VERITAS Confidential and Proprietary Information
11
Family / Model Availability WFM EOL A/A A/P failover PGR iSCSI Notes
StorEdge 9990 Sept 2004 Y not applicable Y planned
StorEdge 9900V/9900 Y not applicable Y N 1
6900 N Auto, Explicit Y N 2
6130 11/2004 N Auto, Explicit Y N 8
6x20 (T4), T3+, 3900 N Auto, Explicit Y N 3
35xx (Dot Hill rebrand) N Auto, Explicit Y N 5
T3 Enterprise Yes N Auto, Explicit N N
A5200/A5100 (Photon) JBOD not applicable N N 6
Sun
Sto
rage
Roa
dmap
VERITAS Confidential
VERITAS Confidential and Proprietary Information
12
VERITAS Confidential
VERITAS Confidential and Proprietary Information
13
FLX280
FLA200/FLA300 FC
FLC200 SATA
FLC250 ATA Blade
FlexLineTM- A Continuum of Disk Solutions
Enterprise Mainframe & Co-
located Environments
Enterprise & Large Workgroup
Open Systems
Workgroup & Departmental
Open Systems
Arrays
Solid PerformanceSecondary disk, Online archive, JBOD & RAIDAccess and Capacity
High PerformanceModular/Scalable
Heterogeneous (Open)High Redundancy
RVM and SnapshotAccess and Capacity
Virtual Disk• Instant SnapShot• PPRCHeterogeneous (MVS/Open)
Fea
ture
s &
Fu
nct
ion
alit
y
FLX 680/640
FLX240
FLX210
FLX SVA Virtual Series
VERITAS Confidential
VERITAS Confidential and Proprietary Information
14
LSI Logic/Engenio Roadmap
VERITAS Confidential
VERITAS Confidential and Proprietary Information
15
LSI Logic (Engenio) resellers
LSI “VAIL” E2400 E2600 E4400 E4600 E5600
IBM* DS4100 na DS4300 na DS4400 DS4500
IBM FAStT100 FAStT200 FAStT600/T FAStT500 FAStT700 FAStT900
STK** FLX210 na na/FLX240 na na FLX280
STK B210 D173 D220, B220, /D240
D176 D178,BC84, B250
D280, B280
SGI na TP9300 TP9400v1 TP9400v2 TP9500
Teradata
*FAStT series renamed to DS4000 series; low-end arrays DS400(FC) and DS300(iSCSI) are not sourced from Engenio.
**OPENstorage D-series and BladeStore B-series renamed to FlexLine series
Department Mid-range Enterprise
VERITAS Confidential
VERITAS Confidential and Proprietary Information
16
VERITAS Confidential
VERITAS Confidential and Proprietary Information
17
VERITAS Confidential
VERITAS Confidential and Proprietary Information
18
VERITAS Confidential
VERITAS Confidential and Proprietary Information
19
Other disks
VERITAS Confidential
VERITAS Confidential and Proprietary Information
20
China vendors
What is necessary to support the market in China?
•
•
•
LangChou
(Legend)
VERITAS Confidential
VERITAS Confidential and Proprietary Information
21
Virtual disk arrays
VERITAS Confidential
VERITAS Confidential and Proprietary Information
22
Tier 1 disk support by VSF platform
Current HCLs as of July 2004Red circle indicates support for enterprise, modular, both, or neither. White center indicates support for IBM SVC.
AxRT 1.2HxRT 3.5U2SxRT 4.0 LxRT 2.2 MP1/MP2 WxRT 4.1 VSFN 1.1
Also Sun Not Sun Not Sun
Platform
StorageTier 1
LxRT 1.0 WxRT 3.1VLUN
backingVLUN
FP1
FP1
FP1
Not Hi-Endfor MP2
2.1 Low3.0 Hi/LowSLES – NoHP or Sun
VERITAS Confidential
VERITAS Confidential and Proprietary Information
23
WW disk system revenue market shareDisk Systems$21.5B 2003$25.6B 2008
Internal$7.1B 2003$6.4B 2008
External$14.4B 2003$19.2B 2008
$6,245M (43%) 2003$9,226M (48%) 2008
FC HP, EMC, IBM
$1,559M (11%) 2003$3,114M (16%) 2008
NAS NTAP, EMC
$18.6M (0.1%) 2003$2,691M (14%) 2008
iSCSI NTAP, EMC
$5,863M (41%) 2003$3,566M (19%) 2008
DAS HP, IBM, HIT
36%44%Windows
HP, EMC, Dell
4%34%Linux
HP, Dell, EMC
44%34%Unix
EMC, HP, IBM
Always supported
Not on HCL
IDC #31663, Aug 2004
5%
30%4%
10%
39%
Not supported
Minor exceptionson Solaris, HPUX
12%
VERITAS Confidential
VERITAS Confidential and Proprietary Information
24
2003 worldwide external disk revenue market share by server OS Windows $5,257M Unix $6,339M Linux $523M
IDC #31663, Aug 2004
HP
EMC
Dell
IBM
HP
EMC
Sun
IBM
HP
EMC
Dell
IBM
VERITAS Confidential
VERITAS Confidential and Proprietary Information
25
WW external disk by price bandWindows $5,257M Unix $5,928M Linux $497M
IDC #31663, Aug 2004
VERITAS Confidential
VERITAS Confidential and Proprietary Information
26
iSCSI market
Application Server
DiskStorage
Storage Network
Storage Network
Ethernet
Fibre Channel
Application Server
DiskStorage
Storage Network
Storage Network
Ethernet
Ethernet
Gateway iSCSI Native iSCSI
2003 $ Share:
NTAP 51%EMC 34%
Cisco Catalyst
iSCSIFC
iSCSI initiators(SW and HW)
2003 $ Share:
HP 30%EMC/Dell 25%/6%IBM 15%Hitachi 8%Sun 7%
VERITAS Confidential
VERITAS Confidential and Proprietary Information
27
iSCSI disk support• What is our iSCSI strategy?
– Important for Windows; interesting for Unix/Linux.• What is our partners’ iSCSI strategies?
– Key to NTAP. All major disk vendors offer iSCSI interface to their disk arrays. Also startups (see below).
• Also refer to Windows WHQL qualification and HCL
• iSCSI offerings:– http://iwww.veritas.com/engineering/NVM/requirements/PM/iSCSI%20Vendors.doc
• Example iSCSI gateways:– Cisco MDS 9000 IPS-4, IPS-8, MSM-14+2, 9216i– Cisco SN 5400 / HP 2122– Crossroads Network Storage Controller– McDATA/Nishan Eclipse 1620, IPS 4300, IPS 3300
• Example iSCSI native disk arrays:– Network Appliance FAS900, F800, FAS200, R200– EMC DMX, Celerra, NS Gateway, AX100 (iSCSI future)– IBM TotalStorage DS300– HP MSA1500 cs– Hitachi TagmaStore (iSCSI future)– NEC FS110G includes FalconStor IPStor on iStorage models S1300/S2300/S1200/S2200– Equalogic PeerStorage Array 100E– Intransa IP5000 Storage System– Lefthand Networks Network Storage Module 100– Adaptec Snap Server 18000– Nimbus Data Systems IPS-500, IPS-1000
VERITAS Confidential
VERITAS Confidential and Proprietary Information
28
Network-attached storage• What is our NAS strategy?• NAS Gateways
– EMC Celerra Clustered Network Server (CNS)– Hitachi Lightning NAS blade– Network Appliance gFiler
• Not interesting to use with NTAP storage since already has NAS– HDS NetApp Enterprise NAS Gateways, TagmaStore– Windows-based NAS with iSCSI targets
• NAS Filers and Unified storage (NAS/iSCSI/FCP)– EMC NS700, NS700G, NetWin– Network Appliance FAS900, FAS200, F800, RA200– Sun StorEdge 5210 (Sun 3000 disk (Dot Hill) + Procom software)– Adaptec (Snap Appliance)– BlueArc Titan, Si8700, Si8300
• What is our CAS (Content Addressed Storage) strategy?– EMC Centera
VERITAS Confidential
VERITAS Confidential and Proprietary Information
29
Just a Bunch Of Disks
• Are all brands of JBOD supported on all platforms? Yes, but no PGR support.
• Does support change if multi-ported disks?– Yes, DMP is supported
• Examples:– Sun StorEdge “Photon”: 5200, 5100, and 5000– Unisys ESM700 (EMC CLARiiON JBOD)– Adaptec (Eurologic) SANbloc-2
VERITAS Confidential
VERITAS Confidential and Proprietary Information
30
Massive Arrays of Idle Disk
• Should supporting MAID be considered any differently than for any other disk device?– Storage Foundation does not support virtual tape– Perhaps NBU might have more interest for D2D2T
• Examples:– Copan Systems Revolution 200T– Exavio ExaVault Media Storage System – Asaca FIREFLY Digital Virtual Libraries DM
VERITAS Confidential
VERITAS Confidential and Proprietary Information
31
Transport technology implications• Disk controller front-end visible to DMP
– UNIX/Linux/Windows use SCSI command sets• How do you know if a disk supports SCSI-3 or SCSI-2?• VERITAS hardware test (VXFENHDWTST) used to determine SCSI-3 compatibility• VCS and SFO I/O fencing requires SCSI-3. SANVM/VSFN A/P support requires SCSI-3 PGR.
– Fibre Channel (direct, loop, fabric)– Storage Foundation does not support other host wire transports (Parallel SCSI, SSA)
• Do we automatically qualify drives with different drive interconnect technology if the host interconnect was already supported?
– Depends on vendor positioning; usually just a PID change
• Disk controller backend is transparent to DMP– FC-AL, SATA, FATA, SSA
• VERITAS has no plans to support traditional mainframes– ECKD command set over ESCON/FICON? No.– Linux on z/OS supported but none sold and no additional investment being made– Should we test interoperability with FICON/FCP switches?
• Not necessary as we would continue to support properly isolated open systems environments
VERITAS Confidential
Review
Host multipathing co-existence
VERITAS Confidential
VERITAS Confidential and Proprietary Information
33
3rd party host multipathing drivers (TPD)
• TPD support is not a commitment to certify the arrays supported by the TPD nor is it a commitment to support the path management between the TPD and the array
• Independent of VERITAS product releases– Version dependencies
• What is support policy by 3rd party?– Usually 3PD is driven by the partner and we have a common
view of supported environments
• VERITAS supports selective third party driver coexistence based on the business case and the degree of coexistence technically possible
VERITAS Confidential
VERITAS Confidential and Proprietary Information
34
3PD offerings• EMC PowerPath• IBM
– MPIO framework (AIX)– Subsystem Device Driver (ESS, SVC)– Redundant Disk Array Control (RDAC) supports DS4000 (FAStT)
• Microsoft MPIO• Sun StorEdge Traffic Manager (formerly MPxIO)• Hitachi HiCommand Data Link Manager (formerly Dynamic Link Manager)• StorageTek SVA Path™ Manager
– Only if Shared Virtual Array added to MDS 9000 interoperability matrix• HP SecurePath, PVLinks
– (Auto Path XP and Auto Path VA not strategic)• QLogic FC driver failover capability • Emulex MultiPulse failover capability• NEC Storage PathManager• RHEL 4 LVM2 utility (1Q05) will have basic failover
– LxRT DMP should also coexist with PP, SecurePath, QLogic/Emulex drivers
VERITAS Confidential
VERITAS Confidential and Proprietary Information
35
DMP/EMC PowerPath co-existence
• PowerPath is strategic to EMC.• Most popular operating systems are supported.• PowerPath and DMP can be active on the same system but DMP
sees all Powerdevices as single path.• PowerPath 4.x has known DMP coexistence issues with
UxRT/LxRT. Not clear if PP 4.x will run on Windows.• All multipathing is done by PowerPath on HP-UX because
PowerPath sits below DMP.• PP and DMP manage on an enclosure level. Is this true?• Sometimes there are version dependencies so new releases don’t
always work (e.g., PP 4.3 does not coexist with DMP)• Both are supported in a clustered environment (VCS and Oracle
RAC) but there are exceptions (per DMP HCL, e.g., AIX).
VERITAS Confidential
VERITAS Confidential and Proprietary Information
36
EMC PowerPath
VERITAS Confidential
VERITAS Confidential and Proprietary Information
37
DMP/IBM SDD co-existence
• SDD is strategic to IBM• Supports IBM ESS (Shark) and IBM SVC• SDD supports HACMP and MSCS.• SDD and DMP can be active on the same system.
– DMP sees ESS as single path disk so it doesn’t do multipathing
• SDD and DMP cannot manage different ESS from same AIX system– Different enclosures of same array type claimed by MPIO/PCM on AIX
• DMP supports Symmetrix with Oracle RAC on Linux• DMP 4.0 supports A/A (Symm, Shark, Hitachi) with Oracle RAC on
AIX• DMP supports VCS.• DMP can coexist with but is not used by SunCluster
VERITAS Confidential
VERITAS Confidential and Proprietary Information
38
IBM SDD in the storage stack
AIX Linux HP-UX Solaris Windows
VERITAS Confidential
VERITAS Confidential and Proprietary Information
39
DMP/IBM MPIO and RDAC co-existence
• MPIO is IBM’s framework for multipathing applications on AIX (only).• Supports Shark, SVC, EMC, Hitachi, and multi-pathed SCSI• “Predefined” attributes must be installed to remove an array from MPIO
framework. We depend on vendors to continue to ship them. Otherwise we will need to modify ODM to disable MPIO for arrays
• MPIO and DMP can be active on the same system– DMP sees MPIO-managed arrays as single path so it doesn’t do multipathing– But PCM sees multiple paths so if DMP included a PCM our value remains
• Different enclosures of same array type claimed by MPIO/PCM on AIX– MPIO and DMP can manage different array types (on the same AIX system)– MPIO and DMP cannot manage the same array type simultaneously
• Support for DS4000 (FAStT) arrays is not yet folded into MPIO – Redundant Disk Array Control (RDAC) is now owned/maintained by IBM and
only supports DS4000 (no other Engenio variants).– RDAC continues to be the driver for these– RDAC supports Windows, Solaris, AIX, with Linux planned– DMP coexists with RDAC but RDAC presents only a single path to DMP
VERITAS Confidential
VERITAS Confidential and Proprietary Information
40
IBM AIX 5L v5.2 MPIO
PCM = Path Control Module
PPI = PCM Programming Interface
VERITAS Confidential
VERITAS Confidential and Proprietary Information
41
DMP/Hitachi HDLM co-existence• Is product strategic to vendor? No. Renamed with TagmaStore• Supports Solaris, AIX, HP-UX, Linux, Windows
– Coexists with VxVM on Solaris and Windows• Supports TagmaStore, Lightning, Thunder, Sun 9900, XP (HP only)• Supports RAC (all), VCS (Solaris, Linux, Windows), AIX HACMP,
HP-UX MC/ServiceGuard, Linux Bundle Cluster, Windows MSCS• Can they be active on the same system? Unknown• How is DMP functionality impacted? Unknown• What restrictions exist if they are both active? Unknown
– For example, must manage different enclosures Unknown• Are there any version dependencies? Unknown• Are there any other related known issues? No.• Any other relevant information?
– IBM SVC 1.2 includes DLM for Hitachi Storage.
VERITAS Confidential
VERITAS Confidential and Proprietary Information
42
DMP/Microsoft MPIO co-existence
• Is product strategic to vendor? Yes.• Should SFW install MPIO DSM or legacy DMP code?• What hosts/devices are supported?• Can they be active on the same system?• How is DMP functionality impacted?• What restrictions exist if they are both active?
– For example, must manage different enclosures• Are there any version dependencies?• Are both supported in a clustered environment?• Are there any other related known issues?• Any other relevant information?
VERITAS Confidential
VERITAS Confidential and Proprietary Information
43
Windows storage stack and MPIO
mpdev.sys
mpspfltr
mpio.sys
Port filter driver
Bus driver
Disk driverreplacement
MPIO multipathing drivers(kernel mode)
Device vendor creates a Device-Specific Module (DSM)
Migrate DMP to MPIO DSM modeland qualify WHQL Multipathing HCT
• DMP is not compatible with W2K3 Storport drivers
• iSCSI Initiator compatibility issue
VERITAS Confidential
VERITAS Confidential and Proprietary Information
44
DMP/Sun STMS co-existence
• Is product strategic to vendor?– Alternate Pathing, Sun StorEdge Traffic Manager (MPxIO)
• Supports Solaris, AIX, HP-UX, Red Hat Linux, Windows• Supports Sun StorEdge FC disk arrays:
– T3B, 3510, 6120, 6320, 6910/6960, 6920, 9900
• Can they be active on the same system?• How is DMP functionality impacted?• What restrictions exist if they are both active?
– For example, must manage different enclosures
• Are there any version dependencies?• Are both supported in a clustered environment?• Are there any other related known issues?• Any other relevant information?
VERITAS Confidential
VERITAS Confidential and Proprietary Information
45
DMP/HP SecurePath co-existence
• Is product strategic to vendor?– Auto Path XP and Auto Path VA are not strategic
• EOL 9/03, DSC 12/03, EOS 6/05
– PVLinks?
• What hosts/devices are supported?• Can they be active on the same system?• How is DMP functionality impacted?• What restrictions exist if they are both active?
– For example, must manage different enclosures
• Are there any version dependencies?• Are both supported in a clustered environment?• Are there any other related known issues?• Any other relevant information?
VERITAS Confidential
VERITAS Confidential and Proprietary Information
46
HP Secure Path driver model
VERITAS Confidential
VERITAS Confidential and Proprietary Information
47
DMP/3rd party offering co-existence
• Any other host multipathing offerings that should be considered?
• iSCSI host support• Network-based multipathing
– Required with network-based virtualization for HA– Does this effectively enable LUN level support for
DMP load balancing algorithm specification?– Any benefits by coordinating with host software?– VSFN Host Toolkit to include DMP for VLUNs only?
VERITAS Confidential
VERITAS Confidential and Proprietary Information
48
Coexistence with 3rd party multipathing
DMP
3PD
Solaris HP-UX AIX
3.2 3.5 4.0 4.1 3.2 3.5 4.0 4.1 3.2 3.5 4.0 4.1
EMC PowerPath 3.x SP SP SP BP SP SP SP BP SP SP SP BP
EMC PowerPath 4.x SP SP SP BP SP SP SP BP SP SP SP BP
EMC PowerPath 4.3 XX XX XX XX XX XX XX XX XX XX XX XX
IBM SDD x.x SP SP SP SP SP SP SP SP SP SP SP B3
IBM RDAC x.x SP SP SP SP SP SP SP SP SP SP SP SP
Hitachi HDLM x.x SP SP SP SP ?? ?? ?? ?? ?? ?? ?? ??
Sun STMS (MPxIO) SP SP SP SP SP SP SP SP SP SP SP SP
HP SecurePath ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
XX = Not compatible
SP = VM uses DMP to single path, 3PD provides multipathing
BP = VM uses 3PD for multipathing, bypassing DMP entirely
B3 = VM uses DMP for multipathing, bypassing 3PD entirely
?? = Unknown
VERITAS Confidential
VERITAS Confidential and Proprietary Information
49
Coexistence with 3rd party multipathing
DMP
3PD
Linux Windows Other
?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
EMC PowerPath 3.x ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
EMC PowerPath 4.x ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
IBM SDD x.x ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
IBM RDAC x.x ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
Hitachi HDLM x.x ?? ?? ?? ?? SP SP SP SP ?? ?? ?? ??
Microsoft MPIO ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
RHEL 4 LVM2 utility ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??
XX = Not compatible (DMP is not compatible with W2K3 Storport drivers)
SP = VM uses DMP to single path, 3PD provides multipathing
BP = VM uses 3PD for multipathing, bypassing DMP entirely
B3 = VM uses DMP for multipathing, bypassing 3PD entirely
?? = Unknown
VERITAS Confidential
Review
Device support methodology
VERITAS Confidential
VERITAS Confidential and Proprietary Information
51
Device support design• Unix/Linux
– Array Support Library (ASL)– User space– Written by IHV or written/ported by VERITAS
• What is it, when is it needed/not needed, who develops it• Existing ASLs: http://clab.veritas.com/ASL/index.html• Planned ASLs: ?• Need online method so user can see current list of available ASLs to load?
– Array Policy Module (APM)– Kernel space– Written in conjunction with ASL
• What is it, when is it needed/not needed, who develops it– Relationship between DDL, DMP, ASL, APM– Relationship to Network platform DMP development– Relationship to Windows DMP development
• Windows– Satellite drivers (changed name to ASL since MS wants drivers tested)– MPIO device support modules– Will we support different DMP modes on Windows to reflect support/non-support of
storport.sys driver by different arrays?– Should we re-write some/all DMP code to use a common model?
VERITAS Confidential
VERITAS Confidential and Proprietary Information
52
Multipathing terminologyActive/Active (A/A) Arrays• I/O can be sent down all paths
simultaneously without impact• HP MSA 1000 Asymmetrical A/A mode has
optimal performance on one Storage Processor (SP)
Active/Passive (A/P) Arrays• I/O sent through active ports to avoid
severe performance degradation if sent through passive ports
• Autotrespass SP failover mode swaps active and passive ports automatically if media access through passive port
• Explicit SP failover mode swaps active and passive ports by vendor-specific SCSI command
• Configuration option determines if SP failover swaps ownership of a single LU or all the logical units in a Group
Primary – same physical SP all the timefor a particular LU. It is the default SP towhich a LU was bound when carved out.
Enabled – port may be used for I/O
Active – port actively being used for I/O
Explicit failover
Auto trespass
LUN level LUN Group levelActive/PassiveDMP Support
A/PF A/PG-F(no such arrays)
A/PG (A/PG-C)A/P (A/P-C)
VERITAS Confidential
VERITAS Confidential and Proprietary Information
53
“Ping-Pong”
VLUN LUN
Host DMP
Swap
Swap-back
Auto-trespass/LUN level A/P array support:
• Media access I/O to active port fails so retry to passive port
• Media access I/O to passive port swaps active and passive
VERITAS Confidential
VERITAS Confidential and Proprietary Information
54
Intelligent switch A/P configuration
VLUN Control
Host VSAN Disk VSAN
xP
xP/VO VS/VES
Host DMP
VT2 VT3
VLUN
VLUN PLUN 1
VLUN PLUN 2
Data
Configuration
2
1
Active/Passive Disk Array
PLUN = LU in physical enclosure
VLUN = LU in virtual enclosure
Network DMP
VERITAS Confidential
VERITAS Confidential and Proprietary Information
55
DMP load balancing algorithms
• Balanced path (A/A)– A modified version of this is used by VSFN
• Round robin (A/P-C)• Single active (A/P)• Minimum queue length (JBOD)• Priority (installation-defined load balancing)• Adaptive priority (varying loads, e.g., DB, SAN)
VERITAS Confidential
VERITAS Confidential and Proprietary Information
56
Adding device support• Prerequisites to adding device support in software
– Hardware platform support of device (compatibility list)– A/P disk array controllers must support SCSI-3 PGR– VxPLC Release (Train) Hardware Compatibility Plans policies?
• May device support be added independently of product release schedules?
• Should support for a device be added to all platforms at the same time?– Just Solaris/AIX/HP-UX?– Just UNIX/RHEL/SLES?– Just Host platforms (UNIX/Linux/Windows)?– All platforms (host and network)?
• Quick qualification for devices that vary by SCSI inquiry information– Dell PowerVault (EMC CLARiiON)– IBM FAStT, StorageTek D-series/BladeStore (LSI Logic/Engenio)– Hitachi/HDS/Sun (HP microcode path differs so full testing required).– Impact of SCSI extended copy (third party copy), e.g., Hitachi ecopy on qualification?
• How should we handle requests to support EOL (but still supported) devices?
VERITAS Confidential
VERITAS Confidential and Proprietary Information
57
Proposed disk support policy• When a disk is added to an HCL, it should be added to the HCL for
all host/network platforms– Unless prevented by unresolvable technical issues– Even if such a configuration is not anticipated
• External disk is only supported if it will be added to the HCL– Internal disk is always supported though not on HCL– Direct-Attached Storage (DAS) is rarely supported (not FC)– Should we augment each HCL with a “special situation list” or…– If business case exists to support it “one-off”, add it to the HCL– Is it OK to add a device to an HCL without testing?
• e.g., add HP XP512 (on SxRT/HxRT HCLs) to VSFN 1.1 HCL
• HCLs may be updated anytime– Independent schedule from release trains
VERITAS Confidential
VERITAS Confidential and Proprietary Information
58
End of life policy for device support
• Should we EOL device support?– What is our policy for supporting devices that the hardware
manufacturer no longer supports?– Is code that supports EOL devices problematic for eng./support?
• Proposal:– When a storage device vendor ends support for their device,
VERITAS may choose to announce that support for that device by our products and by technical services will no longer be provided beyond the current VERITAS product release. Support for the device may be removed from future product releases, although the device support code may not actually be removed. Support will not be removed for other devices that share code.
VERITAS Confidential
VERITAS Confidential and Proprietary Information
59
Testing and qualification
• QA verifies software products satisfy marketing claims regarding capabilities and scalability
• Performance lab studies performance and competition
• SWIFT qualifies software products• cLab qualifies hardware products with host stack
– Including software products that virtualize hardware
• VERITAS Integrated Test Automation (VITA) allows Enabled partners to qualify their hardware
VERITAS Confidential
VERITAS Confidential and Proprietary Information
60
What hardware is / is not qualified
• Host adapters– FC HBAs, iSCSI HBAs, TOEs, NICs, other
• Storage devices– Disk, Tape, Optical, SSD, other
• Gateways– SCSI/FC, SSA/FC, iSCSI/FC, other
• Distance extension– FCIP, CWDM SFPs, DWDM, other
VERITAS Confidential
VERITAS Confidential and Proprietary Information
61
What software is / is not qualified
• VERITAS software products– Who determines which mix of products are tested?– Should host stacks be identical (if possible)?
• Non-VERITAS software products– Do we test interoperability with 3rd party software?
• Integration through SNMP traps• Co-existence of GCS/CC with other management software
• Any pro-active activity related to standards?– FAIS, FDMI, SMI-S, …
VERITAS Confidential
VERITAS Confidential and Proprietary Information
62
Device support methodology issues
• Must all devices on prior HCL be re-qualified?• When can devices be removed from an HCL?• Must all supported devices be qualified?• Must VERITAS qualification require:
– Hardware installation at VERITAS?– VERITAS personnel to run the tests?
• What issues inhibit faster/more qualification?• What functions are / are not tested?• What issues are unique to Windows?
VERITAS Confidential
Review
Communication vehicles
VERITAS Confidential
VERITAS Confidential and Proprietary Information
64
Policies, procedures, and HCLs
• How is new device support communicated?• How is removal of device support communicated?• Who writes and reviews the HCL?
– For example, use consistent terminology across HCLs• Where is the procedure to post the HCL?• Where is device support information provided:
– Internally (product operations, technical support)– Externally to our direct sales force, channel partners, customers
• Should the format(s) and/or content of HCLs change?– For example, VSFN host support is not explicit
• How are device support requests handled?• What is missing or should be improved?
VERITAS Confidential
VERITAS Confidential and Proprietary Information
65
Hardware compatibility lists
• Internal links:– http://clab.veritas.com/HCL/index.html– this does not currently include network platforms
• External links:– http://support.veritas.com (compatibility tab)– ftp://ftp.support.veritas.com/pub/support/products/– http://www.veritas.com/Products/van/
VERITAS Confidential
VERITAS Confidential and Proprietary Information
66
Partner compatibility lists
EMC IBM HDS HP
CNTBrocade Cisco McData
Emulex QLogic AMCC (JNI) Agilent
EngenioSun NetApp StorageTek
Microsoft Red Hat SUSE Oracle
VERITAS Confidential
Establish common device support priorities
UNIX train ( )
Windows train ( )
VSFN train ( )
VERITAS Confidential
VERITAS Confidential and Proprietary Information
68
Current device support priorities• Should DMP capabilities be common across platforms?
• Should support for a device be added to all platforms– Within 3 months, or other short period of time, via a patch?– At the next product release, except to resolve customer issues?
• What platform-specific issues should be considered?– Host Platforms
• Sun Solaris, HP HP-UX, IBM AIX, • Red Hat Linux, Novell SUSE Linux• Microsoft Windows
– Network Platforms• Cisco SAN-OS, Brocade XPATH OS, …
– Storage Platforms• xVM as whitebox component
VERITAS Confidential
VERITAS Confidential and Proprietary Information
69
Common device support priorities
• Open platform storage devices– EMC, IBM, HDS, STK, LSI ?
• Platform-specific storage devices– HP, Sun, NTAP, Fujitsu, NEC ?
• Opportunistic – JBOD, MAID, iSCSI, NAS, China vendors ?– Clones and near clones
• SCSI Inquiry• Different code path (e.g., HP XP Series)
VERITAS Confidential
VERITAS Confidential and Proprietary Information
70
DMP requirements
DMP Requirement Detail: http://iwww.veritas.com/engineering/VSFN/requirements/PM/Mammoth%20DMP%20requirements.doc
VERITAS Confidential
VERITAS Confidential and Proprietary Information
71
VERITAS/IBM quid pro quo agreement
• Add VSFN on Shark (later FAStT) and follow-ons HCL– No successful tests on any host platforms to date for Shark HCL – 1 week testing (all host platforms) once outstanding issue fixed
• VSFN needs to survive cable pulls – San Jose continues work 7/28; Tucson will test future releases – Megamouth will replace Shark hardware in IBM lab 2H04
• IBM confirmed Shark HCL will be updated periodically as needed (not frozen)• VERITAS has provided DMP support, including SDD coexistence with SDD, of SVC
on Solaris, AIX, HP-UX, Linux, and Windows• IBM has completed testing of Solaris and AIX and VRTS has added SVC (both
appliance and MDS versions) to these HCLs• Windows tests in progress, HP and Linux tests not yet started• Alliance to re-open dialog regarding multipathing:• SDD (all host platforms) business model is to only support IBM Shark and SVC• MPIO (AIX multipathing framwork) group has not worked with IBM Storage Group• Support configuration with ASM blade in IBM/partner sold MDS chassis
VERITAS Confidential
VERITAS Confidential and Proprietary Information
72
Issues and resolution plan
VERITAS Confidential
VERITAS Confidential and Proprietary Information
73
Issues and resolution plan