Comments (7)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 Alf_Nicolaysen commented Permalink

Nice Article, Brian. Some comments on this: <div>&nbsp;</div> 1) Depending on the Power hardware you work with, you can not simply take the output of the "lssyscfg" command to generate the input for the "mksyscfg" command, as they were some parameters simply not allowed to use. <br /> Example on a type_model=8203-E4A: electronic_err_reporting=null is a output parameter of lssyscfg, but on mksyscfg: The attribute pair with the invalid value is "electronic_err_reporting=null". Please correct the configuration data and retry the command. <div>&nbsp;</div> 2) You mentioned the very nice option to roll out a lpar on another box. There is slightly more work to do as having the "lssyscfg" output, especially when you are NOT on a fresh hardware. In this case you must edit all virtual adapters to appropriate values on the new VIO-Servers, as you will get errros, if the Slot number is already occupied. <div>&nbsp;</div> 3) Last not least rolling out LPARs on new hardware will create the Client-Slots for virtual SCSI, but they will not work as long you are not editing the virtual SCSI configuration on the VIO Servers, as this is a 1:1 relation. <div>&nbsp;</div> Regards <div>&nbsp;</div> Alf

2 brian_s commented Permalink

Thanks for the comments Alf. Yes, depending on what you are doing the command line might need to be tweaked and modified. A couple of other things to watch out for are LPAR ID's (must be unique) and NPIV WWPN's (don't want 2 LPAR's with the same WWPN's). You can modify the "sed" command line to further modify the lssyscfg input if you are trying to automate this, or just manually make the changes.

3 soos commented Permalink

Hi Brian, great stuff as always. <div>&nbsp;</div> Two things. One, interestingly, lssyscfg lists a certain electronic_err_reporting parameter for aixlinux LPARs; however, mksyscfg refuses to accept it as it is IBM i only. And two, when the LPAR is a CPU pool both shared_proc_pool_id and shared_proc_pool_name are listed; but mksyscfg only accepts one or the other, not both. <div>&nbsp;</div> Regards, <br /> Z

4 brian_s commented Permalink

soos, check out EZH,, it has a "lparclone" command that already addresses both the electronic_err_reporting and shared processor pool issues.

5 soos commented Permalink

Brilliant, thank you.

6 jribeauv commented Permalink

Hi, <div>&nbsp;</div> I'm quite newbie in LPAR cloning stuff. <br /> By using result of lparclone ezh command , I just created a LPAR ( twin sister of my already existing AIX7 LPAR). <br /> What's the easiest way to clone the O.S.itself on it ? <br /> Sorry for this stupid question .. <br /> Thanks for help. <br /> Regards, <br /> J.P.

7 brian_s commented Permalink

To clone the OS you'll probably want to use a mksysb.