[root@monitor ~]# snmpwalk -u beuken -v3 -A xxxxxx -a MD5 -X xxxxxx -x DES -l authPriv     printer_addr 

snmpwalk: Bad context specified

[root@monitor ~]# snmpwalk -u beuken -v3 -A xxxxxx -a MD5 -X xxxxxx -x DES -l authPriv     printer_addr    -n GWMCS

SNMPv2-MIB::sysDescr.0 = STRING: RICOH MP 2554 1.16 / RICOH Network Printer C model / RICOH Network Scanner C model

SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.367.1.1

DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (30480400) 3 days, 12:40:04.00

SNMPv2-MIB::sysContact.0 = STRING:

SNMPv2-MIB::sysName.0 = STRING: MP 2554

….

jmb

On 10 Nov 2017, at 16:32, Adam Armstrong <adama@observium.org> wrote:

Why do you need to specify a context?

adam.

Adam Armstrong

CEO & Lead Architect

Observium Limited

On 2017-11-10 15:28:09, Jean-Michel Beuken <jean-michel.beuken@uclouvain.be> wrote:

Hi,

I try to monitor printers with snmp V3 ( for ex : RICOH MP 2554  or LaserJet 500 color M551 )

the snmpwalk works but I must specify a context name ( -n option ) 

How can I put this parameter in observium ( CE ) ?

in the snmp "Authentication Configuration” form, there is no field for context value.

thanks,