Unsolved
This post is more than 5 years old
12 Posts
0
2115
HDS high-end as a VPLEX back-end
Hi Everybody!
I would like to ask if anybody dealt with HDS high-end as backend storage for VPLEX. I'm interested in selecting the proper host mode and options for VPLEX host group at the HDS array side.
I would like ask also about an article number 000185137. Unique Write Same primitive. I know that there is an ption on mid-range arrays that looks like a tick for enabling WriteSame. But what about high-end arrays? And maybe someone can tell how to disable this primitives in the storage view on VPLEX?
garyo
89 Posts
1
August 6th, 2014 13:00
Hi Vsevolod,
I can't answer the high-end arrays question, but here are the commands to disable the various primitives for VAAI for a storage-view.
Note: I recommend not disabling these unless absolutely necessary.
VAAI primitives are a property of a storage-view.
Check the properties of each storage-view:
Enable/disable primitives for all existing storage-views:
Or modify a single storage-view (substitute "X" below for cluster-1 or cluster-2):
Enable/disable all new storage-views for the various primitives:
Regards,
Gary
vsevolod1
12 Posts
0
August 6th, 2014 23:00
Hi, Gary!
That's usefull info. Thank you!
vsevolod1
12 Posts
0
August 19th, 2014 08:00
Hi everybody!
I found a list of HMO in VPLEX ProcGen. Could be usefull for someone (see below the copy-paste out there).
The write same primitive is mentioned there only for Midrange HDS systems (AMS\HUS).
Storage array family
Model
Vendor
Product ID
Initiator settings
EMC Symmetrix®
EMC
SYMMETRIX
See “EMC Symmetrix”
EMC CLARiiON®
EMC
CLARIION
See “EMC CLaRiiON”
HDS USP/HPXP
Hitachi
OPEN
Default (Standard)
HDS VSP/HP P9500
Hitachi 9900 series (Lightning)
HDS 9910
Hitachi
OPEN
Default (Standard)
HDS 9960
HDS 9970
HDS 9980
Hitachi USP series (TagmaStore)
HDS TagmaStore NSC55
HDS Tagmastore USP100
HDS TagmaStore USP600
HDS TagmaStore USP1100
Hitachi USP VM series
HDS USP VM
Hitachi AMS 2xxx series
HDS AMS 2100
Hitachi
DF600F
Windows
HDS AMS 2300
HDS AMS 2500
Sun/HDS 99xx series
Hitachi
OPEN
Default (Standard)
IBM DS4700
IBM DS4700
IBM
OPEN-V
Linux
IBM DS8000 series
IBM DS8100
IBM
2107900
Windows 2000/2003
IBM DS8300
IBM SVC
SVC
IBM
2145
Generic
IBM XIV
XIV
IBM
2810XIV
Default (Standard)
3PAR
3PAR
3PARdata
VV
Generic or Generic ALUA (if applicable)
Fujitsu DX8x00, ETERNUS 8000
M1200/M2200
ETERNUS 8000
Fujitsu
E8000
Linux
ETERNUS DX8000
ETERNUS_DX800
HP EVA 4/6/8000, 4/6/8100 and 4/6/8400
HP EVA 4000 AA
HP or COMPAQ
HSV101
Linux
HP EVA 4100 AA
HSV200
HP EVA 4400 AA
HSV300
HP EVA 6000 AA
HSV200
HP EVA 6100 AA
HSV200
HP EVA 6400 AA
HSV400
HP EVA 8000 AA
HSV210
HP EVA 8100 AA
HSV210
HP EVA 8400 AA
HSV450
HP StorageWorks XP 48/128/512/1000/10000/12000/20000/24000
HP XP48
HP or COMPAQ
OPEN
Default (Standard)
HP XP512
HP XP128
HP XP1024
HP XP10000
HP XP12000
HP XP20000
HP XP24000
NetApp FAS/V 3xxx/6xxx series
NETAPP
LUN
Linux
vsevolod1
12 Posts
0
March 24th, 2015 08:00
Hi everybody!
Anyway, KB000185137 looks strange on this question. I have consulted on HDS community and there's realy no HMOs which contol the WRITE_SAME primitives itself on high-end arrays.
Is there any way to check it with engineering if HDS high-end arrays are really affected by the issues with WRITE_SAME?