Page 2 of 2

Re: Be careful of VMware 5.5 unless you have InForm 3.1.3

Posted: Thu May 22, 2014 9:26 pm
by Josh26
In any case, with the Heartbleed issue, those arrays are scheduled for upgrade to 3.1.3 next month


If it's JUST about Heartbleed, moving to 3.1.3 is a major upgrade. You can get patch 26 applied to 3.1.2 to fix Heartbleed, without even a reboot. It's much less intrusive an option.

Re: Be careful of VMware 5.5 unless you have InForm 3.1.3

Posted: Fri May 23, 2014 9:19 am
by Richard Siemers
Are you sure its patch 26 and not patch 39? Also 3.1.2 MU5 includes the patch for heart bleed.

Re: Be careful of VMware 5.5 unless you have InForm 3.1.3

Posted: Sun May 25, 2014 6:11 pm
by Josh26
Richard Siemers wrote:Are you sure its patch 26 and not patch 39? Also 3.1.2 MU5 includes the patch for heart bleed.


Sorry you're right.. it's 39.

I had the advisory right in front of me and misread it somehow!

But yes, I'd expect it to be also in MU5, so it's a question of how large an update you want. Considering:

3.1.3 is a major update. And there have been some people on this forum with issues
3.1.2 MU5 is a maintenance update. Time will tell how it goes.
3.1.2 P39 is a very minor patch, the nodes don't even reboot

What I'm saying is that if you're in the position of wanting to give either of the larger updates some time for better feedback before rolling them into production, P39 is for you. Otherwise, take your pick.

Re: Be careful of VMware 5.5 unless you have InForm 3.1.3

Posted: Tue May 27, 2014 10:47 am
by Richard Siemers
Josh26 wrote:What I'm saying is that if you're in the position of wanting to give either of the larger updates some time for better feedback before rolling them into production, P39 is for you. Otherwise, take your pick.


Excellent advice Josh. I like to be conservative with storage upgrades but we were forced to pick either 3.1.3 or 3.1.2 MU5 to install newly purchased drives on a 7200 we have... we chose 3.1.2 MU5. The Mu5 update went flawless like all otheres, except we had to run a scipt/fix for the advisory concerning 3TB and 4TB drives... that took 6 hours.