Lucent Technologies 5ESS-2000 Installation guide

5ESS®-2000 Switch
ROUTINE OPERATIONS AND MAINTENANCE PROCEDURES
5E11(1) and Later Software Releases
Document: 235-105-210
Issue Date: October 1999
Issue Number: 15.00A
235-105-210 October 1999
Copyright © 1999 Page 1

Legal Notice
Copyright ©1999 Lucent Technologies, Inc. All Rights Reserved.
This electronic information product (IP) is protected by the copyright and trade secret laws of the United States and
other countries. The complete document may not be reproduced, distributed, or altered in any fashion. Selected
sections may be copied or printed with the utilities provided by the viewer software as set forth in the contract
between the copyright owner and the licensee to facilitate use by the licensee, but further distribution of the data is
prohibited.
For permission to reproduce or distribute, call:
1-888-LTINFO6 (1-888-584-6366) (From inside the continental United States)
1-317-322-6848 (From outside the continental United States).
Notice
Every effort was made to ensure that the information in this IP was complete and accurate at the time of publication.
However, information is subject to change.
This IP describes certain hardware, software, features, and capabilities of Lucent Technologies products. This IP is
for information purposes; therefore, caution is advised that this IP may differ from any configuration currently
installed.
Lucent Technologies is the successor to the business and assets of AT&T Network Systems business unit.
Mandatory Customer Information
Interference Information: Part 15 of FCC Rules - Refer to the 5ESS®-2000 Switch Product Specification IP.
Trademarks
5ESS-2000, AUTOPLEX, and SLC are registered trademarks of Lucent Technologies.
All other trademarks are identified as they appear in the text.
Warranty
Warranty information applicable to the 5ESS®-2000 switch may be obtained from the Lucent Technologies Account
Management organization. Customer-modified hardware and/or software is not covered by this warranty.
Ordering Information
This IP is distributed by the Lucent Technologies Customer Information Center in Indianapolis, Indiana.
The order number for this IP is 235-105-210. To order, call:
1-888-LUCENT8 (1-888-582-3688) or fax to 1-800-566-9568 (From inside the continental United States)
1-317-322-6848 or fax to 1-317-322-6699 (From outside the continental United States).
Support Telephone Numbers
Information Product Support Telephone Number: To report errors or ask nontechnical questions about this or
other IPs produced by Lucent Technologies, call 1-888-LTINFO6 (1-888-584-6366).
235-105-210 October 1999
Copyright © 1999 Page 1

Technical Support Telephone Numbers: For initial technical assistance, call the North American Regional
Technical Assistance Center (NARTAC) at 1-800-225-RTAC (1-800-225-7822). For further assistance, call the
Customer Technical Assistance Management (CTAM) Center:
1-800-225-4672 (From inside the continental United States)
1-630-224-4672 (From outside the continental United States).
The CTAM center is staffed 24 hours a day, 7 days a week.
Acknowledgment
Developed by Lucent Technologies Customer Training and Information Products.
235-105-210 October 1999
Copyright © 1999 Page 2

1. INTRODUCTION
1.1 DOCUMENT COVERAGE
This Routine Operations and Maintenance Procedures Manual contains both descriptive material and detailed
procedures for routine operations and maintenance of the 5ESS®-2000 switch. This manual covers the 5E11
through 5E14 software releases. As the 5ESS®-2000 switch continues to evolve, this manual will be reissued to
cover future software releases.
This manual is primarily intended for telephone company personnel who schedule or perform routine maintenance
for the 5ESS®-2000 switch.
NOTE: Lucent Technologies has discontinued the availability of software releases 5E10 and earlier. Information
specific to these earlier releases have been deleted from this document.
1.2 UPDATE INFORMATION
Issue 15
Issue 15 is a reissue supporting 5E11 through 5E14 software releases. Many changes in this reissue is from
customer comment cards, hot line calls, and development changes. The Update Instructions identify all the changes
made and instructions for page replacements.
1.3 SOFTWARE RELEASE UPDATE INFORMATION
In accordance with the 5ESS®-2000 Switch Software Support Plan, the 5E11 software release is rated
Discontinued Availability (DA) as of November 13, 1999. The information supporting 5E11 and earlier is being
removed over time, instead of concurrently, from all documentation.
If you are supporting offices using a software release prior to 5E12 and have a need for the information that is
being removed, it is recommended that you retain the associated pages as they are removed from the paper
documents or the earlier copy of CDROM.
1.4 NAME CHANGE
As of March 18, 1999, Bellcore officially changed its name to Telcordia Technologies. Not all pages of this
document are being reissued to reflect this change; instead, the pages will be reissued over time, as technical and
other changes are required. Customers on standing order for this document may see that, on previous-issue pages,
the Bellcore name is still exclusively used.
Customers receiving new orders for this document will see the Telcordia Technologies name used as appropriate
throughout the document, and the Bellcore name used only to identify items that were produced under the Bellcore
name. Exceptions may exist in software-influenced elements such as input/output messages, master control center
screens, and recent change/verify screens. These elements will not be changed in this document until such time as
they are changed in the software code. Document updates will not be made specifically to remove historical
references to Bellcore.
1.5 MANUAL ORGANIZATION
This manual contains the following sections:
SECTION 1INTRODUCTION: This section contains an introduction and general information about the
manual.
235-105-210 October 1999
Copyright © 1999 Page 1

