Hi Subhajit,
Are you trying to say that it is mandatory to have tiering licence to use SSD and HDD in same box.
Mulesh
Hi Subhajit,
Are you trying to say that it is mandatory to have tiering licence to use SSD and HDD in same box.
Mulesh
Unfortunately (and this is dangerous for a pre-sales) the MSA QuickSpecs document does not talk about this limitation.
When you go to configure a storage on OCA tool it gives an orange warning - not red.
Thanks for this warning.
Can someone help me with following VMware integration for MSA 2050 and MSA 2060
MSA 2050 - VAAI
MSA 2060 - VAAI
MSA 2050 - VASA and create vVOL
MSA 2060 - VASA and create vVOL
Thanks
As per my understanding it's mentioned in Quickspec as below,
https://h20195.www2.hpe.com/v2/getdocument.aspx?docname=a00008276enw (page no 7)
"Configurations which have a mixture of both SSDs and HDDs within the same system being used as a capacity Tier (excluding SSD Read Cache), will require the Advanced Data Service Suite LTU. This rule applies to the system level and therefore the license is required regardless of whether the drives are configured for auto-tiering within the same Pool. All SSD configurations and SSD Read Cache extension do not require a license on the MSA2050 array."
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************
You can download this document and look for section "VAAI integration" (page no 48 onwards)
https://pdf4pro.com/cdn/hpe-msa-storage-configuration-and-best-practices-for-464961.pdf
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************
can you please explian to me how much space i have right now and i can create volume from
A B
Need some information,
>> MSA model and controller firmware version
>> Each pool how many Virtual Disk Group(VDG) present and what are the size details of each VDG.
>> You have mentioned 7 volumes in Pool A and 9 volumes in Pool B but not mentioned thin provision size of each volume.
Try to provide actual screenshot of Pool usage, VDG and Volume usage from SMU. Also below command outputs,
show pools
show disk-groups pool A
show volumes pool A
show disk-groups pool B
show volumes pool B
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************
disk management didn't show the MSA disks at all. however they do show in the storage pool of File and Storage Services.
as there was only one storage pool created the MSA disks automatically added to that storage pool. this caused a problem because the virtual disks that were shared across my storage pool cluster re-scanned to accomodate the new space and then became inaccessible to the cluster
.
Now i can't delete the MSA disks from the Pool so have had to delete the volumes, then move the MSA disks to primordial and then start again with the S2D cluster.
thanks for replying. as i want to use the MSA disks as pass through on the hyper V hosts that i'm configuring them on i don't want to set them online here but on the VMs that they are to be attached to. they appear in File and Storage services but not Disk Management
Thanks Sabhajit,
i used the powershell command:
Get-StorageSubSystem Cluster* | Set-StorageHealthSetting -Name "System.Storage.PhysicalDisk.AutoPool.Enabled" -Value False
i gather this stops the pool from auto selecting physical disks.
the MSA disks are now in the primordial pool and are appearing in disk management
i followed your instructions for installing MPIO but still don't get see the MPIO tab on the MSA disk properties.
are there any other steps i need to take under MPIO properties?
We can see that volumes can be seen from disk management which means one part of the issue is resolved now. You can right click and make them online.
Regarding MPIO you can follow instructions from page page 28 onwards,
https://h20195.www2.hpe.com/v2/getpdf.aspx/A00015961ENW.pdf
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS!thumb below!
***********************************************************************
Hi Tom,
What SNMP version are you using? Note that MSA SNMP traps are sent over port 162.
If you're using SNMPv3 this might help: https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=emr_na-a00088574en_us
Cheers,
Dardan
Hi Dardan,
Our monitoring does not recieve traps, so we dont wanne use them.
We just wanna query the snmpd agent on the msa. Is this also possible?
On the monitoring host we tried it with
snmpwalk -c COMMUNTIY -v2c -MSA-IP-
and
snmpwalk -c COMMUNTIY -v1 -MSA-IP-
without luck.
greets Tom
Tried the following against a MSA 2050 (VL270P003-01) and it works:
snmpwalk -r: <IP MSA> -c:"COMMUNITY_STRING" -v:2c -p:161
snmpwalk -r: <IP MSA> -c:"COMMUNITY_STRING" -v:2c
snmpwalk -r: <IP MSA> -c:"COMMUNITY_STRING" -v:1
P.S. Using net-snmp for Windows.
Simple Network Management Protocol (SNMP) is Enabled
Read and Write Community are defined under SNMP section.
Now that the MSA SAS disks are showing in Primordial pool i can recreate the Cluster. i don't want to use the disks in the S2D cluster because S2D doesn't accept them. 'Supported media types are SCM, SSD and HDD.'
However when i run S2D cluster validation i get errors about the SAS disks. and when i create the Cluster and try to enable clusters2d i get errors:
WARNING: 2020/10/22-15:37:07.320 Disk number 7 ({cfaffe09-11d6-a9ba-a69d-55fd1e72d766}, friendly name 'HPE MSA 1050 SAS') on node <server1> has unsupported media type
WARNING: 2020/10/22-15:37:07.321 Disk number 8 ({c948c97e-d566-5166-cbf8-b645882186dd}, friendly name 'HPE MSA 1050 SAS') on node <server1> has unsupported media type
WARNING: 2020/10/22-15:37:07.326 Disk number 7 ({cfaffe09-11d6-a9ba-a69d-55fd1e72d766}, friendly name 'HPE MSA 1050 SAS') on node <server2> has unsupported media type
WARNING: 2020/10/22-15:37:07.327 Disk number 8 ({c948c97e-d566-5166-cbf8-b645882186dd}, friendly name 'HPE MSA 1050 SAS') on node <server2> has unsupported media type
Enable-ClusterS2D : Disk eligibility failed. Review the List All Disks for Storage Spaces Direct test and verify all
disks are of a supported Media Type of SSD or HDD.
please can you tell me how to set the MSA SAS disks so that they are not to be used for S2D?
do i use switches to skip the disk checking or set the MSA disks so they're not available somhow?
Enable-ClusterS2D -CacheMode Disabled -AutoConfig:0 -SkipEligibilityChecks
Not much idea about S2D or Software Defined Storage Solution but you can check below links to get details,
https://h20195.www2.hpe.com/v2/GetPDF.aspx/4AA6-8953ENW.pdf
https://www.reddit.com/r/sysadmin/comments/85tzi9/storage_system_question_hpe_msa_or_storage_spaces/
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************
Hi
I have a msa 60 connected to a sa-P822 controller.
I was wondering if I can get higher data rates than 1.5g,
All of the drives are reported as 1.5g even though the are 3.0 and 6.0 g
according to hpacucli
I have the following firmware
sa p822 Firmware Version: 4.68
Enclosure SEP (Vendor ID HP, Model MSA60) 378
Device Number: 378
Firmware Version: 1.50
WWID: 500110A000CAEEA5
Port: 1E
Box: 1
Vendor ID: HP
Model: MSA60
SEP: (1) 1.50
Backplane Module (BPM): (1) 1.74, (2) 1.74
Fan Control Module (FCM): (1) 1.08, (2) 1.08
Health Monitor Module (HMM): (1) 1.04, (2) 1.04
Seven Segment LED Display: (1) 0.10
Expander 379
Device Number: 379
Firmware Version: 1.50
WWID: 500110A000CAEE80
Port: 1E
Box: 1
Vendor ID: HP
SEP (Vendor ID PMCSIERA, Model SRCv24x6G) 380
Device Number: 380
Firmware Version: RevB
WWID: 50014380283EDF9F
Vendor ID: PMCSIERA
Model: SRCv24x6G
Ideas ? thanks
Thanks for your help Subhajit,
as my initial question has been answered i think that this thread is now at an end.
Hello,
Q1: if I configure all drives into 4 x 10disk-raid6 disk-groupes, and put them all together into the same "virtual pool - Storage A" >> will this virtual pool ( storage A ) be accessed with active/active over both SAS Ports A/B ?
Q2: if i have the above config, is the attached D2700 enclosure accessed over both Controllers A/B, active/active ?
Q3: finally is "storage A" related to Controller/SAS-port A and does only do failover to Controller/SAS-port B in case of error, or are both paths active/active ?
Q4: would there be any benefit from 4 x 10disk-raid6 disk-groupes vs 8 x 6disk-raid6 disk-groupes ( all in one virtual Pool )
Mfg
Norman