PDF(291.6 KB) View with Adobe Reader on a variety of devices
ePub(318.2 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(277.1 KB) View on Kindle device or Kindle app on multiple devices
Updated:September 14, 2017
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes the new Read only CLI feature introduced in Cisco Unified Communications Manager (CUCM) version 11.5.
Contributed by Manjunath Junnur, Cisco TAC Engineer, Edited by Levi Thomas.
There are no specific requirements for this document.
The information in this document is based on these software versions:
Cisco Unified Communications Manager version 11.5
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Often Customers environment requires the ability for users with limited CLI commands access.
On this version, it was included the read only permission feature for CLI.
CUCM and IM&P Administrators can provide users accounts, Read-Only privileges access on the Command Line Interface (CLI), so existing settings information are visible but not changeable.
Note: Commands for write operations are denied for Read-Only Privilege Account users.
How it works in 11.5
At present in current CLI architecture the set account name command, creates two type of users.
1. Level 0 privilege (Read-only/Ordinary user)
2. Level 1 privilege (Privileged user)
Read-only user: Read-only users, can access only read only commands like(show, status); they cannot access set, delete commands or enable/disable settings. If any command become read-only command, in the CLI configuration xml file “priv”, value is 0 and that can be accessed by read-only users.
Privileged user: As per design, privileged users can access read only commands and write commands as well. If any command, in cli configuration file has “priv” value 1, those commands can be access by privileged users only. Privileged users can access command with priv value 0 and 1
Admin user : Admin user have access for all the commands, The level of Admin user is 4. In the cli configuration file If “priv” value is 4 admin user will access those commands. Admin user can access priv value 4,1,0 level commands as well
In order to create the Read only user account, Log in CLI and use the command.
Please enter the password :******** re-enter to confirm :********
Screesshot for the same:
Example 1 : Log in with Read only user credentials and try the DB replication stop
Example 2 : Usi sql query in order to delete a region .
Example 3 : Read only users, can use any Show command.
Example 4 : Log in the Graphical User Interface (GUI) Operating System (OS) Admin with read only User and you can observe there are no write access on any tab. If you open any certificate, it contains the details however there are no options to delete or regenerate.