SECTION 2E UIPMENT TEST LIST: This section lists preventive (routine) maintenance schedules for the
5ESS®-2000 switch. Preventive maintenance is performed on a specified schedule to ensure continuing peak
overall performance of the network.
SECTION 3SYSTEM CONTROL OPERATIONS DESCRIPTION: Describes system control functions, for
example, off-line boot verification, Automatic Trunk Test Scheduler, Authority Management, and Call
Monitoring.
SECTION 4SYSTEM CONTROL OPERATIONS PROCEDURES: This section contains detailed level
procedures for performing the system control functions.
SECTION 5MEMORY ALTERATION DESCRIPTION: This section contains a description of the changes
possible within the 5ESS®-2000 switch data base. Covered within this section are software release update,
office backup methods, office dependent data (ODD) backup, ODD recovery, editing the data base using the
office data base editor (ODBE), software release retrofit, and software-update procedure automation.
SECTION 6MEMORY ALTERATION PROCEDURES: This section contains detailed level procedures for
the subjects described in Section 5 of this manual and supports off-line boot verification.
SECTION 7REMOTE OFFICE TEST LINE: This section describes the functions and equipment of the
remote office test line (ROTL) for the 5ESS®-2000 switch.
SECTION 8FAN AND ALARM TESTS: This section contains detailed level procedures for fan and alarm
tests. This section also contains procedures to change fan unit air filters.
SECTION 9MOVING HEAD DISK PROCEDURE DESCRIPTION: This section contains descriptions for
converting, connecting, or replacing moving head disks (MHD).
SECTION 10MOVING HEAD DISK PROCEDURES: This section contains detailed level procedures for the
subjects described in Section 9 of this manual.
NOTE: Refer to 235-105-220 for Call Trace Procedures. These procedures are not covered in 235-105-210 .
SECTION 11MISCELLANEOUS ROUTINE PROCEDURES: This section contains procedures to record
announcements using the 13A recorded announcement unit, conversion of a RISLU to an ERISLU, and to
update numerous IDCU procedures.
SECTION 12ROUTINE EXERCISE DESCRIPTION: This section provides a description of the 5ESS®-2000
switch routine exercise (REX), including the administration module (AM).
SECTION 13ROUTINE EXERCISE PROCEDURES: This section contains detailed level procedures for the
subjects described in Section 12 of this manual.
SECTION 14FEATURE ACTIVATION PROCEDURES: The section contains the procedures that activate or
turn-on various exchange features. This could be a complete growth of a feature or just the changing or
updating of one or more attributes for a specific feature. This section also covers the removal from service or
de-activation (de-growth) of a feature.
SECTION 15OPERATIONS SUPPORT SYSTEMS ACTIVATION: This section contains detailed level
procedures to bring up the 5ESS®-2000 switch operations support systems (OSS).
GLOSSARY: This section provides brief definitions of acronyms and abbreviations used in this manual.
INDEX: Lists the subjects covered in this manual.
APPENDIX: Contains the operations and maintenance checklist.
235-105-210 October 1999
Copyright © 1999 Page 2

1.6 USER FEEDBACK
The producers of this manual are constantly striving to improve quality and usability. Please use the enclosed user
feedback form for your comments and to advise us of any errors. If the form is missing or your comments will not
fit, you can write to the following address:
Lucent Technologies
Documentation Services
2400 Reynolda Road
Winston-Salem, NC 27106
Please include the issue number and/or date of the manual, your complete mailing address, and telephone number.
We will attempt to answer all correspondence within 30 days, informing you of the disposition of your comments.
You may also call our Documentation HOTLINE if you need an immediate answer to a documentation question.
This HOTLINE is not intended to eliminate the use of the user feedback form, but rather to enhance the comment
process. The HOTLINE number is 1-800-645-6759, and is available from 7:30 a.m. to 6:00 p.m. Eastern time.
Outside of those hours, the line is served by an answering machine. You can leave a message on the answering
machine and someone will return your call the following business day.
Document users who have access to electronic mail facilities may send comments via electronic mail. The
electronic address is [e-mail]. When sending comments via electronic mail, please make
sure that the document title, document number, document issue number, and/or document date are included in the
mail along with the sender's name, phone number, and address.
1.7 DISTRIBUTION
This manual is distributed by the Lucent Technologies Customer Information Center (CIC) in Indianapolis, Indiana.
Most operating telephone companies should place orders through their documentation coordinator. Some
companies may allow customers to order directly from the Customer Information Center; however, the majority do
not. Companies that use documentation coordinators to manage their orders receive a significant discount. If you
do not know the name/number of the documentation coordinator for your company, you may call 1-888-LUCENT-8
(1-888-582-3688) to obtain the name and telephone number.
Customers not represented by a documentation coordinator and Lucent Technologies employees can order the
documentation for the 5ESS-2000 switch directly from the Lucent Technologies Customer Information Center.
Proper billing information must be provided. These orders may be mailed to the following address:
Customer Information Center
Customer Service
2855 N. Franklin Road
Indianapolis, IN 46219
Orders may also be called in on 1-888-LUCENT-8 (1-888-582-3688) or faxed in on 1-800-566-9568.
1.8 TECHNICAL ASSISTANCE
Technical assistance for the 5ESS-2000 switch can be obtained by calling the North American Regional Technical
Assistance Center (NARTAC) at 1-800-225-RTAC (1-800-225-7822) . This telephone number is monitored 24
hours a day, 7 days a week. During regular business hours, your call will be answered by your local RTAC. Outside
of normal business hours, all calls will be answered at a centralized technical assistance center where
service-affecting problems will be dispatched immediately to your local RTAC. All other problems will be referred to
your local RTAC on the next regular business day.
235-105-210 October 1999
Copyright © 1999 Page 3

