LPAR the expansion unit belongs to. If there are ambiguous units, this result cannot be guaranteed without taking action to eliminate ambiguity. When LPAR2 is deployed, there is no guarantee that the validation process will not choose the unit already in use by LPAR1, and create LPAR2 to point to those same resources. Consider the case where the plan for LPAR1 and LPAR2 define ambiguous units that satisfy both partitions. LPAR1 has been deployed, but the deploy of LPAR2 was postponed. When LPAR2 is deployed, there is no guarantee that the validation process will not choose the unit already in use by LPAR1 and create LPAR2 to point to those resources. If LPAR1 happened to be inactive when LPAR2 was activated to install and an initialize was done, LPAR1 data would be lost. Even if the error was caught before an install, the situation must be remedied. The configuration for LPAR2 would need to be manually fixed or redeployed once ambiguity was resolved. Important: If partial deploys are done to a system with ambiguous units, the plan must be updated to include serial numbers for the ambiguous units to avoid the above described scenario. 5.1.4 Eliminating unit ambiguity