Configuring the call home groups automatically

All compatible nodes that have call home packages and are not yet a part of any call home groups can be redistributed into new call home groups by using the mmcallhome group auto command. All the newly created call home groups then use the global call home configuration. The following actions are run in this process:

1. The nodes that can access esupport.ibm.com and have call home packages that are installed on them are detected.
   Note: If a proxy is specified by the mmcallhome proxy change command and enabled by the mmcallhome proxy enable command, then the specified proxy is used for detecting the nodes that have access to esupport.ibm.com. If the proxy configuration is disabled, direct connections are attempted instead.
2. A minimal subset of these nodes is selected, so that all nodes, which are supposed to be distributed into groups, can be distributed into groups with a maximum recommended size of 1024 nodes.
3. New groups are created and set to use the global call home settings.

If you want to redistribute all nodes, which are currently assigned to any groups, use the --force option as shown. The use of the --force option effectively deletes all current groups before creating new ones.

mmcallhome group auto --force

If you want to manually specify the call home nodes to use for the new groups, you can use the --server option as shown:

mmcallhome group auto [--server {ServerName[,ServerName...]}]

In such cases, the following rules apply:

• The number of groups that are created is the same as the number of the specified call home nodes.
• The access to esupport.ibm.com is not checked for any call home nodes.
• Each group gets one of the specified call home nodes that are assigned to it.
• All compatible nodes are distributed between these groups.

If you want to distribute only a part of your cluster into the call home groups, you can use the --nodes option:

mmcallhome group auto --nodes {all | ChildNode1[,ChildNode2...]}