1.9 MAINTENANCE OF VENDOR EQUIPMENT
The 235-xxx-xxx manuals do not provide maintenance procedures for the repair of equipment manufactured by
vendors other than Lucent Technologies (for example, tape drives, disk drives, etc.). To identify the appropriate
maintenance document for other vendor equipment, refer to 235-001-001 , Documentation Description and Ordering
Guide.
1.10 REFERENCES
The Compact Digital Exchange (CDX) and the Very Compact Digital Exchange (VCDX) are switching systems
based on the 5ESS-2000 switch. This document is a standard 5ESS-2000 switch document that is also applicable
to the CDX and VCDX switching systems. Information applicable only to CDX or VCDX may be found in the
following manuals:
235-120-010, Compact Digital Exchange (CDX) Reference Guide
235-120-020, Compact Digital Exchange (CDX) User's Guide
235-120-110, ery Compact Digital Exchange ( CDX) Reference Guide
235-120-120, ery Compact Digital Exchange ( CDX) User's Guide.
When appropriate, this document contains references to the applicable CDX or VCDX documents.
Documents for the SEAGATE TECHNOLOGYTM CDC 340-megabyte (MB) SMD Disk drives may be obtained
from:
Seagate Technology
P.O. Box 12313
Room OK A-100
Oklahoma City, OK 73157
TEL: [phone]
Document numbers and titles for the Seagate Technology CDC 340-MB SMD disk drives are shown as follows:
83325050 Hardware Maintenance Manual, Volume 1
83325060 Hardware Maintenance Manual, Volume 2
83325070 Hardware Maintenance Manual, Volume 3
83322440 Microcircuits Manual, Volume 1
83324440 Microcircuits Manual, Volume 2.
Documents for the Hewlett-Packard Model 88781A 9-track SCSI tape drive (KS-23909, L21) can be ordered from
Hewlett-Packard
TEL: [phone]
and are as follows:
88781-90001 88781 Technical Data Sheet
88781-90030 88781 Service Manual
235-105-210 October 1999
Copyright © 1999 Page 4

5960-7618 88781 User's Guide
HP88781A Product Specifications
Documents for the StorageTek Model 9914V 9-track SCSI tape drive (KS-23909, L10) can be ordered from
StorageTek
2270 S. 88th Street
Louisville, CO 80028
TEL: [phone]
and are as follows:
95 121798 30 9914 SCSI Manual
95 125455 10 9914V User/Diagnostic Manual
95 125456 10 9914V Streamer Servicing Manual
95 124765 10 9914V User/Diagnostic Manual
MG8015A 9914V Product Specification Manual
Documents for the Laser Magnetic Storage International Company PERTEC®interface 9-track tape units
(KEYSTONE®II, KS-22762, and KEYSTONE®III, KS-23113) can be ordered from
Valley Forge Peripherals, Inc.
422 Business Center
Building 0-1530
Oaks, PA 19456-0908
TEL: [phone]
and are as follows:
49762900 Reference Manual - Model 92185
49763000 Vertical Mount Maintenance Manual - Model 92185
49768900 Reference Manual - Model 92181
49769000 Maintenance Manual - Model 92181
235-105-210 October 1999
Copyright © 1999 Page 5

2. EQUIPMENT TEST LIST
2.1 INTRODUCTION
CAUTION: Do not run demand phase on a routine basis. Demand phase is to be run only when required. Demand
phase is not covered in this document. If demand is required, refer to 235-105-220 , 5ESS®-2000
Switch Corrective Maintenance Manual.
This section lists preventive (routine) maintenance schedules for the 5ESS®-2000 switch. Preventive maintenance
is performed on a specified schedule to ensure continuing peak overall performance of the network.
Since peak load periods, features, recent change activities, growth, etc., vary widely in different offices, some tests,
such as routine exercise (REX), may not have specific test schedules that are best for all offices. In cases of this
type, the equipment test list (ETL) gives references where procedures, recommendations, and/or guidelines can be
found for the listed test(s).
2.2 ROUTINE MAINTENANCE SCHEDULES
The routine maintenance schedules are listed in Table 2-1 .
The following documents may also have routine maintenance task requirements:
235-410-350 ,INDAP Operation and Maintenance Guide
250-520-105, Toll and Assistance ideo Display Terminal Description and Operation
250-600-501, OSPS Automated Position Administration, Reporting, Recent Change, and Software
Maintenance for CSG
250-600-502J1, OSPS Automated Position, Equipment Maintenance Job Aid.
250-600-504, OSPS Automated Position, RCP Application for CSG
250-600-505, OSPS Automated Position, SDAP Application for CSG
250-600-506, OSPS Automated Position, Base and Utilities Applications for CSG.
Table 2-1 Equipment Test List Preventive Maintenance Schedule
TASK TITLE TASK LOCATION FREQUENCY
1 Air Filter, Fan Assembly Unit Type - Replace Section 8
Procedure 8.15
6 Months
(Maximum)
2 Air Filter, Fan Unit in General Drawer - Type Units Replace Section 8 Procedure
8.18
6 Months (Maximum)
3 Air Filter, 340-Mb MHD - Replace Section 8 Procedure
8.17
6 Months (Maximum)
4 Backup - (See "Disk Backup" or ``Tape Backup'' in this table,
as appropriate.)
Section 6 a
5 Charge Circuit in PDF, Perform Periodic Test Section 4 Procedure
4.7.2
1 Month
6 Disk Backup, Full Office - Make [An office should keep two
different versions of office backup disks (one of each copy),
with the oldest copy being discarded when a new copy is
made].
Section 6
Procedure 6.21
a
After performing Procedure 6.21 , Verify Software Backup Procedure 6.26
235-105-210 October 1999
Copyright © 1999 Page 1

Disk.
7Equipment OS List - Analyze and Clear (See OP:OOS input
message in 235-600-700).
24 Hours
8 Fan Units, Communication Module/Time Multiplexed Switch, -
Test
Section 8
Procedure 8.14
6 Months
9 Fan Units, Switching Module - Test Section 8
Procedure 8.13
6 Months
10 Fan Units, ISLU - Test Section 8
Procedure 8.24
6 Months
11 Full Office Backup - Make (See ``Disk Backup'' or ``Tape
Backup'' in this table, as appropriate.)
Section 6 a
12 Hourly Plant Report - Evaluate Section 3 a
13 Memory Administration, Routine - Perform Sections 5 and 6 a
14 Miscellaneous Alarm, Major - Test Section 8
Procedure 8.5
12 Months
15 Miscellaneous Alarm, Minor - Test Section 8
Procedure 8.6
12 Months
16 Moving Head Disk Integrity - Verify Section 10
Procedure 10.13
1 Week
17 Office Alarm, Critical - Test Section 8
Procedure 8.2
12 Months
18 Office Alarm, Major - Test Section 8
Procedure 8.3
12 Months
19 Office Alarm, Minor - Test Section 8
Procedure 8.4
12 Months
20 Primary Disk Partitions to Backup Disk Partitions - Copy Section 6
Procedure 6.17
1 Week
21 Routine Exercise (REX) - Description
Routine Exercise (REX) - Schedule
REX Tests - Summary
REX DGN,FAB - Evaluation
REX ELS - Evaluation
Section 12
Procedure 13.1
Procedure 13.4
Procedure 13.5
Procedure 13.6
a
22 This Task Is Un-Assigned
23 Software Updates - Activate Section 6
Procedure 6.4
a
24 Software Updates - Schedule Section 6
Procedure 6.3
a
25 Tape Backup, Full Office - (Tape backup of the entire office
should be done at least once a month or more often if many
software updates and/or ECD changes are being added to the
office. Keep the three latest versions of entire office backup
tapes, with the oldest copy being discarded when a new copy
is made).
Section 6
Procedure 6.23
a
After performing Procedure 6.23 , Verify Backup Text Tapes
(Ignore if verify is automatically done).
Procedure 6.27
26 Tape Operating Procedure (TOP) Tape - Make (An office
should have three TOP tapes available with the oldest one
being replaced every 3 to 4 months; see ``Tape Backup, Full
Office'', Procedure 6.23 ).
Section 6 3-4 Months
27 24-Hour Report - Review and Log Section 3 24 Hours
28 Clean KS-23114 Tape Drive Section 11
Procedure 11.37
Every 8 Hours or
Monthly
29 Air Filter, SCSI Cabinet - Replace Section 8
Procedure 8.16
6 Months
(Maximum)
30 SCSI DAT Drive - Clean Section 11
Procedure 11.36
25 Hours of
Operation or Monthly
31 KS-23909, L10 Tape Drive - Clean Section 11
Procedure 11.36
8 Hours of Operation
or Monthly
32 KS-23909, L21 Tape Drive - Clean Section 11
Procedure 11.36
8 Hours of Operation
or Monthly
235-105-210 October 1999
Copyright © 1999 Page 2

Notes:
a. Since peak load periods, features, recent change activities, growth, etc., vary widely in different offices, some tests may
not have specific test schedules that are best for all offices. In cases of this type, the equipment test list gives
references where procedures, recommendations, and/or guidelines can be found for the listed test(s).
235-105-210 October 1999
Copyright © 1999 Page 3

3. SYSTEM CONTROL OPERATIONS DESCRIPTION
3.1 INTRODUCTION
This section contains descriptive material for system control operations associated with the 5ESS®-2000 switch.
Some operations or system control functions can be performed by means of stand-alone input messages. In such
cases, only a brief explanation of the function or the way to use the input message will be given.
Section 4 contains detailed level procedures for performing the system control operations.
The system control functions described in this section are as follows:
Date and Time: Describes when and how the date and time can be set as well as the input messages to
change the date and/or time.
Alarm System Management: Describes the input messages necessary to perform alarm release and to assign
alarm levels and labels, and the allowing or inhibiting of alarm reports.
Command and Test Scheduling: Describes the four processes (automatic line insulation tests, automatic
progression testing, office dependent data backup, and routine exerciser) that can be scheduled automatically
by means of input messages. How to schedule these processes and how to change already scheduled ones
are discussed.
File and File System Management: Gives a brief explanation of all the possible input/output messages and
some examples of how to use these messages. Since there are a variety of input messages to manage files
and the file system, it is impossible to show standard procedures.
Log File Handling: Detects and corrects transient errors or determines a chronological order of events. How
these log files are built up and what types of log files are present in the system are described.
Network Management: Avoids degrading of the network because of too many call attempts. One of the
management capabilities is the automatic or manual trunk group controls. What these controls are used for and
how it is possible to manipulate these controls by means of input messages are described.
3.2 DATE AND TIME
3.2.1 SET DATE AND TIME AFTER INITIALIZATION
After system initialization, the time and date have to be set. This can be done by using the SET:CLK input message.
This message sets the system clock to the specified date and time or adjusts the system clock by plus or minus the
seconds specified.
3.2.2 CHANGING DATE AND TIME
Changing the date and/or time can be done together or independently from one another. In a normal operating
exchange, the date will not have to be changed. However, when a system clock failure occurs, the date might have
to be changed after recovery. This can be done by means of the input message previously mentioned.
Changing the time can be necessary after a system clock failure or when the time has to be changed to/from
daylight saving time.
When changing date and time in an operating exchange, first check whether there are scheduled tests or ODD
backups present. This can be done by entering the OP:BKUPSTAT input message. If there are some tests
scheduled or ODD backups at the time the clock will be changed, it may be necessary to reschedule those tests.
235-105-210 October 1999
Copyright © 1999 Page 1

