Chapter 3. Transformation scenarios 67
Discover virtual appliances
The last step in the new NIM Server setup is to collect inventory from IBM System Director on
this NIM Server in order to discover the virtual appliances imported earlier:
smcli collectinv -n <nim_server_name> -p "All Inventory"
After succesfully collecting the inventory, the Image repository should show up in the
VMControl Virtual Appliances tab (System Configuration VMControl Virtual
Appliances). The name of your image repository will be the name of your new NIM Server.
3.3.4 Effective migration
This section provides migration guidance.
Discovery, Request Access and collect inventory in HMC
The next logic step in our scenario is to discover the Hardware Management Console on the
IBM Systems Director Server. When you discover HMC devices with IBM Systems Director, it
is a good idea for security and audit reasons to create a special user on the HMC, which IBM
Systems Director uses for connectivity.
For example, if you have an HMC that manages many POWER servers, and you do not want
to discover all of them into IBM Systems Director, then you can add a user and assign roles to
it. These roles will allow your user to manage only the systems you granted access to.
For help on how to create roles for managed resources, you can use section 5.2.3 in
Hardware Management Console V7 Handbook, SG24-7491.
To create users on the HMC through which Systems Director will manage the resources,
again see section 5.2.3 in Hardware Management Console V7 Handbook, SG24-7491.
Discovery
The discovery process is not disruptive. It just interrogates the system using various methods
and protocols and as a result it adds the HMC in IBM Systems Director’s database.
To discover the HMC into Systems Directo,r use the following command:
smcli discover -i <HMC_ip_address> -t OperatingSystem
Request access
After the discovery completes successfully, Systems Director cannot access this HMC
because the credentials to authenticate have not been provided. The next step is to request
access using the user you created in the previous section.
To request access through the command line interface, use the following command:
smcli accesssys -u hscdir -p <hscdir_password> <hmc_system_name>
Note1: This method of accessing a system presents a security risk, because the
credentials might be recorded in the shell or other operating system areas.
Note2: After discovering and providing access to the HMC, you will see only the logical
partitions. Operating systems must be discovered and accessed separately.
68 IBM CSM to IBM Systems Director Transformation Guide
Collect Inventory
The Collect Inventory operation is done to gather information such as LPARs, Virtual
Switches, Virtual Networks and other virtual resources. Use the following command to collect
the inventory from Hardware Management Control:
smcli collectinv -n <hmc_server_name> -p "All Inventory"
After completion of these steps, you have an IBM Systems Director environment ready for
migrating the nodes.
Exporting the CSM nodes and discovering them in Systems Director
Because you may have many systems defined into CSM that you want to discover into IBM
Systems Director, we have provided a few commands to automate the export and the
discovery process.
We could have used the automated discovery of IBM Systems Director based on ranges of IP
addresses but this might not fit everyone’s needs. We want to discover only the nodes we
already had defined in CSM.
After we export necessary node and hardware device data from CSM, we are able to start the
first nondisruptive step of operating systems migration into IBM Systems Director.
Exporting the nodes and hardware devices from CSM
To export the hardware devices and nodes, we used the commands shown in Example 3-24.
Example 3-24 Commands used to export data from CSM
[csm:/]# lshwdev -i | awk '{print $2}' > /tmp/csmhwdevs
[csm:/]# lsnode -i -w "InstallOSName like 'AIX'"|awk '{print $2}' > /tmp/csmnodes
These commands created two files, which are then transferred to the IBM Systems Director
Server. These files contain only IP addresses of the nodes and hardware devices.
Discovering the nodes and hardware devices into IBM Systems Director
In this example, we transferred the files to the /tmp/ directory. We used the commands shown
in Example 3-25 to import the hardware devices and nodes.
Example 3-25 Import CSM hardware devices and nodes in IBM Systems Director
[isd:/]# for i in `cat /tmp/csmhwdevs`; do
> smcli discover -i $i;
> done
[isd:/]# for i in `cat /tmp/csmnodes`; do
> smcli discover -i $i -t OperatingSystem;
> done
Import of CSM nodes to IBM Systems Director endpoints
We recommend to migrate the nodes one at a time to avoid confusion and introduce
problems. It is advised to check that every endpoint is in the correct state before beginning
with migration of the next node.
Note: Discovery does not make any changes on the target system.
Chapter 3. Transformation scenarios 69
By this time, you should have a list of operating system endpoints without access. In the GUI,
you can see this list in the Resource Navigator.
In the smcli, we use the lssys command to display the endpoints without access. Refer to
Example 3-26.
Example 3-26 Partial output of the smcli lssys command
[isd:/]# smcli lssys -l -w "AccessState=Locked"
p6client1:
DisplayName: p6client1
Description: null
IPv4Address: { '172.16.20.72' }
HostName: { 'p6client1' }
AccessState: Locked
Protocols: { 'CAS', 'CIM', 'SSH' }
URL
ManagementSoftware: { 'Unknown-IBM Director Agent-v6.2.0',
'IBM-IBM Director Core Services-v6.2.0.1' }
For each endpoint, we recommend the following steps:
1. Remove the node from CSM by running the following command on the CSM Management
Server:
rmnode <node_name>
2. Grant access to the operating system in IBM Systems Director by running the following
command on the IBM Systems Director Server:
smcli accesssys -u root -p <root_password> <system_name>
3. Collect inventory
Collection of the inventory is needed to gather additional information about the endpoint. It
is strongly recommended after accessing the endpoint for the first time. It is also a good
idea to perform it once a major change in the configuration happens. Collect inventory
using the following command:
smcli collectinv -n <node_name> -p "All Inventory"
4. Verify that the endpoint is correctly migrated.
A properly migrated endpoint is shown in Example 3-27. The output has been truncated,
leaving out irrelevant information.
Example 3-27 Partial output from smcli lssys
[isd:/]# smcli lssys -l -n p6client1
p6client1:
DisplayName: p6client1
SystemBoardUUID: null
IPv4Address: { '172.16.20.72' }
HostName: { 'p6client1' }
AccessState: Unlocked
MachineType: 9117
Note: This method of accessing a system presents a security risk, because the
credentials might be recorded in the shell or other operating system areas. An
interactive alternative is to leave out the password and be prompted.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.