The steps and examples in this section provide commands you can use to determine the configuration of your source system, including details about the guest domain that you plan to lift and shift. The configuration information helps you prepare the target system. After the lift and shift process, the configuration information can also serve as a sanity check by comparing the information with the same information on the guest domain on the target system.
As you perform this procedure, take into account the state of your source system and adjust or omit steps as needed.
Capturing the commands and output provides a means to refer back to the data that is collected.
There are a variety of methods to capture output. You can run the script(1M) command to make a record of a terminal session, or use a terminal window with command and output collection capabilities.
Example:
root@SourceControlDomain# script /tmp/source_guest_domain_output.txt
Note – When you want to stop capturing output, type Ctrl-D.
root@SourceControlDomain# uname -a SunOS SourceControlDomain 5.10 Generic_150400-52 sun4v sparc sun4v
root@SourceControlDomain# prtdiag | head -2 System Configuration: Oracle Corporation sun4v SPARC T4-2 Memory size: 32768 Megabytes root@SourceControlDomain# psrinfo -pv The physical processor has 16 virtual processors (0-15) SPARC-T4 (chipid 0, clock 2848 MHz)
In this example, the solaris10 guest domain is spread across 10 cores (80 vCPUs).
root@SourceControlDomain# ldm ls -o core
NAME
primary
CORE
CID CPUSET
0 (0, 1, 2, 3, 4, 5, 6, 7)
1 (8, 9, 10, 11, 12, 13, 14, 15)
---------------------------------------------------
NAME
solaris10
CORE
CID CPUSET
2 (16, 17, 18, 19, 20, 21, 22, 23)
3 (24, 25, 26, 27, 28, 29, 30, 31)
4 (32, 33, 34, 35, 36, 37, 38, 39)
8 (64, 65, 66, 67, 68, 69, 70, 71)
9 (72, 73, 74, 75, 76, 77, 78, 79)
10 (80, 81, 82, 83, 84, 85, 86, 87)
11 (88, 89, 90, 91, 92, 93, 94, 95)
12 (96, 97, 98, 99, 100, 101, 102, 103)
13 (104, 105, 106, 107, 108, 109, 110, 111)
14 (112, 113, 114, 115, 116, 117, 118, 119)
Make note of the CPU resources that are assigned to the guest domain. The target system must provide equal or greater resources to the guest domain (see Prepare the Target System).
In this example, the guest domain called solaris10 has 80 vCPUs and 128 GB of memory.
root@SourceControlDomain# ldm ls NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME primary active -n-cv- UART 16 32G 1.7% 1.7% 4d 13h 3m solaris10 active -n---- 5000 80 128G 0.2% 0.2% 17h 1m
root@SourceControlDomain# ldm –V Logical Domains Manager (v 3.2.0.4.2) Hypervisor control protocol v 1.12 Using Hypervisor MD v 1.4 System PROM: Hostconfig v. 1.4.9 @(#)Hostconfig 1.4.9 2016/06/28 06:37 Hypervisor v. 1.15.5.a @(#)Hypervisor 1.15.5.a 2016/08/09 15:21 OpenBoot v. 4.38.5 @(#)OpenBoot 4.38.5 2016/06/22 19:34
root@SourceControlDomain# ldm ls-services
VCC
NAME LDOM PORT-RANGE
primary-vcc0 primary 5000-5100
VSW
NAME LDOM MAC . NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE INTER-VNET-LINK
primary-vsw0 primary 00:00:5E:00:53:79 aggr1 0 switch@0 1 1 1500 on
VDS
NAME LDOM VOLUME OPTIONS MPGROUP DEVICE
primary-vds0 primary solaris10_root1 /dev/rdsk/c0t600144F0CD152C9E000057F54CA40024d0s2
solaris10_root2 /dev/rdsk/c0t600144F0CD152C9E000057F54CF20025d0s2
solaris10-disk1 /dev/rdsk/c0t600144F0CD152C9E000057F54D4D0026d0s2
solaris10-disk2 /dev/rdsk/c0t600144F0CD152C9E000057F54D780027d0s2
solaris10-disk3 /dev/rdsk/c0t600144F0CD152C9E000057F54DA20028d0s2
solaris10-disk4 /dev/rdsk/c0t600144F0CD152C9E000057F54DD40029d0s2
In this example, the virtual network (vnet0) on the virtual switch is connected to the physical aggregated interface aggr1.
root@SourceControlDomain# dladm show-link
vsw0 type: non-vlan mtu: 1500 device: vsw0
igb0 type: non-vlan mtu: 1500 device: igb0
igb1 type: non-vlan mtu: 1500 device: igb1
usbecm0 type: non-vlan mtu: 1500 device: usbecm0
aggr1 type: non-vlan mtu: 1500 aggregation: key 1
root@SourceControlDomain# dladm show-aggr
key: 1 (0x0001) policy: L4 address: 00:00:5E:00:53:8e (auto)
device address speed duplex link state
igb0 00:00:5E:00:53:8e 1000 Mbps full up attached
igb1 00:00:5E:00:53:8f 1000 Mbps full up attached
root@SourceControlDomain# ldm ls -o net
NAME
primary
MAC
00:00:5E:00:53:8e
VSW
NAME MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE INTER-VNET-LINK
primary-vsw0 00:14:4f:f9:3d:79 aggr1 0 switch@0 1 1 1500 on
-------------------------------------------------------------------------
NAME
solaris10
MAC
00:00:5E:00:53:79
NETWORK
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU MAXBW LINKPROP
vnet0 primary-vsw0@primary 0 network@0 00:00:5E:00:53:9d 1 1500
Identify the guest domain's storage topology, the total storage capacities, and the amount of storage used. This information is used to prepare the target system. The target system must provide the same storage topology and storage capacities to the guest domain. When the archive is created, you can choose one of these methods to migrate the OS, applications, and data:
Capture all the virtual disks in the archive – When the archive is used to deploy the new guest domain, the OS and application data are migrated to the target. This is the method used in this example.
Capture only the OS virtual disks (Alternate Method)– When the archive is used to deploy the new guest domain, only the software on the captured virtual disks is migrated to the target. For more details, see Lifting and Shifting the Virtual Disks Separately (Alternate Method). If you plan to use this method, identify the which software components are on each virtual disk.
In this example, the solaris10 guest domain has six virtual disks (root_disk1 through data_disk4).
Make note of the IDs assigned to each disk. When the guest is moved to the target system, each disk device must have the same ID. After the move, you might need to manually reassign the IDs, which is described in Review the Target Control Domain Services.
In this example, the guest domain's root_disk1 has an ID of 0, root_disk2 has an ID of 1, and so on.
root@SourceControlDomain# ldm ls -o disk
NAME
primary
VDS
NAME VOLUME OPTIONS MPGROUP DEVICE
primary-vds0 solaris10_root1 /dev/rdsk/c0t600144F0CD152C9E000057F54CA40024d0s2
solaris10_root2 /dev/rdsk/c0t600144F0CD152C9E000057F54CF20025d0s2
solaris10-disk1 /dev/rdsk/c0t600144F0CD152C9E000057F54D4D0026d0s2
solaris10-disk2 /dev/rdsk/c0t600144F0CD152C9E000057F54D780027d0s2
solaris10-disk3 /dev/rdsk/c0t600144F0CD152C9E000057F54DA20028d0s2
solaris10-disk4 /dev/rdsk/c0t600144F0CD152C9E000057F54DD40029d0s2
--------------------------------------------------------------------------------------------
NAME
solaris10
DISK
NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
root_disk1 solaris10_root1@primary-vds0 0 disk@0 primary
root_disk2 solaris10_root2@primary-vds0 1 disk@1 primary
data_disk1 solaris10-disk1@primary-vds0 2 disk@2 primary
data_disk2 solaris10-disk2@primary-vds0 3 disk@3 primary
data_disk3 solaris10-disk3@primary-vds0 4 disk@4 primary
data_disk4 solaris10-disk4@primary-vds0 5 disk@5 primary
Make note of the number of disks, their sizes, and order. The same virtual disk topology and capacities are replicated on the target system. See Prepare the Target System.
You can either enter this command, once for each disk:
iostat -En Disk_Name | grep -i size
where Disk_Name is the name obtained from the previous step, for example: c0t600144F0CD152C9E000057F54CA40024d0 (note that the slice designation is omitted)
Or you can list the all of the disk sizes with this single command line:
root@SourceControlDomain# ldm ls -p -o disk primary | grep dev= | sed -e 's,^.*rdsk\/,,' -e 's,s2.*,,' | xargs iostat -En {} | egrep "c0t6|Size" |grep -i size
Size: 322.12GB <322122547200 bytes>
Size: 322.12GB <322122547200 bytes>
Size: 161.06GB <161061273600 bytes>
Size: 161.06GB <161061273600 bytes>
Size: 214.75GB <214748364800 bytes>
Size: 214.75GB <214748364800 bytes>
Add the individual disk sizes and make note of the total disk size. The size is later used in Prepare a Shared Storage Location for the Archive.
In this example, this calculation provides the total amount of disk space of the guest domain's virtual disks (numbers are in GB and rounded).
322 + 322 + 161 + 161 + 215 + 215 = 1396 GB