Information About SNMP
CLI and SNMP User Synchronization
Any configuration changes to the user group, role, or password, results in the database synchronization
for both SNMP and AAA.
Users are synchronized as follows:
•
•
Note
•
•
•
For information about creating a CLI user by using the username command, see the Cisco 4700 Series
Application Control Engine Appliance Virtualization Configuration Guide. To create an SNMP user by
using the snmp-server user command, see the
Multiple String Index Guidelines
If any SNMP MIB table has more than one string index that contains more than 48 characters, the index
may not show up in the MIB table when you perform an SNMP walk. According to SNMP standards,
SNMP requests, responses, or traps cannot have more than 128 subidentifiers. The following list
contains object names:
•
•
•
•
•
•
•
•
•
Table 7-1
Cisco 4700 Series Application Control Engine Appliance Administration Guide
7-4
If you delete a user by using the no username command, the user is also deleted from both SNMP
and the CLI. However, if you delete a user by using the no snmp-server user command, the user is
deleted only from SNMP and not from the CLI.
User-role mapping changes are synchronized in SNMP and the CLI.
When you specify a password in a localized key or encrypted format for security encryption, the
password is not synchronized.
The password specified in the username command is synchronized as the auth and priv passwords
for the SNMP user.
Existing SNMP users can continue to retain the auth and priv information without any changes.
If you create a new user that is not present in the SNMP database by using the username command
without a password, the SNMP user is created with the noAuthNoPriv security level.
Context name
Real server name
Server farm name
Probe name
HTTP header name
ACL name
Class map name
Policy map name
Resource class name
identifies a list of tables that have more than one string index.
"Configuring SNMP Users"
Chapter 7
Configuring SNMP
section.
OL-20823-01