Quantcast
Channel: MSA Storage topics
Viewing all 2285 articles
Browse latest View live

Best way to setup an MSA 2042/2052

$
0
0

Hi there,

I am thinking about replacing my MSA with a brand new one, so probably the new 2052. Anyone has any negative experiences with AutoTiering or Virtual Storage as a whole? Currently I am using a G4 model with just lineair storage. That never failed on me before. But I think a lot of the code of the bigger EVA platform made it to the MSA now. The techniques look very familier.

That being said, I can use the SSDs for read cache or for performance tiering. Somehow I feel some hesitation towards performance tiering. This is my primary storage system and it must be a set it and forget it system. Can't afford any downtime on this building block. Can anyone say something about the stability of the platform, esp comparing read cache vs performance tiering. And can you even have two pools (one per controller) set up as a performance tier? I thought this was a limitation in the 2042, but couln't find anything for the 2052.

Then, suppose performance tiering is the way to go, how would you set up three enclosures, if you do not want to spread disk groups over different enclosures. Or is it fine to do so? So first enclosure will have 4 x SSD (performance tier setup, need RAID1 at least for the SSD diskgroup, it contains data). That leaves 20 unused bays for the 1st enclosure. Following the power of 2 rule, I can add at most 9 HDDs in a diskgroup (8 data and 1 parity, RAID5). This is per pool, so 18 HDDs in total. Leaves me with 2 free bays. I can add two spares, one per pool?

The next enclosures would have a mix of SAS and MDL. Following the power of 2 here again, leaves me with 6 free bays in the enclosure, coz 18 (2 x (8+1)) will be used by disks. So now what? Again 2 spares? that leaves me with 4 bays unused.

To summarize, I find it rather difficult to find a setup that I can expand per enclosure., like I do now with lineair storage.

Am I missing something? I will be hosting a lot of VMs served by three DL380's on this storage array.

Any advice is welcome.

Grtz,

Ronald

 

 


MSA2040FC - IO traffic only on controller A

$
0
0

Hello,

I have strange problem with MSA2040FC on customer site. To this array are connected directly two linux hosts. Array has two storage pools, on each pool is configured one volume.  Multipathing is configured correctly, on both volume I can see IO on volume statistics but I see IO traffic only on A1 and A2 ports, not B1 and B2.

Pool configuration below. Volume configuration, IO statistics and multipath in attchement files.

------------------------------------------------------------------------------------
Name  Size     Free   Own Pref RAID   Class    Disks Spr Chk  Status Jobs  Job% Serial Number                    Spin Down SD Delay Sec Fmt   Health     Reason Action
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
dg01  5995.1GB 25.1MB A   A    RAID10 Linear   12    0   512k FTOL              00c0ff265c150000a5fd665600000000 Disabled  0        512n      OK                      
dg02  4995.9GB 37.7MB B   B    RAID10 Linear   10    0   512k FTOL   VRSC  63%  00c0ff266b6900009efe665600000000 Disabled  0        512n      OK                      
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Do you have any idea why I dont observe IO on B-ports?

 

MSA 2040 iSCSI "All Other Initiators" working only

$
0
0

Hello,

I have an MSA 2040 and I have setup a volume that I am trying to present to 3 ESXi 5.5 host.  I have other iSCSI Storage technology in my environment so I am familiar with mapping the iSCSI initiator to the volume.  However, with the MSA 2040 the only way the initiaor seems to detect the volume is if I use the "All Other Initiators" options. 

I have setup all my host with their respective initiator, and even grouped them.  I did come across the following in the best practice document:

The HPE MSA 2040/2042 enclosure is presented to vSphere as a fibre channel enclosure using LUN 0. This means all volumes mapped to the vSphere hosts or clusters must not use LUN 0. The SMU software doesn’t automatically detect this and for each mapping created, it defaults to LUN 0.

So when I created the mapping I set the LUN to 1, and I am using  a Host Group I created on the MSA.  That did not make a different.  If I change the mapping to use "All Other Initiators" the hosts detect the volume during the rescan process.

I really hope someone can point me in the right direction on this.

Windows XP 64 - MSA 2040 Chassis Driver

$
0
0

I'm trying to find a Windows XP 64 driver for the MSA 2040 chassis to prevent Windows from prompting to install a driver each time the server is restarted.

We have a mix of Win7 x64, Win2012-R2 and several WinXP 64 servers and only the XP servers are unable to identify the chassis. It's more of a cosmetic prompt but annoying the customer.

Regards,

R3.

MSA 2040, snapshots problem

$
0
0

Hello!

We had one controller failure, it had been repaced, but after this we have problem with snapshots creation:

 

 create snapshots volumes volume snap
 Error: The specified name is already in use. (2017-08-03  09:30:24)

Really snapshot is created, I can see it using

show snapshots snap-pool pool-name

