×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
DLPAR processor is a different animal than what I was talking about.
One of the big things about DLPAR processor is that you still had to fit
that in min/max limits. Otherwise, modifying your partition profile and
IPL from profile was necessary.
Shared Processor Pools are different. Let's say you have 8 processors on
your Power system. Of those 8, five are licensed for IBM i.
You should create a shared processor pool for IBM i and set that to 5
processors and make sure all of our lpars of IBM i are in that pool. The
remaining might stay in shared pool 0 for use by vios, aix and the rack
itself.
min/max rules still apply though.
Sometimes you may want to break down IBM i lpars into different shared
processor pools. We were using a HA product which charged by that. So
the ProdHA lpar and the DevHA lpar on our CBU box were in one shared
processor pool and the rest of the IBM i lpars were in a different shared
processor pool. Neither were in Shared processor pool 0 used by AIX and
VIOS.
This has nothing to do with WRKSHRPOOL.
There was a nice blog which discussed this.
http://ibm.biz/BdZ8FF
https://www.ibm.com/developerworks/community/wikis/home?lang=en_us#!/wiki/Power%20Systems/page/Using%20Shared%20Processor%20Pools%20to%20manage%20CPU%20resources
You can still dynamically lpar processor on HMC 9 but it does look
different.
Stuff in the boxes can be done dynamically. Like the shared processor
pool or the two "Allocated" boxes. Min/Max adjustment will take an IPL.
https://imgur.com/a/AxlevE8
Rob Berendt
midrange.com
