List of EMS events that result in traps being sent
Technical Articles ID:
KB54125
Last Modified: 2023-04-17 11:13:34 Etc/GMT
Environment
Trellix Intrusion Prevention System (Trellix IPS)
Summary
Contents:
Click to expand the section you want to view:
1. Event ivEMSGenEventName: Cannot start control channel service
Reason: Can't start the Control channel since the EMS certificate can't be obtained
Actions: If you have a database backup file and think it's not corrupted, you can try a Restore. If a Restore doesn't work, try executing the Database Maintenance action.
Severity: Critical
2. Event ivEMSGenEventName: Cannot start control channel service
Reason: Can't start the Control Channel service since the EMS keystore can't be loaded.
Actions: If you have a database backup file and think it isn't corrupted, you can try a Restore. If a Restore doesn't work, try executing the Database Maintenance action.
Severity: Critical
3. Event ivEMSGenEventName: Failed to create command channel association
Reason: Can't generate the SNMP association for the specified Sensor.
Actions: Restart the Manager or check the Sensors operating status to make sure that the Sensors health and status are good. Or, do both.
Reason: Can't pull up Sensor configuration MIB information from the Sensor
Actions: Typically, the Manager is unable to display the Sensor in this situation, which can indicate an old software image on the Sensor. If this fault is triggered because the Sensor is temporarily unavailable, the Manager clears this fault when the Sensor is back online. If the fault persists, check to make sure that the Sensor has the latest software image compatible with the Manager Software image. If the images are incompatible, update the Sensor image via a TFTP server.
Severity: Critical
5. Event ivEMSGenEventName: Get peer DoS profile failure
Reason: Get Peer DOS profile action fails, because it can't fetch the profile from the peer Sensor.
Actions: The Manager can neither obtain the requested profile from the peer Sensor, nor can it obtain a saved valid profile. See the log for details.
Severity: Error
6. Event ivEMSGenEventName: Get peer DoS profile failure
Reason: Get Peer DOS profile action fails, because the Manager can't push the profile to the Sensor that sends the request.
Reason: The SSL decryption keys become invalid because the Sensor reinitializes itself with the Manager using a different public key.
During failover pair configuration, each Sensor has different SSL keys or different public keys. The Sensor reports that a key is invalid.
Actions: Reimport the key.
Severity: Error
8. Event ivEMSGenEventName: Sensor changed to a different model
Reason: Sensor changes to a different model number that's not compatible.
Actions: Make sure that you replace with the same Sensor model (for example, replace an I-2700 with an I-2700, not an I-4010).
Severity: Critical
9. Event ivEMSGenEventName: Sensor is unreachable
Reason: SNMP ping to the Sensor fails because of a timeout, authentication failure, or error response. This failure can be caused by a Sensor down, link down, or Sensor SNMP configuration reset.
Actions: Indicates that the Sensor can't communicate with the Manager. The connection between the Sensor and Manager is down, or the Sensor is administratively disconnected.
Troubleshoot connectivity issues:
1) Check that a connection route exists between the Manager and Sensor.
2) Check the Sensors status using the status command in the Sensor command-line interface, or ping the Sensors or the Sensor gateway to ensure connectivity to the Sensor.
This fault clears when the Manager detects the Sensor again.
Reason: Can't push down persisted SNMP MIB configuration information to the Sensor.
Actions: The Manager can't push the original Sensor configuration to the Sensor during Sensor reinitialization, possibly because the trust relationship is lost between the Manager and Sensor. This problem can also occur when a failed Sensor is replaced with a new unit, and the new unit is unable to discover its configuration information.
Reason: Can't pull up Sensor configuration MIB information from the Sensor again during a state transition from DISCONNECTED TO ACTIVE.
Actions: This fault occurs as a second part to the Sensor discovery failure fault. If the condition of the Sensor changes so that the Manager can again communicate with it, the Manager again checks to see if the Sensor discovery is successful. This fault is issued if discovery fails; thus, the Sensor is still not properly initialized. Check to make sure that the Sensor has the latest software image compatible with the Manager Software image. If the images are incompatible, update the Sensor image via a TFTP server.
Reason: Can't successfully generate the VIDS for the Sensor.
Actions: This fault generally occurs in situations where the port in question is configured incorrectly. For example, a pair of ports is configured to be in different operating modes (1A is In-line while 1B is in SPAN). Check the configuration of the port pair for inconsistencies, and then configure the port pair to run in the same operating mode.
Severity: Critical
13. Event ivEMSGenEventName: Alert channel is down
Reason: The Alert channel between the EMS and Sensor is DOWN.
Actions: This fault clears when the alert channel is back up.
Severity: Error
14. Event ivEMSGenEventName: Sensor reports that the alert channel is 'down'
Reason: Sensor reports that the Alert channel between the EMS and Sensor is DOWN, but the EMS detects the link (socket) is up in fact. This inconsistency might be caused by the channel heart beat timeout.
Actions: The Sensor typically recovers on its own. If you're receiving alerts and your Sensor is otherwise behaving normally, you can ignore this message. Determine whether trust is established between the Sensor and Manager by issuing a show command in the Sensor CLI.
Severity: Error
15. Event ivEMSGenEventName: Packet log channel is down
Reason: The Pktlog channel between the EMS and Sensor is DOWN.
Actions: This fault clears when the packet log channel is back up.
Severity: Error
16. Event ivEMSGenEventName: Sensor reports that the packet log channel is down
Reason: Sensor reports that the Pktlog channel between the EMS and Sensor is DOWN, but the EMS detects that the link (socket) is up in fact. This inconsistency might cause by the channel heartbeat timeout.
Actions: The Sensor typically recovers on its own. If you're receiving alerts and your Sensor is otherwise behaving normally, you can ignore this message. Determine whether trust is established between the Sensor and Manager by issuing a show command in the Sensor CLI.
Severity: Error
17. Event ivEMSGenEventName: Sensor is in bad health
Reason: The Sensor is in BAD health.
Actions: If this fault persists, we recommend that you perform a Diagnostic Trace and submit the trace file to Technical Support for troubleshooting.
Severity: Error
18. Event ivEMSGenEventName: Sensor not initialized
Reason: The Sensor isn't initialized. Either the Sensor just starts and some part isn't ready, or the Signature Set is missing on the Sensor.
Actions: The Sensor might have just rebooted and isn't up yet. If this situation isn't the issue, check to make sure that a signature set is present on the Sensor.
Severity: Warning
19. Event ivEMSGenEventName: Signature set download failure
Reason: Can't push down the signature segment to the Sensor. It can be caused by compiling a failure, an invalid segment, or a transfer error.
Actions: It occurs when the Manager can't push the signature set file to a Sensor. It can result from a network connectivity issue.
Reason: Can't push down SSL decryption keys to the Sensor. It can be caused by an encryption error or a transfer error.
Actions: It occurs when the Manager can't push the SSL decryption keys to a Sensor. It can result from a network connectivity issue.
Severity: Critical
21. Event ivEMSGenEventName: Sensor discovery in progress
Reason: Sensor discovery in progress.
Actions: Wait for the discovery of the Sensor to complete.
Severity: Informational
22. Event ivEMSGenEventName: Sensor reports an out-of-range configuration
Reason: Get error value back from the Sensor. Most of the cases get an out of range enumeration int. More details of the specific variable are attached at the end of the additional text.
Actions: Contact Technical Support for assistance.
Reason: User has changed the SSL enable or flow count configuration, which requires a reboot to take effect.
Actions: Reboot the Sensor to cause the SSL change to take effect.
Severity: Critical
24. Event ivEMSGenEventName: Attempt to disable failover failed
Reason: Action to disable failover on the Sensor fails. This failure might be caused by the Sensor being temporarily unavailable.
Actions: Make sure that the Sensor is online. The Manager tries again to disable failover when it detects that the Sensor is up. The fault clears when the Manager is successful.
Severity: Warning
25. Event ivEMSGenEventName: Signature segments are out of sync
Reason: The latest signature segments are only successfully pushed down to one Sensor, and the Signature files on the failover pair Sensors are out of sync.
Actions: Make sure that the Sensor is online and in good health. The Manager tries again to push the file down. The fault clears when the Manager is successful.
Severity: Warning
26. Event ivEMSGenEventName: Firewall connection status inconsistent on failover Sensor pair
Reason: The failover sensors' firewall functions are both enabled, but the actual connection statuses are inconsistent. This situation might cause the firewall behavior to be inconsistent on the failover pairs.
Actions: Make sure that both sensors of the failover pair are connected to the firewall and that both sensors are online and in good health.
Severity: Warning
27. Event ivEMSGenEventName: SSL decryption keys out of sync
Reason: The latest SSL decryption keys are only successfully pushed down to one Sensor, and the SSL decryption keys on the failover pair Sensors are out of sync.
Actions: Make sure that the Sensor is online and in good health. The Manager tries again to push the file down. The fault clears when the Manager is successful.
Severity: Warning
28. Event ivEMSGenEventName: Mailer unreachable
Reason: Mail server is unreachable.
Actions: This fault indicates that the SMTP mailer host is unreachable. It occurs when the Manager fails to send an email notification or a scheduled report. This fault clears when an attempt to send the email is successful.
Severity: Error
29. Event ivEMSGenEventName: Queue size full
Reason: The Manager alert queue has reached its maximum size.
Actions: The Manager alert queue reaches its maximum size (default 200,000 alerts), and is unable to process alerts until there's space in the queue. Alerts are being detected by your sensors faster than the Manager can process them. This situation is evidence of extremely heavy activity. Check the alerts that you're receiving to see what's causing the heavy traffic on the Sensors.
Severity: Error
30. Event ivEMSGenEventName: Unarchived, queued alert count full
Reason: Indicates that the Manager has reached the limit (default of 100,000) of alerts that can be queued for storage in the database.
Actions: Indicates that the Manager has reached the limit (default of 100,000) of alerts that can be queued for storage in the database. Alerts are being detected by your sensors faster than the Manager can process them. This situation is evidence of extremely heavy activity. Check the alerts that you're receiving to see what's causing the heavy traffic on the Sensors.
Severity: Error
31. Event ivEMSGenEventName: System startup in process; alerts being restored
Reason: Alerts buffered on the disk are being restored at system startup.
Actions: Alert Viewer might not show all alerts. Restarting the manager is required to show the restored alerts in Alert Viewer.
Severity: Warning
32. Event ivEMSGenEventName: Queue size full
Reason: The Manager packet log queue has reached its maximum size.
Actions: The Manager Packet log queue reaches its maximum size (default 200,000 packets), and is unable to process packets until there's space in the queue. Packets are being detected by your Sensors faster than the Manager can process them. This situation is evidence of extremely heavy activity. Check the packets that you're receiving to see what's causing the heavy traffic on the Sensors
Severity: Error
33. Event ivEMSGenEventName: Unarchived, queued packet log count full
Reason: Indicates that the Manager has reached the limit (default of 100,000) of packets that can be queued for storage in the database.
Actions: Indicates that the Manager reaches the limit (default of 100,000) of packets that can be queued for storage in the database. Packets are being detected by your sensors faster than the Manager can process them. This situation is evidence of extremely heavy activity. Check the packets that you're receiving to see what's causing the heavy traffic on the Sensors.
Actions: Perform maintenance operations to clean and tune the database.
Severity: Critical
36. Event ivEMSGenEventName: Dropping alerts and packet logs
Reason: Sensor beginning to drop alerts and packet logs
Actions: Perform maintenance operations to clean and tune the database or disable dropping option.
Severity: Critical
37. Event ivEMSGenEventName: Communication failure with the IntruShield Update Server
Reason: Can't communicate with the Update server.
Actions: Any connectivity issues with the Update Server generate this fault, including the DNS name resolution failure, Update Server failure, proxy server connectivity failure, and network connectivity failure. Even situations where the network cable is detached from the Manager server can generate the fault. This fault clears when communication with the Update Server succeeds.
Severity: Critical
38. Event ivEMSGenEventName: Communication failure with the proxy server
Reason: Can't communicate with the proxy server.
Actions: This fault clears when communication to the Update Server through the proxy succeeds.
Reason: Unable to create scheduled database backup.
Actions: Unable to make a scheduled backup of the Manager configuration. This fault can indicate problems such as SQL exceptions, database connectivity problems, or out-of-diskspace errors. Check your Backup configuration settings. This fault clears when a successful backup is made.
Severity: Warning
40. Event ivEMSGenEventName: Scheduled real-time update from Update Server to Manager failed
Reason: Unable to make a scheduled signature set update from the Manager to Sensor.
Actions: This fault can indicate problems with network connectivity between the Update Server and Manager, invalid update sets, or update sets that aren't properly signed. This fault clears when a signature update is applied successfully.
Severity: Error
41. Event ivEMSGenEventName: Real time Scheduler-signature set update from Manager to Sensor failed
Reason: Unable to make a scheduled update from the Manager to Sensor.
Actions: This fault can indicate problems with network connectivity between the Manager and Sensor. This fault clears when a signature update is applied successfully.
Severity: Error
42. Event ivEMSGenEventName: Scheduled update from Manager to Sensor failed
Reason: Unable to make a scheduled update from the Manager to Sensor.
Actions: This fault can indicate problems with network connectivity between the Manager and Sensor, incompatibility between the update set and the Manager software, compilation problems with the signature update set, or an invalid update set. This fault clears when an update is sent to the Sensor successfully.
Reason: Unable to access packet log tables in the database
Actions: An attempt to save packet log data to the database fails, most likely due to insufficient database capacity. Make sure that the disk space allocated to the database is sufficient, and try the operation again.
Severity: Critical
44. Event ivEMSGenEventName: Alert update failed
Reason: Unable to access alertlog tables in the database
Actions: An attempt to save alerts to the database fails, most likely due to insufficient database capacity. Make sure that the disk space allocated to the database is sufficient, and try the operation again.
Actions: This message indicates that an attempt to manually back up the database backup has failed. The most likely cause of failure is insufficient disk space on the Manager server; the backup file might be too large. Check your disk capacity to make sure that there's sufficient disk space, and try the operation again.
Severity: Informational
46. Event ivEMSGenEventName: Database backup in progress
Reason: The Manager is unable to accept more incidents from the Incident Generator.
Actions: You've reached the maximum number of incidents that can be accepted by the Manager. Delete old incidents to provide room for incoming incidents.
Reason: One or more User-Defined Signatures (UDSs) are incompatible with the current update set.
Actions: The UDS Editor indicates which signatures are incompatible. Incompatibility can result from attack or signature overlap. Edit the signature in the UDS Editor and try again.
Severity: Critical
52. Event ivEMSGenEventName: IntruShield-defined UDS overridden by signature set
Reason: One more IntruShield-defined UDS is incorporated in a new signature set and is removed from the UDS Editor.
Actions: This message is informational.
Severity: Informational
53. Event ivEMSGenEventName: UDS export to the Manager in progress
Reason: One or more UDSs are in the process of being exported from the UDS Editor to the Manager server.
Actions: This message is informational.
Severity: Informational
54. Event ivEMSGenEventName: UDS export to the Manager successful
Reason: One or more UDSs are successfully exported from the UDS Editor to the Manager server.
Actions: This message is informational.
Severity: Informational
55. Event ivEMSGenEventName: Low JVM Memory
Reason: The Manager is experiencing high memory usage. Available system memory is low.
Reason: The Audit Log capacity of the Manager is {0.EN_US} records. After this number of records is reached, the Manager overwrites the oldest records with the newest records (that is, First in First Out). This fault indicates that {1.EN_US} records are written to the audit log and that the oldest audit log records are now being overwritten. This fault is raised for every {2.EN_US} records written.
Actions: No action, this event is an indicator to inform that the audit log is overwritten.
Severity: Informational
58. Event ivEMSGenEventName: Manager shutdown was not graceful
Reason: The Manager isn't shut down gracefully. Perform database tuning to fix possible database inconsistencies.
Actions: Perform database tuning to recover from the unclean shutdown. This tuning might take a while, depending on the amount of data currently in the database.
Severity: Informational
59. Event ivEMSGenEventName: Signature set update not successful
Reason: The attempt to update the signature set on the Manager isn't successful, and thus, no signature set is available on the Manager. You must reimport a signature set before performing any action on the Manager.
Actions: A valid signature set must be present before any action can be taken in IntruShield.
Severity: Informational
60. Event ivEMSGenEventName: Sensor software image or signature set import in progress
Reason: A Sensor software image or signature set file is in the process of being imported to the Manager server.
Actions: This message is informational.
Severity: Informational
61. Event ivEMSGenEventName: Sensor software image or signature set import in progress
Reason: A Sensor software image or signature set file is in the process of being imported from the Update Server to the Manager server.
Actions: This message is informational.
Severity: Informational
62. Event ivEMSGenEventName: Sensor configuration update is in progress
Reason: A Sensor configuration update is in the process of being pushed from the Manager server to the Sensor.
Reason: Sensor software update successfully pushed from the Manager server to the Sensor.
Actions: This message is informational.
Severity: Informational
67. Event ivEMSGenEventName: Signature set update is in progress
Reason: A signature set is in the process of being pushed from the Manager server to the Sensor.
Actions: This message is informational.
Severity: Informational
68. Event ivEMSGenEventName: Signature set download successful
Reason: Signature set is successfully downloaded from the Update Server to the Manager server.
Actions: This message is informational.
Severity: Informational
69. Event ivEMSGenEventName: Update Scheduler in progress
Reason: Update Scheduler in progress
Actions: This message is informational.
Severity: Informational
70. Event ivEMSGenEventName: Scheduled signature set download from Update Server to Manager in progress.
Reason: A scheduled signature set update is in the process of downloading from the Update Server to the Manager server.
Actions: This message is informational.
Severity: Informational
71. Event ivEMSGenEventName: Scheduled signature set download from Update Server to Manager is successful.
Reason: A scheduled signature set download from the Update Server to the Manager server is successful.
Actions: This message is informational.
Severity: Informational
72. Event ivEMSGenEventName: Real-time signature file update from Manager to Sensors is in progress.
Reason: A real-time signature file update to Sensors is in progress. This action is tried after a scheduled signature set update to the Manager, and if real-time signature file updates are enabled.
Actions: This message is informational.
Severity: Informational
73. Event ivEMSGenEventName: Real-time signature file update from Manager to Sensors successful.
Reason: A real-time signature file update to Sensors is successful. This action is tried after a scheduled signature set update to the Manager, and if real-time signature file updates are enabled.
Actions: This message is informational.
Severity: Informational
74. Event ivEMSGenEventName: A scheduled signature file update from the Manager to sensors is in progress.
Reason: Scheduled signature file update from Manager to Sensors is in progress.
Actions: This message is informational.
Severity: Informational
75. Event ivEMSGenEventName: Scheduled signature file update from Manager to Sensors successful.
Reason: A scheduled signature file update from the Manager to Sensors is successful.
Actions: This message is informational.
Severity: Informational
76. Event ivEMSGenEventName: Scheduler - Signature Download from Manager To Sensor Failed
Reason: Scheduler - Signature Download from Manager To Sensor fails.
Actions: This fault can indicate problems with network connectivity between the Manager and Sensor, incompatibility between the update set and Manager software, compilation problems with the signature update set, or an invalid update set. This fault clears when an update is sent to the Sensor successfully.
Severity: Informational
77. Event ivEMSGenEventName: Sensor software image download in progress
Reason: Sensor software image is in the process of downloading from the Update Server to the Manager server.
Reason: Sensor software image is successfully downloaded from the Update Server to the Manager server.
Actions: This message is informational.
Severity: Informational
79. Event ivEMSGenEventName: Software Download from Update Server to Manager Failed
Reason: Software Download from Update Server to Manager fails.
Actions: This fault can indicate problems with network connectivity between the Update Server and Manager, invalid update sets, or update sets that aren't properly signed. This fault clears when a signature update is applied successfully.
Severity: Error
80. Event ivEMSGenEventName: No Syslog Forwarder configured
Reason: No Syslog server is configured to accept ACL logs for the Admin Domain. Configure a Syslog server for the Manager to use to forward ACL logs.
Actions: This message appears until a Syslog server has been configured for use in forwarding ACL logs.
Severity: Informational
81. Event ivEMSGenEventName: Daily scheduled report generation in progress
Reason: Daily scheduled report generation in progress.
Reason: The database tuning process is successfully completed.
Actions: This message is informational.
Severity: Informational
89. Event ivEMSGenEventName: DB Tuning Required
Reason: DB Tuning required.
Actions: Shut down IntruShield Manager and Execute DB Tuning Utility at your earliest convenience.
Severity: Warning
90. Event ivEMSGenEventName: Database archival in progress
Reason: The database archival process is in progress.
Actions: Don't try to tune the database or perform any other database activity such as a backup or restore until the archival process successfully completes.
Actions: This message is informational and indicates the status of the alert archival process, which can be any of the following:
Started
In progress
Slowing down
Stopped
Severity: Warning
93. Event ivEMSGenEventName: Data dump retrieval from peer in progress
Reason: The Data dump retrieval from peer ISM is in progress.
Actions: This message is informational.
Severity: Informational
94. Event ivEMSGenEventName: Data dump retrieval successful
Reason: The Data dump retrieval from peer ISM is completed successfully.
Actions: This message is informational.
Severity: Informational
95. Event ivEMSGenEventName: Problem retrieving the data dump from peer
Reason: There's a problem while retrieving the dump from peer, aborting the data import process.
Actions: This message is informational.
Severity: Informational
96. Event ivEMSGenEventName: Reset to standalone has been invoked; Primary Manager is in control of sensors
Reason: A "Reset to Standalone" is invoked; the Primary Manager is standalone and in control of Sensors.
Actions: This message is informational.
Severity: Informational
97. Event ivEMSGenEventName: Reset to standalone has been invoked; Secondary Manager is in control of sensors
Reason: A "Reset to Standalone" is invoked; the Secondary Manager is standalone and in control of Sensors.
Actions: This message is informational.
Severity: Informational
98. Event ivEMSGenEventName: MDR has been configured
Reason: Manager Disaster Recovery is successfully configured.
Actions: This message is informational.
Severity: Informational
99. Event ivEMSGenEventName: MDR has been canceled
Reason: Manager Disaster Recovery configuration is canceled.
Actions: This message is informational.
Severity: Informational
100. Event ivEMSGenEventName: MDR manual switchover successful; Secondary Manager is in control of sensors
Reason: Manager Disaster Recovery is initiated via a manual switchover. Secondary Manager is now in control of Sensors.
Actions: This message is informational.
Severity: Informational
101. Event ivEMSGenEventName: MDR force switch has been completed; Secondary Manager is in control of sensors
Reason: Manager Disaster Recovery is initiated via a manual switchover. Secondary Manager is now in control of Sensors.
Actions: This message is informational.
Severity: Informational
102. Event ivEMSGenEventName: MDR switchback has been completed; Primary Manager is in control of Sensors
Reason: Manager Disaster Recovery switchback is completed. Primary Manager is now in control of Sensors.
Actions: This message is informational.
Severity: Informational
103. Event ivEMSGenEventName: MDR automatic switchover has been completed; Secondary Manager is in control of Sensors
Reason: Manager Disaster Recovery switchover is completed. Secondary Manager is now in control of Sensors.
Actions: This message is informational.
Severity: Informational
104. Event ivEMSGenEventName: MDR configuration information retrieval from Primary Manager successful.
Reason: Manager Disaster Recovery Secondary Manager successfully retrieves configuration information from the Primary Manager.
Actions: This message is informational.
Severity: Informational
105. Event ivEMSGenEventName: MDR has been suspended
Reason: Manager Disaster Recovery functionality is suspended. No failover takes place while MDR is suspended.
Actions: This message is informational.
Severity: Informational
106. Event ivEMSGenEventName: MDR has been resumed
Reason: Manager Disaster Recovery functionality is resumed. Failover functionality is again available.
Actions: This message is informational.
Severity: Informational
107. Event ivEMSGenEventName: IntruShield Manager version mismatch. Primary Manager has latest version
Reason: The two Managers in an MDR configuration must have the same Manager Software version installed. The Current Manager Server software is more recent than the software of the Peer Manager.
Actions: Make sure that both Managers are running the same version of the Manager software.
Severity: Warning
108. Event ivEMSGenEventName: IntruShield Manager version mismatch. Secondary Manager has latest version
Reason: The two Managers in an MDR configuration must have the same Manager Software version installed. The Peer Manager server software is more recent than the software of the Current Manager.
Actions: Make sure that both Managers are running the same version of the Manager software.
Severity: Warning
109. Event ivEMSGenEventName: Manager is archiving the Alerts
Reason: Alert archival is in progress.
Actions: Wait for the Alert archival to complete.
Severity: Informational
110. Event ivEMSGenEventName: Manager is archiving the Packet Logs
Reason: Packet Log archival is in progress.
Actions: Wait for the Packet Log archival to complete.
Severity: Informational
111. Event ivEMSGenEventName: DB Connectivity Problems
Reason: Unable to communicate with database.
Actions: Determine whether the database service is running and connectivity is present.
Severity: Critical
112. Event ivEMSGenEventName: DB No Database Connectivity
Reason: Unable to communicate with database.
Actions: Determine whether the database service is running and connectivity is present.
Severity: Error
113. Event ivEMSGenEventName: Database System Integrity
Reason: Unable to locate the index file for the table.
Actions: Repair the corrupt DB tables.
Severity: Critical
114. Event ivEMSGenEventName: Unable To Clean Alerts And Packet Logs
Reason: Unable To Clean Alerts And Packet Logs.
Actions: Check the database; the Reason for the error is reported in the logs