It can be even mapped to host, but host doesn't see it :-(

There are also frequent errors during snapshot deletion:

delete snapshot snap
Error: Command was aborted by user. - One or more snapshots were not deleted.

And sometimes I get:

Error: The MC is not ready. Wait a few seconds then retry the request.

 

How can I solve this problem?

Thank you!

MSA 2040 Auto Tiering, Terrible performance ...

$
0
0

Hi all,

Hoping someone might be able to help.  We have a HP 2040 with auto tiering, the disk groups, pools and volumes are configured like so:

4x 1TB SSD RAID5

9x 1.8TB 10k SAS RAID5

9x 1.8TB 10k SAS RAID5

All in a single Virtual Pool.  In the virtual pool I have two volumes configured  Vol1, Vol2 at 10TB (or there abouts) assigned as Cluster Shared Volumes (CSV) volumes are set to no affinity re-tiering as per the best practices.

I am using Windows 2016 with Hyper-V and failover clustering.  We currently have two nodes.

Our hosts are directly connected via two 10g NICS (one to each controller) on the same IP subnet, for testing purposes I have disabled one NIC and configured round robin as failover only.  Jumbo frames is not configured but even when it is the performance difference is negligable.

Performance wise from a Hyper-V VM I use IOMETER and I load a 20GB disk with 4kb 100% sequential write access profile and get a pitiful 8k IOPS. 

From the Hyper-V host I do the same at get a better, but not by much, 18K IOPS.  I know the 4KB 100% seq/write is a lousy real world test but should be one the SAN can easily fulfill to up to around 80,000IOPS from what I read.

Can't readily see any errors on the SAN or the host.

My question is, what the hell have I done wrong :)

 

MSA2324fc Unable to communicate with storage controller

$
0
0
hello,
we use a msa2324fc with 2 controllers. The disks are runnig fine but we are not able to configure anything anymore. Via SMU we get "The system is currently unavailable" and cli can't execute any config commands we get "Unable to communicate with Storage Controller. Please retry the command." Also we are not able to do restart SC and rescan doesn't help too.
The attached show configuration output looks very strange.
Any how we can solve the issue without any downtime?

MSA2324i - Degraded Out Port?

$
0
0

We have a degraded Out Port on one of our SAN controllers and also expericing slugging performance. Could anyone shed some light into how we can fix this? 

I have attached a screenshot so you know what I mean. Below are the results of the show system and versions console comands:

 

# show system
System Information
------------------
System Name: MSA2324i
System Contact: Admin
System Location: Server Room
System Information: Shelf1
Vendor Name: HP StorageWorks
Product ID: MSA2324i
Product Brand: MSA Storage
SCSI Vendor ID: HP
Enclosure Count: 3
Health: OK

 

 

 

# versions
Controller A Versions
---------------------
Storage Controller CPU Type: Athlon 2600+ 1600MHz
Storage Controller Code Version: M114P01
Memory Controller FPGA Code Version: F300R22
Storage Controller Loader Code Version: 19.009
Management Controller Code Version: W441R57
Management Controller Loader Code Version: 12.015
Expander Controller Code Version: 1118
CPLD Code Version: 8
Hardware Version: 53

Controller B Versions
---------------------
Storage Controller CPU Type: Athlon 2600+ 1600MHz
Storage Controller Code Version: M114P01
Memory Controller FPGA Code Version: F300R22
Storage Controller Loader Code Version: 19.009
Management Controller Code Version: W441R57
Management Controller Loader Code Version: 12.015
Expander Controller Code Version: 1118
CPLD Code Version: 8
Hardware Version: 53


HDD for MSA2312sa

$
0
0

Hi All,

I have a hdd with P/N 627114-001 and GPN 507129-010, is it compatible with my MSA MSA2312sa?

thanks

HBA Driver

$
0
0

Dear Friends,

I am looking for following HBA driver (Linux) to work with HPE MSA 2040 SAN

HP P/N :AJ764 - 63002
SP P/N: 489191 - 001
S/N: 8C972112EC
MFR P/N: PX2810403 -20 M

I will be thankful if you can direct me to download page
Regards,

Khalid

MSA 2040 Tiering very low IOPS and awful performance

$
0
0

something is wrong with the MSA 2040 performance tiering, i can only have about 5k IOPS out of it while i have another SAN P2000 G3 which is providing 16K for the same workload.

Both SAN are FC are connected through HP 8/24 SAN switches. can you help me diagnosis the issue ?as i am running out of ideas

we are using HP DL 360p Gen8 as hyperV host for the virtualised workload.

commande(s) pour arrêt de baie SAN MAS2040

$
0
0

Bonjour,

En cas de coupure électrique prolongée, je souhaite pouvoir automatiser l'arrêt de ma baie SAN et de son extension de baie, via des commandes déclenchées par mes onduleurs.

