Local cache events

The following table lists the events that are created for the Local Cache component.

Table 1. Events for the Local cache component
Event Event
Type
Severity Call Home Details
lroc_buffer_desc_autotune_tip TIP TIP no Message: For optimal LROC tuning, based on average cached data block sizes of {0} in previously observed workloads, a value of {1} for maxBufferDescs configuration on this node is recommended.
Description: Not enough buffer descriptors available for optimal LROC performance.
Cause: For optimal LROC performance, based on average cached data block sizes calculated, a larger amount of buffer descriptors for this node is recommended.
User Action: Run the mmchconfig maxBufferDescs={recommendedBufferDescs} command. After setting the maxBufferDescs setting to new limit, run the mmshutdown or mmstartup for changes to take effect.
lroc_clear_tips STATE_CHANGE
HEALTHY
INFO no Message: LROC is healthy.
Description: Clear TIP events from LROC.
Cause: N/A
User Action: N/A
lroc_daemon_idle STATE_CHANGE
DEGRADED
WARNING no Message: LROC is not running.
Description: LROC daemon check reported that it is in an idle state, but local cache disks are configured.
Cause: LROC disks are configured, but the LROC daemon is currently idle, which can be a valid transitional state.
User Action: N/A
lroc_daemon_running STATE_CHANGE
HEALTHY
INFO no Message: LROC is normal.
Description: LROC daemon check reported that it is running.
Cause: N/A
User Action: N/A
lroc_daemon_shutdown STATE_CHANGE
DEGRADED
WARNING no Message: LROC is down.
Description: LROC daemon check reported that it is in a shutdown state.
Cause: The result of checking the status of the LROC daemon reported that it is down.
User Action: N/A
lroc_daemon_unknown_state STATE_CHANGE
DEGRADED
WARNING no Message: LROC status cannot be determined.
Description: LROC daemon check reported that it is in an unknown state.
Cause: The result of checking the status of the LROC daemon reported that it is in an unknown state.
User Action: N/A
lroc_disk_failed STATE_CHANGE
FAILED
ERROR no Message: LROC {0} device is not OK.
Description: Local cache disk is defined, but is not configured with LROC.
Cause: The result of checking the configured local cache device was not OK.
User Action: Check the physical status of the LROC device, and the LROC configuration by using the mmlsnsd and mmdiag commands.
lroc_disk_found ADD_ENTITY INFO no Message: The local cache disk {0} was found.
Description: A local cache disk was detected.
Cause: A local cache disk was detected.
User Action: N/A
lroc_disk_normal STATE_CHANGE
HEALTHY
INFO no Message: LROC {0} device is normal.
Description: Local Cache device check is OK.
Cause: N/A
User Action: N/A
lroc_disk_unhealthy STATE_CHANGE
DEGRADED
WARNING no Message: LROC {0} device is not OK.
Description: Local cache disk is defined, but LROC daemon is not configured to use it.
Cause: The result of checking the configured local cache device was not OK.
User Action: Check the local cache configuration by using the mmlsnsd and mmdiag commands.
lroc_disk_vanished DEL_ENTITY INFO no Message: The disk {0} vanished.
Description: A previously declared local cache disk was not detected.
Cause: A local cache disk is not in use, which can be a valid situation.
User Action: N/A
lroc_sensors_active TIP INFO no Message: The GPFSLROC performance sensor is active.
Description: The GPFSLROC performance is active.
Cause: The GPFSLROC performance sensors' period attribute is greater than 0.
User Action: N/A
lroc_sensors_clear STATE_CHANGE
HEALTHY
INFO no Message: Clear any previous bad GPFSLROC sensor state.
Description: Clear any previous bad GPFSLROC sensor state flag.
Cause: N/A
User Action: N/A
lroc_sensors_inactive TIP TIP no Message: The GPFSLROC performance sensor is inactive.
Description: The GPFSLROC performance sensor is not active.
Cause: The GPFSLROC performance sensors' period attribute is 0.
User Action: Enable the GPFSLROC performance sensor. Set the period attribute of the GPFSLROC sensor greater than 0 (default is 10). Therefore, use the mmperfmon config update GPFSLROC.period=N command, where 'N' is a natural number greater 0. On the other hand, you can hide this event by using the mmhealth event hide lroc_sensors_inactive command.
lroc_sensors_not_configured TIP TIP no Message: The GPFSLROC performance sensor is not configured.
Description: The GPFSLROC performance sensor does not exist in the mmperfmon config show command.
Cause: The GPFSLROC performance sensor is not configured in the sensors configuration file.
User Action: Include the GPFSLROC sensors into the performance monitoring configuration by using the mmperfmon config update --config-file InputFile command. The default file is /opt/IBM/zimon/defaults/ZIMonSensors_GPFSLROC.cfg. An example for the configuration file can be found in the mmperfmon command section in the Command Reference Guide.
lroc_sensors_not_needed TIP TIP no Message: LROC is not configured, but performance sensor GPFSLROC period is declared.
Description: There is an active performance sensor GPFSLROC period declared.
Cause: LROC is not configured, but the performance sensor GPFSLROC is active.
User Action: Disable the GPFSLROC performance sensor. Set the period attribute of the GPFSLROC sensor to 0. Therefore, use the mmperfmon config update GPFSLROC.period=0 command. On the other hand, you can hide this event by using the mmhealth event hide lroc_sensors_not_needed command.
lroc_set_buffer_desc_tip TIP TIP no Message: This node has LROC devices with a total capacity of {0} GB. Optimal LROC performance requires setting the maxBufferDescs configuration option. The value of desired buffer descriptors for this node is '{1}', based on assumed 4 MB data block size.
Description: Not enough buffer descriptors are available for optimal LROC performance.
Cause: The maxBufferDescs configuration setting was not set to a value. For optimal LROC performance, IBM Storage Scale daemon requires more buffer descriptors than the default.
User Action: Run the mmchconfig maxBufferDescs={desiredBufferDescs} command. After setting the maxBufferDescs setting to new limit, run the mmshutdown or the mmstartup command for changes to take effect.