DIGITAL SWITCHING SYSTEMS Input/Output

NORTHERN TELECOM PRACTICE 297-1001-129
ISSUED: 93 09 29
RELEASE: 06.03 STANDARD

DIGITAL SWITCHING SYSTEMS

DMS*-100 FAMILY
INPUT/OUTPUT SYSTEM
REFERENCE MANUAL

* DMS is a trademark of Northern Telecom
Page 1
83 pages

PRACTICE 297-1001-129
RELEASE: 06.03

Page 2

PRACTICE 297-1001-129
RELEASE: 06.03
CONTENTS
PAGE
1. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . 5

General . . . . . . . . . . . . . . . . . . . . . . . . 5
Practice Application . . . . . . . . . . . . . . . . . . 5
Reason for Reissue . . . . . . . . . . . . . . . . . . . 5
Software Identification . . . . . . . . . . . . . . . . 5
Command Format Conventions . . . . . . . . . . . . . . . 5
References . . . . . . . . . . . . . . . . . . . . . . . 7

2. INPUT/OUTPUT HARDWARE . . . . . . . . . . . . . . . . . 8
Input/Output Controller . . . . . . . . . . . . . . . . 9
Device Controllers . . . . . . . . . . . . . . . . . . . 9
IO User Classes . . . . . . . . . . . . . . . . . . . . 11

3. INPUT CONTROL SOFTWARE . . . . . . . . . . . . . . . . . 15

Remote Access Security Control . . . . . . . . . . . . . 15
Security and Access Control . . . . . . . . . . . . . . 15
Command Screening . . . . . . . . . . . . . . . . . . . 19
Show-Password Feature . . . . . . . . . . . . . . . . . 22
Dumpsafe State . . . . . . . . . . . . . . . . . . . . . 22 Priority Map Terminal . . . . . . . . . . . . . . . . . 22

4. OUTPUT CONTROL SOFTWARE . . . . . . . . . . . . . . . . 23

Log System Interface . . . . . . . . . . . . . . . . . . 23
SYSLOG . . . . . . . . . . . . . . . . . . . . . . . . . 25
Critical Message Prioritization . . . . . . . . . . . . 26
Guaranteed Background Schedule . . . . . . . . . . . . . 27
Secret Logs . . . . . . . . . . . . . . . . . . . . . . 27
Report Routing . . . . . . . . . . . . . . . . . . . . . 28
Report Thresholding . . . . . . . . . . . . . . . . . . 30
Thresholding for INIT and TRAP Logs . . . . . . . . . . 33 Log Format - Offices With Enhanced Core . . . . . . . . 33

5. MAN-MACHINE INTERFACE . . . . . . . . . . . . . . . . . 34

Types of MMI . . . . . . . . . . . . . . . . . . . . . . 34
Bilingual Man-Machine Interface . . . . . . . . . . . . 34
Parameters and Responses . . . . . . . . . . . . . . . . 35
Common Commands . . . . . . . . . . . . . . . . . . . . 35
Prompting . . . . . . . . . . . . . . . . . . . . . . . 35
Security and Access Control MMI . . . . . . . . . . . . 35
Command Screening MMI . . . . . . . . . . . . . . . . . 43
Report Routing MMI . . . . . . . . . . . . . . . . . . . 55 Search and Display (Browse) MMI . . . . . . . . . . . . 70

6. ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . 83

Page 3

PRACTICE 297-1001-129
RELEASE: 06.03
FIGURES

FIG. TITLE PAGE

1 Relationship of DMS-100 Family System to I/O Devices 10
2 Remote Access Security Control. . . . . . . . . . . . . 17
3 Security and Access Control Scheme. . . . . . . . . . . 18
4 Command Screening Scheme. . . . . . . . . . . . . . . . 21
5 Schematic Representation of Typical Log Buffer. . . . . 24
6 Report Routing Scheme. . . . . . . . . . . . . . . . . 32

TABLES

TABLE TITLE PAGE

A Common Parameters . . . . . . . . . . . . . . . . . . . 80
B Text of Common Command Responses . . . . . . . . . . . 81

Page 4

PRACTICE 297-1001-129
RELEASE: 06.03
1. INTRODUCTION

GENERAL

1.01 This Practice describes the hardware and software aspects
of the DMS-100 Family Input/Output (I/O) system. This
manual also contains details of the command syntax required to
execute the various I/O functions, and the machine responses that
occur as a result of these commands.

PRACTICE APPLICATION

1.02 The information contained in this Practice is applicable
to offices having Batch Change Supplement (BCS) 32 soft-
ware.

It is also applicable to offices having a BCS release greater
than BCS32 unless reissued. The application of all Northern
Telecom Practices (NTP) editions with respect to a given BCS
release is given in 297-1001-001.

REASON FOR REISSUE

1.03 This Practice has been reissued (06.03) to incorporate
minor changes to the log system interface description.

