snmpd: checkLowVoltageTrap: error parsing current voltage of sensor VCC 5V [artificial trap sent]

[Thomas_Eichelbu]

Hello team, 

i stumbled or some quite interesting messages in /var/log/messages ...

messages:Mar 11 11:55:54 2026 NATSBGFIRE01 snmpd: checkLowVoltageTrap: error parsing current voltage of sensor VCC 5V [artificial trap sent]
messages:Mar 12 08:47:21 2026 NATSBGFIRE01 snmpd: checkLowVoltageTrap: error parsing current voltage of sensor CPU1 Vcore [artificial trap sent]
messages.1:Mar 10 01:48:24 2026 NATSBGFIRE01 snmpd: checkLowVoltageTrap: error parsing current voltage of sensor CPU0 Vcore [artificial trap sent]
messages.10:Feb 23 19:31:24 2026 NATSBGFIRE01 snmpd: checkLowVoltageTrap: error parsing current voltage of sensor VCC 12V [artificial trap sent]
messages.10:Feb 24 10:23:43 2026 NATSBGFIRE01 snmpd: checkLowVoltageTrap: error parsing current voltage of sensor CPU0 Vcore [artificial trap sent]
messages.10:Feb 24 15:30:40 2026 NATSBGFIRE01 snmpd: checkLowVoltageTrap: error parsing current voltage of sensor CPU0 DDR4-1 [artificial trap sent]

I see this on a cluster member on a 15600 (EOL) firewall.
under normal circumstances i would raise a ticket to TAC and maybe even a RMA ...
but here the customer still runs EOL hardware with any subscriptions 😞 
no chance to raise a TAC ticket ...

maybe you, my fellow Checkmates can interpret this messages ...

the other remaining cluster members doesnt show this logs ...


best regards

[TurgutKaplanogl · Accepted solution]

Hello Thomas,

This situation may have multiple possible causes. One possibility is that it is related to the version you are currently using and the issue may already be resolved in a newer version. Another possibility is that it could actually be a physical hardware problem. To verify this, I would suggest a few methods:

1. Check the returned values with SNMP
You can run an snmpwalk query for the OIDs that are generating the alert logs to see the actual returned values:

snmpwalk -v2c -c <community> <appliance_ip> .1.3.6.1.4.1.2620.1.6.7.8.3.1.3.1.0

You can find the hardware sensor OIDs for the 15600 appliance at the following link:
https://support.checkpoint.com/results/sk/sk119232

If you see valid values (you can easily verify the correct values and health status from the Hardware Sensors section in the Gaia WebUI) then the data is likely correct.

If you do not see valid values, there might be an issue related to the snmpd service. In that case my first recommendation would be to restart the snmpd service.

If restarting the service does not help, you can try upgrading the device to the latest recommended version supported by the appliance and then install the latest recommended Jumbo Hotfix to test again.

In some scenarios a private hotfix may be required. However, since you cannot open a case with TAC, this option might not be available for you.

2. As a second option, I would also recommend upgrading the version and installing the latest Jumbo Hotfix.

3. You can perform a physical check using the Hardware Diagnostic Tool.
Additionally, it would be useful to review the Hardware Sensors section in the Gaia WebUI.

Since the device is already End of Support (EOS), the options I can recommend are somewhat limited. I hope the information above will still be helpful for your troubleshooting.

Best Regards,

TK

[Thomas_Eichelbu]

Great ... 
Thank you for sharing this Link
https://support.checkpoint.com/results/sk/sk119232

i will built some SNMP monitoring for this stuff to measure it ... 
Thank you

best regards