You can change the level of detail captured in the IBM® Spectrum Symphony
multicluster logs for the
multicluster primary and
multicluster member
clusters. By default the logging level for these logs is to show informational messages. You can
change the logger classes defined in the smc.master.log4j.properties (for the
SMCM service) and smc.proxy.log4j.properties (for the SMCP service) files, or
for a specific SMCM or SMCP service logger, using the smcadmin log command. Once
run, the log level change is effective immediately and remains in effect until you restart the host,
or until affected processes are closed.
Before you begin
To be able to change the multicluster, you must have
SMC_LOG_CONTROL permission.
Procedure
-
To change the level of detailed captured for the multicluster primary cluster
logs, run:
smcadmin log smcm -logger {smcm_all | smcm_logger} -level log_level
For example, to change the logging level for the
multicluster primary cluster to
capture debugging information for all SMCM service loggers, run:
smcadmin log smcm -logger smcm_all -level LOG_DEBUG
To change the logging level for the
multicluster primary cluster to
capture error messages for the
smc.master.daemon SMCM service logger, run:
smcadmin log smcm -logger smc.master.daemon -level LOG_ERROR
-
To change the level of detailed captured in the multicluster member cluster logs,
run:
smcadmin log smcp -logger {smcp_all | smcp_logger} -level log_level -c cluster1[,cluster2]...
For example, to change the logging level to capture debugging information for a
multicluster member cluster
(called MyCluster), for all SMCP service loggers, run:
smcadmin log smcp -logger smcp_all -level LOG_DEBUG -c MyCluster
To change the logging level to capture debugging information for two
multicluster member cluster
(called MyCluster1 and MyCluster2), to capture error messages for the
smc.proxy.daemon SMCP service logger, run:
smcadmin log smcp -logger smc.proxy.daemon -level LOG_ERROR -c MyCluster1,MyCluster2