SOFTWARE IDENTIFICATION

1.04 Software applicable to a specific DMS-100 Family office is
identified by a BCS release number and by Northern Telecom
(NT) Product Engineering Codes (PEC). The significance of the
BCS number and the PEC is described in 297-1001-450 (section 32) and in the Office Feature Record D-190.

1.05 A display of the BCS number and PEC for the NT feature
packages available in a specific office can be obtained by
entering the command string:

PATCHER;INFORM LIST;LEAVE

at a Maintenance and Administration Position (MAP).

COMMAND FORMAT CONVENTIONS
1.06 In this Practice, a uniform system of notation is used to
illustrate system commands and responses. It shows the
order in which command elements appear, the punctuation, and the
options. Where the conventions are not used, an explanation is
given in the text.

Page 5

PRACTICE 297-1001-129
RELEASE: 06.03
CAPITAL letters or show constants, commands, or keywords that
special characters the system accepts when entered as writ-
ten.

lowercase letters show a user- or system-supplied para-
meter. Definitions are given for each par-
ameter.

Brackets [ ] or enclose optional parameters. A vertical
list enclosed in brackets means that one
or more of the parameters may be selected.
Underlined parameter is a default. If no choice is entered, the
system acts as though the underlined para-
meter had been entered.

Underscore connecting means the words are to be treated as one
words item, for example, pm_type or #_one_two.

... indicates repeated steps or items.

In addition, the following conventions are used.

n (lowercase n) is a number from 0 to 9.
a (lowercase a) is a letter from A to Z.

h (lowercase h) is a hexadecimal integer from 0 to F.

1.07 Special features are implemented when the associated soft-
ware package is provisioned and installed. The following
features are available:

Feature In Package
Auto LOGIN NTX001
Bilingual Man-Machine Interface (BMMI) NTX066 Automatic Dial Back NTX293
Critical Message Prioritization NTX001
Enhanced Command Screening NTX292
Guaranteed Background Schedule NTX000
MAP support for DISPLAYPHONE * NTX001
Password and Access Control NTX292
Priority MAP Terminal NTX001
Show Password (SHOWPW) Command NTX001
Secrecy NTX100

1 * DISPLAYPHONE is a trademark of Northern Telecom.

Page 6

PRACTICE 297-1001-129
RELEASE: 06.03
REFERENCES

1.08 References listed as prerequisites are essential for an
understanding of this Practice. Those listed as inform-
ative contain detailed information concerning other items men-
tioned in this Practice, but are not essential. References are
inserted at the appropriate places in the text.

Note: The documents listed may exist in more than one version.
See 297-1001-001 to determine the release code of the version
compatible with a specific release of software.

Prerequisite References

DOCUMENT
NUMBER TITLE

297-1001-100 System Description

Informative References

NUMBER DOCUMENT TITLE

297-1001-001 Master Index of Practices
297-1001-110 Maintenance and Administration Position (MAP)
297-1001-310 Table Editor Reference Manual
297-1001-450 Provisioning
297-1001-451 Customer Data Schema
297-1001-455 The Office Parameters Reference Manual
297-1001-510 Log Report Manual
297-1001-516 Trunks Maintenance Reference Manual
GS1X55 Disk Drive Controller
GS1X67 GS1X61 Terminal Controller Card Input-Output Controller
GS1X68 Magnetic Tape Controller Card

Page 7

PRACTICE 297-1001-129
RELEASE: 06.03
2. INPUT/OUTPUT HARDWARE

2.01 Input/Output (I/O) hardware consists of various types of
controllers and I/O Devices (IOD) which enable the operat-
ing company to properly maintain, operate and administer the DMS
switch. This hardware is located in the maintenance and adminis-
tration area. (See 297-1001-100.)

2.02 The MAP (Maintenance and Administration Position) is the 2
primary device providing communication between the user
and the DMS switch. Through the MAP, the Man-Machine Interface
and display messages or reports. (See 297-1001-110 for details of (MMI) is used to input commands, run tests, request information,
the MAP.)

2.03 In addition, full MAP support is provided for the DISPLAY-
PHONE terminal (F5439). The major difference between the
standard MAP position and the DISPLAYPHONE terminal is the line
editing control function, which is implemented using the cursor
movement keys and the control key sequences as follows:

Down Arrow causes the input line to be refreshed.

Up Arrow allows character insertion at the cursor position.
Right Arrow causes the cursor to advance one character position
to the right for each depression until the end of
the current input line is reached.

Left Arrow causes the cursor to back up one character position
to the left for each depression until the beginning
of the input line is reached.

CONTROL U this key sequence causes the contents of the input
line to be deleted (see Note).
CONTROL E this key sequence causes the input line from the
current cursor position to the end of the input line
to be deleted (see Note).

CONTROL X this key sequence turns off the effect of the Up
Arrow (see Note).

? retrieves the previous input line. The DMS remem-
bers the current and the two previous lines.

