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.
- Register the system with InfoSight
- Configure VMware integration in the Service Processor
- 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
2 Now go to Systems from the main menu
3 From the Actions Menu chose Edit System
3 Choose VMware integration
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
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:
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”.
Now 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.
To be able to view the collected stats we need to wait 2-4 hours then log onto InfoSight and click “VM Details”:
Now you get lots of VM to Storage related information:
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.
8 thoughts on “Configuring 3PAR with InfoSight”
Good stuff. A couple of notes:
– HPE InfoSight is NOT StoreFront Remote. We have discountinued StoreFront Remote. While some of the way we show information in InfoSight probably looks familiar if you used SFR in the past, they aren’t the same. You’ll see the gap widen as our team adds more functionality and views with HPE InfoSight.
– For anyone that wants a detailed “QuickStart” guide, I just posted a blog yesterday that has it – from the 3PAR engineering team who is doing the integration work. Here’s a link: https://community.hpe.com/t5/HPE-Storage-Tech-Insiders/3PAR-and-InfoSight-user-s-guide/ba-p/7001116
Great post Richard!
A little outlook.
Today 3PAR InfoSight requires the 3PAR systems to run 3.3.1 and SP 5.03.
It is planned to also support systems running 3.2.2 and SP 4.xx in 3Q18.
HPE InfoSight added support for Cross-stack Analytics for VMware to 3PAR OS 3.2.2 MU4/MU6 with Service Processor version 4.4 MU7 last month. Per the release notes displayed in the Bulletin you see when logging into the portal. The only requirements in addition to the above is that the SP needs to be using the RDA Transport Agent. Assuming the customer already registered their systems in the portal, they would just go in via SPOCC, choose SPmaint, option 3 for Configuration Management, hit “Add StoreServ”, then “Add vCenter” and supply the IP and read-only credentials for their vCenter. There needs of course to be VMs created and using the 3PAR storage for us to provide monitoring, but we’ll scan the configuration immediately, collect perf for an hour and send it home, and it should be linked up and visible within a few hours.
Dear Wiley Thrasher:
Excuse me, but the option you mention does not exist in SP 4.4 MU7. I’m checking it right now. I have two 3PAR 7200 3.2.2 MU6 P10x with SP 4.4 MU7.
I retract! You need to change the SSA Service Processor to RDA via ssh.
How To from 3PARUG
You log into the SP via putty as your 3parcust account, then menu options 1, 14, 1, 4 to reset the password for cpmaint. Then log into the SP again using the cpmaint account via putty and select option 11. It will step you through switching to RDA mode. You need to be sure your firewall allows connections to the new RDA addresses.
Port 443 (https) to be opened (outbound) between Service Processor IP and the
following IP Addresses:
188.8.131.52 – storage-support1.itcs.hpe.com
184.108.40.206 – storage-support2.itcs.hpe.com
g4t2481g.houston.hp.com – (220.127.116.11)
g4t2482g.houston.hp.com – (18.104.22.168)
g9t1615g.houston.hp.com – (22.214.171.124)
g9t1616g.houston.hp.com – (126.96.36.199)
Richard, this is simply great! I was looking for such document to share with our channel community … you made my day :-)))
RDA to SSA switching is no longer supported (((