TP-Link T1600G-18TS T1600G-18TSUN V2 CLI Reference Guide Guide - Page 430
snmp-server user
View all TP-Link T1600G-18TS manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 430 highlights
49.4 snmp-server user Description The snmp-server user command is used to add User. To delete the corresponding User, please use no snmp-server user command. The User in an SNMP Group can manage the switch via the management station software. The User and its Group have the same security level and access right. Syntax snmp-server user name { local | remote } group-name [ smode v3 ] [ slev noAuthNoPriv ] [ cmode none ] [ cpwd confirm-pwd ] [ emode none ] [ epwd encrypt-pwd ] snmp-server user name { local | remote } group-name [ smode v3 ] slev authNoPriv cmode { MD5 | SHA } cpwd confirm-pwd [ emode none] [ epwd encrypt-pwd ] snmp-server user name { local | remote } group-name [ smode v3 ] slev authPriv cmode { MD5 | SHA } cpwd confirm-pwd emode DES epwd encrypt-pwd no snmp-server user name Parameter name -- User Name, ranging from 1 to 16 characters. local | remote -- User Type, with local and remote options. Local indicates that the user is connected to a local SNMP engine, while remote means that the user is connected to a remote SNMP engine. As the remote engine ID and user password are used to compute the authentication and privacy digests, before configuring a remote user, you need to set the remote engine ID first. group-name -- The Group Name of the User. The User is classified to the corresponding Group according to its Group Name, Security Model and Security Level. v3 --The security mode for the user. v3 indicates SNMPv3, the most secure model. slev -- The Security Level of SNMP v3 User. There are three options, including noAuthNoPriv (No authentication algorithm but a user name match is applied to check packets, and no privacy algorithm is applied to encrypt them), authNoPriv (An authentication algorithm is applied to check packets, but no privacy algorithm is applied to encrypt them) and authPriv (An authentication algorithm and a privacy algorithm are applied to check and 409