Call home configuration examples
The following section gives some examples of the call home configuration.
Until IBM Spectrum Scale 4.2.3.7, each call home group had its own configuration, which had to be configured and managed separately. All call home nodes with the release version between 4.2.3.7 to 5.0.0.x are set to use global call home settings, after the first change of the corresponding setting from the default value. The change of values happens automatically if the groups are created using the mmcallhome group auto command.
For all call home nodes with IBM Spectrum Scale version 5.0.1.0 or later, the call home nodes are automatically set to use the global call home configuration upon their creation.
For the following use cases we assume the following customer information:
- Customer name: User1
- Customer ID: 123456
- E-mail: customer@ibm.com
- Country-code: JP
Use Case 1: To automatically create call home groups for all Linux nodes in the cluster where call home packages are installed, and enable all call home features.
Note: For this use case, we assume the following:
- Call home has not been configured before.
- Some of the nodes have a direct connectivity to esupport.ibm.com.
- Automatic daily and weekly data collection is to be enabled.
- Set the customer
information:
[root@g5001-21 ~]# mmcallhome info change --customer-name User1 --customer-id 123456 --email customer@ibm.com --country-code JP Call home country-code has been set to JP Call home customer-name has been set to User1 Call home customer-id has been set to 123456 Call home email has been set to customer@ibm.com
- Enable the daily and weekly
schedule:
[root@g5001-21 ~]# mmcallhome schedule add --task DAILY Call home daily has been set to enabled [root@g5001-21 ~]# mmcallhome schedule add --task WEEKLY Call home weekly has been set to enabled
- Enable call home to actually send
data:
[root@g5001-21 ~]# mmcallhome capability enable By accepting this request, you agree to allow IBM and its subsidiaries to store and use your contact information and your support information anywhere they do business worldwide. For more information, please refer to the Program license agreement and documentation. If you agree, please respond with "accept" for acceptance, else with "not accepted" to decline. (accept / not accepted) accept Call home enabled has been set to true Additional messages: License was accepted. Callhome enabled.
- Create the call home groups
automatically:
[root@g5020-31 ~]# mmcallhome group auto [I] Analysing the cluster... [I] Creating <1> new call home groups: [I] Call home child nodes = g5020-31.localnet.com,g5020-32.localnet.com,g5020-34.localnet.com [I] Call home group autoGroup_1 has been created [I] Nodes without call home: <1> (g5020-33.localnet.com) [I] Updating call home node classes... g5020-32.localnet.com: QOS configuration has been installed and broadcast to all nodes. g5020-32.localnet.com: QOS configuration has been installed and broadcast to all nodes. [I] The automatic group creation completed successfully.
Use Case 2: To distribute all Linux nodes in the cluster where call home packages are installed into two call home groups, and set the nodes g5001-21 and g5001-22 as their call home nodes.
Note: For this use case, we assume the following:
- Call home has not been configured before.
- Both the call home nodes require an authenticated proxy.
- Enable only weekly data collection.
- Set the customer
information:
[root@g5001-21 ~]# mmcallhome info change --customer-name User1 --customer-id 123456 --email customer@ibm.com --country-code JP Call home country-code has been set to JP Call home customer-name has been set to User1 Call home customer-id has been set to 123456 Call home email has been set to customer@ibm.com
- Enable the weekly
schedule:
[root@g5001-21 ~]# mmcallhome schedule add --task WEEKLY Call home weekly has been set to enabled
- Define the proxy settings and enable
proxy:
[root@g5001-21 ~]# mmcallhome proxy change --proxy-location 192.168.0.10 --proxy-port 5085 --proxy-username clusteradmin --proxy-password MyPass Call home proxy-port has been set to 5085 Call home proxy-username has been set to clusteradmin Call home proxy-password has been set to MyPass Call home proxy-location has been set to 192.168.0.10 [root@g5001-21 ~]# mmcallhome proxy enable --with-proxy-auth Call home proxy-enabled has been set to true Call home proxy-auth-enabled has been set to true
- Enable call home to send
data:
[root@g5001-21 ~]# mmcallhome capability enable By accepting this request, you agree to allow IBM and its subsidiaries to store and use your contact information and your support information anywhere they do business worldwide. For more information, please refer to the Program license agreement and documentation. If you agree, please respond with "accept" for acceptance, else with "not accepted" to decline. (accept / not accepted) accept Call home enabled has been set to true Additional messages: License was accepted. Callhome enabled.
- Create the call home groups automatically, while specifying the call home
nodes:
[root@g5020-31 ~]# mmcallhome group auto --server g5020-31,g5020-32 [I] Analysing the cluster... [I] Creating <2> new call home groups: [I] Call home child nodes = g5020-31.localnet.com,g5020-34.localnet.com [I] Call home group autoGroup_1 has been created [I] Call home child nodes = g5020-32.localnet.com [I] Call home group autoGroup_2 has been created [I] Nodes without call home: <1> (g5020-33.localnet.com) [I] Updating call home node classes... QOS configuration has been installed and broadcast to all nodes. QOS configuration has been installed and broadcast to all nodes. [I] The automatic group creation completed successfully.
Use Case 3: To automatically create call home groups for all Linux nodes in the cluster where call home packages are installed, but disable the scheduled data collection.
Note: For this use case, we assume the following:
- Call home has been configured before, but must be reconfigured. Ensure that the old settings are removed, and the old groups are deleted.
- Both the call home nodes require an authenticated proxy.
- Neither weekly nor daily data collection must be enabled, as data upload is only be done on demand. For example, in case of PMRs.
- Set the customer
information:
[root@g5001-21 ~]# mmcallhome info change --customer-name User1 --customer-id 123456 --email customer@ibm.com --country-code JP Call home country-code has been set to JP Call home customer-name has been set to User1 Call home customer-id has been set to 123456 Call home email has been set to customer@ibm.com
- Disable the proxy
configuration:
[root@g5001-21 ~]# mmcallhome proxy disable Call home proxy-enabled has been set to false Call home proxy-auth-enabled has been set to false
- Disable the task
schedule:
[root@g5001-21 ~]# mmcallhome schedule delete --task DAILY Call home daily has been set to disabled [root@g5001-21 ~]# mmcallhome schedule delete --task WEEKLY Call home weekly has been set to disabled
- Enable call home to send data when
needed:
[root@g5001-21 ~]# mmcallhome capability enable By accepting this request, you agree to allow IBM and its subsidiaries to store and use your contact information and your support information anywhere they do business worldwide. For more information, please refer to the Program license agreement and documentation. If you agree, please respond with "accept" for acceptance, else with "not accepted" to decline. (accept / not accepted) accept Call home enabled has been set to true Additional messages: License was accepted. Callhome enabled.
- Create the call home groups automatically, while removing all previously existing
groups:
[root@g5020-31 ~]# mmcallhome group auto --force [I] Analysing the cluster... [I] Deleting old call home groups (--force mode) [I] Creating <1> new call home groups: [I] Call home child nodes = g5020-31.localnet.com,g5020-32.localnet.com,g5020-34.localnet.com [I] Call home group autoGroup_1 has been created [I] Nodes without call home: <1> (g5020-33.localnet.com) [I] Updating call home node classes... QOS configuration has been installed and broadcast to all nodes. QOS configuration has been installed and broadcast to all nodes. [I] The automatic group creation completed successfully.