IBM BladeCenter PS703, Technical Overview And Introduction, Page: 173 / 198

Chapter 5. Systems Director Management Console
159
5.4.1 IVM to SDMC transition process
The transition process is performed manually for the IVM to SDMC transition. The transition
wizard available for HMC to SDMC moves cannot be used for IVM to SDMC transitions. Prior
to the transition the managed system has to be in an IVM-managed state. After the transition
is complete, you are not able to use the IVM user interface, because the Virtual Management
Channel (VMC) is deactivated. The VMC is the device on the Virtual I/O Server that enables a
direct hypervisor configuration. This device is activated only when the Virtual I/O Server
detects that the environment has to be managed by IVM.
What information is transitioned
When you transition managed systems from IVM to SDMC, only the following information is
transitioned:
򐂰 Managed system information.
򐂰 Virtual server information is automatically retrieved from the managed system after a
request access to the managed system is successful.
How to transition
The following steps are used to transition a managed system from IVM to SDMC:
1. Discover the managed system.
2. Request access to the managed system.
3. Update the ASM passwords.
When the access state of the system changes to OK, additional tasks are now available on
the context menu for managing the system. The virtual servers hosted by the system are
retrieved and listed on the Welcome page. Information on the actual steps required to
perform the transition can be found in 5.4.2, “Steps to SDMC management of POWER-based
blades” on page 160.
This transition performs the following operations internally:
򐂰 Fetches the virtual server configuration information from the hypervisor.
򐂰 Updates the SDMC with the managed system information from the hypervisor.
򐂰 The virtual slots ranging from 2 to 10 are reserved in SDMC. The IVM does not have such
restrictions, and it is possible that you were using some virtual slots in the reserved range
in the IVM environment. The transition process looks for such virtual slots and dynamically
adjusts the virtual slots range to a new available range within the maximum slots value
specified.
򐂰 Creates default profiles based on virtual server current configuration read from PHYP
because IVM does not support profiles.
Messages
By default, all success and failure messages are listed in the Event Log page. The Event Log
page is available under the System Status and Health category in the navigation area. Check
Note: If the automatic readjustment of the reserved virtual slot range is unsuccessful,
then you have to shut down and activate the Virtual I/O Server again to use the
advanced PowerVM features. The shutdown and reboot are needed only when you
want to use the advanced PowerVM features; the virtual servers continue to run
normally even without the shutdown and reboot.