Platform alarm reference
Platform alarms are generated for the following BMC Real End User Experience Monitoring components:
Applicable component | Component name |
|---|---|
Aggregation Server | Aggregation Server for Extended Reporting |
Analyzer 1 | Real User Analyzer |
APM Console | BMC Application Management Console |
Collector 1 | Real User Collector or TS-4200 hardware Collector |
Hardware 1 | BMC TrueSight End User Monitor 4200 Series |
PAE | Performance Analytics Engine |
APM Central 2 | Application Performance Management Central |
1.Alarms that apply to an Analyzer, Collector, or hardware, also apply to a Real User Monitor.
2.Alarms that apply to APM Central, apply to the AM Console, PAE, and Monitor installed with that component.
The tables below list the alarms and indicate the components to which the alarm applies.
For information about platform alarms and the ways in which you can view them, see End-user-experience-monitoring-platform-alarms.
System alarms
Alarm name | Severity | Short description | Long description | Applicable components | Automatic corrective actions |
|---|---|---|---|---|---|
system.account.defined | error | Security Officer account not configured | A user account with the Security role must exist on the system for UI access. | All | None |
system.capture.broken | critical | Unable to setup capture interface | The system is unable to set up the capture interface from the network interfaces available to the system. Corrective actions will be taken. | Collector, Hardware, APM Central | If this alarm has been raised for 5 consecutive minutes, the system will re-initialize the capture interface. After 3 unsuccessful initialization attempts, the system will reboot. |
system.capture.drop | attention | System dropping packets on capture ports | Within the last minute, the system was unable to process all network traffic on the capture ports. These drops occur at the OS level. | Collector, Hardware, APM Central | None |
system.capture.noHttp | info | Captured traffic contains no HTTP data | Within the last minute, the system detected receipt of network traffic but it is not HTTP traffic. | Collector, Hardware, APM Central | None |
system.capture.noHttps | info | Captured traffic contains no HTTPS data | Within the last minute, the system detected receipt of network traffic but it is not HTTPS traffic. | Collector, Hardware, APM Central | None |
system.capture.noTraffic | error | System not receiving TCP traffic on capture ports | Within the last minute, the system detected receipt of network traffic but it is not TCP traffic. Since the HTTP protocol uses TCP, no HTTP traffic detected either. | Collector, Hardware, APM Central | None |
system.capture.onedirection | info | System receives unbalanced ratio of SYN and SYN-ACK packets | Within the last 5 minutes, the system detected an unbalanced SYN/SYN-ACK ratio exceeding 30%. The traffic is detected as only going in one direction. | Collector, Hardware, APM Central | None |
system.capture.sampling | attention | System dropping traffic due to resource starvation | In the last 10 minutes, there was at least 1 hit (HTTP transaction) dropped by the system due to resource starvation. | Analyzer, Collector, Hardware, APM Central | None |
system.capture.sampling.query | attention | System is dropping traffic due to resource starvation while a user-initiated database query was executed | The system has detected a drop in processed traffic and an active Session Browser query was started before this condition. The query has also been running for more than 60 seconds. | Analyzer, Hardware, APM Central | None |
system.console.multipleconsoles | error | Several Consoles attempt to manage this device: consoleNames. If the Console IP was recently changed, this condition should clear in 5-10 minutes. | A PAE traffic server can be managed by only one Console at a time. You have incorrectly configured PAE on the following Consoles: consoleNames For instructions, see Managing Performance Analytics Engine instances. | PAE | None |
system.console.notpresent | info | No AM Console detected | The PAE traffic server is not being managed by an AM Console. Your PAE configuration is incomplete. For instructions, see Assigning-data-providers. | PAE | None |
system.cpu.busy | attention | Average CPU utilization number% in the last 5 minutes is above configured threshold | The system has detected a CPU utilization in the last 5 minutes that is higher than the configured threshold (current utilization is number%). cpuUtilThreshold property 1 : The maximum percentage of CPU utilization that can be reached before an alarm is raised; the default value is 90%. | All | None |
system.cpu.freeze | critical | One or more CPU not responding | One or more CPUs on the system are not behaving as expected and could be halted. Corrective actions will be taken. | All | If this alarm has been raised for 5 consecutive minutes, the system will perform a full system reboot. If the condition persists after 20 minutes, the system might be unsuccessfully trying to restart. The alarm will force a low level reboot. |
system.data.badVersion | critical | System image not compatible. Data migration required | The system is currently running a product version that is incompatible with the data stored on the system. Open a ticket with Customer Support immediately. | All | None |
system.database.connection | critical | Too many connections registered in DB engine | The database engine reports there are too many processes connecting to it. This causes system instability. | Analyzer, Hardware, APM Central | After raising the alarm, the system immediately performs a software reboot to clear this situation. |
system.database.full | critical | The database is full. Purging might not be possible. Contact Customer Support immediately | The database is taking too much space on the disk. Automatic purging by the system might not be possible. Contact BMC Customer Support immediately to clean the disk. pollFrequency property 1 : How often to check for this condition; the default value is 5 minutes. dbFullThreshold property 1 : How much of total disk space is used by the database; the default value is 98%. | Analyzer, Hardware, APM Central | None |
system.database.small | error | The database is running in demo mode (max. 1 GB). This configuration is not recommended for production systems. | When deploying an Analyzer, you must configure additional storage for the Session Browser database. If it was not allocated, then the default 1GB database will provide data retention for only a few minutes. minimalDBBytes property 1 : The minimum number of bytes a database file part needs to be before being declared small; the default value is 25000000000. For information, see Storage requirements. | Analyzer, Hardware, APM Central | None |
system.dataprovider.connection | error | System is unable to connect to data provider (provider IPaddresses) | The PAE system is unable to connect to one or more configured data providers: provider IPaddresses.
| PAE | None |
system.datawarehouse.notavailable | error | Data warehouse is not available | The Aggregation Server is unable to detect a configured data warehouse. You will get data loading errors in the UI. | Aggregation Server | None |
system.datawarehouse.notconfigured | error | Data warehouse is not configured properly | A data warehouse is not configured properly on the Aggregation Server. Try to reconfigure this system. For instructions, see Connecting-the-Aggregation-Server-to-a-data-warehouse. | Aggregation Server | None |
system.epx.watchdog | critical | Packet capture process not responding | The system detected a problem in the packet capture process. The system could be in trouble and will perform corrective actions. | Collector, Hardware, APM Central | If this alarm has been raised for 5 consecutive minutes, the system will restart the packet capture process gracefully. If this does not fix the problem, the system will restart the packet capture process forcefully. If it is still unsuccessful, then the system will perform a software reboot. |
system.ethernet.noTraffic | error | No traffic on capture interface (network Interface name) | There is no network traffic detected from the capture interface (network Interface name). threshold property 1 : The minimum number of bytes that must be flowing within a minute before triggering the alarm. enabled property 1 : The current status of the alarm; the default value is 0, which is disabled. | Collector, Hardware, APM Central | None |
system.ethernet.portsMissing | critical | Capture port (network Interface name) is missing. | A configured capture port (network Interface name) is no longer defined in the system. Your system will not process some traffic fed to it. | Collector, Hardware, APM Central | None |
system.fanout.case | attention | One or more case fans failed | One or more of the internal fans failed. This can result in overheating of the unit. Prolonged overheating of the unit will result in hardware failures. | Hardware | None |
system.fanout.cpu | attention | One or more CPU fans failed | One or more of the internal CPU fans failed. This can result in overheating of the CPU module. Prolonged overheating of the CPUs will result in hardware failures. | Hardware | None |
system.https.connection | error | Stale HTTP connection detected: client IP and Port List | The system has detected a stale connection from client IP and Port List to the management port. | All | If this alarm has been raised for 5 consecutive minutes, the system will automatically reset all stale connections. |
system.http.ping | critical | Cannot get data from the HTTP management port | The system is unable to access its own management port. You will not have access to the end-user experience monitoring component until the condition is cleared. raiseThresholdMinutes property 1 : The time the system will wait before the alarm is raised; the default value is 15 minutes. | All | If this alarm has been raised for 5 consecutive minutes, the system will perform a software reboot. If this does not fix the problem, a full reboot is performed. |
system.https.ping | critical | Cannot get data from the HTTPS management port | The system is unable to access its own management port. You will not have access to this end-user experience monitoring component until the condition is cleared. raiseThresholdMinutes property 1 : The time the system will wait before the alarm is raised; the default value is 15 minutes. | All | If this alarm has been raised for 5 consecutive minutes, the system will perform a software reboot. If this does not fix the problem, a full reboot is performed. |
system.java.oom | critical | Java process out of memory | The system detected that the Java portion of the software has run out of memory. It was restarted automatically. | All | None |
system.management.IfDown | error | No link detected on the management port | No network link signal can be detected on the management port of the system. Since this is the primary way to interact with the system, it must be corrected. | All | If this alarm has been raised for 5 consecutive minutes, the system will restart the management interface. If this does not fix the problem, the link speed will be set to autonegotiation and the management interface will be restarted. |
system.management.IfSpeedLow | info | Management port not negotiated at maximumMode (current mode: speed duplex duplex). | The management port's network link is not negotiated at the highest speed possible. It is currently set to speed and duplex. | Hardware | None |
system.memory.hypervisor.swap | error | Hypervisor swapped the memory of this VM to disk | The system (running on VMware) has had its memory space swapped out by the host hypervisor. The system functions can be compromised and its performance degraded. | All running on VMware except Hardware | None |
system.memory.swap | attention | System is swapping memory | The system detected that it had to swap a lot of memory out to disk. | All | None |
system.mode.booting | attention | System is booting | The system is currently booting up. Data processing might not have resumed, and the UI might not be available. | All | None |
system.mode.migrate | info | System config migration on going | The system is undergoing configuration migration. This might take some time for data processing to resume. The UI is not available at this time. | All | None |
system.mode.safe | critical | System running in safe mode | The system is running in safe mode. This is either because the system entered an unstable state or the Customer Support team has done this. The system is not processing data. | All | None |
system.mode.softreboot | info | System performing software reboot | The system is performing a software reboot. This is typically done by a critical alarm to solve an issue. | All | None |
system.nas.notconfigured | error | Network attached storage (or local data storage) is not configured | There is no data storage configured for this system. Data loading will not work. For instructions, see Assigning-data-providers or Connecting-the-Aggregation-Server-to-a-NAS-device. | Aggregation Server, PAE | None |
system.nas.notmounted | error | The configured (remote or local) data storage is not mounted. Check whether configuration parameters are correct | The configured data storage for this system is not available for access. No new data loaded will be loaded until this is resolved. | Aggregation Server, PAE | None |
system.network.connectivity | error | The system is unable to ping its default gateway IP address | The system is unable to ping the configured default gateway IP address. You might be unable to access the UI during this time. | All | None |
system.notPublishing.data | critical | Received data not published in the database | The system is receiving data but recent data was not inserted into the database. | Analyzer, Hardware, APM Central | If this alarm has been raised for 5 consecutive minutes, the system will perform a software reboot. If this isn't solved by a software reboot, the system will perform a full reboot. |
system.notPublishing.rawdata | critical | Received raw data not published in the database. The database is in error | The system is receiving data but the Session Browser database is not being updated. raiseThresholdSeconds property 1 : The time to wait for a persisting condition before raising the alarm; the default value is 600 seconds. | Analyzer, Hardware, APM Central | If this alarm has been raised for 5 consecutive minutes, the system will perform a software reboot. If this isn't solved by a software reboot, the system will perform a full reboot. |
system.notPublishing.sum_obj | critical | Summary object data not published in the database | The system is receiving data but the Watchpoint database is not being updated. raiseThresholdSeconds property 1 : The time to wait for a persisting condition before raising the alarm; the default value is 1200 seconds. | Analyzer, Hardware, APM Central | If this alarm has been raised for 5 consecutive minutes, the system will perform a software reboot. If this isn't solved by a software reboot, the system will perform a full reboot. |
system.notPublishing.sum_page | critical | Summary page data not published in the database | The system is receiving data but the Watchpoint database is not being updated. raiseThresholdSeconds property 1 : The time to wait for a persisting condition before raising the alarm; the default value is 1200 seconds. | Analyzer, Hardware, APM Central | If this alarm has been raised for 5 consecutive minutes, the system will perform a software reboot. If this isn't solved by a software reboot, the system will perform a full reboot. |
system.oracle.load | error | Data load issues were detected that could be related to the data warehouse state. Check whether the data warehouse is properly configured and is reachable from the Aggregation Server | Data load issues were detected that could be related to the data warehouse state. Check whether the data warehouse is properly configured and is reachable from the Aggregation Server For instructions, see Connecting-the-Aggregation-Server-to-a-data-warehouse. | Aggregation Server | None |
system.process.database | critical | DB engine is not running | The database engine is not running. None of the captured or processed data is kept for viewing. | Analyzer, Collector, Hardware, APM Central | None |
system.process.epx | critical | EPX not running | The packet capture engine is not running. No traffic is being monitored. | Collector, Hardware, APM Central | None |
system.process.etl | critical | ETL process is not running | The database loading engine is not running. The Aggregation Server is not storing new data. | Aggregation Server | None |
system.process.java | critical | java not running | The Java portion of the software is not running. No data is being capture or processed. | All | If this alarm has been raised for 5 consecutive minutes, the system will restart the Java software. If this does not resolve the issue, the system will perform a software reboot. |
system.process.snmp | attention | SNMP not running | The SNMP agent process is not running. System alerts will not be sent out by SNMP. | All | None |
system.process.virgo.deadlock | critical | Virgo detected a deadlock in the java application | The system detected that the Java portion of the software is in trouble. It was restarted automatically. | Aggregation Server Console, PAE, APM Central | None |
system.publishing.rcsp.loss | critical | Data loss occured for record streaming protocol clients: IPaddressList | The system detected a drop in the outgoing queue of the RCSP publisher. This is used to feed PAE with data. The following systems are affected: IPaddressList | Analyzer, Hardware, APM Central | None |
system.publishing.screen | info | System receiving data, but traffic exclusion policies reject all of it | The system is receiving traffic but all traffic was rejected by the configuration. Check your configuration settings. For information, see Traffic inclusion and exclusion policies. raiseThresholdSeconds property 1 : The time the system will wait before the alarm is raised; the default value is 1200 seconds. | Analyzer, Hardware, APM Central | None |
system.query.slow | info | query Count queries are running for more than threshold hours | The system detected long running queries. The duration of the queries (query Count) exceeded the configured threshold (threshold) time. queryThreshold property 1 : The maximum duration of a query before it is considered to be running too long; the default value is 1 hour. | PAE, APM Central | None |
system.ssh.status | info | SSH access is disabled | The access to the system by SSH is currently disabled. If you don't have access to the system from an APM Console, enabling SSH is the only way to access the CLI commands. For instructions, see Controlling-remote-access-to-the-command-line-interface. | All | None |
system.status.lastreset | info | Last reboot caused by reset Flag value | The onboard diagnostics system detected the cause of the last system reboot. | Hardware | None |
system.status.psu | error | PSU redundancy lost. Check that both power supply units are correctly powered | The diagnostics module detected an inconsistency in the power supply. Verify they are both running properly to ensure availability of the system. | Hardware | None |
system.status.watchdog | error | System was rebooted by the watchdog | The system was last rebooted by the diagnostics module because it did not think the system was operational. | Hardware | None |
system.stream.termination | error | A watchpoint stream for wpid from username at ip-address was terminated after time | The user username from system ip-address terminated a getstream API call for Watchpoint ID wpid after duration time. | Analyzer, Hardware | None |
system.time.drift_adjusted | attention | System readjusted its time after detecting a time drift | The system's internal clock was adjusted. | All except Hardware | None |
system.time.drift_detected | error | System time drifting. Software does not keep up the time | The system's internal clock has drifted. | All except Hardware | None |
system.time.ntp | attention | NTP service is enabled but the system is not synchronized with any time source. possibleCause | The system detected no synchronization with any of the configured NTP servers. If a cause is given in this alarm, the system is unable to reach the configured NTP servers. | All | None |
system.time.ntpsync | error | NTP time synchonization detected a time offset greater than 5 seconds in the last 24 hours | The system detected it was more than 5 seconds from the NTP servers. It resynchronized itself. | All | None |
system.userlogin | info | The user user Name last logged on more than allowed interval minutes ago | The system detected the user user Name has not logged in since allowed interval minutes. user property 1 : The user account name to watch; the default value is default. allowed_internal property 1 : The maximum interval between logins for the specified user; the default value is 0 minutes, which disables the alarm. | Analyzer, Collector, Hardware, APM Central | None |
systemCaptureIfDown | error | No link detected on capture port interfaceName | There is no network link detected on the capture port interfaceName. Traffic processing is disabled. | Collector, Hardware, APM Central | None |
systemCaptureIfSpeedLow | info | Capture port[s] interfaceList not negotiated at 1000 Mb/s or 10000 Mb/s | The system detected that the configured capture ports are not currently negotiating at 1Gb/s or 10Gb/s. This can seriously impair the main function of the system. | Hardware | None |
systemUserReboot | attention | User userName requested system reboot. | System was rebooted by user username. | All | None |
systemUserShutdown | attention | User userName requested system shutdown. | System was shutdown by user username. | All | None |
1.To view alarm properties, use the alarm-command -p parameter. To set alarm properties, use the -s parameter.
Storage alarms
Alarm name | Severity | Short description | Long description | Applicable components | Automatic corrective actions |
|---|---|---|---|---|---|
storage.data_partition.full | critical | The system has reached the CRITICAL disk space threshold configured threshold%. The system has stop loading data to prevent data inconsistencies. Restart the Aggregation Server and, contact BMC Customer Support, if the alarm does not clear. | None. diskFullThreshold property 1 : The amount of disk space used by the temporary files before this alarm is raised; the default value is 97%.
| Aggregation Server | If this alarm has been raised for 5 consecutive minutes, the system will stop the data loading process. No new data will be added to the database until this situation is corrected. |
storage.data_partition.nearfull | error | The system has reached the warning disk space threshold configured threshold%. When critical disk space threshold is reached the system will stop loading Data warehouse data to prevent data inconsistencies. Restart the Aggregation Server and, contact BMC Customer Support, if the alarm does not clear. | None. diskNearFullThreshold property 1 : The amount of disk space used by the temporary files before this alarm is raised; the default value is 94%. | Aggregation Server | None |
storage.drive.full | critical | The filesystem on mount Folder is full | The maximum disk allocation for the folder named mount Folder has been reached by the system. System stability is compromised. Please contact BMC Customer Support as soon as possible. | All | None |
storage.drive.missing.perc | error | Missing drives detected in the RAID array. missing Disk Message | The system has detected that some default disk drives are no longer online. The message indicates which drives are missing. Please contact BMC Customer Support as system stability may be compromised. | Hardware | None |
storage.drive.temperature | attention | Hard disk drive drive Identifier too hot | The system detected the hard drive temperature has exceeded the configured threshold. scsiDriveTempThreshold property 1 : The temperature at which a SCSI drive will raise the alarm; the default value is 40 Celsius. sataDriveTempThreshold property 1 : The temperature at which a SATA drive will raise the alarm; the default value is 40 Celsius.
| Hardware | None |
storage.image.rescue | attention | Rescue image not synchronized | The rescue image partition is not properly synchronized with the currently running system image. To correct the issue, run the installRescue CLI command. | All | None |
storage.innodb.readerror | attention | Innodb read error: message | The system has detected an error reading a database file. Please contact Customer Support to verify the disks. | Analzer, Hardware, APM Central | None |
storage.nas.full | critical | The configured (remote or local) data storage has reached the critical disk space threshold (configured Threshold%). Please allocate more space to this storage location to prevent data continuity from being affected. | None. nasFullThreshold property 1 : The amount of disk space used before this alarm is raised; the default value is 97%. | Aggregation Server, PAE, APM Central | None |
storage.nas.nearfull | error | The configured (remote or local) data storage has reached the warning disk space threshold (configured Threshold%). Please allocate more space to this storage location to prevent data continuity from being affected. | None. nasNearFullThreshold property 1 : The amount of disk space used before this alarm is raised; the default value is 94%. | Aggregation Server, PAE, APM Central | None |
storage.nas.write | critical | Error writing to the configured (remote or local) data storage. Check availability and permissions. | None. | Aggregation Server, PAE, APM Central | None |
storage.performance.io | attention | Performance of drives drive Identifiers does not match data processing volume | Drive performance for drive Identifiers is not sufficient for optimal operations.
| All | None |
storage.raid.perc.degraded | error | Raid Identifier disk array is running in degraded mode. Run raidstate for more details | The system has detected the RAID system is running in degraded mode. Please run the raidstate CLI command for more details. | Hardware | None |
storage.raid.perc.rebuilding | info | Raid Rebuilding State | The system is currently rebuilding the RAID system. The current progress is Raid Rebuilding State. | Hardware | None |
storage.smart.error | attention | SMART errors on drives: drive Identifier (Serial numbers: drive Serial Numbers) | The internal RAID system has detected SMART errors on the following drives: drive Identifier and drive Serial Numbers. | Hardware | None |
storage.smart.failed_test | attention | SMART test failed on drives: drive Identifier (Serial numbers: drive Serial Numbers) | The internal RAID system has detected failed SMART tests on the following drives: driveI dentifier and drive Serial Numbers. | Hardware | None |
storage.smart.failing | critical | Imminent failure of drives: drive Identifier (Serial numbers: drive Serial Numbers) | The internal RAID system has detected imminent failure on the following drives: drive Identifier and drive Serial Numbers. | Hardware | None |
storage.smart.pending_sectors | info | Unreadable sectors pending for reallocation: message | The internal RAID system has detected unreadable, pending sectors with the following message: message | Hardware | None |
storage.smart.reallocated | info | system Message | The system detected a disk sector reallocation from the controller. | Hardware | None |
Config alarms
Alarm name | Severity | Short description | Long description | Applicable components | Automatic corrective actions |
|---|---|---|---|---|---|
config.javapublishing.disabled | info | RAW data storage is disabled by config | The system configuration disabled the storage of transcript data. The Session Browser feature will not return any results, and drilling down from a dashlet, a report, or an incident will not return any result. | Analyzer, Hardware, APM Central | None |
config.trafficCapture.disabled | attention | Traffic capture is disabled | The system configuration disabled the traffic capture process. Data capture and processing will not be performed, and data will not be sent to the Analyzers. | Collector, Hardware, APM Central | None |
configPublicTrafficExcluded | info | Traffic-exclusion policy configured. Some traffic might be excluded. | The system configuration has traffic exclusion policies configured. Some traffic will not be processed. | Analyzer, Hardware, APM Central | None |
Collector alarms
Alarm name | Severity | Short description | Long description | Applicable components | Automatic corrective actions |
|---|---|---|---|---|---|
collector.downloadTime.exceeded | error | Download time for one or more collectors has been exceeded | One or more configured Collector feeds took longer than 30 seconds to transfer its traffic payload to the Analyzer. | Analyzer | None |
collectorDisconnected | error | Collector feed list Of Collectors not responding | One or more configured Collector feeds in the list Of Collectors is not responding. The Analyzer should automatically reconnect shortly. If this alarm has been raised for more than 5 minutes, open a support ticket with Customer Support to investigate.
| Analyzer | None |
collectorDrdDataBufferFilling | attention | Data buffer for the data-receiving device analyzer-name is 70% full | The data buffer for the Analyzer analyzer-name is 70% full. If this situation worsens, a more severe alarm will be raised. | Collector | None |
collectorDrdDataBufferFlushed | info | Data-receiving device analyzer-name flushed its buffer on the Collector | The Analyzer system analyzer-name sent a flush request to this Collector and its data buffer was cleared. | Collector | None |
collectorDrdDataBufferFull | attention | Data buffer for the data-receiving device analyzer-name is 95% full | The data buffer for the Analyzer analyzer-name is 95% full. This situation can lead to data loss. | Collector | None |
collectorDrdDataOld | info | Age of buffered data exceeds 70% of the tolerance level for the data-receiving device analyzer-name | The oldest data in the Collector's buffer exceeds 70% of the tolerance level configured on the Analyzer analyzer-name. If this situation worsens a more severe alarm will be raised.
| Collector | None |
collectorDrdDataTooOld | attention | Age of buffered data exceeds 95% of the tolerance level for the data-receiving device analyzer-name | The oldest data in this Collector's buffer exceeds 95% of the tolerance level configured on the Analyzer analyzer-name. If this situation worsens a more severe alarm will be raised.
| Collector | None |
collectorDrdDroppingData | error | Data buffer for the data-receiving device analyzer-name is full. The Collector dropped oldest data. | The data buffer for the Analyzer analyzer-name exceeded capacity. This Collector has dropped the oldest data to recover. | Collector | None |
collectorDrdDroppingDataTooOld | error | Age of buffered data exceeds of the tolerance level for the data-receiving device analyzer-name. The Collector dropped this data. | The oldest data in this Collector's buffer exceeds the tolerance level configured on the Analyzer analyzer-name. The Collector dropped the oldest data. | Collector | None |
collectorDrdTimedOut | error | Disconnected inactive data receiving device analyzer-name | The data connection between this Collector and the Analyzer analyzer-name has timed out. Check for possible network problems between the two devices.
| Collector | None |
collectorNoDrdConnected | info | No data receiving device connected | This Collector is not feeding its captured traffic to any Analyzer. | Collector | None |
collectorNoTrafficReceived | error | Cannot retreive data from Collector feed listOfCollectors | This Analyzer is not receiving any traffic from the following configured Collectors: listOfCollectors. | Analyzer | None |
Memory alarms
Alarm name | Severity | Short description | Long description | Applicable components | Automatic corrective actions |
|---|---|---|---|---|---|
memory.product.ts4200 | error | Amount of memory detected RAM size not valid | The amount of memory detected on this system is invalid: RAM size. This system should always have 32GB of RAM. | Hardware | None |
memory.product.tsvm | error | Amount of memory detected RAM size not valid | The amount of memory detected on this system is invalid: RAM size. This system should always have at least 3.9GB of RAM. | All except Hardware | None |
Product alarms
Alarm name | Severity | Short description | Long description | Applicable components | Automatic corrective actions |
|---|---|---|---|---|---|
product.image.installation | info | Installation in progress | The system is currently installing an image file. System performance can be slightly impacted. | All | None |
Content contributed by BaoPhac Do