AFM events

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

Table 1. Events for the AFM component
Event Event Type Severity Message Description Cause User Action
afm_fileset_found INFO_ADD_ENTITY INFO The afm fileset {0} was found. An AFM fileset was detected. An AFM fileset was detected. This is detected through the appearance of the fileset in the mmdiag --afm output. N/A
afm_fileset_vanished INFO_DELETE_ENTITY INFO The afm fileset {0} has vanished. An AFM fileset is not in use anymore. An AFM fileset is not in use anymore. This is detected through the absence of the fileset in the 'mmdiag --afm' output. N/A
afm_cache_up STATE_CHANGE INFO The AFM cache fileset {0} is active. The AFM cache is up and ready for operations. The AFM cache shows 'Active' or 'Dirty' as status in mmdiag --afm. This is expected and shows, that the cache is healthy. N/A
afm_cache_disconnected STATE_CHANGE WARNING Fileset {0} is disconnected. The AFM cache fileset is not connected to its home server. Shows that the connectivity between the MDS (Metadata Server of the fileset) and the mapped home server is lost. The user action is based on the source of the disconnect. Check the settings on both sites - home and cache. Correct the connectivity issues. The state should change automatically back to active after solving the issues.
afm_cache_dropped STATE_CHANGE ERROR Fileset {0} is in Dropped state. The AFM cache fileset state moves to Dropped state. An AFM cache fileset state moves to dropped due to different reasons like recovery failures, failback failures, etc.

There are many different reasons why the cache might go into the Dropped state. Some depend on previous cache states or what the user did before. Those different reasons and their steps to fix the issue can be found in Monitoring fileset states for AFM DR.
afm_cache_expired INFO ERROR Fileset {0} in {1}-mode is now in Expired state. Cache contents are no longer accessible due to time expiration. Cache contents are no longer accessible due to time expiration. N/A
afm_failback_complete STATE_CHANGE WARNING The AFM cache fileset {0} in {1}-mode is in FailbackCompleted state. The independent-writer failback is finished. The independent-writer failback is finished, and needs further user actions. The administrator must run the mmafmctl failback --stop to move the IW cache to Active state.
afm_failback_running STATE_CHANGE WARNING The AFM cache fileset {0} in {1}-mode is in FailbackInProgress state. A failback process on the independent-writer cache is in progress. A failback process has been initiated on the independent-writer cache and is in progress. No user action is needed at this point. After completion the state will automatically change into the FailbackCompleted state.
afm_failover_running STATE_CHANGE WARNING The AFM cache fileset {0} is in FailoverInProgress state. The AFM cache fileset is in the middle of a failover process. The AFM cache fileset is in the middle of a failover process. No user action is needed at this point. The cache state is moved automatically to Active when the failover is completed.
afm_flush_only STATE_CHANGE WARNING The AFM cache fileset {0} is in FlushOnly state. Indicates that operations are queued but have not started to flush to the home server. Indicates that the operation of queuing is finished but flushing to the home server did not start yet. This state will automatically change and needs no user action.
afm_cache_inactive STATE_CHANGE WARNING The AFM cache fileset {0} is in Inactive state Initial operations are not triggered by the user on this fileset yet. The AFM fileset is in 'Inactive' state until initial operations on the fileset are triggered by the user. Trigger first operations e.g with the mmafmctl prefetch command.
afm_failback_needed STATE_CHANGE ERROR The AFM cache fileset {0} in {1}-mode is in NeedFailback state. A previous failback operation could not be completed and needs to be rerun again. This state is reached when an previously initialized failback was interrupted and was not completed. Failback automatically gets triggered on the fileset. The administrator can manually rerun a failback with the mmafmctl failback command.
afm_resync_needed STATE_CHANGE WARNING The AFM cache fileset {0} in {1}-mode is in NeedsResync state. The AFM cache fileset detects some accidental corruption of data on the home server. The AFM cache fileset detects some accidental corruption of data on the home server. Use the mmafmctl resync command to trigger a resync. The fileset moves automatically to the Active state afterwards.
afm_queue_only STATE_CHANGE INFO The AFM cache fileset {0} in {1}-mode is in QueueOnly state. The AFM cache fileset is in the process of queueing changes. These changes are not flushed yet to home. The AFM cache fileset is in the process of queueing changes. N/A
afm_cache_recovery STATE_CHANGE WARNING The AFM cache fileset {0} in {1}-mode is in Recovery state. In this state the AFM cache fileset recovers from a previous failure and identifies changes that need to be synchronized to its home server. A previous failure triggered a cache recovery. This state will be automatically changed back to Active when the recovery is finished.
afm_cache_unmounted STATE_CHANGE ERROR The AFM cache fileset {0} is in Unmounted state. The AFM cache fileset is in an Unmounted state because of issues on the home site. The AFM cache fileset will be in this state if the home server’s NFS-mount is not accessible, if the home server’s exports are not exported properly or if the home server’s export does not exist. Resolve issues on the home server's site. Later this state will change automatically.
afm_recovery_running STATE_CHANGE WARNING AFM fileset {0} is triggered for recovery start. A recovery was started on this AFM fileset. A recovery process was started on this AFM cache fileset. N/A
afm_recovery_finished STATE_CHANGE INFO A recovery process ended for the AFM cache fileset {0}. A recovery process has ended on this AFM fileset. A recovery process has ended on this AFM cache fileset. N/A
afm_fileset_expired INFO WARNING The contents of the AFM cache fileset {0} are expired. The AFM cache fileset contents are expired. The contents of a fileset expire either as a result of the fileset being disconnected for the expiration timeout value, or when the fileset is marked as expired using the AFM administration commands. This event is triggered through an AFM callback. N/A
afm_fileset_unexpired INFO WARNING The contents of the AFM cache fileset {0} are unexpired. The AFM cache fileset contents are unexpired. The contents of these filesets are unexpired, and now available for operations. This event is triggered when the home gets reconnected and cache contents become available, or the administrator runs the mmafmctl unexpire command on the cache fileset. This event is triggered through an AFM callback. N/A
afm_queue_dropped STATE_CHANGE ERROR The AFM cache fileset {0} encountered an error synchronizing with its remote cluster. The AFM cache fileset encountered an error synchronizing with its remote cluster. It cannot synchronize with the remote cluster until AFM recovery is executed. This event occurs when a queue is dropped on the gateway node. Initiate® I/O to trigger recovery on this fileset.
afm_recovery_failed STATE_CHANGE ERROR AFM recovery on fileset {0} failed with error {1}. AFM recovery failed. AFM recovery failed. Recovery will be retried on next access after the recovery retry interval (OR). Manually resolve known problems and recover the fileset.
afm_rpo_miss INFO INFO AFM RPO miss on fileset {0} The primary fileset is triggering RPO snapshot at a given time interval. The AFM RPO (Recovery Point Objective) MISS event can occur if a RPO snapshot is missed due to network delay or failure of its creation on the secondary site. No user action is required. Failed RPOs are re-queued on the primary gateway and retried at the secondary site.
afm_prim_init_fail STATE_CHANGE ERROR The AFM cache fileset {0} is in PrimInitFail state. The AFM cache fileset is in PrimInitFail state. No data will be moved from the primary to the secondary fileset. This rare state appears if the initial creation of psnap0 on the primary cache fileset failed.
  1. Check if the fileset is available, and exported to be used as primary.
  2. The gateway node should be able to access this mount.
  3. The primary id should be setup on the secondary gateway.
  4. It might also help to use the mmafmctl converToPrimary command on the primary fileset again.
