View Only
  • 1.  Create LPAR without a template?

    Posted Tue January 20, 2015 09:36 AM

    Originally posted by: SueBaker

    Is there a way to create an LPAR without using a template?  Current templates are inadequate and even when I captured a template, it says I require dedicated processors.  We use shared processors.

    Or is the only option to use a template then go in an edit the profile?

  • 2.  Re: Create LPAR without a template?

    Posted Tue January 20, 2015 02:51 PM

    Originally posted by: Amartey Pearson

    You should be able to edit any template to customize it to use shared processors...then when creating the partition based on the template, it will use shared.

    If you captured a partition that used shared processors, but the template shows dedicated, then there is a bug - the captured template should reflect the settings of the lpar from which it was captured.

  • 3.  Re: Create LPAR without a template?

    Posted Tue January 20, 2015 05:16 PM

    Originally posted by: SueBaker


    I believe I'm losing my mind.  Earlier today I captured a shared processor LPAR and it came back with dedicated.  I am trying again, and everything is working as it is supposed to. 


  • 4.  Re: Create LPAR without a template?

    Posted Mon August 07, 2017 05:19 PM

    Originally posted by: ssrjazz

    I still have this question.  I don't -want- to create a partition via a template.  Why not allow the option to start from scratch?  I may not have any lpars to capture a template from on a new system, or I just might not want to use a template at all.


    How do you do this via the enhanced gui?

  • 5.  Re: Create LPAR without a template?

    Posted Mon August 07, 2017 07:13 PM

    Originally posted by: sashok

    The idea behind templates is in many cases servers and LPARs follow a definition pattern.  For example, test, dev, and production servers / LPARs in an environment follow certain defined (as per business requirements) patterns.  So rather than create each single LPAR from scratch using the classic UI wizard, use templates for those common properties, only changing LPAR-specific values at deployment time.


    If you see!/wiki/Power%20Systems/page/HMC%20V8%20R8.6.0%20Enhanced%20UI%20Updates, HMC introduced the concept of quick creation in the 8.6 release.  You'll still need to modify virtual storage, network, etc. before activation, but it provides one alternative to templates.



  • 6.  RE: Create LPAR without a template?

    Posted Tue November 10, 2020 11:02 AM
    Save an LPAR configuration (this will be your first template after some cleaning (1)).
    Edit the configuration file as needed - several fields needs customization (name, virtual_eth_adapters, VLAN, virtual_fc_adapters, slot numbers, etc.) (1)
    Copy the config file to the HMC using ssh hscroot@HMC:.
    On HMC, run: mksyscfg -r lpar -m $power -f $LPAR_CFG_FILE

    Note 1: Some fields must be removed or mksyscfg will fail. You may start with a minimal config file and then add attributes one by one until mksyscfg fails: skip that attribute and continue with others until you have sorted all needed/unwanted attributes.
    LPAR attributes which can't be given within the config file at LPAR creation time can be changed after creation with chsyscfg. Example:
    HMC> chsyscfg -r lpar -m $power -i "sync_curr_profile=1,simplified_remote_restart_capable=1" -p $LPAR_NAME" 

    After LPAR has been created you may have to create virtual adapters on the VIOS, for example virtual FC adapters:
    HMC> chhwres -r virtualio -m $power --rsubtype fc -o a -p $VIO_LPAR -s $CSLOT_NUM -a "adapter_type=server,remote_lpar_name=$LPAR_NAME,remote_slot_num=CSLOT_NUM"

    Then, on VIOS:
    Discover the new server vFC adapters with: ioscli cfgdev
    Retrieve vfchosts with: ioscli lsmap -all -npiv
    Map your FC with: ioscli vfcmap -vadapter $VFCHOST -fcp $FCS

    We use this method using a few config files as templates depending on the type of LPAR we want to create. With of course several scripts to retrieve/edit partition ID, free slot numbers, vswitch, VLAN, vfchost filenames, etc.
    Until now HMC templates didn't provide us enough flexibility to pretend replace our method. I guess HMC REST API could do the job but for now we are happy with our method.

    Antoine Morpain