Lucent Technologies Stinger, Administration Manual

Page: 40 / 374

1-18 Stinger® Administration Guide
Administering a Stinger System
Managing administrative access to the unit
atmnbase ( debug )
[More? <ret>=next entry, <sp>=next page, <^C>=abort]
Typically, read-write accounts enable the System command class. They might also
enable the Update and Code command classes. Read-only accounts might be limited
to the Diagnostic command class. Table 1-1 shows command class and the associated
permission.
Typical permission configurations
The following commands create a read-write administrative login named Marco ,
which is based on the admin user profile, but has access only to System, Diagnostic,
and Update command classes:
admin> new user admin
USER/admin read
admin> set name = marco
admin> set password = my-password
admin> set allow-password = yes
admin> set allow-code = no
admin> write
USER/marco written
The following commands create a user profile named test based on the user profile
admin , but restricts some permissions and assigns a different password:
Table 1-1. Permissions and associated commands
Permission Command class
N/A
(always enabled) User
Allow-System System
Allow-Update Update
Allow-Code Code
Allow-
Diagnostic Diagnostic
Allow-Termserv Termserv ( Does not apply to the Stinger unit.)
Allow-Password N/A. The Allow-Password permission enables a user to view
passwords. If the permission is set to
no , the user sees a row
of asterisks instead of the actual configured password. If the
administrator who backs up system configurations does not
have the
allow-password permission set to yes , passwords
are not saved as part of the configuration.