Ad Widget

Collapse

Zabbix 3.2 SNMPv3 Agent

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • kyern
    Junior Member
    • Nov 2016
    • 14
    #1

    Zabbix 3.2 SNMPv3 Agent

    Доброго времени суток!
    Есть проблема с мониторингом ИБП от APC через Zabbix 3.2
    Создан узел сети для ИБП, прописан SNMP-интерфейс 192.168.254.31
    Прописаны элементы данных с нужными OID
    Параметры авторизации следующие:
    Имя безопасности monitoring
    Уровень безопасности authPriv
    Протокол аутентификации MD5
    Пароль аутентификации AUTHPASSPHRASE
    Протокол безопасности DES
    Ключевая фраза безопасности PRIVPASSPHRASE
    На ИБП создан пользователь "monitoring" для доступа по SNMP, для него прописаны AUTHPASSPHRASE и PRIVPASSPHRASE
    Мониторится все через Zabbix Proxy
    Весь вопрос в том, что через Zabbix это все не мониторится, в логах
    Code:
    Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key)
    При этом с прокси делаю snmpget:
    Code:
    snmpget -v 3 -a MD5 -A AUTHPASSPHRASE -l authPriv -u monitoring -x DES -X PRIVPASSPHRASE 192.168.254.31 .1.3.6.1.4.1.318.1.1.1.2.2.1.0
    Все проходит нормально:
    Code:
    SNMPv2-SMI::enterprises.318.1.1.1.2.2.1.0 = Gauge32: 100
    Ткните носом в ошибку, пожалуйста
    Tags: None
    • DmitryL
      Senior Member
      Zabbix Certified SpecialistZabbix Certified Professional
      • May 2016
      • 278
      #2
      Если снмпгет выполняется успешно с прокси, но ключ не работает - значит проблема в конфигурации ключа.
      Тайпо, лишний параметр например...
      А ещё убедитесь что прокси получил свежую конфигурацию от сервера.

        Comment

        • kyern
          Junior Member
          • Nov 2016
          • 14
          #3
          А теперь вишенка на торте
          Вот то что проскальзывает в логах Zabbix - сервера
          Code:
           15526:20161227:154854.770 item "UPSR1:apc_snmp_batt_test" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:154925.155 item "UPSR1:apc_snmp_batt_test" became supported
 15524:20161227:154944.802 error reason for "UPSR1:upsAdvBatteryCapacity" changed: SNMP error: authorizationError (access denied to that object)
 15525:20161227:154956.357 item "UPSR1:apc_snmp_batt_test" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15526:20161227:155242.164 item "UPSR1:iemStatusProbeCurrentTemp" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:155244.170 item "UPSR1:upsAdvBatteryActualVoltage" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15527:20161227:155245.239 item "UPSR1:upsAdvBatteryCapacity" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15527:20161227:155246.277 item "UPSR1:upsAdvBatteryRunTimeRemaining" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15527:20161227:155247.351 item "UPSR1:upsAdvBatteryTemperature" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15526:20161227:155249.660 item "UPSR1:upsAdvInputFrequency" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15526:20161227:155250.837 item "UPSR1:upsAdvInputLineVoltage" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15526:20161227:155251.871 item "UPSR1:upsAdvOutputCurrent" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15524:20161227:155253.496 item "UPSR1:upsAdvOutputFrequency" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15524:20161227:155253.496 item "UPSR1:upsAdvOutputLoad" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:155255.530 item "UPSR1:upsAdvOutputVoltage" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:155429.929 item "UPSR1:upsAdvBatteryReplaceIndicator" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:155433.813 item "UPSR1:upsAdvIdentSerialNumber" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:155441.126 item "UPSR1:upsBasicBatteryLastReplaceDate" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:155441.127 item "UPSR1:upsBasicBatteryStatus" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15526:20161227:160429.148 item "UPSR1:upsAdvBatteryCapacity" became supported
 15526:20161227:160458.329 item "UPSR1:upsAdvBatteryCapacity" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15524:20161227:161425.152 item "UPSR1:apc_snmp_batt_test" became supported
 15526:20161227:161426.231 item "UPSR1:iemStatusProbeCurrentTemp" became supported
 15524:20161227:161427.232 item "UPSR1:upsAdvBatteryActualVoltage" became supported
 15526:20161227:161428.322 item "UPSR1:upsAdvBatteryCapacity" became supported
 15524:20161227:161429.742 item "UPSR1:upsAdvBatteryReplaceIndicator" became supported
 15527:20161227:161430.521 item "UPSR1:upsAdvBatteryRunTimeRemaining" became supported
 15527:20161227:161431.779 item "UPSR1:upsAdvBatteryTemperature" became supported
 15524:20161227:161432.805 item "UPSR1:upsAdvIdentSerialNumber" became supported
 15524:20161227:161435.048 item "UPSR1:upsAdvInputLineVoltage" became supported
 15524:20161227:161436.089 item "UPSR1:upsAdvOutputCurrent" became supported
 15524:20161227:161436.090 item "UPSR1:upsAdvOutputFrequency" became supported
 15526:20161227:161439.659 error reason for "UPSR1:upsBasicBatteryLastReplaceDate" changed: No Such Instance currently exists at this OID
 15525:20161227:161455.061 item "UPSR1:apc_snmp_batt_test" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15527:20161227:161458.417 item "UPSR1:upsAdvBatteryCapacity" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15526:20161227:161506.592 item "UPSR1:upsAdvOutputCurrent" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15527:20161227:161528.382 item "UPSR1:upsAdvBatteryActualVoltage" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:161531.531 item "UPSR1:upsAdvBatteryTemperature" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:161537.631 item "UPSR1:upsAdvOutputFrequency" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15527:20161227:161557.125 item "UPSR1:iemStatusProbeCurrentTemp" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15525:20161227:161604.610 item "UPSR1:upsAdvInputLineVoltage" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
 15527:20161227:161631.791 item "UPSR1:upsAdvBatteryRunTimeRemaining" became not supported: Cannot connect to "192.168.254.31:161": Authentication failure (incorrect password, community or key).
          Это при том, что никаких изменений в элементы данных внесено не было.
          Само по себе получило данные и отвалилось с ошибкой аутентификации обратно.
          Last edited by kyern; 28-12-2016, 05:46.

            Comment

            • Kos
              Senior Member
              Zabbix Certified SpecialistZabbix Certified Professional
              • Aug 2015
              • 3406
              #4
              Если мне не изменяет мой склероз, то показанные Вами события должны "светиться" в логе того, кто делает опрос устройства. Т.е. в Вашем случае - не Zabbix-сервера, а Zabbix-прокси. У Вас точно настроено мониторить этот девайс через Zabbix-прокси? А если надо таки не с прокси, а с сервера, то что показывает snmpget с этого сервера?

                Comment

                • kyern
                  Junior Member
                  • Nov 2016
                  • 14
                  #5
                  Originally posted by Kos
                  Если мне не изменяет мой склероз, то показанные Вами события должны "светиться" в логе того, кто делает опрос устройства. Т.е. в Вашем случае - не Zabbix-сервера, а Zabbix-прокси. У Вас точно настроено мониторить этот девайс через Zabbix-прокси? А если надо таки не с прокси, а с сервера, то что показывает snmpget с этого сервера?
                  Вот мне тоже кажется, что это должно отображаться в логах моего прокси, но нет, по факту это висит на сервере. На узле сети стоит мониторинг через прокси, с другими узлами сети все нормально, есть несколько свичей, в той же серверной, в той же сети, но они мониторятся по SNMPv2 и с ними проблем нет. Уже перезагружал и сервер и прокси и сетевые интерфейсы на ИБП. Осталось только попробовать удалить и снова добавить узлы сети.

                    Comment

                    • kyern
                      Junior Member
                      • Nov 2016
                      • 14
                      #6
                      Передобавил узлы сети, картина не поменялась

                        Comment

                        • kyern
                          Junior Member
                          • Nov 2016
                          • 14
                          #7
                          Проблема до сих пор актуальна, есть у кого еще какие соображения на этот счет?

                            Comment

                            • Nagainos
                              Member
                              • Oct 2016
                              • 46
                              #8
                              Поставьте Debug=4 на прокси и на сервере, станут видны ошибки от SNMP-библиотеки, может там будут подробности

                                Comment

                                Previous template Next
                                Working...