

- #Hp 3par ssmc ova install#
- #Hp 3par ssmc ova serial#
- #Hp 3par ssmc ova upgrade#
- #Hp 3par ssmc ova full#
- #Hp 3par ssmc ova software#
I will be opening a case with HP for this when I get around to it.

Anyway, my network guy for a while has been telling me that the active port for the 3par looks good but all the other ports not being used are constantly flapping and filling up the logs. We are plugging into nexus 2000s into 5000's into 7000's. This Hewlett Packard Enterprise (HPE) concepts guide is for all levels of system and storage administrators who plan storage policies, configure storage resources, or monitor the storage usage of HPE 3PAR StoreServ Storage systems. Reduce troubleshooting and management headaches with HPE InfoSight Advanced Performance Analytics, available in HPE SSMC 3. I asked the networking guys if this was a new feature they implemented but they said it is standard on all their switches. Protect existing investments and grow within the 3PAR 8000 series with Data-in-Place upgrades to meet your on-going business requirements. A simple reset of the mgmt ports on the switch side (all of them) got the arrays back on the network and it finished without any other issues.Īs you can tell I found this quite odd.
#Hp 3par ssmc ova upgrade#
The reason seemed to be that during this particular upgrade the cisco switches marked the ports as offline due to all the flapping. HP has introduced a new management console for it gigantic Storage solution 3PAR. Granted no connectivity was lost but at a certain point in the upgrade, the array mgmt port went offline. However, the upgrade to 3.2.1 mu2 caused all our arrays to pause during the upgrade. All the upgrades we have done went rather well. We've had some for over a year now but we are starting to get more. If it were not for flash cache (which we are not eve sure will benefit us) and express writes I would stay on 3.1.3 as long as possible as I am so tired of these painful upgrades. I get the "deer in the headlights" reaction from support and have to leverage my account team to escalate cases to make even the smallest progress. And since going to 3.2.1 one of our arrays shows unknown status int he new SSMC console, but is fine in IMC.ĭon't get me wrong, I understand the complexity of code, but 3par QA is suspect here as well as their inability to react when we encounter these issues. Also in 3.2.1 we are finding issues with AO tasks failing.
#Hp 3par ssmc ova serial#
Our RC ports had similar issues in 3.1.3 such that we were locked out of the entire array with no RC until a tech could come on site and serial into the array.
#Hp 3par ssmc ova full#
We have had to flip flop between our management ports being set to AUTO and then locked to 100 FULL with every release. Seems with every version they make changes to the NIC drivers. The Service Processor (SPOCK) is still a separate entity again, I expect this will be integrated further as the dot releases become available.So we never have any luck with Inform OS upgrades.
#Hp 3par ssmc ova software#
Over the long term I expect that the SSMC will be integrated into the VSP for 3PAR as this will give HP the ability to control software updates to the SSMC in a controlled fashion. It will also be available in certain flavours of Linux.
#Hp 3par ssmc ova install#
SSMC will be available as a Windows based install on Windows Server 2008 R2, 2012 or 2012 R2. No licenses are required this will be a free download

SSMC will be compatible with 3PAR Inform OS 3.1.3 or above. Something in my opinion has been long overdue. HP is moving towards a similar management experience for storage, servers and networking. So what does it look like? Well below are a couple of screenshots to wet your appetite. I already have version 2.1 of SSMC deployed on a virtual machine therefore it was just a case of downloading the latest ISO from HP and running the installation wizard. Management of file and block from same interface HP 3PAR SSMC Excel Add-in Several usability improvements Miscellaneous: 32 systems support Japanese localization.

