|
Well, that "on a non partitioned, non hmc-managed system a restart with
*FULL restart *YES will trigger a full server restart including the FSP"
is good news.
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: Roberto José Etcheverry Romero <yggdrasil.raiker@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 08/28/2013 05:44 PM
Subject: Re: PTF install questions
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Yes, on a non partitioned, non hmc-managed system a restart with *FULL
restart *YES will trigger a full server restart including the FSP.
I've seen clients running from A side since the machine was installed (one
even had QBASE as the controlling subsystem....)
Best Regards,
Roberto
On Wed, Aug 28, 2013 at 6:30 PM, John McKee <jmmckee@xxxxxxxxxxxxxx>
wrote:
This is a 520. No LPARs. No HMC.that
Will restart *YES *FULL fix it? I think I read (was away from desk)
this won't work with LPARs. But will it work with p05?intended,
John McKee
On Wed, Aug 28, 2013 at 3:35 PM, Roberto José Etcheverry Romero <
yggdrasil.raiker@xxxxxxxxx> wrote:
I think this is one of those p5 machines with TwinAx/Lan consoles (i
support lot's of them). In that no-partition case, it works as
away
*full restart does exactly what it says it does. Of course if we'retalking
about partitions there should be NO way to update the FW from the LPAR(as
you've say lot's of times, FW MUST be HMC controlled for it not to go
wholetoo new for the hmc code) and a full restart can only be achieved fromthe
HMC (either the system stays on "standby" or shutdowns when the lastback.
partition is off, either way you must start it manually).
I can count at least 4 systems off the top of my head that are
non-partitioned, non-hmc-managed and were installed just a few months
Fresh from the factory 720 express, lan console. Seems like hmc is too
expensive for some, on those systems it still works...
Best Regards,
On Wed, Aug 28, 2013 at 5:11 PM, <rob@xxxxxxxxx> wrote:
A full 'server' ipl cannot be done with RESTART(*YES). You must use
RESTART(*NO). Otherwise you're just IPLing that lpar and not the
serverbox. (Yes, this isn't your father's AS/400.) So, to do a full
panel.IPL
remotely (without an HMC) would probably require either operationsconsole
or lan console. This will give you a gui picture of the control
whiteSo
after the system has powered all the way off you could press the
<midrange-l@xxxxxxxxxxxxbutton via the control panel picture on lan/operations console.
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: John McKee <jmmckee@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion
desk,not.
Date: 08/28/2013 03:34 PM
Subject: Re: PTF install questions
Sent by: midrange-l-bounces@xxxxxxxxxxxx
I wondered about that this morning. Debated on whether to do it or
wouldFrom previous messages exchanged with Rob, I was not sure if that
have made a difference.
I started the IPL from my apartment (long boring story). Got to
andremotely
terminal session was down. My DEVD had ONLINE (*NO). I have since
changed
it to *YES. In theory, now, I could then perform a full IPL
and01
fix this minor irritant. Am I right?
John
On Wed, Aug 28, 2013 at 2:22 PM, Roberto José Etcheverry Romero <
yggdrasil.raiker@xxxxxxxxx> wrote:
Ah! i know what your problem is...
Front panel, does it perchance read: 01 B N V=F P? it should read
BP
N
V=F T. In the same way you have A side and B side for LIC you have
loaded.andIPL'ing
T
(permanent and temporal) sides for the FSP's firmware. You are
from
P which is the same as IPLing from A and expecting ptfs to be
aNext time, do a PWRDWNSYS but take care that it's a *FULL and not
<jmmckee@xxxxxxxxxxxxxx>*SYS
one. It'll restart the FSP and load the correct fw.
Best Regards!
On Wed, Aug 28, 2013 at 4:15 PM, John McKee
IPL0997.wrote:
Finally did.
DSPPTF SELECT(*ACTRQD)
shows eight MH PTFs - 1076, 1073, 1070, 1053, 1007, 1004, 1001,
sourceAll
permantly applied. All show "Permanently applied - IPL". IPL
is
##MACH#B ##SERV#P.
Displaying general information for 5722999 MH01076 shows Server
fromrequired ##SERV#T
Sticking my neck way out - does this imply that a second IPL
"B"on
side
will fix?
We had PTFs temp applied on "B" for years. We are IPLed, now,
IPL"B".
Did
IPL this morning only end up syncing B and A sides, and another
Willwill
rememberfix it?
DSPPTF LICPGM(5722SS1) shows most recent (?) cum as TC10292.
I have applied PTFs suggested in (I have three documents don't
which one) manuals for v5r4 to v61 maybe v71 (mind is going).
loaderrecentlook
thingsthrough the docs a lot more to be sure nothing was missed. Since
are working, predictably, is there any point in loading a more
CUME? I know you guys with LOADS more experience say link
isget
no
longer an issue. But, is there any point to loading a CUME to
tomailing
mailingmailingnext
level if upgrade PTFs are permanently applied?
John McKee
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
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)
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)
mailinglist
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)
listlistlist
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
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
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.