Good Day,
We are using an HPE MSA 1040 with the firmware GL225P002. We are also interested in moving to
VSphere 6.5 Upd2.
The VSphere Compatibility guide says this MSA 1040 is good up to VSphere 6.5 Upd1. We want to move it to upd 2 instead.
The HP support rep I mentioned this to on the phone thought it shouldn't be a problem.
Is this idea OK? Or a bad idea?
Thank you,
HRM
Hi There,
There are several items in this forum with the same question but no really solution. I also want to monitor my MSA, in my case with AutoTask Endpoint Management (RMM, AEM).
SNMP is succesfully working. I have searched with SNMP tester, SNMP Walk, etc. I can perform succesfull requests. For example the hostname has OID .1.3.6.1.2.1.1.5.0. Bu I am uanble to find more needed info. The overal Health status, array status, disks, etc. I would like to monitor that.
Another example: OID .1.3.6.1.3.94.1.8.1.6.80.12.15.241.172.246.192.0.0.0.0.0.0.0.0.0.1 gives the value "On-Board Temperature 1-Ctlr A: 53 C 127.40F", but I just want 53 C so that I can use tresholds to create tickets.
I have looked into the MIB files that you can download but none of the items in the MIB will point me to the correct OID's.
Has somebody got this working? AEM Support cant help since the do not have the OID's.
Thanks.
Hi,
I have HP P2000 SAN Storage MSA G3, last week I'd logged into the SAN Storage and analyzed that there is a degraded error on the enclosure, I further checked the logs and events then examined there is an issue with FlashCard. Also, the firmware is old TS250P003 which can be upgraded up to the newly available.
1) I need to know the steps for upgrading the firmware that how to upgrade from the current version to the latest one.
2) CompactFlash is a temporary memory (I believed) and if replaced the faulty one there should not affect on the SAN configuration (Need to confirm)
Your valuables feedback and response will be highly appreciated.
Regards,
Kashif.
Dear All,
I read a lot of docs on web in the topic, however the more I read the more question I have.
1)In a raid5 or raid6 using more disk than the minimum, the total iops calculated with the total disk number with the parity disk(s) or without those?
2)In a capacity tier pool includes raid1 2xSSD with oips X and raid5 6x10k sas with iops Y. Is the calculated total will be its sum (X+Y)?
3)In case of using read cache (for example 2x800Gb ssd in raid1) what is the general method to guess the read cache usage (%) and how can it summarize with the underlying pool iops capability to get a roughly total?
Thank you very much
Hello,
I have an ESXI 6.0 host which is part of a cluster. All other host can access the LUNS created on my 2050, however this one particular host is unable to detect any luns./datastores.
This same host can access luns/datastores on another storage appliance using iSCSI with out any issues. My IQNs and IPs all look correct and this host is configured the exact same as the other host in my clusters.
in vmware, when I click on the storage devices, the host sees the HPE iSCSI Enclosure but no disks/luns.
At a loss as to why this host will not detect the LUN I created.
Apologies for this if I am missing something, but: I've got an MSA 2050 connected via SAS to a ProLiant DL380 gen10.
I have looked at the Best Practice Guide and the MSU Guide but I cannot work out how to provision the storage. I have Disc Groups and Volumes, and I have mapped two disc groups to all initiators... But, there are no Hosts or Initiators.
The lights on the SAS interfaces on the back of the MSA are not lit.
Never having worked with storage provisioning in this fashion, I'm a bit stuck - it seems to me that if there's no light on the SAS cables. I would expect A1-SAS and B1-SAS to be lit and active in the console but they're not. Is this a cabling issue, or do they only light up when they're enabled?
Hello,
A customer cannot delete some old snapshots. When checking the log file I see this for the status of snapshots
A VSS170828204859249 2017-08-28 21:47:01 Available N/A Pool_A_CSV01 Pool_A_CSV01 0 8 N/A 376.9GB 212.1GB 164.8GB never-delete
This I see for multiple snapshot. So the setting most likely prevents the deletion of the snaps. How can I change this setting so I can delete the snapshots? I cannot find it in the documentation I have (SMU Guide)
We have a MSA which is showing a disk with Read Erros, however the disk is not failed yet.
We have a spare disk avaialble for replacement, and the config has a spare assigned to the dg.
How can safely replace the disk with read errors. I have not found a way to remove the disk with read errors from the vdisk/dg. Simply pulling the drive does also not seem a wise thing to do, since there is chance you pull the disk in the midst of an write operation and corrupt data this way. Should we wait untill the disk is marked failed?
The disk is predictive fail, but up and running
Dear All,
I found this doc (HPE MSA Storage Configuration and Best Practices for VMware vSphere) on the hpe site (from the hpe site), which claims the following:
-page 5: Msa has vSphere support VAAI, VASA, SRM
-page 12: Virtual Volumes
However when I try to search on the vmware hal: vmware vvol
"What are you looking for: vShere APIs for Virtual Volumes (VVOL)" ; select hpe in the partner name it does not show me the msa 2052 in the array model.
When I changed the "What are you looking for: vShere APIs for storage awarness (VASA), for non-VVOLs then the array models window shows me the msa 1040 and 2040.
From vmware:
"Virtual Volumes constitutes five major components namely VVol Device, Protocol End Point, Storage Container, VASA Provider and Array and......"
So what does the "vasa for non-vvol" and what does the first selection means? What is the difference between those?
Thank you very much
Hi,
I've been attempting to assist someone rebuild a failed RAID5 VDISK in a 2 enclosure MSA 2321FC system. Sadly when a new drive is inserted the rebuild runs for some time and eventually fails. When I examine the logs I can see the reconstruction has failed as below
B9320 2019-05-30 12:45:55 44 W B Unwritable cache data exists for a volume. (volume: , SN: 00c0ffd811c500003261c44a01000000) It comprises 1% of cache space.
B9321 2019-05-30 12:45:55 44 W B Unwritable cache data exists for a volume. (volume: , SN: 00c0ffd811c500003261c44a02000000) It comprises 1% of cache space.
B9322 2019-05-30 12:45:55 44 W B Unwritable cache data exists for a volume. (volume: , SN: 00c0ffd811c500003261c44a03000000) It comprises 1% of cache space.
B9323 2019-05-30 12:45:55 44 W B Unwritable cache data exists for a volume. (volume: , SN: 00c0ffd811c500003261c44a04000000) It comprises 1% of cache space.
B9324 2019-05-30 12:45:55 44 W B Unwritable cache data exists for a volume. (volume: , SN: 00c0ffd811c500003261c44a05000000) It comprises 1% of cache space.
B9325 2019-05-30 12:45:55 18 W B Vdisk reconstruct failed. Command failed. (error code: 1). (vdisk: VDISKAA SN: 00c0ffd811c50000c358c34a00000000)
B9326 2019-05-30 12:45:55 172 W B A vdisk was quarantined. (vdisk: VDISKAA SN: 00c0ffd811c50000c358c34a00000000)
B9341 2019-05-31 11:50:37 44 W B Unwritable cache data exists for a volume. (volume: , SN: 00c0ffd811c500003261c44a01000000) It comprises 1% of cache space.
B9342 2019-05-31 11:50:37 44 W B Unwritable cache data exists for a volume. (volume: , SN: 00c0ffd811c500003261c44a02000000) It comprises 1% of cache space.
B9343 2019-05-31 11:50:37 44 W B Unwritable cache data exists for a volume. (volume: , SN: 00c0ffd811c500003261c44a03000000) It comprises 1% of cache space.
B9344 2019-05-31 11:50:37 44 W B Unwritable cache data exists for a volume. (volume: , SN: 00c0ffd811c500003261c44a04000000) It comprises 1% of cache space.
B9345 2019-05-31 11:50:37 44 W B Unwritable cache data exists for a volume. (volume: , SN: 00c0ffd811c500003261c44a05000000) It comprises 1% of cache space.
B9346 2019-05-31 11:50:38 172 W B A vdisk was quarantined. (vdisk: VDISKAA, SN: 00c0ffd811c50000c358c34a00000000)
B9347 2019-05-31 11:50:38 18 W B Vdisk reconstruct failed. Command failed. (error code: 1). (vdisk: VDISKAA, SN: 00c0ffd811c50000c358c34a00000000)
It seems I end up with this unwritable cache data error everytime this drive is replaced. It's always the same drive at the same slot.
I'm a bit stumped why this may be occurring. I've tried clearing the cache, clearing the metadata on the newly inserted drive and repeating the process of reconstruction again (with a couple of different replacement drives) but the outcome is always the same.
Details of the volume referred to above taken from the log dump.
<OBJECT basetype="volumes" name="volume" oid="157" format="rows">
<PROPERTY name="virtual-disk-name">VDISKAA</PROPERTY>
<PROPERTY name="volume-name">VDISKAA_v002</PROPERTY>
<PROPERTY name="size" units="GB">998.9GB</PROPERTY>
<PROPERTY name="size-numeric">1951171872</PROPERTY>
<PROPERTY name="preferred-owner">B</PROPERTY>
<PROPERTY name="preferred-owner-numeric">0</PROPERTY>
<PROPERTY name="owner">B</PROPERTY>
<PROPERTY name="owner-numeric">0</PROPERTY>
<PROPERTY name="serial-number" key="true">00c0ffd811c500003261c44a02000000</PROPERTY>
<PROPERTY name="write-policy">write-back</PROPERTY>
<PROPERTY name="write-policy-numeric">1</PROPERTY>
<PROPERTY name="cache-optimization">standard</PROPERTY>
<PROPERTY name="cache-optimization-numeric">0</PROPERTY>
<PROPERTY name="read-ahead-size">Default</PROPERTY>
<PROPERTY name="read-ahead-size-numeric">-1</PROPERTY>
<PROPERTY name="volume-type">standard</PROPERTY>
<PROPERTY name="volume-type-numeric">0</PROPERTY>
<PROPERTY name="volume-class">standard</PROPERTY>
<PROPERTY name="volume-class-numeric">0</PROPERTY>
<PROPERTY name="blocks" blocksize="512">1951171872</PROPERTY>
<PROPERTY name="volume-parent"></PROPERTY>
<PROPERTY name="snap-pool"></PROPERTY>
<PROPERTY name="virtual-disk-serial">00c0ffd811c50000c358c34a00000000</PROPERTY>
<PROPERTY name="volume-description"></PROPERTY>
<PROPERTY name="progress">0%</PROPERTY>
I am wondering if other drives which are part of this VDISK are also failing however I could not see anything from the log dump to indicate this during the reconstruction.
Firmware is M112R14 which I am aware is deprecated. I know there is an Oct 2013 firmware available (M114P01-01) which I may suggest they update to,
Has anyone ever seen this behaviour? Is there a workaround or fix? We are now considering deleting the entire VDISK, rebuilding from scratch and restoring to see if that will resolve it.
Any advice appreciated.
thanks
Ad
Hello,
I write from Italy and I have a problem similar with MSA 1050 SAS and 2 DL 380 Gen10 servers and same cables but with VMWare vSphere 6.7 U2.
Configure MSA storage with Pool, Disk Group, Volume and Mapping.
I connect to the first ESX server and create the datastore by connecting it to the MSA volume and it works;
I connect to the second ESX server I try to create the datastore but I don't see the MSA volume.
It appears that the first server exclusively uses the volume.
The Firmware and BIOS are all updated.
Do you have any idea what to do?
Could you tell me how I had to configure MSA and Server?
Thank you and good day.
Mauro.
P.S: This post was moved as a new topic from
The Virtual Pool B was over-provisioned and it ran out of space. Now that, the disk space has been cleaned up at VMWare side, but the pool B is not recovering from its state. Not sure how to reset it without restarting the controller.
What is unallocated space/capacity displayed on the home page? How it is calculated?
Hello, I would like to check on what is the best way to replace the whole unit of my MSA 2050 (which is still working).
I have found the guide for replacing chassis and guide for replacing controller module individually.
I have a question on whether configuration setting is required on the new controller in a dual controller config or will it synchronise between the old and the new set?
If it can synchronise, does it mean I can make use of the existing unit to synchronise my new controllers one by one, then removing them and the hard disks and placing them into the new MSA 2050 unit without any settings required?
Hello,
I looked through the documentation from top to bottom and couldn't find the part number for the sleds / drive bay trays / drive caddy / carrier converter - just units with the drives already in them.
I have a MSA 1050 with 2.5" bays.
Thanks
hello
im struggle with connecting 2 devices msa 2012fc into one logical, is it possible to do ?
in modules there are "expansion SAS" plugs that if i connect from 1 device to 2 device in console after put comman show expander status i can see PHY EGRESS that status is OK but in website there is no additional enclosure visible from second device.
is that possible to make those 2 devices visible eachother ? so i could do redundant backup from one device to second, or in this models its not possible ? or it can be done by Fiber?
Hi. Recently there is a disk failure but NMS did not pick it up. Running on version GL210R004. Upgrade to current version is able to address the problem? Thanks.
Hi, I'm looking for some advice on best practice on an MSA 2052 and expander.
The MSA has 2 x 800GB SSD and 22 x 1.8TB SAS drives.
The expansion cage has 12 x 4TB MDL drives.
The SAN is SAS-connected to an HPE ML350 Gen9 using HBA and all of this storage is to be used for Windows files.
The 2052 is RAID 10 and will present one "drive" to a Windows server.
The expansion is RAID 6 and will present as another drive in Windows server.
My question is regarding maximum volume and pool recommendations to allow one snapshot on each pool. What would be the recommended setup for this? Before the expansion cage was installed today, we had one pool covering the performance cache and 10 SAS drives (volume A, 8TB), and another covering the second set of 12 SAS drives (volume B, 9TB), but this seems too high I think.
Many thanks
Was wondering if the MSA 2052 San DC Controller will connect to a 10gBaseT network Switch. I am finding conflicting information?
I am only finding sfp+ to sfp+ transceivers from HP website. But if i do a google search I am finding HP 813874-B21 sfp+ but I am not sure if they will more in the MSA 2052.
Any thoughts or insight?
Thank you
Hi there,
This may be a silly question. How do you similate a controller failover on an iSCSI MSA 2052? Do I need to pull out a c ontroller card manually while switched on?
I'm used to Nimble which has a button for this.
Thanks
Matthew Taylor
