Adding HMCs to the KSYS

Edit online

The KSYS interacts with the HMC for discovery, verification, monitoring, recovery, and cleanup operations. HMCs that are configured in both the active and backup sites provide details about the hosts and VIOS partitions that are managed by the HMCs in each site. The VM Recovery Manager DR solution cannot be implemented without configuring the HMCs. Therefore, you must provide the HMC details to the KSYS.

Note:

The HMC user, whose user name and password details are provided to the KSYS, must have hmcsuperadmin privileges with remote access enabled.
If the HMC password contains any special characters, you can enter password only by using the ksysmgr command via the command-line interface (CLI). To enter a password that contains special characters, run the following command:
```
ksysmgr add hmc HMC1 login=hscroot site=Site1
```
When you run the command, the ksysmgr command prompts you to enter the password.
```
password : ********
Re-Enter password : *******
```

To add the HMCs to a specific site, complete the following steps in the KSYS LPAR:

Add the HMC (for example, HMC name: Site1_HMC1, user name: hscroot, password: xyz123) that manages the host or hosts in the active site (Site1) by running the following command:
```
ksysmgr add hmc Site1_HMC1 login=hscroot password=xyz123 
        hostname=Site1_HMC1.testlab.ibm.com site=Site1
```
Note: If you do not want to enter the password in the command line, you can omit the password field. In this case, the ksysmgr command prompts for the password later.
Add the HMC (for example, HMC name: Site2_HMC1, user name: hscroot, password: xyz123) that manages the host or hosts in the backup site (Site2) by running the following command:
```
ksysmgr add hmc Site2_HMC1 login=hscroot password=xyz123 
        hostname=Site2_HMC1.testlab.ibm.com site=Site2
```
Repeat Step 1 and Step 2 for all the HMCs that you want to add to the KSYS.

Optional: Verify the HMCs that you added by running the following command:

ksysmgr query hmc

An output that is similar to the following example is displayed:

Name:              Site2_HMC1
Site:              Site2
Ip:                9.xx.yy.zz
Login:             hscroot

                        Managed Host List:

Host Name                               Uuid
=========                               ====
Host1_Site2                             82e8fe16-5a9f-3e32-8eac-1ab6cdcd5bcf
Host2_Site2                             74931f30-e852-3d47-b564-bd263b68f1b1
Host3_Site2                             c15e9b0c-c822-398a-b0a1-6180872c8518
Host4_Site2                             f6cbcbda-8fec-3b6e-a487-160ca75b2b84
Host5_Site2                             4ce17206-4fde-3d5a-a955-dbf222865a77
Host6_Site2                             346f184d-bace-36f5-97b5-3955c62a6929
Host7_Site2                             a977d52e-fd3a-325d-bd02-124663066cac
Host8_Site2                             ae115482-3a50-32f3-935a-7ff9be433e33
Host9_Site2                             b3880199-3b8b-3ade-b360-f76146c2d7f3
Host10_Site2                            26c7c48e-3b81-363b-85d0-e110ebc43b15
============================================================================


Name:              Site1_HMC1
Site:              Site1
Ip:                9.xx.yy.zz
Login:             hscroot


                        Managed Host List:

Host Name                               Uuid
=========                               ====
Host1_Site1                             caffee0a-4206-3ee7-bfc2-f9d2bd3e866f
Host2_Site1                             6ce366c5-f05d-3a12-94f8-94a3fdfc1319
Host3_Site1                             67ff62ec-ecb5-3ad4-9b35-0a2c75bb7fe4
============================================================================