RE: 520 vs FSP firmware SF225_096 MH00254

[rob@xxxxxxxxx]

Hopefully we have a different situation.  Our lpar's are working.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Haase, Justin C." <justin.haase@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/07/2005 09:37 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: 520 vs FSP firmware SF225_096 MH00254






I put the same firmware on a 550... When it was done cycling the FSP, it
came up OK, but the first time I tried activating a LPAR it said there
was not enough memory to complete the operation.

Long story short, changed the memory requirements in the profile and
reactivated - it worked.  Dynamically LPARed in the memory I reduced it
by and all is well.  My theory is that the system needed a "wake-up
call" from the HMC to clear out its knowledge of the current memory
being used (which since all partitions were down was ZERO, although the
CEC properties showed it all being used.)  I have no idea.

Anyway - that's my experience on an LPAR system for that microcode
level.  Although not the same problem, I am concerned as to being this
far along in the iterations of the firmware code and seeing something
like this.  IBM is aware of it though, so hopefully we won't see it
again.

Justin C. Haase - iSeries System Administrator
IBM Certified Systems Expert - eServer i5
Kingland Systems Corporation
email - justin.haase@xxxxxxxxxxxx
 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Saturday, May 07, 2005 7:53 AM
To: midrange-l@xxxxxxxxxxxx
Subject: 520 vs FSP firmware SF225_096 MH00254

Put on firmware SF225_096 on to my 520 and my system attention light is
on.
Called IBM and report that my HMC listed these codes:  B181B600 and
B303001.  Turns out these are quite common during a FSP reboot.
Basically they mean communication was lost between the FSP and the HMC.
Makes sense to me.  So far, no big deal.  Now how do I turn the
attention light off? 
They said
STRSST
1-Start a service tool
7-Hardware service manager
6-Work with service action log
And just when I was about to hit F6 to clear all this stuff... I ask
"This also shows a A7001730, what's that?"  IBM's response - "Well have
a CE call you and it will involve replacing some parts...".  Me-"I am
putting this same firmware on my 570 today.  Will I have the same
issue?" 
IBM-"It's more 520 specific."  Now I am waiting on the call from the
CE...

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
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.



CONFIDENTIALITY NOTICE:  This e-mail communication, including attachments, 
is covered by the Electronic Communications Privacy Act, 18 U.S.C. 
2510-2521, is confidential, and may be legally privileged.  If you are not 
the intended recipient or believe you received this communication in 
error, please reply to the sender indicating that fact and delete the copy 
you received.  In addition, retention, dissemination, distribution, 
copying, or otherwise use of the information contained in this 
communication is strictly prohibited.  Thank you.

-- 
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.