Note: The key sequence, CONTROL , means that the Con-
trol key is held down while the character is entered.
2.04 Other IOD are: printers, which can be used for MMI, and to
provide printed copies of reports; and magnetic tape or
disk recording devices, used for storage or retrieval of data.

2 MAP is a trademark of Northern Telecom

Page 8

PRACTICE 297-1001-129
RELEASE: 06.03
INPUT/OUTPUT CONTROLLER

2.05 The Input/Output Controller (IOC) is the hardware entity
which provides the interface between the Central Control
Complex (CCC) and the various types of IOD. (See Figure 1 on
page 10.) The CCC side of the IOC is connected via a pair of
32-channel, 2.56 Mb/s serial data links (designated DS30), to the
Central Message Controllers (CMC), and hence to the Central Proc-
essing Units (CPU) in the CCC.

2.06 Each of the two CMC has 70 serial data ports to which the
ports are assigned to the IOC, and others to the network message DS30 data links are assigned in pairs. Some of these
controllers (NMC) in the two planes of the switching network.

2.07 Offices having BCS16 and higher software can have up to 12
pairs of ports assigned to links to up to 12 IOC (0 to
11). In this configuration, however, the number of pairs of
ports available for assignment to NMC is reduced to a maximum of
58. If less than 12 IOC are required, the number of ports avail-
able for assignment to NMC increases accordingly.

2.08 CMC port assignments to IOC and NMC are controlled by data
The format of the maintenance displays on the MAP, showing the entered in the peripheral equipment assignment tables.
status of the IOC units, depends on which BCS release number is
in effect.

2.09 The other side of the IOC provides common parallel data
and address buses, to which up to nine (numbered 0 to 8)
Device Controllers (DC) are connected. The flow of data and its
routing to the addressed DC, is handled by the I/O message con-
troller.

2.10 Physically, the I/O message controller and the DC are cir-
The IOC shelves are housed in single-bay I/O equipment (IOE) cuit cards which plug into the backplane of the IOC shelf.
frames. For more details of the IOC refer to GS1X61.

DEVICE CONTROLLERS

2.11 The DC converts the characteristics of the various IODs to
the common data bus format in the IOC. Three types of DC
circuit cards are required, and the number of each used depends
on the number of IOCs in service, and the number of IODs in use.
The provisioning of DC circuit cards forms part of the office
as follows: engineering process. The applications of the three DC types are

* Disk Drive Controller (DDC) Interfaces the Disk Drive Unit
(DDU) with the IOC data bus. Enables the DDU to be con-
trolled by commands input at the MAP. Provides read/write
facilities for retrieval and storage of data on magnetic
disks. (See GS1X55 for details of the DDU.)

Page 9

PRACTICE 297-1001-129
RELEASE: 06.03

Program< > CPU < > Data
Store Store
(PS) A (DS)
DMS-100 Family
V CCC

CMC

A A A
To mate >To NMC
CMC and
CPU < DS30 >To other IOC

V V
I/O CONTROLLER SHELF
IO Message NT1X61
Controller
NT1X62
ADDRESS BUS
DATA BUS

0 6 7 8

DEVICE
CONTROLLERS TC . . . . . TC MTC DDC
(DC)

AA A A A A
0 .. 3 0 ... 3

EIA/ASCII
Interface MODEM V
DISK DRIVE UNIT
A
V
/ MAGNETIC TAPE DRIVE
MAP <
V V
Current Loop Interface
PRT REMOTE
PRINTER < I/O DEVICEV
DATAPAC or Datalink Devices

Fig. 1 - Relationship of DMS-100 Family System to I/O Devices

Page 10

PRACTICE 297-1001-129
RELEASE: 06.03
* Magnetic Tape Controller (MTC) Interfaces the Magnetic Tape
Drive (MTD) with the IOC data bus. Enables the MTD to be
controlled by commands input at the MAP. Provides read/write
facilities for retrieval and storage of data on magnetic
tapes. (See GS1X68 for details of the MTC.)

* Terminal Controller (TC) The TC are multi-purpose circuit
cards which interface up to four IOD per card with the IOC
data bus. The four ports to which IOD are connected can have
their configurations set to match the characteristics of the
IOD connected to that port. (See GS1X67 for more details of
the TC.) Port configurations are programmable, and are set by entries in table TERMDEV to either of the following con-
figurations:

EIA/ASCII used for IOD (MAP or PRT) located within 50 ft
(15m) of the IOE frame; also to connect to a modem for
operation with remote devices.

Current Loop used for IOD located within 1200 ft (366m)
of the IOE frame.

2.12 The proper DC for each type of IOD is assigned by data
istics such as baud rate, port configuration, etc. are also entered in the appropriate IOD table. Other character-
assigned in these tables.

2.13 IO devices and their associated data tables are as fol-
lows:

* Magnetic Tape Drives - table MTD
* Disk Drive Units - table DDU
* Visual Display Unit - (part of MAP), printers (PRT), or modem
3 to a remote PRT - table TERMDEV
* DATAPAC - table DPACDEV
* Data Link Controller - DLCDEV.

IO USER CLASSES

2.14 IO users should be organized into classes which define a
specific set of functions that these users are required to
perform. These functional needs in turn dictate the IOD require-
ments for each user class. The actual organization of I/O user
classes is completely flexible to meet operating company opera-
tional requirements. The general principle is that the division
of tasks shall serve the purpose of each user class, yet will
ensure that they do not interfere with each other's functions.
2.15 The selection of the type and quantity of IOD for each
user-class function depends on operating company require-

3 DATAPAC is a trademark of Bell Canada

Page 11

PRACTICE 297-1001-129
RELEASE: 06.03
ments, and forms part of the office engineering process. Infor-
mation on the provisioning is contained in 297-1001-450.

2.16 Following are the names and descriptions for some typical
I/O user classes:

Administration (ADMIN): provides the user with unlimited
access from any IOD to all command classes (see PRIVCLAS),
and in addition is assigned the highest priority level (see
PERMIT). The password associated with ADMIN cannot be dis-
played, and cannot be changed by any other user (see COMMAND
SCREENING).
Switch Maintenance (SMtc): enables the user to maintain the
DMS switch by performing regular maintenance and fault cor-
rection for the following:

* Central Control (CC)
* Central Message Controller (CMC)
* Input/Output Devices (IOD)
* Network Modules (NM)
* Peripheral Modules (PM)

The SMtc user can also perform all necessary database mod- ification to administer the switch, monitor the switch sta-
tus, run diagnostic programs and replace equipment. The user
therefore has the capability to execute all input commands
associated with the Table Editor, and the Support Operating
System (SOS).

Trunk Maintenance (TMtc): permits the user to perform regu-
lar maintenance and fault correction for trunk circuits and
trunk facilities. The user monitors the trunk status, runs
diagnostic programs and performs hardware tests.

The TMtc user is limited to the repertoire of input commands available only to this user class. Only those commands
applicable to testing and maintaining trunks and trunk facil-
ities are permissible. This user has access to the Table
Editor repertoire of commands but is restricted in the manip-
ulation of tables. The TMtc functions are performed from a
Trunk Test Position (TTP), see 297-1001-516.

Network Management (NWM): enables the user to make optimum
use of available facilities and equipment by exercising rout-
ing controls over traffic-oriented switch resources. The
user monitors traffic levels, applies manual controls,
adjusts automatic controls and receives traffic reports.
This user class has interactive capabilities to execute only
those input commands assigned to this class. The user is
allowed data table query capabilities, but is restricted to
changes to specific data tables.

Page 12

PRACTICE 297-1001-129
RELEASE: 06.03
Dial Administration (DAdm): enables the user to monitor
traffic reports and operational measurements of the switching
unit. The user also has the ability to alter Operational
Measurements (OM) scheduling, assignments and thresholds.

This user class has interactive capabilities to execute only
those commands assigned to this class. The DAdm user has
access to the Table Editor repertoire of commands when alter-
ing data associated with OM. Full data table query capabili-
ties are also afforded the user (in particular, traffic
register assignment and readings).
Service Analysis (SA):enables the user to monitor, on a
random basis, customer dialed and operator assisted toll
calls to obtain information on the quality of service pro-
vided by the operating company equipment and personnel.

This user class has interactive capabilities to execute only
those commands assigned to this class. The SA user has
access to the Table Editor repertoire of commands but is
screened on a table basis, to control changes to only those
data tables directly associated with this class.

Technical Assistance Center (TAC): enables the user to moni-
tor unattended switching units and provide technical assist-
ance to switching center personnel as required. TAC is a
centralized operating company plant maintenance group.

This user class has interactive capabilities to execute all
the input commands that are applicable to Switch Maintenance.

Emergency Technical Assistance Service (ETAS): provides
assistance to Switch Maintenance or TAC personnel when they
cannot correct switching problems. ETAS is a service pro-
vided by Northern Telecom.
ETAS users have a user class of ALL, as they may be required
to perform various operations in order to assist TAC person-
nel.

Line Maintenance (LMtc): enables the user to monitor the
status of line cards, run diagnostics on line cards, section-
alize troubles, test and diagnose troubles within the office,
query and change subscriber data, and schedule automatic line
card diagnostics.

Repair Service Bureau (RSB): enables the user to sectional-
ize troubles,test and diagnose facility troubles, schedule
Automatic Line Insulation Testing (ALIT), receive ALIT out-
puts, and query or change subscriber data.

Traffic Administration (TA): enables the user to receive
automatic periodic summary reports of traffic statistics
accumulated by the switching system. These reports reflect
traffic peg counts, overflow, and usage of the switching

Page 13