Pour cela, j'ai contacté le support hp téléphonique, qui m'a donné une réponse insatisfaisante : il faut être physiquement devant la baie pour l'éteindre... Or vu la ducumentation HP de la baie, il semble pourtant que ce soit possible en ligne de commande.

Comme je ne suis pas un expert en script, pourriez-vous m'aider en me fournissant un script ou bien la ligne de commande complète qui va bien pour déclencher cet arrêt "propre" de la baie SAN svp ?

idem pour son extension de baie  : l'arrêt de la baie principale (MSA2040) déclenche-t-il automatiquement l'arrêt de l'extension de baie (HP StorageWorks) ? et si non dans quel ordre les arrêter ? et quelles lignes de commande pour arrêter l'extension ?

Merci pour votre aide,

Cyril

There is a problem with a FRU - MSA2324i

$
0
0

Hey guys,

One of the disks is amber and I saw this error on on one of the vdisks

There is a problem with a FRU. (FRU type: disk, enclosure: 1, device ID: 5, vendor: HP , product ID: DG0300FAMWN , SN: 3SEXXFE200009013YXXX, version: HPDC, related event serial number: A22614, related event code: 55).

Can I just replace the hard drive with a new one? and will it will rebuild?

I'm very new to the company and I'm still trying to understand the way things are set up here.

 

 

 

MSA 2040 presenting one large volume

$
0
0

hi all,

we have a MSA 2040 and a second shelf. 48 drives in total. We are using the Storage Management Utility to configure the disks.

We have created three 16 drive vRAID-10 1 disks. Each vdisk has one volume. Right now each volume shows up as an extent (mount point/share) on the fiber channel network.

is there any way to show these 3 volumes as 1 large virtual volume?

i could change the vdisks to a different RAID so one volume would have more disks. But a single vdisk is not able to have all 48 drives in it. so i would have the same question with 2 volume rather than 3.

any help or comments would be appreciated!

メールにて通知される「Server Agents:~」の対処について

$
0
0

お世話になっております。HP Strageworks X1600を使用しております。

以下のようにほぼ定期的に①・②を繰り返してメール通知されます。

内容を見るとどうもストレージのベイにて異常な温度(245℃)を通知されているようです。

①Server Agents: 温度ステータス 劣化

②Server Agents: 温度ステータス OK

サーバ自体に異常がないようなので対処に困っております。

対処方法をご教示願います。


MSA2312i controller firmware needed

$
0
0

Hello,

We have an old MSA2000i G2 which was used in a test lab.  Its controllers (model AJ803A) died because of a power outage - They display the error "Warning The system is currently unavailable." when accessing them via the web interface.

The office is being closed next month and we are scrapping most of the old equipment.  However, as I believe this old MSA still has some value, we would like to donate it to a charity, but this is impossible in its current, inoperable state.

As a result, I would like to have one last chance at resurrecting the device, otherwise it will have to be scrapped (which seems wasteful).  As it appears to be a firmware issue, I am assuming that this would still be possible to fix it via the FTP upload method.  However, I no longer have the firmware files and the support contract has long since expired.

Is this something that anyone can help with?

Thanks in advance,

 

Stephen.

MSA 2040 iSCSI 10gb speed option

$
0
0

I've recently setup a MSA 2040 with 10gb iSCSI connection but in the SMU the host port speed option only have auto or 1gb. Is this normal?

MSA2040 SAN Controller failure

$
0
0

Hi everyone,

First of all, I'm not an expert when it comes to HP Storage, I'm a networker myself. I have what appears to be a failed controller on on an enlcosure. Correct me if I'm wrong, there are 2 controllers (A and B), that are connecting 4 encosures we have. Controller B seems to have failed. The SAN is still functioning, but we have no redundancy. I have reboot controller B, but it still did not come back up. I'm not quite sure where to go from here. The product is out of warranty, so I'm not quite sure where to go from here. Where should I go from here?

New firmware for the MSA 2040/2042/1040 and MSA 2050/2052

$
0
0

Howdy All,

I wanted to make sure everyone saw HPE just released a new firmware version for both the MSA 2040/2042/1040 and the new MSA 2050/2052. 

 It is highly recommended to immediately update to the new firmware versions. 

For the MSA 2040/2042/1040 here is the link to the bulletin for the new GL220P010 firmware:  http://h20566.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-a00025799en_us 

For the MSA 2050/2052 here is the link to the bulletin for the new VL100P001 firmware:  http://h20564.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay/?docId=emr_na-a00025800en_us

Cheers!
/Kipp

HP MSA P2000

$
0
0

We have a P2000 G3 iSCSI SAN , we have configured Vdisks and two Terabyts are availble and not configured.

When we tried to create Vdisk for the available 5 TB , I found no disks to select.

Please advice,

Thanks for any help in advance.

 

Regards,

Mohammed 

Viewing all 2285 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>