The following events are available for Assure UI subscriptions that monitor Assure MIMIX for AIX instances.
The New Subscription Defaults columns in Table 2 identify whether an event is automatically added when a new subscription is created and its initial delay value. A numeric delay value specified in an event overrides the delay value specified in a subscription. New subscriptions default to a delay value of 0 minutes.
For additional information, refer to “Subscribing to instance events” in the refer to the Assure Unified Interface User’s Guide packaged with Assure MIMIX for AIX.
|
Category |
Event / Description |
Severity |
New Subscription Defaults |
OID for SNMP Trap |
|
|---|---|---|---|---|---|
| Delay After Event (min) |
Automatically Added |
||||
|
Cluster |
Clusters with action required status |
Action Required |
Use subscription value |
Yes |
.1.3.6.1.4.1.47240.1.3.0.3 |
| Checks for clusters with an overall status of action required, such as network, communication failure, or status is unknown. | |||||
|
Cluster |
Clusters with stopped status |
Stopped |
Use subscription value |
No |
.1.3.6.1.4.1.47240.1.3.0.4 |
|
Checks for clusters with an overall status of stopped. Cluster will have stopped status only when you stop the cluster services. |
|||||
|
Instance |
Cannot monitor instance. |
Action required |
Use subscription value |
Yes |
.1.3.6.1.4.1.47240.1.3.0.5 |
|
Checks for conditions that prevent the Assure UI portal from monitoring the instance, such as not being able to connect to the instance or the portal connection may not be configured correctly. There is a network error or the configuration daemon is not running. Also, you may have specified the incorrect password in the portal connection. |
|||||
|
Instance |
Detect instance problems when the Assure UI portal starts monitoring the instance. |
Action required |
0 and cannot be changed |
Yes |
.1.3.6.1.4.1.47240.1.3.0.6 |
| Event for instance problems when the Assure UI portal starts monitoring the instance. Other subscribed events, if used, provide additional monitoring. | |||||
|
Logical Volume |
Protected logical volumes size on recovery server 1 or recovery server 2 does not match production server |
Attention |
Use subscription value |
Yes |
.1.3.6.1.4.1.47240.1.3.0.11 |
|
Event for when the size of a protected logical volume on the recovery 1 or recovery server 2 does not match the size on the production server. |
|||||
|
Logical Volume |
Logical volume removed. |
Action required |
Use subscription value |
Yes |
.1.3.6.1.4.1.47240.1.3.0.19 |
|
Event for when a protected logical volume on the production server is removed. |
|||||
|
Node |
Licenses that are expired or not valid. |
Action required |
0 and cannot be changed |
Yes |
.1.3.6.1.4.1.47240.1.3.0.8 |
|
Checks for licenses that have either expired or not valid. |
|||||
|
Node |
Licenses about to expire. |
Attention |
0 and cannot be changed |
Yes |
.1.3.6.1.4.1.47240.1.3.0.7 |
|
Checks for licenses that will expire in the next 30 days. Replication will be stopped when the license expires and cannot be started until the license is updated on the server. While the Assure UI server is up and running, this event will be sent out once every 24 hours until the problem is corrected or until the license expires. Users can replace the expiring license with a valid license on the node. At the next license check interval, the warning status will be cleared. |
|||||
|
Node |
Maintenance about to expire. |
Attention |
0 and cannot be changed |
Yes. This event will also be added to all existing Assure MIMIX for AIX subscriptions automatically when the portal application is updated. |
.1.3.6.1.4.1.47240.1.3.0.10 |
|
Event for when maintenance is about to expire. Current maintenance is required for product upgrades, efixes, and product support. While the Assure UI server is up and running, this event will be sent out once every 24 hours until the problem is corrected or until the license expires. Users can replace the expiring license with a valid license on the node. At the next license check interval, the warning status will be cleared. |
|||||
|
Node |
Maintenance expired. |
Attention |
0 and cannot be changed |
Yes.This event will also be added to all existing Assure MIMIX for AIX subscriptions automatically when the portal application is updated. |
.1.3.6.1.4.1.47240.1.3.0.9 |
|
Event for when maintenance is expired. Current maintenance is required for product upgrades, efixes, and product support.While the Assure UI server is up and running, this event will be sent out once every 24 hours until the problem is corrected. Users can replace the expired license with a valid license on the node. At the next license check interval, the warning status will be cleared. |
|||||
|
Node |
Server IP address changed. |
Action required |
Use subscription value |
Yes. This event will also be added to all existing Assure MIMIX for AIX subscriptions automatically when the portal application is updated. |
.1.3.6.1.4.1.47240.1.3.0.18 |
|
Event for when the network IP address of the server does not match the configured IP address. |
|||||
|
Node |
Replication groups with stopped or partially stopped status. |
Stopped |
Use subscription value |
No |
.1.3.6.1.4.1.47240.1.3.0.16 |
|
Checks for replication groups with an overall status of stopped or partially stopped. |
|||||
|
Procedure |
Procedures with action required status. |
Action required |
Use subscription value |
Yes |
.1.3.6.1.4.1.47240.1.3.0.12 |
|
Checks for procedures with a status of action required, such as a step has failed. |
|||||
|
Procedure |
Procedures with stopped status. |
Stopped |
5 |
No |
.1.3.6.1.4.1.47240.1.3.0.13 |
|
Checks for procedures with a status of stopped and waiting for the next step to be started. |
|||||
|
Replication Group
|
Replication groups with action required status |
Action required |
Use subscription value |
Yes |
.1.3.6.1.4.1.47240.1.3.0.14 |
| Checks for replication groups with an overall status of action required, such as snapshot buffer is full, synchronization did not complete, production server rollback failed, or status is unknown. | |||||
|
Replication Group
|
Applications not being managed. |
Attention |
Use subscription value |
Yes |
1.3.6.1.4.1.47240.1.3.0.1 |
|
Checks for applications that are not being managed by the cluster. In the Clusters portlet on the Summary page use the Manage Applications action to enable cluster management of the application. |
|||||
|
Replication Group
|
Configuration initializations with action required status |
Action required |
Use subscription value |
Yes |
.1.3.6.1.4.1.47240.1.3.0.15 |
|
Checks for replication group configuration initialization with a status of action required. For example, a step during the initial configuration of a replication group or reconfiguration of a replication group failed. |
|||||
|
Replication Group |
Snapshot buffer thresholds exceeded. |
Attention |
Use subscription value |
Yes |
.1.3.6.1.4.1.47240.1.3.0.17 |
| Checks for replication backlog thresholds that have been exceeded. | |||||
|
Replication Group |
Replication backlog threshold exceeded. |
Attention |
5 |
Yes |
.1.3.6.1.4.1.47240.1.3.0.02 |
| Checks for snapshot buffer thresholds that have been exceeded. | |||||