Modifying the KSYS configuration

Edit online

Growing business requirements might need changes in your current configuration, for example, adding a specific host to your environment or modifying the attributes of an existing resource. After the VM Recovery Manager HA solution is implemented in your environment, the KSYS subsystem continues to monitor for any changes in the KSYS configuration. The KSYS subsystem scans the environment regularly and adapts to changes. However, if you want KSYS to immediately update the changes, you must run the discovery and verification operations to discover and validate the changes in the KSYS configuration.

You can change the resource attributes as shown in the following examples:

To change the host group details, run the following command:

ksysmgr modify host_group <name> <add | remove | options>
[<hosts=<host1>,<host2>...>| file=<filepath>] 
[memory_capacity=<(1-1000) | minimum | current_desired | none | default> priority=<low | medium | high>] 
[cpu_capacity=<(1-1000) | minimum | current_desired | none | default> priority=<low | medium | high>] 
[ha_disk=<ViodiskID>] 
[repo_disk=<ViodiskID>] 
[backup_repo_disk=<ViodiskID[,ViodiskID2...]> | backup_repo_disk=none] 
[ha_monitor=<enable | disable>] 
[proactiveha=<enable | disable>] 
[lpm_support=<enable | disable | none>] 
[restart_policy=<auto | advisory_mode>] 
[vm_failure_detection_speed=<fast | normal | slow>] 
[host_failure_detection_time=<90-600>] 
[ [snapshotpolicyname=<snapshot_policy_name>] | suspendsnapshotpolicy | resumesnapshotpolicy | removesnapshotpolicy ] 

modify => mod*, ch*, 
set host_group => hg, host_g* 

Note: If you specify cpu_capacity and memory_capacity together, only specify a single priority. If multiple priorities are given the latest priority value is modified. 
Note: snapshotpolicyname, suspendsnapshotpolicy, resumesnapshotpolicy options are supported for SVC storage

To update the HMC name, login credentials, or IP address, run the following command:

ksysmgr modify hmc hmcname
     [login=new_username]
     [password=new_password]
     [hostname|ip=new_hostname|new_ip]

To update the attributes of virtual machines, run the following command:

ksysmgr modify vm <vmname[,vmname2,...]> | ALL host=<hostname> | ALL host_group=<host_group_name> | file=<filepath>
[uuid=<uuid>] 
[homehost=<hostname>] 
[priority=<Low|Medium|High>] 
[ha_monitor=<enable | disable>\] \[proactiveha=<enable | disable>] 
[vm_failure_detection_speed=<fast | normal | slow>] 
[blocklist_hosts=<hostname[,hostname2...]> | [policy=<add | delete>]] 
[appmessaging=<enable | disable>] 
[poolmap=<enable | disable>] 
[vm_start_time=<(1-60) time in minutes>] 

modify => mod*, ch*, set vm => lp*, vm* 
host_group => hg, host_g*

Note: The

ksysmgr modify vm ALL
host_group=<host_group_name>

command does not work with the blocklist_hosts attribute.

To update the contact information to receive the KSYS notification, run the following command:

ksysmgr modify notify 
     oldcontact=old_username newcontact=new_username
 ksysmgr modify notify 
     oldcontact=old_email_address newcontact=new_email_address

To update the system tunable attributes, run the following command:
```
ksysmgr modify system attribute=new_value
```

Removing resources from the KSYS subsystem

You can remove the resources as shown in the following examples:

to remove a host_group user must remove all hosts from a host_group, run the following command:
```
ksysmgr delete host_group hg_name
```
If an HMC, which is included in the KSYS configuration, is not managing any hosts, you can remove the HMC from the KSYS configuration by running the following command:
```
ksysmgr delete hmc hmcname
```
To remove a host, you must first remove the host from the host group, and then remove the host by running the following command:
```
ksysmgr modify host_group <HGname> remove hosts=<hostname>
```
Remove the host by running the following command:
```
ksysmgr delete host <hostname>
```

Start and stop applications

To start an application, run the following command:

ksysmgr start app [name=<appname1,[appname2,...]>] vm=<vmname>

To stop an application, run the following command:

ksysmgr stop app [name=<appname1,[appname2,...]>] vm=<vmname>

Note: The name attribute can have multiple applications, which must belong to the same VM. If you do not provide the name of the application for the name attribute, the command will start or stop all the applications of the VM.

