
Interface (EAI) commands. The SCC and MCC terminals support terminal-level authority checking only. Authority
checking is not supported on
UNIX
®
terminals.
3.8.3 AUTHORITY CHECKING CONCEPTS
3.8.3.1 Command Groups
3.8.3.1.1 General
A command group is a set of input messages and command pokes grouped together because they share a
common function, operate on a common unit, or have some other common characteristics. Each input message
and poke is a member of exactly one command group. Command groups are assigned to users and devices to
define the set of permissible commands. Example command groups include NMOC (Network Management and
Overload Control), SM (Switching Module Maintenance), and ALARM (Alarm Manipulation).
A complete table of command group names and explanations is located in the Introduction section of 235-600-700,
5ESS
®
-2000 Switch Input Messages Manual
.
The Command Group Index, an alphabetically-ordered list of input message identifiers and their command groups,
is located in the Indexes section of 235-600-700,
5ESS
®
-2000 Switch Input Messages Manual
.
The Command Group Appendix, which maps commands groups to input message identifiers, is located in the
Appendixes section of 235-600-700,
5ESS
®
-2000 Switch Input Messages Manual
.
In addition, each input message in the 235-600-700,
5ESS
®
-2000 Switch Input Messages Manual
specifies its own
command group or groups.
3.8.3.1.2 Special Command Groups
Two special command groups, NOCHK and SUPERUSR, are defined to bypass authority checking for two different
purposes.
NOCHK Command Group:
The NOCHK command group contains input messages that are never authority
checked. For example,
OP:CLK
, a popular input message that presents no danger to the system, is in the NOCHK
command group.
All users and terminals are implicitly permitted to execute NOCHK commands. Thus, the system administrator can
not assign the NOCHK command group to users or terminals. CMDLOG logfile entries are never created for
NOCHK commands. Furthermore, CMDLOG logging and reporting is not configurable for the NOCHK command
group.
SUPERUSR Command Group:
The SUPERUSR command group does not actually contain any input messages
or pokes. It is a keyword that, when assigned to a user, instructs the system to by-pass terminal restrictions.
Judicious use of SUPERUSR is advised for security reasons.
3.8.3.1.3 Command Profiles
To simplify assignment of command groups to users and terminals, the administrator may define one or more
command
profiles
, which are simply lists of command groups. Command profiles are assigned to users or terminals
similar to the way command groups are assigned.
3.8.3.2 Levels of Authority Checking
3.8.3.2.1 General
235-105-210
October 1999
Copyright © 1999
Page 22
Summary of Contents for 5ESS-2000
Page 96: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 184: ...235 105 210 October 1999 Copyright 1999 Page 3 ...
Page 300: ...13 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 55 ...
Page 339: ...7 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 342: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 359: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 609: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 12 ...
Page 676: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 792: ...3 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 799: ...Figure 11 36 3 1 Cleaning Points 235 105 210 October 1999 Copyright 1999 Page 7 ...
Page 801: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 839: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 16 ...
Page 999: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 1008: ...Figure 11 55 1 CTSNS DIP Switch Settings 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1011: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1053: ...235 105 210 October 1999 Copyright 1999 Page 15 ...
Page 1289: ...Figure 15 17 2 AMATPS Data Link 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1292: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1303: ...9 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1360: ...Figure 15 47 2 Typical SCANS III Link Diagram 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1372: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1374: ...235 105 210 October 1999 Copyright 1999 Page 4 ...
Page 1421: ...Table 1 1 O M Checklist 235 105 210 October 1999 Copyright 1999 Page 3 ...