Functions of administrator roles and levels of the USG6000 series

The USG6000 series controls administrator permissions by administrator role and level as follows:
- Bind an administrator role: Control administrator permissions based on the menu of the web UI, which mainly applies to web administrators.
On the web UI, choose System > Administrator > Administrator, create an administrator, and specify a role for it. Administrators with different roles have different operation permissions.
- Specify an administrator level: Control administrator permissions based on the levels of administrator-executable commands, which mainly applies to CLI administrators.
The following example is provided for you to set the permission level for an administrator account.
# Set the permission of the administrator abc to level 3.
system-view
[sysname] aaa
[sysname-aaa] manager-user abc
[sysname-aaa-manager-user-abc] level 3
The administrator role has a higher priority than the administrator level, that is, if an administrator is bound to a role, the level specification no longer takes effect.
Even if an administrator account is not bound to a specific role, the administrator role and level have a default mapping as follows:
- 1: Monitoring level corresponds to the configuration administrator (monitoring).
- 2: Configuration level corresponds to the configuration administrator.
- 3: Management level to the 15th level correspond to the system administrator.
For more details, see the administrator chapter in the product documentation of the USG6000 series.

Scroll to top