What is required on the Global Environment for Live Application Mobility to function?

A production application is hosted across two Power 750 Express servers, managed by an HMC.
Each machine has 16 cores and 32GB RAM. Four 8GB LPARs are defined across the two
systems and only 3 LPARs are active at once. Live Partition Mobility is used to maintain
availability when maintenance is required.
A test environment is being built across two Power 550 Express servers.

Each machine has 8 cores and 16GB RAM. Four 4GB LPARs will be defined across the two
systems, again only 3 will be active at once. To isolate the test and production environment, the
test environment is managed by two IVMs.
Two LPARs have been created on each test server. The administrator initiates a Live Partition
Mobility operation to test moving LPARs between the servers.
The migrlpar command fails to migrate the 4th LPAR with the following error:
“The target managed system does not have enough available memory to create the partition.”
Because the 4th LPAR was inactive, it was expected that an inactive migration would be
successful.
Why would this inactive migration fail on the test environment, but succeed on the production
environment?

An LPAR was created on a POWER6 system with default processor/memory settings. It was
migrated from the POWER6 system to a POWER7 system. Over time, that LPAR has been
shutdown and restarted.
An administrator now needs to migrate the LPAR back to the POWER6 system, but it fails to
validate.
There have been no changes in the LPAR profile, network, or in the SAN configuration.
Which action will enable the operation to complete successfully?

Given the following lspath command output from an LPAR, what is the most likely reason for the
current situation?
$ lspath
Failed hdisk0 vscsi0
Enabled hdisk0 vscsi1
Failed hdisk1 fscsi0
Failed hdisk1 fscsi0
Enabled hdisk1 fscsi1
Enabled hdisk1 fscsi1
Failed hdisk2 fscsi0
Failed hdisk2 fscsi0
Enabled hdisk2 fscsi1
Enabled hdisk2 fscsi1
Failed hdisk3 fscsi0
Failed hdisk3 fscsi0
Enabled hdisk3 fscsi1
Enabled hdisk3 fscsi1

Following the reboot of one VIO server (VIOS) in a redundant configuration, a client is showing
failed disk paths on some channels.
What is the most likely reason the disk paths have failed?

A customer has four LPARs: VIO1, VIO2, LPAR1 and LPAR2
VIO Servers (VIOS) are configured with SEA adapter failover and 802.1Q is enabled on the
LPARs.
During scheduled maintenance, VIO1 is brought down and the SEA failover happens
automatically.
However, network traffic is not leaving the VIO for LPAR1.
The SEA interfaces are setup as follows:
VIO1 – SEA
PVIDs 55,60,65,70
VIO2 – SEA

PVIDs 45,60,65,75
The LPARs have their virtual network devices setup as follows:
LPAR1 – Adapter ID 55 – VLAN ID 75
LPAR2 – Adapter ID 60 – VLAN ID 45
What is the reason for the networking problem?

An administrator needs to update a legacy VIO server (VIOS) partition from version 1.5 to the
most current version. The rootvg of the VIOS server is presented from SAN and is managed using
the SDDPCM package.
Which of the following must be considered?

After applying the latest Fix Pack to a VIO server, the administrator finds an issue with the hosted
media repository. The lsrep command fails with the following error:

“Unable to retrieve repository date due to incomplete repository structure”
What is the most likely cause for this error?

An administrator is attempting to apply a Fix Pack to an VIO server which is not connected to a
network. The administrator loaded the Fix Pack DVD into the drive. The updates command fails
with an error stating that the local SAS optical drive is busy.
What must be verified before attempting to use the optical drive?

An administrator is troubleshooting a network connectivity error on a POWER blade.
Checking netstat, the administrator can see that the relevant adapter is “up and running”. A ping
test to the default gateway times out.
Checking on another adapter, connected to the same LPAR, ping works as expected.
What needs to be checked?