Re: v5r4 520 with thin console upgrade to v6r1

Rob,

I think the thin console has been set that way from beginning.
We did make it thru v5r4 cume, v6r1 release update, but
v6r1 cume hung w/c900 2967 - they are on phone w/iBM now.
Jim
----- Original Message ----- From: <rob@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Sunday, March 24, 2013 7:12 PM
Subject: RE: v5r4 520 with thin console upgrade to v6r1

Jim,

Also verify that your DSPFMWSTS shows
Firmware update policy . . . . . . . . . . : *OPSYS

Now, in an HMC shop this is taboo. You can ptf yourself up to a firmware
level not supported by your hmc, if, your hmc is way behind on code.
In a shop with no hmc *OPSYS is generally preferred. But if your nonhmc
shop doesn't have it set to *OPSYS then no amount of cumes, etc, will
upgrade your firmware.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Pete Massiello - ML <pmassiello-ml@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 03/24/2013 04:48 PM
Subject: RE: v5r4 520 with thin console upgrade to v6r1
Sent by: midrange-l-bounces@xxxxxxxxxxxx



In your DSPFMWSTS below, notice that on one you are booting the FSP from
the P side at V5R4, and the other screen shot (7.1) you are booting it
from the T side. Just like PTFs, unless you have a GREAT reason, you
should always be booting from the T side.

Pete

--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com





-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Wood
Sent: Saturday, March 23, 2013 12:05 PM
To: Midrange Systems Technical Discussion
Subject: Re: v5r4 520 with thin console upgrade to v6r1

Jim,

We've had this exact situation.

i5/Power Server Firmware absolutely applies and must be addressed. I'd
attack this first and install via i5/OS PTF process. Cumulative PTF
packages do not update server firmware.

The Thin Console Neoware is not a HMC and those instructions will not
apply, nor do you have the ability to update firmware via this pseudo HMC.

I would get comfortable with a LAN attached console configuration as a
backup before moving forward and ensure that you can switch between
Neoware and LAN consoles. I've enjoyed the simplicity of the Neoware
device, but it's a single point of failure. The LAN attached console will
allow you to perform these same tasks with less restraints.

*DSPFMWSTS on a V5R4:*
Display Firmware Status

Service partition . . . . . . . . . . . . . : Yes
Firmware update policy . . . . . . . . . . : *OPSYS
Server IPL source . . . . . . . . . . . . . : Permanent
Firmware product ID/release . . . . . . . . : 5722999 V5R4M0
Server IPL required . . . . . . . . . . . . : Yes
--Server firmware-- -Operating system--
Fix PTF Fix PTF Update
Copy pack ID pack ID Status
*ACTIVE SF230_143 MH00376
*TEMP SF240_338 MH01053 SF240_338 MH01053 None
*PERM SF230_143 MH00376 SF240_338 MH01053 None


*DSPFMWSTS on a V7R1:*
Display Firmware Status

Service partition . . . . . . . . . . . . . : Yes
Firmware update policy . . . . . . . . . . : *OPSYS
Server IPL source . . . . . . . . . . . . . : Temporary
Firmware product ID/release . . . . . . . . : 5733905 V1R1M
Server IPL required . . . . . . . . . . . . : No
--Server firmware-- -Operating system--
Fix PTF Fix PTF Update
Copy pack ID pack ID Status
*ACTIVE SF240_418 MH01304
*TEMP SF240_418 MH01304 SF240_418 MH01304 None
*PERM SF240_418 MH01304 SF240_418 MH01304 None





On Sat, Mar 23, 2013 at 9:14 AM, franz400 <franz400@xxxxxxx> wrote:

Planning an upgrade from v5r4 to 6.1 that has a IBM i Thin Console
(Neoware) that IBM was selling in 2006.
I see that there is Server Firmware and HMC Wizard minimums but not
sure if these apply.
Anyone know?

Jim Franz
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

--
----------------
Joe Wood
----------------

E: wood3875@xxxxxxxxx
M: 801-891-5223
L: http://www.linkedin.com/in/josephgwood
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.