Network Security Platform/Trellix Intrusion Prevention System system fault messages
Technical Articles ID:
KB55037
Last Modified: 2022-12-09 05:20:33 Etc/GMT
Last Modified: 2022-12-09 05:20:33 Etc/GMT
Environment
Trellix Intrusion Prevention System
Summary
Severity: Critical
| Fault | Severity | Description or Cause | Action | AutoCleared |
| Critical | An attempt to save alerts to the database fails. It's caused by insufficient database capacity. |
Make sure that the disk space allocated to the database is sufficient, and then try the operation again. | N | |
| Critical | The Manager's certificate is unavailable. This condition indicates database corruption. | If you have a clean database backup, you can try a Restore. If the Restore doesn't work, you might need to manually repair the database. Contact Technical Support. | N | |
| Critical | The Manager's key file is unavailable and possibly corrupted. This fault indicates a database corruption. | If you have a clean database backup, you can try a Restore. If the Restore doesn't work, you might need to manually repair the database. Contact Technical Support. | N | |
| Critical | The Manager is unable to communicate with the Update Server. Any connectivity issues with the update server generate this fault, including failure of DNS name resolution, Update Server, proxy server connectivity, network connectivity, or situations where the network cable is detached from the Manager server. |
This fault clears when communication with the Update Server succeeds. If your Manager is connected to the internet, make sure it has connectivity to the internet. Contact Technical Support if you lose your Update Server authentication information. |
Y | |
| Critical | The Manager is unable to communicate with the proxy server. This fault can occur only when the Manager is configured to communicate with a proxy server. | This fault clears when communication to the Update Server through the proxy succeeds. | Y | |
| Critical | A manual attempt to back up the database fails. | This condition can indicate insufficient disk space for storage of the backup file. Check your disk capacity and clear enough space to accommodate the backup file, and then try the backup again. | N | |
| Critical | The Manager isn't communicating with the database; the alert and packet log queues are full. | Perform maintenance operations to clean and tune the database. | N | |
| Critical | As with the Approaching alert capacity threshold error below, this message indicates the percentage of space occupied by alerts in the database. This message is displayed after you exceed the alert threshold specified in the Manager. | Perform maintenance operations to clean the database. Delete unnecessary alerts, such as alerts older than a specific number of days. Failure to create more space might cause undesirable behavior in the Manager. |
N | |
| Critical | This fault indicates a failure to create a secure connection between the Manager and Sensor. This fault is caused by loss of synchronicity between the system time of the Manager Server and Sensor. It also indicates that the Sensor isn't completely online after a reboot. | Restart the Manager. Check the Sensor's operating status and make sure that the Sensor's health and status is good. |
Y | |
| Critical | Communication times out between the Fail Open Controller in the Sensor's Compact Flash port and the Fail Open Control Module. This situation causes the Sensor to move to Bypass mode and traffic to bypass the Sensor. | This fault clears automatically when communication resumes between the Fail Open Controller and Fail Open Control Module. | Y | |
| Critical | This fault indicates whether the Sensor peer is up or down. | This fault clears automatically when the Sensor peer is up. | Y | |
| Critical | One or more of the fans inside the Sensor fails. | If a fan isn't operational, Technical Support strongly recommends turning off the Sensor and contacting Technical Support to schedule a replacement unit. In the meantime, you can use an external fan (blowing into the front of the Sensor) to prevent the Sensor from overheating until the replacement is complete. |
Y | |
| Critical | The connectivity between the Sensor and firewall is down. This fault can occur in situations where, for example, the firewall system is down, or the network is experiencing problems. | Ping the firewall to see whether the firewall is available. Contact your IT department to troubleshoot connectivity issues. This fault clears when communication is re-established. |
Y | |
| Critical | The Sensor is configured to operate with an external Fail-Open Module hardware component, but can't detect the hardware. | This error applies only to Sensors running in in-line mode with a gigabit port in fail-open mode (using the external Fail Open Module). When this fault is triggered, the port is in bypass mode and sends another fault of that nature to the Manager. When an appropriate configuration is sent to the Sensor (either the hardware is discovered or the configuration changes), the Sensor begins to operate in in-line-fail open mode. | Y | |
| Critical | A user-defined signature (UDS) is incompatible with the current update set. | You need to edit your existing UDS attacks to make them conform to the new signature set definitions. Bring up the UDS Editor (Policies, Policies, UDS) and manually perform the edit or validation. This fault clears when a subsequent UDS compilation succeeds. |
N | |
| Critical | The Sensor detects that a particular SSL decryption key is no longer valid; for example, it might be failing to decrypt traffic. | Reimport the key, which is identified within the error message. The fault clears itself after the key is determined to be valid. | Y | |
| Critical | Indicates that your license is about to expire; this fault first appears seven days before expiration. | Contact Technical Support for a current license. This fault clears when the license is current. |
N | |
| Critical | Indicates that your license has expired. | Contact Technical Support for a current license. This fault clears when the license is current. |
N | |
| Critical | The link between a Monitoring port on the Sensor and the device to which it's connected is down, and communication is unavailable. The fault indicates which port is affected. | Contact your IT department to troubleshoot connectivity issues. Check the cabling of the specified Monitoring port and the device connected to it. Check the speed and duplex mode of the connection to the switch or router to ensure parameters such as port speed and duplex mode are set correctly. Check the power to the switch or router. This fault clears when communication is re-established. |
Y | |
| Critical | The Manager experiences high memory usage. Available system memory is low. | Reboot the Manager Server. | N | |
| Critical | The Manager experiences high memory usage. Available system memory is low. | Reboot the Manager Server. | N | |
| Critical | An attempt to save packet log data to the database fails, most likely due to insufficient database capacity. | Ensure that the disk space allocated to the database is sufficient, and try the operation again. | ||
| Critical | This fault indicates a problem with the setup or configuration of the 10/100 Ethernet ports or devices connected to those ports. It also indicates a compatibility issue between the Sensor and the device to which it's connected. | The Sensor might detect an issue with another device on the same network link. Check to see whether there's a problem with one of the other devices on the same link as the Sensor. This situation can cause traffic to cease flowing on the Sensor and might require a Sensor reboot. | N | |
| Critical | This message indicates that the ports are now able to resume In-line Mode as configured. Before this indication, traffic bypasses the Sensor completely, flows through the Fail Open Control Module, and is reflected by the port status as being in Bypass Mode. | This message clears the 'Port pair is in Bypass Mode' message. | Y | |
| Critical | This fault indicates that the indicated GBIC ports are unable to remain in In-line Mode as configured. This fact causes fail-open control to initiate and the Sensor now operates in Bypass Mode. Bypass Mode indicates that traffic flows through the Fail Open Control Module, bypassing the Sensor completely. | Check the health of the Sensor and indicated ports. Check the connectivity of the Fail Open Control Cable to make sure that the Fail Open Control Module can communicate with the Fail Open Controller in the Sensor's Compact Flash port. | Y | |
| Critical | A Sensor is replaced with a different model type (for example, an I-1200-FO (failover only) Sensor). The alert channel is unable to make a connection. | When replacing a Sensor, make sure that you replace it with an identical model. For example, replace an I-1200 with an I-1200. Don't try to replace a regular Sensor with a failover-only model, and conversely. | Y | |
| Critical | The Manager cannot push original Sensor configuration to Sensor during Sensor reinitialization, possibly because the trust relationship is lost between Manager and Sensor. This fault can also occur when a failed Sensor is replaced with a new unit, and the new unit is unable to discover its configuration information. |
The link between Manager and Sensor might be down, or you might need to re-establish the trust relationship between Sensor and Manager by resetting the shared key values. | Y | |
| Critical | The Sensor fails to discover its configuration information, and thus isn't properly initialized. Typically, the Manager is unable to display the Sensor. This also indicates an old Sensor 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 ensure 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. |
Y | |
| Sensor found a conflict with MDR status; ISM IP address/MDR status as& | Critical | There's a problem with the MDR configuration. Check your MDR settings. | n/a | N |
| Critical | An internal communication error occurs within the Sensor. | You must manually clear this fault. This error might cause a reboot of the Sensor, which might resolve the issue causing the fault. If the fault persists, we recommend that you perform the following steps to help Technical Support with troubleshooting:
|
N | |
| Critical | A Sensor is replaced with a different model (for example, an I-4000 Sensor is replaced by an I-2600 Sensor, or a regular Sensor is replaced by a failover model). | A Sensor can be replaced only by a similar model. Make sure that the configuration information matches the model type. For instructions on replacing a Sensor, see section Replacing a Sensor in the Sensor Installation and Configuration Guide. | Y | |
| Critical | User-configured SSL decryption settings for a particular Sensor changes, requiring a Sensor reboot. | Reboot the Sensor to cause the changes to take effect. | Y | |
re-discovery failure |
Critical | 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 whether the Sensor discovery is successful. This fault is issued if discovery fails, and thus the Sensor is still not properly initialized. |
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. | Y |
| Critical | This fault indicates that an error has occurred with a signature set that has been successfully applied on a Sensor. | Reimport the signature set onto the Sensor. This fault can indicate a problem within the signature set itself that wasn't detected during download. If reimporting the same set doesn't solve the problem, providing a new signature set might clear the fault. If a new signature set doesn't solve the issue, reboot the Sensor. If the fault persists, contact Technical Support. The fault clears after the signature set is successfully applied on the Sensor and continues to be error-free after application. |
N | |
| Critical | The Sensor moves from detection mode to Layer 2 (bypass) mode. This fault indicates that the Sensor experiences the specified number of errors within the specified time frame and Layer 2 mode is triggered. | The Sensor remains in Layer 2 mode until Layer 2 is disabled and the Sensor is rebooted. | N | |
| Critical | Indicates that the Sensor cannot communicate with the Manager, indicating that the connection between the Sensor and Manager is down, or that the Sensor is administratively disconnected. | Contact your IT department to troubleshoot connectivity issues. Check that a connection route exists between the Manager and Sensor. Check the Sensor's status using the status command in the Sensor command line interface. Or, ping the Sensor or the Sensor gateway to ensure connectivity to the Sensor. This fault clears when the Manager detects the Sensor again. |
Y | |
| Critical | This fault occurs when the Manager cannot push the signature set file to a Sensor. It can result from a network connectivity issue. | Contact your IT department to troubleshoot connectivity issues. Check that a connection route exists between the Manager and Sensor. | Y | |
| Critical | Indicates a recoverable software error within the Sensor. | This error might cause a reboot of the Sensor, which might resolve the issue causing the fault. If the fault persists, we recommend that you collect a |
N | |
| Critical | This fault occurs when the Manager cannot push a decryption key file to a Sensor. It can result from a network connectivity issue. | Contact your IT department to troubleshoot connectivity issues. Check that a connection route exists between the Manager and Sensor. | Y | |
| Critical | This fault indicates that the temperature of the Sensor is abnormal. The fault clears when the Sensor's temperature falls below its internal Low temperature threshold. (See Temperature in the Sensor Installation and Configuration Guide for temperature thresholds.) |
Check for a Fan Status fault, and also check the Sensor's front panel LEDs to see whether the Sensor's fans are operational. If a fan isn't operational, we strongly recommend contacting Technical Support as soon as possible to schedule a replacement unit. In the meantime, you can use an external fan (blowing into the front of the Sensor) to prevent the Sensor from overheating until the repair is completed. If a fan isn't the issue, make sure that the room where the Sensor is located is cool enough for the Sensor to operate without overheating. |
Y | |
| Critical | This fault generally occurs in situations where in 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 to see whether there's an inconsistency, and make the port pair run in the same operating mode. | N |
Severity: Error
| Fault | Severity | Description or Cause | Action | AutoCleared |
| Error | This fault indicates a failure to communicate with the Sensor via the channel on which the Manager listens for Sensor alerts. | This fault clears when the alert channel is back up. | Y | |
| Error | Displays the percentage of space occupied by alerts in the database. As available space decreases, this message continues to appear at 50%, 70%, 90%, and 100%. When you've exceeded this threshold, an Exceeding fault appears. | Perform maintenance operations to clean the database. Delete unnecessary alerts, such as alerts older than a specific number of days. | Y | |
| Error | This fault indicates that an attempt to apply firewall filters from the Sensor to the firewall fails. It indicates that the application exceeds the maximum number of allowed filters, or that the Sensor-firewall connection fails and the attempt to apply the filter times out. If the connection goes down, the Sensor caches the filters and waits for a connection. Each filter has a timeout value; if the duration of the connection failure exceeds the timeout value of a filter, it times out and raises a fault. |
Check your firewall configuration. If possible, increase the maximum number of available filters. Ensure connectivity between the Sensor and firewall. You must acknowledge or delete the fault to dismiss it. |
Y | |
| Error | The Manager is unable to accept more incidents. You've reached the maximum number of incidents that can be accepted by the Manager. | Delete old incidents to provide room for incoming incidents. The fault clears when the Manager can accept incoming incidents. | N | |
Ver2.1 (Invalid SSL decryption key) |
Error | The Manager detects that a particular SSL decryption key is no longer valid. The detailed reason why the fault occurs is shown in the fault message. These reasons can range from the Sensor reinitializing itself with a different certificate to an inconsistency between the decryption key residing on a primary Sensor and its failover peer Sensor. | Reimport the key (which is identified within the error message). The fault clears itself when the key is determined to be valid. | Y |
| Error | The Manager is unable to obtain the requested profile from a peer Sensor. This situation is likely due to the unavailability of the requested profile or a valid, saved version. | See the |
Y | |
| Get peer DoS profile failure | Error | The Sensor is unable to obtain the requested profile from a peer Sensor. This condition is likely due to the unavilability of the requested profile or a valid, saved version. | See the |
Y |
| Error | This fault indicates that the SMTP mailer host is unreachable, and 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. | N | |
| Error | This fault indicates a failure to communicate with the Sensor via the channel on which the Manager receives packet logs. | This fault clears when the |
Y | |
| Error | The Sensor is unable to push a requested profile to the Manager. | See the |
Y | |
| Error | 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. | This fault is evidence of extremely heavy activity. Check the packets that you're receiving to see what's causing the heavy traffic on the Sensor. Also, see the suggested actions for the fault below: Unarchived, queued alert count full. |
N | |
| Error | The Manager packet log queue reaches its maximum size (default 200,000 alerts), and is unable to process packet logs until there's space in the queue. | This fault is evidence of extremely heavy activity. Check the packet logs you're receiving to see what's causing the heavy traffic on the Sensor. Also, see the suggested actions for the fault below: Unarchived, queued packet log count full. |
N | |
| Error | Unable to make scheduled update of Manager signature sets. This fault can indicate, for example, problems with network connectivity between the Update Server and Manager or between the Manager and Sensor; invalid update sets; or update sets that aren't properly signed. | This fault clears when a signature update is applied successfully. | Y | |
| Error | Unable to make a scheduled update of the Sensor. 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 invalid update set. | This fault clears when an update is sent to the Sensor successfully. | Y | |
| Error | This fault occurs with any type of Sensor software failure, and usually occurs with a Software error fault. | If this fault persists, we recommend that you perform a Diagnostic Trace and submit the trace file to Technical Support for troubleshooting. See the Manager Server Configuration Guide for information about performing a Diagnostic Trace. | Y | |
| Error | This fault indicates that the Sensor reports that the alert channel is down, but the physical channel is up. | The Sensor typically recovers on its own. If you're receiving alerts and your Sensor is otherwise behaving normally, you can ignore this message. Check to see whether trust is established between the Sensor and Manager by issuing a show command in the Sensor CLI. If this fault persists, contact Technical Support. |
Y | |
| Error | This fault indicates that the Sensor reports that the packet log channel is down, but the physical channel is up. This inconsistency can be caused by a channel heartbeat timeout. |
The Sensor typically recovers on its own. If you're receiving alerts and your Sensor is otherwise behaving normally, you can ignore this message. Check to see whether trust is established between the Sensor and Manager by issuing a show command in the sensor CLI. If this fault persists, contact Technical Support. |
Y | |
| Error | The Manager receives a value from the Sensor that's invalid. The additional text of the message contains details. | This fault doesn't clear automatically; it must be cleared manually. Contact Technical Support for assistance. |
N | |
| Error | The Sensor isn't properly initialized. Either it's in the process of starting and isn't ready, or the signature set is missing on the Sensor. | The Sensor might have just been rebooted and isn't up yet. Wait a few minutes to see if a recent reboot is the issue; if not, make sure that a signature set is present on the Sensor. A |
Y | |
| Error | Indicates that the Manager reaches the limit (default of 100,000) of alerts that can be queued for storage in the database. It also indicates the number of dropped alerts. | Alerts are being detected by your Sensors faster than the Manager can process them. This fault is evidence of extremely heavy activity. Try the following:
|
N | |
| Error | This fault indicates that the Manager reaches the limit (default of 100,000) of packet logs that can be queued for storage in the database. It also indicates the number of dropped packet logs. | See the suggestions for the fault 'Unarchived, queued alert count full.' | N |
Severity: Warning and Informational
| Fault | Severity | Description or Cause | Action | AutoCleared |
| Warning | The Manager's attempt to disable failover on the Sensor fails. This fault is likely because the Sensor is unavailable or down. |
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. | Y | |
| Warning | This fault is related to Version Control. You see this fault in the system health when the Manager tries to detect the difference between changes made in the IPS Policy and revisions of the same IPS policy present in the IPS Policy Editor. | If the issue persists, contact Technical Support and provide |
N | |
| Warning | This fault is related to Version control. You see this fault in the system health when the Manager tries to detect the difference between changes made in the Reconnaissance Policy and revisions of the same policy present in the Reconnaissance Policy Editor. | If the issue persists, contact Technical Support and provide |
N | |
| Warning | The failover pair Sensors' firewall functions are both enabled, but the actual connection statuses are inconsistent. | Make sure that both Sensors of the failover pair are connected to the firewall and that both Sensors are online and in good health. | Y | |
| Warning | The Audit Log capacity of the Manager is reached, and the Manager begins overwriting the oldest records with the newest records (in other words, first in first out). This fault indicates the number of records that have been written to the audit log; an equal number of audit log records are now being overwritten. |
This fault is raised after a configured number of records are written. No action is required. The capacity is configured in the |
N | |
| Warning | The Manager experiences an abrupt shutdown, such as a crash. | Perform database tuning (dbtuning) to fix possible database inconsistencies that might have resulted. Tuning might take a while, depending on the amount of data currently in the database. See the Best Practices Guide for your Manager. | N | |
| Warning | Any attempt to add an apostrophe prompts the user with a pop-up error warning that invalid characters are entered. You might be unable to push updated policies to Sensors. After a policy update, the Manager still shows that a policy update is required. |
You must delete the alert filter with the apostrophe and re-create it without an apostrophe. To delete an alert filter:
|
N | |
| Warning | An attempt to update the signature set on both Sensors of a failover pair is unsuccessful for one of the pair, causing the signature sets to be out of sync on the two Sensors. | The Manager tries again to automatically push the signature file down to the Sensor on which the update operation fails. Make sure that the Sensor in question is online and in good health. The fault clears when the Manager is successful. If the operation fails a second time, a Critical Signature set download failure fault is shown as well. Both faults clear when the signature set is successfully pushed to the Sensor. |
Y | |
| Warning | 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. |
Y | |
| Warning | The Sensor just completes booting and is online. | This message is informational. Acknowledge or delete the fault to clear it. |
N | |
| Warning | The Manager is unable to update the decryption key on one Sensor in a failover pair, causing the key on one Sensor to be out of sync with the one on its failover peer. | The Manager tries again to update the key. Make sure that the Sensor is online and in good health. The fault clears when the Manager successfully pushes the key to the Sensor and both keys are in sync. |
Y | |
| Warning | System startup restores alerts from the archive file. Alert Viewer might not show all alerts. | Alert Viewer might not show all alerts. | Y | |
| Informational | The alert archival process is started. | n/a | Y | |
| Informational | n/a | N | ||
| Informational | n/a | Y | ||
| Informational | The database archival process is in progress. | 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. | Y | |
| Informational | The database archival is successful. | n/a | N | |
| Informational | Unable to back up database tables. | This message indicates that an attempt to manually back up the database fails. 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. | N | |
| Informational | A manual or scheduled database backup process is in progress. | 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. | Y | |
| Informational | The database backup is successful. | n/a | N | |
| Informational | The database tuning process is in progress. |
The user cannot perform the following operations during tuning process:
|
Y | |
| Informational | The database tuning process successfully completes. | n/a | N | |
| Informational | The two Managers in an MDR configuration must have the same Manager software version installed. The Primary Manager software is more recent than the version of the Secondary Manager. | Make sure that the two Managers run the same software version. | N | |
| Informational | The two Managers in an MDR configuration must have the same Manager software version installed. The Secondary Manager software is more recent than the version of the Primary Manager. | Make sure that the two Managers run the same software version. | N | |
| Informational | A Trellix-defined UDS is incorporated in a new signature set and is removed from the UDS editor. | This message is informational and indicates that an emergency Trellix-provided UDS signature is appropriately overwritten as part of a signature set upgrade. | N | |
| Informational | Manager Disaster Recovery switchover is complete; the Secondary Manager is in control of Sensors. | Failover occurs; the Secondary Manager is now in control of the Sensor. Troubleshoot problems with the Primary Manager and try to bring it online again. Once it's online, you can switch the control back to the Primary. |
N | |
| Informational | Manager Disaster Recovery Secondary Manager successfully retrieves configuration information from the Primary Manager. | n/a | N | |
| Informational | Manager Disaster Recovery is canceled. | n/a | N | |
| Informational | Manager Disaster Recovery is successfully configured. | n/a | N | |
| Informational | Manager Disaster Recovery functionality is resumed. Failover functionality is again available. | n/a | N | |
| Informational | Manager Disaster Recovery functionality is suspended. No failover takes place while MDR is suspended. | n/a | N | |
| Informational | Manager Disaster Recovery switchback is completed; the Primary Manager regains control of the Sensors. | n/a | N | |
| Informational | No Syslog server is configured to accept ACL logs for the Admin Domain <Admin Domain Name>. Configure a Syslog server for the Manager to use to forward ACL logs. | This message appears until a Syslog server is configured for use in forwarding ACL logs. | N | |
| Informational | n/a | Y | ||
| Informational | A Reset to Standalone is invoked; the Primary Manager is standalone and is in control of the Sensors. | n/a | N | |
| Informational | A Reset to Standalone has been invoked; the Secondary Manager is standalone and is in control of Sensors. | n/a | N | |
| Informational | Sensor configuration update failed while transferring from the Manager server to the Sensor. | n/a | Y | |
| Informational | A Sensor configuration update is in the process of being pushed from the Manager server to the Sensor. | n/a | Y | |
| Informational | Sensor configuration update successfully pushes from the Manager server to the Sensor. | n/a | N | |
| Informational | The Manager tries to discover the Sensor. | n/a | Y | |
| Informational | There's a problem with the MDR configuration. Check your MDR settings. | n/a | N | |
| Informational | There's a problem with the MDR configuration. Check your MDR settings. | n/a | N | |
| Informational | Sensor software image fails to download from the Update Server to the Manager server. | n/a | Y | |
| Informational | Sensor software image is in the process of downloading from the Update Server to the Manager server. | n/a | Y | |
| Informational | Sensor software image successfully downloads from the Update Server to the Manager server. | n/a | N | |
| Informational | A Sensor software image or signature set file is in the process of being imported from the Update Server to the Manager server. | n/a | Y | |
| Informational | Signature set is in the process of downloading from the Update Server to the Manager server. | n/a | Y | |
| Informational | Signature set successfully downloads from the Update Server to the Manager server. | n/a | N | |
| Informational | Signature set update fails while transferring from the Manager server to the Sensor. | n/a | Y | |
| Informational | A signature set is in the process of being pushed from the Manager server to the Sensor. | n/a | Y | |
| Informational | 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. A valid signature set must be present before any further action can be taken. | N | |
| Informational | n/a | N | ||
| Informational | ACL logging is enabled, but no Syslog server is configured to accept the log messages. | Configure a Syslog server to receive forwarded ACL logs. | N | |
| Informational | One or more UDS is in the process of being exported from the UDS Editor to the Manager server. | n/a | N | |
| Informational | n/a | N |
Previous Document ID (Secured)
8663009
Affected Products
Languages:
This article is available in the following languages:
