Enterprise Communications Server
Release 6
Maintenance for R6vs/si
555-230-127
Comcode 108041948
Issue 1
August 1997
Page 2
Copyright 1996, Lucent Technologies
All Rights Reserved
Printed in U.S.A.
Notice
Every effort was made to ensure that the information in this book was
complete and accurate at the time of printing. However, information is
subject to change.
Your Responsibility for Your System’s Security
Toll fraud is the un auth orized use of your telecommun icat ion s sy stem by an
unauthorized party, for example, persons other than your company’s
employees, agents, subcontractors, or persons working on your company’s
behalf. Note that there may be a risk of toll fraud associated with your
telecommunications system and, if toll fraud occurs, it can result in
substantial additional charges for your telecommunications services.
You and your system manager are responsible for the security of your
system, such as programming and configuring your equipment to prevent
unauthorized use. The system manager is also responsible for reading all
installation, instruction, and system administration documents provided
with this product in order to fully understand the features that can introduce
risk of toll fraud and the steps that can be taken to reduce that risk. Lucent
Technologies does not warrant that this product is immune from or will
prevent unauthorize d use o f co mmon- carrier telecommunication serv ices o r
facilities accessed through or connected to it. Lucent Technologies will not
be responsible for any charges that result from such unauthorized use.
Lucent Technologies Fraud Intervention
If you suspect that you are being victimized by toll fraud and you need
technical support or assistance, call Technical Service Center Toll Fraud
Intervention Hotline at 1 800 643-2353.
Federal Communica tions Commission Stateme nt
Part 15: Class B Statement. This equipment has been tested and found to
comply with the limits for a Class B digital device, pursuant to Part 15 of
the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference in a residential installation. This equipment
generates, uses, and can radiate radio-frequency energy and, if not installed
and used in accordance with the instructions, may cause harmful
interference to radio communications. However, there is no guarantee that
interference wi ll n ot occu r in a par ti cul ar insta llation. If this equ ipment does
cause harmful interference to radio or television reception, which can be
determined by turning the equipment off and on, the user is encouraged to
try to correct the interference by one or more of the following measures:
•Reorient the receiving television or radio antenna where this
may be done safely.
•To the extent possible, relocate the receiver with respect to the
telephone equipment.
•Where the telephone equipment requires ac power, plug the
telephone into a different ac outlet so that the telephone
equipment and receiver are on different branch circuits.
Part 68: Network Registration Number. This equipment is registered
with the FCC in accordance with Part 68 of the FCC Rules. It is identified
by FCC registration number AS593M-11185-MF-E.
Part 68: Answer-Supervision Signaling. Allowing this equipment to be
operated in a manner that does not provide proper answer-supervision
signaling is in violation of Part 68 rules. This equipment returns
answer-supervision signals to the public switched network when:
•Answered by the called station
•Answered by the attendant
•Routed to a recorded announcement that can be admin istered by
the CPE user
This equipment returns answer-supervision signals on all DID calls
forwarded back to the public switched telephone network. Permissible
exceptions are:
•A call is unanswered
•A busy tone is received
•A reorder tone is received
Trademarks
DEFINITY is a registered trademark of Lucent Technologies in the U.S.
and throughout the world.
AUDIX is a registered trademark of Lucent Technologies.
Ordering Information
Call:Lucent Technologies Publications Center
For additional documents, refer to the section entitled, “Related
Documents” in “About This Book.”
You can be p laced o n a S tand in g Ord er list f or th is and other document s yo u
may need. Standing Order will enable you to automatically receive updated
versions of individual documents or document sets, billed to account
information that you provide. For more information on Standing Orders, or
to be put on a list to receive future issues of this document, please contact
the Lucent Technologies Publications Center.
Warranty
Lucent Technologies provides a limited warranty on this product. Refer to
the “Limited use Software License Agreement” card provided with your
package.
European Union Decl aration of Co nformity
Lucent Technologies Business Communications Systems declares that
XXX equipment specified in this document conforms to the referenced
European Union (EU) Directives and Harmonized Standards listed below:
EMC Directive89/336/EEC
Low Voltage Directive73/23/EEC
The “CE” mark affixed to the equipment
means that it conforms to the above
Directives.
Disclaimer
Intellectual property related to this product and registered to AT&T
Corporation has been transferred to Lucent Technologies Incorporated.
Any references within this text to American Telephone and Telegraph
Corporation or AT&T should be interpreted as references to Lucent
Technologies Incorporated. The exception is cross references to books
published prior to December 31, 1996, which retain their original AT&T
titles.
Heritage
Lucent Technolo gies - f orm ed as a r es ult o f A T& T’s p lanned restructuring designs, builds, and delivers a wide range of public and private networks,
communication systems and software, consumer and business telephone
systems, and microelectronics components. The world-renowned Bell
Laboratories is the research and development arm for the company.
Acknowledgment
This document was prepared by the Product Documentation Development
group, Lucent Technologies, Denver, CO and Columbus, OH
.
Page 3
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
555-230-127
Contents
Contents
Contents iii
About This Book xxi
■ Generalxxi
■ Conventions Used in This Documentxxii
■ Organizationxxiii
■ Safety Precautionsxxiv
■ Class 1 Laser Devicexxv
■ Secu rity Issu e sxxv
■ Standards Compliancexxv
■ Electromagnetic Compatibility Standardsxxvi
■ Trademarks and Service Marksxxvii
■ Related Documentsxxviii
Issue 1
August 1997
Page iii
■ Federal Communications Commission Statementxxxi
1 M ai nten ance Arch ite cture 1-1
■ Maintenance Objects1-1
■ Alarm and Error Reporting1-2
■ Maintenance Testing1-2
■ Protocols1-3
■ Service C odes1-17
■ Facility Interface Codes1-18
■ Multimedia Interfa ce (M MI )1-19
2 Circuit Packs and Power 2-1
■ Circuit Packs2-1
■ Power2-6
3 Management Te rminals 3-1
■ General3-1
■ Management Terminals3-1
■ System Login Procedure3-3
■ Switch-Based Bulletin Board3-24
■ System Logoff Procedure3-26
■ DEC VT220 Terminal3-27
4 Initi a lization and Recovery 4-1
■ Reset System 1 (System Warm Start)4-2
Page 4
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
555-230-127
Contents
■ TIE-BD (Ti e Tr unk Circuit Pack)10-1347
■ TIE-DS1 (DS1 Tie Trunk)10-1348
■ TIE-TRK (Tie Trunk)10-1366
■ TONE-BD (Tone-Clock Circuit Pack)10-1391
■ TONE-PT (Tone Generator)10-1411
■ TSC-ADM (Administered Temporary
Signaling Connections)10-1422
■ TTR-LEV (TTR Level)10-1428
■ UDS1-BD (UDS1 Interface Circuit Pack)10-1433
■ VC-BD10-1523
■ VC-DSPPT10-1527
■ VC-LEV (Voice Conditioner
DSP Port Level)10-1536
■ VC-SUMPT10-1539
■ WAE-PORT (Wideband Access Endpoint Port)10-1544
Issue 1
August 1997
Page xv
■ XXX-BD (Common Port Circuit Pack)10-1551
A Error Messages A-1
■ Error Messages from Chapter 8,
Maintenance CommandsA-1
■ busyout access-endpointA-1
■ busyout boardA-2
■ busyout cdr-linkA-3
■ busyout data-moduleA-4
■ busyout journal-printerA-5
■ busyout linkA-5
■ busyout misA-6
■ busyout modem-poolA-7
■ busyout packet-controlA-8
■ busyout pms-linkA-8
■ busyout portA-9
■ busyout pri-endpointA-10
■ busyout sp-linkA-11
■ busyout spe-standbyA-11
■ busyout stationA-12
■ busyout tdmA-13
■ busyout tone-clockA-13
Page 16
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
555-230-127
Contents
■ busyout trunkA-15
■ cancel hardware-groupA-16
■ change circuit-packsA-16
■ change synchronizationA-17
■ clear auditsA-17
■ clear errorsA-17
■ clear interfaceA-18
■ clear isdn-testcallA-19
■ clear linkA-20
■ clear mstA-21
■ clear pktA-21
■ clear portA-22
■ copy update-fileA-22
■ disable administered-connectionA-23
■ disable mstA-24
Issue 1
August 1997
Page xvi
■ disable suspend-alm-origA-24
■ disable synchronization-switchA-25
■ disable test-numberA-25
■ display alarmsA-26
■ display disabled-testsA-28
■ display errorsA-28
■ display eventsA-33
■ display initcausesA-33
■ display memory-configurationA-33
■ display portA-34
■ display synchronizationA-34
■ display system-parameters maintenanceA-35
■ display timeA-35
■ download update-fileA-35
■ enable administered-connectionA-38
■ enable mstA-39
■ enable suspend-alm-origA-39
■ enable synchronization-switchA-40
■ enable test-numberA-40
■ format card-memA-41
Page 17
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
555-230-127
Contents
■ get vectorA-41
■ list disabled-mosA-42
■ list historyA-42
■ list isdn-testcallA-43
■ list marked-portsA-43
■ list measurementsA-44
■ list mstA-44
■ list suspend-alm-origA-45
■ list test ca ll sA-45
■ mark portA-46
■ monitor bcmsA-47
■ monitor healthA-47
■ monitor systemA-48
■ monitor tra fficA-49
■ monitor trunkA-49
Issue 1
August 1997
Page xvii
■ recycle carrierA-50
■ refresh spe-standbyA-51
■ release access-endpointA-51
■ release boardA-52
■ release cdr-linkA-53
■ release data-moduleA-54
■ release journal-printerA-55
■ release linkA-55
■ release misA-56
■ release modem-poolA-57
■ release packet-controlA-58
■ release pms-linkA-58
■ release portA-59
■ release pri-endpointA-60
■ release sp-linkA-61
■ release spe-standbyA-62
■ release stationA-62
■ release tdmA-63
■ release tone-clockA-64
■ release trunkA-65
Page 18
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
555-230-127
Contents
■ reset boardA-66
■ reset interfaceA-67
■ reset maintenanceA-69
■ reset spe-standbyA-70
■ reset systemA-70
■ restore announcementsA-71
■ resume hardware-groupA-72
■ save announcementsA-73
■ save translationA-74
■ set expansion-linkA-75
■ set optionsA-76
■ set signaling-groupA-78
■ set synchronizationA-78
■ set td mA-79
■ set tim eA-80
Issue 1
August 1997
Page xviii
■ set tone-clockA-81
■ set vectorA-83
■ status access-endpointA-84
■ status administered-connectionA-85
■ status attendantA-86
■ status auditsA-86
■ status bri-portA-87
■ status card-memA-88
■ status cdr-linkA-89
■ status cleared-alarm-notifA-89
■ status conferenceA-89
■ status data-moduleA-89
■ status hardware-groupA-90
■ status healthA-91
■ status interfaceA-91
■ status isdn-testcallA-92
■ status journal-linkA-93
■ status linkA-94
■ status loginsA-94
■ status mstA-95
Page 19
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
555-230-127
Contents
■ status packet-controlA-95
■ Ostatus periodic-scheduledA-96
■ status pms-linkA-96
■ status pri-endpointA-97
■ status processor-channelA-97
■ status signaling-groupA-98
■ status sp-linkA-99
■ status stationA-99
■ status synchronizationA-100
■ status systemA-100
■ status trunkA-101
■ status tsc-administeredA-102
■ status ttiA-103
■ test access-endpointA-103
■ test alarmsA-104
Issue 1
August 1997
Page xix
■ test analog-testcallA-108
■ test boardA-110
■ test card-memA-111
■ test cdr-linkA-112
■ test customer-alarmA-113
■ test data-moduleA-113
■ te s t ds1- l oopA-114
■ test duplication-interfaceA-116
■ test eda-external-device-alrmA-117
■ test environmentA-117
■ test hardware-groupA-117
■ test inads-linkA-120
■ test interfaceA-120
■ test isdn-testcallA-122
■ test journal-printerA-123
■ test ledA-124
■ test linkA-124
■ test maintenanceA-125
■ test me moryA- 126
■ test modem-poolA-128
Page 20
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
555-230-127
Contents
■ test network-controlA-129
■ test packet-controlA-131
■ test pktA-131
■ test pms-linkA-132
■ test portA-133
■ test pri-endpointA-134
■ te s t proc essorA-135
■ test shadow-li nkA-136
■ test signaling-groupA-137
■ test sp-linkA-138
■ test spe-standbyA-138
■ test statio nA-139
■ test synchroniz at i onA-140
■ test tdmA-141
■ test tone-clockA-142
Issue 1
August 1997
Page xx
■ test trunkA-143
■ test tsc-admini ste re dA-144
■ upgrade softwareA-145
IN Index IN-1
Page 21
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
About This Book
555-230-127
About This Book
General
Issue 1
August 1997
Page xxiGeneral
This book has the information needed to monitor, test, and maintain DEFINITY
®
Enterprise Communications Server Release 6 Systems and covers many of the
faults and troubles that can occur in the system. Most maintenance requirements
are simple procedures due to the modular, self-testing nature of the system.
This document covers information related to DEFINITY ECS Release 6.1,
including all incremental releases.
Simple, traditional troubleshooting methods are sometime s sufficient to locate
and clear faults. The traditional methods include terminal substitution, visual
inspections, continuity checks, and clarification of operating procedures with
users.
The information in this book is intended for use by:
■ A maintenance tec hnician dispa tched to a DEFINITY System site in
response to a trouble alarm or a user trouble report,
■ A maintenance technician located at a remote maintenance facility, or
■ The user’s assigned mainte nance te chnician. The technician is expected
to have a knowledge of telecommunications fundamentals and of the
DEFINITY
Enterprise Communications Server Release 5 Systems to the
extent that the procedures in this book can be performed, in most cases,
without assistance.
Page 22
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
About This Book
555-230-127
Each DEFINITY System has a user-designated System Manager who is
responsible for administration of the system. The maintenance technician should
work closely with the user’s System Manager.
This book is not intended to solve all levels of troubles. It is limited to troubles that
can be solved by using the Alarm Log, Error Log, trouble-clearing procedures,
maintenance tests, and traditional troubleshooting methods. If the trouble still has
not been resolved, it the responsibility of the maintenance technician to escalate
the problem to a higher level of technical support. Escalation should conform to
the procedures in the
Technical and Administration Escalation Plan
When features, screen displays, equipment, or operations differ between system
types, for example, Generic 3 V4, Release 5si, or Release 5si + memory, these
differences are clearly identified by use of the following indicators: “[G3V4]”,
“[R5si]”, or “[R5 si + mem ory ].”
Conven tions Used in Th is Document
The following conventions are used in this document:
Issue 1
August 1997
Page xxiiConventi ons Used in This Document
.
■ DEFINITY Systems are called G3V4, Release 5; Release 5vs, Release 5si,
Release 5si + memory, and Release 6.
■ All occu rrences of G3siV 4, G3siV4+ m, Releas e 5si, and Releas e 5 si +
memory are called Release 5si unless a specific configuration is required
to differentiate among product offerings.
■ All occurrences of R5 without a suffix following the “5” refer to Release 5si,
and Release 5si + memory.
■ A component of a DEFINITY System, such as a circuit pack, occurring
without a reference to any specific system, is part of G3V4 or Release 5.
■ The term “ASAI” is synonymous with the newer CallVisor ASAI.
■ All physical dimension s in this book are in English (Foot Pound Second)
(FPS) followed by the metric Centimeter Grams Second (CGS) in
parenthesis. Wire gauge measuremen ts are in AWG followed by the
diameter in millimeters in par en t he s is .
■ Adm oni shmen ts used in this book are as follows:
!
CAUTION:
This sign is used to indicate possible harm to software, possible loss
of data, or possible service interuptions.
!
WARNING:
This sign is used where there is possible harm to hardware or
equipment.
Page 23
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
About This Book
555-230-127
!
DANGER:
This sign is used to indicate possible harm or injury to people.
Organization
This book is organized into two volumes: volume 1 contains Chapters 1 through
9, and volume 2 contains Chapter 10.
■ Chapter 1, ‘‘Maintenance Architecture’’ describes the system’s design
and maintenance strategy.
■ Chapter 2, ‘‘Circuit Packs and Power’’ describes DEFINITY circuit
packs. It also explains how power is supplied to the system.
■ Chapter 3, ‘‘Man a gement Terminals’’ describes the various
management terminals that can be used on the system and how to set up
the terminals.
■ Chapter 4, ‘‘Initialization and Recovery’’ describes the various reset
and reboot processes, and discusses how these processes are used to
perform maintenance and to recover systems or subsystems that are out
of service.
Issue 1
August 1997
Page xxiiiOrganization
■ Chapter 5, ‘‘Rout i ne Maintena nce P r ocedures’’ discusses common
maintenance tasks, including: removing and installing circuit packs,
removing and restoring power, performing syst em backups, upgrading
software, and various testing and troubleshooting procedures.
■ Chapter 6, ‘‘Reliability Systems: A Maintenance Aid’’ prov id es de ta il e d
hardware and functional descriptions as well as additional repair strategy
(in addition to the procedures provided in this document) for Standard,
High, and Critical Reliability systems.
■ Chapter 7, ‘‘LED Interpretation’’ is a quick reference to interpreting
circuit pack LEDs.
■ Chapter 8, ‘‘Mai nt enance Comm a nd s and Trouble-Clearing Aids’’ has
the maintenance commands, and explains how to use these commands
using the management terminal. Specific command syntax plus typical
forms and display output are also given in the chapter.
■ Chapter 9, ‘‘Packet Bus Fault Isolation and Correction’’ describes
Pack Bus maintenance and the interactions of the bus with Packet circuit
packs. The chapter also discusses how Packet Bus faults are isolated and
corrected.
■ Chapter 10, ‘‘Maintenan ce Object Repair Proce dures’’ has specific
troubleshooting and repair instructions for every component in the system.
The chapter contains repair procedures for system-alarmed and userreported troubles. For each MO, a table lists the alarm level, hardware
error associated with the MO, and the associated test that caused the
error. The test sequences and the specific command line entry required to
Page 24
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
About This Book
555-230-127
run the tests are given and a brief description of each test. Explanations of
error codes associated with each test are given, as are specific
maintenance procedures to be used to resolve each problem.
Issue 1
August 1997
Page xxivSafety Precautions
Each MO is described in a separate section of Chapter 10, ‘‘
Repair Procedures’’. The individual sections are labeled with the name of the MO
exactly as the name appears in the Alarm Log; for example, MAINT (for
Maintenance circuit pack). The only exception is the MO name for Common Port
Circuit Pack maintenance which is XXX-BD. The XXX-BD section contains a set of
common tests used by certain circuit packs listed in the section. The common
portion of these circuit packs is the generic hardware that interfaces with the
Time Division Multiplex (TDM) Bus.
Lucent Technologies listens carefully to its readers. The organization of this book
is a direct result of user feedback. Your feedback is important. Use the feedback
form at the back of this book to send your comments to Lucent Technologies.
Safety Precautions
When performing maintenance or translation procedures on the system, users
must observe certain precautions. Observe all caution, warning, and danger
statements to prevent loss of service, possible equipment damage, and possible
personal injury. In addition, the following precautions regarding electromagnetic
interference (EMI) and static electricity must be observed:
Electromagnetic Interfer ence
Maintenance Object
This equipment generates, uses, and can radiate radio frequency energy.
Electromagnetic fields radiating from the switch may cause noise in the
customer’s equipment. If the equipment is not installed and used in accordance
with the instruction book, radio interference may result.
!
WARNING:
To maintain the EMI integrity of the system, maintenance personnel must
ensure that all cabinet panels, covers, and so forth, are firmly secured
before leaving the customer’s premises.
Static Electricity
To prevent or reduce electrostatic discharge (ESD), always attach wrist
grounding straps before working on switch components or handling circuit
packs.
!
CAUTION:
Electrostatic discharge can damage or destroy circuit packs containing
integrated circuits (ICs).
Page 25
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
About This Book
555-230-127
The ESD wrist strap, cable assembly, and spare fuses are packed in a plastic
bag and placed in the top of the system cabinet. Use the ESD wrist strap when
troubleshooting, performing maintenance, or handling any circuit packs
associated with the system.
Class 1 Laser Device
The DEFINITY ECS contains a Class 1 Laser device if single-mode fiber optic
cable is connected to a remote Expansion Port Network (EPN). The LASER
device operates within the following parameters:
Power Output: -5 dBm
Wavelength: 1310 nm
Mode Field Diameter: 8.8 microns
!
DANGER:
Use of controls or adjustments or performance of procedures other than
those specified herein may result in hazardous radiation exposure.
Issue 1
August 1997
Page xxvClass 1 Laser Device
Contact your Lucent Technolgies representative for more information.
Security Issues
A number of matters concerning maintenance are affected by security issues.
For details, be sure to consult the
555-025-600.
!
CAUTION:
Login security is an attribute of the DEFINITY® Enterprise Communications
Server (ECS) Release 5 software.
Standards Compliance
The equipment presented in this document complies with the following (as
appropriate):
■ ITU-T (Formerly CCITT)
■ ECMA
■ ETSI
■ IPNS
GBCS Products Security Handbook, Release 6,
■ DPNSS
■ National ISDN-1
■ National ISDN-2
Page 26
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
555-230-127
About This Book
■ ISO-9000
■ ANSI
■ FCC Part 15 and Part 68
■ E N55022
■ EN 50081
■ EN 50082
■ CISPR22
■ Australia AS3548 (AS/NZ35 48)
■ Australia AS3260
■ IEC 825
■ IEC950
■ UL 1459
■ UL19 50
Issue 1
August 1997
Page xxviElectr omagnetic Compatibility Sta ndards
■ CSA C222 Numbe r 225
■ TS001
Electromagnetic Compatibility
Standards
This product complies with and conforms to the following:
■ Limits and Me thods of Measuremen ts of Radio Interference
Characteristics of Information Technology Equipment, EN55022
(CISPR22), 1993
■ EN 50082-1, Europ ean Generi c Immun ity Stand ard
■ FCC Parts 15 and 68
■ Australia AS3548
NOTE:
The system conforms to Class A (industrial) equipment. Voice
terminals meet Class B requirements.
■ Electrostatic Discharge (ESD) IEC 1000-4-2
■ Radiate d radio frequency field IEC 1000-4-3
■ Electrical Fast Transient IEC 1000-4-4
■ Lightning effects IEC 1000-4-5
■ Conducted radio frequency IEC 1000-4-6
■ Mains frequency ma gnetic field IEC 1000-4-8
Page 27
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
555-230-127
About This Book
■ Low frequen cy mains disturbance
The system conforms to the following:
■ Elect romagnetic compatibility General Immunity Standard, part 1;
■ Radiate d radio frequency field immunity requirements IEC 1000-4-3
■ Electrical fast transient/burst immunity requirements IEC 1000-4-4
European Union Standards
Lucent Technologies Business Communica tions Systems declares that the
DEFINITY equipment specified in this document bearing the “CE” mark conforms
to the European Union Electromagnetic Compatibility Directives.
The “CE” (Conformité Europeénne) mark indicates conformance to the European
Union Electromagnetic Compatibility Directive (89/336/EEC) Low Voltage
Directive (73/23/EEC) and Telecommunication Terminal Equipment (TTE)
Directive (91/263/EEC) and with i-CTR3 Basic Rate Interface (BRI) and i-CTR4
Primary Rate Interface (PRI) as applicable.
Issue 1
August 1997
Page xxviiTrademarks and Service Marks
The “CE” mark is applied to the following Release 5 products:
■ Global AC powered Multi-Carrier Cabinet (MCC)
■ DC powered Multi-Carrier Cabinet (MCC) with 25-Hz ring generator
■ AC powered Single-Carrier Cabinet (SCC) with 25-Hz ring generator
■ AC powered Compact Single-Carrier Cabinet (CSCC) with 25-Hz ring
generator
■ Enhanced DC Power System
Trademar ks a nd Se rvice Marks
The following are trademarks or registered trademarks of Lucent Technologies:
■ 5ESS ™, 4ESS™
■ AUDIX
■ Callvisor
■ Callmaster
■ CentreVu ™
■ CONVERSANT
■ DEFINITY
®
®
®
®
®
Page 28
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
About This Book
555-230-127
Issue 1
August 1997
Page xxviiiRelated Documents
■ DIMENSION
■ MERLIN
■ VOICE POWER
®
®
®
The following are trademarks or registered trademarks of AT&T:
■ ACCUNET
■ DATAPHO NE
■ MEGACOM
■ MULTI QUE ST
■ TELES EE R
®
®
®
®
®
The following are trademarks or registered trademarks of other companies:
■ Ascend
■ Audichron
■ MS-DOS
■ MicroCha nnel
■ MU LTIQUEST
■ PagePac
■ UNIX
®
(registered trademark of Ascend, Inc.)
®
(registered trademark of the Audichron Company)
®
(registered trademark of the Microsoft Corporation)
®
(registered trademark of IBM Systems)
®
(registered trademark of Telecommunications Service)
®
(trademark of the Dracon Division of the Harris Corporation)
®
(trademark of the Novell Corporation)
Related Documents
The following books are useful for system-related information:
Gives a high-level overview of what is new in DEFNITY ECS Release 6. Describes
the hardware and software enhancements and lists the problem corrections for
this release.
Provides hardware descript ions, syst em parameters, listin g of hardware req uired
to use features, system configurations, and environmental require men ts. This
compact reference combines and replac es Release 6
Specifications
DEFINITY ECS Release 6 — Administration and Feature Description, Issue
, 555-230-522
2
and Release 6
Pocket Reference
555-230-474
System Description and
.
Page 29
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
About This Book
555-230-127
Provides descriptions of system features. Also provides step-by-step procedures
for preparing the screens that are required to implement the features, functions,
and services of the system. Includes the applications and benefits, feature
interactions, administration requirements, hardw are requirement s, and
procedures for voice terminal, data module, and trunk group administration.
Issue 1
August 1997
Page xxixRelated Docu me nts
DEFINITY ECS Release 5 — System Monitoring and Reporting, Issue 4,
555-230-511
Provides detailed descriptions of the measurement , status, security, and recent
change history reports available in the system and is intended for administrators
who validate traffic reports and evaluate system performance. Includes
corrective actions for potential problems. Issue 2 of this document was titled
Traffic Reports
. The Release 5 version of this document applies to Release 6 as
well.
DEFINITY Communications System Generic 3 Planning and Configuration,
Issue 2, 555-230-601
This document was written for Generic 3 Version 2 software, but still contains
relevan t inf o rmation for the ECS.
Provides step-by-step procedure s for the account team in determining the
customer’s equipment and hardware requirements to configure a system
according to the customer specifications. Includes detailed requi remen ts and
block diagrams.
DEFINITY ECS Release 5 — Installation and Test for Single-Carrier Cabinets,
Issue 3
, 555-230-894
Provivdes procedures and information for hardware installation and initial testing
of single-carrier cabinets.The Release 5 version of this document applies to
Release 6 as well.
This document is available in the following languages: English, German (DE),
Dutch (NL), Brazilian Portugues e (PTB ), Euro pean French (FR), Castillian
Spanish (SP), Italian (IT), Russian (RU), and Japanese (JA). To order, append the
language suffix to the document number; for example, 555-230-894DE for
German. No suffix is needed for the English version.
DEFINITY ECS Release 5 — Installation and Upgrades for R5vs, Issue 1
,
555-230-124
Provivdes procedures and information for hardware installation, upgrades, and
initial testing of compact single-carrier cabinets. The Release 5 version of this
document applies to Release 6 as well.
DEFINITY ECS Release 6 — Installation and Test for Multi-Carrier Cabinets,
Issue 3,
555-230-112
Provides procedures and information for hardware installation and initial testing
of multi-carrier cabinets.
Page 30
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
About This Book
555-230-127
DEFINITY ECS Release 6 — Installation for Adjuncts and Peripherals, Issue
, 555-230-125
2
Provides procedures and information for hardware installation and initial testing
of ECS adjunct and peripheral systems and equipment .
DEFINITY Communications System Generic 3vs/si — Upgrades and
Additions, Issue 1
, 555-230-108
Provides procedures for an installation technician to convert an existing
DEFINITY Communications System earlier than Generic 3 Version 4 to Generic
3vs/si Version 4.
Issue 1
August 1997
Page xxxRelated Documents
DEFINITY ECS Release 6 — Upgrades and Additions for R6vs/si, Issue 3
,
555-230-120
Provides procedures for an installation technician to convert an existing
DEFINITY Communications System Generic 3 Version 4 to DEFINITY ECS and
from DEFINITY ECS Release 5 to DEFINITY ECS Release 6.
Included are upgrade considerations, lists of required hardware, and
step-by-step upgrade procedures. Also included are procedu res to add control
carriers, switch node carriers, port carriers, circuit packs, auxiliary cabinets, and
other equipment.
DEFINITY ECS
Release 6 —
Maintenance for R6r, Issue 1
, 555-230-126
Provides detailed descriptions of the procedures for monitoring, testing,
troubleshooting, and maintaining the R6r ECS. Included are main tena nce
commands, step-by-step trouble-clearing procedures, the procedures for using
all tests, and explanat ions of the syst em’ s error codes.
BCS Products Security Handbook, Issue 6
, 555-025-600
Provides information about the risks of telecommunications fraud and measures
for addressing those risks and preventing unauthorized use of BCS products.
This document is intended for telecommunications managers, console operators,
and security organizations within companies.
DEFINITY ECS
Release 5 —
Terminals a nd A dj uncts Reference, Issue 8
,
555-015-201
Provides descriptions of the peripheral equipment that can be used with System
75, System 85, DEFINITY Communications System, and DEFINITY ECS. This
document is intended for customers and Lucent Technologies account teams for
selecting the correct peripherals to accompany an ECS. The Release 5 version of
this document applies to Release 6 as well.
DEFINITY Wireless Business System Users Guid e,
DEFINITY Wireless Business System Installation and Test Guide,
555-232-105
555-232-102
Page 31
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
About This Book
555-230-127
Issue 1
August 1997
Page xxxiFederal Comm unications Commission Statement
DEFINITY Wireless Business Systems System In terface
AT&T Network and Data Connectivity Reference
Federal Comm unications Commissi on
Statement
Part 68: Statement
Part 68: Answer-Supervision Signaling. Allowing this equipment to be operated in
a manner that does not provide proper answer-supervision signaling is in
violation of Part 68 rules. This equipment returns answer-supervision signals to
the public switched network when:
■ Answered by the called station
■ Answ ered by the attendant
■ Routed to a recorded announcement that can be administered by the CPE
user
This equipment returns answer-supervision signals on all DID calls forwarded
back to the public switched telephone network. Permissible exceptions are:
, 555-232-108
, 555-025-201
■ A call is unanswered
■ A busy tone is received
■ A reorder tone is received
This equipment is capable of providing users access to interstate providers of
operator services through the use of access codes. Modification of this
equipment by call aggregators to block access dialing codes is a violation of the
Telephone Operator Consumers Act of 1990.
This equipment complies with Part 68 of the FCC Rules. On the rear of this
equipment is a label that contains, among other information, the FCC registration
number and ringer equivalence number (REN) for this equipment. If requested,
this information must be provided to the telephone company.
The REN is used to determine the quantity of devices which may be connected to
the telephone line. Excessive RENs on the telephone line may result in devices
not ringing in response to an incoming call. In most, but not all areas, the sum of
RENs should not exceed 5.0. To be certain of the number of devices that may be
connected to a line, as determined by the total RENs, contact the local telephone
company.
NOTE:
REN is not required for some types of analog or digital facilities.
Page 32
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
About This Book
555-230-127
Means of Connection
Connection of this equipment to the telephone network is shown in the following
table.
DID Trunk02RV2-T0.0BRJ2GX, RJ21X
CO Trunk02GS20.3ARJ21X
CO Trunk02LS20.3ARJ21X
Tie TrunkTL31M9.0FRJ2GX
1.544 Digital Interf ace04DU9-B,C6.0PRJ48C, RJ48M
1.544 Digital Interf ace04DU9-BN,KN6.0PRJ48C, RJ48M
120A2 Channel Service Unit04DU9-DN6.0PRJ48C
SOC/REN/
A.S. CodeNetwork Jacks
RJ11C
If the terminal equipment (DEFINITY® System) causes harm to the telephone
network, the telephone company will notify you in advance that temporary
discontinuance of service may be required. But if advance notice is not practical,
the telephone company will not if y the cus tomer as soon as poss ibl e. Also, you
will be advised of your right to file a complaint with the FCC if you believe it is
necessary.
The telephone company may make changes in its facilities, equipment,
operations or procedures that could affect the operation of the equipment. If this
happens, the telephone company will provide advance notice in order for you to
make necessary modifications to maintain uninterrupted service.
If trouble is experienced with this equipment, for repair or warranty information,
please contact the Technical Service Center at 1-800-248-1234. If the equipment
is causing harm to the telephone network, the telephone company ma y request
that you disconnect the equipment until the problem is resolved.
It is recommended that repairs be performed by Lucent Technologies certified
technicians.
The equipment cannot be used on public coin phone service provided by the
telephone company. Connection to party line service is subject to state tariffs.
Contact the state public utility commission, public service commission or
corporation commission for information.
This equipment, if it uses a telephone receiver, is hearing aid compatible.
Page 33
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
1
Maintenance Architecture
The maintenance subsystem is a part of the software that initializes and
maintains the system. The software continuously monitors system health, and
keeps a record of errors detected in the system. The maintenance subsystem
also provides a user interface for on-demand testing.
555-230-127
Issue 1
August 1997
Page 1-1Maintenan ce O bjects
1
This chapter provides a brief description of the Release 5 maintenance strategy
and the bac kground information on the system’s overall functions. For detailed
descriptions of components and subsystems, refer to related topics in Chapter
10, ‘‘Maintenance Object Repair Procedures’’.
Maintenance Objects
The system is partitioned into separate entities called Maintenance Objects
(MOs). Each MO is referred to by an upper-case, mnemonic-like name that
serves as an abbreviation for the MO. For example, “CO-TRK” stands for “Central
Office TRunK”. Each MO is monitored by the system and has its own
maintenance strategy. Most MOs are individual circuit packs. Som e MOs are
hardware components that reside on part of a circuit pack. For example, the
TDM bus Clock circuits reside on the Tone/Clock circuit pack. Other MOs, such
as cabinet environmental sensors, represent larger subsystems or sets of
monitors. Finally, some MOs, such as SYNChronization, represent processes or a
combination of processes and hardware.
“Maintenance names” are recorded in the error and alarm logs. Individual copies
of an MO are assigned an address that defines the MO’s physical location in the
system. These locations disp lay a s the “PORT” fiel d in the alarm and err or lo gs
and as output of various commands such as test board, busy tdm-bus, and so
forth.
Page 34
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
Alarm and Error Reporting
During normal operations, software or firmware may detect error conditions
relevant to specific MOs. The system attempts to fix or circumvent these
problems automatically. However, if a hardware component incurs too many
errors, an alarm is raised. Errors are detected in two ways:
■ For “in-line” errors, firmware on the component det ects the
occurrence of an error during ongoing operations.
■ For other types of errors, a “periodic test” or a “scheduled test”
started by the software detects the error. The technician can run
these tests on demand by using the maintenance comman ds
described in Chapter 8, ‘‘
‘‘Maintenance Object Repair Proced ures ’’.
Software puts the error in the error log, and increments the error counter for that
error. When an error counter is “active,” (greater than zero), there is a
maintenance record for the MO.
busyout journal-printer’’, and Chapter 10,
Issue 1
August 1997
Page 1-2Alarm and Error Reporting
Alarms are classified as MAJOR, MINOR, or WARNING, depending on the effect
on system operation. They are also classified as ON-BOARD or OFF-BOA R D.
— MAJOR alarms identify failures that cause a critical degradation of
service. These alarms require immediate attention.
— MINOR alarms identify failures that cause some service degradation but
that do not render a crucial portion of the system inoperable. MINOR
alarms require attention. However, typically a MINOR alarm affects only a
few trunks or stations or a single feature.
— WARNING alarms identify failures that cause no significant degradation of
service or equipment failures external to the switch. These failures are not
reported to INADS or to the attendant console.
— ON-BOARD problems originate in the circuitry on the alarmed circuit
pack.
— OFF-BOARD problems originate in a process or component that is
external to the circuit pack.
Alarms are discussed further in Chapter 10, ‘‘
Procedures’’.
Maintenance Testing
Maintenance Ob ject Repair
Most troubles are reduced to the circuit pack level and can be identified by LEDs
on the circuit packs and software reports generated by the system. The
maintenance tests in the system are divided into three groups:
■ Periodic
Page 35
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
Background tests are performed by software maintenance, usually on an
hourly basis. These tests are nondestructive and can be run during high
traffic periods without interfering with calls.
■ Scheduled
Background tests performed by software maintenanc e, usually on a daily
basis, are generally more thorough than periodic testing. The tests are
considered destructive and are run only during off-hours so as not to
interfere with calls.
■ Fixed interval
Background tests performed by software maintenance at regular time
intervals (these intervals cannot be administered). These tests run
concurrently with periodic maintenance. The following table lists the MOs
that run fixed interval testing.
Maintenance Object
Issue 1
August 1997
Page 1-3Protocols
Interval
(minutes)
Demand tests are also run by the system when it detects a need or by
maintenance personnel in trouble-clearing activities. Demand tests include
periodic tests plus other tests required only when trouble occurs. Some
nonperiodic demand tests may disrupt system operation. In this book,
destructive (service-disrupting) tests are identified in boldface type.
Maintenance personnel can use the management terminal to initiate the same
tests that the system initiates. The terminal screen displays the test results.
Protocols
This section describes the protocols handled by the system and the points where
these protocols change. Figure 1-1
transmission state changes. Figure 1-1
equipment, like a terminal or host, through DCE equipment, like a modem or data
module, into a communications port on the system. The data flow is shown by
solid lines. Below these lines are the protocols used at particular points in the
data strea m.
POWER60
SPE-SELEC60
STBY-SPE120
TDM-BUS10
TONE-PT10
is a pictorial guide through data-
illustrat es the flo w of dat a fro m DT E
Not shown in the Figure 1-1
is the treatment of D-channels in ISDN-PRI and
ISDN-BRI transmissions. PRI and BRI D-channels transport information elements
Page 36
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
that contain call-signaling and caller information. These elements conform to
ISDN level-3 protocol. In the case of BRI, the elements are created by the
terminal or data module; for the PRI, the elements are created by the system,
which inserts them into the D-channel at the DS1 port.
For ISDN transmissions, therefore, BRI terminals and data modules, and DS1
ports insert, interpret, and strip both layer-2 DCE information and layer-3
elements. Also, the DS1 port passes layer-3 elements to the system for
processing.
Layers
The Open System Interconnect (OSI) model for data communi cations cont ains
seven layers, each with a specific function. Communications to and through the
system concern themselves only with layers 1 and 2 of the model.
Issue 1
August 1997
Page 1-4Protocols
Layer 1, or the
physical layer,
covers the physical interface between devices and
the rules by which bits are passed. Among the physical layer protocols are
RS-232, RS-449, X.21, DCP, DS1, and others.
Layer 2, or the
data-link layer
, refers to code created and interpreted by the DCE.
The originating equipment can send blocks of data with the necessary codes for
synchronization, error control, or flow control. With these codes, the destination
equipment checks the physical-link reliability, corrects any transmission errors,
and maintains the link. When a transmission reaches the destination equipment,
it strips any layer-2 information the originating equipment may have inserted. The
destination equipment only passes to the destination DTE equipment the
information sent by the originating DTE equipment. The originating DTE
equipment can also add layer-2 code to be analyzed by the destination DTE
equipment. The DCE equipment treats this layer as data and passes it along to
the destination DTE equipment as it would any other binary bits.
Layers 3 to 7 (and the DTE-created layer 2) are embedded in the transmission
stream and are meaningful only at the destination DTE equipment. Therefore,
they are shown in the figure as ‘‘user-defined,’’ with no state changes until the
transmission stream reaches its destination.
Page 37
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
Issue 1
August 1997
Page 1-5Protocols
ORIGINATING
DCE
DTE
DTE
RS232C
2DMIASCIIASCII
3-7
DTE
DATA
MODULE
DATA
MODULE
MODEM
ANALOGANALOG1PCMRS232CRS232C
D
I
P
G
O
I
R
T
T
A
L
D
I
P
G
O
I
R
T
T
A
L
USER DEFINED
A
P
N
L
O
A
I
R
L
N
T
O
E
G
PCM
D
I
P
G
O
I
R
T
T
A
L
D
I
P
G
O
I
R
T
T
A
L
A
P
N
O
A
R
L
T
O
G
A
T
P
N
R
O
A
U
R
L
N
T
O
K
G
DESTINATION SYSTEM
MODULE
MODULE
MODEM
MODEM
DCE
DATA
DATA
RS232CRAW BITSDCPDCP 1
MODEM
POOLING
CABLE
DTE
DTE
VOICE GRADE DATAASCIIASCII 2
3-7 USER DEFINED
P
ADUADUDTE
RS232CRS232CADU PROTADU PROT1 RAW BITS
3-7 USER DEFINED
DTE
1
RS232CDS1 FORMATDCP
3-7USER DEFINED
DATA
MODULE
E
O
I
R
A
T
DMIASYNCH ASCIIASYNCH ASCII 2
D
I
P
G
O
I
R
T
T
A
L
RAW BITS
DMIASCII 2
Figure 1-1. Data Transmission States
P
E
O
I
R
A
T
P
D
O
S
R
1
T
DTE
DS1
PORT
Page 38
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
Usage
The following is a list of the protocols when data is t ransmitted to and through the
system. The list is organized by proto c ol layers. Refer to Figure 1-1
Layer-1 Protocols
Layer-1 protocols are used between the terminal or host DTE and the DCE, used
between the DCE equipment and the system port, and used inside the system.
The following layer-1 protocols are used between the DTE equipment and the
DCE equipment. DCE equipment can be data modules, modems, or Data
Service Units (DSUs). A DSU is a device that transmits digital data to a particular
digital endpoint over the public network without processing the data through any
intervening private network switches.
■
RS-232
This protocol is typically used for communicating up to 19.2 kbps
■
RS-449
restrictions and lack of modem control
— A common physical interface used to connect DTE to DCE.
— Designed to overcome the RS-232 distance and speed
Issue 1
August 1997
Page 1-6Protocols
.
■
V.35
— A physical interface used to connect DTE to a DCE. This protocol
is typically used for transmissions at 56 or 64 kbps
The following protocols are used at layer 1 to govern communication between the
DCE equipment and the port. These protocols consist of codes inserted at the
originating DCE and stripped at the port. The DS1 protocol can be inserted at the
originating, outgoing trunk port and stripped at the destination port.
■
Digital Communications Protocol (DCP)
— A standard for a 3-channel
link. This protocol sends digitized voice and digital data in frames at 160
kbps. The channel structure consists of two information (I) channels and
one signaling (S) channel. Each I-channel provides 64 kbps of voice
and/or data communication and the S-channel provi des 8 kbps of
signaling communication between the system and DTE equipment. DCP is
similar to ISDN-BRI
■
Basic Rate Interface (BRI)
— An ISDN standard for a 3-channel link,
consisting of two 64-kbps bearer (B) channels and one 16-kbps signaling
(D) channel. For the implementation of this standard, see
DEFINITY
Communications System and System 75 and System 85 ISDN BRI
Reference
■
Primary Rate Interface (PRI)
, 555-025-103
— An ISDN standard that sends digitized
voice and digital data in T1 frames at 1.544-Mbps or, for countries outside
the United States, in E1 frames at 2.048-Mbps. Layer 1 (physical), layer 2
(link), and layer 3 (network) ISDN PRI protocols are defined in
—
System 75 and 85
DS1/DMI/ISDN-PRI — Reference Manual
AT&T
,
555-025-101. At 1.544 Mbps, each frame consists of 24 64-kbps channels
plus 8 kbps for framing. This represents 23 B-channels plus 1 D-channel.
Page 39
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
The maximum user rate is 64 kbps for voice and data. The maximum
distances are based on T1 limitations. At 2.048 Mbps, each E1 frame
consists of 32 64-kbps channels
■
Analog
■
ADU Proprietary
— A modulated voice-frequency carrier signal
— A signal generated by an ADU. The signal is for
communication over limited distances and can be understood only by a
destination ADU or destination system port with a built-in ADU
■
Digital Signal Level 1 (DS1)
— A protocol defining the line coding,
signaling, and framing used on a 24-channel line. Many types of trunk
protocols (for example, PRI and 24th-channel signaling) use DS1 protocol
at layer 1
■
European Conference of Postal and Telecommunications rate 1 (CEPT1)
— A protocol defining the line coding, signaling, and framing used on a
32-channel line. Countries outside the United States use CEPT1 protocol
Inside the system, data tra n smi ssi o n appear s in one of two forms:
1. Raw digital data, where the physical layer protocols, like DCP, are
stripped at the incoming port and reinserted at the outgoing port.
Issue 1
August 1997
Page 1-7Protocols
2. Pulse Code Modulation (PCM)-encoded analog signals (analog
transmission by a modem), the signal having been digitized by an
analog-to-digital coder/decoder (CODEC) at the incoming port.
Layer-2 Protocols
Layer-2 protocols are given below:
■
8-bit character code —
equipment. Depending on the type of equipment used , the code can be
any proprietary code set.
■
Digital multiplexed interface
the originating DCE and the destination DCE for digital transmission. See
DEFINITY Communications System and System 75 and System 85
DS1/DMI/ISDN PRI Reference
Interface [DMI] Technical Specification,
■
Voice-grade data
DCE for analog transmission
Between the DTE equipment and the DCE
proprietary — Family of protocols between
, 555-025-101; and
Digital Multiplexe d
555-025-204
— Between the originating DCE and the destination
Page 40
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
Protocol States
Table 1-1 summarizes the protocols used at various points in the data
transmissi on stream. See Figure 1-1
Table 1-1. Protocol States for Data Communicatio n
Incoming
Transmiss-
ion Type
DTE to
DCE
OSI
Layer
Protocols DTE t o
.
DCE
Issue 1
August 1997
Page 1-8Protocols
DCE to System
PortInside System
AnalogModem1RS-232, RS-449,
or V.35
28- or 10-bit codevoice-grade dat avoice-grade data
ADU1RS-232ADU proprietaryraw bits
2asynchronous
8-bit code
DigitalData
Module
Digital
Signal
Level 1
(DS1)
1RS-232, RS-449,
or V.35
28-bit codeDMIDMI
1anyDS1PCM or raw bits
28-bit codeDMI or voice-
NOTE:
OSI means Open Systems Int erconnect
PCM means Pulse Code Modulated
DMI means Digital Multiplexed Interface
Both the physical-layer protocol and the Digital Multiplexed Interface (DMI) mode
used in the connection are dependent upon the type of 8-bit code used at layer 2
between the DTE equipment and DCE equipment, as listed in Table 1-2
Table 1-3
.
analogPCM
asynchronous
8-bit code
DCP or BRIraw bits
grade data
DMI
DMI or voice- grade
data
and
Table 1-2. Physical-Layer Protocol Versus Character Code
ProtocolCode
RS-232Asynchronous 8-bit ASCII, and synchronous
RS-449Asynchronous 8-bit ASCII, and synchronous
V.35Synchronous
Page 41
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
Table 1-3. Digital Multiplexed Interface (DMI) Mode Versus
Character Code
DMI Mod eCode
0Synchronous (64 kbps)
1Synchronous (56 kbps)
2Asynchronous 8-bit ASCII (up to 19.2 kbps), and
synchronous
3Asynchronous 8-bit ASCII, and private proprietary
Connectivity Rules
Figure 1-1 implies the following connectivity rules:
Issue 1
August 1997
Page 1-9Protocols
■ Only the DS1 port and the analog trunk port are trunking facilities (all other
ports are line ports). For communication over these facilities, the
destination DCE equipment can be a hemisphere away from the system,
and the signal can traverse any number of intervening switching systems
before reaching the destination equipment.
■ Data originating at any type of digital device, whether DCP or BRI, can exit
the system at any type of digital port — BRI, digital-line, PRI, DS1, and
others; as long as the call destination is equipped with a data module
using the same DMI mode used at the call origin. This is because once the
data enters the system through a digital port, its representation is uniform
(raw bits at layer 1, and DMI at level 2), regardless of where it originated.
■ Although data entering the system through an EIA port has not been
processed through a data module, the port itself has a built-in data
module. In s i de the sys tem, po r t d a ta is ide n tical to digital li ne data. Data
entering the system at a DCP line port can exit at an EIA port. Conversely,
data entering the system at an EIA port can exit at any DCP line port. The
destination data module must be set for Mode-2 DMI communication.
■ Voice-g rade data can be carried over a DS1 facility as long as the
destination equipment is a modem compatible with the originating modem
■ If a mismatch exists between the types of signals used by the endpoints in
a connection (for example, the equipment at one end is an analog
modem, and the equipment at the other end is a digital data module), a
modem-pool member must be inserted in the circuit. When the endpoints
are on different switches, it is recommended that the modem-pool
member be put on the origination or destination system. A modem-pool
Page 42
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
member is always inserted automatically for calls to off-premises sites via
analog or voice-grade trunking. For internal calls, however, the systems
are capable of automatically inserting a modem-pool member.
■ Data cannot be carried over analog facilities unless inside the system it is
represented as a Pulse Code Modulation (PCM)-encoded analog signal.
To do this for data originating at a digital terminal, the signal enters the
system at a digital port and exits the system at a digital port. The signal
then reenters the system through a modem-pool connection (data-module
to modem to analog-port) and exit s the syste m again at an analo g port .
■ Althoug h DS1 is commonly call ed a trunk speed, here it names the
protocol used at layer 1 for digital trunks. Some trunks use different
signaling methods but use DS1 protocol at layer 1 (for example, PRI and
24th-channel signaling trunks).
Disconnect Supervision
Disconnect supervision means the CO has the ability to release a trunk when the
party at the CO disconnects, and the system is able to recognize the release
signal. In general, a CO in the United States provides disconnect supervision for
incoming calls but not for outgoing calls. Many other countries do not provide
disconnect supervision on either incoming or outgoing calls.
Issue 1
August 1997
Page 1-10Protocols
The system must provide the assurance that at least one party on the call can
control the dropping of the call. This avoids locking up circuits on a call where no
party is able to send a disconnect signal to the system. Internal operations must
check to be sure one party can provide disconnect supervision. An incoming
trunk that does not provide disconnect supervision is not allowed to terminate to
an outgoing trunk that does not provide disconnect supervision.
In a DCS environment, an incoming trunk without disconnect supervision can
terminate to an outgoing DCS trunk connecting two nodes. The incoming trunk is
restricted from being transferred to a party without disconnect supervision on the
terminating node.
This is because, through messaging, the terminating node knows the originating
node cannot provide disconnect supervision. This messaging is not possible with
non-DCS tie trunks, and the direct call is denied.
Some two-wire loop start trunks outside the United States provide busy tone
disconnect in place of line signals. For these trunks, an adjunct can be attached
to the trunk to listen for busy or other disconnect tone. When a tone is detected,
the adjunct sends line signals for disconnect to the system.
Administration is provided for each trunk group to indicate whether it provides
disconnect supervision for incoming calls and for outgoing calls.
Page 43
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
Transfer on Ringing
A station or attendant may conference in a ringing station or transfer a party to a
ringing station. When a station conferences in a ringing station and then drops
the call, the ringing station is treated like a party without disconnect supervision.
However, when a station transfers a party to a ringing station, the ringing station
party is treated like a party with disconnect supervision. Two timers (Attendant
Return Call Timer and Wait Answer Supervision Timer) are provided to ensure the
call is not locked to a ringing station.
Conference, Transfer, and Call-Forwar ding
Denial
If a station or attendant attempts to connect parties without disconnect
supervision together, the following is possible:
■
Digital Station or Local Attendant Transfer
transfer the two parties together, the call appearance lamp flutters,
indicating a denial. If transferring to a DCS trunk, the denial may drop the
call since the transfer is allowed and the other system is queried for
disconnect supervision.
Issue 1
August 1997
Page 1-11Protocols
: if a digital station attempts to
■
Analog Station Transfer
parties together by going on-hook, the analog station is no longer on the
call and the transfer cannot be denied.
■
Centralized Attendant Service (CAS) Attendant Transfer
to transfer two parties together by pressing the release key, the release
link trunk is released and the branch attempts a transfer by going on-hook
■
Station Conference/Dropout
conference is allowed since the station has disconnect supervision. When
the station is dropped from the call, the call is dropped since the other
parties do not have disconnect supervision.
■
Station Call Forwarding
without disconnect supervision, the calling party without disconnect
supervision is routed to the attendant
Table 1-4
: if an analog station attempts to transfer two
: if a CAS attempts
: if a station conferences all parties, the
: if a station is call forwarded off-premise to a trunk
lists the various protocols, with applications and maximum limitations.
Page 44
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
Table 1-4. Protocols Used in DEFIN IT Y
Maximum
ProtocolApplications
Data RateMaximum Distance
Issue 1
August 1997
Page 1-12Protocols
DCPDigital switch to data
endpoints
RS-232System to administration
terminal. Data module to
host computer
Data module to printer
Data module for
downloading and
high-speed data transfer
EIA interface
(Data line to ADU)
RS-449Processor Interface to
Processor Interface
SSI715 BCS-2 to Processor
Interface
500 series printers to
Processor Interface
64 kbps5000 f eet (1524 m) for data
3000 feet (915 m) for voice
19.2 kbps
64 kbps
64 kbps
19.2 kbps
9.6 kbps
4.8 kbps
2.4 kbps
1.2 kbps
0.3 kbps
19.2 kbps
9.6 kbps
4.8 kbps
2.4 kbps
56 kbps5000 f eet (1524 m)
50 feet (15.2 m)
17 feet (5.9 m)
17 feet (5.9 m)
2000 feet (610 m)
5000 feet (1524 m)
7000 feet (2130 m)
12,000 feet (3654 m)
20,000 feet (6100 m)
40,000 feet (12200 m)
200 feet (61 m)
400 feet (122 m)
800 feet (244 m)
1600 feet (488 m)
BISYNCProcessor Interface line
controller to host
comput e r fo r termina l
emulation (9.6 kbps)
BX.25Communication interface
to MSA, D C S , ISDN, or
AUDIX
SDCPIDat a module to Processo r
Interface
RS-366Host computer to ACU
Data module to ACU64 kbps
V.35Data module to data
endpoints
2.4 kbps
4.8 kbps
9.6 kbps
9.6 kbps
64 kbps17 fee t (5.9 m)
50 feet (15.2 m)
17 feet (5.9 m)
56 kbps50 fee t (15.2 m)
Continued on next page
Page 45
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
Table 1-4. Protocols Used in DEFIN IT Y — Continued
Maximum
ProtocolApplications
Data RateMaximum Distance
Issue 1
August 1997
Page 1-13Protocols
Category AData modules to terminals
or cluster controller
Data module in ASCII
emulation mode
ISDN-BRICommunication interface
to ISDN-BRI S/T
ISDN-BRI U
ISDN-PRICommunication interface
to ISDN-P R I
NOTE:
ADU means Asynchronous Data Unit
BCS means Business Communicat ions System
MSA means Message Servicing Adjunct
ACU means Automatic Call Unit
64 kbps
9.6 kbps
64 kbps
160 kbps
64 kbps655 fe et (199.3 m) to network
500 feet (152 m)
655 feet (199.3 m) to network
interface or repeater
1310 feet (399.3 m) system to
system
18,000 feet (5486.4 m) from
system to network interface,
and then ~2000 feet to phone
interface or repeater
1310 feet (399.3 m) system to
system
Continued on next page
Transmission Characteristics
The system transmission characteristics comply with the American National
Standards Institute/Electronic Industries Association (ANSI/EIA) standard
RS-464A (SP-1378A). The following tables list some general switch transmission
characteristics.
Page 46
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
Frequency Response
Table 1-5 lists the analog-to-analog frequency response for station-to-station or
station-to-CO trunk, relative to loss at 1 kHz for the United States.
Table 1-5. Analog-to- Analog Frequency Response
Frequency (Hz)Maximum Loss (dB)Minimum Loss (dB)
60—20
2005 0
Issue 1
August 1997
Page 1-14Protocols
300 to
3000
32001.5 -0.5
340030
1-0.5
Table 1-6 lists the analog-to-digital frequency response of the system for station
or CO-trunk-to-digital interface (DS0), relative to loss at 1 kHz for the United
States.
Table 1-6. Analog-to-Digital Frequency Response
Frequency (Hz)Maximum Loss (dB)Minimum Loss (dB)
60—20
2003 0
300 to
3000
32000.75 -0.25
34001.5 0
0.5 -0.25
Page 47
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
Insertion Loss for Port-to-Port; Analog or Digital
Table 1-7 lists the insertion loss in the system for different connection types for
the United States. Table 1-8
Table 1-7. Insertion Loss for the United States
Typical Connecti ons
On-premises to on-premises station6
On-premises to off-premises station3
Off-premises to off -premises station0
On-premises station to 4-wire trunk3
Off-premises station to 4-wire trunk2
Station-to-trunk0
Trunk-to-t runk0
shows the overload and cross-talk characteristics.
Nominal Loss
(dB) at 1 k H z
Issue 1
August 1997
Page 1-15Protocols
Table 1-8. Overload and Crosstalk
Overload level+3 dBm0
Crosstalk loss>70 dB
Intermodulation Distortion
Table 1-9 lists the intermodulation distortion in the system for analog-to-analog
and analog-to-digital, up to 9.6 kbps data
Table 1-9. Intermodulation Distortion
Four-Tone MethodDistortion
Second-order tone products>46 dB
Third-order tone products>56 dB
Page 48
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
Quantization Distortion Loss
Table 1-10 lists the quantization distortion loss in the system for analog port to
analog po rt.
Table 1-10. Quantization Distortion Loss
Analog Port-to-Analog Port
Signal LevelDistortion Loss
0 to -30 dBm0>33 dB
-40 dBm0>27 dB
-45 dBm0>22 dB
Table 1-11 lists the quantization distortion loss in the system for analog port to
digital port and digital port to analog port.
Issue 1
August 1997
Page 1-16Protocols
Table 1-11. Quantization Distortion Loss
Analog Port-to-Digital Port or
Digital Port-to-Analog Port
Signal LevelDistortion Loss
0 to -30 dBm0>35 dB
-40 dBm0>29 dB
-45 dBm0>25 dB
Terminating Impedance: 600 Ohms nominal
Trunk balance impedance (selectable): 600 Ohms nominal or complex Z [350 Ohms + (1
k Ohms in parallel with 0. 215uF)]
Impulse Noise
On 95% or more of all connections, the impulse noise is 0 count (hits) in five
minutes at +55 dBrnC (decibels above reference noise with C-filter) during the
busy hour.
Page 49
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
ERL and SFRL Talking State
Echo-Return Loss (ERL) and Single-Frequency Return Loss (SFRL) performance
is usually dominated by termination and/or loop input impedances. The system
provides an acceptable level of echo performance if the ERL and SFRL are met.
Station-to-stationERL should meet or exceed 18 dB
SFRL should meet or exceed 12 dB
Issue 1
August 1997
Page 1-17Serv i c e C odes
Station to 4-wire trunk
connection
Station to 2-wire trunk
connection
4-wire to 4-wire trunk
connection
Peak Noise Level
Analog to analog — 20 dBrnC (decibels above reference noise with C-filter)
Analog to digital
Digital to analog
Echo Path Delay
Analog port to analog port — < 3 ms
Digital interface port to digital interface port — <
ERL should meet or exceed 24 dB
SFRL should meet or exceed 14 dB
ERL should meet or exceed 18 dB
SFRL should meet or exceed 12 dB
ERL should meet or exceed 27 dB
SFRL should meet or exceed 20 dB
— 19 dBrnC
— 13 dB rnC
2 ms
Service Codes
Service codes (for the United States only) are issued by the Federal
Communications Commission (FCC) to equipment manufact urers and
registrants. These codes denote the type of registered terminal equipment and
the protective characteristics of the premises wiring of the terminal equipment
ports.
Private line service codes are as follows:
■ 7.0Y — Totally protected private communications (microwave) systems
■ 7.0Z — Partially protected private communications (microwave) systems
■ 8.0X — Port for ancillary equipment
■ 9.0F — Fully protected terminal equipment
Page 50
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
■ 9.0P — Partially protected terminal equipment
■ 9.0N — Unpro tected terminal equipm ent
■ 9.0Y — Totally protected terminal equipment
555-230-127
The product line service code is 9.0F indicating it is terminal equipment with fully
protected premises wire at the private line ports.
Facility Interface Codes
A Facility Interface Code (FIC) is a five-character code (United States only) that
provides the technical information needed to order a specific port circuit pack for
analog private lines, digital lines, MTS lines, and WATS lines.
Issue 1
August 1997
Page 1-18Facilit y Int erface Codes
Page 51
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
555-230-127
Table 1-12 through Table 1-14 list the FICs. Included are service order codes,
Ringer Equivalency Numbers (RENs), and types of network jacks that connect a
line to a rear panel connector on a carrier.
Table 1-12. Analog Private Line and Trunk Port Circuit Packs
Issue 1
August 1997
Page 1-19Multimedia Interface (MMI)
Service
Circuit PackFIC
TN742 and TN747B Off-Premises
Station Port, and TN746B Off-Premises
Station Port or On-Premises Station port
TN760/B/C/D Tie Trun kTL31M9.0FRJ2GX
0L13C9.0FRJ21X
Order Code
Network
Jack
Table 1-13. Digital Trunk Port Circuit Packs
Service
Circuit Pack FIC
TN1654 and TN574 DS1 Convert er; TN722B
DS1 Tie trunk; and TN767 and TN464 DS1
Interface
04DU9B,C6.0PRJ48C
Order Code
Table 1-14. MTS and WATS Port Circuit Packs
Ringer
Circuit Pack FIC
Equivalen cy
Number (REN)
Network
Jack
Network
Jack
and
RJ48M
TN742 and TN746B Analog Line02LS2NoneRJ21 and
TN747B Central Office Trunk02GS21.0ARJ21X
TN753 DID Trunk02RV2-T0,0BRJ21X
TN790 Processor02LS21.0ARJ21X
TN1648 System Access and
Maintenance
Multimed ia I nt er face (M MI )
The Multimedia Interface handles the following protocols:
RJ11C
02LS20.5ARJ21X
Page 52
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Maintenance Architecture
1
■ International Tele com mun ications Union (IT U) H.221 — Includes H.230,
555-230-127
H.242, H.231, and H.243 protocol
■ American National Standards Institute (ANSI) H.221 — Includes H.230,
H.242, H.231, and H.243 protocol
■ BO ND I N G ( B a ndw idth On Dem an d INoperabilit y Gr ou p) M o de 1
■ ESM HLP HDLC Rate Adaptation
The Vistium Personal Conferencing System is supported either through the
8510T BRI terminal or directly through the Vistium TMBRI PC board.
Using the W o rld Class Core ( W C C) BR I int er face, most desk t op m u lt imedia
applications are supported through the Personal Computer’s BRI interface.
Issue 1
August 1997
Page 1-20Multimedia Interface (MMI)
Page 53
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Circuit Packs and Power
2
2
Circuit Packs and Power
This chapter discusses the hardware configurations contained within and
supported by the DEFINITY Systems. Where appropriate, detailed information
down to the circuit pack level is provided. This chapter also discusses the power
sources required to enable the various components within the system.
555-230-127
Issue 1
August 1997
Page 2-1Circuit Packs
2
Circui t Pa c ks
The following table list all circuit packs supported by DEFINITY Release 5
systems. For information concerning vintages and current versions, see
Reference Guide for Circuit Pack Vintages and Change Notices
published periodically as a special edition of the
For more information concerning which circuit packs are needed for different
environments and locales, see the Application Notes section of
Enterprise Communications Server Release 5.4 Administration and Feature
Description
Table 2-1
Reference Guide for Circuit Pack Vintages and Change Notices
that pertain to your system.
which is
AT&T Technical Monthly
DEFINITY
.
lists circuit packs by Apparatus Code, Name, and Type. See the
for circuit packs
.
Page 54
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Circuit Packs and Power
2
Table 2-1. Circuit packs and modules
Apparatus
CodeNameType
631DA1AC Power UnitPower
631DB1AC Power UnitPower
644A1DC Power UnitPower
645B1DC Power UnitPower
649ADC Power UnitPower
676BDC Power SupplyPower
982LSCurren t LimiterPower
CFY1BCurrent LimiterPower
CPP1Memory Expansion Control
TN2149Analog LinePo rt
TN2180Analog LinePo rt
TN2181Digital Line 2-Wire DCPPort
TN2182/BTone-Cl ock -Tone Detector and Call Classif ierControl
TN2183Analog LinePo rt
TN2184DIOD TrunkPort
TN2198ISDN-BRI 2-Wire U InterfacePort
TN2199Central Office TrunkPort
TN2202Ring GeneratorPower
TN2224Digi tal Line, 24- Port, 2-Wire DCPPort
UN330BDuplication InterfaceControl
UN331BProcessorControl
UN332Mass Storage/Network ControlControl
WP-90510AC Power Supply (Compact Single-Carrier Cabinet)Power
WP-91153AC Power Supply (Single-Carrier Cabinet)Power
Continued on next page
Page 58
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Circuit Packs and Power
2
555-230-127
Power
There are two basic powering options available with the Release 5si systems.
These options include AC and DC. The cabinets and their associated power
supplies can be powered by 120/208 volts AC either directly or from a Universal
Power Supply (UPS) system. Alternatively, the cabinets and their power supplies
may be powered by -48 volts DC from a battery power plant.
The Release 5vs system requires between 80 and 264 or between 90 and 132
volts AC. The system can be powered directly or from the WP-90510 power
supply. The DC power option is not available with this system.
Except for the Release 5vs system, each control cabinet in an AC-powered
system has an internal batte ry th a t provides a short term holdover to protect the
system against short power interruptions. This method is known as the Nominal
Power Holdover Strategy. The battery is connected so that it automatically
provides power if the AC service fails. The time and extent of the holdover varies
according to the type of cabinet and to whether or not the system has a
duplicated control complex.
Issue 1
August 1997
Page 2-6Power
Table 2-2
summarizes the response to the interruption of power service in
systems without an internal holdover battery.
Table 2-2. Response to Power Service Interruption (without Internal
Holdover Battery)
Cabinet Power
Interruption
-48 volt DC external power
or multicarrier cabinet with
UPS, no internal battery.
Less Tha n Power
Supply Dec ay
None on system, some
impact on 48-volt
powered circuits.
Greater Than Power
Supply Decay
All calls dropped,
system reloads.
The next two tables indicate various responses to the interruption of power
service in DEFINITY Systems equipped with an internal holdover battery.
Table 2-3
provides a summary of holdover times. Table 2-4 indicates the types of
cabinet power interruption based on power holdover durations.
Page 59
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Circuit Packs and Power
2
555-230-127
Issue 1
August 1997
Page 2-7Power
Table 2-3. Response to Power Service Interruption with an Internal Holdover Battery
1. The holdover times listed are in effect if the EPN contains a TN775 maintenance circuit pack.
However, if the EPN c ont ains a TN77 5B mai ntenance c ircui t pack, t he holdov er ti me for t he enti re
cabinet is 10 seconds , and the holdover time for the control carrier is 10 minutes.
Table 2-4.Types of Ca bine t Po w er Inter ruption
Longer Holdover than
System and
Cabinet
Shorter Holdover
Than Entire
Cabinet
Entire Cabinet, Shorter
Holdover than Co ntrol
Carrier
Longer Holdover
Than Control
Carrier
PPN SCCNo call s droppe dAll calls droppedS ystem reloads
EPN SCCNo call s droppe dAll calls droppedS ystem reloads
NOTE:
When EPN power is interrupted for greater than the cabinet holdover but
less than the control carrier holdover, calls in the control carrier are held for
the duration of the interruption but are dropped when power is restored.
Single-Carrier Cabinets
In single-carrier cabinets, there is no internal AC wiring or distribution and no
software interacti o n with th e powe r system. The power supplies themselves take
about 250 milliseconds for the voltages to drop below limits.
The control cabinet that houses the Switch Processing Element (SPE) is the only
cabinet that has an internal battery reserve. All other control cabinets and port
cabinets have the 250 millisecond power supply deca y de lay, after which all
connections and links associated with the cabinets are dropped.
Page 60
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Circuit Packs and Power
2
555-230-127
The SPE control cabinet has a battery that furnishes power to the processor
memory complex for a minimum of two minutes if the battery is fully charged. This
battery is recharged after power is restored, but the charging process is not
monitored by the system. The cabinet is not able to detect AC power loss, and it
notices only a DC power output failure as the power supply output decays.
The memory contents are preserved, and the processor continue s operating
during the two minute period. However, the tone-clock circuit pack is not held
over, and as a result, no connections are possible. The battery does not supply
all the voltages necessary for the internal modem circuit on the processor circuit
pack. As a result, no call is originated to INADS, and the switch cannot answer
any calls. Thus, the switch cannot report any internal or external alarms during
this period. After two minutes (depending on the condition of the battery), the
processor and memory are lost, and the system is totally inactive.
If power is restored in less than 250 milliseconds, no calls are dropped. If power
is restored between 250 milliseconds and two minutes, all calls are dropped, and
memory is maintained. However, since the tone-clock was lost, the system
undergoes a reset once the AC restoral process clears all calls and the alarm log
(in which errors are retained). The switch keeps a record of the restart in the error
log, but it might not detect a power error if the outage is between 1/4 of a second
and one minute, during which time only a loss of clock and not a loss of the
power failure that caused the loss of clock is logged. After one minute, a power
error is logged. If the outage exceeds the battery holdover interval, the error logs
and alarm logs are lost (since they cannot be saved to tape). Depending on the
size of the system, it can take up to one minute to restore service to the ports.
After a power outage of two minutes following the restoral of AC power, the
system re-initializes from the tape. It takes about 10 minutes to restore service.
Again, if the customer has frequent power outages or critical service needs, an
external UPS or DC power system should be considered.
Issue 1
August 1997
Page 2-8Power
NOTE:
For more power control information, refer to AC-POWER, DC-POWER, and
POWER maintenance objects.
Page 61
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
3
Management Terminals
555-230-127
General
Issue 1
August 1997
Page 3-1General
3
Maintenance personnel can use the management terminal to initiate the same
tests that the system initiates. Test results display on the terminal screen. This
chapter illustrates these terminals, explains how to use them, and identifies the
typical maintenance tasks that can be performed from them.
Management Terminals
The maintenance interface for the system technician is the management terminal.
These terminals may be referred to as an
The following terminals are supported as administration terminals:
■ 715 BCS
■ 2900/715 BCS
■ 715 BCS-2
In a standard reliability system, the terminal connects to the Processor circuit
pack. In the PPN of a high or critical reliability system , the administration terminal
connects to the Duplication Interface circuit pack in the PPN. In the EPN of a
standard reliabili ty system or of a high or critical reliability system, the
administration terminal connects to the Maintenance circuit pack in the EPN.
Duplication Interface circuit pack A controls and monitors the same environment
leads as the Maintenance/Tape Processor in a PPN system without high or
critical reliability. Duplication Interface circuit pack A also supports the serial
channel to the terminal in a PPN for a high or critical reliability system. The
terminal connects to Duplication Interface circuit pack A via a connector, labeled
administration terminal
.
Page 62
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
DOT (Duplication Option Terminal), on the back of cabinet A. At any time, the
terminal may be disconnected from the Duplication Interface circuit pack A and
connected directly to the active processor circuit pack by attaching the terminal
to the connector labeled TERM. This connection should be made only if the
terminal fails to function, since a problem with the Duplication Interface circuit
pack A may be present.
Typical tasks that can be performed at the terminal are shown below.
■ Display Error and Alarm logs
■ Test circuit packs
■ Test system functions
■ Busyout and release system equipment
■ Reset the system
■ Monitor the system
■ Chec k status of maintenanc e objects
■ Chec k system translations
Issue 1
August 1997
Page 3-2Management Terminals
Most maintenance functions performed at the local administration terminal can
also be done remotely at the INADS (Initialization and Administration System).
Terminal Keyboard
The keyboard is equipped with cursor keys, editing keys, and transaction keys.
The three types of keys are described here.
Cursor Keys:
pages on a screen form. The cursor must be positioned on a field before the user
can add or change information in that field.
Editing Keys:
used to erase the character at the current cursor position. The cursor moves one
position to the left each time the key is pressed. If the cursor is at the first position
of the data entry field, it erases the character at the first position.
pressed simultaneously with the
form. The cursor must be positioned at the field the user wants to clear before
Clear is pressed.
Transaction Keys:
CANCEL is used to erase a form or command. Once the key is pressed, the
system returns the use r to the command (tasks request) level and asks for a n ew
command.
system’s memory.
entered into the field associated with the current cursor position. The system
displays all the permissible entries the user can input for that field. This key can
be pressed at the ”enter command” level to obtain a list of all commands.
Cursor keys are used to move the cursor between fields and
Two editing ke ys, BACKSPACE and Clear, are provided. BACKSPACE is
Clear when
Shift is used to clear all data in a field on a screen
Three transaction keys, Cancel, Enter, and Help, are provided.
Enter is used to store the data entered on a screen form in the
Help displays information on the type of data that can be
Page 63
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
System Login Procedure
Forced Password Aging and Administrable
Logins
Release 5 and later releases provide enhanced login/passw ord security by
adding a security feature that allows users to define their own logins/passwords
and to specify a set of commands for each login. The system allows up to 11
customer logins. Each login name can be customized and m ust be made up of
from 3 to 6 alphabetic/numeric characters, or a combination of both. A password
must be from 4 to 11 characters in length and contain at least 1 alphabetic and 1
numeric symbol. Password aging is an optional feature that the super-user
administering the logins can activate.
NOTE:
If several users are logging in and out at the same time, a user may see the
message “Transient command conflict detected; please try later”. After the
“users” have completed logging in or out, the terminal is available for use.
Issue 1
August 1997
Page 3-3System Login Procedure
The password for each login can be aged starting with the date the password
was created, or changed, and continuing for a specified number of days (1 to
99). The user is notified at the login prompt, 7 days before the password
expiration date, that the password is about to expire. When the password expires
the user is required to enter a new password into the system before logging in. If
a login is added or removed, the “Security Measurement” reports are not
updated until the next hourly poll, or a clear measurements security-violations
command is entered. Once a non-super-user has changed the password, the
user must wait 24 hours to change the password again.
Security is enhanced by providing a logoff notification screen to a system
administrator at log off while either the facilit y test call or remote access features
are still administered. The administrator can be required to acknowledge the
notification before completing the logoff process. Logoff notification is
administered on the Login Administration screen.
Release 5 and later releases are delivered to the customer with one customer
“super-user” login/password defined. The customer is required to administer
additional login/passwords as needed. The super-user login has full customer
permissions and can customize any login created.
Login permissions for a specified login can be set by the super-user to block any
object that may compromise switch security. Up to 40 administration or
maintenance objects commands can be blocked for a specified login in.
Release 5 and later releases commands are grouped into three comma nd
categories. Each of the three command categories has a group of command
subcategories listed under them, and each command subcategory has a list of
command objects that the commands acts on. A super-user can set a users
Page 64
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
permissions to restrict or block access to any command in these categories. The
three main categories are:
■ Comm on Commands
— Display Admin. and Maint. Data
— System Measurements
■ Admini stration Comma nds
— Administer Stations
— Administer Trunks
— Additional Restrictions
— Administer Features
— Administer Perm is s ion s
■ Maintenance Commands
— Maintain Stations
— Maintain Trunks
Issue 1
August 1997
Page 3-4System Login Procedure
To Log In
— Maintain Systems
— Maintain Switch Circuit Packs
— Maintain Process Circuit Packs
These categories are displayed on the Command Permissions Categories form.
1. Enter your login name and password on the login and password screen.
If your password has expired, you see the message:
Your password has expired, enter a new one.
Reenter current password:
Page 65
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
Issue 1
August 1997
Page 3-5System Login Procedure
Login: telmgr
Password:
Your Password has expired, enter a new one.
Reenter Current Password:
New Password:
Reenter New Password:
Figure 3-1. Password Expiration Screen
The Password Expiration screen displays when you log in. See Figure 3-1
password is expired, you are prompted to enter a new password. If your
password is within 7 days of the expiration date, you see:
WARNING: Your password will expire in X days
To Logoff
To logoff, enter “logoff” at the command prompt. You will receive a logoff screen
if any of the following is true. If either a or b (see below) is true and an
acknowledgment is required, or if any of c, d, or e is true, you need to respond to
the “Proceed with Logoff?” prompt on the logoff screen. See Figure 3-2. The
response is defaulted to “n”; you will need to enter “y” to override the default.
. If y our
a. If Facility Test Call Notification has been enabled for your login (see
Adding Customer Logins and Assigning Initial Passwords).
b. If Remote Access Notification has been enabled for your login (see
Adding Customer Logins and Assigning Initial Passwords).
c. If Alarm Origination is disabled.
d. If any active major or minor alarm is active.
e. If any resource is busied out.
!
CAUTION:
To leave the Facility Test Call administered after you logoff poses a
significant security risk.
!
CAUTION:
To leave the Remote Access feature administered after logging off poses a
significant security risk if you are using the feature in conjunction with the
Facility Te st C a ll fe a ture .
Page 66
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
!
CAUTION:
555-230-127
No alarms report through the INADS interface if Alarm Origination is
disabled.
!
CAUTION:
A busied out resource is one that is out of service. Be sure to verify if a
busied resource needs to be released or if the resource should remain
busied out.
Facility Test Call Administered
Remote Access Administered
Alarm Origination is currently disabled.
Active major or minor alarm detected; be sure to resolve it.
*** Busied out resource detected; verify if release is needed! ****
Proceed With Logoff: [n]
Issue 1
August 1997
Page 3-6System Login Procedure
Figure 3-2. Logoff Screen
To Display a Login
1. Enter the command displ a y login [ l ogin name ] and press Enter.
The system displays the requested login’s:
■ Name
■ Login type
■ Service level
■ Disable following a security violation value
■ Access to Inads Port value
■ Password aging cycle length
Page 67
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
■ Facility test call notification and acknowledgment
■ Remote access notification and acknowledgment
To List Logins
1. Enter the command list logins.
The system displays the followi n g inf or mati on for all curr ent login s:
■ Name
■ Service level
■ Status (active, inactive, disabled, svn-disabled, void)
■ Password aging cycle length
The system displays only those logins wit h the same, or lower, se rvi ce
level as the requestor.
To Remove a Login
Issue 1
August 1997
Page 3-7System Login Procedure
1. Enter the command remove login [login nam e ].
The system displays the Login Administration form.
2. Press the
ENTER key to remove the login, or press Cancel to exit the
remove login procedure without making a change.
To Test a Login
1. Enter your login name at the login prompt.
2. After the user enters the correct login name and password and the login is
administered correctly, the system displays the command line interface.
Administering Customer Logins and Forced
Password Aging
Adding Customer Logins and Assigning Initial
Password
To add a customer login you must be a super-user, have administrative
permissions, and:
1. En te r the add login [name] command to access the Login Administration
form.
2. Enter your super-user password in the Password of Login Making Change
field on the Login Administration form.
The 3- to 6-character login name (characters 0-9, a-z, A-Z) entered with
the add login [name] command is displayed in the Login’s Name field.
Page 68
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
3. Enter “custom er” in the Login Type field. The system defau lt for the Login
Type field is “customer.” The maximum number of customer logins of all
types is 11.
4. Enter super-user or non-super-user in the Service Level field. Default is
none-super-user.
■ “super-user” gives access to the add, change, display, list, and
remove commands for all customer logins and passwords. The
super-user can administer any mix of super-user/non-super-user
logins up to a total of ten additional system logins.
■ “non-super-user” permissions are limited by restrictions specified
by the super-user when administering the non-super-user login. A
non-super-user can change his/her password with permission set
by the super-user, however once a password has been changed
the non-super-user must wait 24 hours before changing the
password again. A non-super-user cannot change other user
passwords, login characteristics, or permissions.
5. Enter “y” in the Disable Following a Security Violation field to disable a
login following a login security threshold violation,. This field is a dynamic
field and only appears on the Login Administration form when the SVN
Login Violation Notification feature is enabled. The system default for the
Disable Following a Security Violation field is “y.”
Issue 1
August 1997
Page 3-8System Login Procedure
6. Enter “y” in the Access to INADS Port? field to allow access to the remote
administration port,. This field only displays if Acct. has first enabled
customer super-user access to the INADS Remote Administration Port.
Default is “n”.
7. Enter a password for the new login in the Login’s Password field. A
password must be from 4 to 11 characters in length and contain at least 1
alphabetic and 1 numeric symbol. Valid characters include num bers,
and!&*?;’^(),.:- (the system will not echo the password to the screen as
you type).
8. Re-enter the password in the Login’s Password field. The system will not
echo the password to the screen as you type.
9. Enter the number of days (1 to 99) from the current day, that you want the
password to expire, in the Password Aging Cycle Length field. If a you
enter a blank in this field, password aging does not apply to the login.
10. Deci de w h et h er or not to le av e t he def a ult o f ye s (“y”) in the F acility Test
Call Notification? field. If “y” is selected, the user receives notification at
logoff that the facility test call feature access code is administered. If you
do not want the notification to appear, set the field to “n”.
!
CAUTION:
Leaving The facility Tes t Call ad mi nis tere d after logg ing off pose s a
significant security risk.
Page 69
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
11. Decide w he t he r o r not to lea v e t h e de f au lt of y es (“y” ) in the F acility Test
Call Notification Acknowledgment Required field. If “y” is selected, the
user is required to acknowledge that they wish to logoff while Facility Test
Call is still administered. If you do not want to force the user to
acknowledge, set the field to “n”. This field appears only if the Facility Test
Call Notification field is set to 'y”
12. Decide whether or not to leave the default of yes (“y”) in the Remote
Access Notification? field. If “y” is selected, the user receives notification
at logoff that remote access is still administered. If you do not want the
notification to appear, set the field to “n”.
!
CAUTION:
To Leave Remote Access feature administered after logging off
poses a significant security risk if you are using the feature in
conjunction with the Facility Test Call feature.
13. Decide whether or not to leave the default of yes (“y”) in the Remote
Access Acknowledgment Required? field. If “y” is selected, the user is
required to acknowledge that they wish to logoff while remote access is
still administered. If you do not want to force the user to acknowledge, set
the field to “n”. This field appears only if the Facility Test Call Notification
field is set to 'y”.
Issue 1
August 1997
Page 3-9System Login Procedure
Password of Login Making Change:
LOGIN BEING ADMINISTERED
Login’s Name:xxxxxxx
Login Type:
Service Level:
Disable Following a Security Violation?
Facility Test Call Notification? y Acknowledgment Required? y
Remote Access Notification? y Acknowledgment Required? y
LOGIN ADMINISTRATION
Access to INADS Port?
Screen 3-1. Login Administration
Page 70
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
Changing a Login’s Attributes
To change a customer login’s attributes you must be a super-user, have
administrative permissions (specifically, the Administration Permission field must
be set to “y” for the super-user), and:
1. En te r the change login [name] comm and to access the Login
Administration form.
2. Enter your super-user password in the Password of Login Making Change
field on the Login Administration form. The 3- to 6-character login name
(characters 0-9, a-z, A-Z) entered with the change login [nam e]
command is displayed in the Login’s Name field.
3. Enter “customer” in the Login Type field.
4. Enter “super-user” or “non-super-user” in the Service Level field.
NOTE:
You cannot change your own service level.
5. To disable a login following a login security threshold violation, enter “y” in
the Disable Following a Security Violation field. This field is a dynamic field
and only appears on the Login Administration form when the SVN Login
Violation Notification feature is enabled.
Issue 1
August 1997
Page 3-10System Login Procedure
6. To allow access to the remote administration port, enter “y” in the Access
to INADS Port? field. This field will only display if Lucent Technologies has
first enabled customer super-user access to the INADS Remote
Administration Port.
7. Enter a password for the new login in the Login’s Password field. A
password must be from 4 to 11 characters in length and contain at least 1
alphabetic and 1 numeric symbol. Valid characters include num bers,
and!&*?;’^(),.:- (the system will not echo the password to the screen as
you type).
8. Re-enter the password in the Login’s Password field. The system will not
echo the password to the screen as you type.
9. Enter the number of days (1 to 99) from the current day, when you wish the
password to expire, in the Password Aging Cycle Length field. If a blank is
entered in this field, password aging does not apply to the login.
Page 71
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
Administering Login Command Permissions
Users with super-user permissions can set the permissions of the logins they
create. The Command Permissions Categories form displays fields to which a
user with super-user permissions can give or limit access. These commands are
divided into three categories:
■ Comm on Command
■ Admini stration Comma nds
■ Optional M aintenance Commands
Each of the three main categories have subcategories listed under them that
when set to a “y” give permission to use the command sets associated with that
category. When the Command Permissions Categories form is displayed for a
login, the subcategories fields appear with the fields set to give the login full
permissions for that login type. The super-user administering login permissions
can set any of these field to deny access to a command category for the
specified login. If the super-user making the assignments has full super-user
permissions and would like to limit permissions for a category, the super-user
can do so by entering “y” in the Additional Restrictions field located under the
Administration Category section of the Command Permissions Categories form.
Issue 1
August 1997
Page 3-11System Login Procedure
Refer to the Command Permissions Form Entries Tables at the end of t hi s s ection
for a list of command Objects and Actions by:
■ Display Administration and Maintenance
■ Admini ster Features
■ Admini ster Permissions
■ Adm inister Stations
■ Admini ster Trunks
The information is the tables will help you to establish command permissions for
user logins.
To administer command permissions, log in as super-user and:
1. Access the Command Permissions Categories form by entering change permiss io ns l ogi n [ lo gi n name]. When the form is displayed for a login,
the default permissions for that “login type” are shown. The super-user
administering the login can change a “y” to “n” for each subcategory field.
2. Select a category for the login and enter “y” in each field where
permission to perform an administrative or maintenance action is needed.
The command object you select must be within the permissions for the
login type you are administering.
If the Maintenance option is set to “y” on the Customer Options form, the
super-user can enter “y” in the Maintain Switch Circuit Packs? or Maintain
Process Circuit Packs fields.
Page 72
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
3. A super-user with full super-user permissions (super-user administering
the login cannot have the Additional Restrictions field set to “y” for his/her
own login) can restrict additional administrative or maintenance actions for
a specified login by entering “y” in the Additional Restrictions field on the
Command Permission Categories form. Enter the additional restrictions for
a login in the Restricted object list fields on the Command Permission
Categories Restricted Object List form. You can enter up to 40 command
names (object names) to block actions associated with a command
category for a specified login.
Page 1 of 3
COMMAND PERMISSION CATEGORIES
Login Name: Sup3ru
COMMON COMMANDS
Display Admin. and Maint. Data? y
System Measurements? _*
ADMINISTRATION COMMANDS
Administer Stations? y Administer Features? y
Administer Trunks? y Administer Permissions? y
Additional Restrictions? n
Issue 1
August 1997
Page 3-12System Login Procedure
MAINTENANCE COMMANDS
Maintain Stations? n Maintain Switch Circuit Packs? n
Maintain Trunks? n Maintain Process Circuit Packs? n
Maintain Systems? n
Screen 3-2. Command Permission Categories (Page 1 of 3)
*This field only displays on Release 5vs and Release 5si + memory systems.
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
Issue 1
August 1997
Page 3-14System Login Procedure
Table 3-1. Command Permissions Form Entries — Display Administration and
Maintenance — Continued
Action
Object
ChangeDisplayListMonitorRemoveStatus
alternate-frlX
analog -testcallX
announcementsX
ars anal ysisXX
ars anal ysisX
ars digit-conversionX
ars digit-conversionX
ars route-chosen X
ars-tollX
attendantXX
bcms agentX
bcms login ID sX
bcms sp litX
bcms trunkX
bcms vdnX
boardX
bri-portX
bridged-extensio nsX
bullet in-boardX
button- lo cation-acaX
cabinetXX
call-forwardin gX
call-screeningX
capacityX
card-mem (MIPS Only)XX
cdr-linkXX
circuit-packsX
cleared-alarm-notifX
communication-interface hop-channelsXX
communi cation-interface linksX
Tes
t
Continued on next page
Page 75
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
August 1997
Page 3-15System Login Procedure
Table 3-1. Command Permissions Form Entries — Display Administration and
Maintenance — Continued
Action
Object
ChangeDisplayListMonitorRemoveStatus
communi cation-interface proc-ch annelsXX
config ur a tio n al lX
config ura t io n bo ardX
config ur a tio n ca r rie rX
config ur a tio n co ntrolX
config ura t io n ne tworkX
config ur a tio n so ftwareX
config ur a tio n stationX
config ura t io n tru nkX
console-parametersX
corXX
cosX
coverage answer-groupXX
coverage groupsX
coverage pathXX
customer-alarmX
data-moduleXXXX
dialplanX
digit-absorptionX
display-formatXX
do-not-disturb groupX
do-not-disturb stationX
ds1XX
dsp-msg-auto-wakeupX
dsp-msg-call-identifierX
dsp-msg-date-timeX
dsp-msg-lwcX
dsp-msg-mctX
dsp-msg-miscellaneousX
dsp-msg-property-mgmtX
Issue 1
Tes
t
Continued on next page
Page 76
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
Issue 1
August 1997
Page 3-16System Login Procedure
Table 3-1. Command Permissions Form Entries — Display Administration and
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
Issue 1
August 1997
Page 3-17System Login Procedure
Table 3-1. Command Permissions Form Entries — Display Administration and
Maintenance — Continued
Action
Object
ChangeDisplayListMonitorRemoveStatus
listed-directory-numbersX
loginX
login (MI PS Only )X
login-i dsX
maintenanceX
marked-portX
mct-gro up - ex te ns io nsX
mct-historyX
meas-selection coverageX
meas-selection principalX
meas-selection route-patternX
meas-s election trunk-gr oupX
meas-selection wideband-trunk-grpX
meas ure me nts security-viola ti ons detailX
meas ure me nts security-viola ti ons
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
August 1997
Page 3-18System Login Procedure
Table 3-1. Command Permissions Form Entries — Display Administration and
Maintenance — Continued
Action
Object
ChangeDisplayListMonitorRemoveStatus
pgateXX
pickup-groupXX
pktX
pmsX
pms-downX
pms-linkX
pms-logX
pncX
portXX
stationXXX
svn-button-locationX
suspend-alm-origX
synchronizationXXX
sys-linkXX
systemX
system 1 s t-cabinetX
system 2 nd-cabinetX
system 3rd-cabinetX
system a ll-cabinetsX
system connX
system customer-optionsX
system featuresX
system-maintenanceX
system-parameters cdrX
system-parameters country-optionsX
system-parameters hospitalityX
system-parameter s securityX
tdmX
term-ext-groupXX
terminal-parameters 603/302B1X
Issue 1
Tes
t
Continued on next page
Page 79
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
Issue 1
August 1997
Page 3-19System Login Procedure
Table 3-1. Command Permissions Form Entries — Display Administration and
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
Table 3-4. Command Permissions Form Entries — Administer Trunks
Issue 1
August 1997
Page 3-21System Login Procedure
Object
Action
AddChangeDisplayDuplicateRemove
aar analysisX
aar digit-conversionX
access-endpointXXXX
announcementsX
ars analysisX
ars digit-conversionX
ars tollX
digit-absorptionX
meas-selection route-patternX
meas-selection trunk-groupX
meas-selection wideband-trunk-grpX
modem-poolXXX
personal-CO-lineXXX
pri-endpointXXXX
remote-accessXX
rhnpaX
route-patternX
time-of-dayX
tollX
trunk-groupXXX
Testing a Login
1. Enter your login name at the login prompt.
Login: telmgr
Password:
Screen 3-5.Login Pro mpt Fo rm
Page 82
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
After the user enters the correct login name and password and the login is
administered correctly, the system displays the command line interface.
To log into the system, do the following:
1. Turn on the administration terminal. Verify that the screen displays:
login:
Issue 1
August 1997
Page 3-22System Login Procedure
2. Enter your login name, then press
Enter. Verify that the screen displays:
password:
3. Enter your password, then press
Enter.
For security reasons, the password is not displayed as you type it. The
system verifies that a valid login and password name were entered. If an
invalid login or password name was entered, the screen displays:
login incorrect:, and you must repeat the procedure.
If the system recognizes the login and password name, verify that the
screen displays the software version.
4. For your terminal type, complete one of the following:
Terminal Type (Enter 513, 715, VT220, 4410, or 4425): [513]
a. If the terminal is a 513 BCT, press Enter. The 513 in brackets [513] is
the system default terminal.
b. If the terminal is a 610 BCT or a 615 MT that has a 513 emulation
cartridge, press
Enter.
c. If the terminal is a 610 BCT or a 615 MT that does not have a 513
emulation cartridge, enter 4410 and press
Enter.
d. If the terminal is any other of the types listed, enter the terminal type
and press
Enter.
5. You can deactivate INADS alarm origination whenever you log in as craft.
After you supply the terminal type information requested, the system
displays the following if alarm origination is activated on the Maintenance
System-Parameters screen:
NOTE:
Unless you are in a special situation, please reduce unnecessary
trouble tickets by always answering “y” to the following prompt to
suppress Alarm Origination.
Suppress Alarm Origination: [y]
The default answer is yes. If you do NOT wish to suppress alarm
origination, enter no. Any other entry defaults to yes. The test inads-link
command works regardless of whether you have overridden INADS alarm
origination.
6. Verify that the screen displays:
enter command:
Page 83
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
You may enter the desired command, such as display station xxxx or
Help to obtain the list of permissible commands.
press
Command Line Details
After a successful login, the administration terminal displays enter command:
and waits for entry of a command.
A command is made up of multiple words that are typed on the keyboard and
that instruct the system to perform a particular task. The system’s command
structure follows the format: Action, Object, and Qualifier.
Action
The first word entered is the
example, test, display, or reset).
. It specifies the operation to be done (for
Issue 1
August 1997
Page 3-23System Login Procedure
The second word entered is the
action (for example, station, trunk group, or hunt group).
The third word(s) entered is/are the
or digits used to further identify or complete the Object. Depending on the Object
used, a Qualifier may or may not be used.
An example of a command line used to do a short test twice on a station with the
extension number 1212 is:
Action,
Spaces separate the Action, Object, and Qualifier on the command lin e.
Screen Forms
After the user completes a command line, the terminal displays the appropriate
screen form(s). Screen forms are system-generated forms that are formatted to
allow easy entry of translation data.
Screen forms enable the user to change the translations of the system by typing
parameters on the keyboard. Screen forms also allow system technician to
display errors and alarms. Each screen form consists of a title, page number,
body area, and a help and error message line. Specific screen forms exist for
each type of administrable function.
station
is the Object, and
Object
test station 1212 short r 2
. It specifies the object to receive the
Qualifier
. The Qualifier is one or more words
. In this example,
1212 short r 2
is the Qualifier.
test
is the
NOTE:
Command line words do not have to be completely spelled out. All that is
required is to type enough letters to make the word unique.
DEFINITY Enterprise Communications Server Release 5.4 Administration and
Feature Description
contains detailed information and examples of the screen
forms generated by the system.
Page 84
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
Switch-Based Bulletin Board
This feature will allow a user to leave messages in the system in order to
communicate with other system users.
NOTE:
This feature is not intended as a substitute for the existing procedures for
escalating problems, but only as an aid to the existing process.
Descrip tion
The bulletin board service provides an easy interface for the customer and
Lucent Technologies to leave messages on the system .
The bulletin board feature makes it easy for the customer to communicate with
Lucent Technologies (and vise-versa). For example, when a new load is installed
on a switch in the customer’s system, Lucent Technologies can leave the
customer messages which describe new functionality. This feature also allows
Lucent Technologies to keep the customer informed on the progress of trouble
items. In addition, the feature can be used by the customer to provide additional
information concerning problems that have already been escal ated.
Issue 1
August 1997
Page 3-24Switch-Based Bulletin Board
Accessing the Bulletin Board
Any user with the appropriate permissions can log into the system and have
access to the bulletin board. User’s who have “Maintain System” or “Administer
Features” permissions can enter, change, display, print, or schedule to print a
message. Users who have “Display Admen” and “Maintain Data” permission can
display the bulletin board. Any user who has “Display” permission can display,
print, and schedule to print the contents of the bulletin board.
When logging onto the system, users will be notified of any messages on the
bulletin board. The notification message will indicate the last time the bulletin
board was updated, if any “High-Priority” message exists, and if the bulletin
board is 80% or more full. If a “High-Priority” message exists, the command
prompt will change to the following message:
■ High-Priority Bulletin Board Messages Entered:
After the next command is entered, the default command prompt returns to the
screen.
User Considerations
■ Only one user at a time may edit a message on the bulletin board.
■ The user must have the proper permissions to access the bulletin board.
Page 85
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
■ The user must maintain the information stored on the bulletin board. It is
555-230-127
the user’s responsibility to delete old messages. If the bulletin board is full,
any new messages overwrite old messages.
System Considerations
The Bulletin Board feature provides up to 3 pages of text for each message.
Each page is limited to 20 lines of text, and each line of text is limited to 40
characters per line. The first 10 lines of text on page 1 is reserved for Lucent
Technologies Service’s High-Priority messages.
System Bulletin Board Commands
The system commands “change bulletin board,” “display bulletin board,” and
existing commands in the user interface are provided for use in the Switch Based
Bulletin Board.
Editing a Bulletin Board Message
Issue 1
August 1997
Page 3-25Switch-Based Bulletin Board
1. Log into the system with “Maintain System” or “Administer Features”
permissions.
2. Enter the command “change bulletin-board.”
3. Follow system prompts.
To display messages on the Switch Based Bulletin Board the user must:
1. Log into the system with “Maintain System”, “Display Admin”, or “Maint
Data” permissions.
2. Enter the command “display bulletin board.”
3. Follow system prompts.
Editing a Switch-Based Bulletin Board Message
A message may contain up to three pages of information. Message lines 1
through 10 on page 1 are reserved for Lucent Technologies Services
High-Priority
page one). Pages 2 and 3 will allow up to 20 lines of text, and each line of text
may be up to 40 characters per line. Each line of text has an associated date
field that is populated automatically by the system each time the line is modified.
The control keys used to edit existing feature forms must be used to edit a
message in the Switch Based Bulletin Board. The following characters are
allowed for use in the text field:
messages (the “init” and “inads” logins can edit the first 10 lines on
■ Uppercase/Lowercase letters, spaces, numerals, and !@#$%^&*()_
-+=[]{};’”<>./?.
Page 86
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
NOTE:
Tab characters are not allowed. The existing command line interface will
cause the cursor to move to the next field if a Tab character is entered.
If a user changes any lines that cause two or more consecutive blank lines, then
the bulletin board will be automatically reorganized (upon submittal). Two or
more blank lines will be consolidated into a single blank line. If a blank line is at
the top of a form, it will also be deleted. This function will help prevent holes in the
bulletin board screens as old entries are deleted.
To save a message entered into the bulletin board text field, the user must
execute the save translation comm and.
G3V3 software is required for the bulletin board feature. The bulletin board
feature, as described in this document is available in G3V4. The G3V3/G3V4
feature on the systems-parameters customers-options form need not be
enabled.
The following screen is an example of bulletin board messages between Lucent
Technologies and a customer who is having trouble with trunk group translations:
Issue 1
August 1997
Page 3-26System Logoff Procedure
display bulletin-board Page 1 of 3
Messages (* indicates high-priority) Date
* AT&T is in the process of 02/02/95
* investigating your trunk lockup problem. 02/02/95
* The Bulletin Board will be updated as 02/02/95
* information is found. 02/02/95
* We have identified the problem. 02/02/95
* The trunk you added does not provide 02/02/95
* disconnect supervision, however your trunk 02/02/95
* group was administered as such. 02/02/95
* Please call for details. 02/02/95
*
We recently added a new trunk group (14) 02/03/95
and have had trunk group members locking up. 02/03/95
We see the error - Thanks for checking. 02/03/95
System Logoff Procedure
The system logoff procedure should be done any time the terminal is not being
used. This assures that system tran sl at i ons are not accidentally corrupted. The
monitor system command, when canceled, automatically causes a terminal
user to be logged off and, thus, prevents unauthorized use of the terminal. Use
the following procedure to log off the system:
1. Verify that the screen displays: enter command:
2. Enter logoff and press
Enter. The screen displays:
login:
Page 87
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
If after either logging on as system technician or issuing a system technician
command no additional command is issued for 30 minutes, an automatic
time-out and logoff occurs. At that time, any alarms in the system previously
unreported to INADS are reported. If you are logged in at two separate
administration terminals, the system waits until the second terminal times out or
until you log off before reporting such alarms to INADS.
Issue 1
August 1997
Page 3-27DEC VT220 Terminal
Logoff Notification
significant security risk are enabled. A message displays on the system
administration/maintenance interface. Additionally, the user can be required to
acknowledge the notification before the logoff is completed.
DEC VT220 Terminal
The system supports use of the DEC VT220 connected to the system and used in
the same way as the other terminals. When logging in, at the terminal-type
prompt the user should enter ”VT220” to initialize the correct parameters.
Keyboard definitions shown in Table 3-5
Table 3-5. Keyboard Definitions for the DEC VT220 Terminal
FUNCTIONVT220 KEY
HelpHelpESC[28~
Previous PagePrevious ScreenESC[5~
Next PageNext ScreenESC[6~
CancelRemoveESC[3~
ExecuteDoESC[29~
alerts system adminis trato rs if features that present a
are in effect:
ESCAPE
SEQUENCE
Previous FieldF17ESC[31~
Next FieldF18ESC[32~
Clear FieldF19ESC[33~
RefreshF20ESC[34~
Next FormSelectESC[4~
Up ArrowUp_ArrowESC[A
Down ArrowDown_ArrowESC[B
Right ArrowRight_ArrowESC[C
Left ArrowLeft_ArrowESC[D
Update FormFindESC[1~
Page 88
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Management Terminals
3
555-230-127
Issue 1
August 1997
Page 3-28DEC VT220 Terminal
Page 89
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Initialization and Recovery
4
4
Initialization and Recovery
When the system is powered up, or when it experiences a catastrophic fault that
interrupts its basic functions, the system undergoes a reboot. Besides “reboot,”
there are several less severe resets available to the system that allow it to recover
from disrupting errors. The user can initiate these resets by using the reset
system commands. These commands are used to manually restart the system at
various levels, depending on the required test activity. The reset system
commands are discussed in Chapter 8, ‘‘
Trouble-Clearing Aids’’.
555-230-127
Issue 1
August 1997
Page 4-1
4
Maintenance Commands and
A system is reset due to a loss of power, or via one of the following:
■ Reset command s at the adminis tration terminal.
■ Maintenance software, from which the system can reset itself. (This
process starts when certain software and hardware errors are detected by
the softwa r e .)
■ “Int erchang e,” which is a type of reset that can be scheduled as part of
daily maintenance in High or Critical Reliability systems.
!
WARNING:
When the system is rebooted or reset at level 2, 3, 4, or 5, all voice
terminal and attendant console features are adversely affected.
Users should be advised of services that are lost and that, as a
result, must be reactivated. See “Removing Power” in Chapter 5,
‘‘Routine Maintenance Procedures’’.
The administration terminal display and circuit pack LEDs indicate the progress
of the recovery process. LEDs are discussed in Chapter 7, ‘‘
The sections that follow discuss successful system resets. For each level of
reset, a typical administration terminal display is provided. Note that any
LED Interpretation’’.
Page 90
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Initialization and Recovery
4
hexadecimal numbers shown in parentheses, such as”(=8B89),” are only
examples and are subject to change. Subsequent sections discuss the recovery
process following an SPE-Down Mode and for "duplication interface-processing
element communication down."
NOTE:
If any of the diagnostic tests fail, the system may or may not function
properly, and the LMM may or may not proceed with the restart. If the LMM
does not proceed with the restart, the system goes into SPE-Down Mode. In
failure cases, the appropriate part (for example, the Processor circuit pack)
should be replaced.
NOTE:
Use and check the results of the set/get vector command found in the "Set
Commands" section in Chapter 8, ‘‘
Trouble-Clearing Aids’’, to determine how much time should be added for
the recovery levels. Also, if an update file is applied on a system reset, add
from 30 seconds to one minute to the recovery time for that reset.
555-230-127
Maintenance Command s and
Issue 1
August 1997
Page 4-2Reset System 1 (System Warm Start)
Reset System 1 (System Warm Start)
This recovery takes about 30 seconds. All stable phone calls remain up.
In-progress calls are dropped. No new calls can be made during this time.
In this restart, all software (Oryx/Pecos, drivers, maintenance, and so forth.) is
reset.
Typical Display
RESET 1 (WARM) PERFORMED
Reset System 2 (System Cold Start
Without T ranslation s L oad ing)
All Port circuit packs are reset. All telephone sessions are dropped. Telephones
begin to reconnect to the switch within 30 seconds. In a large system,
reconnection of all telephones may take up to five minutes.
In this restart, all software (Oryx/Pecos, drivers, maintenance, and so forth) is
reset. In addition, the TDM Bus and all port circuit packs are reset. Typical
displays in a Release 5vs/si system follow:
Page 91
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Initialization and Recovery
4
555-230-127
Typical Display Release 5vs/si and Later Systems
INTERNAL REGISTER TESTPASSED
LOCAL BUS TESTPASSED
ROM CHECKSUM TESTPASSED
CONTROL STATUS TESTPASSED
DCACHE TESTPASSED
ICACHE TESTPASSED
WRITE BUFFER TESTPASSED
BTO TESTPASSED
TIMER TESTPASSED
RESET 2 (COLD_2) PERFORMED
Issue 1
August 1997
Page 4-3Reset System 3 (Syste m Cold Star t Wit h Translations Loading)
Reset System 3 (System Cold Start
With Translations Loading)
Emergency Transfer is invoked. Translations reload from translation card.
Depending on the translations, the reloading process could take from five to 30
seconds. Thereafter, all port circuit packs are reset, and all telephone sessions
drop. Telephones begin to reconnect to the switch within 30 seconds. In a large
system, reconnection of all telephones may take up to five minutes.
In this restart, all software (Oryx/Pecos, drivers, maintenance, and so forth) is
reset. After the software is reset, all translations load from translation card. In
addition, the TDM Bus and all port circuit packs are reset. Typical displays in a
Release 5 vs/si system follow:
Page 92
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Initialization and Recovery
4
555-230-127
Typical Display (TN790 Release 5vs/si and Later
Systems)
INTERNAL REGISTER TESTPASSED
LOCAL BUS TESTPASSED
ROM CHECKSUM TESTPASSED
CONTROL STATUS TESTPASSED
DCACHE TESTPASSED
ICACHE TESTPASSED
WRITE BUFFER TESTPASSED
BTO TESTPASSED
TIMER TESTPASSED
RESET 3 (COLD_1) PERFORMED
Issue 1
August 1997
Page 4-4Reset System 4 (Syste m Reboot)
Reset System 4 (System Reboot)
Emergency Transfer is invoked. The boot image is already in the flash ROM
memory. The system reboots immediately after the LMM performs a series of
diagnostics on the processor and memory. Translations reload from the
translation card. Depending on the translation, the reloading process takes from
five to 30 seconds.
Thereafter, all port circuit packs are reset, and all telephone sessions drop.
Telephones begin to reconnect to the switch within 30 seconds. In a large
system, reconnection of all telephones may take up to five minutes. Typical
displays in a Release 5 system follo w:
Typical Display (TN790 Release 5 and Later)
INTERNAL REGISTER TESTPASSED
LOCAL BUS TESTPASSED
ROM CHECKSUM TESTPASSED
CONTROL STATUS TESTPASSED
DCACHE TESTPASSED
ICACHE TESTPASSED
Continued on next page
Page 93
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Initialization and Recovery
4
WRITE BUFFER TESTPASSED
BTO TESTPASSED
MEM CONFIG TESTPASSED
MEMORY FUNCTIONAL TESTPASSED
MEMORY MODULE A STUCK BIT TESTPASSED
MEMORY MODULE A PARITY TESTPASSED
MEMORY MODULE A BURST TESTPASSED
MEMORY MODULE B STUCK BIT TESTPASSED
MEMORY MODULE B PARITY TESTPASSED
MEMORY MODULE B BURST TESTPASSED
MEMORY MODULE C STUCK BIT TESTPASSED
MEMORY MODULE C PARITY TESTPASSED
MEMORY MODULE C BURST TESTPASSED
555-230-127
Issue 1
August 1997
Page 4-5Reset System 5 (Syste m Reboot and Run Al l 24-Hour Tests)
RAM DATA CHECKSUM TESTPASSED
RESET 4 (EXT REBOOT) PEFORMED
Reset System 5 (System Reboot and
Run All 24-Hour Tests)
out_cnt = 1802240
Continued on next page
Emergency Transfer is invoked. The LMM performs a series of diagnostics on the
processor, on memory, and on memory card. Some diagnostics perform twice.
This takes less than three minutes.
Page 94
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Initialization and Recovery
4
555-230-127
The boot image is already in the flash ROM memory. The system reboots
immediately after the LMM performs a series of diagnostics on the processor and
memory. Translations reload from the translation card. Depending on the
translation, the reloading process takes from five to 30 seconds. Thereafter, all
port circuit packs are reset, and all telephone sessions drop. Telephones begin
to reconnect to the switch within 30 seconds. In a large system, reconnection of
all telephones may take up to five minutes. Finally, scheduled maintenance is
initiated. Typical displays in a Release 5vs/si system follow:
Typical Display (TN790 Release 5 and Later)
INTERNAL REGISTER TESTPASSED
LOCAL BUS TESTPASSED
ROM CHECKSUM TESTPASSED
CONTROL STATUS TESTPASSED
DCACHE TESTPASSED
Issue 1
August 1997
Page 4-6Reset System 5 (Syste m Reboot and Run Al l 24-Hour Tests)
ICACHE TESTPASSED
WRITE BUFFER TESTPASSED
BTO TESTPASSED
MEM CONFIG TESTPASSED
MEMORY FUNCTIONAL TESTPASSED
MEMORY MODULE A STUCK BIT TESTPASSED
MEMORY MODULE A PARITY TESTPASSED
MEMORY MODULE A BURST TESTPASSED
MEMORY MODULE A COUPLE TESTPASSED
MEMORY MODULE B STUCK BIT TESTPASSED
MEMORY MODULE B PARITY TESTPASSED
MEMORY MODULE B BURST TESTPASSED
MEMORY MODULE B COUPLE TESTPASSED
MEMORY MODULE C STUCK BIT TESTPASSED
MEMORY MODULE C PARITY TESTPASSED
MEMORY MODULE C BURST TESTPASSED
MEMORY MODULE C COUPLE TESTPASSED
VIRTUAL MEMORY TESTPASSED
Continued on next page
Page 95
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
RAM DATA CHECKSUM TESTPASSED
RESET 5 (EXT REBOOT ) PEFORMED
555-230-127
Issue 1
August 1997
Page 4-7Reset System Inter change (High or Critical Reli ability Systems Only)
out_cnt = 1802240
Continued on next page
Reset Sy s te m Interchange (High or
Critical Reliability Systems Only)
SPE-interchange (system hot start) is denoted by an "i" in the initcauses log. This
restart is used to transfer control from the Active SPE to the Standby SPE in the
least disruptive manner. Interchange (i) is the most transparent of all levels of
restart and causes no disruption of service to telephone users. This restart takes
fewer than two seconds.
NOTE:
The administration terminal is logged off. No diagnostics are performed,
and only the login prompt displays.
An interchange (i) can be performed in one of the following three ways:
a. System Technician-Demanded: using the reset system interchange
command
b. Scheduled Maintenance
c. Software-Requested: The software requests the interchange when it
determines that the Standby SPE is healthier than the current Active SPE
NOTE:
For most SPE alarms, interchange to the standby SPE is achieved using the
hot restart (i). However, there may be other alarms for which another restart
level (1 through 4) must be used to achieve a transition to the Standby SPE.
See Table 6-1
Condit io n s ” in Chapter 6, ‘‘Reliability Systems: A Maintenance Aid’’, for a
complete list of alarms and restart levels.
, “Software-Requested Interchanges Caused by Alarm
Page 96
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Initialization and Recovery
4
555-230-127
Procedure for SPE-Down Mode
Due to fatal hardware and software problems, it is possible for a system to go
into SPE-Down Mode. In this mode, the system invokes emergency transfer and
does not provide any other service. Moreover, while in this mode, the software
does not (or cannot) run at all. In a high or critical reliability system the system
goes into SPE-Down mode only when both SPEs go into SPE- Down mode.
There is an interface to the system by maintenance. The Processor circuit pack,
is responsible for maintenance in a standard reliability system. In a high or
critical reliability system, the maintenance is provided by the A-carrier
Duplication Interface (DUPINT-A) TN772 circuit pack with help from the
processor.
The administration terminal, which connects directly to the processor in a
standard reliability system and to DUPINT-A in a high or critical reliability system,
provides a very limited interface to the system. Technicians can display alarms or
restart the system. Only a subset of control complex alarms displays.
Issue 1
August 1997
Page 4-8Procedure for SPE-Down Mode
The following are sample displays for SPE-Down mode and the alarms
displayed.
Display for SPE-Down in a Standard Reliability system:
************* *SP E D OW N MODE********** ***
You can display alarms and reset system(4).
SPE_DOWN->
Screen 4-1
and Screen 4-2 show all possible SPE-Down ala rms in a standard
reliabil ity s y st em and in a high or cr iti ca l re liability syst em, respective ly .
DISPLAY ALARMS:
Physical Logical On Alternate Alarm Date Date
Name Name Board? Name Type Alarmed Resolved
------ PROC_BD y ----- MAJOR ------ ------
------ MEM_BD_0 y ----- MAJOR ------ ------
------ M_BUS y ----- MAJOR ------ ------
------ MAINT* y ----- MAJOR ------ ------
------ NETCON_BD y ----- MAJOR ------ ------
------ TAPE_UNIT ------ ----- MAJOR ------ ------
------ NO_TAPE ------ ----- MAJOR ------ ------
Screen 4-1. Display Alarms Command
Page 97
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Initialization and Recovery
4
555-230-127
* The “MAINT” designation is used for PR-MAINT.
Display for SPE-Down in a High or C ritical Reliab ili ty Sy stem:
************* *SP E D OW N MODE********** **
You can display alarms [a|b] and reset system(4) [a|b].
SPE_DOWN->
Issue 1
August 1997
Page 4-9Procedure for SPE-Down Mode
Screen 4-2
shows only one SPE-Down alarm in a high or critical reliability system
after entering the display b command:
DISPLAY ALARMS B:
Physical Logical On Alternate Alarm Date Date
Name Name Board? Name Type Alarmed Resolved
------ PROC_BD y ----- MAJOR ------ ------
Screen 4-2. Display Alarms (one SPE-Down)
NOTE:
A standard rel iabili ty system t ries to rest art i tse lf ever y 20 m inutes. A hig h or
critical system tries to re sta rt itself every 10 minutes.
The first step is to determine the location of the problem. It is possible for two or
more circuit packs to have failed. It is also possible for a fatal problem with one
circuit pack to affect another circuit pack. This is especially true for the Processor
and Memory circuit packs, where a failure in one affects the other. All three of the
following methods should be employed to determine where the fatal fault lies.
1. Use display alarms command:
Issuing t he display alarms [a | b] command at the administration terminal
shows where maintenance thinks the problem lies. The alarms are a good
indication of why the system went down. They should be used with the
following two methods.
2. Observe red LEDs:
Observe the red LEDs on the circuit pack to determine where software or
processor firmware (LMM) had a problem.
3. Use the reset command:
In 286 system, issuing th e reset command (Standard Reliability system) or
the reset [a | b ] command (High or Critical Reliabil it y system) causes the
system to attempt a reset system 4. Observe all the diagnostics on the
screen, and note if the LMM has a problem with any of the diagnostics, as
this information should give a good indication of where the problem lies.
Page 98
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Initialization and Recovery
4
555-230-127
The procedure to get a system out of SPE-Down mode follows.
NOTE:
This is important! If you cannot complete the first step or have problems
with the maintenance interface, then the first step should be to replace the
Processor circuit pack. In a high or critical reliability system the DUPINT-A
circuit pack can also cause SPE-Down.
1. If the alarms indicate a tape failure, replace the tape or tape drive and go
to Step 3. Otherwise, verify that there is a good tape in the tape drive. If a
tape is not present or if either the tape or tape drive is defective, then
restarting the system using the reset command causes the system to go
down again.
2. In a High or Critical Reliabili ty system, select a carrier to repair first.
When it is possible to accurately determine the location of the problem,
use the display alarms [a | b ] command to display alarms for both SPEs
and check the red LEDs on the processor complex circuit packs. Select
the carrier where the red LEDs indicate the circuit pack alarmed. Bring up
the system on that carrier and then refer to Standby SPE Maintenance
documentation to repair the Standby SPE.
Issue 1
August 1997
Page 4-10Procedure for SPE-Down Mode
In a Standard Reliability system or after a carrier is chosen in a High or
Critical Reliability system, determine which circuit pack is defective by
displaying alarms and observing the red LEDs (as discussed previously).
Depending on the alarms, use Table 4-1
to replace the circuit packs
indicated, one by one, in the order shown.
Page 99
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Initialization and Recovery
4
Table 4-1. Order of Circuit Pack Replacement
PROC_BD1) Processor
MEM_BUS1) Processor
PROC_MEM1) Processor
OFFBD_MEM1) Processor
INVALID_ERR1) Processor
555-230-127
AlarmSuggested Circuit Pac ks
To Replace
2) Network Control
2) Network Control
2) Network Control
2) Network Control
Issue 1
August 1997
Page 4-11Procedure for Duplication Interface — Processing Element Communication Down
MAINT_BD1) Processor
2) Network Control
NETCON_ABSENT1) Network Control
2) Processor
NO_CARTRIDGE1) Memory Card
2) Network Control
3) Processor
Procedure for Dup licat ion Interface —
Processing Element Communication
Down
In a High or Critical Reliabil i ty system, it is possible for both SPEs to stop
communicating with the A-carrier TN772 Duplication Interface (DUPINT-A) circuit
pack. Thus, the DUPINT-A, which is in charge of maintenance, prints the
following message on the administration terminal:
Duplication Interface-Processing Element Communication down
The system may continue to function on one of the SPEs. However, the system is
not able to provide any interface to the administration terminal.
If the system is still providing service, connect the administration terminal to the
Active SPE (check the amber LED on the Processor circuit pack). Then, if
Page 100
DEFINITY Enterprise Com munications Server Release 6
Maintenance for R6vs/si
Initialization and Recovery
4
555-230-127
software provides a login on the administration terminal, you can determine the
problems via the display alarms command.
If the system is not providing service, there is a problem with the Processor
circuit packs and/or DUPINT-A. Replace these circuit packs, one by one, until
the system starts functioning normally.
Issue 1
August 1997
Page 4-12Procedure for Duplication Interface — Processing Element Communication Down
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.