Notification for the KSYS events

Edit online

The KSYS subsystem tracks various events that occur in the environment and saves the information in log files. The KSYS subsystem also sends emails and text notifications to the administrator if the contact information is registered on the KSYS configuration by using the ksysmgr add notify command.

You can run the following command to list all the events that can be notified:
ksysmgr query event
The events are categorized as critical errors, warning, and informational events. To query all events of a specific event type, use the following command:
ksysmgr query event type=error|warning|info

The following table lists few important events that are monitored by the KSYS:

Table 1. Notification for KSYS events
Events Event type Description Suggested actions
HMC_UNREACHABLE Critical HMC is down or not reachable  
STG_UNREACHABLE Critical Storage subsystem is down or not reachable Check the network between the KSYS node, EMC Solution Enabler, and the storage disks. Also, check whether the EMC Solution Enabler server is down.
HMC_REACHABLE Informational HMC recovered and is now reachable  
VIOS_RMC_STATE_DOWN Critical The RMC connectivity between HMC and VIOS has problems  
INSUFFICIENT_HOST_CAPACITY Critical Backup host does not have sufficient capacity to perform a successful disaster recovery failover  
VIOS_FAILURE Critical VIOS has failed  
VM_CONFIG_COLLECTION_FAILURE Critical Configuration data collection failed for the VM  
DAILY_VERIFY_FAILED Critical Daily verification has failed  
REPLICATION_FAILURE Critical Storage reports replication problem Verify the replication between the local and the remote disks.
MIRROR_RELATIONSHIP_MISSING Critical Disk has no mirror pair Create a mirror pair for the disk.
HOST_FAILURE Critical Host failure has occurred  
FILESYSTEM_SPACE_WARNING Warning File system is reaching full condition Free up some space in the /var location by removing old log files or any unwanted files.
HMC_LOGIN_FAILURE Critical HMC login failed  
DISK_VALIDATION_FAILURE Critical Disk group validation failed Investigate the disk groups and resolve the issue.
VIOS_DELETED Warning VIOS deletion has been detected  
VM_NOT_ACTIVE Informational VM is not active  
DUPLICATE_VMS Informational VM exists on multiple hosts  
VM_MOVE Informational VM has moved from one host to another  
DAILY_VERIFY_COMPLETE Informational Daily verification has completed successfully  
HOST_IN_INVALID_STATE Informational Host is in an invalid state  
VM_STORAGE_COLLECTION_FAILURE Critical Storage information collection has failed for the VM Check VIOS for more details.
VM_DISCOVERED_ON_HOST Informational A new VM is discovered in a host  
VM_DELETED_FROM_HOST Warning A VM has been deleted from a host  
VM_NOT_FOUND Critical A VM does not exist  
VM_NOT_ACTIVE Informational VM is not active  
Table 2. Site event and description
Event Description
SITE_DISCOVERY_STARTED Site discovery started
SITE_DISCOVERY_SUCCESS Site discovery is successful
SITE_VERIFY_STARTED Site verify started
SITE_VERIFY_SUCCESS Site verify is successful
SITE_MOVE_START Site move started
SITE_MOVE_SUCCESS Site move is successful
DAILY_VERIFY_STARTED Daily verify started
DAILY_VERIFY_SUCCESS Daily verify is successful
SITE_DRREHEARSAL_START Site DR rehearsal started
SITE_DRREHEARSAL_SUCCESS Site DR rehearsal is successful
Note:
  • Users might not get event notification while disaster recovery operations are in progress as the quick discovery process is blocked during the disaster recovery operation.
  • The VM_CPU_THRESHOLD_EXCEEDED event can be ignored when VM uses shared processors in uncapped mode.
  • The KSYS subsystem sends site event notifications without considering the value of the notification_level system attribute.