Complete the Target Guest Domain Configuration

Language:

This procedure describes how to make a few administrative changes to ensure that the target guest domain is properly configured in the target environment.

Log into the target guest domain as superuser.

Mount the shared storage.

root@TargetGuestDom# mount -F nfs TargetControlDom:/ovas1 /ovas1

Adjust the swap and dump sizes on the target guest domain.
It is possible that swap and dump sizes on the source system are larger than the migrated size of swap and dump on the target system. Refer to information collected in Review the Source System Configuration.

In this example, the swap and dump sized are adjusted to match the sizes from the source system to ensure these resources can properly support the workloads.
```
root@TargetGuestDom# zfs set volsize=160g rpool/swap
root@TargetGuestDom# zfs set volsize=3g rpool/dump
```
Configure network parameters to suit the target network environment.
The ldmp2vz_convert script copies these configuration files from the source system into the target guest domain:
- /etc/defaultdomain
- /etc/nsswitch.conf
- /etc/pam.conf
- /var/ldap/
If the network environment of the target guest domain matches that of the source system, the settings in the configuration files are likely suitable and do not need to be changed. In this case, skip the following substeps.

If the target guest domain environment differs from that of the source system, the configuration files might not function correctly on the target domain. For example, you might have executed the ovmtconfig command to set up the target guest domain. If this is the case, you can restore the configuration files to their default contents in the target guest domain by temporarily mounting the original boot environment and using the tar command to copy the files from there to the current boot environment.
1. List the status of the target boot environments.
  In this example, s10s_u11wos_24a is the original target boot environment that has the proper configuration files. mybe is the boot environment created by the ldmp2vz_convert command (in Shift the Source Environment to the Target Guest Domain) and has configuration files from the source system.
```
root@TargetGuestDom# lustatus
Boot Environment           Is       Active Active    Can    Copy
Name                       Complete Now    On Reboot Delete Status
-------------------------- -------- ------ --------- ------ ----------
s10s_u11wos_24a            yes      no     no        yes    -
mybe                       yes      yes    yes       no     -
```
2. Create a directory and move the configuration files to it.
  This step moves the unwanted files to a safe location in the unlikely event that they need to be referenced for some reason.
```
root@TargetGuestDom# cd /
root@TargetGuestDom# mkdir /etc/p2v/configs_backup
root@TargetGuestDom# mv etc/defaultdomain etc/nsswitch.conf etc/pam.conf var/ldap /etc/p2v/configs_backup
```
3. Mount the original boot environment to a temporary mount point on the guest domain.
```
root@TargetGuestDom# lumount s10s_u11wos_24a /mnt
/mnt
```
4. In the original boot environment, create a tar file of the configuration files.
```
root@TargetGuestDom# cd /mnt
root@TargetGuestDom# tar cvf /etc/p2v/configs_tar_orig etc/defaultdomain etc/nsswitch.conf etc/pam.conf var/ldap
a etc/defaultdomain 1K
a etc/nsswitch.conf 2K
a etc/pam.conf 4K
a var/ldap/ 0K
a var/ldap/ldap_client_file 3K
a var/ldap/ldap_client_cred 1K
a var/ldap/cachemgr.log 4K
a var/ldap/restore/ 0k
```
5. Extract the tar file in the target guest domain.
```
root@TargetGuestDom# cd /
root@TargetGuestDom# tar xvf /etc/p2v/configs_tar_orig
x etc/defaultdomain, 11 bytes, 1 tape blocks
x etc/nsswitch.conf, 1202 bytes, 3 tape blocks
x etc/pam.conf, 3263 bytes, 7 tape blocks
x var/ldap, 0 bytes, 0 tape blocks
x var/ldap/ldap_client_file, 2935 bytes, 6 tape blocks
x var/ldap/ldap_client_cred, 204 bytes, 1 tape blocks
x var/ldap/cachemgr.log, 3469 bytes, 7 tape blocks
x var/ldap/restore, 0 bytes, 0 tape blocks
```
Consider reconfiguring other services that have a different configuration in the target environment.
There might be other services whose configuration has to be changed in the target guest domain rather than using the source machine's configuration. For example, after rebooting the target guest domain, you might see syslog messages like this example:
```
Jul  30 14:40:40 TargetGuestDom ntpdate[415]: no server suitable for synchronization found
```
This message occurs because the NTP client configuration file was restored by ldmp2vz_convert from the source system. Refer to the xntpd(1M) for further information on NTP configuration.

Some SMF services carried over from the source system OS might not run because the platform is different, for example during a sun4u to sun4v migration. In this case, disable the SMF services, for example:
```
root@TargetGuestDom# svcadm disable dcs
root@TargetGuestDom# svcadm disable oplhpd
root@TargetGuestDom# svcadm disable sckmd
```