Ad Widget

Collapse

Suggestion -> SNMP credentials tied to host

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Reepicheep
    Junior Member
    • Jul 2006
    • 2

    #1

    Suggestion -> SNMP credentials tied to host

    Would it make more sense if the SNMP credentials (SNMP version, Port, Community String) where tied to the host instead of the item? After all every SNMP item for a specific host will use the same credentials. That way you would be able to use a SMNP template for hosts with different community strings.

    For instance I have many different Cisco Routers that are all similar but with different SNMP Comunity Strings, as it currently is I have to set up each item on each host or create a different template for each router where the only thing different between the templates is the community string.

    An idea would be to have a check box in the host details page that when checked gives you the option to set the SNMP credentials. In the same way you also could have a check box for the use of the Zabbix Agent because in the case of an SNMP machine you would not always need the Zabbix Port. The SNMP poller then can get the credentials for each host from the host table instead of the items table.
  • hxtom
    Junior Member
    • Mar 2006
    • 1

    #2
    Yes ,that is a pain for me too, I have some network devices that have different snmp community string , but I want to use the same template.

    Comment

    • nelsonab
      Senior Member
      Zabbix Certified SpecialistZabbix Certified Professional
      • Sep 2006
      • 1233

      #3
      I agree. I recently wanted to add per port traffic information for a 50 port switch and found the web interface too much of a pain to use. I ended up using Konda and mysql-administrator to directly import the snmp data into the items table.
      RHCE, author of zbxapi
      Ansible, the missing piece (Zabconf 2017): https://www.youtube.com/watch?v=R5T9NidjjDE
      Zabbix and SNMP on Linux (Zabconf 2015): https://www.youtube.com/watch?v=98PEHpLFVHM

      Comment

      Working...