Where can I find firmware for older products like MSA2000 or MSA2000G2.
Where can I find firmware for older products like MSA2000 or MSA2000G2.
Good, would it be possible to install a h241 controller on a gen 8 server? in the compatibility matrix is not supported but I need to connect the server to a 1050 msa booth by sas connection
thanks
You haven't mentioned Operating System installed in the server. So if I assume ESX6.5 then H241 is supported with Gen 8 Server which is Compatible with MSA1050. Please find the SPOCK link to get the details,
You can also refer the below forum where it's mentioned that H241 used in Gen 8 server and this is working fine with MSA1050,
https://community.hpe.com/t5/MSA-Storage/DL360pG8-with-P431-and-MSA-1050-SAS/m-p/7015554#M12071
Note: In order to access HPE SPOCK you need HPE Passport login
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS!thumb below!
***********************************************************************************
I have the hp msa 2050, but there is no access to the firmware update due to the absence of the service contract.
Please share direct link to download VL270R001-01 or send firmware to e-mail msa20150@race.ru, Thanks
A contract or warranty is needed, that's the policy.
Hello,
Since you have an MSA2050 you are still under warranty. This means that as long as you link the SN of the chassis to your HPE Support Center profile you will be able to download firmware. There are two very good advisories that will help guide you through this process. Once you have the SN from the array linked to your HPE Support Center profile you will be able to download the firmware.
Here is the advisory posted for the MSA arrays. There are guided steps to help you find the correct SN for your array. https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c05351364
Here are the step-by-step instructions on how to link the SN from your array to your HPE Support Center profile. There are also instructions on how to create an HPE Support Center profile in case you do not have one currently. https://support.hpe.com/hpsc/doc/public/display?docId=c04055475
Hopefully this will help get you to our latest firmware!
I do suggest bookmarking the MSA Firmware page. This page has direct links to the latest firmware and release notes. www.hpe.com/storage/MSAFirmware
Cheers,
Shawn
I've been having the error below on some replication sets between my MSA 2050 storage boxes:
Scheduler: The scheduler was unable to complete the replication. - An internal timeout has occurred. (task: <replication_set>, task type: Replicate)
EVENT ID:#A21489
EVENT CODE:362
EVENT SEVERITY:Error
The two boxes are currently in the same site, replication over iSCSI, replication interval is every 6 hours, they also maintain both primary and secondary volumes' snapshot history. I've also configured snapshots on primary volume. Limit is 10%, low threshold is 75%, limit policy is delete snapshots for both sites.
I've also noticed that unique data for certain volumes'snapshots at times even upto 5GB. Is there something I'm missing? Please help. Thanks.
PS: Noticed from QuickSpecs that there's no mention of deduplication on MSA. Is this by design or an omission in documentation?
Hi BoSsNeX,
I suspect fault with the SAS cable. Kindly check the SAS cable spare part number used to connect between the H241 controller and the MSA2040 SAS controller.
As per quickspecs we should be using following 12G SAS cables for 12G SAS initator.
QuickSpecs : https://h20195.www2.hpe.com/v2/GetPDF.aspx/c04123144
HP External 1.0m (3ft) Mini-SAS HD 4x to Mini-SAS HD 4x Cable 716195-B21
HP External 2.0m (6ft) Mini-SAS HD 4x to Mini-SAS HD 4x Cable 716197-B21
HP External 4.0m (13ft) Mini-SAS HD 4x to Mini-SAS HD 4x Cable 716199-B21
In case issue persist with the above P/N cables, capture AHS report and Store logs from MSA and open ticket with HPE Support.
Hope this helps.
MSA don't support deduplication feature
Coming to your issue which is related to scheduler failure, I would like to know both MSA running with what version of Controller firmware ?
If not in latest then you should consider upgrading Controller firmware to latest version VE270R001-01 which is having many fix related to replication. Please refer the released notes from below link,
There could be space issue as well. We need to check how much is the Virtual Pool size and how many volumes part of it. How much space consumed by each volume. Related to replication two internal snapshots will be there and that also consumes space and it depends upon how "over commit" setting configured.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Hello,
One small correction to note in previous post. If you are running an MSA2050 you should be intalling firmware version VL270R001-01. The VE270R001-01 firmware is used for an MSA1050. The two firmware versions contain the same fixes and enhancements but are meant for two different systems. You can find more information on the issues fixed and enhancements by reviewing the release notes. One quick and easy way to find these is by accessing the following link: https://www.hpe.com/storage/MSAFirmware
As mentioned previously, upgrading first and retest to determine if your issue has been corrected.
Deduplication was never a feature for the MSA arrays. As such, it was not a mistake in omitting this from documentation or QuickSpecs. If you need a system that has this feature you should talk to your HPE Sales representative. HPE has many systems that offer deduplication.
Cheers,
Shawn
Hello, I need Help.
A support Customer has an P2000 which shows an "The status of 'Cache 1' Backup copy power source (batteries) is 'Defective' " error.
So I've proceed to replace the battery. Then Ive Try to boot the Storage with no success. It didn't recognize it's hard disks. So I've returned it's original battery and no error showed.
Many Moths after, Storage shows same error, again I tried to replace it´s Battery with same results (Storage doesn't boot 'cause didn't recognize HDD). But, this time, when I put back it's orginal battery, error didn't disappear.
So, any body can help me to fix this issue?
Hi Subhajit,
Thanks for the reply.
Our firmware version is VL100P001., virtual pool is 7 TB with 10 volumes, with about 4000GB allocated.
Replication errors were related to specifically 2 large volumes (1TB each), even with shortened replication intervals of 1 hour. Replication is set to queue latest, maintain both primary and secondary volume snapshot history.
Snapshot space in secondary system is set to 10% of total space (~700 GB), limit-policy is delete snapshots, mid threshold is 75%.
Any tips to optimize the replication configuration?
Disappointing not to have Dedup, but I suspected it.
Your configuration looks ok but there are many things which actually improve system overall performance which may in turn improve replication as well.
Most important you should always update your MSA all components with latest firmware.
You should utilize both Virtual Pool instead of one Pool.
I hope you are taking advantage of sub-lun auto tier feature as well.
If over commit enabled then 3 internal snapshots will not be full provisioned. So you can save more space. This is important because when you do replication on Thin provisioned volume then only allocated blocks gets copied to another array.
It's important to understand rate of data change and based on that we should set subsequent Replication interval . This is not COW (Cope On Write) technology rather this works with ROW (Redirect On Write) technology
If you are keeping Replication Snap history for each replicated volume then you should consider space consumption, tree structure for those as well. You can keep max 16 replication snap
Refer latest Controller firmware release notes, MSA 2050 best practice white paper and MSA Remote Snap Software White paper to get more tips and suggestion.
Note: MSA is entry level Storage Box and we shouldn't expect Deduplication in this. HPE having other high end Storage box like 3PAR and Nimble where Deduplication available
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Battery is not a replacable part in P2000 series MSA controllers.
Reconfirm the model number / product number of the unit.
Log a case with HPE support team once you have product serial number and model number details.
It seems to be a hardware issue that requires further investigation:
https://support.hpe.com/hpesc/public/home
Hello,
It sounds as if you are replacing the cache battery on the Smart Array card connected to the P2000 array. It has been my experience that you need to be sure the cache battery is new and has not been sitting on a shelf for some time. If the battery has discharged before being installed into the Smart Array you might experience different or unexpected results.
As mentioned previously, if needed you should gather logs from the host (ADU/AHS) and log a case with your product number.
Cheers,
Shawn
Hi, can't find option, web or CLI where add new disk for GroupDisk DG01.
Can you tell me how to add disk to gropu to expand volume.
If no option, then correct solusion remove diskgropu and recreated new one ?
Then deleted all data Storage !!!
Thank's For Help
Daw
Hi Daw,
If you are just adding a new disk group you can do this through either the System Management Utility (SMU) or CLI.
SMU - Pools topic on the left hand tree > Action > Add Disk Group
CLI - # add disk-group type virtual disks 1.17-20 level r6 pool a
However, you are stating that you wish to add the disk-group in order to expand a volume. If you have overcommit on the Pool for the volume you wish to expand disabled, then you can only expand the volume to the the physical capacity of the pool. For example, if Pool A has overcommit disabled and is 100GB your volume V1 can only by 100GB.
To determine whether overcommit is enabled in the CLI issue: # show pools
Be careful in enabling overcommit if it is not enabled currently. To learn more about thin provisioning you can read the MSA SMU Guide. Also, you cannot expand the size of a replication volume.
If you have the physical space to add another disk-group, use either one of the two methods outlined above to add a new disk-group. Once the disk-group has been added, you can then expand a volume, for example volume V1. You will need to issue the following command in the CLI.
CLI - # expand volume size 100GB V1
In case it is needed here are links to our guides.
SMU - https://support.hpe.com/hpsc/doc/public/display?docId=a00017707en_us
CLI - https://support.hpe.com/hpsc/doc/public/display?docId=a00017709en_us
Also, the MSA2050 has a new firmware release, VL270R001-01. I suggest you should upgrade to the latest firmware first before adding disk-groups or volume expansion. If you need a link to the firmware or release notes please access our MSA Firmware here: https://hpe.com/storage/msafirmware
Cheers,
Shawn
Fully agree with Shawn
I just want to add one more thing as you have asked, it's not possible to add new disk to existing Virtual Disk Group in MSA2050. In this array only option to increase space is by addition of new Virtual Disk Groups to existing Pool.
MSA2050 only supports Virtual Array and this is not supporting Linear array like P2000 or MSA2040 where you can add new drive to enhance existing Virtual Disk size.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS!thumb below!
***********************************************************************************