HPE MSA Setup

HPE MSA Setup

This post walks through the initial install and setup of a HPE MSA.

Assign management IP address

Once you have your HPE MSA racked, cabled and powered on the next step will be to assign it a management IP. To setup the management IP you have two options:

1 Connect via CLI cable – Connect to one of the controllers using the supplied mini USB cable to plug into the CLI port.  You will need to use the connection settings and password supplied in the MSA 2040 User Guide.  Once connected the command to set the IP address details are:

set network-parameters ip address netmask netmask gateway gateway controller a|b

For example

set network-parameters ip 192.168.0.10 netmask 255.255.255.0 gateway 192.168.0.1

controller a

You can then check the settings with the command:

show network-parameters

2 Set with laptop and Ethernet cable – by default the controllers will have the IP address information:

  • Management Port IP Address: 10.0.0.2 (controller A), 10.0.0.3 (controller B)
  • IP Subnet Mask: 255.255.255.0
  • Gateway IP Address: 10.0.0.1

A Set an IP address on the laptop on the same range as the HPE MSA factory default

B Connect the laptop to the MSA with an Ethernet cable

C Open up a web browser and enter the IP address of one of the controllers e.g. https://10.0.0.2

D Click on system settings on the dashboard and as you run through the wizard you will be prompted to set the IP address information.

Update Firmware

Open a web browser and enter the new ip address to connect https://newaddress

When you first logon to the home screen it will prompt you to check if the firmware needs to be upgraded.

HPE MSA Upgrade firmware

Click on the Upgrade Firmware button and see which version of the firmware you are on.  You can check the latest version https://h41111.www4.hpe.com/storage/msafirmware.html. Download and apply the firmware update if necessary or just close the dialog box if the system is already up to date.

HP MSA Update Firmware

Basic System Settings

Click System Settings on the dashboard and this will run you through an initial configuration wizard to get the basics setup.

  • Date and time – Set the time manually or specify NTP server
  • Manage users – This gives you a chance to reset the default manage password and create any additional accounts
  • Install licence – Install additional licences
  • Network – This will be the IP addressees you set earlier so there should be no need for any action here
  • Services – Here you can set how the device can be managed ed via SSH or web

Once you have your basic system setup you can start to work through the steps to get the storage presented to hosts.

Hosts

You can see connected hosts by clicking hosts in the main left toolbar. Assuming you have already connected your hosts and completed any necessary zoning you will see a list of connected hosts. Select each in turn and choose modify from the action menu to choose a friendly name.

Creating a Disk Pool

Your first step in provisioning storage is to create a Pool, a pool is like a RAID group in which you define RAID type and disks to add.

HPE MSA Create Disk Pool

  • Select Pools from the left hand menu
  • Action menu, add disk group
  • Name the pool
  • Select which controller you wish to own the pool. Try to balance the pools across the controllers, so there is an even number of pools on each controller
  • Choose your data protection level aka RAID level
  • Select the disks you wish to add into the group
  • For RAID 5 and 6 you need to ensure that the number of data drives in the RAID group is divisible by two for best performance. RAID 6 is recommended for larger NL disks
    • RAID 1. Requires 2 disks.
    • RAID 5. Requires 3-16 disks.
    • RAID 6. Requires 4-16 disks.

Assigning Spares

You will need some spares to act as a hot standby should a disk fail.  Dynamic sparing is enabled by default which means that disks not assigned to a disk group will be counted as Global Spares which means that they can act as a spare for any disk group. Spare disks must be at least the same size as the disk they are standing in for.

It is best practice to have one global hot spare per disk group. So make sure you have the correct number and size of disks not in a disk group so they can be global hot spares.

Configuring the Read Cache

Configuring MSA Read Cashe Pool

An SSD disk can be added into a spinning disk group to act as a read cache to extend the size of the controller cache and improve performance.  To add an SSD read cache:

  • Select pools from left-hand tool bar
  • From the action menu choose add disk group
  • From the type drop down select read cache
  • Select an SSD and click add

Provisioning Volumes

Next you need to create your volumes which are effectively LUN’s.

Creating Virtual Volumes for HPE MSA

  • Select volumes from the lefthand tool bar
  • From the action menu choose create volume
  • Enter the name and size of the volume
  • Remember to balance volumes across controllers

The end result we end up with is as below. We have two volumes balanced across the two storage pools which themselves are balanced across the controllers.  By maintaining a one to one relationship between pools and volumes we reduce the complexity of troubleshooting and performance monitoring and this is also a recommended practice for performance as workloads will not be conflicting.

Volume summary

 

Mapping Volumes to Hosts

Lastly you need to map your volumes to your hosts.

  • Select mapping from the left hand menu
  • From the action menu choose mapping
  • Simply select the initiator you wish and then select the volumes to map to map it to and select map.

 

 

 

 

 

 

 

 

 

 

Choosing infsight VM details option in 3PAR

Configuring 3PAR with InfoSight

HPE previously announced the availability of HPE InfoSight for 3PAR. This guest post by Armin Kerl runs through the process of setting up 3PAR Cross-stack Analytics for VMware. This allows a number of insights into the performance of VM’s held on the storage.

HPE 3PAR InfoSight PERQUISITES

