Ad Widget

Collapse

Windows Server flooding Zabbix proxy with SNMP traps

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • oct
    Junior Member
    • Dec 2009
    • 22

    #1

    Windows Server flooding Zabbix proxy with SNMP traps

    Hello,

    We have a Windows Server 2008 that sends SNMP traps to a Zabbix Proxy v2.0.3. This server sends a loooot of traps, what causes the snmpd and snmtt process to use high CPU resources. This high CPU usage causes that some of the snmp traps we need to monitor backup jobs, are lost.

    We have several Windows servers with the same configuration that work well. The server in question is an Intel Server. The snmpd.log looks like this:

    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.50 Enterprise Specific Trap (1) Uptime: 0:07:29.17
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.10.1 = STRING: "Full Redundancy" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.5.1 = INTEGER: 3 SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.3.1 = "" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.2.1 = INTEGER: 139264
    2012-11-22 12:05:22 Server [192.168.100.2] (via UDP: [192.168.100.2]:62369->[192.168.100.3]) TRAP, SNMP v1, community public
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.50 Enterprise Specific Trap (1) Uptime: 0:07:29.17
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.10.1 = STRING: "Redundancy Lost: Deasserted" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.5.1 = INTEGER: 3 SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.3.1 = "" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.2.1 = INTEGER: 139264
    2012-11-22 12:05:23 Server [192.168.100.2] (via UDP: [192.168.100.2]:62369->[192.168.100.3]) TRAP, SNMP v1, community public
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.50 Enterprise Specific Trap (1) Uptime: 0:07:29.17
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.10.1 = STRING: "Non-redundant: sufficient resources from redundancy: Deasserted" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.5.1 = INTEGER: 3 SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.3.1 = "" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.2.1 = INTEGER: 139264
    2012-11-22 12:05:24 Server [192.168.100.2] (via UDP: [192.168.100.2]:62369->[192.168.100.3]) TRAP, SNMP v1, community public
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.50 Enterprise Specific Trap (7) Uptime: 0:07:29.17
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.10.1 = STRING: "Predictive Failure Asserted" SNMPv2-SMI::enterprises.343.2.10.3.5.400.20.1.5.2 = INTEGER: 4 SNMPv2-SMI::enterprises.343.2.10.3.5.400.20.1.3.2 = STRING: "PS2 Status" SNMPv2-SMI::enterprises.343.2.10.3.5.400.20.1.2.2 = INTEGER: 5316608
    2012-11-22 12:05:25 Server [192.168.100.2] (via UDP: [192.168.100.2]:62369->[192.168.100.3]) TRAP, SNMP v1, community public
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.50 Enterprise Specific Trap (1) Uptime: 0:07:35.19
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.10.1 = STRING: "Full Redundancy" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.5.1 = INTEGER: 3 SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.3.1 = "" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.2.1 = INTEGER: 139264
    2012-11-22 12:05:26 Server [192.168.100.2] (via UDP: [192.168.100.2]:62369->[192.168.100.3]) TRAP, SNMP v1, community public
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.50 Enterprise Specific Trap (1) Uptime: 0:07:38.21
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.10.1 = STRING: "Full Redundancy" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.5.1 = INTEGER: 3 SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.3.1 = "" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.2.1 = INTEGER: 139264
    2012-11-22 12:05:27 Server [192.168.100.2] (via UDP: [192.168.100.2]:62369->[192.168.100.3]) TRAP, SNMP v1, community public
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.50 Enterprise Specific Trap (1) Uptime: 0:07:38.21
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.10.1 = STRING: "Redundancy Lost: Deasserted" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.5.1 = INTEGER: 3 SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.3.1 = "" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.2.1 = INTEGER: 139264
    2012-11-22 12:05:28 Server [192.168.100.2] (via UDP: [192.168.100.2]:62369->[192.168.100.3]) TRAP, SNMP v1, community public
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.50 Enterprise Specific Trap (1) Uptime: 0:07:38.21
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.10.1 = STRING: "Non-redundant: sufficient resources from redundancy: Deasserted" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.5.1 = INTEGER: 3 SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.3.1 = "" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.2.1 = INTEGER: 139264
    2012-11-22 12:05:29 Server [192.168.100.2] (via UDP: [192.168.100.2]:62369->[192.168.100.3]) TRAP, SNMP v1, community public
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.50 Enterprise Specific Trap (1) Uptime: 0:07:41.23
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.10.1 = STRING: "Full Redundancy" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.5.1 = INTEGER: 3 SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.3.1 = "" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.2.1 = INTEGER: 139264
    2012-11-22 12:05:30 Server [192.168.100.2] (via UDP: [192.168.100.2]:62369->[192.168.100.3]) TRAP, SNMP v1, community public
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.50 Enterprise Specific Trap (1) Uptime: 0:07:41.23
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.10.1 = STRING: "Redundancy Lost: Deasserted" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.5.1 = INTEGER: 3 SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.3.1 = "" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.2.1 = INTEGER: 139264
    2012-11-22 12:05:32 Server [192.168.100.2] (via UDP: [192.168.100.2]:62369->[192.168.100.3]) TRAP, SNMP v1, community public
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.50 Enterprise Specific Trap (1) Uptime: 0:07:41.23
    SNMPv2-SMI::enterprises.343.2.10.3.5.1000.10.1 = STRING: "Non-redundant: sufficient resources from redundancy: Deasserted" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.5.1 = INTEGER: 3 SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.3.1 = "" SNMPv2-SMI::enterprises.343.2.10.3.5.400.10.1.2.1 = INTEGER: 139264


    This kind of event seem to be referred to power supply redundancy, but Intel Active System Console shows everything in hardware is "Optimal", and no events are generated into the event log. Also, IASC wasn't configured to send traps yet.

    Can anybody help me to find what is generating these traps?

    Thanks all,

    Oct
Working...