Ad Widget

Collapse

SNMPV3 - temporarily disabling SNMP checks

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • nicolas250
    Junior Member
    • Jun 2013
    • 7

    #1

    SNMPV3 - temporarily disabling SNMP checks

    Someone could help me with these errors SNMPv3
    I can not run, to lower the MTU to the problem is not that
    If I do a tcpdump I see the packages, so do not know why I stopped
    thanks

    1420:20130611:150055.945 SNMP item [PD.13] on host [13] failed: first network error, wait for 15 seconds
    1419:20130611:150056.946 SNMP item [PV.13] on host [13] failed: first network error, wait for 15 seconds
    1411:20130611:150057.951 SNMP item [SD.13] on host [13] failed: first network error, wait for 15 seconds
    1408:20130611:150058.953 SNMP item [PD] on host [247] failed: first network error, wait for 15 seconds
    1409:20130611:150058.968 SNMP item [SV.13] on host [13] failed: first network error, wait for 15 seconds
    1420:20130611:150101.958 SNMP item [SD] on host [247] failed: first network error, wait for 15 seconds
    1419:20130611:150102.958 SNMP item [.1.3.6.1.2.1.2.2.1.10.3] on host [247] failed: first network error, wait for 15 seconds
    1411:20130611:150103.964 SNMP item [.1.3.6.1.2.1.2.2.1.16.3] on host [247] failed: first network error, wait for 15 seconds
    1422:20130611:150119.991 SNMP item [wan2d.13] on host [13] failed: another network error, wait for 15 seconds
    1422:20130611:150126.003 SNMP item [PD] on host [247] failed: another network error, wait for 15 seconds
    1422:20130611:150141.053 SNMP item [wan1u.13] on host [13] failed: another network error, wait for 15 seconds
    1422:20130611:150159.091 temporarily disabling SNMP checks on host [247]: host unavailable
    1408:20130611:150209.982 SNMP item [.1.3.6.1.2.1.2.2.1.16.126] on host [10.64.0.126] failed: first network error, wait for 15 seconds
    1422:20130611:150210.115 temporarily disabling SNMP checks on host [13]: host unavailable
    1422:20130611:150224.128 resuming SNMP checks on host [10.64.0.126]: connection restored
    1422:20130611:150235.337 enabling SNMP checks on host [92]: host became available
    1422:20130611:150247.374 enabling SNMP checks on host [28]: host became available
    1422:20130611:150259.564 enabling SNMP checks on host [247]: host became available
    1422:20130611:150311.745 enabling SNMP checks on host [13]: host became available
    1411:20130611:150416.552 SNMP item [wan1u.92] on host [92] failed: first network error, wait for 15 seconds
    1411:20130611:150425.576 SNMP item [SV] on host [28] failed: first network error, wait for 15 seconds
    1422:20130611:150437.812 SNMP item [wan1u.92] on host [92] failed: another network error, wait for 15 seconds
    1422:20130611:150446.833 SNMP item [SV] on host [28] failed: another network error, wait for 15 seconds
    1422:20130611:150458.854 SNMP item [PD.92] on host [92] failed: another network error, wait for 15 seconds
    1422:20130611:150507.876 SNMP item [wan2u] on host [28] failed: another network error, wait for 15 seconds
    1422:20130611:150519.918 temporarily disabling SNMP checks on host [92]: host unavailable
    1422:20130611:150531.999 temporarily disabling SNMP checks on host [28]: host unavailable
  • randydrobinson
    Junior Member
    • Jan 2013
    • 2

    #2
    I am also seeing similar errors on a zabbix proxy.

    SNMP works fine when the host is not monitored via the proxy. When the host is monitored via proxy we see the following:

    @sd-zabbixproxy ~]# tail -f /tmp/zabbix_proxy.log
    32110:20130925:041635.525 housekeeper deleted 3186 records from history (spent 0.012495 seconds)
    32004:20130925:041651.659 SNMP item [ifOperStatus.194] on host [SD1] failed: another network error, wait for 15 seconds
    31951:20130925:041652.087 Received configuration data from server. Datalen 16606
    32004:20130925:041712.666 temporarily disabling SNMP checks on host [SD1]: host unavailable
    32004:20130925:041812.739 enabling SNMP checks on host [SD1]: host became available
    31995:20130925:041821.227 SNMP item [ifOperStatus.194] on host [SD1] failed: first network error, wait for 15 seconds
    32004:20130925:041838.818 resuming SNMP checks on host [SD1]: connection restored
    31985:20130925:041851.231 SNMP item [ifOperStatus.194] on host [SD1] failed: first network error, wait for 15 seconds
    32004:20130925:041912.828 SNMP item [ifOperStatus.194] on host [SD1] failed: another network error, wait for 15 seconds
    32004:20130925:041933.843 SNMP item [ifDescr.2] on host [SD1] failed: another network error, wait for 15 seconds
    32004:20130925:041948.918 resuming SNMP checks on host [SD1]: connection restored
    31999:20130925:042003.238 SNMP item [ifDescr.1] on host [SD1] failed: first network error, wait for 15 seconds
    31964:20130925:042005.239 SNMP item [ifDescr.2] on host [SD1] failed: first network error, wait for 15 seconds
    31985:20130925:042006.239 SNMP item [ifDescr.3] on host [SD1] failed: first network error, wait for 15 seconds
    31974:20130925:042007.237 SNMP item [ifDescr.194] on host [SD1] failed: first network error, wait for 15 seconds
    32004:20130925:042028.926 SNMP item [ifDescr.2] on host [SD1] failed: another network error, wait for 15 seconds
    32004:20130925:042049.932 SNMP item [ifOperStatus.194] on host [SD1] failed: another network error, wait for 15 seconds
    32004:20130925:042110.974 temporarily disabling SNMP checks on host [SD1]: host unavailable
    32004:20130925:042211.051 enabling SNMP checks on host [SD1]: host became available


    We have a trigger condition setup like this:

    Name: {HOSTNAME} SNMP Failed

    Expression: {SD2:cpu.nodata(14400)}=1

    Description: {HOSTNAME} SNMP Failed. Check configuration, ACL.


    Please advise why the trigger condition is met when the host is monitored via proxy but not triggered when monitored from the main zabbix server.

    Comment

    • nicolas250
      Junior Member
      • Jun 2013
      • 7

      #3
      Originally posted by randydrobinson
      I am also seeing similar errors on a zabbix proxy.

      SNMP works fine when the host is not monitored via the proxy. When the host is monitored via proxy we see the following:

      @sd-zabbixproxy ~]# tail -f /tmp/zabbix_proxy.log
      32110:20130925:041635.525 housekeeper deleted 3186 records from history (spent 0.012495 seconds)
      32004:20130925:041651.659 SNMP item [ifOperStatus.194] on host [SD1] failed: another network error, wait for 15 seconds
      31951:20130925:041652.087 Received configuration data from server. Datalen 16606
      32004:20130925:041712.666 temporarily disabling SNMP checks on host [SD1]: host unavailable
      32004:20130925:041812.739 enabling SNMP checks on host [SD1]: host became available
      31995:20130925:041821.227 SNMP item [ifOperStatus.194] on host [SD1] failed: first network error, wait for 15 seconds
      32004:20130925:041838.818 resuming SNMP checks on host [SD1]: connection restored
      31985:20130925:041851.231 SNMP item [ifOperStatus.194] on host [SD1] failed: first network error, wait for 15 seconds
      32004:20130925:041912.828 SNMP item [ifOperStatus.194] on host [SD1] failed: another network error, wait for 15 seconds
      32004:20130925:041933.843 SNMP item [ifDescr.2] on host [SD1] failed: another network error, wait for 15 seconds
      32004:20130925:041948.918 resuming SNMP checks on host [SD1]: connection restored
      31999:20130925:042003.238 SNMP item [ifDescr.1] on host [SD1] failed: first network error, wait for 15 seconds
      31964:20130925:042005.239 SNMP item [ifDescr.2] on host [SD1] failed: first network error, wait for 15 seconds
      31985:20130925:042006.239 SNMP item [ifDescr.3] on host [SD1] failed: first network error, wait for 15 seconds
      31974:20130925:042007.237 SNMP item [ifDescr.194] on host [SD1] failed: first network error, wait for 15 seconds
      32004:20130925:042028.926 SNMP item [ifDescr.2] on host [SD1] failed: another network error, wait for 15 seconds
      32004:20130925:042049.932 SNMP item [ifOperStatus.194] on host [SD1] failed: another network error, wait for 15 seconds
      32004:20130925:042110.974 temporarily disabling SNMP checks on host [SD1]: host unavailable
      32004:20130925:042211.051 enabling SNMP checks on host [SD1]: host became available


      We have a trigger condition setup like this:

      Name: {HOSTNAME} SNMP Failed

      Expression: {SD2:cpu.nodata(14400)}=1

      Description: {HOSTNAME} SNMP Failed. Check configuration, ACL.


      Please advise why the trigger condition is met when the host is monitored via proxy but not triggered when monitored from the main zabbix server.

      now, i use external script to check snmp

      Comment

      • officielmc
        Member
        • Apr 2011
        • 32

        #4
        Hi,

        I have also the same problem, but when i tried to get value using command line it's works. It's really strange.
        I have this problems with Juniper SSG140, and the wierd things it's I have to monitor 2 Juniper for each location (Main and backup) and everytime for one device ok no error but for the osecond one I got this error.


        item [Failover_status] on host [BJSOPS-router-back] failed: first network error, wait for 150 seconds
        item [Interface.0] on host [BJSOPS-router-back] failed: first network error, wait for 150 seconds
        item [Interface.0out] on host [BJSOPS-router-back] failed: first network error, wait for 150 seconds
        item [Interface.1] on host [BJSOPS-router-back] failed: first network error, wait for 150 seconds
        item [Interface.1out] on host [BJSOPS-router-back] failed: first network error, wait for 150 seconds
        SNMP checks on host [BJSOPS-router-back]: connection restored
        item [Failover_interface] on host [BJSOPS-router-back] failed: first network item [VPN_Status] on host [BJSOPS-router-back] failed: first network error, wait for 150 seconds


        I'm using zabbix 2.0.8 with centos 6.4 and postgresql.

        Thanks

        Comment

        • officielmc
          Member
          • Apr 2011
          • 32

          #5
          Solved for me,

          The problem was the local-engine-id number it was the same in all my devices. So maybe you can check if you don't have the same problem.

          Comment

          Working...