PRACTICE 297-1001-129
RELEASE: 06.03
unit, Operational Measurements. This TA user also has the
capability to modify the schedule (and output) of these
reports.

International Switch Maintenance Center (ISMC): enables the
user to maintain the switch by performing regular maintenance
and fault correction for the majority of subsystems. The
ISMC function is similar to that of the Switch Maintenance
user class but is required for DMS-300 International offices
only.

International Transmission Maintenance Center (ITMC): ena- bles the user to perform maintenance fault correction for the
Trunks Subsystem and trunk facilities. The ITMC function is
similar to that of the Trunk Maintenance user class but is
required for DMS-300 offices only.

International Service Coordination Center (ISCC): enables
the user to monitor the quality of service provided by the
operating company personnel and equipment. The ISCC function
is similar to the Service Analysis user class but is required
for DMS-300 offices only.

Network Management Control (NWC): enables the user to make optimum use of available facilities and equipment by exercis-
ing routing controls over traffic-oriented switch resources.
The user monitors traffic levels, applies manual controls,
adjusts automatic controls and receives traffic reports. The
NWC function is similar to the NWM user class but is required
for DMS-300 offices only.

Page 14

PRACTICE 297-1001-129
RELEASE: 06.03
3. INPUT CONTROL SOFTWARE

3.01 Input control software resides in the CCC and performs the
following functions:

* security and access control by means of passwords and user
identifications

* command screening by assigning selected commands to classes
of I/O users, appropriate to their tasks

* implementation of special input control features through optional software packages

REMOTE ACCESS SECURITY CONTROL

3.02 Security methods controlling Remote Access to the I/O sys-
tem depend on whether the Automatic Dialback Feature (part
of NTX293) is present and active. Figure 2 on page 17 illus-
trates the differences.

Automatic Dialback Active
3.03 Application of the Automatic Dialback feature is con-
trolled by the MODEM_DIALBACK_CONTROL field in OFCOPT. To
be active this field is set to Y at the time of office datafill
and cannot thereafter be changed by the operating company.

3.04 Whenever a remote user logs in, the system initiates a
request for dialback ID and password, then disconnects the
modem and attempts a callback to the remote user. The elapsed
time between the modem disconnect and the completion of the
return call may vary from 40 to 120 seconds, depending upon the
length of the directory number and the type of the modem used for
the callback.

3.05 If the callback is successful the user is required to
login again, the BREAK key should not be used at this
time. From this point on, access to the I/O system is the same
as that for an onsite user, and the final login requirements
depend on whether or not the Enhanced Security Feature is active.

SECURITY AND ACCESS CONTROL

3.06 Security involves the use of passwords to ensure that only
authorized users can have access to the I/O system. The
methods of controlling the validity and assignment of passwords
depend on whether the "enhanced security package" software is
present and active, or not. Figure 2 on page 17 illustrates the
remote access control, and Figure 3 on page 18 illustrates the
onsite security and access control scheme.

Page 15

PRACTICE 297-1001-129
RELEASE: 06.03
Enhanced Security Active

3.07 Application of the enhanced security feature is controlled
by the ENHANCED_PASSWORD_CONTROL field in OFCOPT. To be
active, this field is set to TRUE at the time of office datafill,
and cannot be changed thereafter by the operating company.

3.08 The password entered at a terminal (IOD) is compared with
entries in OFCENG to ensure that it complies with: mini-
mum password length; password lifetime (not expired); expired
password grace (if expired, the grace period before password
with the PASSWORD command. renewal has not been exceeded).
Password changes must be made

3.09 The LOGINCONTROL command is part of the enhanced security
package, and is active only when the
ENHANCED_ACCESS_CONTROL field in OFCOPT is set to TRUE at the
time of office data fill. LOGINCONTROL sets the conditions under
which designated terminals are permitted to log-in. Terminals
can be enabled or disabled, manually or automatically, for speci-
fied periods or indefinitely.

3.10 When a LOGIN attempt meets all the enhanced security pack-
age criteria, access is given to the command interpreter
(CI) level. Violations of any of the security criteria, and
automatic enabling or disabling, are recorded in the security
(SECU) log subsystem. SECU logs are classified SECRET (see
SECRET LOGS), and are only displayed to users authorized to use
the OPENSECRET command.

Enhanced Security Inactive.

3.11 When the ENHANCED_PASSWORD_CONTROL field (OFCOPT) is set
to FALSE, the enhanced password control feature, with its
associated parameters in OFCENG and the PASSWORD command, is not
to FALSE, and the LOGINCONTROL command is not present. These present. Also the ENHANCED_ACCESS_CONTROL field (OFCOPT) is set
fields are set to FALSE at the time of office datafill and cannot
be changed, except by consultation with NT.

3.12 The unenhanced LOGIN scheme (see Figure 3 on page 18) is
active, and requires only LOGIN with the user name and
password to be entered at the terminal. Security consists of an
automatic check to ensure that the user name and password are
valid. If valid, access is given to the CI level.

