File system manager events
The following table lists the events that are created for the Filesysmgr component.
| Event | Event Type |
Severity | Call Home | Details |
|---|---|---|---|---|
| filesystem_mgr | INFO_ADD_ENTITY | INFO | no | Message: File system {0} is managed by this node. |
| Description: A file system managed by this node was detected. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| filesystem_no_mgr | INFO_DELETE_ENTITY | INFO | no | Message: File system {0} no longer managed by this node. |
| Description: A previously managed file system is no longer managed by this node. | ||||
| Cause: A previously managed file system is not managed by this node anymore. | ||||
| User Action: N/A | ||||
| managed_by_this_node | STATE_CHANGE | INFO | no | Message: The file system {0} is managed by this node. |
| Description: This file system is managed by this node. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| qos_check_done | INFO | INFO | no | Message: The QOS check cycle did not succeed. |
| Description: The QOS check cycle did succeed. | ||||
| Cause: The QOS check cycle did succeed. | ||||
| User Action: N/A | ||||
| qos_check_ok | STATE_CHANGE | INFO | no | Message: File system {0} QOS check is OK. |
| Description: The QOS check succeeded for this file system. | ||||
| Cause: N/A | ||||
| User Action: N/A | ||||
| qos_check_warn | INFO | WARNING | no | Message: The QOS check cycle did not succeed. |
| Description: The QOS check cycle did not succeed. | ||||
| Cause: The QOS check cycle did not succeed. | ||||
| User Action: This might be a temporary issue. Check the configuration and the mmqos command output. | ||||
| qos_not_active | STATE_CHANGE | WARNING | no | Message: File system {0} QOS is enabled but throttling or monitoring is not active. |
| Description: The QOS is declared as enabled but throttling or monitoring is not active. | ||||
| Cause: The QOS is declared as enabled but throttling or monitoring is not active. | ||||
| User Action: Check configuration. | ||||
| qos_sensors_active | TIP | INFO | no | Message: The perfmon sensor GPFSQoS is active. |
| Description: The GPFSQoS perfmon sensor is active. | ||||
| Cause: The GPFSQoS perfmon sensors' period attribute is greater than 0. | ||||
| User Action: N/A | ||||
| qos_sensors_clear | TIP | INFO | no | Message: Clear any previous bad QoS sensor state. |
| Description: Clear any previous bad GPFSQoS sensor state flag. | ||||
| Cause: Clear any previous bad GPFSQoS sensor state. | ||||
| User Action: N/A | ||||
| qos_sensors_inactive | TIP | TIP | no | Message: The perfmon sensor GPFSQoS is inactive. |
| Description: The perfmon sensor GPFSQoS is not active. | ||||
| Cause: The GPFSQoS perfmon sensors' period attribute is 0. | ||||
| User Action: Set the period attribute of the GPFSQoS sensor greater than 0. Therefore, use the mmperfmon config update GPFSQoS.period=N command, where N is a number greater 0. On the other hand, you can hide this event by using the mmhealth event hide qos_sensor_inactive command. Enable the perfmon GPFSQoS sensor. | ||||
| qos_sensors_not_configured | TIP | TIP | no | Message: The QoS perfmon sensor GPFSQoS is not configured. |
| Description: The QoS perfmon sensor does not exist in the mmperfmon config show command. | ||||
| Cause: The QoS perfmonance sensor GPFSQoS is not configured in the sensors configuration file. | ||||
| User Action: Include the sensors into the perfmon configuration by using the mmperfmon config add --sensors /opt/IBM/zimon/defaults/ZIMonSensors_GPFSQoS.cfg command. For more information, see the mmperfmon command section in the 'Command Reference Guide'. | ||||
| qos_sensors_not_needed | TIP | TIP | no | Message: Qos is not configured but performance sensor GPFSQoS period is declared. |
| Description: There is an active perfmonance sensor GPFSQoS period declared. | ||||
| Cause: QoS is not configured but the perfmonance sensor GPFSQoS is active. | ||||
| User Action: Disable the perfmonance GPFSQoS sensor. | ||||
| qos_state_mismatch | TIP | TIP | no | Message: File system {0} has an enablement mismatch in QOS state. |
| Description: Mismatch between the declared QOS state and the current state. One state is enabled and the other state is not enabled. | ||||
| Cause: There is a mismatch between the declared QOS state and the current state. | ||||
| User Action: Check configuration. | ||||
| qos_version_mismatch | TIP | TIP | no | Message: File system {0} has a version mismatch in QOS state. |
| Description: There is a mismatch between the declared QOS version and the current version. | ||||
| Cause: There is a mismatch between the declared QOS version and the current version. | ||||
| User Action: Check configuration. |