Ad Widget

Collapse

SNMPv3 with context engine ID

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • greyser81
    Junior Member
    • Jan 2011
    • 2

    #1

    SNMPv3 with context engine ID

    Hello, we are trying Zabbix and hope to monitor our device with Zabbix. But we hit a wall, we need to use snmpv3 with context engine ID.

    Our ISP force us to use a different context engine ID for each device. We have to monitor 1600 device and more.

    I'm trying to configure an snmpv3 item in Zabbix to use "context engine ID" but I cannot find the right parameter or the right place to put the contexte Engine ID in the GUI.

    I know I have the right information, when I use in CLI snmpwalk or snmpget, I can talk to the device without any problem.

    This is the command I use :

    snmpget -v 3 -u UTILISATEUR -l authPriv -a MD5 -A PASSPHRASE -x DES -X PASSPHRASE -E AAAAAAAAAAA x.x.x.x sysName.0
    .1.3.6.1.2.1.1.5.0 = STRING: Name_of_the_device

    the information I receive is the right information. The context engine ID is and hexadecial value of 12 characters.

    But When I try to configure the item in the Zabbix GUI, I cannot find the right place to add the context engine ID of the device. Can I add a parameter in some way to informe Zabbix that he need to use a context engine ID when he query the device ?

    I try many parameter in the OID and Key field, but nothing work.

    Is it possible with Zabbix to send more information with snmp query then the OID ? If yes, how ?

    Where do I add the context engine ID in the item ? We need to be able to send the "-E AAAAAAAAAAA" when zabbix send it's query to the proxy.



    Thank you for you help.

    P.S sorry for my english, it's not my mother tongue.
    Attached Files
  • dimi
    Junior Member
    Zabbix Certified Trainer

    • Nov 2004
    • 13

    #2
    I have also the same problem with Zabbix v.2.0.3, it seems with the SNMPv3 agent not support some of the option flag usually used for this kind of version, for example in my case i have need the "-n" (context name) to monitor the Brocade 82xx SAN Switch. At the moment i workaround the problem using an external check that call "snmpget" but i think is not the best solution.
    I also open a feature request ZBXNEXT-1438 i hope this is feature is coming nearly in the future.

    Thanks to Zabbix Team for the great work!

    Comment

    Working...