This happens when commands are run from a script or run by the system, such as periodic maintenance reports.
The user identity may not be present, which means the input request was not associated with a specific user. This
happens when the login process is not enabled or when commands are run by the system, such as periodic
maintenance reports.
The following two example CMDLOG entries illustrate how CMDLOG can be used to track command usage.
CMDLOG Example 1
CMDLOG example 1 shows that
OP:STAT,ACSR,CORC
was entered from ttyr on March 10, 1993 at 6:30 p.m. The
request was denied due to insufficient authority. No user identity is available, presumably because ttyr was not
configured to run the login process.
REPT CMDLOG ttyr 93-03-10 18:30
OP:STAT,ACSR,CORC;
NG - INSUFFICIENT AUTHORITY
CMDLOG Example 2
CMDLOG example 2 shows that user identity "user1" entered command poke 196 (Office Dependent Data Recent
Change) from ttyn on March 10, 1993 at 6:35 p.m. The request was allowed (there is no acknowledgment indicating
insufficient authority).
REPT CMDLOG user1 ttyn 93-03-10 18:35
196;
3.8.4.10 Unrestricted Access
3.8.4.10.1 General
For software release retrofits or emergency situations where immediate unrestricted input is required, authority
checking can be disabled for a period of time on the MCC and SCC devices. Authority checking on devices other
than the MCC or SCC can only be disabled through normal authority administration procedures.
3.8.4.10.2 Manual Request, Activation, and Deactivation
An application parameter on the Emergency Action Interface (EAI) page requests unrestricted MCC and SCC
access. The application parameter is '+' (plus), thus poke 42!+!50 requests unrestricted access. The request results
in a
REPT:SECURITY
output message with a critical alarm to alert operations personnel of a change in the level of
security on the MCC and SCC.
Once the '+' application parameter has been entered, the first MML input message request fully activates
unrestricted access. All input messages and command pokes are executed without restrictions until unrestricted
access is deactivated.
Unrestricted access is deactivated by the first MML input message request following another 42!+!50 EAI poke or
after 60 minutes has transpired, whichever comes first.
NOTE:
An MML input request (or at least a carriage return) must be entered to fully restore command restrictions.
A
REPT:SECURITY
output messages reports that the original security level has been restored.
3.8.4.10.3 Automatic Activation and Deactivation
235-105-210
October 1999
Copyright © 1999
Page 33
Содержание 5ESS-2000
Страница 96: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Страница 184: ...235 105 210 October 1999 Copyright 1999 Page 3 ...
Страница 300: ...13 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 55 ...
Страница 339: ...7 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Страница 342: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Страница 359: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Страница 516: ...Figure 10 24 1 KS 23483 L13 Disk Drive Cable Connection Rear View 235 105 210 October 1999 Copyright 1999 Page 2 ...
Страница 517: ...Figure 10 24 2 KS 23483 L21 Disk Drive Cable Connection Rear View 235 105 210 October 1999 Copyright 1999 Page 3 ...
Страница 518: ...Figure 10 24 3 KS 23841 L15 Disk Drive Cable Connection Rear View 235 105 210 October 1999 Copyright 1999 Page 4 ...
Страница 523: ...Figure 10 24 6 Top View of DUP Showing Internal Cabling 235 105 210 October 1999 Copyright 1999 Page 9 ...
Страница 609: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 12 ...
Страница 628: ...a SM inhibited Response OK 2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 8 ...
Страница 653: ...Response OK 2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 16 ...
Страница 676: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Страница 792: ...3 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 9 ...
Страница 799: ...Figure 11 36 3 1 Cleaning Points 235 105 210 October 1999 Copyright 1999 Page 7 ...
Страница 801: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Страница 839: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 16 ...
Страница 999: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Страница 1008: ...Figure 11 55 1 CTSNS DIP Switch Settings 235 105 210 October 1999 Copyright 1999 Page 2 ...
Страница 1011: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Страница 1053: ...235 105 210 October 1999 Copyright 1999 Page 15 ...
Страница 1165: ...Procedure 14 14 RESERVED FOR FUTURE USE PROCEDURE 1 Reserved For future use 235 105 210 October 1999 Copyright 1999 Page 1 ...
Страница 1186: ...Procedure 14 17 RESERVED FOR FUTURE USE PROCEDURE 1 Reserved For future use 235 105 210 October 1999 Copyright 1999 Page 1 ...
Страница 1187: ...Procedure 14 18 RESERVED FOR FUTURE USE PROCEDURE 1 Reserved For future use 235 105 210 October 1999 Copyright 1999 Page 1 ...
Страница 1284: ...Figure 15 15 1 PARADYNE Paradyne Corporation 3810 Modem Diagnostic Control Panel 235 105 210 October 1999 Copyright 1999 Page 6 ...
Страница 1287: ...Figure 15 16 1 153A Adapter Connection Figure 15 16 2 AMATPS Block Diagram 235 105 210 October 1999 Copyright 1999 Page 3 ...
Страница 1289: ...Figure 15 17 2 AMATPS Data Link 235 105 210 October 1999 Copyright 1999 Page 2 ...
Страница 1290: ...Figure 15 17 3 Single Housing B25A Cable Assembly 235 105 210 October 1999 Copyright 1999 Page 3 ...
Страница 1292: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Страница 1294: ...Figure 15 17 8 201C to TN82 Data Set Cable Drawing 235 105 210 October 1999 Copyright 1999 Page 7 ...
Страница 1303: ...9 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 2 ...
Страница 1324: ...11 Type and enter q 12 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 2 ...
Страница 1342: ...Figure 15 40 1 SCANS II Dial Up Data Set Installation Diagram 235 105 210 October 1999 Copyright 1999 Page 2 ...
Страница 1344: ...Figure 15 40 4 59A1 Mounting Front in Slot J3 Figure 15 40 5 2048A Data Set Front 235 105 210 October 1999 Copyright 1999 Page 4 ...
Страница 1345: ...Figure 15 40 6 Berg Connector Terminations and Layout 235 105 210 October 1999 Copyright 1999 Page 5 ...
Страница 1346: ...Figure 15 40 7 B25A Cable 4 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 6 ...
Страница 1360: ...Figure 15 47 2 Typical SCANS III Link Diagram 235 105 210 October 1999 Copyright 1999 Page 2 ...
Страница 1368: ...Response FA or OK appears 17 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 2 ...
Страница 1372: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Страница 1374: ...235 105 210 October 1999 Copyright 1999 Page 4 ...
Страница 1376: ...Figure 15 55 6 201C to TN83 Data Set Cable Drawing 235 105 210 October 1999 Copyright 1999 Page 6 ...
Страница 1418: ...Figure 15 56 1 PARADYNE 3810 Modem Diagnostic Control Panel 235 105 210 October 1999 Copyright 1999 Page 4 ...
Страница 1421: ...Table 1 1 O M Checklist 235 105 210 October 1999 Copyright 1999 Page 3 ...