3.13 Automatic Log-in. The AUTOLOGIN feature allows users who
are permanently associated with a terminal, or use the
terminal frequently, to log in quickly without the necessity for
entering a password. AUTOLOGIN is applied to a terminal when the
device name entered in the TERMDES field of table TERMDEV is the
same as the user name (see PERMIT). When the user name is
entered, the terminal is automatically logged-in. For security,
AUTOLOGIN is usually assigned to local terminals, not to dial-up
or remote terminals. The operating company should ensure that

Page 16

PRACTICE 297-1001-129
RELEASE: 06.03

Remote User - Dial-in
V
System - Answer tone
V
Remote User - Origination tone
- - login

V
/ \
/ \
OFCOPT \ // \
/ \
(Inactive) / MODEM_ \ (Active)
< ( DIALBACK ) >
NO \ CONTROL / YES
\ /
\ Field / AUTOMATIC < ID DIALBACK
\ / DIALBACK < DIRNUM Fields
\ / CONTROL
\_/
NTX293 < DIALBACKPW OFCOPT
V ENCRYPTED Field
V User - ID and Password
/ \ V
/ \ User - ON-HOOK
/Auto \ :
YES / Dial- \ delay - at least 30sec.
< ( back ) :
\ / System - call-back attempted
\ OK? /
\ /
\_/ AUTOMATIC LOGINCONTROL
NO V DIALBACK < Command CONTROL DIALOUT
ABORT NTX293 Parameter

> Logs SECU113 to 118

V V

(continued on Figure 3.) V

Fig. 2 - Remote Access Security Control.

Page 17

PRACTICE 297-1001-129
RELEASE: 06.03

(from Fig. 2 remote site access)
V
< LOGIN, Username, Password (on site access)
V
(Active)
MAP <--- AUTO < OFCOPT TERMDEV
or PRT LOG TRUE
OUT AUTO- IDLE-
TERMDEV Feature (Inactive) LOGOUT TIMEOUT
TERMDES < Field Field
V A FALSE
/ \
/ \
/ \
OFCOPT \ /
/ \
(Inactive)/ ENHANCED_ \ (Active)
< ( PASSWORD ) > Required for Remote
NO \ CONTROL / YES Automatic Dialback
\ /
\ Field / Required for the Partitioned
\ / \ / Table Editor feature
\_/

LOGIN < MIN PASSWORD LENGTH
>AUTOLOGIN ENHANCED
ID if USER PASSWORD < PASSWORD LIFETIME OFCENG
=TERMDES CONTROL Fields
< EXPIRED PASSWORD GRACE

No username NTX292
or password required < LOGINCONTROL Command

> Logs SECU113 to 118

V V

V
(continued on Figure 4.)

Fig. 3 - Security and Access Control Scheme.

Page 18

PRACTICE 297-1001-129
RELEASE: 06.03
none of the device names at non-local terminals match any valid
user name. If a match exists, an unauthorized AUTOLOGIN can
result.

Automatic Logout

3.14 The AUTOLOGOUT feature increases security by automatically
logging-out idle logged-on terminals, after a preset peri-
od of idleness. This reduces the likelihood of unauthorized
users misusing legally logged-in, but unattended, terminals.

3.15 AUTOLOGOUT is active when the AUTO_LOGOUT field in table OFCOPT is set to TRUE. The idle period for each terminal
device is set by entering the time (in minutes) into the IDLE-
TIMEOUT field of table TERMDEV. If zero minutes is entered
against a terminal, AUTOLOGOUT does not affect that terminal.
The minimum period, otherwise, is five minutes.

3.16 AUTOLOGOUT is inactive for all terminals, when the
AUTO_LOGOUT field is set to FALSE.

COMMAND SCREENING
3.17 The purpose of command screening is to ensure that termi-
nals are only used for their assigned tasks. For example,
a terminal assigned to service orders does not need to have
access to the commands used by a network management terminal (see
Part 2 on page 8, which describes a typical organization dividing
tasks between groups of users).

3.18 Each command is associated with one of 31 command class
number, ranging from 0 to 30, which is assigned by the
operating company management, using the PRIVCLAS command. The
command class number is then assigned to terminals and users
through the PERMIT command. The permissible command class num- bers for each terminal are entered in the COMCLASS field of table
TERMDEV, and can be displayed by the SHOW USERS command.

3.19 The effective command class of a user is the intersection
of the user's command class and that of the terminal. The
user's command class is set by the PERMIT command while the com-
mand class of the terminal is determined by the field COMCLASS in
table TERMDEV. If the effective command class is empty, the user
is not allowed to log onto that terminal since commands cannot be
performed while logged onto it anyway.

3.20 The command classes of users and terminals can be set-up so that users may login but are not allowed to logout
because their effective command class does not permit them to do
so. Such users would have to be logged out by a user such as
ADMIN who is authorized to use the FORCE logout command in order
to force their logout. To avoid situations where users can login
but not logout, provide all users, and all terminals, with the
command class of the logout command.

Page 19

PRACTICE 297-1001-129
RELEASE: 06.03
3.21 The effect is to ensure that only authorized users can use
designated classes of commands on designated terminals.
Commands which have not been assigned class numbers are unre-
stricted. Changes to command class assignments can be entered at
any time, and are effective immediately. Changes are acknowl-
edged in the response to PRIVCLAS, but are stored until a restart
occurs (warm, reload, cold) and then implemented.

3.22 The usage of command screening depends on whether the
Enhanced Security Package (NTX292) software is present,
and if the enhanced command screening feature is active. (See
Figure 4 on page 21.)
Enhanced Command Screening Active.

3.23 Application of this feature is controlled by the
ENHANCED_COMMAND_SCREENING field in table OFCOPT. When
active this field is set to TRUE at the time of office data fill
and cannot be changed thereafter by the operating company. The
effect upon the command screening scheme is as follows:

* PRIVCLAS - can assign up to 31 class numbers per command

* PERMIT - cannot change passwords, but can create new pass- words

* PASSWORD - must be used to change passwords

Enhanced Command Screening Inactive

3.24 When the ENHANCED_COMMAND_SCREENING field is set to FALSE,
the enhanced command screening feature is inactive, and
"regular" command screening is active. The purpose of command
screening is the same, but the usage is affected as follows:

* PRIVCLAS - can only assign one class number per command
* PERMIT - can change passwords as well as creating new pass-
words

* PASSWORD - not present

Admin User

3.25 The user-class ADMIN is not subject to command screening,
always has access via any terminal, and cannot be denied
the use of any commands. The password assigned to ADMIN (see
PERMIT) can only be displayed to or changed by, the ADMIN user. It is recommended that the ADMIN password be changed period-
ically, and always after a new BCS release has been loaded. The
ADMIN password should be verified, recorded, and securely stored
by representatives of at least two different management func-
tions.

Page 20

PRACTICE 297-1001-129
RELEASE: 06.03

(from Fig. 3)

V
/ \
/ \
/ \
OFCOPT \ /
/ \
(Inactive) / ENHANCED_ \ (Active)
NO \ SCREENING / YES < ( COMMAND ) >
\ Field /
\ /
\ /
\ /
\_/

PRIVCLAS
Assigns
no. per 1 class PASSWORD
command
PRIVCLAS. Assigns up
> REGULAR ENHANCED < to 31 class numbers
COMMAND COMMAND < per command.
> SCREENING SCREENING <
PERMIT NTX292 <
can create A PERMIT. Cannot change
and change passwords. Can create
passwords. new.

UNPERMIT. PASSWORD com-
UNPERMIT. mand required. Deletes
PASSWORD users names.
command not
required.
Deletes
users' V V
names.
'Browse' > LOGUTIL < Report Routing Commands
Commands Module

Output Reports To Devices

Fig. 4 - Command Screening Scheme.

Page 21

PRACTICE 297-1001-129
RELEASE: 06.03
SHOW-PASSWORD FEATURE

3.26 The "Show-Password" (SHOWPW) feature enables any user to
obtain a display of the current password associated with
that user's name via PASSWORD or PERMIT commands. SHOWPW is
available when the PASSWORD_ENCRYPTED field in table OFCOPT is
set to FALSE. If the SHOWPW feature is not provisioned, the
PASSWORD_ENCRYPTED field is set to TRUE, and the SHOWPW command
is not available. Only the ADMIN user can obtain a display of
other users' passwords. The PASSWORD_ENCRYPTED field is set at
the time of office data fill and cannot be changed thereafter by
the operating company, except by consultation with NT. SHOWPW is an independent feature, and does not depend on the presence of
any other features.

DUMPSAFE STATE

3.27 Command screening is also used to restrict the entry of
commands during office image production (DUMP) which could
overwrite and change protected data store. Commands that can be
entered are designated DUMPSAFE. Commands that cannot be entered
are designated DUMPUNSAFE.
3.28 The DUMPSAFE state for each command is set with the PRIVC-
LAS command, using the parameters DUMPSAFE or DUMPUNSAFE.
The DUMPSAFE states are defined by the operating company before
the office goes into service. A DUMPUNSAFE command is not
allowed to be executed while DUMP is in progress.

3.29 If an office has ENHANCED_COMMAND_SCREENING feature
active, the DUMPSAFE states of all commands are in table
CMDS. Otherwise, enter PRIVCLAS ALL for a display of
commands/modules (increments) and their DUMPSAFE states. (See
Part 5 on page 34.)

PRIORITY MAP TERMINAL

3.30 The priority MAP terminal feature, part of Feature Package
NTX001, enables the ADMIN class user to LOGON at any
authorized MAP using the ADMIN password, and to have improved
terminal response. This feature is used to perform diagnostic
and corrective procedures in situations where high call process-
ing occupancy of 60% or more could reduce terminal response time.

3.31 Guaranteed background scheduling, for up to six other
tasks, is described in Part 4 on page 23.

Page 22

PRACTICE 297-1001-129
RELEASE: 06.03
4. OUTPUT CONTROL SOFTWARE

4.01 Output control software operates through the log utility
module (LOGUTIL), which provides the mechanism for imple-
menting the log system commands. These commands perform the fol-
lowing functions:

* routing of reports to selected Input/Output Devices (IODs),
temporarily superseding the permanent assignments in the data
tables LOGCLASS and LOGDEV;

* interrogating and searching all reports in the various log subsystems; and

* enabling operating company personnel to add, change or delete
reports, and to apply threshold values which limit the basis
on which reports are output.

4.02 In addition to LOGUTIL, there are a number of optional
software packages through which special logging features
can be applied.

LOG SYSTEM INTERFACE
4.03 Output reports are created by individual DMS subsystem
software and are transmitted to a history file, called
LOGS. The LOG system in turn stores this report information in a
log buffer dedicated to that subsystem. In addition to being
logged, the output report may also be forwarded to an output
device. The routing of reports is controlled by the report rout-
ing subsystem. All current log reports are also listed and
described in detail in the log report manual 297-1001-840.

4.04 The log buffers can hold up to 32 000 two-byte words. The
parameter LOG_CENTRAL_BUFFER_SIZE in table OFCVAR (default value log buffer size is determined by the value of office
= 2000).

4.05 Figure 5 on page 24, is a schematic representation of a
typical log buffer. Specifically, the example shows the
log buffer which stores data from events in the CMC subsystem.

4.06 Each type of event within a log subsystem is allotted a
report number (REPNUM). Any report in the log system is
fully identifiable by the combination of LOGNAME and REPNUM
(example: CMC112), referred to as REPNAME. Reports are entered
in chronological order as they are generated.

Page 23

PRACTICE 297-1001-129
RELEASE: 06.03

Events Data to Other Log Buffers
A A A A A A A

*
*
Data *
from * OFCVAR
events *
in DMS * * * * LOG_CENTRAL_BUFFER_SIZE *
Subsystems * : :
CMC Events Data * : :

To CMC Log Buffer

OPEN Oldest
Newest Report (LAST)< Report (FIRST)

> <
V V A

Logname CMC * * * CMC CMC CMC * * * CMC

Repnum 108 * * * 102 112 101 * * * 112

Event Time 1630 * * * 1640 1647 1555 * * * 1615
: : V A : :
: : : : : :
: : >Data entry sequence : :
A V in log buffers A V

>Older Reports (BACK)

Newer Reports (FORWARD)<

Logname + Repnum = Repname.

Fig. 5 - Schematic Representation of Typical Log Buffer.

Page 24

PRACTICE 297-1001-129
RELEASE: 06.03
4.07 In the example, report CMC112 has been generated and
entered in the CMC log buffer at event time 1647 hours.
The CMC log buffer also contains older reports which occurred at
various times up to 1555 hours, which is the oldest log for which
the buffer has space. Note that the buffer also contains a pre-
vious CMC112 report which occurred at 1615 hours. By using
appropriate commands the user can select which of the two CMC112
reports is to be displayed, or can "browse" through a selected
log subsystem buffer to examine the contents of any report.

4.08 Once a subsystem buffer is full, the next report that is
the next report after 1647 hours would be entered in the buffer generated displaces the oldest report. In the example,
location containing report CMC101 (1555 hours). Report CMC101 is
overwritten and lost unless it has previously been routed to a
data storage device.

4.09 As subsequent reports are generated, the 1647 CMC112
report becomes older until eventually it becomes the old-
est report, and is replaced by the newest. Similar action occurs
in all the other log buffers.

4.10 There are several commands (referred to as "browse" com-
gate the contents and display particulars of the reports in the mands) that allow operating company personnel to interro-
log buffers. The functions of these commands include:

* selecting a particular log subsystem (OPEN) for display;

* displaying the newest or oldest report (LAST, FIRST);

* displaying the newer (BACK) or older (FORWARD) entries in a
log buffer;

* deleting the reports in a particular log buffer (CLEAR);
* displaying the log names currently defined in the LOG system
(LISTREPS); and

* selecting either the normal or an abbreviated form of a
report for display (FORMAT).

SYSLOG

4.11 The SYSLOG feature allows the operating company to desig-
nate selected log reports for recovery after an office
reload has been performed. The designated reports are written into the SYSLOG buffer as well as the LOGUTIL buffer. In the
event of a reload, the LOGUTIL buffers are overwritten, but the
designated reports remain in SYSLOG.

4.12 The log reports in SYSLOG, plus the SWERR and TRAP logs
contain information about the state of the system prior to

Page 25

PRACTICE 297-1001