|
|
|
The dpmnim image command uses individual resources to deploy an IBM AIX image from a NIM master server to an existing logical partition (LPAR).
This command has the following format:
dpmnim image [-sc sc_url] -type individual_res [-install_type {rte|mksysb}] -spot spotResource [mksysb mksysbResource] [-lpp lppresource] [-boinst_data bosDataResource] [-resolv_conf resolveconf] [-fb_script fbscript] [-post_inst_scripts script1,script2,script3] [-image_data imageDataResource] -machine_res_name machineresourcename -nim_master_host_name nimmasterhostname -auto_deploy {Yes|No} -target_username targetusername [-target_password targetpassword] [-auth_file authorizationfile] [-auth_comp componentID] -provision_lpar {Yes|No} -hmc name -managed_system managedsystemname -partition_name partitionname [-profile_name lparprofile|lparname] [-scalability_server servername] [-wait [timeout]] [-pre] [-post][-locale iso629value]
(Optional) Defines the URL for the service controller host.
Example: https://hostname:port/...
Defines the fully qualified host where the service controller is installed.
Example: localhost.ca.com
Defines the listening port for the service controller server.
Example: 80
Specifies to use the imaging operation type resource group or individual resources.
Specifies to use the resource group for imaging.
Specifies to use individual resources for imaging.
(Optional) NIM installation type. Accepted values are rte or mksysb. rte is the default if –install_type is not specified.
Defines the shared product object tree to use for an imaging request.
mksysb resource. Only valid if –install_type is mksysb.
Specifies the licensed program product files to use for an imaging request. Optional if –install_type is mksysb. Required if -install_type is rte.
Defines the shared product object tree to use for an imaging request.
Specifies a file that contains information for the base operating system (BOS) installation program. Optional if –install_type is mksysb. Required if -install_type is rte.
(Optional) Defines a file that contains valid /etc/resolv.conf entries that define Domain Name Protocol name-server information for local resolver routines.
(Optional) Defines the name of the file to use to configure devices when a NIM client is initially booting after the BOS installation process is complete.
(Optional) Specifies a comma-separated list of scripts to run after installation.
(Optional) Specifies the image data resource file that describes how physical disks, volume groups, logical volumes, file systems, and paging space are configured on the root volume.
Defines the name of the machine resource. This name must be predefined at the NIM Master.
Defines the NIM master host name to perform the image deployment.
Specifies whether CA Server Automation agents are deployed automatically. Options include the following:
Deploys CA Server Automation agents automatically.
Prevents CA Server Automation agents from being deployed automatically.
Default: no
Defines the user name used for deploying agents to the target host server to which you are deploying the image.
(Optional) Defines the user password used for deploying agents to the target host server to which you are deploying the image. If you do not specify the password, it is retrieved from the authorization file.
Note: Use the dpmutil CLI to set up the authorization file.
(Optional) Specifies the full path name of the authorization file to use to retrieve the encrypted password. This file contains the CA Server Automation administrator credentials that were generated using the dpmutil set auth command. When this option is not specified, the default authorization file is used.
(Optional) Specifies a component ID that you can use to group hosts and users.
Indicates whether the logical partition is imaged. Options are:
Images the logical partition.
Treats partition as machine to provision to, if basic NIM requirements are met.
Default: No
Specifies the Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM) that controls the managed systems where the logical partition resides.
Specifies the managed system on which the logical partition resides. The managed system must exist on the HMC/IVM.
Specifies the logical partition to which the resources are going to be applied. The partition must exist on the managed system.
Specifies the partition profile to use when you activate the logical partition. Required for HMC. Optional for IVM, and if specified the name must match the partition name.
(Optional) Specifies the CA DSM scalability server for software distribution.
(Optional) Indicates whether to display the status of the job and not return until the operation completes, fails, or the timeout period is met (if you specify a timeout value). If you do not specify this option, the CLI returns without waiting for completion. If there is no response, the optional timeout value defines the timeout period in minutes. If you enter the wait option with no timeout value, the CLI uses the default wait time from the caimgconf.cfg file or defaults to 120 minutes. In addition to any positive integer, the following timeout values are also possible:
No timeout value.
Wait indefinitely.
(Optional) Specifies whether to generate an event before the operation is performed.
(Optional) Specifies whether to generate an event after the operation is performed.
(Optional) Specifies an IS0 639_3166 combination (for example: fr_FR for French) to override the default English output. To use the locale of the command prompt, specify "native".
Example: Deploy an IBM AIX image to an LPAR using individual resources
This example deploys an IBM AIX image from a NIM Master server to an IBM AIX LPAR using individual resources.
dpmnim image -type individual_res -lpp lpp_res -spot spot -bosinst_data bid_ow -resolv_conf master_net_conf -post_inst_scripts postins_scripts -machine_res_name ResPartition -nim_master_host_name machine.domain.com -auto_deploy no -target_username root -target_password testpw -provision_lpar yes -hmc hmc01 -managed_system testMS -partition_name lpartest01 -profile_name Default
Example: Deploy an Image to an IBM AIX LPAR by specifying individual resources with a mksyb image.
This example deploys an IBM AIX image from a NIM Master server using MKSYSB installation to an IBM AIX LPAR.
dpmnim image -type individual_res -install_type mksysb -machine_res_name development_1 -spot 530spot_res -mksysb 5300_mksysb_image -target_username root -target_password testpw -nim_master_host_name main_master -provision_lpar yes -hmc hmc01 -managed_system testMS -partition_name lpartest01 -profile_name Default
Example: Deploy an IBM AIX image to an LPAR using RTE installation by specifying individual resources.
This example deploys an IBM AIX image from a NIM Master server using RTE installation using individual resource to an IBM AIX LPAR.
dpmnim image -type individual_res -install_type rte -machine_res_name development_1 -lpp 5301l_res -spot 530spot_res -bosinst_data 530_bid_ow -resolv_conf master_net_conf -fb_script fb1 -post_inst_scripts script1,script2 -target_username root -target_password testpw -nim_master_host_name main_master -provision_lpar yes -hmc hmc01 -managed_system testMS -partition_name lpartest01 -profile_name Default
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |