Platform Event Trap PET Explained in Simple Words
A Platform Event Trap also called PET is a message that comes from the hardware inside a server or network device, it tells you when something important or dangerous is happening, PET alerts you before the operating system starts or even when the system is not working, this makes PET one of the best early warning tools in any data center Increditools
In this guide you will learn what PET is how it works why it matters and how to use it, everything is explained in basic words so anyone can understand it
What is a Platform Event Trap PET
A Platform Event Trap is a fast alert that is sent when a part inside the system detects a problem, the alert is sent using a protocol called SNMP, this protocol helps devices send messages to monitoring tools
PET warns you about events that happen at the hardware level, these events happen before the operating system loads or when the system is stuck, because of this PET gives you the earliest possible warning about a failure
Simple meaning of PET
PET is a message that warns you about hardware problems
PET works even when the operating system is down
PET helps you fix things before the server stops working
Why PET is important
It protects your servers from damage
It helps you avoid downtime
It warns you early so you can respond fast
Where PET Events Come From
PET events do not come from software, they come from the physical parts of the server, these parts always run even when the system is powered off, they watch for problems and send alerts when needed
Main sources of PET events
BIOS or UEFI firmware
The baseboard management controller also called BMC
Fans and temperature sensors
Power supplies
Voltage controllers
CPU and memory sensors
Chassis intrusion sensors
These parts make sure the system is safe at all times. When something looks wrong they send a PET message.
Table of Common PET Event Categories
This table shows the types of events that usually trigger PET alerts
| Event Category | What It Means |
|---|---|
| Thermal events | The system is too hot or cooling is not working |
| Fan events | A fan is slow or stopped |
| Power events | Power supply failed or lost input power |
| Voltage events | Voltage is too high or too low |
| CPU or memory events | CPU or memory has errors |
| Chassis alerts | Someone opened the case or tampered with the system |
| Boot errors | BIOS reports a startup failure |
These are the main reasons a PET alert happens, they help you see what part needs attention
How PET Works Step by Step
PET follows a simple and clear process, sensors watch the system, when they find a problem the BMC records it, then a PET message is sent to your monitoring tool
Simple steps of PET operation
A sensor detects a problem
The BMC stores the event in the event log
The event gets classified
A PET message is created
The message is sent to your monitoring system
This happens very fast, PET messages are sent without waiting for any reply so alerts never get slowed down
Table of PET Message Fields
A PET message contains several pieces of information, these help monitoring tools understand what happened
| PET Field | Purpose |
|---|---|
| Sensor type | Shows which part triggered the event |
| Event type | Explains the nature of the problem |
| Severity | Tells if the issue is warning critical or severe |
| Event time | Shows when the event happened |
| Event source | Tells where the event started |
| Event data | Contains details about the event |
| Vendor info | Extra data added by the manufacturer |
These fields help you know exactly what is going wrong and where
Real Examples of PET Events
Here are simple examples of situations that cause PET alerts
Thermal examples
CPU is too hot
Case temperature is too high
Cooling system not working
Fan examples
Fan is spinning too slow
Fan has stopped
Fan is missing
Power examples
Power supply failed
Power input lost
Redundant power not available
Voltage examples
High voltage detected
Low voltage detected
Voltage regulator failure
Security examples
Chassis opened
Intrusion switch triggered
Boot examples
BIOS error
Memory test failed
CPU failed to start
These events can damage systems if not handled early, PET helps you act before that happens
How to Configure PET
Configuring PET is easy when you follow the right steps, most systems use a BMC interface or a vendor management tool
Steps to enable PET
Turn on PET in the BMC menu
Set up the SNMP trap receiver address
Choose an SNMP community or SNMPv3 user
Adjust event filters
Test the PET output
Where you can configure PET
Server BMC web interface
BIOS or UEFI menu
Vendor tools like UCS Manager
Command line tools like IPMItool
What you must configure
PET on or off
SNMP destination server
Event filters
Security settings like SNMPv3
When finished PET will send alerts to your monitoring tool
PET in Monitoring Systems
PET is supported by many monitoring tools, these tools help you view alerts store them and create actions
Monitoring tools that support PET
SolarWinds
Zabbix
Nagios
PRTG
ManageEngine
DataDog with SNMP traps
Splunk with SNMP collector
What monitoring tools can do with PET
Show alerts instantly
Make dashboards
Create support tickets
Trigger automated fixes
Record events for history
Help find root causes
With PET you get alerts at the hardware level before the system fails
PET and Syslog Working Together
PET is fast and simple, syslog is detailed and provides history. Both are important
PET strengths
Sends alerts right away
Works without the operating system
Very light and fast
Syslog strengths
Stores complete event history
Contains detailed information
Helps with deep troubleshooting
Best practice
Use PET for fast warnings
Use syslog for deep analysis
Together they give complete visibility
Troubleshooting PET Problems
Sometimes PET does not behave as expected, here are simple solutions
PET not sending alerts
PET might be off
Wrong SNMP destination
SNMP service not enabled
Network firewall blocking port 162
Too many PET alerts
Sensor thresholds too low
Bad sensor
Filters not configured
Monitoring tool cannot read PET
Missing MIB files
Wrong parser rules
Vendor fields not recognized
Duplicate PET alerts
Multiple BMC controllers
Two sensors for one event
Fixing PET issues starts with checking the event log inside the BMC
PET and Security
PET can help with security too, it reports physical issues and strange hardware activity
Security risks if using SNMPv2c
Data is not encrypted
Attackers can read messages
Attackers can spoof alerts
Benefits of SNMPv3
Encryption
Authentication
User control
Safe communication
Security events PET can detect
Case opened
Power removed without reason
Hardware tampering
Abnormal temperature from hidden workloads
Using PET as part of a security plan strengthens physical protection
Best Practices for Using PET
Follow these simple guidelines
Always enable SNMPv3
Use more than one trap receiver
Update firmware often
Test PET alerts on a schedule
Avoid sending non critical alerts
Connect PET to ticketing tools
Match PET events with syslog events
Monitor PET history for patterns
These steps help you use PET in the most stable and safe way
Frequently Asked Questions
What is a Platform Event Trap?
A Platform Event Trap is a fast alert from the hardware that warns you when a part inside the server has a problem, it sends a message before the operating system starts so you get early warning of failures
Why is a Platform Event Trap important?
A Platform Event Trap helps you stop hardware damage and avoid downtime, it gives you early alerts so you can fix problems before the system stops working
How does a Platform Event Trap work?
The system has sensors that watch for problems, when they detect an issue the BMC records it and creates a Platform Event Trap, the message is then sent to your monitoring tool
What problems can a Platform Event Trap detect?
A Platform Event Trap can detect heat issues power loss fan failure voltage problems boot errors and even chassis intrusion
Can a Platform Event Trap work when the system is off?
Yes a Platform Event Trap works even when the operating system is down because it comes from the hardware and not from software
How do I set up a Platform Event Trap?
You turn it on inside the BMC, you set the SNMP trap destination, you adjust event filters, then you test the alert to make sure it works
Does a Platform Event Trap help with security?
Yes it can warn you when someone opens the case or tampers with the hardware, it also helps detect strange power or temperature activity
Which monitoring tools support Platform Event Trap?
Tools like Solar Winds Zabbix Nagios PRTG Manage Engine and Splunk can receive Platform Event Trap alerts through SNMP
What should I do if I get too many Platform Event Trap alerts?
You should check sensor settings and tune the event filters, some sensors may need repair, set filters only for important alerts
Does a Platform Event Trap need SNMPv3?
SNMPv3 is strongly recommended because it gives safe and encrypted communication, SNMPv2c is less secure
Conclusion
Platform Event Traps are one of the most powerful and reliable tools for detecting hardware problems early, they work even when the operating system is not working, they alert you about the most serious issues like heat problems fan failures power issues and physical tampering, PET gives you time to act before damage happens
