HPE 3PAR StoreServ Storage
1824982 Members
3830 Online
109678 Solutions
New Discussion юеВ

Upgrade HP 3PAR OS 3.3.2. EM1

 
SOLVED
Go to solution
ahotm
Advisor

Upgrade HP 3PAR OS 3.3.2. EM1

hi team

I am experiencing a problem when upgrading to HP 3PAR OS 3.3.2. EMU1 from 3PAR OS 3.3.2 MU1.
I get the following message:

check_features_list: The combination of features running on this array may exceed the memory resources of this array. Upgrading is not recommended at this time.


I've stopped Rcopy and scheduled Tasks but I get the same message.

Thanks for your help.

9 REPLIES 9
support_s
System Recommended

Query: Upgrade HP 3PAR OS 3.3.2. EM1

System recommended content:

1. HP 3PAR OS 3.2.1 GA/MU1/EGA/MU2/EMU1/EMU2/MU3/EMU3 Release Notes

2. HPE 3PAR OS 3.3.1 GA/EGA/MU1/EMU1/MU2/MU3 Release Notes

 

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

 

Thank you for being a HPE valuable community member.


Accept or Kudo

ahotm
Advisor

Re: Query: Upgrade HP 3PAR OS 3.3.2. EM1

hi team

ok thanks for your answer.

But   i want to upgrade from  3PAR OS V3.3.2 MU1  to 3PAR OS V3.3.2.159-EMU1 .

thanks

veeyarvi
HPE Pro
Solution

Re: Query: Upgrade HP 3PAR OS 3.3.2. EM1

Hi Ahotm,

The warning indicates, the array has more features than the supported combinations allowed. I assume the array you have is either 8200 or 8400. 
(For example, if RC is using, the only other feature can be used is AFC). This is enforced in low memory arrays to avoid out of memory situations.

Being that said, if you are already running on 3.3.1 MU5, you may ignore the warning and go ahead installing 3.3.2 since there is not much change in memory consumption between these versions. If you need to check the historical memory consumption of the nodes, please reach to HPE support and if the system connected to HPE backend, they will be able to check historical data and confirm any memory pressure on the nodes now.

Regards,
Veeyaarvi



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
ahotm
Advisor

Re: Query: Upgrade HP 3PAR OS 3.3.2. EM1

@veeyarvi hi Veeyaarvi,

thank for your answer.
yes indeed I use RC with compression and dedupe. I saw in the matrix that this was no longer possible for array 8200 or 8400.

I'm currently on version 3.3.2 MU1 patch P08 and I'd like to install version 3.3.1 EMU1.

Is it possible to ignore this warning?
 I could stop replication of my Volumes to reliev memory

thank you for your help
Ahotm

veeyarvi
HPE Pro

Re: Query: Upgrade HP 3PAR OS 3.3.2. EM1

Hi Ahotm,

Yes, no issues expected in the EMU1 (P10) installation related to this. You can ignore the warning.

Regards,
Veeyaarvi



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
ahotm
Advisor

Re: Query: Upgrade HP 3PAR OS 3.3.2. EM1

hi Veeyaarvi,


Thanks for your feedback
so I can upgrade from version 3.3.2 MU1 to version 3.3.2 EMU1 without any problem.

thank you for your help
Ahotm

support_s
System Recommended

Query: Upgrade HP 3PAR OS 3.3.2. EM1

Hello,

 

Let us know if you were able to resolve the issue.

 

If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

 

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

 

Thank you for being a HPE valuable community member.


Accept or Kudo

ahotm
Advisor

Re: Query: Upgrade HP 3PAR OS 3.3.2. EM1

hi team

yes we resolve the issue. we applied the patches without probleme despite the warning

thanks

Sunitha_Mod
Honored Contributor

Re: Query: Upgrade HP 3PAR OS 3.3.2. EM1

Hello @ahotm,

That's Excellent!

We are extremely glad to know the issue has been resolved.