Quantcast
Channel: All MSA Storage posts
Viewing all 8461 articles
Browse latest View live
↧

Re: MSA2060/206x MIBS

April 26, 2024, 12:34 pm
$
0
0

Here are the answers:

1. MIBs for MSA2060 Integration with Solarwinds Orion: To download the HPE MSA Storage Systems SNMP MIBs package, which includes the MSA2060 MIBs, you can visit the HPE support page at [HPE MSA SNMP MIBs](https://www.hpe.com/support/MSASNMPMIB). This package contains various MIB files including `msa2000traps.mib` which is specific to the MSA2000 series and applicable for MSA2060.

2. Recommended Maximum Volume Size for MSA Based LUN Connecting to a Windows 2022 System: 140TB. This size is supported across various MSA models including MSA 1060, MSA 2060, and MSA 2052, among others.

3. O/S Specific Implementation Guides for the MSA206x Family: https://support.hpe.com/hpesc/public/docDisplay?docId=a00105313en_us&docLocale=en_US

4. Automating Response for Showsystem Type Commands with NCM & SAM: No idea

↧
Search

Re: Convert MSA 2060 ISCSI TO FC

April 26, 2024, 12:41 pm
$
0
0

MSA is "modular storage architecture" so it better work  

Anyway jokes aside, yes, the controller type can be swapped as long as you don't mix-and-match. Whether it is cost efficient or not is a different issue. 

↧
↧

Use MSA 2060 as backup repository in Veeam Backup

April 27, 2024, 10:05 pm
$
0
0

Hi

We have a DL380 G10 with a HPE SN1100Q 16Gb Dual Port Fibre Channel, also we have a MSA 2060. MSA directly connected to server by FC to SN1100Q. ESXi 6.7 Installed on server and a veeam backup installed as a VM, also we have other VMs on server. we want to backing up or VMs to storage and SN1100Q Passed through to Veeam Backup. but we cant introduct MSA in veeam not as backup infrastructure or repository. Are we in true Way? 

thanks

↧

Query: Use MSA 2060 as backup repository in Veeam Backup

April 27, 2024, 11:06 pm
↧

Re: Query: Use MSA 2060 as backup repository in Veeam Backup

April 29, 2024, 4:04 am
$
0
0

Hi,

should work, as you planed.

Create a Volume on the MSA and present it to the ESX.
Then create a new Datastore in ESX.
Now add a new Disk from this Datastore to the Veeam VM.
Inside the VM there is now a new Windows Disk, which you can format with ReFS.
Add this Disk as a Veeam Repository.

Cali

↧
↧

replica MSA 2060

April 29, 2024, 9:48 am
$
0
0

I have two MS 2060 FC, I need to replicate volumes between these computers, each computer is in two different geographical locations, I do not have point-to-point FC, it is necessary that they be seen by FC or it can be replicated by IP through the administration positions that are to 1G, which will REQUIRE to be carried out, they will have a document that explains it and a diagram to present to the managers since I have found something clear, Greetings and THANK YOU very much.

↧

Re: MSA2060/206x MIBS

April 29, 2024, 10:05 am
$
0
0

@Hoge_SANMAN 

1. Yes the MIBs have not changed for a Long time
2. Maximum volume size is 140TB (as already answered)
3.  No per OS implementation guides.  There are some details about MSFT MPIO in the best practices guide and VMware guide:  HPE MSA Storage Configuration and Best Practices for VMware vSphere technical white paper
4. The CLI guide linked by @shuff  includes a topic on scripting the using CLI.  To avoid confirmation commands change the CLI output to use one of the API outputs.  api == XML,  json == JSON   Using HTTPS to pass commands into the MSA would be recommended as it uses the lowest resources from the Management Controller.  (i.e. creating and tearing down SSH or telnet sessions is more resource intensive)

Example:

# set cli-parameters json
{

"status":[
{
"object-name":"status",
"meta":"/meta/status",
"response-type":"Success",
"response-type-numeric":0,
"response":"Command completed successfully. (2024-04-29 10:59:48)",
"return-code":0,
"component-id":"",
"time-stamp":"2024-04-29 10:59:48",
"time-stamp-numeric":1714409988
}
]
}

↧

Can I extend existing pool and volume using MSA2060?

May 1, 2024, 2:08 am
$
0
0

Hello folks,
We are going to create an Hyper-V cluster to handle our workload. 
We are planning to install two HPE Gen11 servers and shared storage via SAS connections..

I looked for a MSA storage and I noticed MSA2060.

The main doubt is as follows:
Will it be possible to expand the existing disk pool in the future?
For example I have 4 HDDs in RAID 5, can I add disks and expand the existing pool?
Do I have to use RAID 6 to do this?

Should I use other MSA model to achive this goal?

Thanks for your help

↧
Search

Re: Can I extend existing pool and volume using MSA2060?

May 1, 2024, 1:14 pm
$
0
0

Yes, it is possible to expand the existing disk pool in the MSA2060 by adding disks to a RAID 5 configuration. The MSA2060 allows for the addition of disk groups to expand storage pools, and this can be done using various RAID configurations including RAID 5. You do not necessarily need to use RAID 6 unless you require its additional level of fault tolerance, which allows for two simultaneous drive failures without data loss. As for other MSA models, the MSA 1060 and MSA 2050 also support similar features for expanding disk pools with flexible RAID configurations

↧
↧

Re: Can I extend existing pool and volume using MSA2060?

May 2, 2024, 3:17 am
$
0
0

Hi Federico,

 

In MSA 2060 , pool is an aggregation of disk groups.

You can add a new disk group in the same pool to add more space to the Pool.

Of course, you will lose drives for parity every time you create a new RAID 5 or RAID 6 disk group.

MSA 2060 supports DP+ disk group which requires a minimum of 12 disks.

MSA DP+ disk groups offers the advantage of expanding existing disk group by adding more disks to it.

RAID 5 and RAID 6 disk groups cannot be expanded by adding disks to it.  You may refer to the system concepts listed in MSA 2060 storage management guide (Pages 18-22) for more information: https://support.hpe.com/hpesc/public/docDisplay?docId=a00128580en_us&docLocale=en_US

 

 

 

↧

Re: replica MSA 2060

May 2, 2024, 3:30 am
$
0
0

Hi,  MSA 2060 FC controllers would have 4 FC host ports per controller and one management ethernet port. For replication to work the controller FC host ports on the 2 MSAs should be able to communicate with each other and transfer data. The management ethernet port wont handle the replication data traffic.   From SMU guide(Page 45):  https://support.hpe.com/hpesc/public/docDisplay?docId=a00128580en_us&docLocale=en_US To replicate a volume, you must first create a peer connection or use an existing one, and create a replication set. A peer connection establishes bi-directional communication between a local and remote system, both of which must have FC or iSCSI ports, a virtual pool, and an Advanced Data Services license. The system establishes a peer connection by
connecting a host port on the local system with a user-specified host port on the remote system, then exchanging information and setting up a long-term communication path in-band. Because the communication path establishes a peer connection between the two systems, replications can occur in either direction.

 

↧

Re: replica MSA 2060

May 3, 2024, 12:17 am
$
0
0

Hi , We wanted to follow up and check if the information shared addressed the query. Request you to please respond with a Yes/No. You may also click on "Accept as a solution" button if the issue is resolved.

↧

Re: Can I extend existing pool and volume using MSA2060?

May 3, 2024, 12:18 am
$
0
0

Hi , We wanted to follow up and check if the information shared addressed the query. Request you to please respond with a Yes/No. You may also click on "Accept as a solution" button if the issue is resolved.

↧
↧

Re: MSA2062 - 25Gbps iSCSI connectivity

May 3, 2024, 11:55 am
$
0
0

I'm looking for a new MSA 2062 using iSCSI, but when I look at the MSA 2062 end-to-end performance figures in the QuicksSpecs document, I see that there are a lot of differences in terms of performance when comparing FC, SAS, and iSCSI configurations. One of the reasons is the slower speed of the host protocol:

- 16 Gbps bus speed in FC
- 12 Gbps bus speed on SAS
- 10 Gpbs link speed in iSCSI Other important aspect is de protocol eficiency. And we know that iSCSI on TCP is the worst of the three protocols.

So the dilemma is about using a 25 Gbps link with iSCSI. If we connect the hosts directly to MSA using full 25 Gbps kits, we really gain performance. Does anyone have experience with this? Are there any performance comparisons using a 25 Gbps link with iSCSI? It's really recommended to upgrade these to 25 Gbps.

I would appreciate any feedback if anyone has experience with this setup.

Thank!Sin título.png

↧

Re: MSA2062 - 25Gbps iSCSI connectivity

May 3, 2024, 1:16 pm
$
0
0

@xaviermn 
Thanks for attaching the table from the quickspecs it seems to be a little out of date.  Here is a link to the latest QS with updated numbers. 
https://www.hpe.com/psnow/doc/a00094629enw.pdf

I will point out what I see in this table and let you make an informed decision.
Sequential READs:
iSCSI system states a maximum throughput of 8700MB/sec.  Note that the other Protocols have higher ability (12000MB/sec).  This indicates that the system has potential for more performance so what is the bottleneck.  If the ports are all 10GbE then each port will be capped at a little over 1000MB/sec. There are only 8 ports so  the bottleneck is the host ports running at 10Gb.  So it would be reasonable to expect that Sequential READs would see a bump in performance with updating to 25Gb.

Sequential WRITEs:
Doing the same across protocol comparison it would be reasonable to expect a small bump in performance but the limit is definitely not the host ports, which should have the same potential as READs.

Random READs:
Again the same comparison across protocols shows a potential small bump in performance.  But also looking at the maximum IOPS for an individual 10G port which would be limited by throughput == 10Gb convert to Bytes => ~1000 MB divide by block size (8k) => 125,000 IOPS to fill a 10Gb port with data.  So the potential IOPS with 8 ports is ~1M IOPS.  The host ports are not the bottleneck .... unlikely to unlock additional speed with a port speed increase.

Random WRITEs:
See above

So if your workload is heavily sequential READs then you should see performance increase.  For other workloads you will likely see some performance increase but you should not expect 2.5x increase which may be inferred by increasing individual port speed from 10Gb -> 25Gb.
On the otherhand if your configuration is port limited (further limiting sequential potential) you could see significant sequential performance increases.

All of the above also assumes that the backend (disks) has the ability to meet the maximum performance of the system.  You can get a good idea of configuration performance with the HPE MSA Sizer tools.   https://ninjaonline.ext.hpe.com/
It is recommended to use the AUTO tools when initially configuring a system but using the manual tool can show you the potential of an existing setup in either a single or dual pool configuration.

↧
Search

Re: MSA2062 - 25Gbps iSCSI connectivity

May 4, 2024, 2:40 am
↧

HP MSA 2050 \ DL380 Gen10 \ Windows 2019 Hyper V Host iSCSI errors

May 5, 2024, 8:20 am
$
0
0

Hello

We have a MSA 2050 with 1 pool. Connected via 10GB fiber to a DL380 Gen 10 Server (2 Xeon Processors & 128GB RAM). Direct connection (no switch) Controller A1 and Controller B1 ports are connected via fiber to the back of the DL380 10GB Network Card.

This worked for a couple years. We had a data incident and I had to rebuild the Server and MSA with all new drives. Everything is setup now.

I am using iSCSI to connect the Windows 2019 DC Edition. We use this as a Hyper V Host only. The Guests are using the mapped iSCSI drive as the location of the VHDX file.

The Guests are extremly slow to respond at times. In event viewer of the Hosts I see iSCSI error messages. Guests have 4 vCPU and 16GB RAM. Just OS installed on guests. No apps yet.

Event ID 129 

The description for Event ID 129 from source iScsiPrt cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\RaidPort1

Event ID 39

Initiator sent a task management command to reset the target. The target name is given in the dump data.

Event ID 9

Target did not respond in time for a SCSI request. The CDB is given in the dump data.

Im affraid maybe I missed a setting from a few years ago because this setup worked great before i had to replace all the drives and setup everythging again.

 

Thanks

↧
↧

Query: HP MSA 2050 \ DL380 Gen10 \ Windows 2019 Hyper V Host iSCSI errors

May 5, 2024, 9:21 am
↧

Re: MSA2062 FC - How to distribute the disks between the polls?

May 6, 2024, 1:32 pm
$
0
0
@Carlos_Oliveira wrote:

Hello team, can you help me with this implementation question for a new MSA2062, in the box?

The products are:

1 x MSA2062 FC;

7 x 1.92TB SSD;

17 x 2.4TB SAS

36 x 20TB NL

My question is what would be the best HPE practice to distribute these disks among the Polls!!!

At first I decided to create Pool A with the SSD disks and Pool B with the other disks... and configuring the SSD as performance, SAS as Standard and NL as Archive... what do you think? Or based on best HPE practices should I go with another distribution of Pools versus disks?

Regards,

Carlos Oliveira.

Ok i got this,...

↧

Query: Convert MSA 2060 ISCSI TO FC

April 26, 2024, 10:32 am
↧
Viewing all 8461 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>