Announcing New MSA 2050/2052/1050 Controller firmware!!!
Yesterday we published new controller firmware for the MSA 2050/2052/1050. The new firmware and release notes are now available on the MSA Firmware site (www.hpe.com/storage/MSAFirmware).
VL270R001-01 (MSA 2050/2052)
VE270R001-01 (MSA 1050)
Hi, I have a HP MSA 2040 with a SAS connection on HP DL380 G9 servers running Windows Server 2016 Datacenter and the connectivity between the Windows server and the MSA 2040 is only 6 GB \ s while it should be 12 GB \ s. The two controllers on the MSA 2040 are 12 GB \ s and the 8644 12 GB \ s. On the servers I have HP h241 HBA 12 GB \ s cards. But it only works for 6 GB \ s.
Hi guys,
How are you?
I´m configuring a new MSA 2050 but I´m having problems creating the pools. It´s simple, I have 2 x SSD disks and 6 x 1.2 TB SAS.
The objective is to create 2 RAIDs: Raid 1 with SSD and Raid 5 with SAS disks but I can´t because the MSA says that I need a license... (performance Tier License).
I don´t need to create a singles pool with both types of disks, etc I only need to create 2 separate RAIDs.
I´ve been reading that I can do this with linear configuration but When I´m creating a pool I cannot see this option.
How Can I enable / configure this 2 independent RAIDs?
Thanks a lot for your help.
Hi,
my receller said to me to buy a P431 controller to connect my DL360P G8 with my MSA 1050 SAS. On the MSA 1050 i see the link is ok with controller, the connector led is on, the initiator is mapped with volumes. Everything looks ok but the P431 doesn't see anything.
I use VMWare 6.7 and modify with ssacli the P431 to enable HBA mode but no more success.
My MSA 1050 works fine with another server DL360 G9 with H241 controller
An idea ? Thank's
Do the model HPE MSA 2050 compatible with D3600 base enclosure ??
Do the Model HPE MSA 2050 support D 3600 Base enclosure??
I have a Proliant dl180 G6 with a P812 Smart Controller showing 4 logical devices, running Windows 2008 R2. I have three HP Storagework D2600 disk Enclosures attached to it.
Enclosure A) 12 x 2TB SATA Drives
Enclosure B) 12 x 2TB SATA Drives
Enclosure C) 12 x 2TB SAS Drives
I would like to decommission enclosure B. You'd think it would be a simple matter. I've decommisioned enclosures on other servers without a problem. On this server I'm getting a strange result. When I remove enclosure B from service and bring up the server, the controller, it shows 0 logical drives instead of 3 logical drives. If I go back to the original setup, I get 4 logical drives. When I leave the enclosure B connected and disconnected another enclosure (as a test), the controller shows 0 logical drives. None of the logical drives have anything shared between them (ie. hot spare drives). Why is this happening? How can I fix this? I don't want to screw up the other two enclosures. Thanks, in advance.
Kevin
Hello,
My msa2050 has 2 virtual pools , with one disk group each :
1 diskgroup on pool A with 9 x 800Gb SSD's (raid 6)
1 disgroup on pool B with 11 x 12Tb SAS drives. (raid 6)
I have a 12Tb not assigned disk ( just available) that want to use as a spare for pool B diskgroup.
With dynamic sparing ( default i think) , will this disk been used for reconstruction on both diskgroup ?
What is the difference to declare this disk as a global spare ?
I don't want this disk to reconstruct a failure of a drive in the SSD diskgroup.
in other words how can i dedicate this disk to the "B" diskgroup
thank's in advance
Gérard
Hello,
I want to add a seconf SAS diskgroup on an MSA2050 but the system is asking for a performance license.
I have a fist SSD disgroup (says "performance") and i don't want to use tiering
i want to disable automatic tiering. How can this be done ?
thanks in advance.
Gérard
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
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?
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, 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
I had purchased a MSA2012i online. It has some problems but I am looking to see if anyone would have the firmware J212P01 handy to see if it resolves the issue I am running into. Any help would be appreciated.
I need remplace st2000nm0011 for seagate ST2000VX008, it's possible?
I have a HP DL380 G8 attached to a HP P2000 G3 10GbE iSCSI MSA Controller.
We want to know if the MSA will support iSCSI connection to a Windows 2012 R2 or 2016 Server? I am having a hard time getting exact info, as I can not find T250P01-01 in here: https://h20272.www2.hpe.com/SPOCK/
Can someone post the link where I can find this info?
DETAILS:
CPLD Version 22
Storage Controller Code Version T250P01-01
Model P2000 G3 iSCSI
Storage Controller CPU Type Intel Tolapai
Part Number AW595B
Hardware Version 53
Revision G
Manufacturing Date 2013-11-08 17:18:45
Hello All,
We are trying to configure direct attached scheme with MSA2050 and two Dell server.
Models are followin:
Q1J03A: HPE MSA2052 SAN DC SFF Storage
MSA inserted host ports:
C8R25B: HPE MSA 10Gb SR iSCSI SFP 4pk XCVR
Dells are with:
DELL X520DA2: Intel 10 GB , Dual Port Karte, SFP+
We have connected in following way.
A1 and B1 connect to the .srv1 and A2 and B2 connect to the .srv2
Does that scheme wil work.
We have assigned IPs on all ports. I am trying to ping from srv1 IP of A1 or B1 without any success.
Links are shown as UP.
Thank you for any help.
I lost the connection with the controller management via IP. I can log in, but I do not see any data or technical disks, or the logical or physical structure of the regiments. Nothing.
When I want to perform some operation via the web panel, I have the following message:
"Link veryfication failed
The Storage Controller has been shut down. The current operation is not possible"
I have access to disk drives from hosts for now. I can see the data by the hosts.
Why does not the manager download data from disk shelves?
Hi, We are having some strange issues with an MSA P2000 SAS and VMWare and wondered if somebody had seen similar problems before.
Our environment is as follows:
HP MSA P2000 G3 SAS – firmware TS251P006-02
2 * HP servers used as ESX hosts (ESXi 5.5) directly attached via SAS to the MSA. Each server is connected to each controller.
We initially had a single RAID-5 vdisk, with a single volume provisioned to ESX. This has worked fine for years. The hosting team use thin provisioning at a VMware level. Recently they have had problems as it appeared they had run out of actual capacity due to the thin provisioning. This caused problems with the VM’s as you’d expect. It appeared that this was purely a capacity management issue.
The hosting team worked to free up some space and have managed to get the VM’s on-line. There is now around 400GB free in the datastore according to VMWare however they are still seeing disk capacity issues when trying to provision VM’s. We assumed this was a problem with VMWare not freeing up the now unused thin provisioned space…. However ..
In the background, an additional 4 disks were purchased to allow us to create a new vdisk and present additional capacity to VMWare. We took the decision to create a new RAID-5 Vdisk rather than to extend the existing one as it seemed like the safer option. The vdisk was created and a single volume presented to the ESX hosts (roughly 1.3TB). The ESX hosts detected the volume and a datastore was created all without issue. We assumed our job was done. Unfortunately even though the datastore was created without issue, the hosting team are unable to migrate any VM’s to it. Migrations will start and then fail with an ‘insufficient disk space’ error.
Maybe coincidentally, on the day the majority of the issues started, the Compact flash card was replaced in one of the MSA controllers due to a failure. Since the Compact Flash card replacement, the array is up and healthy.
We have tried the following:
Migrating VM’s from the old datastore to the new.
Creating new thick provisioned VM’s on the new datastore.
Creating new thin provisioned VM’s on the new datastore.
Rebooted each of the MSA controllers one at a time (to avoid an outage rather than a whole array reboot).
Rebooted both ESX hosts.
Disabled VAAI within ESX (the HP specific VAAI plug-in doesn’t seem to be installed)
Provisioned a smaller volume.
Created the datastore as VMFS3 rather than VMFS5.
Logged into the ESX hosts via SSH and tried to copy into the new datastore.
During all testing we get some data copied and then the ‘insufficient disk space’ or similar error. The amount of data copied seems to vary but it’s never very much.
We are at a loss to understand what could be happening as the system has worked fine for a number of years. We’re not even sure where the problem lies … VMWare/MSA etc. As there is some data that can be copied and the fact that you can create the datastore, it feels like the volume is writeable but maybe the communications is being interupted.
Any help/suggestions would be much appreciated!
Hi All,
Require suppport to copy/migration data between MSA internal disks. From NL drives to new drives.