VM auto-discovery

VM auto-discovery is a system-level property. You can disable or enabled this property. By default, this property is enabled.

By default, the KSYS subsystem manages all VMs automatically. The VM auto-discovery property allows the KSYS subsystem to manage or unmanage the newly created VMs and undiscovered VMs.

If the VM auto-discovery property is enabled, all VMs are managed automatically. If the auto-discovery property is disabled, all the newly created VMs on the KSYS managed hosts and the undiscovered VMs (existing VMs that are not yet discovered by the KSYS subsystem) will not be managed by the KSYS subsystem.

To check whether the VM auto-discovery property is enabled or disabled to discover the resources, run the following command:
```
ksysmgr -a vm_auto_discovery query system
```
An output that is similar to the following example is displayed:
```
System-Wide Persistent Attributes
  vm_auto_discovery: enable
```
To enable the VM auto-discovery property, run the following command:
```
ksysmgr modify system vm_auto_discovery=enable
```
To disable the VM auto-discovery property, run the following command:
```
ksysmgr modify system vm_auto_discovery=disable
```

Disabling LPM operations

You can enable or disable the Live Partition Mobility (LPM) feature at the system, host group, or host level through the lpm_support tunable attribute. If disabled, the KSYS subsystem does not allow LPM operations. The lpm_support attribute is enabled by default.

To set the LPM tunable attribute at the system level, run the following command:
```
ksysmgr modify system lpm_support=<enable|disable>
```
To set the LPM tunable attribute at the host group level, run the following command:
```
ksysmgr modify hg <host_group_name> options lpm_support=<enable|disable>
```
To set the LPM tunable attribute at the host level, run the following command:
```
ksysmgr modify host <host_name> lpm_support=<enable|disable|None>
```

By default, the LPM feature is enabled at the system level. You can enable or disable the LPM feature at the system level. By default, the LPM status for host and host group is set to none. You can set LPM status as enable, disable or none at the host and host group level. If the LPM status is not modified at the host and host group level, the LPM status that is set at the system level is also applicable at the host and host group level. If the LPM status is modified at the host or host group level, the first preference is given to the LPM status that is set at the host level, then the LPM status that is set at the host group level, and then the LPM status that is set at the system level.

The KSYS subsystem checks the LPM status of host, then the LPM status of host group, and then the LPM status of system. For example, the KSYS subsystem checks the LPM status of a host, if the status is set to enable or disable, the same status is applicable to the host. If the LPM status of the host is set to none, the KSYS subsystem checks the LPM status of the host group. If the status is set to enable or disable for the host group, the same status is applicable to the host group and all the hosts within the host group that have LPM status set as none. If the LPM status of the host group is set to none, the KSYS subsystem checks the LPM status at the system level.

Failover of a managing node from one KSYS node to another KSYS node when high availability of KSYS nodes is handled by the inbuilt high availability features

Complete the following procedure to change the group leader node:

To identify the current group leader node (GL node), run the following command:

ksysmgr query cluster

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


Name:                ksys_cluster
State:               Online
Type:                HA
Ksysnodes:           node1:1:Online    (Managing node)
                     node2:2:Online
KsysState:           node1:1:Online
                     node2:2:Online

The output displays node1 as the group leader node (GL node).

To stop the VMR daemon on the group leader node (GL node), that is node1 in this example, run the following command on the group leader node (GL node):
```
stopsrc -s IBM.VMR -c
```
The process to stop the VMR daemon may take a few minutes.

To check the group leader node (GL node), run the following command on node2:

ksysmgr query cluster

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

Name:                ksys_cluster
State:               Online
Type:                HA
Ksysnodes:           node1:1:Online  
                     node2:2:Online   (Managing node)
KsysState:           node1:1:Offline
                     node2:2:Online

Now, the output displays node2 as the group leader node (GL node).

To start the IBM.VMR daemon on the first node, that is node1, run the following command:
```
startsrc -s IBM.VMR
```

To check online status of both KSYS nodes, run the following command:

ksysmgr query cluster

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

Name:               ksys_cluster
State:              Online
Type:               HA
Ksysnodes:          node1:1:Online
                    node2:2:Online  (Managing node)
KsysState:          node1:1:Online
                    node2:2:Online