Specifications

108 IBM Power 770 and 780 Technical Overview and Introduction
If you want to migrate an LPAR from a POWER6 processor-based server onto a POWER7
processor-based server using PowerVM Live Partition Mobility, consider this: If the source
server is managed by one HMC and the destination server is managed by a different HMC,
ensure that the HMC managing the POWER6 processor-based server is at V7R7.3.5 or later
and the HMC managing the POWER7 processor-based server is at V7R7.4.0 or later.
2.13 IBM Systems Director Management Console
The newly released IBM Systems Director Management Console (SDMC) is intended to be
used in the same manner as the HMC. It provides the same functionality, including hardware,
service, and virtualization management, for Power Systems server and Power Systems
blades. Because SDMC uses IBM Systems Director Express Edition, it also provides all
Systems Director Express capabilities, such as monitoring of operating systems and creating
event action plans.
No configuration changes are required when a client moves from HMC management to
SDMC management.
Much of the SDMC function is equivalent to the HMC. This includes:
򐂰 Server (host) management.
򐂰 Virtualization management.
򐂰
Redundancy and high availability: The SDMC offers console redundancy similar to the HMC.
The scalability and performance of the SDMC matches that of a current HMC. This includes
both the number of systems (hosts) and the number of partitions (virtual servers) that can be
managed. Currently, 48 small-tier entry servers or 32 large-tier servers can be managed by
the SDMC with up to 1,024 partitions (virtual servers) configured across those managed
systems (hosts).
The SDMC can be obtained as a hardware appliance in the same manner as an HMC.
Hardware appliances support managing all Power Systems servers. The SDMC can
optionally be obtained in a virtual appliance format, capable of running on VMware (ESX/i 4,
Tips: Note the following tips:
򐂰
When upgrading the code of a dual HMC configuration, a good practice is to disconnect
one HMC to avoid having both HMCs connected to the same server but running different
levels of code. If no profiles or partition changes take place during the upgrade, both
HMCs can stay connected. If the HMCs are at different levels and a profile change is
made from the HMC at level V7R7.4.0, for example, the format of the data stored in the
server could be changed, causing the HMC at a previous level (for example, 3.50) to
possibly go into a recovery state because it does not understand the new data format.
򐂰 Compatibility rules exist between the various software that is executing within a
POWER7 processor-based server environment:
–HMC
–VIO
– System firmware
– Partition operating systems
To check which combinations are supported and to identify required upgrades, you can
use the Fix Level Recommendation Tool web page:
http://www14.software.ibm.com/webapp/set2/flrt/home