Informational events
The informational events provide information about the status of an operation.
Informational events are recorded in the event log and based on notification type, can generate notifications through email, SNMP, or syslog. Informational events are distinguished from error events, which are associated with error codes and might require service procedures. For a list of error events, see Error event IDs and error codes.
Informational events can be either notification type I (information) or notification type W (warning). An informational event report of type (W) might require user attention. Table 1 provides a list of informational events, the notification type, and the reason for the event.
| Event ID | Notification type | Description |
|---|---|---|
| 009152 | W | The system has failed to send a required email. A retry is attempted in 15 seconds. |
| 010127 | I | The usage rate for a flash drive was high, but is now within normal limits. |
| 020016 | I | Easy Tier cannot operate normally because there is not enough available capacity in the pool. |
| 050988 | I | Configuration change that is requested by the last command is completed successfully. |
| 050990 | W | Configuration change that is requested by the last command has failed. |
| 051054 | W | vCenter partition linking and async-DR policy for replicated VGs is required. |
| 052009 | W | Automatic increase of bitmap memory for policy-based replication failed. |
| 054009 | W | Admin LUN hosts for vVols exist outside the vCenter storage partition but are mapped to volumes in a partition. |
| 060011 | I | Error occurred during the recovery of the pool and some data has possibly been lost to one through to all vdisks. |
| 060012 | W | Data reduction pool space warning. |
| 062004 | I | Type conversion completed and the original copy has been deleted. |
| 071570 | I | Battery protection unavailable. |
| 071571 | I | Battery protection is temporarily unavailable; one battery is expected to be available soon. |
| 071572 | I | Battery protection is temporarily unavailable; both batteries are expected to be available soon. |
| 079600 | I | Patch installation successful |
| 079601 | I | Auto-update of a patch is disabled. |
| 085221 | I | Successful write to USB Flash Drive. |
| 086004 | I | Write to USB Flash Drive successful. |
| 086011 | I | An attempt to regenerate the internal key (rekey) has failed. |
| 088077 | I | Fibre Channel I/O port has more than the recommended active login. |
| 980221 | I | The error log is cleared. |
| 980230 | I | The SSH key was discarded for the service login user. |
| 980231 | I | Username has changed. |
| 980301 | I | Degraded or offline managed disk is now online. |
| 980310 | I | A degraded or offline storage pool is now online. |
| 980320 | I | Offline volume is now online. |
| 980321 | W | Volume is offline because of a degraded or offline storage pool. |
| 980330 | I | All nodes can see the port. |
| 980349 | I | A node has been successfully added to the cluster (system). |
| 980350 | I | The node is now a functional member of the cluster (system). |
| 980351 | I | A noncritical hardware error occurred. |
| 980352 | I | Attempt to automatically recover the offline node starting. |
| 980370 | I | Both nodes in the I/O group are available. |
| 980371 | I | One node in the I/O group is unavailable. |
| 980372 | W | Both nodes in the I/O group are unavailable. |
| 980392 | I | Cluster (system) recovery completed. |
| 980435 | W | Failed to obtain directory listing from remote node. |
| 980440 | W | Failed to transfer file from remote node. |
| 980445 | I | The migration is complete. |
| 980446 | I | The secure delete is complete. |
| 980501 | W | The virtualization amount is close to the limit that is licensed. |
| 980502 | W | The FlashCopy feature is close to the limit that is licensed. |
| 981002 | I | Fibre Channel discovery occurred; configuration changes are pending. |
| 981003 | I | Fibre Channel discovery occurred; configuration changes are complete. |
| 981004 | I | Fibre Channel discovery occurred; no configuration changes were detected. |
| 981007 | W | The managed disk is not on the preferred path. |
| 981009 | W | The initialization for the managed disk failed. |
| 981014 | W | The LUN discovery has failed. The cluster (system) has a connection to a device through this node but this node cannot discover the unmanaged or managed disk that is associated with this LUN. |
| 981015 | W | The LUN capacity equals or exceeds the maximum. Only part of the disk can be accessed. |
| 981020 | W | The managed disk error count warning threshold has been met. |
| 981022 | I | Managed disk offline imminent, offline prevention started. |
| 981025 | I | Drive firmware download completed successfully. |
| 981026 | I | Drive FPGA download completed successfully. |
| 981027 | I | Drive firmware download started. |
| 981028 | I | Drive FPGA download started. |
| 981029 | I | Drive firmware download cancelled by user. |
| 981101 | I | SAS discovery occurred; no configuration changes were detected. |
| 981102 | I | SAS discovery occurred; configuration changes are pending. |
| 981103 | I | SAS discovery occurred; configuration changes are complete. |
| 981104 | W | The LUN capacity equals or exceeds the maximum capacity. Only the first 1 PB of disk will be accessed. |
| 981105 | I | The drive format has started. |
| 981106 | I | The drive recovery was started. |
| 981110 | I | iSCSI discovery occurred, configuration changes pending. |
| 981111 | I | iSCSI discovery occurred, configuration changes complete. |
| 981112 | I | iSCSI discovery occurred, no configuration changes were detected. |
| 981113 | I | Drive erase operation started. |
| 981114 | I | Drive erase operation ended successfully. |
| 982003 | W | Insufficient virtual extents. |
| 982004 | W | The migration suspended because of insufficient virtual extents or too many media errors on the source managed disk. |
| 982007 | W | Migration has stopped. |
| 982009 | I | Migration is complete. |
| 982010 | W | Copied disk I/O medium error. |
| 982011 | W | A distributed array expansion has been suspended due to migration failures. |
| 983001 | I | The FlashCopy® operation is prepared. |
| 983002 | I | The FlashCopy operation is complete. |
| 983003 | W | The FlashCopy operation has stopped. |
| 983004 | I | Volume group clone completed. |
| 983005 | I | Volume clone completed. |
| 984001 | W | First customer data being pinned in a volume working set. |
| 984002 | I | All customer data in a volume working set is now unpinned. |
| 984003 | W | The volume working set cache mode is in the process of changing to synchronous destage because the volume working set has too much pinned data. |
| 984004 | I | Volume working set cache mode updated to allow asynchronous destage because enough customer data has been unpinned for the volume working set. |
| 984506 | I | The debug from an IERR was extracted to disk. |
| 984507 | I | An attempt was made to power on the slots. |
| 984508 | I | All the expanders on the strand were reset. |
| 984509 | I | The component firmware update paused to allow the battery charging to finish. |
| 984511 | I | The update for the component firmware was paused because the system was put into maintenance mode. |
| 984512 | I | A component firmware update is needed but is prevented from running. |
| 984514 | I | Node battery conditioning started. |
| 984515 | I | Node battery conditioning completed. |
| 985003 | W | Unable to find path to disk in the remote cluster (system) within the timeout period. |
| 986001 | W | The thin-provisioned volume copy data in a node is pinned. |
| 986002 | I | All thin-provisioned volume copy data in a node is unpinned. |
| 986010 | I | The thin-provisioned volume copy import has failed and the new volume is offline; either update the system software to the required version or delete the volume. |
| 986011 | I | The thin-provisioned volume copy import is successful. |
| 986020 | W | A thin-provisioned volume copy space warning has occurred. |
| 986030 | I | A thin-provisioned volume copy repair has started. |
| 986031 | I | A thin-provisioned volume copy repair is successful. |
| 986032 | I | A thin-provisioned volume copy validation is started. |
| 986033 | I | A thin-provisioned volume copy validation is successful. |
| 986034 | I | The import of the compressed-virtual volume copy was successful. |
| 986035 | W | A compressed-virtual volume copy space warning has occurred. |
| 986036 | I | A compressed-virtual volume copy repair has started. |
| 986037 | I | A compressed-virtual volume copy repair is successful. |
| 986038 | I | A compressed-virtual volume copy has too many bad blocks. |
| 986039 | I | A data reduction pool repair process has begun. |
| 986040 | I | A data reduction pool repair process has completed successfully. |
| 986201 | I | A medium error has been repaired for the mirrored copy. |
| 986203 | W | A mirror copy repair, using the validate option cannot complete. |
| 986204 | I | A mirror disk repair is complete and no differences are found. |
| 986205 | I | A mirror disk repair is complete and the differences are resolved. |
| 986206 | W | A mirror disk repair is complete and the differences are marked as medium errors. |
| 986207 | I | The mirror disk repair has been started. |
| 986208 | W | A mirror copy repair, using the set medium error option, cannot complete. |
| 986209 | W | A mirror copy repair, using the resync option, cannot complete. |
| 987102 | W | Node coldstarted. |
| 987103 | W | A node power-off has been requested from the power switch. |
| 987104 | I | Additional Fibre Channel ports were connected. |
| 987106 | I | Additional ethernet ports connected. |
| 987107 | I | Additional fibre channel IO ports connected. |
| 987301 | W | The connection to a configured remote cluster (system) has been lost. |
| 987302 | I | Compression is temporarily suspended. |
| 987400 | W | The node unexpectedly lost power but has now been restored to the cluster (system). |
| 988022 | I | The rebuild for an array MDisk was started. Performance may be affected, wait for rebuild to complete. |
| 988023 | I | The rebuild for an array MDisk has finished. |
| 988028 | I | Array validation started. |
| 988029 | I | Array validation complete. |
| 988100 | W | An overnight maintenance procedure has failed to complete. Resolve any hardware and configuration problems that you are experiencing on the cluster (system). If the problem persists, contact your support representative for assistance. |
| 988300 | W | An array MDisk is offline because it has too many missing members. |
| 988304 | I | A RAID array has started exchanging an array member. |
| 988305 | I | A RAID array has completed exchanging an array member. |
| 988306 | I | A RAID array needs resynchronization. |
| 988307 | I | A failed drive has been re-seated or replaced. The system has automatically configured the device. |
| 988308 | I | Distributed array MDisk rebuild started. |
| 988309 | I | Distributed array MDisk rebuild completed. |
| 988310 | I | Distributed array MDisk copyback started. |
| 988311 | I | Distributed array MDisk copyback completed. |
| 988312 | I | Distributed array MDisk initialization started. |
| 988313 | I | Distributed array MDisk initialization completed. |
| 988314 | I | Distributed array MDisk needs resynchronization. |
| 988322 | I | Block correction requests count. This is for support use only and requires no action from the user. |
| 988323 | I | Block correction requests are enabled for the drive. This is for support use only and requires no action from the user. |
| 988324 | I | Block correction requests are enabled for the array. This is for support use only and requires no action from the user. |
| 988325 | I | Block correction requests are enabled for an IO group. This is for support use only and requires no action from the user. |
| 988326 | I | Block correction requests are disabled for the drive. This is for support use only and requires no action from the user. |
| 988327 | I | Block correction requests are disabled for the array. This is for support use only and requires no action from the user. |
| 988328 | I | Block correction requests are disabled for IO group. This is for support use only and requires no action from the user. |
| 988315 | I | A distributed array has started an expansion process. |
| 988316 | I | A distributed array has completed an expansion process. |
| 988317 | I | Distributed array mdisk rebuild in place started. |
| 988318 | I | Distributed array mdisk rebuild in place completed. |
| 988319 | I | RAID Reconstruct Read attempted by DRP. |
| 988320 | I | Distributed array mdisk disaster recovery synchronize started. |
| 988321 | I | Distributed array mdisk disaster recovery synchronize completed. |
| 989001 | I | Pool space (either physical or logical) is above the threshold that the has user set through command-line interface. The threshold can be a percentage or a size with units that gets converted to a percentage. |
| 989003 | I |
NVMe drive diagnostics
Drive statistics were sent to IBM® by the call home function. |
| 989004 | I | NVMe drive format started. |
| 989005 | I | NVMe drive firmware download started. |
| 989006 | I | NVMe drive firmware download completed successfully. |
| 989008 | I | The number of concurrent NVMe Discovery associations reached the limit. Additional new associations will be rejected. |
| 989009 | I | The number of concurrent NVMe IO associations reached the limit. Additional new associations will be rejected. |
| 989010 | I | Fibre Channel adapter port re-initialized. |
| 989011 | I | NVMe drive secure erase started. |
| 989012 | I | NVMe drive secure erase successfully completed. |
| 989013 | I | NVMe drive format successfully completed. |
| 989014 | W | Fabric congestion was detected on the Fibre Channel port. The link was reset to help resolve the effects of the congestion. |
| 989015 | I | A volume name conflict was resolved. |
| 989051 | I | Two person integrity was enabled. |
| 989052 | I | Two person integrity was disabled. |
| 989055 | I | The metadata migration task was completed successfully. |
| 989061 | I | An attempt to regenerate the internal key (rekey) has failed. |
| 989062 | I | Unable to delete partnership between remote system in migration and DR linked system. |
| 989063 | I | Workload diagnostic for host. |
| 989064 | I | Replication policy removed as it conflicted with the current type of replication. |
| 989066 | I | Auto update feature downloaded. |
| 989067 | I | Feature auto updated. |
| 989068 | I | User attempted to log in with incorrect password five times. |
| 989069 | I | Consider enabling automatic user locking to improve security. |