HPE stopped giving firmware/driver free of cost. They modified their policy and according to that if you don't have valid support contract with HPE then you can't download firmware for this device. Please find the link to get more details on this,
https://support.hpe.com/hpsc/doc/public/display?docId=c04055475
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Thank you for your response.
If I connected the units via SAS would'nt VMWare allow me to expand the virtual storage?
Hello,
Your original information indicated the arrays had 10G iSCSI controllers. If this is true then you do not have the ability to add SAS connections between the two arrays. Connecting the two arrays via the backend SAS cables is not supported. This would be similar to connecting two Smart HBAs or Smart Array cards - chaos and not supported.
If you are changing the SAN fabric to SAS, then yes you can connect the two MSA 2040 SAS arrays via a switch. However, we do not have a SAS switch for DL380 G9 servers. We do have SAS switches for c7000 blade enclosures.
Hopefully this clears up any confusion.
Cheers,
Shawn
I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.
Hello,
Please forgive my ignorance as I am fairly new to managing SAN and iSCI devices.
I am currently getting intermitent connection to the LUN and Storage of our P2000 SAN.
Initially our vCentre appliance lost connection to all of the LUNs on the SAN.
A restart of the Management and Storage controllers brought 2 of the 3 LUNs back temporarily but after some time it has dropped off of our vCentre (Shows the LUN but reports 0 disk available and 0 used)
We then shut the storage controllers down and pulled the power on the storage controller which had the same result as above.
. I can ping the address for each of the manaement interfaces and telnet/ssh into each of them. However the storage controller seems to be stuck in a "not read for the operation" state.
Can I get some help in where to look for logs in the system and also if another restart would be worth it?
Hello,
The issue requires in depth log analysis to proceed further.
Log a support case with HPE using the following web link, if the unit is under warranty:
https://support.hpe.com/hpesc/public/home
Log a chat support case with HPE using the following web link to check for options, if the unit is out of warranty:
https://pg-receiver-pro.glb.itcs.hpe.com/WCLWeb/WCLEntry.aspx
If you feel this was helpful please click the KUDOS! thumb below!
i just have serial number and product number but this page want me SAID and SAR . how should i get these? pla help me
Hello,
As mentioned previously, you need to link your array to a service agreement. Once that is done you will have the SAID and SAR.
Cheers,
Shawn
I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.
Hello,
I have a MSA2052 with 2 additional enclousures = 3
It is configured with several disk groups (RAID10) splitted over all 3 enclousures.
When I power off enclousure 2 to simulate a failure, all disk groups become degraded but everything keeps working as expected.
When I now power up enclousure 2 again, the head unit discovers it and states that all disks in this enclousure 2 were previously member of a disk group. See screenshot here: https://imgur.com/a/Ce9o3KV
I was assuming that the MSA detects that these disks belong to the existing disk group and becomes healthy again. But nothing happens ...
Is this assumption wrong? How could I bring back the disk groups to a healthy state?
Thanks
It seems your MSA not having any valid support coverage with HPE otherwise you should know what is Support Agreement ID (SAID) and Support Account Reference (SAR)
You can search your Proof of Purchase (POP) document as well and look for SAID or SAR information if you have bought before and now for some reason misplaced it.
Please find the link and contact HPE sales to buy HPE Support or related service to get SAID or SAR if you don't have it,
https://www.hpe.com/in/en/buy-parts-products.html
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Hello,
You have disk groups that are striped across enclosures. When you power down the enclosure you remove drives from the array. This simulates drive(s) removal.
The array controller stamps each drive with metadata that identifies the drive as belonging to a disk-group, vdisk, pool, etc and adds a time stamp. That time stamp is updated frequently. When you remove an enclosure the remaining drives in a disk-group/vdisk are updated but the removed drives do not get the time stamp update. So when you re-add the enclosure the drives in the enclosure have a time stamp that does not match the existing drives in the disk-group/vdisk. By design the array firmware will mark those drives as belonging to a disk-group/vdisk but in a leftover state if the time stamps are not coherant enough to automatically add back into the original disk-group/vdisk. At this point it is up to the user to take corrective steps.
You can use the Trust command to accept disks back into a disk-group/vdisk. Linear vdisks behave differently than virtual. You should use great caution when using Trust as this can lead to data integrity issues. Please read the MSA Troubleshooting Guide for further instructions and cautions when using Trust: https://support.hpe.com/hpsc/doc/public/display?docId=c05177410
Cheers,
Shawn
I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.
You can try power off complete MSA and take out one controller for few inch. Then power up the MSA by single controller only. If the array come up fine then you can physically insert other controller as well.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Hello,
doesn anyone know **for sure** if the speed of iSCSI 10Gbps is fixed to 10Gbps or autosenging 1/10 ?
thanks in advance
Best regards
Davide
Thanks Shawn for the explanation.
Since all disks are in a Raid 10 and I "lost" 1/3 of the HDDs, I was assuming that this can be easily rebuilt/resynced..?
I could think of clearing the metadata on all the "lost" disks so they become available again and can be set to global spare so the disk groups can be rebuilt from scratch.
But I know that then the rebuild will mix up my pre-defined disk order, means that it will not keep the desired order as I did it on creation, resulting in mixing the disks for Controller A and B. More an optical/clear view thing than an performance issue, I know.
This is how it was setup: https://imgur.com/a/cwRxvhs
first 5 disks belong to Controller A, disk group 2
second 5 disks belong to Controller B disk group 2
last 6 disks belong to Controller A, disk group 3
This is how it will look like when I clear all metadata and the system has done a auto-rebuild: https://imgur.com/a/cvkowQU
This also happens to the two small SSD groups which I didnt colour in the pictures....
How can I get it in the original state so it looks like 3 blocks?
Thanks
As per the User guide it says as below,
https://support.hpe.com/hpsc/doc/public/display?docId=a00017710en_us (Page no 29)
"
The 10GbE iSCSI ports are used in either of two capacities:
• To connect two storage systems through a switch for use of Remote Snap replication.
• For attachment to 10GbE iSCSI hosts directly, or through a switch used for the 10GbE iSCSI traffic.
"
As per the Quickspec it says,
https://h20195.www2.hpe.com/v2/getdocument.aspx?docname=a00008276enw (Page No 12)
"
Fibre Channel results were measured using 16 Gb FC Host Bus Adapters. SAS results were measured using 12 Gb SAS Host Bus Adapters. 10 GbE iSCSI results were measured using 10GbE iSCSI Host Bus Adapters. 1 GbE iSCSI results were measured using 1GbE network interface controllers (NICs). Hosts were directly attached to the HPE MSA 2050 array
"
So all the official information mentioned for 10 GbE only.
10 GbE Controller host ports may work with 1 GbE SAN Switch but this is not recommended or supported so we shouldn't use the same. HPE may not provide support for any issue arise for this type of setup in future.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Since the activation of mail notification I receive the following alert each 1 hour. Managed logs wrapped: A log region has wrapped, and log data has been lost. (region: SC debug, region code: 5)
Steps tested so far:
Transferring log data to a log-collection system
Checked level of set up mail notifications
Managed logs option disabled
Cleared logs
Power cycled the device and reseated all disks
Nothing helps
Any ideas?
Hi,
the problem is that by O365 there is no IP address of mail server. But in the same time such is needed to configure the notifications in SMU.
No, unfortunately I've gotten different answers from the 2 resellers I checked with, but they of course want to sell a unit and drives so...here I am completely confused and ready to scrap $25k worth of existing <2yr old storage and move to another manufacturer...or spend another $25k for additional HPE drivespace that I may not be able to use....
>We have a MSA2040 connected to (2) Netgear XS724EM switches via fiber<
The switches are running Large Frame iSCI over ethernet back to the (3) DL380P Gen9 servers, but the exisating MSA 2040 uses fiber.
I suppose if the existing MSA 2040 is NOT using SAS back to the servers it makes no difference? It would seem you're indicating only 1 connection type can be used, and SAS between controllers (as pictured in both MSA 2040 and MSA 2050 manuals) is not supported because there is an existing fiber connection??
Very dissapointing and frustrating to learn this now, as our purchase decision was based on HPE telling me how easy it was to expand.
Hi SV101,
I see that almost all troubleshooting steps has already been tried.
Please try a firmware update to latest version :
https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_ae8ea19036ea4353b6b87800dc
Chaz ,
As I understand , there are 2 faulty drives (1:6 and 1:13). I would advise to remove these drives if HPE support has told you the same is faulty. MSA Gen2 lets you add 8 spares. You may find this detail in the CLI guide :
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c01755995
(Page : 110)
You could try adding spares via CLI also . Please let me know the error message you can see when trying to add the spares.
Since , I do not have complete details or logs , I have answered this question on best effort basis.
Please share the error message here or you may log a support case with HPE if any issues. We will help you further.
I am an HPE Employee
Hello,
If the managed logs are wrapping this usually indicates some activity is happening on the array that is generating a lot of events. You should look at the events in either SMU or CLI and review what is occurring, You may have a drive that is generating a lot of errors, or a backend cable that is not funcitoning, or a disk-group/vdisk that needs attention.
Once you correct the issue it should help the logs from wrapping. If you can't find the component that is causing the events to occur, then please open a support case with HPE Support using the following web link, if the unit is under warranty: https://support.hpe.com/hpesc/public/home
If the unit is out of warranty, you can open a chat support case with HPE using the following web link to check for options: https://pg-receiver-pro.glb.itcs.hpe.com/WCLWeb/WCLEntry.aspx
Cheers,
Shawn
I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.