Resolving problems reported in the Monitors field - assure_mimix - 10.0

The Monitors field located in the upper right corner of the Work with Application Groups display summarizes the status of the MIMIX monitors on the local system. Each node or system in the product configuration has MIMIX monitors which run on that system to check for specific potential problems. A status of *ACTIVE indicates that all enabled monitors on the local system are active.

Table 8 shows possible status values for the Monitors field that require user action. For a complete list of possible values, press F1 (Help).

 

Do the following:

1. Press F14 (Monitors) to display the list of monitors on the local system on the Work with Monitors display.

2. Check the Status column for status values of FAILED, FAILED/ACT, and INACTIVE.

3. If the monitor is needed on the local system as indicated in Table 9, use option 9 (Start) to start the monitor.

   Possible monitors and the nodes on which they should be active

   Monitor	When and Where Needed
   application-group-name - AGDFN status monitor Checks the statuses reported for the application group for any values of *ATTN (except for logical replication).	All nodes in the application group.
   device-CRG-name -  independent ASP switch delay monitor Checks for conditions that may require action to prevent a prolonged switch.	On the primary node for a *DEV, *GMIR, *LUN, *PPRC or *XSM data resource group entry. This monitor should be disabled on all other nodes.
   journal-name - remote journal link monitor Checks the journal message queue for indications of problems with the remote journal link. A monitor exists for both the local and remote system of the RJ link.	Primary node and the current Backup node of application groups which perform logical replication.
   application group-name - DB2 Mirror replication monitor Checks the replication status of the DB2 Mirror environment to ensure that the replication occurs between the primary nodes of the different DB2 mirror sites.	Primary node
   #MCADMDMN - cluster administration domain monitor Checks for new objects to be added to the IBM cluster administrative domain and adds a Monitored Resource Entry to the administrative domain for all objects that have been found.	All nodes of an application group whose configuration includes a cluster administrative domain
   MCSANCNN - SAN connection monitor Checks the QSYSOPR message queue for indications of problems with the fiber channel connection between a node and the SAN storage device that could prevent a switch.	All nodes of an application group which includes data resource groups of type *LUN, *GMIR or *PPRC.
   MMIASPMON - independent ASP threshold monitor Checks the QSYSOPR message queue for indications that the independent ASP threshold has been exceeded. This monitor improves the ability to detect overflow conditions that put your high availability solution at risk due to insufficient storage.	On all nodes which control an independent ASP.
   MMNFYNEWE - monitor for new object notification entries Monitors the source system for the newly created libraries, folders, or directories that are not already included or excluded for replication by a data group configuration.	Primary node when the application group is configured for logical replication.
   MQRCDIMG - MQ record image monitor This monitor is optional for environments that use Assure MIMIX IBM MQ. The monitor run a time-based event which runs the IBM MQ for IBM i command RCDMQMIMG for each active queue manager on the system.	Primary node