MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » December 2013

Re: I get CPF9E7F on 9117-MMC P7



fixed

I think that it depends on waht the configuration of the shared prc. pool
is. If you put the 4 LPAR's in a pool with MAX 16 prc, and when each of the
4 LPAR scales beyond 1 CPU then I think that with WRKLICINF you will see 16
prc. usage across all 4 LPAR's in that pool.


On Mon, Dec 16, 2013 at 6:32 PM, Roberto José Etcheverry Romero <
yggdrasil.raiker@xxxxxxxxx> wrote:

On the same topic, i was wondering if 4 IBM i partitions with 1 cpu
assigned each but 4 virtual cpus and uncapped weights would count as 4
procs or 16...


On Mon, Dec 16, 2013 at 12:44 PM, Tsvetan Marinov
<tsetso.marinov@xxxxxxxxx>wrote:

Hi all,

I have very strange issue here and I blame the OS API but just in case
maybe someone has encountered the same issue.

So i have 7 V6R1 LPAR's on 9117-MMC P7 which are in a separate shared
processor pool with max 4 prc. limit to this pool and 4 prc OS licenses.
WRKLICINF for 5761SS!/V6/5051 shows that the usage limit is 4 but the
usage
count accross all LPAR's is 16 which is not possible for sure because of
the limitation of the shared pool.

I get CPF9E7F every hour and I'm getting anoyed since my customer thinks
that this is a BIG issue, which is not :


Message ID . . . . . . : CPF9E7F Severity . . . . . . . : 40
Message type . . . . . : Information
Date sent . . . . . . : Time sent . . . . . . :

Message . . . . : i5/OS usage limit exceeded - operator action
required.
Cause . . . . . : The processor usage limit of 4 processors for product
5761SS1, license term V6, feature 5051 has been exceeded.
-- Current processor usage across all active i5/OS partitions is
4,00.
-- Current processor usage for the local partition is 1,00.


I checked 100 times that the LPAR is in the correct pool but even then it
shows the wrong usage across all the LPAR's.

My system is with firmware AM740_100.

I assume that API QSYS/QLZARCAPI is bugged but I can't be sure.

Any clues, PTF or some trick?

Best Regards,

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







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact