The ELS exerciser uses TTF or GDSF circuits (a shared resource among SMs/SM-2000s) to perform its tests. If
ELS exercises are running concurrently in more SMs/SM-2000s than there are TTF or GDSF circuits, exercisers in
some of the SMs/SM-2000s may terminate due to the unavailability of a TTF or GDSF. The user should consult
Section 12.8
"REX Scheduling Recommendations" for scheduling procedures to eliminate this problem.
12.9.2
UNIX
®
RTR/CM REX System
Apart from 5ESS-2000 switch routine exercise,
UNIX
®
RTR REX system has its own routine exercise. Its functions
and actions are totally independent of 5ESS-2000 switch routine exercise. The units that the UNIX RTR system
exercises include, Control Units (CU), Disk File Controllers (DFC), Moving Head Disks (MHD), and Input/Output
Processors (IOP).
The MSGS, which is the responsibility of 5ESS-2000 switch REX, is permanently inhibited for UNIX RTR REX
system in the equipment configuration data (ECD).
It is important for the user of both UNIX RTR REX system and 5ESS-2000 switch REX to realize that input
commands to both are similar in syntax. One should refer to the procedures in this section for correct 5ESS-2000
switch REX command syntax.
As mentioned in previous sections, CM REX should not be scheduled to run at the same time as UNIX RTR REX
system. This is due mainly to the fact that when a soft switch of the CUs is performed, all active CM diagnostics will
be aborted by the switch maintenance kernel process (SMKP). This may leave units like the ONTC and the MSGS
in a simplex configuration.
12.9.3 SM/SM-2000 DGN/FAB EXERCISE
Fabric exercise holds a high-level service circuit (HLSC) for about 5 to 7 minutes per grid or grid board. If fabric
exercises are running in line unit 0 (LU0) and diagnostics start on LU0, diagnostics will not be able to run on that
HLSC. Hence, diagnostics will skip the GDXACC circuit in both service groups of LU0.
Similarly, if REX is running line unit channel circuit diagnostics and FAB exercise needs the associated B-link, then
fabric tests will result in a conditional all tests pass (CATP).
The user should consult Section 12.8 entitled ``REX SCHEDULING RECOMMENDATIONS'' for scheduling
procedures to eliminate these problems. Section 12.10 describes a newly developed program, called the
``Operations Support System (OSS) REX SCHEDULER PROGRAM'', which is useful for avoiding conflicts in any
central office, especially those having a large number of switching modules.
12.10 OSS REX SCHEDULER PROGRAM
12.10.1 GENERAL
The OSS REX scheduler is a non-switch resident, support-system based program developed to ease the process of
customizing REX schedule offices. See Section 12.11 , Automatic REX Scheduler).
The process is divided into four major phases:
(1)
Data Collection:
The user is prompted for pertinent central office equipage data that is needed to create a
REX schedule.
(2)
Data Processing:
The program uses formulas and algorithms designed to reduce resource contention and
generates a REX schedule tailored to the configuration of each central office.
(3)
Recent Change Script Generation:
The program creates a recent change APPTEXT file that can be
executed from the switching control center (SCC) using the
SEND:OFC
command. This SCC command
235-105-210
October 1999
Copyright © 1999
Page 11
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 ...