Specifying the attributes for a partition mobility operation by using the VIOS

You can list the attributes associated with the vioslpm0 pseudodevice by running the following command, where vioslpm0 is the name of the pseudodevice:

lsdev -dev vioslpm0 -attr 

You can set the following attributes:

• The cfg_msp_lpm_ops attribute is used to control the maximum number of concurrent partition mobility operations that the VIOS can support. You can limit the number of concurrent partition mobility operations that the VIOS will run, based on the configuration and work load of the VIOS. For example, if the VIOS is configured with a single 1 GB network adapter, the value of the cfg_msp_lpm_ops attribute must be a value of 4. The default value for this attribute is 8 for VIOS version 2.2.2.0, or later; therefore, the VIOS version 2.2.2.0 supports up to eight concurrent partition mobility operations. To run the maximum number of supported partition mobility operations on the VIOS, this value must be set to the supported maximum number. The attribute value range is 1 - 8 for VIOS version 2.2.2.0, or later
• The concurrency_lvl attribute controls the amount of resources that are allocated for each partition mobility operation. The attribute value range is 1 - 5, where lower numbers allocate more resources than higher numbers. For most users, it is recommended that the default value is used for all partition mobility operations. However, there are some situations where it might be prudent to change the default value either for a specific partition mobility operation or for the entire VIOS. For more information about when the concurrency level must be changed, see The concurrency level attribute.
• The lpm_msnap_succ attribute indicates whether partition mobility trace data must be saved for migrations that complete successfully. This information is required by IBM® support teams to analyze partition mobility performance problems. The default value is 1, which means that data from successful partition mobility operations is saved.
• The tcp_port_high and tcp_port_low attributes are used to control the range of ports you can select for partition mobility operations. By default, both attributes are set to zero, indicating that any of the 32,768 ephemeral ports on the VIOS can be used for partition mobility operation. When you set the port range, it is suggested that you allocate enough ports for the maximum number of concurrent partition mobility operations in addition to a few more. This helps prevent partition mobility operations from failing when one or more of the ports are in use by other parts of the system. Two ports are used for each partition mobility operation.
• The auto_tunnel attribute allows you to choose whether to enable automatic creation of secure IP tunnels, when you have not already configured secure IP tunnels in the VIOS. This setting is required on the VIOS at both the source and destination servers that are part of the partition mobility operation. The default value of 1 creates secure IP tunnels as required, changing the attribute to 0 prevents secure IP tunnels from being created regardless of any viosecure profile that might be applied to the VIOS.
• The src_lun_val attribute is used to enable and disable LUN level validation of N_Port ID Virtualization (NPIV) devices. This attribute had two possible values, on and off. When the attribute is set to off, LUN level validation is not performed, and when the attribute is set to on, LUN level validation is performed. For more information about disk level validation, see NPIV LUN or disk level validation.
• The dest_lun_val attribute is used to disable LUN level validation of NPIV devices for different operations and is relevant only when src_lun_val has the value on in the source VIOS. This attribute affects only the destination VIOS that is hosting the NPIV storage for remote restart and partition mobility operations. There are four allowed values for this attribute, on, off, restart_off, and lpm_off. By default the attribute is set to restart_off. This value disables LUN level validation for remote restart but allows it for partition mobility operations. Setting the attribute to lpm_off allows LUN level validation for remote restart operations but disables it for partition mobility operations. A value on allows LUN level validation for both partition mobility and remote restart and a value off disables LUN level validation for all operations. For more information on disk level validation, see NPIV LUN or disk level validation.
• The max_val_cmds attribute controls the number of command elements that are allocated for NPIV disk level validation. Higher values reduce the amount of time that is required to perform disk level validation, but they also allocate more resources and use more SAN bandwidth per physical port. It is recommended that the default value is used unless the user has more than 100 disks and the validation time is unacceptable since there is no performance advantage to changing this attribute if the client does not have more than 100 devices visible through the port. For more information on disk level validation, see NPIV LUN or disk level validation.

chdev -dev vioslpm0 -attr cfg_msp_lpm_ops=5