Quick Reference Guide
PowerConnect B-Series TI24X Configuration Guide 1023
53-1002269-02
SNMP v3 Configuration examples
32
Syntax: show snmp user
Interpreting varbinds in report packets
If an SNMP version 3 request packet is to be rejected by an SNMP agent, the agent sends a report
packet that contains one or more varbinds. The varbinds contain additional information, showing
the cause of failures. An SNMP manager application decodes the description from the varbind. The
following table presents a list of varbinds supported by the SNMP agent.
SNMP v3 Configuration examples
The following sections present examples of how to configure SNMP v3.
Simple SNMP v3 configuration
PowerConnect(config)# snmp-s group admingrp v3 priv read all write all notify all
PowerConnect(config)# snmp-s user adminuser admingrp v3 auth md5 <auth password>
priv <privacy password>
PowerConnect(config)# snmp-s host <dest-ip> version v3 privacy adminuser
Table 0.12:
Varbind object Identifier Description
1. 3. 6. 1. 6. 3. 11. 2. 1. 3. 0 Unknown packet data unit.
1. 3. 6. 1. 6. 3. 12. 1. 5. 0 The value of the varbind shows the engine ID that needs to be used in
the snmp-server engineid command
1. 3. 6. 1. 6. 3. 15. 1. 1. 1. 0 Unsupported security level.
1. 3. 6. 1. 6. 3. 15. 1. 1. 2. 0 Not in time packet.
1. 3. 6. 1. 6. 3. 15. 1. 1. 3. 0 Unknown user name. This varbind may also be generated:
• If the configured ACL for this user filters out this packet.
• If the group associated with the user is unknown.
1. 3. 6. 1. 6. 3. 15. 1. 1. 4. 0 Unknown engine ID. The value of this varbind would be the correct
authoritative engineID that should be used.
1. 3. 6. 1. 6. 3. 15. 1. 1. 5. 0 Wrong digest.
1. 3. 6. 1. 6. 3. 15. 1. 1. 6. 0 Decryption error.
PowerConnect# show snmp user
username = bob
ACL id = 2
group = admin
security model = v3
group ACL id = 0
authtype = md5
authkey = 3aca18d90b8d172760e2dd2e8f59b7fe
privtype = des, privkey = 1088359afb3701730173a6332d406eec
engine ID= 800007c70300e052ab0000