Call home configuration changes to be made while upgrading to IBM Storage Scale 5.0.x from IBM Storage Scale 4.2.1

When you upgrade from IBM Storage Scale 4.2.1 to IBM Storage Scale 5.0.0 or later, the existing group configuration will be incompatible with the new format.

Follow one of the given methods to deploy the existing group configuration after an upgrade:

If the existing call home groups do not need to be saved, you can use the mmcallhome group auto --force command to automatically delete all the current groups, and create new groups with the necessary configuration.
If you want to save the existing call home group configuration, follow the given steps:
1. Find the current call home group configuration by using the mmcallhome group list command.
2. Delete all listed call home groups by using the mmcallhome group delete <groupName> command.
3. Add all the call home groups that were listed in step 1, by using the following command:
```
mmcallhome group add GroupName server [--node {all | ChildNode[,ChildNode...]}]
```
4. Set the new groups to track the global settings.
  1. Run the mmcallhome capability list, mmcallhome proxy list, or mmcallhome schedule list commands to view the current global settings and default settings for the new groups.
    The system displays output similar to this:
```
[root@g5001-21 ~]# mmcallhome capability list
group    callHomeNode            status
-------- ----------------------- ----------
global    ---                    enabled
g1       g5001-21.localnet.com   disabled
g2       g5001-22.localnet.com   disabled
```
  2. For each group, execute the mmcallhome capability, mmcallhome proxy, the mmcallhome schedule commands to configure the system with the existing settings available in the global field.
    After each change for each group, the corresponding group entry will disappear from the list command output. Therefore, the new group uses the global value for their setting. The system displays output similar to this:
```
[root@g5001-21 ~]# mmcallhome capability list
group    callHomeNode            status
-------- ----------------------- ----------
global    ---                    enabled
g1       g5001-21.localnet.com   disabled
g2       g5001-22.localnet.com   disabled
```
    Change the capability to enabled for the group g1. The g1 group is set to use the global value, and is not listed in the output of the mmcallhome capability list command anymore, as shown in the sample output:
```
[root@g5001-21 ~]# mmcallhome capability enable accept
Call home enabled has been set to true

Additional messages:
License acceptance specified on command line. Callhome enabled.
[root@g5001-21 ~]# mmcallhome capability list
group    callHomeNode            status
-------- ----------------------- ----------
global    ---                    enabled
g2       g5001-22.localnet.com   disabled
```
    After this procedure is successfully completed, the mmcallhome capability list, mmcallhome proxy list, and mmcallhome schedule list commands must list only one global set of values.