Re: Question about LPAR weights and LPAR group controls [EXTERNAL]
Thanks Tom. I think I understand. :) -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tom Mathias Sent: Wednesday, January 13, 2021 12:29 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question about LPAR weights and LPAR group controls [EXTERNAL] This message was sent from an external source outside of Western & Southern's network. Do not click links or open attachments unless you recognize the sender and know the contents are safe. Jerry, Based upon what you are trying to do, I suggest the following: Make the total weights for LPARs 1, 2, 3, and 4 add up to 1000, assuming all four are normally active. Then you can easily do the math and for example, give LPAR 2 say 15% of the machine by setting its weight to 150 (15/1000). This is the only LPAR you would want to cap. Have LPARs 1, 3 and 4, have weights that together add up to the remaining 85% and don't cap them. If there are spare CPU cycles, then your uncapped LPARs will be able to use them too. LPAR 2 would be the only one limited. Don't forget to also set up the number of processors in each LPAR appropriately. For example, if you have 10 processors and you only give LPAR #2 one processor, then it can only ever use one processor, even if its weight says 15%. Or, if you want a production LPAR to have 3/8 of the system, then it needs at least 4 processors if you have a total of 10 so that it can fully use its 37.5% of the system. And if you give it say 5 processors, then it could even get up to 50% of the system if other LPARs weren't fully using their processing power. Tom -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question about LPAR weights and LPAR group controls [EXTERNAL]
Jerry, Based upon what you are trying to do, I suggest the following: Make the total weights for LPARs 1, 2, 3, and 4 add up to 1000, assuming all four are normally active. Then you can easily do the math and for example, give LPAR 2 say 15% of the machine by setting its weight to 150 (15/1000). This is the only LPAR you would want to cap. Have LPARs 1, 3 and 4, have weights that together add up to the remaining 85% and don't cap them. If there are spare CPU cycles, then your uncapped LPARs will be able to use them too. LPAR 2 would be the only one limited. Don't forget to also set up the number of processors in each LPAR appropriately. For example, if you have 10 processors and you only give LPAR #2 one processor, then it can only ever use one processor, even if its weight says 15%. Or, if you want a production LPAR to have 3/8 of the system, then it needs at least 4 processors if you have a total of 10 so that it can fully use its 37.5% of the system. And if you give it say 5 processors, then it could even get up to 50% of the system if other LPARs weren't fully using their processing power. Tom -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question about LPAR weights and LPAR group controls [EXTERNAL]
Thank you, Tom. That is exactly what I was reading. So, here is what I am attempting - to allow Production LPAR to use all the machine, which is production. - to allow the Test LPAR to use, if busy, up to a certain amount of CPU The other LPARs, I am not really concerned about. My thinking so far. Change the defined capacity to 0, then move the current defined to the LPAR weights. So, I think that would provide what I am looking for. Thanks, Jerry -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tom Mathias Sent: Wednesday, January 13, 2021 11:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question about LPAR weights and LPAR group controls [EXTERNAL] This message was sent from an external source outside of Western & Southern's network. Do not click links or open attachments unless you recognize the sender and know the contents are safe. Jerry, MSU settings (LPAR or group) are enforced by software. LPAR weights (LPAR level only) and absolute capping (at the LPAR or group level) are enforced by the hardware/firmware itself. Weights apply only to active LPARs and control the LPAR's portion of shared processors. In your example, if all 4 LPARs are active and have weights equal to their initial values (30, 10, 10, 30), then LPAR #1 can use 30/80 or about 37.5% of the shared processors. If LPAR #1 doesn't have capping explicitly turned on, then if LPARs #2-4 aren't using their portion of resources, then LPAR #1 could get more. Conversely, if you wind up with only LPAR #1 active, then LPAR #1 can use 30/30 of the processors or 100% of the system. If you don't use software management (like WLM), then you can leave the defined capacity (which is == MSUs) set to 0. If you want LPARs #1 and #4 to not be capped, then make sure the image profile is set up to not cap (and you can check/change via "Change LPAR Controls" on the HMC). If you want LPAR #2 to be capped, then you can turn on capping in the image profile. But, what type of capping do you want? Are you trying to ensure you don't exceed some license agreement for processing power in LPAR #2? If so, then you should instead use "absolute capping". You could either set an absolute cap limit on that specific LPAR or if appropriate, you could set an absolute cap limit on an LPAR group if you want a group of LPARs to be limited in total. For example, maybe you are licensed to only run at most 2 processors worth of power in a given LPAR and no more than say 5 processors worth of power for the entire machine. In that case, you could set each LPAR with this restriction up be capped at 2 processors and then put these LPARs into a group with an absolute cap of 5. On the other hand, if you just want to ensure that LPAR #2 doesn't use too much power (perhaps because it is used for test purposes), then simply capping in the image might be enough because you presumably wouldn't care if the test LPAR used all of the processing power if it happened that it was the only LPAR that was active. The "Processor Resource/Systems Manager Planning Guide" (e.g. SB10-7175) has a lot more details on how LPAR weights and capping and the like work. Still, I know that it is complicated, particularly as there are a number of ways that an LPAR can wind up being capped, either explicitly or implicitly. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question about LPAR weights and LPAR group controls [EXTERNAL]
Jerry, MSU settings (LPAR or group) are enforced by software. LPAR weights (LPAR level only) and absolute capping (at the LPAR or group level) are enforced by the hardware/firmware itself. Weights apply only to active LPARs and control the LPAR's portion of shared processors. In your example, if all 4 LPARs are active and have weights equal to their initial values (30, 10, 10, 30), then LPAR #1 can use 30/80 or about 37.5% of the shared processors. If LPAR #1 doesn't have capping explicitly turned on, then if LPARs #2-4 aren't using their portion of resources, then LPAR #1 could get more. Conversely, if you wind up with only LPAR #1 active, then LPAR #1 can use 30/30 of the processors or 100% of the system. If you don't use software management (like WLM), then you can leave the defined capacity (which is == MSUs) set to 0. If you want LPARs #1 and #4 to not be capped, then make sure the image profile is set up to not cap (and you can check/change via "Change LPAR Controls" on the HMC). If you want LPAR #2 to be capped, then you can turn on capping in the image profile. But, what type of capping do you want? Are you trying to ensure you don't exceed some license agreement for processing power in LPAR #2? If so, then you should instead use "absolute capping". You could either set an absolute cap limit on that specific LPAR or if appropriate, you could set an absolute cap limit on an LPAR group if you want a group of LPARs to be limited in total. For example, maybe you are licensed to only run at most 2 processors worth of power in a given LPAR and no more than say 5 processors worth of power for the entire machine. In that case, you could set each LPAR with this restriction up be capped at 2 processors and then put these LPARs into a group with an absolute cap of 5. On the other hand, if you just want to ensure that LPAR #2 doesn't use too much power (perhaps because it is used for test purposes), then simply capping in the image might be enough because you presumably wouldn't care if the test LPAR used all of the processing power if it happened that it was the only LPAR that was active. The "Processor Resource/Systems Manager Planning Guide" (e.g. SB10-7175) has a lot more details on how LPAR weights and capping and the like work. Still, I know that it is complicated, particularly as there are a number of ways that an LPAR can wind up being capped, either explicitly or implicitly. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question about LPAR weights and LPAR group controls [EXTERNAL]
Remember that LPAR weights defined from the HMC really only come into play when the system is running hot. Capping will keep an LPAR from exceeding the number of MSU's being consumed. This is generally done to help control cost. On Wed, Jan 13, 2021 at 10:35 AM Edgington, Jerry < jerry.edging...@westernsouthernlife.com> wrote: > Thanks Paul. Yes, the defined capacity was setup like LPAR weights, > instead of MSUs. My goal is to have LPAR #1 and #4, not capped, with LPAR > #2, capped. So, I am thinking of changing the defined capacities to 0, and > update the initial, max and min with the current defined capacity. But, > still researching it. > > Jerry > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Feller, Paul > Sent: Wednesday, January 13, 2021 10:28 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Question about LPAR weights and LPAR group controls [EXTERNAL] > > This message was sent from an external source outside of Western & > Southern's network. Do not click links or open attachments unless you > recognize the sender and know the contents are safe. > > > > Jerry, from what I recall the define capacity is related to what you want > to limit the lpar to for MSU usage. You can have an lpar as part of a > group that is capped plus you can cap the lpar itself. I've done that > before. If I read your email correctly you have a group capacity of 20 MSU > which is less then the defined capacity. If that is true I find it > interesting that the HMC would let you do that. My comments are based on > what I understand related to group capacity stuff and defined capacity > stuff. > > From the help screen on the HMC: Defined capacity - The measure of > processor resource consumption for a logical partition, expressed in > millions of service units (MSU) per hour. > > > > Thanks.. > > Paul Feller > GTS Mainframe Technical Support > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Edgington, Jerry > Sent: Wednesday, January 13, 2021 8:37 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Question about LPAR weights and LPAR group controls [EXTERNAL] > > I am looking for some advice about how LPAR group controls, weights and > MSUs work. We have one LPAR group with all the LPAR as members, with MSU > group capacity value. On each LPAR, we have LPAR initial and min/max > weights. > > LPAR group capacity 20 MSU > LPAR #1defined capacity = 900, Initial=30, > min=20, max=30 > LPAR #2defined capacity = 60, initial = > 10, min = 5, max=10 > LPAR #3defined capacity = 60, initial = > 10, min = 5, max=10 > LPAR #4defined capacity = 135, init = 30 > > Questions: > > 1) Does the defined capacity units = MSU or LPAR weights? > > 2) Is LPAR #1 definition mean 900 MSUs? And LPAR #2 with 60 MSUs? > > 3) What would be the capacity of LPAR #1? > > 4) Can LPAR #2 cause CPU issues for LPAR #1? > > Thanks, I thought I understood this stuff, but it would seem I don't. > > Jerry Edgington > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > Please note: This message originated outside your organization. Please > use caution when opening links or attachments. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- ><º>`·.¸¸´¯`·.¸.·´¯`·...¸>(((º> .·´¯`·.><º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><º> <>< Go fishing ><> -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question about LPAR weights and LPAR group controls [EXTERNAL]
Thanks Paul. Yes, the defined capacity was setup like LPAR weights, instead of MSUs. My goal is to have LPAR #1 and #4, not capped, with LPAR #2, capped. So, I am thinking of changing the defined capacities to 0, and update the initial, max and min with the current defined capacity. But, still researching it. Jerry -Original Message- From: IBM Mainframe Discussion List On Behalf Of Feller, Paul Sent: Wednesday, January 13, 2021 10:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question about LPAR weights and LPAR group controls [EXTERNAL] This message was sent from an external source outside of Western & Southern's network. Do not click links or open attachments unless you recognize the sender and know the contents are safe. Jerry, from what I recall the define capacity is related to what you want to limit the lpar to for MSU usage. You can have an lpar as part of a group that is capped plus you can cap the lpar itself. I've done that before. If I read your email correctly you have a group capacity of 20 MSU which is less then the defined capacity. If that is true I find it interesting that the HMC would let you do that. My comments are based on what I understand related to group capacity stuff and defined capacity stuff. >From the help screen on the HMC: Defined capacity - The measure of processor >resource consumption for a logical partition, expressed in millions of service >units (MSU) per hour. Thanks.. Paul Feller GTS Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Edgington, Jerry Sent: Wednesday, January 13, 2021 8:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Question about LPAR weights and LPAR group controls [EXTERNAL] I am looking for some advice about how LPAR group controls, weights and MSUs work. We have one LPAR group with all the LPAR as members, with MSU group capacity value. On each LPAR, we have LPAR initial and min/max weights. LPAR group capacity 20 MSU LPAR #1defined capacity = 900, Initial=30, min=20, max=30 LPAR #2defined capacity = 60, initial = 10, min = 5, max=10 LPAR #3defined capacity = 60, initial = 10, min = 5, max=10 LPAR #4defined capacity = 135, init = 30 Questions: 1) Does the defined capacity units = MSU or LPAR weights? 2) Is LPAR #1 definition mean 900 MSUs? And LPAR #2 with 60 MSUs? 3) What would be the capacity of LPAR #1? 4) Can LPAR #2 cause CPU issues for LPAR #1? Thanks, I thought I understood this stuff, but it would seem I don't. Jerry Edgington -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Please note: This message originated outside your organization. Please use caution when opening links or attachments. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question about LPAR weights and LPAR group controls [EXTERNAL]
Jerry, from what I recall the define capacity is related to what you want to limit the lpar to for MSU usage. You can have an lpar as part of a group that is capped plus you can cap the lpar itself. I've done that before. If I read your email correctly you have a group capacity of 20 MSU which is less then the defined capacity. If that is true I find it interesting that the HMC would let you do that. My comments are based on what I understand related to group capacity stuff and defined capacity stuff. >From the help screen on the HMC: Defined capacity - The measure of processor >resource consumption for a logical partition, expressed in millions of service >units (MSU) per hour. Thanks.. Paul Feller GTS Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Edgington, Jerry Sent: Wednesday, January 13, 2021 8:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Question about LPAR weights and LPAR group controls [EXTERNAL] I am looking for some advice about how LPAR group controls, weights and MSUs work. We have one LPAR group with all the LPAR as members, with MSU group capacity value. On each LPAR, we have LPAR initial and min/max weights. LPAR group capacity 20 MSU LPAR #1defined capacity = 900, Initial=30, min=20, max=30 LPAR #2defined capacity = 60, initial = 10, min = 5, max=10 LPAR #3defined capacity = 60, initial = 10, min = 5, max=10 LPAR #4defined capacity = 135, init = 30 Questions: 1) Does the defined capacity units = MSU or LPAR weights? 2) Is LPAR #1 definition mean 900 MSUs? And LPAR #2 with 60 MSUs? 3) What would be the capacity of LPAR #1? 4) Can LPAR #2 cause CPU issues for LPAR #1? Thanks, I thought I understood this stuff, but it would seem I don't. Jerry Edgington -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Please note: This message originated outside your organization. Please use caution when opening links or attachments. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Question about LPAR weights and LPAR group controls
I am looking for some advice about how LPAR group controls, weights and MSUs work. We have one LPAR group with all the LPAR as members, with MSU group capacity value. On each LPAR, we have LPAR initial and min/max weights. LPAR group capacity 20 MSU LPAR #1defined capacity = 900, Initial=30, min=20, max=30 LPAR #2defined capacity = 60, initial = 10, min = 5, max=10 LPAR #3defined capacity = 60, initial = 10, min = 5, max=10 LPAR #4defined capacity = 135, init = 30 Questions: 1) Does the defined capacity units = MSU or LPAR weights? 2) Is LPAR #1 definition mean 900 MSUs? And LPAR #2 with 60 MSUs? 3) What would be the capacity of LPAR #1? 4) Can LPAR #2 cause CPU issues for LPAR #1? Thanks, I thought I understood this stuff, but it would seem I don't. Jerry Edgington -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