Hello 3PAR Guys, today I will show you how to enable VMware integration in HPE InfoSight. Before you register your system in InfoSight you need the following prerequisites in place:

  • 3PAR Call Home enabled, as I describe here
  • An active support contract is in place, which you can verify with the HPE Warranty Checker
  • Additionally if you wish use Cross-stack Analytics for VMware  the following requirements apply:
    • Minimum 3PAR OS 3.2.2 MU4 minimum with Service Processor version 4.4 MU7 or later
    • 3PAR OS 3.3.1 with Service Processor 5.0 MU3 or later
    • 3PAR Service Processor must be configured to use the RDA Transport Agent (SSA is not supported)
    • VMware vCenter versions 5.5, 6.0 or 6.5

High-level setup steps

If the above requirements are in place you will then be able to complete the following high level steps to get InfoSight with cross-stack analytics.

  1. Register the system with InfoSight
  2. Configure VMware integration in the Service Processor
  3. Ensure that the RDA transport mode is used for the Service Processor

We will run through these steps in the next sections:

Registering system with InfoSight

  • Logon to InfoSight with your HPE passport ID
  • Click on the HPE 3PAR StoreServ / StoreOnce Register Systems link on the Welcome Page (Settings > Register Systems). It’s easiest if you create
  • You will then choose a system group you want to assign the device to.  This allows you to group all your organisations devices
  • You will then be presented with a System Group Registration Token to copy and paste onto each 3PAR to perform registration.  You will see a full set of instructions on how to do this, with the choice of doing this via CLI, SSMC and IMC.

Integrating the 3PAR Service Processor with vCentre

The exact steps you need to take will depend on the version of the Service Processor you are running. First we look at doing this with service processor 5.0.3

vCentre integration Service Processor 5.0.3

1 Once you are logged into your Service Processor you can see the firmware version of the service processor like in the screenshot below

503 error

2 Now go to Systems from the main menu

3 From the Actions Menu chose Edit System

3 Choose VMware integration

Adding vCentredetails to ServiceProcessor

4 Choose Add vCenter. Enter IP address, password and other relevant information for your vCenter. The account supplied needs to have read only access to the vCentre

Adding vCenterto infosight

vCentre integration Service Processor 4.x

  • Login to SPOCC
  • Select SPmaint from the Main Menu and choose Option 3 “StoreServ Configuration Management”
  • Choose “Add StoreServ” then “Add vCenter”
  • Supply the required information and click add. The account supplied needs to have read only access to the vCentre

RDA transport mode

If you got this Message:

RDA Message

Than the RDA Transport Protocol is not active, and the SP uses the old SSA transfer agent. This happens mostly, if you have updated the Service Processor from 4.4 to 5.0. To solve this:

Logon to the Service Processor with the “hpepartner” Account and go to “Edit SP configuration”.

Service Processor EditNow under Support change from SSA to RDA Transport Agent.

Check if Call Home Transfer is still working, it may be the RDA needs different firewall exceptions on your site.

Note that Service Processor 4.x releases require HPE Support to modify the configuration from Secure Service Agent (SSA) to Remote Device Access (RDA).

Checking Infosight is integrating with vCentre

The setup steps are now complete we can now check everything is working as expected.

In Activity, we see now VM Collections running.

3PAR activity log

To be able to view the collected stats we need to wait 2-4 hours then log onto InfoSight and click “VM Details”:

Choosing infsight VM details option in 3PAR

 

Now you get lots of VM to Storage related information:

Example 3PAR INfoSight Repor2t

 

Example 3PAR INfoSight Report

For further information on the setup process look at the HPE Infosight For 3PAR Quickstart Guide v1.4

In this previous post available you can see more examples other reports InfoSight will make available. That is all the steps you need to configure 3PAR with InfoSight.

Thanks to the HPE InfoSight team for reaching out with additional information to support this post.

 

 

How to rename a 3PAR Remote Copy Group

This guest post by Armin Kerl  runs you through the procedure to rename a 3PAR remote copy (RCOPY) group. The truth is, that you cannot rename them, so the correct title should be:
How to move a Volume between RCopy Groups without the need to do a full resync,
below are the steps you need to take:

1 First, create a new empty RCopy Group with the new Name (using SSMC).

2 Next we need to stop the RCopy group and unexport the volume. From the CLI stop the Old_Group:

showrcopy -d groups Old_Group

stoprcopygroup Old_Group

Unexport the Volume from Old_Group on the Secondary Site (using SSMC).

3 Having stopped the RCOPY group and unexported the volume we can remove the Volume from Old_Group but choose to keep the snapshot:

dismissrcopyvv -keepsnap Prim_Volume Old_Group

4 To avoid a full resysnc of the volume we want the new RCOPY group to use the existing snapshot. Find the newly generated snapshot name:

showvv -p -type vcopy

5 Add the Volume to the new New_Group:

admitrcopyvv Prim_Volume:sv.0.rcpy.36.264.1 New_Group Sec_3PAR:Sec_Volume.r

6 Start and check the New_Group:

startrcopygroup New_Group
showrcopy -d groups New_Group

7 If the Old_Group hasremaining Volumes, do the same:

startrcopygroup Old_Group

showrcopy -d groups Old_Group

8 Export the Volume again on the secondary 3PAR (use SSMC).

9 Finally delete the temporary Snapshot:

removevv sv.0.rcpy.36.264.1

Armin  is a regular contributor to d8taDude.com, if you would like the chance to share your experiences in front of thousands of reader check out the guest posting opportunities.