For example: if an ODD backup is scheduled and date and time has to be changed until a time past the scheduling,
this ODD backup will be bypassed. In such a case, the backup might be rescheduled.
It is also possible to check whether scheduled routine exercises have been bypassed. This can be done by entering
the OP:ST=REX input message.
3.3 ALARM SYSTEM MANAGEMENT
3.3.1 GENERAL
The alarm system management is used to set the alarm retire mode, to provide alarm control, and to assign the
level, label, and repeatability of scan points.
3.3.2 ALARM RETIRE
The critical and major audible alarms in an exchange can be retired manually or automatically. When the alarm
retire mode is manual, the alarms have to be retired by pressing the ALM RLS function key at the master control
center (MCC) video terminal, or by entering the CLR:ALARMS input message. If the alarm retire mode is set to
automatic, the alarms will be retired in 8 seconds by the system. Minor alarms will be retired automatically all the
time, independent of the alarm retire mode.
Automatic or manual alarm retire mode can be activated by means of the menu commands 800 and 801 at the
MCC Page 105/106BLDG/POWER & ALARM CNTRLS.
3.3.3 ALARM ASSIGNMENTS
Alarm level, label, and repeatability assignments can be given to building or miscellaneous alarms. The assignments
are shown at the MCC Pages 105/106BLDG/POWER & ALARM CNTRLS and 119MISCELLANEOUS
ALARMS.
The alarm level can be critical, major, minor, or informational. The label can consist of a maximum of nine letters,
digits, spaces, plus, or minus signs. The alarm repeatability is either nonrepeating or repeating (at 15-minute
intervals). Once level, label, and repeatability are filled in, they are protected from loss when the system is booted.
The procedure for changing Automatic Message Accounting (AMA) alarm levels for the AMA alarm feature is
located in the 235-190-300, Billing and Feature Specifications manual.
3.3.4 ALARM CONTROL
Some alarms can be inhibited or allowed manually from alarm reporting. These alarms are as follows:
Building/power alarms
External sanity monitor alarm
Fan or fuse alarms of the time multiplex switch (TMS) or the message switch (MSGS)
Miscellaneous alarms.
When a building/power alarm is inhibited, the respective indicator at the MCC Page 105/106 will show the
abbreviation INH in reverse video. Also the words BLDG INH in the SUMMARY STATUS AREA will be backlighted.
To inhibit or allow building power alarms, one can use the appropriate input message or the menu command (shown
at the MCC Page 105/106).
The external sanity monitor alarm indicator is shown at the MCC Page 116MISCELLANEOUS. Once the alarm is
235-105-210 October 1999
Copyright © 1999 Page 2

inhibited, the INHIBIT indicator will be in reverse video. Also this alarm can be inhibited or allowed by either the input
message or the menu command at the appropriate MCC page.
The MSGS, TMS, and ONTC fan or fan fuse alarms can be inhibited by the system. When such an alarm is
inhibited, this is shown at MCC Page 115COMMUNICATION MODULE SUMMARY. The reason an alarm will be
inhibited is because the respective scan point is chattering. After solving the problem, the alarm can be allowed
again by entering the input message:
ALW:ALM,MSGS=a[,b];
ALW:ALM,TMS=a[,b];
ALW:ALM,ONTC=a[,b];
Where: a= unit number 0or 1
b= FANALM or FRMFUSE (must choose one).
The miscellaneous alarms can be allowed or inhibited manually by means of the appropriate input message or the
menu command at the MCC Page 119MISCELLANEOUS ALARMS. When the alarm is inhibited, the respective
indicator at the MCC Page 119 will show the abbreviation INH in reverse video. Also the INHIBIT indicator of
MISCELLANEOUS ALARMS at MCC Page 116 will be in reverse video.
The miscellaneous frame fuse alarm indicator is marked FRAME FUSE and is shown at MCC Page 116
(MISCELLANEOUS ALARMS). This alarm can be inhibited by the system if the scan point is chattering. After
solving the problem, the alarm can be allowed by entering ALW:ALM,MFFUSE=a;
Where: a= miscellaneous frame fuse unit number 0or 1
When this alarm is inhibited, the abbreviation INH is displayed in reverse video at the right of the FRAME FUSE
indicator.
The miscellaneous frame fan alarm indicator is marked FRAME FAN and is shown at MCC Page 116
(MISCELLANEOUS ALARMS). This alarm can be inhibited by the system if the scan point is chattering. After
solving the problem, the alarm can be allowed by entering ALW:ALM,MFFAN;.
When this alarm is inhibited, the abbreviation INH is displayed in reverse video at the right of the FRAME FAN
indicator.
3.4 COMMAND AND TEST SCHEDULING
3.4.1 GENERAL
There are eight processes that can be automatically scheduled by means of input messages. The processes are as
follows:
Automatic line insulation test
Automatic progression testing
Office dependent data (ODD) backup
Routine exerciser
Automatic line evaluation
Per call test failure
235-105-210 October 1999
Copyright © 1999 Page 3

Stuck coin failures
Automatic mismatch detection.
3.4.2 AUTOMATIC LINE INSULATION TEST (ALIT)
The automatic line insulation test (ALIT) scans lines to detect leakage to battery or ground and to report
unpressurized or under pressurized line cables. The ALIT is scheduled by means of recent change data. The
parameters that have to be filled in can be found in 235-118-2XX, View 8.1OFFICE PARAMETERS. The ALIT
parameters can be temporarily changed by the input message EXC:LIT?. The next ALIT session will run at the
normally scheduled time. If a complete rescheduling of the ALIT is necessary, the parameters have to be changed
by means of recent change.
NOTE: If you reschedule ALIT via the 8.1 RC/V, the scheduling change of ALIT will not take place until the next
ALIT session is over. After ALIT has run, the new parameters will take effect. To verify how the next ALIT
session has been scheduled, the EXC:LIT,OPT=V; input message can be used. Once an ALIT has
started, it will generate an autonomous start message.
When the switching module/switching module-2000 (SM/SM-2000)) is in minimum mode (for example, initialization),
the ALIT is skipped or suspended. This is indicated by an EXC:LIT-SUSPEND message. When the SM/SM-2000 is
fully initialized or in normal mode, ALITs run normally. A system overload can cause a suspension. A report
EXC:LIT-IN is displayed when the ALIT resumes.
ALIT does not get suspended on a per SM/SM-2000 basis. However, ALIT can be suspended for an individual unit
(LU, ISLU, RT, etc.) being tested. When an individual unit is suspended a SINGLE CIRCUIT ABORT message is
created. The response to a manual OP:LIT input command will indicate if ALIT is currently suspended for a
particular unit.
There are two possible reports indicating the completion of an ALIT. One will indicate that all lines have been tested
in the scheduled time. The other report indicates that the test has stopped because the allotted time for the ALIT ran
out. The test will be terminated gracefully.
It is also possible to demand line insulation tests. They are called demand line insulation tests (DLIT). These tests
can be requested for one line or a range of lines, as well as a directory number.
NOTE: When using directory number only one line can be requested. However, a range of lines may be requested
when using line equipment number.
3.4.3 SUBSCRIBER LINE INSTRUMENT MEASUREMENT (SLIM)
The subscriber line instrument measurement (SLIM) equipment is located in the modular metallic service unit
(MMSU) which is one of the SM service units. SLIM is used to test subscriber analog lines for voltage, resistance,
and capacitance. A Routine and Operator mode of operation is provided.
Routine: This mode is used for automatic testing of analog lines. In this mode, a set of tests will run at a scheduled
time on a large number of analog lines. The tests, thresholds, and time schedules are defined via recent change
data. The parameters that have to be filled in can be found in the Recent Change Manual. The routine mode is
normally used to test large numbers of analog lines during times when machine traffic is at a minimum. Analog lines
that fail the test thresholds are stored on disk as line equipment numbers (LENs). At the end of the scheduled time,
these results are printed on the ROP.
The SLIM test status (suspended, done, in progress, scheduled or defined) and control (allow, inhibit, abort pokes)
can be viewed on the 162 [,1-4] page or using commands for that unit (OP:TSESS; ALW:TSESS; INH:TSESS;
ABT:TSESS; DUMP:FILEA;).
235-105-210 October 1999
Copyright © 1999 Page 4

Operator: This mode is used for manual testing of analog and digital lines. These tests are executed by MCC
pages, sometimes in combination with predefined, SLIM related recent change views. The operator mode is
normally used to test those lines that failed the routine mode tests. Procedures to clear line troubles detected by
SLIM routine testing can be found in 235-105-220.
3.4.4 AUTOMATIC PROGRESSION TESTING
An automatic progression test (APT) is performed on outgoing trunks. This test can indicate incorrect office
dependent data, wiring or cross-connect errors, or faulty trunk circuit hardware. The APT runs operational tests and
code answer test line (CATL) tests on trunks, and follows a specified schedule for these tests. This test is scheduled
by means of recent change procedures. The APT tests can determine only if the test passed or failed, not the actual
measured characteristics of the trunk. The parameters which must be entered can be found in 235-118-2XX. Like
the ALIT, an APT can be rescheduled once by means of the SCHED:APT input message. When APT is to be
rescheduled definitely, the parameters must be changed by means of recent change.
NOTE: The APT is disabled in a 5ESS®-2000 switch for AUTOPLEX®System 1000.
To verify how the next APT has been scheduled, the OP:APT input message can be used. When an APT has
started, an autonomous report RPT APT STARTED will be displayed. In APT, a history keeps track of information
concerning the tests. This allows interruptions of the testing cycle when the trunks are needed for service or when
the scheduled test time has run out. This will be indicated by an autonomous SUSPEND or STOP report. When the
whole test cycle has completed, an autonomous COMPLETED report will be displayed. When an APT has been
suspended, testing should resume again within 2 hours; otherwise, the APT will be aborted.
3.4.5 AUTOMATIC TRUNK TEST SCHEDULER
3.4.5.1 General
The automatic trunk test scheduler (ATTS) is used for automatic trunk testing in a 5ESS®-2000 switch for
AUTOPLEX®System 1000. (The ATTS is a secured feature that can be optionally purchased and can be used in a
5ESS®-2000 switch that is not part of the 5ESS®-2000 switch for AUTOPLEX®System 1000.) The ATTS feature
provides the ability to schedule routine testing on a periodic basis and is capable of supporting multiple, independent
schedules of test sessions.
Features of the ATTS include the following:
Programmable scheduling of tests, including ability to add, modify, and delete test sessions
Automatic logging of test results
Optional real-time printing of test results
Report generation
Flexible test-session control such as skipping, linking, etc.
3.4.5.2 ATTS Parameter Input
The technician is required to provide test-schedule-dependent data using the ATTS parameters. The required input
data may be entered through recent change/verify (RC/V) screen prompts (ATTS parameters view) or by manual
man-machine language (MML) input commands.
To obtain a printout of the population of the RC ATTS TEST SESSION PARAMETERS View 14.10 for a specific
235-105-210 October 1999
Copyright © 1999 Page 5

