Migrating a NIM client to an IBM Power Systemsserver logical partition using the command line
Once all prerequisites needed to run the nim_move_up application have been met, nim_move_up performs the migration process in two steps: configuration and phase execution.
Command-Line Usage
nim_move_up {[-S] | [-K [-h control_host] ] | [-r [-R] ]} | { [-c NIM_client] [-i target_ip[-ending_ip]] [-s subnet_mask] [-g gateway] [-h control_host] [-m managed_sys] [-V vio_server [-e] [-D] ] [-I img_src] [-l resource_dir] [-t seconds] [-p loops] [-j nimadm_vg] [-L lpp_source] [-U spot] [-B bosinst_data] [-E exclude_files] [-C script_resource] [-b installp_bundle] [-f fix_bundle] {{[-n] [-d]} | -O} [-q] }
| Flag | |
|---|---|
| -c NIM_client | Either a NIM standalone client (standalone object type), or a NIM machine group (mac_group object type). The indicated clients must be reachable via the network from the NIM master and must allow the NIM master to execute commands on them. If you specify a NIM machine group in this argument, they must all reside in the same NIM network. The clients will be the target machines that will be migrated onto equivalent LPARs on an IBM Power Systems server. |
| -i target_ip[-ending_ip] | The IP address that the new migrated client will be configured with after it is installed onto the IBM Power Systems server. If a NIM machine group is supplied to the -c option, a range of IP addresses must be supplied here and there must be enough addresses in the range to enumerate the amount of clients that will be migrated. |
| -s subnet_mask | The subnet mask that the clients will be configured with after the migration to the IBM Power Systems server. |
| -g gateway | The IP address of the default gateway that the clients will be configured with after the migration to the IBM Power Systems server. |
| -h control_host | The hostname or IP address of the HMC that is used for hardware control of the IBM Power Systems server that nim_move_up is to use. |
| -m managed_sys | The name of the managed system corresponding to the IBM Power Systems server as tracked by the HMC. |
| -I img_src | Path to the source of the installation images to be used to create the NIM resources needed to perform the migration and installation. This path can be a device, such as dev/cd0 if using AIX® product media, or a path to a location on the file system containing the installation images. |
| -l resource_dir | Path to a location on the file system that will contain any new NIM resources created through nim_move_up. The location should have enough space to accommodate an lpp_source and a spot unless existing resources were provided through the -L and -U options. |
| Flag | |
|---|---|
| -S | Displays the status of the execution of the current phase or the next phase to be executed. All saved values are displayed as well. nim_move_up exits immediately after displaying the information. This flag cannot be used with any other options. |
| -n | Executes only the next phase of the nim_move_up migration process. nim_move_up will exit when the phase completes or fails. If you do not provide this flag, all the subsequent phases will be executed, and nim_move_up will exit when all the phases have executed, or one of them has failed. |
| -d | nim_move_up will execute in the background and return control of the terminal to the caller. The progress of nim_move_up can be tracked through the -S flag described above. |
| -q | Quiet mode. No output will be printed to the terminal, but will instead be kept in the logs. This flag has no effect if nim_move_up is being executed with the -d flag described above. |
| -O | Only save supplied values. nim_move_up will save values provided through other options and then exit without executing any phases. This flag cannot be used with any other of the execution or control flags. |
| -K | Configures SSH keys on the specified HMC to allow the unattended remote execution of commands from th NIM master without password prompts. This flag cannot be used with any other options except for the -h option. |
| -r | Unconfigures nim_move_up, which causes it to reset all its saved data, including saved options, phase-specific data, and current phase information. This operation must be executed if the migration process is to be started over for the migration of a new client or set of clients. |
| -R | Removes all NIM resources created by nim_move_up in addition to unconfiguring the environment. This flag can only be used with -r, described above. |
| Flag | |
|---|---|
| -V vio_server | LPAR name of a Virtual I/O Server residing on the IBM Power Systems server denoted through the -m flag described above. |
| -e | Forces the use of physical network adapters instead of shared ethernet adapters in creating the new LPAR on the IBM Power Systems server when a Virtual I/O Server LPAR has been specified. This flag is only valid when used with the -V option described above. |
| -D | Forces the use of physical storage controllers instead of virtual SCSI adapters in creating the new LPAR on the IBM Power Systems server when a Virtual I/O Server LPAR has been specified. This flag is only valid when used with the -V option described above. |
| -p loops | Number of times to execute system analysis tools on the target NIM clients in analyzing its resource utilization. The final resource utilization data will be the average of the values obtained from each loop and will be taken into account when determining the equivalent IBM Power Systems server resources from which the migrated LPAR will be derived. If you do not provide this option, it will default to 1 loop. |
| -t seconds | Number of seconds for which each loop runs. If you do not provide this option, it will default to 10 seconds. |
| -j nimadm_vg | The volume group to be used by the underlying nimadm call for data caching. If this option is not provided, the default value will be rootvg. |
| -L lpp_source | An existing lpp_source NIM resource to whose AIX level the target clients will be migrated to. If this option is not provided, nim_move_up will attempt to create a new lpp_source from the installation image source provided through the -I option, described above. |
| -U spot | An existing spot NIM resource that will be used in the migration and installation of the clients. If this option is not provided, a new spot will be created from the provided lpp_source NIM resource (see the -L and -I options above). |
| -B bosinst_data | An existing bosinst_data NIM resource that will be used by nim_move_up to install the new clients onto the IBM Power Systems server LPARs. If this option is not provided, nim_move_up will generate a bosinst_data resource with default unattended installation values. |
| -E exclude_files | An existing exclude_files NIM resource that nim_move_up will use when creating a mksysb of the original clients. If this option is not provided, nim_move_up will generate an exclude_files resource that will exclude the contents of /tmp from the backup. |
| -C script_resource | An existing script NIM resource that, if provided, nim_move_up will execute in phase 10 (Post-installation Customization) on all of the newly migrated LPARs. |
| -b installp_bundle | An existing installp_bundle NIM resource whose software will be installed on each of the new migrated LPARs in phase 10 (Post-installation Customization) if the option is provided to nim_move_up. |
| -f fix_bundle | An existing fix_bundle NIM resource whose APARs will be installed on each of the new migrated LPARs in phase 10 (Post-installation Customization) if the option is provided to nim_move_up. |
Example:
To configure the nim_move_up application with the required options and to start the first phase of the migration process, you would enter the following:
nim_move_up -c client1 -i 192.168.1.100 -s 255.255.255.0 -g 192.168.1.1 -h hmc1.mydomain.com -m
my-p5 -l /big/dir -I /dev/cd0 -n- -c client1 is a NIM standalone client reachable via the network from the NIM master
- -i 192.168.1.100 is the IP address that the new migrated client will be configured with after it is installed onto theIBM Power Systems server
- -s 255.255.255.0 is the subnet mask that the clients will be configured with after the migration to the IBM Power Systems server
- -g 192.168.1.1 is the IP address of the default gateway that the clients will be configured with after the migration to the IBM Power Systems server
- -h hmc1.mydomain.com is the hostname or IP address of the HMC that is used for hardware control of theIBM Power Systems server to be used by the nim_move_up application
- -m my-p5 is the name of the managed system corresponding to the IBM Power Systems server as tracked by the HMC
- -l /big/dir is the path to a location on the file system that will contain any new NIM resources created by the nim_move_up application
- -I /dev/cd0 is the path to the source of the installation images to be used to create the NIM resources needed to perform the migration and installation
- -n begins the next phase of the migration process.
nim_move_up -Y -d