MENU
You are creating a new user account using a predefined login class on a Junos device. The account should be able to run operational mode commands such as show interfaces and ping, but should not be allowed to change or commit configuration. Which login class should you assign to this user?
Junos OS utilizes a Role-Based Access Control (RBAC) model through the use of login classes, which define the specific permissions and restrictions for different user levels. To simplify administration, Juniper provides several predefined classes that cater to common organizational roles. The requirement here is for an account that can perform basic network diagnostics (operational mode) but lacks the authority to modify the system state (configuration mode).
The operator class is specifically engineered for this purpose. It grants permissions such as clear, network, reset, trace, and view. These permissions allow the user to execute monitoring commands like show, use diagnostic tools like ping and traceroute, and clear statistics. Crucially, the operator class does not include the configure or commit permissions, preventing the user from entering configuration mode or making any permanent changes to the device.
Comparing this to other options: the read-only class is more restrictive, generally allowing only the viewing of configuration and some state data, but often restricting active diagnostic tools like ping. The super-user class provides unrestricted access, while maintenance is not a standard predefined class for general operational roles. Assigning the operator class ensures that junior staff or automated monitoring systems have the visibility they need to troubleshoot connectivity without risking the integrity of the device configuration.
Currently there are no comments in this discussion, be the first to comment!