afm_prim_init_running STATE_CHANGE WARNING The AFM primary cache fileset {0} is in PrimInitProg state. The AFM cache fileset is synchronizing psnap0 with its secondary AFM cache fileset. This AFM cache fileset is a primary fileset and synchronizing the content of psnap0 to the secondary AFM cache fileset. This state will change back to Active automatically when the synchronization is finished.
afm_cache_suspended STATE_CHANGE WARNING AFM fileset {0} was suspended. The AFM cache fileset is suspended. The AFM cache fileset is in Suspended state. Run the mmafmctl resume command to resume operations on the fileset.
afm_cache_stopped STATE_CHANGE WARNING The AFM fileset {0} was stopped. The AFM cache fileset is stopped. The AFM cache fileset is in Stopped state. Run the mmafmctl restart command to continue operations on the fileset.
afm_sensors_active TIP HEALTHY The AFM perfmon sensors are active. The AFM perfmon sensors are active. This event's monitor is only running once an hour. The AFM perfmon sensors' period attribute is greater than 0. N/A
afm_sensors_inactive TIP TIP The following AFM perfmon sensors are inactive: {0}. The AFM perfmon sensors are inactive. This event's monitor is only running once an hour. The AFM perfmon sensors' period attribute is 0. Set the period attribute of the AFM sensors greater than 0. Use the command 
mmperfmon config 
update 
SensorName.period=N
, where SensorName is one of the AFM sensors' name, and N is a natural number greater 0. You can also hide this event by using the mmhealth event hide afm_sensors_ inactive command.
afm_fileset_created INFO INFO AFM fileset {0} was created. An AFM fileset was created. An AFM fileset was created. N/A
afm_fileset_deleted INFO INFO AFM fileset {0} was deleted. An AFM fileset was deleted. An AFM fileset was deleted. N/A
afm_fileset_linked INFO INFO AFM fileset {0} was linked. An AFM fileset was linked. An AFM fileset was linked. N/A
afm_fileset_unlinked INFO INFO AFM fileset {0} was unlinked. An AFM fileset was unlinked. An AFM fileset was unlinked. N/A
afm_fileset_changed INFO INFO AFM fileset {0} was changed An AFM fileset was changed. An AFM fileset was changed. N/A
afm_sensors_not_configured TIP TIP The AFM perfmon sensor {0} is not configured. The AFM perfmon sensor does not exist in mmperfmon config show The AFM perfmon sensor is not configured in the sensors configuration file. Include the sensors into the perfmon configuration through the mmperfmon config update --config-file InputFile command. An example for the configuration file can be found in the mmperfmon command page.
Parent topic: Events