schedule, use the DUMP:ATPRM; input command.
3.4.5.3 ATTS Data Input
The technician is required to provide session scheduling information, including the trunk group (TG), the TG
member, and the range of members to test during the session. The required input data may be entered through
RC/V screen prompts (ATTS test session data view) or by manual MML input commands.
To obtain a printout of the population for the ATTS TEST SESSION SCHEDULER DATA View 14.9 for a specific
scheduler, use the DUMP:ATDTA; input command.
Before setting up the ATTS sessions, some conditions to observe are as follows:
The specified TG number has an associated automatic trunk test table number (TEST MODE) and signaling
type on the TRUNK GROUP View 5.1. This signaling type must be valid with the scheduled test. There must
also be an AUTO TRUNK TEST View 14.1, defined with the test and the TEST MODE.
Individual test sessions with the same ATTS schedule are not allowed to overlap in time.
For detailed information on the ATTS RC views and the related RC views, refer to the Recent Change Manual.
3.4.5.4 ATTS Recent Change and Verify Access
A complete test schedule consists of a collection of ATTS sessions. The ATTS sessions are usually populated from
a trunk line work station (TLWS). The steps required to define the ATTS sessions are as follows:
(1) Access the 196 page (RC View).
(2) Verify that the TRUNK GROUP View 5.1 and the AUTO TRUNK TEST View 14.1 are populated correctly.
(3) Request the ATTS TEST SESSION PARAMETERS View 14.10.
(4) When all of the test schedule parameters are completed, access the ATTS TEST SESSION SCHEDULE
DATA View 14.9.
Each ATTS is enabled with the ST:ATTS; input command, and begins executing sessions according to their
scheduled week, day, and start time. The ATTS continues to execute as scheduled until the STP:ATTS; input
command is executed. The variables and domain values for the ATTS input commands are found in the Input and
Output Messages Manual. To obtain the status information for a schedule, use the OP:ATTS; input command.
NOTE: Once a schedule is set up, the test type should not be changed. If it must be changed, the session data
(ATDTA) for that schedule must be deleted first. If the log file for that schedule already has data in it, when
the new schedule with the new test type is run, there may be REPT ATTS messages indicating that the old
results are being purged.
3.5 OPERATIONAL TESTS
3.5.1 GENERAL
Operational tests test the transmission characteristics of a trunk by measuring a signal from one exchange to
another. Operational tests are done as follows:
Automatically - Maintenance personnel are allowed to automatically schedule routine trunk testing sessions for
specific days of the week, given a start time and duration.
235-105-210 October 1999
Copyright © 1999 Page 6

Manually, on Demand - The maintenance personnel can run an operational test on specific trunks using either
the MCC/TLWS display pages or the input command TST:TRK;. The maintenance personnel can connect a
trunk to the TLWS test access unit so that other measurements can be made using external test equipment.
CAUTION: All interactive and noninteractive transient test calls that terminate on a subscriber line with any services
that are charged on a per-incoming-call basis will result in the subscriber being charged for the service
activation.
The services affected include call diversion, call waiting, call queuing, and freephone.
Maintenance personnel start and control testing from a TLWS. Manually-started test calls allow maintenance
personnel to specify the required non-interactive tests, and the incoming and outgoing trunks and trunk groups to be
tested.
Maintenance personnel can specify the following for both on-demand and automatically-scheduled test sessions:
Type of output results. The maintenance personnel can specify:
The type and flavor of test output reports
The number of test report lines.
Type of test termination criteria to be used, as follows:
The nominal attenuation in both transmission and reception directions for both outgoing and incoming
trunks
The transmissions level of test tones
The access code to the responder
The threshold for maintenance and service (for outgoing trunks only).
On a per-test-session basis, the test command includes a test termination criterion and an output results type.
Test call names are defined in the market-dependent data (MDD). These names are assigned to a particular set of
test calls and test line types that are available in the exchange. The test call names are used by the test call
interface tools: RC/V, MML commands and reports, and TLWS menu displays and pokes.
Maintenance personnel can use test call names while using a TLWS. They can examine test call names available,
and optionally request information about analog/digital for all tests. Output reports contain information about a test
call, including the test call name.
3.5.2 AUTOMATIC TRUNK TEST SCHEDULER
3.5.2.1 General
The ATTS is an integrated 5ESS-2000 switch software-based feature which provides a means of scheduling
automatic execution of specific types of operational test calls on out-going trunks and logging the individual test
results on the AM disk for retrieval at a later time.
Scheduling is accomplished by creating and maintaining a set of ``sessions'' in a ``schedule'' via an RC/V interface.
235-105-210 October 1999
Copyright © 1999 Page 7

