PowerFlex SNMP Trap Behavior Differences in 3.x and 4.x

Summary: This article discusses the changes in SNMP trap behavior between PowerFlex 3.x and 4.x, focusing on the shift from repeated traps to state-change notifications and the implications for external monitoring systems. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Instructions

In earlier PowerFlex versions (3.x), SNMP traps could be configured to send alerts to a custom address at regular intervals while an alert was active. This allowed external monitoring systems to track alert states based on the presence or absence of these repeated traps. Further details regarding 3.x behavior can be found below:

In PowerFlex 4.x, SNMP behavior changed to sending a single trap only on state changes (e.g., alert raised or cleared). Also, the traps for alert initiation and clearance contain a field that indicates the difference between a raise or clear event (E:1139.101.1.4). Further detail regarding 4.x behavior can be found below:

In the below example, E:1139.101.1.4="SIO03.01.0000001" indicates the raised alarm, and E:1139.101.1.4="SIO03.01.1000001" indicates the cleared alarm.

 
 09:48:48.149615 eth0  In  IP PFMPSERVER.48030 > SNMPSERVER.snmptrap:  C="redlab" V2Trap(198)  system.sysUpTime.0=9756172 S:1.1.4.1.0=E:1139.101.2 E:1139.101.1.1=3 E:1139.101.1.2="SDS.SDS.SDS_Disconnected" E:1139.101.1.3="ee5d821f00000004" E:1139.101.1.4="SIO03.01.0000001" S:18.1.3.0=10.10.10.151
 
09:50:54.048872 eth0  In  IP PFMPSERVER.42771 > SNMPSERVER.snmptrap:  C="redlab" V2Trap(198)  system.sysUpTime.0=9768763 S:1.1.4.1.0=E:1139.101.2 E:1139.101.1.1=3 E:1139.101.1.2="SDS.SDS.SDS_Disconnected" E:1139.101.1.3="ee5d821f00000004" E:1139.101.1.4="SIO03.01.1000001" S:18.1.3.0=10.10.10.151

For technical reasons, a 4.x MDS/PFMC will still use the legacy behavior of sending alerts at a regular 60-second interval while the alert is active. The new behavior is only observed in the Production PowerFlex cluster.

Example of Legacy SNMP Trap Behavior

 23:39:33.345132 eth0  In  IP PFMPSERVER.49421 > SNMPSERVER.snmptrap:  C="LAB_01" V2Trap(285)  system.sysUpTime.0=16206006 S:1.1.4.1.0=E:1139.101.2 E:1139.101.1.1=2 E:1139.101.1.2="System.Oscillating_Failures.Object_has_oscillating_failures" E:1139.101.1.3="2514c01a00000003" E:1139.101.1.4="SIO01.03.0000001" E:1139.101.1.6="52ffd8be4aed86cf" E:1139.101.1.7="mds" S:18.1.3.0=10.10.10.210
 
<60 SECONDS LATER>
 
23:40:33.354340 eth0  In  IP PFMPSERVER.13890 > SNMPSERVER.snmptrap:  C="LAB_01" V2Trap(285)  system.sysUpTime.0=16212006 S:1.1.4.1.0=E:1139.101.2 E:1139.101.1.1=2 E:1139.101.1.2="System.Oscillating_Failures.Object_has_oscillating_failures" E:1139.101.1.3="2514c01a00000003" E:1139.101.1.4="SIO01.03.0000001" E:1139.101.1.6="52ffd8be4aed86cf" E:1139.101.1.7="mds" S:18.1.3.0=10.10.10.210
 
<60 SECONDS LATER>
 
23:41:33.327966 eth0  In  IP PFMPSERVER.30892 > SNMPSERVER.snmptrap:  C="LAB_01" V2Trap(285)  system.sysUpTime.0=16218006 S:1.1.4.1.0=E:1139.101.2 E:1139.101.1.1=2 E:1139.101.1.2="System.Oscillating_Failures.Object_has_oscillating_failures" E:1139.101.1.3="2514c01a00000003" E:1139.101.1.4="SIO01.03.0000001" E:1139.101.1.6="52ffd8be4aed86cf" E:1139.101.1.7="mds" S:18.1.3.0=10.10.10.210

Affected Products

PowerFlex rack, ScaleIO
Article Properties
Article Number: 000307540
Article Type: How To
Last Modified: 13 Apr 2025
Version:  1
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.