Sensor warning faults

These are the warning faults for a Sensor device.

Fault	Severity	Description/Cause	Action
Device Startup Detected	Warning	The device has powered up or rebooted.	If the device rebooted, confirm that the reboot was intentional. If not, consult the system log for details.
Voltage Error	Warning	Device voltage is outside its normal range	Ensure that all cables are connected correctly. Check connections on the fans and HDDs. Replace the CMOS battery. Remove all, but minimum components for operation and check sensor. If the issue follows a particular component, swap it, otherwise, replace the board. If the issue remains, replace the power supplies.
Fan Error	Warning	Device fan is not performing at expected capacity	Swap the fans round to see whether the problem stays with the location or follows the fan. Replace the fan or fan wiring/housing depending on the previous outcome. If the system has been in this use for a while, the event may be a sign of impending fan failure. Replace the fan.
Power Supply Error	Warning	Device power supply is outside its normal range	Remove and reapply AC. If the power supply still fails, replace it.
Processor Error	Warning	Device processor error	Internal Error: Swap processors and test. Replace the processors depending on the results of the test. Thermal Issues: Verify heatsink is properly attached and has thermal grease. If the system has a heatsink fan, ensure the fan is spinning. Check all system fans are operating properly. Check that the air used to cool the system is within limits.
Memory Error	Warning	Device memory error	Review and confirm memory stick (RAM) population rules for environment. Swap suspect memory for known working memory within system. Observe for any error messages that might clarify whether the error is limited to the memory or the socket/location on the server board. If error travels with memory, replace memory. If error remains localized to the same memory socket, replace server board.
Physical Security Error	Warning	Device physical security error	Chassis intrusion: Use the Quick Start Guide and the Service Guide to determine whether the chassis intrusion switch is connected properly. If this is the case, make sure it makes proper contact when the chassis is closed. LAN Leash lost: Could be most likely due to unplugging the cable but can also happen if there is an issue with the cable or switch. Check the LAN cable and connector for issues. Investigate switch logs where possible. If this is also the case, someone has opened the chassis. Ensure nobody has access to the system that should not.
Physical Interrupt Error	Warning	Physical Interrupt error.	PCI related Issue: Refer Intel SEL Troubleshooting guide to decode the bus, device, and function to identify the card. If this is an add-in card: Verify the card is inserted properly. Install the card in another slot and check whether the error follows the card or stays with the slot. Update all firmware and drivers, including non-Intel components. If this is an on-board device: Update all BIOS, firmware, and drivers. Replace the board.
Physical Interrupt Error	Warning	FP (NMI) Interrupt (Frontend Panel Non-Maskable Interrupt)	If this button was not actually pressed, ensure there is no physical fault with the front panel. This event creates a memory dump to preserve state of Sensors for further inspections. This event only gets logged if a user pressed the NMI button or sent an IPMI Chassis Control command requesting this action and, although it causes the OS to crash, is not an error.
System Firmware Error	Warning	Device system firmware error	If this is a serious error, there is typically also a corresponding System Event Log entry logged for whatever was the cause of the error; this event may contain more information about what happened.
Watchdog Error	Warning	Device watchdog error	Capture a System BMC Debug Log as soon as possible after the failure. OS event logs need to be investigated to determine what may have caused this.
Logging Error	Warning	Device logging disabled error	The BMC logs an SEL clear event. This is an informational event only. This is only ever the first event in the SEL. The cause of this event is either a manual SEL clear or some other IPMI-aware utility or is done in the factory as one of the last steps in the manufacturing process.
Generic Hardware Error	Warning	Device General Hardware error	Caused by another event. System event logs would be cleared manually. Platform event Filters were triggered to send alerts of system event logs. Inspect system event logs that are found around the time of event.
Operating System Shutdown Error	Warning	Operating system shutdown error	These events are usually found along with several other events. Examine System event log entries found around the event timestamp. Events come along with reason code. Refer Intel SEL troubleshooting guide to decode them.
Sensor Health Changed	Warning	Health of sensor {0} changed from {1} to {2}	Please visit Devices → Sensor Health → Health Status to more about the health of the sensor
HA Peer Status Change	Warning	High-availability device {0} is {1}	A status of Incompatible indicates that the HA member Sensors are not running the same Sensor software version, which is required for proper HA function. A status of Down indicates that the peer Sensor cannot be reached. In this case, check the HA interconnect port's status as well as the peer Sensor's health.
Device Reboot Required	Warning	The jumbo frame parsing setting on this device has been updated and a reboot is required for the change to take effect.	Reboot the device to make the change take effect.
Pluggable Interface Certification Status	Warning	Pluggable interface in port {0} is {1}	Replace the non-certified transceiver with a Trellix-certified one or update the physical port's settings to allow a non-certified connector type.
Device performance - {0}	Warning	{0}{1} {2} detected on {3}. ({4} Threshold: {5}{6}).	Review the number and duration of performance-related faults for this device and refer its performance charts to determine if high usage is an on-going occurrence. If yes, a model with a higher system capacity should be considered. (Tip: Multiple capacities are supported on some models with a license change to increase the capacity)
Alert Channel Down	Warning	The alert channel for device {0} is down, but the physical link is up. Details: {1}	The device normally auto recovers from this issue. If your device is otherwise behaving normally, you can ignore this message.
Device Configuration Change Detected	Warning	A change in the physical configuration for device {0} has been detected. A new configuration has been discovered.	Refer the physical ports and confirm if the configuration change is intended.
Failed to Dismantle HA Pair	Warning	The HA pair could not be dismantled as device {0} is disconnected from the Manager. (The Manager will try to dismantle once the device reconnects.)	Ensure that both member devices in the HA pair are connected to the Manager.
HA pair Configuration Out-of-Sync	Warning	Pending changes could not be deployed to the device {0} in a HA pair {1}. Configuration will be out-of-sync until pending changes are deployed to both devices in the pair. (The Manager will continue to deploy changes until the deployment is successful.)	Ensure that the device is connected to the Manager and is in good health.
HA pair Configuration Out-of-Sync	Warning	The firewall connection status for the devices in the HA pair {0} is inconsistent. This results in inconsistent functioning of firewall in the pair.	Ensure that both devices in a HA pair are connected to the firewall and the devices are online in good health.
HA Pair Decryption Certificates Out-of-Sync	Warning	SSL decryption certificates could not be deployed to device {0} in HA pair {1}. The certificates will be out-of-sync until they are deployed to both devices in the pair. (The Manager will continue to attempt to deploy them until deployment is successful.)	Ensure that the device is connected to the Manager and in good health.
Callback Detectors Out-of-Sync	Warning	The deployment of Callback Detectors to the device {0} failed. The Callback Detectors on the HA pair {1} are out-of-sync as a result. (The Manager will automatically make another attempt to deploy them.)	Ensure that the device is connected to the Manager and in good health.
Device Discovered with Expiring License	Warning	Device {1} was discovered with a license that will expire on {0}.	Renew the expiring license.
Pending Device License Expiration	Warning	Device {0} ({1}) license expires in less than {2} days.	Renew the expiring license.
Pending Device Support License Expiration	Warning	Device {0} (support {1}) license expires in less than {2} days.	Renew the expiring license.
Pending Device Add-On License Expiration	Warning	Device {0} (device {1}) license expires in less than {2} days.	Renew the expiring license.
Pending Device Support Add-On License Expiration	Warning	Device {0} (support {1}) license expired in less than {2} days.	Renew the expiring license.
License Detected for {0} of Type {1}	Warning	License valid until {0}.	Renew the license before it expires.
Pending License Expiration for {0} of Type {1}	Warning	License for this device expires in {0} days.	Renew the license.
Expiring License	Warning	The SSL proxy decryption license key {0} will expire on {1}. Updates to the Sensor to which it is assigned will be prevented once the license has expired. License details - Model:{2}, Capacity:{3}, Required Devices:{4}, Grant ID:{5}, Customer Name:{6}, Expiration:{7}, Assigned To:{8}	Renew the license.
Expiring License	Warning	The SSL proxy decryption license key {0} will expire on {1}. License details - Model:{2}, Capacity:{3}, Required Devices:{4}, Grant ID:{5}, Customer Name:{6}, Expiration:{7}, Assigned To:{8}	Renew the license.
Expired License	Warning	Proxy Decryption License with key {0} has expired. License details - Model:{1}, Capacity:{2}, Required Devices:{3}, Grant ID:{4}, Customer Name:{5}, Expiration:{6}, Assigned To:{7}	Replace the expired license with a valid one.
System License Required	Warning	Sensor {0}, which was added to admin domain {1}, is running without a valid system license. Updates to the Sensor will be prevented until a valid license is assigned.	Assign the device a valid system license.
Expired License	Warning	The system license with key {0} has expired and 30 days passed beyond expiry. License details - Model:{1}, Capacity:{2}, Required Devices:{3}, Grant ID:{4}, Customer Name:{5}, Expiration:{6}, Assigned To:{7}	Replace the expired license with a valid one.
Expired License	Warning	The system license with key {0} has expired. Post 30 days of expiry the license cannot be used. License details - Model:{1}, Capacity:{2}, Required Devices:{3}, Grant ID:{4}, Customer Name:{5}, Expiration:{6}, Assigned To:{7}	Replace the expired license with a valid one.
Expired License	Warning	The evaluation system license with key {0} has expired. License details - Model:{1}, Capacity:{2}, Required Devices:{3}, Grant ID:{4}, Customer Name:{5}, Expiration:{6}, Assigned To:{7}	Replace the expired license with a valid one.
Expiring License	Warning	The system License with key {0} will expire on {1}. Post 30 days of expiry, license cannot be used. License details - Model:{2}, Capacity:{3}, Required Devices:{4}, Grant ID:{5}, Customer Name:{6}, Expiration:{7}, Assigned To:{8}	Renew the license.
Expiring License	Warning	The system License with key {0} will expire on {1}. Post 30 days of expiry, updates to the Sensor to which it is assigned will be prevented. License details - Model:{2}, Capacity:{3}, Required Devices:{4}, Grant ID:{5}, Customer Name:{6}, Expiration:{7}, Assigned To:{8}	Renew the license.
Console Login Failure	Warning	{3} login failure threshold of 3 attempts is exceeded for user name {0} from remote IP Address {1} on remote port {2}.
Device Packet Capturing Terminated	Warning	Packet capturing has been stopped during device re-initialization.	Restart the packet capture, as required.
Packet Capture Complete	Warning	The device is near capacity. Packet captures might not capture all packets.	Verify the packet capture configuration and restart the packet capture, as required.
Device DNS Server Connectivity Status	Warning	DNS server is {0} from the device.	Confirm the status of, and connectivity with, the configured DNS servers, and update the name resolution settings, as needed.
SNMP Trap Received from Load Balancer	Warning	Load balancer "{0}" reported trap type "{1}".
Load Balancer Port Mode Change for {1}	Warning	Load balancer "{0}" reports operating mode for port "{1}" changed to "{2}".
Load Balancer Port HA Mode Change for {1}	Warning	Load balancer "{0}" reports port "{1}" HA mode changed.
Load Balancer HA Mode Change	Warning	Load balancer "{0}" reports HA mode change to "{1}".
Load Balancer HA Status Change	Warning	Load balancer "{0}" reports HA status change to "{1}".
Load Balancer Peer HA Status Change	Warning	Load balancer "{0}" reports peer HA status change to "{1}".
Load Balancer Port Load Balancing Mode Change for {1}	Warning	Load balancer "{0}" reports port "{1}" load balancing mode changed to "{3}"
I/O Module {0} Status Change	Warning	A {1} I/O module has been inserted into slot {0} on the device. A (full) Device reboot is required to make the new I/O module active. An I/O module has been removed from slot {0} on the device. Device reports I/O module {2} in slot {0}.
Hitless Reboot Status	Warning	The device was unable to complete a hitless reboot. It will perform a full reboot instead.
Device Auto-Recovery Status	Warning	The device was unable to complete auto-recovery. It will perform a full reboot instead.
Monitoring Configuration Mismatch	Warning	Device latency monitoring configuration requires Layer 2 pass-through monitoring to be enabled.	Disable moving device to Layer 2 bypass mode on high latency or enable Layer 2 pass-through monitoring.
Device in High Latency Mode	Warning	Device high latency mode is currently {1}. Device high latency mode and Layer 2 bypass mode are currently {1}.	No explicit action is required. The device will attempt to automatically recover from the high latency condition.
Device Reboot Required	Warning	The SSL decryption state and/or the number of flows allocated for decryption has changed on device {0}. (New flow value = {1}). A device reboot is required for the configuration to be updated.	Reboot the device for the configuration to be updated.
Temperature Error	Warning	Device temperature is outside its normal range.	Check the cooling of your server room. Ensure there are no fan failures. Ensure the air used to cool the system is within the thermal specifications for the system (typically below 35°C).