The ATTS is accessible from normal maintenance terminals such as TLWS. The ATTS supports up to 20 schedules
which can run concurrently. The entries in these schedules correspond to scheduled test sessions.
Each schedule is operated independently, with the schedule data base accessible to multiple users simultaneously.
A single time entry in a single schedule, containing a single trunk group to be tested, is considered a session. The
ATTS includes only trunk groups as session entries. The ATTS allows schedule cycles of 8 weeks.
The tests start when specified by an entry in a routine test schedule control data table in the ODD. These tests are
done on a scheduled basis by agreement with the administration of a remote exchange. The ATTS implementation
involves an AM-based scheduler.
Test parameters or ``test result analysis thresholds'' determining success or failure of a test call are part of the trunk
group relationships in the data base. These parameters are used for demand testing. Each trunk group relationship
references a set of parameters to be used for testing their trunks.
The number of test sessions available accommodates all trunk groups to be tested for different types of trunk tests.
The exchange allows all trunk groups to be scheduled for testing. Some of these may be tested more than once in 8
weeks.
The telephone administration can specify the number of schedules/directors on a per-exchange basis with a
minimum of 20 concurrent schedules.
3.5.2.2 ATTS Scheduling
The ATTS has a granularity of start time in minutes. Administrations can impose constraining conventions, that is,
schedule sessions in 10-minute steps, thereby scheduling several trunk groups in one hour. However, the
constraints are enforced only by administrative procedures, not by switch software.
Test sessions in a schedule do not overlap. The system prevents maintenance personnel from creating conflicting,
overlapping session assignments. If it is desirable to reallocate part of an existing session, the system may require
that session first be unallocated.
Sessions can be linked together in a ``chain''. A session with a ``chain'' flag starts as soon as the prior session ends,
provided the stop time of the first session exactly matches the start time of the second session. A session always
stops at its assigned stop time, or earlier if all trunk group members have been tested.
Schedule data is entered per session, with each session representing a trunk group to be tested. For each test
session, the following must be specified:
Schedule number
Week and day
Start time/stop time (hour and minute)
Type of automatic test
Trunk group to test
First member number
Last member number.
Link indicator (indicating whether to link the session to the previous session)
Skip indicator (indicating whether to skip the test session entry)
235-105-210 October 1999
Copyright © 1999 Page 8

Retry indicator (indicating whether to do an automatic second attempt on failure).
Split trunk group testing is permitted. A trunk group can be tested over two or more sessions, if it is too big to be
tested in one session. This is done by providing start and end member numbers as inputs to the testing session.
The default start member is the first member of the trunk group. The default end member is the last member of the
group. Testing over this default range is completed only if time permits.
Routine testing is done on a trunk-group basis. Trunk groups may be tested in any order, and may be tested more
than once. However, in one schedule, only one trunk group at a time is tested.
The scheduler can be set to attempt an immediate single retry of aborting trunks using RC/V screen ATTS TEST
SCHEDULE PARAMETERS, field RETRY ON ABORT. The default status of this option is DISABLED (that is,
aborting trunks are not retried).
The scheduler can also be set to attempt an immediate single retest of failing trunks, using RC/V screen ATTS
TEST SCHEDULE PARAMETERS, field RETEST ON FAILURE. The default status of this option is DISABLED (that
is, failing trunks are not retested).
The progression (the trunk selection for testing in a group) is trunk group member number order. Busy trunks or a
busy responder in the far exchange (unavailable trunks) are skipped for later retry when revisiting the group.
Scheduled time permitting, the system iterates over the group member number list, attempting to test trunks
previously skipped. The maximum number of revisit iterations is controlled by the RC/V screen ATTS TEST
SCHEDULE PARAMETERS, field MAX LOOPS, and is associated with the session in the schedule indicated in the
view. A reasonable initial default revisit-iterations value is provided by the administration when populating the data
base.
The maintenance personnel can view the entered data of the ATTS schedules via the DUMP:ATDTA message as
follows:
Print or display an entire schedule, with schedule number as an input parameter
Print or display a specific day's schedule, by specifying the schedule number, week number, day within the
week, and trunk group number (optionally)
Print or display a specific week's schedule, obtained by specifying the schedule number and week number
Print or display the schedule for a particular trunk group, over all schedules.
The function has an 8-week schedule of automatic tests divided into two 4-week periods. The 12 months of any year
therefore correspond to 6 cycles of the 8-week schedule. The first day of the first week of the 4-week period, must
align with the first Monday in a month. So, if a month has five Mondays, there is no scheduled routine testing during
the week starting on the fifth Monday.
Each schedule is controlled separately. The running of a schedule is controlled by MML input commands (for
example, ST:ATTS and STP:ATTS). A running session can be halted by an MML stop-session message. Similarly,
via RC/V, maintenance personnel may skip individual, non-executing sessions in a running schedule without
deleting the full-session data.
Schedules run continuously, once started, except when all schedules are stopped by high-level commands or AM
recovery (manual or automatic). When the scheduler resumes normal activities after recovery, all schedules are
self-synchronizing to the AM clock and calendar.
Maintenance personnel can start an available schedule simply by specifying the schedule number via the ST:ATTS
235-105-210 October 1999
Copyright © 1999 Page 9