AT&T Definity Enterprise Definity ECS R6 - Maintenance for R6r

Download

Page 1

DEFINITY®

Enterprise Communications Server Release 6

Maintenance for R6r Volumes 1 & 2

555-230-126 Comcode 108136128 Issue 2 January 1998

Page 2

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 chan ge.

Your Responsibility for Your System’s Security

Toll fraud is th e unauthorized use of your telecommunicati ons system by an unauthorized party, for example, per s ons other than your com-

pany’s employees, agents, subcontr actors, or per s ons working on your company’s behal f. Note that there may be a ris k of tol l fraud associ ated with your telecommunicati ons s ys tem and, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services.

You and your sys tem manager are resp ons ible for the security of your system, such as programming and configuring your equipment to prevent unauthorized use. The syst em manager is also responsible for reading all installation, instruction, and system administration documents provid ed w ith this prod uct in order to fully under s tand the features that can introdu ce risk of toll fraud and the step s that can be t aken to reduce that risk. Lu cent Te chn ol ogie s does not w a rrant that this product is immune from or will prevent unauthor ized use of common-carrier telecommunication services or facilities accessed through or connected to it. Lucent Technologies will not be responsible for any charges that result from such unauthorized use.

Lucent Technol ogies Fraud Intervention

If you suspect that you are being victimized by toll fraud and you need technical sup por t or assistance, call Technical Service Cente r Toll Fraud Inter vention Hotline at 1 800 643-2353.

Federal Communications Commission Statement Part 15: Class A Statement. This equi pment has been tested and

found to comply with the limit s for a Class A digita l dev ic e, pur suan t to Part 15 of the FCC Rules. These limits ar e designed to provide reasonable prot ection agains t harmful inte rference when th e equipment is operated in a commer cial environ m ent. This equi pment generates , uses, and can radiate radio-frequency energy and, if not installed and used in accorda nce with the ins tru ctio ns, may caus e har mful in terfe rence to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense.

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-13283-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 administered by the CPE use r

This equipmen t returns answer -supervis ion signals on all D ID calls forwarded back t o the public switched telephone network. Per m issible exceptions ar e:

• A call is unanswered

• A busy tone is received

• A reorder tone is received

Canadian Department of Communications (DOC) Interference I nformation

This digital appara tus does not exce ed the Cla ss A limits for radi o noise emissions set out in the radio interference regulations of the Canadian Depar tment of Communications.

ésent Appareil Nomérique n’ém et pas de br u i ts r a di oélectriques

Le Pr

épassant les limites applicables aux appareils numériques de la class

éscrites dans le reglement sur le brouillage radioélectrique édicté

A pr par le minist

Trademarks

See the preface of this document.

Ordering Information Call: Lucent Technologies Publications Center

Write: Lucent Technologies Publications Center

Order: Document No. 555-230-126

For additional documents, refer to the section in “About This Document” entitled “Related Resources.”

You can be placed on a standi ng order lis t for this and other docum ents you may need. Standing order will enable you to automatically receive updated versions of individual documents or document sets, billed to account information that you provid e. For more infor mation on stan ding orders , or to be put on a list to receive futu re issues of th is document, contac t t he Lucent Technol ogies Publications Center.

European Uni on Declarati on of Confo r mity

The “CE” mark affixed to the DEFINITY® equipment described in this book indica te s that th e equ ipm ent c onf or ms to the followin g European Union (E U) Directives:

For more inform ation on standards compliance, contact your local distributor.

Comments

To comment on thi s document, ret ur n the comment card a t the f ront of the document.

Acknowledgment

This document w as prepa re d by Produ ct Doc umen tation Devel opm ent, Lucent Technologies, Denver, CO.

ére des Communications du Canada.

Voice 1 800 457 - 1235 International Voice 317 322-6791 Fax 1 800 457-1764 International Fax 317 322-6849

P.O. Box 410 0 Crawfordsville, IN 47933

Comcode 108136128 Issue 2, January 1998

• Electromagnetic Compatibility (89/336/EEC)

• Low Voltage (73/23/EEC)

• Telecommunications Terminal Equipment (TTE) i-CTR3 BRI and i-CTR4 PRI

Page 3

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

Contents

Contents iii About This Book xv

■ Safety Precautions xvi

■ Electromagnetic Compatibility Standards xvi

■ Standards Compliance xviii

■ Conventions Used in This Document xix

■ Intended Use xx

■ How to Use this Document xx

■ Organization xx

■ Trademarks and Service Marks xxi

■ Related Documents xxii

■ Federal Communications Commission Statement xxiv

Issue 2

January 1998

Page iii

■ How to Order Documentation xxvi

■ How to Comment on This Document xxvi

1 Maintenance Architecture 1-1

■ What’s new for R6.2r 1-1

■ Maintenance Objects 1-7

■ Alarm and Error Reporting 1-7

■ Port Network Connectivity (PNC) 1-9

■ SPE Duplic at io n 1-12

■ Power Interruptions 1-22

■ Protocols 1-24

■ Service Code s 1-38

■ Facility Interface Codes 1-39

■ Multimed ia Interface (MMI) 1-40

2 Hardware Configurations 2-1

■ Multi-Carrier Cabinet 2-1

■ Carriers in Multi-Carrier Cabinets 2-3

■ PNC Cabling — Fiber Hardware 2-8

■ Circuit Packs 2-12

■ Duplication: Reliability Options 2-17

3 Management Te rmina l 3-1

■ Terminals Supported 3-1

Page 4

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

Contents

■ Multiple A cc es s 3-1

■ Switch-Based Bulletin Board 3-2

■ Switch-Based Bulletin Board Message Notification 3-5

■ Connecting the MT 3-24

■ Logging On 3-26

■ Logging Off 3-28

4 Initializat ion and Recovery 4-1

■ Multiple Offer Categories 4-2

■ Hot Restart 4-3

■ Reset Level 1 (Warm Restart) 4-3

■ Reset Level 2 (Cold-2 Restart) 4-5

■ Reset Level 3 (Cold-1 Restart) 4-6

■ Reset Level 4 (Reboot) 4-6

■ Reset Level 5 (Extended Reboot) 4-7

Issue 2

January 1998

Page iv

■ Initialization Diagnostics 4-7

■ SPE-Down Command Interface 4-9

5 Responding to Alarms and Errors 5-1

■ Safety Precautions 5-1

■ DEFINITY AUDIX System Power Procedures 5-2

■ Electrostatic Discharge 5-3

■ Suppress Alarm Origination [y] 5-4

■ Reseating and Replacing Circuit Packs 5-5

■ Replacing a BIU or Rectifier 5-6

■ Replacing SPE Circuit Packs 5-7

■ Troubleshooting a Duplicated SPE 5-10

■ Executing a Planned SPE Interchang e 5-15

■ Fiber Fault Isolation Procedure 5-18

■ Multimedia Call Handling (MMCH) 5-26

■ Troubleshooting ISDN-PRI Problems 5-33

■ Troubleshooting ISDN-PRI Endpoints (Wideband) 5-36

■ Troubleshooting ISDN-BRI/ASAI Problems 5-38

■ Troubleshooting ISDN-PRI Test Call Problems 5-42

■ Troubleshooting the Outgoing ISDN-Testcall Command5-44

■ Packet Bus Fault Isolation and Repair 5-45

Page 5

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

Contents

6 Additional Maintenance Procedures 6-1

■ Software Updates 6-1

■ DS1 CPE Loopback Jack (T1 Only) 6-10

■ Facility Test Calls 6-23

■ Preventive Maintenance 6-31

■ Analog Tie Trunk Back-to-Back Testing 6-34

■ Ter m ina t ing Trunk T rans mission Testing 6-38

■ Removing and Restoring Power 6-39

■ Automatic Transmission Measurement System (ATMS) 6-40

7 LED Indic ators 7-1

■ Terminal Alarm Notification 7-1

■ Attendant Console LEDs 7-2

■ Circuit Pack LEDs 7-3

■ Expansion Interface Circuit Pack LEDs 7-4

Issue 2

January 1998

Page v

■ Maintenance Circuit Pack LEDs 7-5

■ Duplication Interface Circuit Pack LEDs 7-7

■ Switch Node Interface LEDs 7-8

■ DS1 CONV (TN574/TN1654) Circuit Pack LEDs 7-9

■ Tone-Clock Circuit Pack LEDs 7-13

■ Maintenance/Test Circuit Pack LEDs 7-13

■ LEDs on Standby Components 7-14

8 Maintenance Co mm ands 8-1

■ Command Line Syntax 8-1

■ Common Input Parameters 8-2

■ Common Output F ield s 8-5

■ Contention Between Simultaneous Commands 8-7

■ Busyout and Release Commands 8-8

■ Common Abort and Fail Codes 8-10

■ Alarm and Error Categories 8-13

■ backup disk 8-35

■ busyout cdr-link 8-37

■ busyout data-module 8-37

■ busyout disk 8-38

■ busyout ds1-facility 8-38

■ busyout fiber-link 8-39

Page 6

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

Contents

■ busyout host-adapter 8-40

■ busyout journal-printer 8-41

■ busyout link 8-42

■ busyout spe-standby 8-42

■ busyout sp-link 8-43

■ busyout tape 8-43

■ busyout trunk 8-44

■ cancel hardware-group 8-44

■ change circuit packs 8-46

■ change fiber-link 8-49

■ change synchronization 8-52

■ change system-parameters maintenance 8-54

■ clear errors 8-63

■ clear firmware-counters 8-63

■ clear pgate-port 8-63

Issue 2

January 1998

Page vi

■ disable suspend-alm-orig 8-64

■ display alarms 8-65

■ display errors 8-73

■ display events 8-80

■ display fiber-link 8-82

■ display initcauses 8-83

■ display system-parameters maintenance 8-85

■ display time 8-94

■ enable administered-connection 8-94

■ enable suspend-alm-orig 8-94

■ enable synchronization-switch 8-96

■ enable test-number 8-97

■ format card-mem 8-97

■ get vector 8-99

■ list cabinet 8-101

■ list configuration 8-102

■ list configuration software-versio n 8-106

■ list disabled-MOs 8-112

■ list fiber-link 8-113

■ list history 8-114

Page 7

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

Contents

■ list isdn-testcall 8-117

■ list marked-ports 8-118

■ list measurements ds1 8-119

■ list pms-down 8-123

■ list suspend-alm-orig 8-124

■ list sys-link 8-126

■ mark port 8-127

■ monitor bcms 8-127

■ monitor health 8-133

■ monitor security violations 8-133

■ monitor system 8-134

■ monitor traffic 8-142

■ monitor trunk 8-144

■ recycle carrier 8-145

■ release commands 8-145

Issue 2

January 1998

Page vii

■ reset board 8-147

■ reset disk 8-147

■ reset fiber-link 8-148

■ reset host-adapter 8-149

■ reset maintenance 8-149

■ reset packet-interface 8-150

■ reset interchange 8-152

■ reset port-network 8-155

■ reset spe-standby 8-157

■ reset system 8-158

■ reset system interchange 8-160

■ reset tape 8-162

■ restore announcements 8-163

■ restore disk 8-165

■ resume hardware-group 8-167

■ save announcements 8-168

■ save translation 8-171

■ set options 8-173

■ set pnc 8-181

■ set signaling-group 8-182

Page 8

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

Contents

■ set snc 8-182

■ set synchronization 8-182

■ set tdm 8-183

■ set time 8-184

■ set tone-clock 8-185

■ set vector 8-186

■ status access-endpoint 8-189

■ status administered-connection 8-189

■ status attendant 8-192

■ status bri-port 8-192

■ status cdr-link 8-201

■ status cleared-alarm-notif 8-202

■ status conference 8-203

■ status data-module 8-243

■ status hardware-group 8-245

Issue 2

January 1998

Page viii

■ status health 8-247

■ status isdn-testcall 8-250

■ status journal-link 8-252

■ status link 8-253

■ status logins 8-261

■ status packet-interface 8-261

■ status periodic-scheduled 8-262

■ status pgate-port 8-264

■ status pms-link 8-265

■ status pnc 8-265

■ status port-network 8-269

■ status processor-channel 8-273

■ status signaling-group 8-274

■ status spe 8-277

■ status sp-link 8-280

■ status station 8-281

■ status switch-node 8-283

■ status sys-link 8-285

■ status trunk 8-287

■ status tsc-administered 8-289

Page 9

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

Contents

■ status tti 8-290

■ test alarms 8-292

■ test analog-testcall 8-301

■ test board 8-302

■ test cdr-link 8-303

■ test customer-alarm 8-303

■ test data-module 8-303

■ test disk 8-303

■ test ds1-facility 8-304

■ test ds1-lo op 8-304

■ test duplication-interface 8-308

■ test eda-external-device-alrm 8-310

■ test environment 8-313

■ test fiber-link 8-314

■ test hardware-group 8-316

Issue 2

January 1998

Page ix

■ test host-adapter 8-321

■ test inads-link 8-321

■ test isdn-testcall 8-324

■ test journal-printer 8-324

■ test led 8-325

■ test link 8-326

■ test maintenance 8-326

■ test mass-storage 8-328

■ test memory 8-328

■ test mssnet 8-329

■ test packet-in terfa ce 8-330

■ test pr oces sor 8-330

■ test signaling-group 8-331

■ test spe-standby 8-331

■ test stored-data 8-333

■ test switch-control 8-333

■ test synchroniz ation 8-334

■ test sys-link 8-334

■ test tape 8-336

■ test tdm 8-337

Page 10

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

Contents

■ test tone-clock 8-337

■ test trunk 8-337

■ test tsc-admini stere d 8-337

■ upgrade software 8-337

9 Maintenance Object Repair Procedures 9-1

■ Escalation Procedures 9-1

■ ABRI-PORT (ASAI ISDN-BRI Port) 9-2

■ AC-POWER 9-3

■ ADM-CONN (Administered Connection) 9-11

■ ADX8D-BD (AUDIX Circuit Pack) 9-14

■ ADX8D-PT (AUDIX Digital Port) 9-15

■ ADX16D-B ( 1 6 Port AUDIX C ir c u i t P a c k) 9-22

■ ADX16A-BD (AUDIX Circuit Pack) 9-23

■ ADX16D-P (16-Port AUDIX Digital Port) 9-24

Issue 2

January 1998

Page x

■ ADX16A-PT (AUDIX Analog Line/Control Link) 9-31

■ ALARM-PT ( ALAR M PORT) 9-38

■ ANL-16-L (16-Port Analog Line) 9-42

■ ANL-BD (Analog Line Circuit Pack) 9-58

■ ANL-LINE, ANL-NE-L (8-Port Analog Line) 9-59

■ ANN-BD (Announcement Circuit Pack) 9-87

■ ANN-PT (Announcement Port) 9-104

■ ANNOUNCE 9-112

■ ASAI -BD (Multi-Appl ica t ion Platform B oard) 9-115

■ ASAI-EPT 9-117

■ ASAI-PT 9-125

■ ASAI-RES/E-DIG-RES (TN800 reserve slot) 9-135

■ AUDIX-BD (AUDIX Circuit Pack) 9-136

■ AUDIX-PT (AUDIX Port) 9-137

■ AUX-BD (Auxiliary Trunk Circuit Pack) 9-138

■ AUX-TRK (Auxiliary Trunk) 9-139

■ BRI-BD/LGATE-BD (ISDN-BRI Line Circuit Pack) 9-148

■ BRI-DAT (ISDN-BRI Data Module) 9-157

■ BRI-PORT (ISDN-BRI Port),

ABRI-PORT (ASAI ISDN-BRI Port)] 9-158

■ BRI-SET, ASAI-ADJ, BRI-DAT 9-188

Page 11

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

Contents

■ CABINET (Cabinet Sensors) 9-221

■ CARR-POW 9-228

■ CDR-LNK (Call Detail Recording Link) 9-246

■ CLSFY-BD (Call C lassifier Ci rc u it Pack) 9-247

■ CLSFY-PT (Call Classifier Port) 9-248

■ CO-BD (Central Office Trunk Circuit Pack) 9-253

■ CO-DS1 (DS1 CO Trunk) 9-254

■ CO-TRK (Analog CO Trunk) 9-269

■ CONFIG (System Configuration) 9-291

■ CUST-ALM (Customer-Provided Alarming Device) 9-297

■ DAT-LINE (Data Line Port) 9-299

■ DC-POWER (Single Carrier Cabinet Environment) 9-308

■ DETR-BD (Tone Detector Circuit) 9-313

■ DID-BD (Direct Inward Dial Trunk Circuit Pack) 9-314

■ DID-DS1 (Direct Inward Dial Trunk) 9-315

Issue 2

January 1998

Page xi

■ DID-TRK (Direct Inward Dial Trunk) 9-326

■ DIG-BD (Digital Line Circuit Pack) 9-339

■ DIG-LINE (Digital Line) 9-340

■ DIOD-BD (DIOD Trunk Circuit Pack) 9-361

■ DIOD-DS1 (DS1 DIOD Trunk) 9-362

■ DIOD-TRK (DIOD Trunk) 9-373

■ DISK (MSS Disk Circuit Pack) 9-382

■ DLY-MTCE (MO-DAILY) 9-405

■ DS1-BD (DS1 Interface Circuit Pack) 9-406

■ DS1-FAC (DS1 Facility) 9-478

■ DS1 CONV-BD 9-502

■ DT-LN-BD (Data Line Circuit Pack) 9-533

■ DTMR-PT (Dual Tone Multi-Frequency Receiver Port) 9-534

■ DUP-CHL (Duplication Interface) 9-539

■ DUPINT (Duplication Interface Circuit Pack) 9-571

■ E-DIG-BD (Multi Application Platform Board) 9-583

■ E-DIG-RES (TN800 reserve slot) 9-585

■ E-DIG-STA (Emulated Digital Line) 9-586

■ EMG-XFER (Emergency Transfer) 9-596

■ EPN-SNTY (EPN Sanity Audit) 9-602

Page 12

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

Contents

■ ERR-LOG (Error Log) 9-604

■ ETR-PT (Enhanced Tone Receiver Port) 9-605

■ EXP-INTF (Expansion Interface Circuit Pack) 9-611

■ EXP-PN (Expansion Port Network) 9-669

■ EXT-DEV ADMIN? N (External Device Alarm) 9-675

■ EXT-DEV ADMIN? Y (External Device Alarm) 9-679

■ FIBER-LK (Fiber Link) 9-682

■ GPTD-PT (General Purpose Tone Detector Port) 9-721

■ H-ADAPTR (MSS Host Adapter) 9-726

■ HYB-BD (Hybrid Line Circuit Pack) 9-741

■ HYB-LINE (Hybrid Line) 9-742

■ INADS (INADS L ink ) 9-762

■ ISDN-PLK (ISDN-PRI Signaling Link Port) 9-765

■ ISDN-LNK (ISDN-PRI Signaling Link Port) 9-770

■ ISDN-SGR (ISDN-PRI Signaling Group) 9-777

Issue 2

January 1998

Page xii

■ ISDN-TRK (DS1 ISDN Trunk) 9-790

■ JNL-PRNT (Journal Printer Link) 9-813

■ LGATE-AJ 9-814

■ LGATE-BD 9-814

■ LGATE-PT 9-814

■ LOG-SVN (Login Security Violation) 9-815

■ MAINT (EPN Maintenance Circuit Pack) 9-818

■ MEM-BD (3 2 MB Me mory Circuit Pack ) 9-831

■ MET-BD (MET Line Circuit Pack) 9-843

■ MET-LINE (MET Line) 9-844

■ MIS (Management Information System) 9-861

■ MMI-BD 9-862

■ MMI-LEV (Multimedia Interface Resource Level) 9-872

■ MMI-PT 9-875

■ MMI-SYNC 9-881

■ MODEM-BD (Modem Pool Circuit Pack) 9-883

■ MODEM-PT (Modem Pool Port) 9-884

■ M/T-ANL (Maintenance/Test Analog Port) 9-900

■ M/T-BD (Maintenance/Test Circuit Pack) 9-909

■ M/T-DIG (Maintenance/Test Digital Port) 9-913

Page 13

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

Contents

■ M/T-PKT (Maintenance/Test Packet Bus Port) 9-928

■ OPS-LINE (DS1 Off Premises Station Line) 9-933

■ PDATA-BD (Packet Data Line Circuit Pack) 9-947

■ PDATA-PT (Packet Data Line Port) 9-952

■ PDMODULE (Processor Data Module)

TDMODULE (Trunk Data Module) 9-968

■ PE-BCHL (PRI Endpoint Port) 9-985

■ PGATE-BD (Packet Gateway Circuit Pack) 9-1002

■ PGATE-PT (Packet Gateway Port) 9-1018

■ PKT- BU S (Pack et Bus) 9-1043

■ PKT-INT (Packet Interface Circuit Pack) 9-1052

■ PMS-LINK (Property Management System Link) 9-1089

■ PMS-PRNT/JNL-PRNT (PMS Printer Link) 9-1096

■ PNC-DUP (PNC Duplication) 9-1101

■ POWER 9-1119

Issue 2

January 1998

Page xiii

■ PRI-CDR/SEC-CDR (Call Detail Recording Link) 9-1131

■ PROC-SAN (Process Sanity Audits) 9-1137

■ PROCR (RISC Processor Circuit Pack) 9-1138

■ RING-GEN 9-1149

■ S-SYN-BD (Speech Synthesis Circuit Pack) 9-1155

■ S-SYN-PT (Speech Synthesis Port) 9-1156

■ SN-CONF (Switch Node Configuration) 9-1169

■ SNC-BD (Switch Node Clock Circuit Pack) 9-1177

■ SNC-LINK (Switch Node Clock Link) 9-1214

■ SNC-REF (Switch Node Clock Reference) 9-1219

■ SNI-BD (SNI Circuit Pack) 9-1222

■ SNI-PEER (SNI Peer Link) 9-1285

■ SPE-SELE (SPE Select Switch) 9-1290

■ STBY-SPE (Standby SPE Maintenance) 9-1292

■ STO-DATA (Stored Data) 9-1315

■ STRAT-3 (Stratum 3 Clock) 9-1338

■ SVC-SLOT (Service Slot) 9-1350

■ SW-CTL (Switch Control) 9-1352

■ SYNC (Synchronization) 9-1364

■ SYS-LINK (System Links) 9-1393

■ SYS-PRNT (System Printer) 9-1399

Page 14

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

Contents

■ SYSAM (Circuit Pack) 9-1404

■ SYSTEM (System) 9-1425

■ TAPE 9-1430

■ TBRI-BD (TN2185

ISDN Trunk-Side BRI) 9-1465

■ TBRI-PT (TN2185

ISDN Trunk-Side BRI Port) 9-1473

■ TBRI-TRK (TN2185

ISDN Trunk-Side BRI) 9-1494

■ TDM- BUS (TD M Bus) 9-1504

■ TDM-CLK (TDM Bus Clock) 9-1521

■ TDMODULE (Trunk Data Module) 9-1535

■ TIE-BD (Tie Tr unk Circuit Pack) 9-1536

■ TIE-DS1 (DS1 Tie Trunk) 9-1537

■ TIE-TRK (Analog Tie Trunk) 9-1555

Issue 2

January 1998

Page xiv

■ TIME-DAY (Time of Day) 9-1576

■ TONE-BD (Tone-Clock Circuit Pack) 9-1578

■ TONE-PT (Tone Generator) 9-1597

■ TSC-ADM (Administered Temporary

Signaling Connections) 9-1607

■ TTR-LEV (TTR Level) 9-1613

■ UDS1-BD (UDS1 Interface Circuit Pack) 9-1618

■ VC-BD 9-1705

■ VC-DSPPT 9-1709

■ VC-LEV (Voice Conditioner

DSP Port Level) 9-1719

■ VC-SUMPT 9-1722

■ WAE-PORT (Wideband Access Endpoint Port) 9-1728

■ XXX-BD (Common Port Circuit Pack) 9-1736

IN Ind ex IN-1

Page 15

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

About This Book

555-230-126

About This Book

This document provides instructions and supporting informat ion needed t o monitor, test, and maintain the hardware components of the DEFINITY Enterprise Communications Server Release 6 systems.

These system’s extensive background testing and technician-demanded tests

allow many problems to be addressed before they severely disrupt call processing. Duplication options further enhanc e this reliability, giving the technician an opportunity to provide a high level of service while resolving problems or performing routine maintenance.

Issue 2

January 1998

Page xv

This book provides the necessary information to make full use of these capabilities and introduces some new componen ts and strategies found in R6r.

NOTE:

This document is intended for Release 6 and later systems only. For previous DEFINITY systems (G3V5 and earlier), refer to

DEFINITY

Enterprise Communications Server, Release 5 Maintenance for R5r,

555-230-122.

Page 16

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

About This Book

555-230-126

Safety Precautions

Before working on a system, the technician must be thoroughly familiar with the precautions and practices described at the beginning of Chapter 5,

‘‘Responding to Alarms and Errors’’.

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 CLASS 1 LASER PRODUCT IEC825 1993

DANGER:

Use of controls or adjustments or performance of procedures other than those specified herein may result in hazardous radiation exposure.

Issue 2

January 1998

Page xviSafety Precautio ns

Contact your Lucent Technologies representati ve for more information.

Electromagnetic Compatibility Standards

This product complies with and conforms to the following:

■ Limits and Methods of Measurements of Radio Interference

Characteristics of Information Technology Equipment, EN55022 (CISPR22), 1993

■ EN50082-1, European Generic 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

■ Radiated radio frequency field IEC 1000-4-3

■ Electrical Fast Transient IEC 1000-4-4

■ Lightning effects IEC 1000-4-5

Page 17

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

About This Book

■ Conducted radio frequency IEC 1000-4-6

■ Mains frequency magnetic field IEC 1000-4-8

■ Low frequency mains disturbance

The system conforms to the following:

■ Electromagnetic com pat ib ilit y General Immuni ty St andard, part 1;

residential, commercial, light industry, EN50082-1, CENELEC, 1991

■ Issue 1 (1984) and Issue 2 (1992), Electrostatic discharge immunity

requirements (EN55024, Part 2) IEC 1000-4-2

■ Radiated 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.

Issue 2

January 1998

Page xviiElectromagnetic Compatibil it y Standards

The “CE” (Conformité Européenne) 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.

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

Page 18

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

About This Book

Standards Compliance

The equipment presented in this document complies with the following (as appropriate):

■ ITU-T (Formerly CCITT)

■ ECMA

■ ETSI

■ IPNS

■ DPNSS

■ National ISDN-1

■ National ISDN-2

■ ISO-9000

■ ANSI

■ FCC Part 15 a nd Par t 68

Issue 2

January 1998

Page xviiiStandards Compliance

■ EN55022

■ EN50081

■ EN50082

■ CISPR22

■ Australia AS3548 (AS/NZ3548)

■ Australia AS3260

■ IEC 825

■ IEC950

■ UL 1459

■ UL1950

■ CSA C222 Number 225

■ TS001

Page 19

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

About This Book

555-230-126

Conven tions Use d in This Doc ume nt

The following conventions are used in this document:

■ DEFINITY Systems are called G3V4, G3 Release 5, G3vs, G3si , and G3r

— All occurrences of G3siV4, G3siV4+m, G3siV5, and G3siV5+m are

called G3si unless a specific configuration is required to differentiate among product offerings

— All occurrences of G3 with out a suffix following the “3” refer to

G3vs, G3si, and G3r

■ A component of a DEFINITY System, such as a circuit pack, occurring

without a reference to any specific system, is part of G3

■ DEFINITY Communications Sever is abbreviated DEFINITY ECS

■ All physical dimensions in this book are in English (Foot Pound Second)

(FPS) followed by metric Centimeter Grams Second) (CGS) in parenthesis. Wire gauge measuremen ts are in AWG followed by the diameter in millimete rs in par en t he s is .

Issue 2

January 1998

Page xixConventions Used i n This Document

■ Information you type at the management terminal is shown in the following

typeface: list system-parameters maintenance

■ Information displayed on the management terminal screen is shown in the

following typeface: login

■ Keyboard keys are shown in the following typeface: Enter.

■ Circuit pack codes (such as TN790 or TN2182B) are shown with the

minimum acceptable alphabetic suf fix (like the ‘‘B” in the code TN2182B). Generally, an alphabetic suffix higher than that shown is also acceptable.

However, not every

vintage

of either the minimum suffix or a higher suffix

code is necessarily acceptable.

NOTE:

Refer to

Vintages and Change Notices

Technical Monthly: Reference Guide for Circuit Pack

, for current information about the usable vintages of specific circuit pack codes (including the suffix) in a Release 6 system.

■ Admonishments 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 interruptions.

WARNING:

This sign is used where there is possible harm to hardware or equipment.

Page 20

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

About This Book

DANGER:

555-230-126

This sign is used to indicate possible harm or injury to people.

Intended Use

■ As a guide to diagnosing and repairing the Release 6r system for use by

field technicians, remote service personnel, and user-assigned maintenance personnel

■ As a training manual for teaching technicians how to maintain the system

■ As a reference source on the system’s maintenance capabilities

This document assumes that the technician has a working knowledge of telecommunications fundamentals and PBX maintenance practices. This document also assumes that the system was initially installed and tested properly and brought into service with all faults cleared. Adjuncts and other devices external to the switch are covered by their own service documentation.

Issue 2

January 1998

Page xxIntended Use

How to Use this Document

Most maintenance sessions involve analyzing the Alarm and Error Logs to diagnose a trouble source and replacing a component such as a circuit pack. The information in Chapter 9, ‘‘ generally suffice to address these needs. Certain complex elements of the system, such as fiber links and the packet bus, require a more comprehensive approach. Special procedures for these elements appear in Chapter 5,

‘‘Responding to Alarms and Errors’’.

This document is not intended to solve all levels of trouble. When the limits of these procedures have been reached and the problem has not been resolved, it is the technician’s responsibility to escalate to a higher level of technical support. Escalation should conform to the procedures in the

Plan

Organization

■ Chapter 1, ‘‘Maintenance Architecture’’, describes the system’s desig n

and maintenance strategy.

■ Chapter 2, ‘‘Hardware Configurations’’, shows the locations and

arrangements of the system’s cabinets, carriers, circuit packs, and cabling.

Maintenance Object Repair Proced ures ’’ will

Technical and Administration

■ Chapter 3, ‘‘Manage men t Terminal’’, describes how to set up and use the

management terminal.

Page 21

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

555-230-126

About This Book

■ Chapter 4, ‘‘Initialization and Recovery’’, describes the various reset and

reboot processes and how these are used to perform maintenance and recover systems or subsystems that are out of service. Use of the terminal SPE-down interface on non-functional or standby Switch Processor Elements is included here.

■ Chapter 5, ‘‘Respond ing to Alarms and Errors’’, describes general repair

procedures such as replacing circuit packs and special troublesho oting procedures such as those for fiber link and packet bus faults.

■ Chapter 6, ‘‘Add itional Maintenance Procedures’’, describes preventive

maintenance, software updates and other procedures not associated with specific alarms or components.

■ Chapter 7, ‘‘LED Indicators’’, is a guide to interpreting indications given by

circuit pack and attendant console LEDs.

■ Chapter 8, ‘‘Maintenance Commands’’, contains a description of each

maintenance command available through the management terminal. The commands are ordered alphabetically. A general description of command syntax and conventions appears at the beginning of the chapter.

Issue 2

January 1998

Page xxiTrademarks and Service Marks

■ Chapter 9, ‘‘Maintenance Object Repair Procedures’’, contains speci fic

troubleshooting and repair instructions for every component in the system. The maintenance objects are listed alphabetically by name as they appear in the Alarm and Error Logs. Under each maintenance object appears a description of the object’s function, tables for interpreting alarm and error logs, and instructions on how to use tests, commands, and replacements to resolve associated problem s. Most of these procedu res are complete and self-contained, while others rely upon procedures in

Chapter 5, ‘‘

Responding to Alarms and Errors’’.

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

■ DIMENSION

■ VOICE POWE R

The following are trademarks or registered trademarks of AT&T:

■ ACCUNET

Page 22

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

About This Book

555-230-126

Issue 2

January 1998

Page xxiiRelated Docume nts

■ DATAPHONE

■ MEGACOM

■ MULTIQUEST

■ TELESEER

The following are trademarks or registered trademarks of other companies:

■ Ascend

■ Audichron

■ MS-DOS

■ MicroChannel

■ MULTIQUEST

■ PagePac

■ UNIX

(trademark of the Novell Corporation)

Federal Comm unications Commi ssion 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:

555-015-201

555-232-105

, 555-232-108

, 555-025-201

■ Answered by the called station

■ Answered 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:

■ 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

Page 25

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

About This Book

555-230-126

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.

Means of Connection

Connection of this equipment to the telephone network is shown in the following table.

Issue 2

January 1998

Page xxvFederal Communications Commissio n Statement

Manufa cture r’s Po rt

Identifier FIC Code

Off/On Premises Station OL13C 9.0F RJ2GX, RJ21X,

DID Trunk 02RV2-T 0.0B RJ2GX, RJ21X CO Trunk 02GS2 0.3A RJ21X CO Trunk 02LS2 0.3A RJ21X Tie Trunk TL31M 9.0F RJ2GX

1.544 Digital Interface 04DU9-B,C 6.0P RJ48C, RJ48M

1.544 Digital Interface 04DU9-BN,KN 6.0P RJ48C, RJ48M 120A2 Channel Service Unit 04DU9-DN 6.0P RJ48C

If the terminal equipment (DEFINITY

System) causes harm to the telephone

SOC/REN/

A.S. Code Network Jacks

RJ11C

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.

Page 26

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

About This Book

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 for information.

This equipment, if it uses a telephone receiver, is hearing aid compatible.

555-230-126

How to Or der Doc um e n tation

In addition to this book, other description, installation and test, maintenance, and administration books are available. A complete list of DEFINITY books can be found in the 555-000-010.

This document and any other DEFINITY documentation can be ordered directly from the Lucent Technologies Business Communications System Publications Fulfillment Center toll free at 1-800-457-1235 (voice) and 1-800-457-1764 (fax). International customers should use 317-322-6791 (v oice) and 317-322-6849 (fax).

Business Communications System Publications Catalog

Issue 2

January 1998

Page xxviHow to Order Documentation

How to Comment on This Document

Lucent Technologies welcomes your feedback . Please fill out the reader comment card found at the front of this manual and return it. Your comments are of great value and help improve our documentation.

If the reader comment card is missing, FAX your comments to 1-303-538-1741 or

to your Lucent Technologies representative, and mention this document’s name and number,

Maintenance for R6r,

DEFINITY Enterprise Communication Server Release 6

555-230-126.

Page 27

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

The maintenance subsystem is that part of the software that is responsible for initializing and maintaining the system. This software continuously monitors system health and maintains a record of errors detected in the system. The maintenance subsystem also provides a user interface for on-demand testing.

555-230-126

Issue 2

January 1998

Page 1-1What’s new for R6.2r

This chapter provides a brief description of the R6r maintenance strategy, and

presents background information on the system’s ove rall functions. For detailed descriptions of components and subsystems, refer to related topics in Chapter 9,

‘‘Maintenance Object Repair Proced ures ’’. Sections on the following MOs are

particularly useful for gaining an understanding of how the system works:

■ STBY-SPE

■ PNC-DUP

■ EXP-PN

■ SNI-BD

■ DUP-INT

■ SYNC

What’s new for R6.2r

■ ‘‘Multiple feature offers’’

■ ‘‘Passwor d/ Sy s t em Security’’

■ ‘‘Multimedia Call Handling (MMCH) Enhancements’’

Page 28

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Multiple feature offers

Features are classified into two offer categories as depicted in Figure 1-1.

Features & Capacities

Category A

Category B

Boards

Issue 2

January 1998

Page 1-2What’s new for R6.2r

Category B

ValuePricedBoards

Category A

Standard

Priced Boards

Offers

Category A

Call Center

Top Tier Prologix

Wireless

Figure 1-1. Offer categories and related hardware, features, and capacities

Category B

BCS

Guestworks

qrdf0001 RPY 102297

■ Category A refers to top-tier offers and encompasses all current

DEFINITY (including ProLogix Communications Solutions) systems.

— All customer options allowed

Page 29

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

— All features allowed — Standard capacities

Issue 2

January 1998

Page 1-3What’s new for R6.2r

— Standard priced hardware

■ Category B refers to the cost and efficiency configurations with either

only

standard or value priced hardware and a reduced customer options and feature set (highlights).

— Standard or value priced hardware:

Standard Value Function

TN746 TN791 16-port analog TN2224 TN2214 24-port, 2-wire DCP TN2183 TN22 15 16-p ort analog

— No ASAI — No CDS — No m ult imedia — Limited Call Center — No remote access — No extension number portability — Reduced capacit ies

The offer category along with the model determines feature “set” as well as the allowed hardware and capacities.

Offer Security

Several security considerations have been added to protect the offer categories and the associated hardware.

■ Once translations for a Category A system have been entered, they

■ Standard-priced hardware is required for all Category A systems.

cannot be changed to Category B. Migrating from Category A t o Cat egory B requires a complete retranslation of circuit packs and software.

— Category A allows administering value-priced hardware (for

example, TN791, TN2214, and TN2215), but it will not function.

NOTE:

The Terranova system management software graphically represents the system configuration, including all line boards. This product must be modified to support the new valued-priced board types described above.

Page 30

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Initializ ation

At initialization, the system provides only the System-parameters offer-option screen; all other screen forms are disabled until the offer category is both administered and activated in the system. See ‘‘

‘‘Initialization and Recovery’’ for more information.

Password/System Security

DEFINITY uses two software products to secure the switch’s administration and maintenance ports. While these ports help customers and technicians alike, they also provide potential access to hackers, whose activities can result in unauthorized use of network facilities and theft of long distance services.

Remote Port Security Device (RPSD)

The RPSD software works with DEFINITY ECS (prior to Release 6.2) and DEFINITY Communications Systems; System 75 (V2 or higher) and System 85; DIMENSION PBX Systems; the AUDIX, DEFINITY AUDIX, and AUDIX Voice Power Systems; and all System Management products. For details on RPSD, see

BCS Products Security Handbook

the

Communications Systems Remote Port Security Device User’s Manual

555-025-400.

, 555-025-600 or the

Issue 2

January 1998

Page 1-4What’s new for R6.2r

Initialization’’ in Chap ter 4,

DEFINITY

Softlock

Beginning with DEFINITY ECS Release 6.2 and higher, SoftLock (also referred to as the Integrated Lock for the Security Toolkit) can be purchased and

the DEFINITY software base

. SoftLock is a centralized access interface that uses

installed in

a challenge/response protocol to verify the authenticity of a user and to reduce the opportunity for unauthorized access. Topics covered in this section are:

■ ‘‘Locking administered passwords’’

■ ‘‘Init l o gins’’

■ ‘‘INADS and craft log ins’’

Locking administered passwords

CAUTION:

While SoftLock is embedded in the DEFINITY ECS system, the feature is not customer-accessible until Release 6.3. This information is provided to alert technicians of the possiblity of locking all administered passwords on a

customer’s system.

Page 2 of the Change System-parameters Customer-options form contains a

Do not

SoftLock? field with a default of n, as shown in the screen below. change this field.

Page 31

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

change system-parameters customer-options Page 2 of 4 OPTIONAL FEATURES

OPERATIONS SUPPORT PARAMETERS ISDN-BRI trunks? n Restrict Call Forward Off Net? y ISDN-PRI? y Secondary Data Module? y ISDN-PRI over PACCON? y Softlock? n Malicious Call Trace? n Station and Trunk MSP? n Mode Code Interface? n Tenant Partitioning? n Multifrequency Signaling? y Terminal Trans. Init. (TTI)? y Multimedia Appl. Server Interface (MASI)? n Time of Day Routing? n Multimedia Call Handling (Basic)? n Uniform Dialing Plan? n Usage Allocation Enhancements? n Personal Station Access (PSA)? y Wideband Switching? n Wireless? n Processor and System MSP? n Private Networking? n

(NOTE: You must logoff and login to effect the permission changes.)

555-230-126

January 1998

Issue 2

Page 1-5What’s new for R6.2r

Figure 1-2. Change system-parameters customer-options form

WARNING:

Do not change the

Softlock?

field to y, as it locks all admi n is te re d

passwords in the system.

Similarly, Figure 1-3 shows page 2 of the Change System-paramet ers Security form containing the following SoftLock fields that

■ SYSAM-LCL?

■ SYSAM-RMT?

■ MAINT?

■ SYS-PORT?

should not

These fields are shown in bold for reference only.

be changed:

Page 32

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

change system-parameters security Page 2 of 2

SECURITY-RELATED SYSTEM-PARAMETERS

SECURITY VIOLATION NOTIFICATION PARAMETERS

SVN Station Security Code Violation Notification Enabled? n

STATION SECURITY CODE VERIFICATION PARAMETERS

Minimum Station Security Code Length: 4 Security Code for Terminal Self-Administration Required? y

SOFTLOCK PARAMETERS

SYSAM-LCL? n SYSAM-RMT? n MAINT? n SYS-PORT? n

555-230-126

Issue 2

January 1998

Page 1-6What’s new for R6.2r

Figure 1-3. Change system-parameters security form

WARNING:

Do not change any of these fields to y.

Init logins

There are no changes to these logins for R6.2.

INADS and craft logins

There are no changes to these logins for R6.2.

Multimedia Call Handling (MMCH) Enhancements

A new TN2207 PRI circuit pack allows connection to the Expansion Services Module (ESM).

■ Provides T.120 data-sharing capability on a MMCH multipoint H.320 video

conference

■ Each conference participant must have endpoints administered and a

personal computer with the H.320 video application installed.

■ The DEFINITY ECS must have the expansion service module installed.

See ‘‘

Expansion Services Module’’ in Chapter 5, ‘‘Res pond ing to Alarms and

Errors’’ for connectivity information.

Page 33

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Maintenance Objects

The system is partitioned into separate entities called maintenance objects (MOs). Each MO is monitored by the system and has its own maintenance strategy. Most MOs are individual circuit packs such as the processor circuit pack (PROC) and expansion interface circuit pack (EXP-INTF). Some are hardware components that reside on part of a circuit pack. For example, the TDM bus clock (TDM-CLK) and tone generator (TONE-PT) circuits reside on the tone/clock circuit pack (TONE-BD). Others represent larger subsystems or sets of monitors, such as expansion port network (EXP-PN) and cabinet environmental sensors (CABINET).

Finally, some MOs represent processes or combinations of processes and hardware, such as synchronization (SYNC) and duplicated port network connectivity (PNC-DUP). The above abbreviations are recorded in the error and alarm logs. Individual copies of a given MO are further distinguished with an address that defines its physical location in the system. These addresses are described in Chapter 8, ‘‘

instructions and a description of each MO appear alphabetically in Chapter 9,

‘‘Maintenance Object Repair Proced ures ’’.

Issue 2

January 1998

Page 1-7Maintenan ce O bjects

maintenance names

Maintenance Commands’’. Repair

Alarm and Error Reporting

During normal operations, software, hardware, or firmware may detect error conditions related to specific MOs. The system attempts to fix or circumvent these problems automatically, but if a hardware component incurs too many errors, an alarm is raised.

Alarm and Error Logs

The system keeps a record of every alarm detected in the system. This record, the alarm log, and the error log can be displayed locally on the management terminal or remotely by Initialization and Administration System (INADS) personnel. An alarm is classified as MAJOR, MINOR, or WARNING, depending on its effect on system operation. Alarms are also classified as ON-BOARD or OFF-BOARD.

■ MAJOR alarms identify failures that cause critical degradation of service

and require immediate attention. On high and critical reliability systems, MAJOR alarms can occur on standby compone nts without affecting service since their active counterparts continue to function.

■ MINOR alarms identify failures that cause some service degradation but

do not render a crucial portion of the system inoperable. The condition requires attention, but typically a a MINOR alarm affects only a few trunks or stations or a single feature.

Page 34

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

■ WARNING alarms identify failures that cause no significant degradation of

555-230-126

service or failures of equipment external to the system. These are not reported to INADS or the attendant console.

■ ON-BOARD problems originate in circuitry on the alarmed circuit pack.

■ OFF-BOARD problems originate in a process or component external to the

circuit pack.

Multiple alarms against a given MO can change the level of a given alarm as it appears in the alarm log. If there is an active error against an MO that causes a MINOR alarm and an active error that causes a MAJOR alarm, then the alarm log would show two MAJOR alarms. If the MINOR alarm problem is resolved first, the error is still marked as al ar med until the M AJ OR alarm pr oblem is reso lv ed, and the alarm log would still show two MAJOR alarms. If the MAJOR alarm problem is resolved first, the error is still marked as alarmed until the MINOR alarm problem is resolved, and the alarm log would now show two MINOR alarms. Similarly, the presence of an ON-BOARD alar m will caus e all alarm s against that MO to report as ON-BOARD.

NOTE:

To determine the actual level and origin of each alarm when there are more than one against the same MO, you must consult the

Entries

table for that MO.

Issue 2

January 1998

Page 1-8Alarm and Error Reporting

Hardware Error Log

The alarm log is restricted in size. If the log is full, a new entry overwrites the oldest resolved alarm. If there are no resolved alarms, the oldest error (which is not alarmed) is overwritten. If the log consists of only active alarms, the new alarm is dropped.

INADS Alarm Reporting

All M ajor and Minor alarms an d som e downgrad ed Warni ng al arms are report ed to INADS. (Some classes of alarms can be downgraded to lower levels by INADS

at the customer’s request). When the system raises one of these alarms, an attempt is made to call INADS. If the call to INADS fails, the call is retried in 7 minutes. This is repeated until four attempts have been made in a period of approximately 21 to 30 minutes. If all 4 attempts fail, the system waits 1 hour. Then it starts over again with 4 call attempts spaced 7 minutes apart. This cycle repeats until either the call to INADS successfully completes, or until the whole cycle is repeated 6 times. If, at any time during, a new alarm is raised by the system that should be reported to INADS, all timers and counts are reset and the strategy is repeated from the beginning.

During the 4 call attempts, the ACK lamp on the attendant console is turned off. Approximately 15 minutes into the hour interval between call attempts, the ACK lamp flashes, indi c at i ng th e syste m is having tr ouble reporting alarms to INADS. At the end of the entire scenario described above, if the system could not report the alarm to INADS, the ACK lamp continues to flash.

Page 35

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Port Network Con nectivity (PNC)

Port network connectivity is the equipment and controlling software that allows building large systems comprised of multiple Port Networks (PNs). Each PN is composed of Time Division Multiplexing (TDM) and packet (PKT) busses, and the port circuit packs connecting to them. A multi-carrier cabinet can contain more than one PN.

NOTE:

The terms LAN bus and PKT bus are interchangeable on the Release 5r. This document uses the term PKT bus, but “LAN” appears marked on some

hardware components.

This section describes the hardware, software and firmware components that support the PNC. Knowledge of the service and maintenance functions of these components will aid in diagnosing and resolving troubles. Troubleshooting techniques for general PNC components such as busses appear in Chapter 6,

‘‘Additional Maintenance Proc edures’’.

Issue 2

January 1998

Page 1-9Port Network Connectivity (PNC)

PNC Configurations

The PNC is provided in one of two different configurations: Direct Connect and Center Stage Switch (CSS). In either configuration the TN570 Expansion Interface (EI) board provides the interface to the data on the TDM/PKT busses. In the direct connect configuration up to three PNs connect by hardware between each pair of PN EIs. See Figure 1-4

Page 36

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Issue 2

January 1998

Page 1-10Port Network Connectivity (PNC)

Slot #

E E E E

I I I I

Slot # Slot #

EPN

Cabinet 2 Cabinet 3 Carrier A Carrier A

Fiber Links

PPN

Cabinet 1

PORT Carrier

PPN

Cabinet 1

PORT Carrier

EPN

2 1 2 1

Figure 1-4. Direct Connect PNC

In the CSS configuration, up to 16 PNs (including the PPN) can connect to one switch node (SN). With two SNs, up to 22 PNs can be connected. Each SN consists of a carrier containing the following components (in critical reliability systems, each SN is duplicated on a second, identically configured carrier):

■ 1 to 16 switch node interface (SNI) circuit packs (TN573)

Each SNI serves as the interface for TDM/PKT data to and from its associated PN EI or to and from an SNI in the other switch node.

■ 1 or 2 switch node clock (SNC) circuit packs (TN572)

The SNCs provide timing for bit synchronized switching among the SNIs.

■ Two power units

Each power unit provides +5V to the circuit packs in its half of the SN and to both SNCs.

■ Optionally in the PPN only, one Expansion Interface

■ Optionally, 1 or 2 DS1 converter (DS1C) circuit packs

The DS1 CONV circuit packs allow PNs to be located remotely up to 100 miles (161 km) between the two most distant PNs. The DS1 CONVs provide DS1 facility transport for a subset of the fiber timeslots between EIs in a direct connect system or between EIs and SNIs in CSS configurations. They can also be located on port carriers.

Page 37

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

■ TDM and PKT busses, and bus terminations

555-230-126

There are 16 data busses in the SN. Each SNI has a slot dependent data bus on which it transmits data and has 16 inputs, one for each SN SNI slot, including its own. The data busses are terminated by 4 AHF105 paddle boards that mount on the backside of the backplane slots 2 and 20.

■ Power distribution and control leads

Issue 2

January 1998

Page 1-11Port Network Connectivity (PNC)

Figure 1-5

shows two examples of CSS configurations. Illustrations of the switch

node carrier hardware appear in Chapter 2.

CSS with one switch node

EPN

not

used

Switch

node

carrier

PPN

EPN

EPN EPN

EI EI

5 4 3 20 18 17 16 15 14 13 12 11 10 9 8 7 6 2 1

CSS with two switch nodes

EPN

PPN

EPN EPN

EI EI

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 20 21 Slot number 19

Switch

node

carrier

Switch

node

carrier

EE2

Slot number 19

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 20 21

EPN

EPN EPN EPN

EPN EPN

EPN

EPN EPN EPN

EI EI EI

EPN EPN

S N

EPN

19 Slot number

EI EI

EPN

EPN EPN EPN

EI EI EI

EPN EPN

Fiber links

* * *

EPN EPN

* * *

Inter-switch

node ﬁbers

* *

EI EI EI

* The PPN EI or a DS1C circuit pack may reside in this slot

** A DS1C circuit pack may reside in this slot

Figure 1-5. Center Stage Switch Configurations (Simplex Examples)

Page 38

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

SPE Dupli ca tion

The Switch Processing Element (SPE) consists of the following circuit packs.

Table 1-1 . SPE C ir cu it Pa ck s a nd Mainten a nc e O bj e cts

Issue 2

January 1998

Page 1-12SPE Duplication

Apparatus

Code Circuit Pack Name

TN1648 System Access and

Associated

Maintenance Objects

SYSAM

Maintenance

UN330B Duplication Interface DUPINT,

DUP-CHL UN331B Processor PROCR TN1650B Memory MEM-BD TN1655 Packet PKT-INT UN332 Mass Storage System/

Network Control (MSSNET)

H-ADAPTR,

SW-CTL TN1657 Disk Drive DISK TN1656 Tape Drive TAPE

STBY-SPE

STO-DATA

These circuit packs reside on the A carrier (control carrier) of the PPN in all systems, except fo r the UN330B which is f ound o nly in high and critica l re l iab i lity systems. In high and critical reli ability systems, the PPN B carrier duplica te s exactly the configuration of the A carrier, making two identical SPE complexes. This duplication allows the system to recover from many faults, and enables troubleshooting and repairing of SPE components without interrupting service.

The Tone-Clock circuit pack also resides on the control carrier, and is also duplicated. However, it is not considered a part of the SPE. Although the SPE-Select switches control Tone-Clock selection, its duplication strategy differs from that of the SPE. See the ‘‘

TDM-CLK (TDM Bus Clock)’’ and ‘‘TONE-BD (Tone-Clock Circuit Pack)’’ sections in Chapter 9, ‘‘Maintenance Object Repair Procedures’’ for details.

Duplicated SPEs employ an active/standby strategy. At any one time, one SPE, A or B, is designated active and controls the switch services network. The other SPE, designated standby, is not required for switch service but remains ready to become active and resume control of service should a service-affecting failure occur in the active SPE. This action is termed an SPE interchange. It is important that the standby SPE be kept as available as possible to allow for a rapid interchange.

Page 39

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Standby SPE Availability

The STBY-SPE maintenance object is responsible for testing of the standby SPE so that any faults that would prevent it from being available for service can be isolated and repaired. Various factors affect the availability of the standby SPE:

■ The condition of the individual hardware components of the standby SPE,

including circuit packs, power supplies, cables and other supporting components.

Loss of pow er in an SP E due to power s upply or powe r deliv e ry components is discussed under the condition SPE-Down. If a circuit pack in the standby SPE that is critical to call service has failed, t he standby will not be able to become active. Maintenance testing of the standby SPE allows isolation and repair of component problems so that the standby can be made available again.

■ Standby memory content

Each write operation in active memory is shadowed to the corresponding location in the standby SPE’s memory. The standby memory should be in

agreement with the active in order to support an interchange that will preserve call, feature and translation information. Maintenance software tracking the STBY-SPE MO aims to keep the two memories in agreement.

Issue 2

January 1998

Page 1-13SPE Duplication

■ Standby State-of-Health (SOH)

The Duplication Interface circuit packs maintain a state-of-health value which reflects the availability of the standby SPE. If the Standby SPE’s state-of-health level is too poor, it cannot automatically be interchanged into (made active).

■ Standby SPE-Down

If the standby SPE is completely dead and held reset by its SYSAM (in SPE-Down), or the standby SPE has no power, it is unavailable for service.

■ System Time-of-Day

If the Time-of-Day clock of the standby SPE is substantially out of synch with the active, interchanges could be more disruptive to service than desirable.

System software running on both active and standby SPEs attempts to ensure that the standby SPE is kept fully available in terms of the above factors. The health of both the active and standby is tracked as a State-of-Health (SOH) value.

Page 40

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

TN1648 UN332

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SPE-Down

Interface

G3-MT

555-230-126

LAN Bus

UN330B

D U P

I N T

Duplication

Cable

Processor Multiplexed Bus

UN331B

R O

R Y

TN1650B TN1650B

E M O R Y

S P E B

TN1655

P K T I N T

TDM Bus

N E

TN1657

SCSI Bus

B Processor Carrier

T A

TN1656

Issue 2

January 1998

Page 1-14SPE Duplication

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

T N

C L K

G3-MT

Active

Maintenance

Interface

UN330B

TN1648 UN332TN1655

Figure 1-6. Duplic ated SPEs — Hardware Configuration

Standby SPE State of Health

The Duplication Interface circuit packs on each of the two SPEs keep track of the State of Health (SOH) of each of the two SPEs. This circuitry ensures that, at any time, unless the SPE-select switches are locked:

D U P

I N T

UN331B

Processor Multiplexed Bus

LAN Bus

P R O C R

S P E A

TN1650B TN1650B

T I N T

A Processor Carrier

SCSI Bus

TN1657 TN1656

S N

S K

TDM Bus

T N

C L K

■ If the two SPEs have the same SOH, the current active SPE remains

active.

Page 41

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

■ If the two SPEs have different SOH, the SPE with the better SOH becomes

555-230-126

or remains the active SPE.

These descriptions apply to SOH levels on the standby SPE. Four possible levels of SPE SOH are supported and maintained by system hardware and software.

functional The standby SPE is fully healthy with up-to-date

memory content identical to active SPE memory content. An interchange into this SPE will cause minimal service disruption.

not refreshed The standby SPE’s hardware and operational software

are fully healthy but the standby memory content is not currently identical to active SPE memory content. Typically either memory shadowing is off or a memory refresh operation is in progress to bring the memories’ contents into agreement. Interchange into an SPE of this health level will lead to calls dropping and a service outage of several minutes.

partially-functional One of the following conditions is in effect:

Issue 2

January 1998

Page 1-15SPE Duplication

— A failure of a critical standby SPE componen t has

occurred. — The standby SPE has been busied out. — The SPE is in recent interchange mode (see

STBY-SPE (Standby SPE Maintenance)’’ in

‘‘

Chapter 9, ‘‘

Procedures’’).

non-functional This is the worst and most seriously disabled state of a

standby SPE. The SPE has lost either power or basic sanity; the standby processor and its software are unable to cycle. Such an SPE cannot be made active by an interchange.

Standby SPE Maintenance Architecture

The maintenance strategy for the standby SPE is based on several independent components.

■ Maintenance of handshake communication so that software on the active

SPE can control maintenance of the standby SPE and its componen ts.

■ Controlling memory shadowing and performing the standby memory

refresh operation.

Maintenance Object Repair

■ Activities, independent of handshake communi cat ion and mem ory

shadowing, used to allow tracking of the standby SPE’s condition. This includes reading of hardware status to determine the actual state of standby S PE.

Page 42

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

As shown in Figure 1-7, all maintenance capabilities for the standby SPE are built upon these three strategies.

Issue 2

January 1998

Page 1-16SPE Duplication

Standby SPE

Hardware Status

Reading

Maintain

Standby SOH,

Shadowing,

Lock

Status

Memory

Shadowing

Memory

Refresh

G3-MT

Access to Standby SPE Components

Handshake Comm. Up

Error/Alarm

for Standby

Components

Figure 1-7. Components of Standby Maintenance

Standby SPE maintenance software is designed to attempt to self-correct problems. If a problem occurs, this software automatically tries to address the problem, bring the standby SPE back to a state of availability and clear all alarms which might have been raised. Typically, if a standby SPE problem has not cleared, it is of a hardware nature and some type of hardware component maintenance or replacement action is indicated. Once such correction s have been made, the syst em soft ware will automat icall y bring the st andby S PE back to full availability. There is no management terminal command to stimulate refresh of standby SPE memory; system software automatically accomplishes this itself when conditions are appropriate. The same is true of efforts to turn on shadowing where no explicit user interface command to turn on/off shadowing is available (note that busyout/release, below, can be used to indirectly accomplish this).

Logging

Maintain

Handshake

Communication

Time of day

clocks

in synch

Handshake

Comm.Down

Stby SPE

down/lock

G3-MT

Access to

SPE-Down

Interface

Standby Maintenance Monitor Software

The Standby Maintenance Monitor (SMM) is a software package that is running on key components of the standby SPE to verify its competence. SMM tests individual standby SPE components and reports back to the active SPE, by the handshake message, any failures of individual tests. Failure reports trigger enhanced maintenance attention to standby SPE component problems by active

always

Page 43

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

SPE software. SMM also ensures that when handshake communication has been down for an extended period, the standby SPE will transition into the SPE-down state.

Handshake Communication

Every 30 seconds, the active SPE sends a handshake request message to SMM and waits for SMM to respond with a handshake response message. This message transmission occurs across the Duplication Interface circuit packs and their interconnecting cable. As long as SMM responds to these regular handshake request messages, handshake communication is considered reported on the status spe screen.

The physical path of handshake communication is illustrated below. Hardware problems at any point in this route could interfere with handshake communication. If the standby SPE fails to respond to four successive handshake requests, handshake communication is considered down. A major alarm is logged against STBY-SPE with error type 1 logged. The status spe screen will indicate that handshake is down. It is then no longer possible to communicate with the standby SPE. Maintenance te sting of the standby by the active SPE (or by command) is discontinued, and the error and alarm logs become outdated for standby components.

Issue 2

January 1998

Page 1-17SPE Duplication

Handshake communication fa ilure is a severe and rare condition. It is due to either a failure of Duplication Interface hardware or a catastrophic failure of the standby SPE. As long as the active SPE is not locked by the switches, software attempts every 30 seconds, to re-establish handshake commu nication.

When the SPEs are locked with the switches, handshake communi cation is physically impossible, but no alarm is raised. When the standby is busied out, handshake communication should remai n up, but in any case, only the busyout WARNING alarm will be raised.

Whenever the active SPE has undergone a restart (levels 1-5), handshake is technically considered down during and just after the restart. After a level 1 (hot) restart, if there are no standby SPE problems, handshake communication should be restored within 30 seconds. After active-SPE restarts of levels 2 and up, handshake should be restored within 3 minutes of G3-MT re-enabling.

The active SPE keeps hardware configuration and vintage data about the components of the standby SPE. This data can be accessed with list configur a tio n c on t rol . Whene ve r handshak e is down, this data may be out of date. Whenever handshake has been down and is restored, the active SPE requests standby SPE software to transmit the current version of this data. The data is then stored in active SPE memory.

Failure to use the lock-and-power- down method for standby circuit pack replacement can lead to incorrect standby component hardware configuration and vintage data.

Page 44

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Issue 2

January 1998

Page 1-18SPE Duplication

D U

Active

SPE

Standby

SPE

Duplication

Interface Cable

D U P

Figure 1-8. Handshake Communication Path

Maintenance of Standby Components

When handshake commu nication is up, mainten ance for individual com pone nts of the standby SPE is the same as that for the active (except in some details for PKT-INT). The same commands are used to test standby and active circuit packs, and the error and alarm logs maintained on the active side record data for both.

MAP

software

DUP

Driver

. . . . . . . . . . .

SMM

software

. . . . . . . . . . .

P R O C R

MAP: Maintenance Action Process

SMM: Standby Maintenance Monitor

P R O C R

Request

Response

If a major on-board alarm is raised against a standby SYSAM, Processor, Memory, MSSNET, or Packet Interface board, the standby SPE’s SOH is lowered

partially-functional

to system software autom atically raises the stan db y SPE’ s SOH to

functional

, depending on whether its memory is up to date.

. Once that board’s problem is fixed and the alarm cleared,

not-refreshed

Standby component faults can also affect memory shadowing. Certain faults can have negative effects o n system operation if memory sha dowi n g is left on. When these components get major alarms, memory shadowing is automatically kept off by system software. These are referred to as

shadowing relevant

components. Roughly, these include the hardware that provide shadowing or the hardware into which shadowed writes occur.

Table 1-2

below shows the effect often major on-board alarms against standby

components on standby SOH and on memory shadowing. Note that off-board

Page 45

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

alarms, minor alarms and warning alarms have no effect on memory shadowing or on the SOH of the standby SPE.

Table 1-2. Effects of Major Alarms on Shadowing and Standby SOH

Alarmed

Component SOH Effect Shadowing Effect

PROCR partially functional no effect MEM-BRD partially functional shadowing kept off SW-CTL partially functional shadowing kept off SYSAM partially functional no effect PKT-INT partially functional s ha dowin g kept off DUPINT no effect shadowing kept off DUP-CHL no effect shadowing kept off HOST-ADAPTER no effect no effect

Issue 2

January 1998

Page 1-19SPE Duplication

DISK no effect no effect TAPE no effect no effect

When handshake commu nication is down, but the standby SPE is not in SPE-down mode (SOH is not

nonfunctional

), autonomous testing of standby SPE

components by the SMM occurs on the standby SPE. If a component fails a test

while handshake is down,

its red LED is lit and the standby SOH is lowered to

partially-functional.

A standby SPE component is considered to be testable if it can be tested with the usual maintenance commands from a management terminal connected to an ACTIVE connector on the SPE. In this condition, full maintenance software for it is running in the active SPE and the error/alarm data for it is up to date. Table 1-3 gives testability requirements for the various SPE components.

Page 46

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Table 1-3. Testability Requirements for Standby Components

Component Required Condition

PROCR handshake up MEM-BD handshake up SW-CTL handshake up SYSAM handshake up PKT-INT handshake up and Stby Refreshed DUPINT handshake up DUP-CHL handshake up HOST-ADAPTER handshake up DISK handshake up and Stby Refreshed TAPE handshake up and Stby Refreshed

Issue 2

January 1998

Page 1-20SPE Duplication

Locking th e Active SPE

Duplica tion Interface hardwa r e su pports the ability to lock the a ct iv e SP E in active mode by means of the SPE-Select switches. The procedure for safely doing this is described in Chapter 5, ‘‘

STBY-SPE (Standby SPE Maintenance)’’ in Chapter 9, ‘‘Maintenance Object

‘‘ Repair Procedures’’. In locked mode, the system operates as if it is simplex:

■ The standby SPE is inaccessible to the active SPE and active G3-MT

■ No SPE-interchange is possible.

■ Handshake is down and memory shadowing is off.

The locked state is intended for temporary use to prevent interchanges during maintenance sessions. No alarm is raised when the switches are locked. However, alarms against SPE-SELE are raised later if the switches are left out of the AUTO position for an extended length of time.

Memory Shadowing

Memory shadowing is used to keep the standby SPE’s memory content up-to-date relative to the active SPE’s memory. Memory shadowing is turned on automatically when the standby SPE has booted up and comp leted its own memory testing. Each write operation in active memory is replicated in the corresponding location in standby memory.

Responding to Alarms and Errors’’, and in

Page 47

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

When shadowing into the standby SPE has been off (as when the system first comes up), system software checks to see if it is safe to restore shadowing. Handshake communication must be up. Then software verifies (with Test #920) that the SPEs have identical hardware configurations. If this passes and there are no shadow-relevant component failures, system software turns on shadowing again.

Once shadowing is turned on, it is necessary to refresh the contents of standby

memory to bring it into full agreement with the active’s by copying every word of active SPE memory to the standby. This takes approximately 5 minutes, though traffic load can increase the duration. When completed, the standby SPE is said to be "refreshed". status spe or the

Standby SPE Status Query Test (#855)

STBY-SPE test sequence can be used to check the REFRESH status of the standby. Unless the standby SPE is refreshed, interchange into it can disrupt service for several minutes. Otherwise, interchanges are minimally disruptive. A standby SPE exiting lock mode or just released from busyout must undergo this full re-initialization.

System software tracks the operation and raises a major alarm when refresh failure occurs. If shadowing stays on, system software automatically tries to refresh again 5 minutes later.

Issue 2

January 1998

Page 1-21SPE Duplication

in the

Generally, memory shadowing should always remain on. But there are conditions when the system legitimately operates with shadowing off:

■ The standby SPE is undergoing any restart.

■ The active SPE is undergoing a restart level of 2 or greater.

■ The active SPE is locked.

■ The standby SPE is busied out.

In any other situation, it is an error condition for shadowing to be off. The first 2 situations are transitory and shadowing should automatically be restored within 10 minutes. If shadowing has been on for several minutes, it is an error condition for the standby not to be refreshed.

Initialization: Bringing the Standby SPE Up

When the standby SPE has been out of service or is first coming up, SPE software executes the following steps:

1. Establishes handshake comm unic ation.

2. When SMM answers handshake, raises the standby SPE’s SOH to

refreshed

there are critical component alarms.

3. Tests for component mismatch (test number 920).

if it has no critical component alarms, or

not

partially functional

4. If there is no mismatch, and no major alarms against shadow-relevant components, and if SMM permits, turns on memory shado wing

Page 48

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

5. If memory shadowing is successfully turned on, initiates the process of overall memory refresh

6. When refresh completes, if there are no critical component major alarms, raises the standby SPE’s SOH to level

Standby SP E in it ialization is a low er pr iority than initi a liz ing the active SPE and is therefore “paced” to lower CPU consumption. The above steps are carried out at 10 second intervals. During system initialization, the above sequence begins about 2 minutes after the terminal login prompt becomes available. Normally, the standby SPE should be fully initialized about 5 minutes after the availability of the login prompt. You can follow the execution of this sequence by repeatedly entering the command “status spe.”

Should a step of this initialization sequence fail, system software retries that step at 30 second intervals until it succeeds. It does not proceed to the next step until the current one has succeeded. The failed condition is alarmed.

A procedure for bringing up the standby SPE after being in the SPE-down or locked modes is described at the end of Chapter 4, ‘‘

Issue 2

January 1998

Page 1-22Power Interrupti ons

functional

Initialization and Recovery’’.

Power Interruptions

System cabinets and their associated power supplies can be powered by 110/208 volts AC either directly or from an Uninterruptible Power Supply (UPS) system. Alternatively, the cabinets and their power supplies may be powered by a -48 VDC battery power plant, which requires DC-to-DC conversion power units in the system.

If power is interrupted to a DC-powered cabinet or an AC-powered cabinet without optional backup batteries, the effect depends upon the decay time of the power distribution unit. If the interruption period is shorter than the decay time, there is no effect on service, though some -48V circuits may experience some impact. If the decay time is exceeded for a PPN, all service is dropped, emergency transfer is invoked and the system must reboot when power is restored. If the decay time is exceeded for an EPN, all service to that Port network is dropped and the EPN must be reset when power is restored. If the EPN contains a Switch Node carrier, all service to Port Networks connected to that Switch Node is dr opped .

Single-carrier cabinets, which can be used for EPNs, also have no battery backup. If power is interrupted for more than 0.25 seconds, all service is dropped, and emergency transfer is invoked for the EPN.

In the above cases, the cabinet losing power is unable to log any alarms. However, in the case of an EPN going down while the PPN remains up, alarms associated with the EPN will be reported by the system.

Page 49

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Nominal Power Holdover

AC-powered multicarrier cabinets are equipped with an internal battery, powered by its own charger, that provides a short term holdover to protect the system against brief power interruptions. This feature, known as the Nominal Power Holdover, is optional on cabinets supplied by a UPS and required on all other AC-powered cabinets. The battery is controlled in such a manner that it automatically provides power to the cabinet if the AC service fails. The duration of the holdover varies according to the type of carrier and whether or not the system has a duplicated SPE. See Table 1-4

Table 1-4. Nominal Power Holdover

Cabinet Type Control Carrier Entire Cabinet

PPN, duplicated SPE 5 minutes 10 seconds PPN, simplex SPE 10 minutes 10 seconds EPN 10 minutes 15 seconds

Issue 2

January 1998

Page 1-23Power Interrupti ons

for duration times:

Effects of Power Interruptions

Power holdover is controlled by software in the above manner in order to allow the system to sustain multiple brief power interruptions without exhausting the batteries before they have time to recharge. After power is restored, the batteries are recharged by a circuit that monitors current and time. If the batteries take more than 30 hours to recharge, a minor alarm is raised, indicating that the batteries must be replaced or the charger replaced.

The 397 Battery Charger Circuit immediately detects loss of AC power and raises a warning alarm against AC-POWER that is not reported to INADS. Certain maintenance objects such as external DS1 timing will report major alarms in this situation. When power is restored, the AC-POWER alarm is resolved.

PPN Cabinet with Power Holdover

When power is interrupted to a PPN cabinet, the effects depend upon the duration of the outage. Battery power is supplied to the whole cabinet for 10 seconds. If power is restored during that period, service is not affected. If the interruption exceeds the cabinet holdover period, but is restored before the control carrier holdover expires, all service is dropped and emergency transfer is invoked. The SPE is kept up allowing for a speedy restoration of service since a reboot is not required. All non-SPE circuit packs must be reinserted, taking about a minute, depending on the size of the system. If the interruption exceeds the control carrier holdover, all service is dropped and the system must reboot when

Page 50

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

power is restored, taki n g up t o 15 minut e s, dep en din g on th e size o f the system. Human intervention may be required if central office equipment has been busied out.

555-230-126

EPN Cabinet with Power Holdover

When power is interrupted to an EPN MCC for less than 15 seconds, no service effect results. If the interruption exceeds 15 seconds, only the control carrier is kept up. Circuit packs on other carriers are powered down. Only calls and other services maintained by circuit packs on the control carrier are maintained. For this reason, critical services and those that require a long time to restore (for example, Announcement circuit packs) should be located on control carriers. All service to Port Networks connected to a Switch Node in the EPN is lost. When power is restored, all affected EPNs are reset by system software (see ‘‘

(Expansion Port Network)’’ in Chapter 9, ‘‘Maintenance Object Repair Procedures’’). As with the PPN, a warning alarm is raised against AC-POWER.

External Alarm Leads

Issue 2

January 1998

Page 1-24Protocols

EXP-PN

Each cabinet provides two leads for one major and one minor alarm contact closure that can be connected to external equipment. These are located on the SYSAM and Maintenance circuit packs. If the switch is under warranty or a maintenance agreement, EXT-DEV alarms are generated by the equipment connected to these leads and reported to INADS. These may be used to report failures of UPSs or battery reserves powering the switch. They are also commonly used to monitor adjuncts such as AUDIX.

Protocols

This section describes the protocols handled by the system and the points where these protocols change. Figure 1-9 transmission state changes. Figure 1-9 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.

Not shown in the Figure 1-9 ISDN-BRI transmissions. PRI and BRI D-channels transport information elements 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.

is a pictorial guide through data-

illustrat es the flo w of dat a fro m DT E

is the treatment of D-channels in ISDN-PRI and

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.

Page 51

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

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 2

January 1998

Page 1-25Protocols

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 52

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Issue 2

January 1998

Page 1-26Protocols

ORIGINATING

DCE

RS232C

DATA

MODULE

DATA

MODULE

MODEM

ANALOG ANALOG1 PCMRS232C RS232C

DTE

2 DMIASCII ASCII

3-7

DTE

D I

A L

D I

A L

USER DEFINED

PCM

D I

A L

D I

A L

O G

DESTINATION SYSTEM

MODULE

MODEM

DCE

DATA

RS232CRAW BITSDCP DCP 1

MODEM POOLING

CABLE

DTE

3-7 USER DEFINED

ADU ADUDTE

RS232C RS232CADU PROT ADU PROT1 RAW BITS

3-7 USER DEFINED

DTE

RS232C DS1 FORMATDCP

3-7 USER DEFINED

DATA

MODULE

D I

A L

Figure 1-9. Data Transmission States

VOICE GRADE DATAASCII ASCII 2

DMIASYNCH ASCII ASYNCH ASCII 2

RAW BITS

DMIASCII 2

DTE

DS1 PORT

Page 53

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

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-9

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 2

January 1998

Page 1-27Protocols

■

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 54

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

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 2

January 1998

Page 1-28Protocols

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 Multiple xe d

555-025-204

— Between the originating DCE and the destination

Page 55

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Protocol States

Table 1-5 summarizes the protocols used at various points in the data

transmissi on stream. See Figure 1-9

Table 1-5. Protocol States for Data Communication

Incoming Transmission Type

DTE to

DCE

OSI Layer

Protocols DTE to DCE

Issue 2

January 1998

Page 1-29Protocols

DCE to System Port Inside System

Analog Modem 1 RS-232, RS-449,

or V.35

2 8- or 10-bit code voice-grade data voice-grade data

ADU 1 RS-232 ADU proprietary raw bits

2 asynchronous

8-bit code

Digital Data

Module

Digital

Signal

Level 1

(DS1)

1 RS-232, RS-449,

or V.35 2 8-bit code DMI DMI 1 any DS1 PCM or raw bits 2 8-bit code DMI or voice-

NOTE:

OSI means Open Systems Int erconnect PCM means Pulse Code Modulated DMI means Digital Multiplexed Interface

analog PCM

asynchronous 8-bit code

DCP or BRI raw bits

grade data

DMI

DMI or voice- grade data

Page 56

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

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-6

Table 1-7

Table 1-6. Physical-Layer Protocol Versus Character Code

Protocol Code

RS-232 Asynchronous 8-bit ASCII, and synchronous RS-449 Asynchronous 8-bit ASCII, and synchronous V.35 Synchronous

Table 1-7. Digital Multiplexed Interface (DMI) Mode Versus

Character Code

Issue 2

January 1998

Page 1-30Protocols

and

DMI Mod e Code

0 Synchronous (6 4 kbps) 1 Synchronous (5 6 kbps) 2 Asynchronous 8-bit ASCII (up to 19.2 kbps), and synchronous 3 Asynchronous 8-bit ASCII, and private proprietary

Connectivity Rules

Figure 1-9 implies the following connectivity rules:

■ 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.

Page 57

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

■ Although data entering the system through an EIA port has not been

555-230-126

processed through a data module, the port itself has a built-in data module. I n s i de the sy stem, port data is id enti c a l to d igita l li ne da ta. 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-grade 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 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 .

Issue 2

January 1998

Page 1-31Protocols

■ Although DS1 is commonly called 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.

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.

Page 58

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

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.

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.

Issue 2

January 1998

Page 1-32Protocols

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.

■

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

: if an analog station attempts to transfer two

: if a station conferences all parties, the

: if a station is call forwarded off-premise to a trunk

: if a digital station attempts to

: if a CAS attempts

Table 1-8

lists the various protocols, with applications and maximum limitations.

Page 59

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Table 1-8. Protocols Used in DEFINITY

Maximum

Protocol Applications

Data Rate Maximum Distance

Issue 2

January 1998

Page 1-33Protocols

DCP Digital switch to data

endpoints

RS-232 System 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-449 Processor Interface to

Processor Interface

SSI 715 BCS-2 to Processor

Interface 500 series printers to Processor Interface

64 kbps 5000 feet (1524 m) for dat a

3000 feet (915 m) for voice

19.2 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 kbps 5000 feet (1524 m)

50 feet (15.2 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)

BISYNC Processor Interface line

controller to host comput e r fo r termin a l emulation (9.6 kbps)

BX.25 Communication interface

to MSA, D C S , ISDN, or AUDIX

SDCPI Data module to Processo r

Interface

RS-366 Host computer to ACU

Data module to ACU 64 kbps

V.35 Data module to data

endpoints

2.4 kbps

4.8 kbps

9.6 kbps

64 kbps 17 feet (5.9 m)

50 feet (15.2 m) 17 feet (5.9 m)

56 kbps 50 feet (15.2 m)

Continued on next page

Page 60

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Table 1-8. Protocols Used in DEFINITY — Continued

Maximum

Protocol Applications

Data Rate Maximum Distance

Issue 2

January 1998

Page 1-34Protocols

Category AData modules to terminals

or cluster controller

Data module in ASCII emulation mode

ISDN-BRI Communication interface

to ISDN-BRI S/T

ISDN-BRI U

ISDN-PRI Communication 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 kbps 655 feet (199.3 m) to net work

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 61

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Frequency Response

Table 1-9 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-9. Analog-to-Analog Frequency Response

Frequency (Hz) Maximum Loss (dB) Minimum Loss (dB)

60 —20

200 5 0

300 to 3000 1 -0.5

3200 1.5 -0.5 3400 3 0

Tabl e 1- 10 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.

Issue 2

January 1998

Page 1-35Protocols

Table 1-10. Analog-to-Digital Frequency Response

Frequency (Hz) Maximum Loss (dB) Minimum Loss (dB)

60 — 20

200 3 0

300 to 3000 0.5 -0.25

3200 0.75 -0.25 3400 1.5 0

Page 62

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Insertion Loss for Port-to-Port; Analog or Digital

Table 1-11 lists the insertion loss in the system for different connection types for

the United States. Table 1-12

Table 1-11. Insertion Loss for the United States

Typical Connecti ons

On-premises to on-premises stat ion 6 On-premises to off-premises station 3 Off-premises to off -premises station 0 On-premises station to 4-wire trunk 3 Off-premises station to 4-wire trunk 2 Station-to-trunk 0 Trunk-to-t runk 0

shows the overload and cross-talk characteristics.

Nominal Loss (dB) at 1 k H z

Issue 2

January 1998

Page 1-36Protocols

Table 1-12. Overload and Crosstalk

Overload level +3 dBm0 Crosstalk loss >70 dB

Intermodulation Distortion

Table 1-13 lists the intermodulation distortion in the system for analog-to-analog

and analog-to-digital, up to 9.6 kbps data

Table 1-13. Intermodulation Distortion

Four-Tone Method Distortion

Second-order tone products >46 dB Third-order tone products >56 dB

Page 63

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Quantization Distortion Loss

Table 1-14 lists the quantization distortion loss in the system for analog port to

analog po rt.

Table 1-14. Quantization Dist ortion Loss

Analog Port-to-Analog Port

Signal Level Distortion Loss 0 to -30 dBm0 >33 dB

-40 dBm0 >27 dB

-45 dBm0 >22 dB

Table 1-15 lists the quantization distortion loss in the system for analog port to

digital port and digital port to analog port.

Issue 2

January 1998

Page 1-37Protocols

Table 1-15. Quantization Dist ortion Loss

Analog Port-to-Digital Port or Digital Port- to-Analog Port

Signal Level Di stortion 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 64

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

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-s tati on ERL should meet or exceed 18 dB SFRL

should meet or exceed 12 dB

Station to 4-wire trunk connection ERL should meet or ex ceed 24 dB SFRL

should meet or exceed 14 dB

Station to 2-wire trunk connection ERL should meet or ex ceed 18 dB SFRL

should meet or exceed 12 dB

4-wire to 4-wire trunk connection ERL should meet or ex ceed 27 dB SFRL

should meet or exceed 20 dB

Peak Noise Level

■ Analog to analog — 20 dBrnC (decibels above reference noise with

C-filter)

Issue 2

January 1998

Page 1-38Serv i c e C odes

■ Analo g to di git a l — 19 dBrnC

■ Digital to analog — 13 dBrn C

Echo Path Delay

■ Analog port to analog port — < 3 ms

■ Digital interface port to digital interface port — < 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

■ 9.0P — Partially protected terminal equipment

■ 9.0N — Unprotected terminal equipment

Page 65

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

■ 9.0Y — Totally protected terminal equipment

555-230-126

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 2

January 1998

Page 1-39Facilit y Int erface Codes

Table 1-16

through Table 1-18 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-16. Analog Private Line and Trunk Port Circuit Packs

Service

Circuit Pack FIC

TN742 and TN747B Off-Premises Station Port, and TN746B Off-Premises Station Port or On-Premises Sta tion port

TN760/B/C/D Tie Trun k TL31M 9.0F RJ2GX

0L13C 9.0F RJ21X

Order Code

Network Jack

Table 1-17. Digital Trunk Port Circuit Packs

Circuit Pack FIC

TN1654 and TN574 DS1 Convert er; TN722B DS1 Tie trunk; and TN767 and TN464 DS1 Interface

04DU9B,C 6.0P RJ48C

Service Order Code

Network Jack

and RJ48M

Page 66

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Maintenance Architecture

555-230-126

Table 1-18. MTS and WATS Port Circuit Packs

Circuit Pack FIC

TN742 and TN746B Analog Line 02LS2 None RJ21 and

TN747B Central Office Trunk 02GS2 1.0A RJ21X TN753 DID Trunk 02RV2-T 0,0B RJ21X TN790 Processor 02LS2 1.0A RJ21X TN1648 System Access and

Maintenance

02LS2 0.5A RJ21X

Multimed ia I nt er face (M MI )

Ringer Equivalen cy Number (REN)

Issue 2

January 1998

Page 1-40Multimedia Interface (MMI)

Network Jack

RJ11C

The Multimedia Interface handles the following protocols:

■ International Telecommunicat ions Union (ITU) H.221 — Includes H.230,

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

■ BONDIN G ( B a ndw idth On De m a nd INoperab ilit y G ro up) 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 Cor e ( W C C ) BR I int e rface, mos t desk t o p multime dia applications are supported through a personal computer’s BRI interface.

Page 67

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

The DEFINITY System supports a variety of configurations consisting of a PPN and up to 21 EPNs. In addition, the system may use a Center Stage Switch (CSS) consisting of one or two Switch Nodes. This chapter describes the PPN and EPN cabinets, and the configuration of carriers and circuit packs within these cabinets.

555-230-126

Issue 2

January 1998

Page 2-1Multi-Carrier Cabinet

Multi- Ca r rier Cabinet

The Multi-Carrier Cabinet (J58890A) accommodates from one to five circuit pack carriers, and is always used for the PPN. EPNs may use either multicarrier cabinets or single-carrier cabinets.

The power unit in the bottom of the MCC cabinet supplies AC voltage or DC voltage from an external source to the power supply in each carrier. The AC powered cabinet optionally contains a battery charger and backup batteries to provide temporary power to the cabinet if the external source fails. The backup unit is optional for systems powered from an Uninterruptible Power Supply (UPS). The fan unit in the middle of the cabinet cools the carriers. AC-powered cabinets have two 120V AC receptacles in the back for use as an AC power source. These can be used to power the G3-MT.

Each cabinet must be connected to one of the following dedicated power sources:

■ 120V AC 60 Hz at 50A from a National Electrical Manufacturing

Association (NEMA) 5-50R power outlet or equivalent

■ Single phase 240V AC, or three phase 208V AC, 60 Hz at 30A from a

NEMA L 14-30R power outlet or equivalent

Page 68

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

■ -48V DC battery plant

■ Global MCC uses 50-60 Hz at 200-240 VAC power source

555-230-126

Issue 2

January 1998

Page 2-2Multi-Carrier Cabinet

Port

Carrier

J58890BB

Port

Carrier

J58890BB

Port

Carrier

J58890BB

Port

Carrier

J58890BB

PPN Control

Distribution

Unit (G Carrier)

Carrier

J58890AP

Power

Duplicated

PPN Control

Carrier

J58890AP

Duplicated

Switch

Carrier

J58890SA

Switch

Carrier

J58890SA

Processor Port Network

Node

C Carrier

B Carrier

A Carrier

Fan Unit

D Carrier

E Carrier

Port

Carrier

J58890BB

Port

Carrier

J58890BB

Expansion

Control

Carrier

J58890AF

Port

Carrier

J58890BB

Port

Carrier

J58890BB

Distribution

Unit (G Carrier)

Power

Duplicated

Switch

Carrier

J58890SA

Switch

Carrier

J58890SA

Expansion Port Network

Node

Figure 2-1. Multicarr i er Cabinet (J 58890A) Configurations

Processor Port Network Cabinet

The PPN cabinet, pictured above, is the primary cabinet in all G3r systems. It contains the Switch Processing Element (SPE) that controls the system and one Port Network that is interconnected by the daisy-chained TDM/LAN bus. If the system has a CSS, the PPN cabinet also contains a switch node. The individual carriers are described in following sections.

The A position always contains a PPN Control Carrier (J58890AP), also known as the Processor Carrier, which holds the SPE circuit packs. If the system has a duplicated SPE, the B position holds a second PPN Control Carrier. At least one, and up to four, Port Carriers (J58890BB) can be located in the other four carrier positions, depending on traffic needs and whether the system uses those positions for other types of carriers. In general, Port Carriers are added in the sequence, B-C-D-E, unless those positions are used otherwise, as follows.

Page 69

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

If the system has a Center Stage Switch, the E position holds a Switch Node Carrier. In a CSS system with duplicated PNC, the D position holds a Switch Node Carrier that duplicates the one in E position. In large systems requiring a CSS with two Switch Nodes, the second SN is located in an EPN cabinet, for both simplex and duplicated systems. Systems th at have added a CSS configurat ion after the original installation may have their first SN in an EPN cabinet.

555-230-126

Expansion Port Network Cabinets

When used for an EPN, the multicarrier cabinet supports one Port Network with a daisy-chained TDM/LAN bus, or, optionally, two separate PNs if the cabinet does not contain a Switch Node. A cabinet with two PNs has two separate TDM/LAN bus daisy-chains. One TDM/LAN bus between carriers in positions A, B and C supports the first PN, and another TDM/LAN bus between positions D and E supports the second PN. Figure 2-1

Each EPN cabinet contains one Expansion Control Carrier (J58890AF) located in the A position. In cabinets with one PN, up to four Port Carriers are added as needed in the sequence B-C-D-E, unless the D or E positions are used for a Switch Node. Cabinets with two PNs use optional Port Carriers in the B position, and then the C position for the first PN (above the fans). The second PN, (below the fans), is configured with the first Port Carrier in the E position and an optional second Port Carrier in D position.

shows locations of carriers in EPN cabinets.

Issue 2

January 1998

Page 2-3Carriers in Multi-Carrier Cabinets

In large systems with a CSS that requires two Switch Nodes, the second SN is located in an EPN cabinet (this is usually cabinet number 2, PN number 2). This EPN may not be remoted by a DS1CONV complex. An EPN with an SN has a Switch Node Carrier in E position. In systems with duplicated PNC, (Critical Reliability option), the D position holds another Switch Node Carrier that duplicates the one in E position.

Carriers in Multi-Carrier Cabinets

PPN Control Carrier (J58890AP)

The PPN Control Carrier contains dedicated slots used for circuit packs that compose the switch processing element (SPE). It does not contain port circuit pack slots. This carrier always resides in position A of the PPN cabinet. In a system with a duplicated SPE, a second PPN Control Carrier resides in the B position of the PPN cabinet.

Page 70

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

555-230-126

Table 2-1 describes the function of each slot in the PPN Control Carrier.

Table 2-1. PPN Control Carrier Circuit Pack Slots

Slot Name Circuit Pack Code Notes

Issue 2

January 1998

Page 2-4Carriers in Multi-Carrier Cabinets

POWER UNIT (right side)

SYS ACCESS/ MAINTENANCE

DUP INTFC Duplication Interface UN330B Required for systems with dupl icated

PROCR RISC Processor UN331B Required TEST INTFC Used by field support to connect

MEMORY 1 to 4 32 Mbyte Memory TN1650B Two required, up to four optional,

PACKET INTFC 1 to 3

TONE-CLOCK Tone-Clock TN780

MSS/ NET CON Mass Storage System/

DISK DRIVE Disk Drive TN1657 Required TAPE DRIVE Tape Drive TN1656 Required

Power Unit (+5V)

System Access and Maintenance

Packet Interface TN1655 One required, two sl ots reserved for

Network Control

649A Required for DC-powered systems. TRI

PLS OUTPUT DC-Powered cabinets

TN1648 Required

SPE

diagnostic equipm ent

Release 5 requires 3

future use; with duplicated SPE, both carriers must use same slot

Required; TN780 required for interface

TN2182 UN332 Required

to external Stratum 3 Clock

Page 71

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

555-230-126

Port Carrier (J58890BB)

Table 2-2 describes the function of each carrier slot.

Table 2-2. Port Carrier Circuit Pack Slots

Test

Error Code Circuit Pack

Result Description/ Recommendation

Issue 2

January 1998

Page 2-5Carriers in Multi-Carrier Cabinets

POWER UNIT (right side)

POWER UNIT/ SERVICE

TONECLOCK 1

Power Unit (+5V)

Power Unit, Neon

Call Classifi er TN744 Integrated

Announcement Speech

Synthesizer

Tone Detector TN748,

Maintenance/ Test

Tone-clock TN768

649A Required for DC-powered systems. TRI

TN755B This position is addressed as “00” in

TN750

TN725B, TN433, TN457

TN420B TN771D

TN2182

PLS OUTPUT DC-Powered

commands and displays . It does not provide tip and ring to the wall field. The following circui t packs are optional, depending on system features. One TN771D is required in all PPNs, and one in each EPN of Criti cal Reliabil it y systems.

Required as follows: EPN with duplicated PNC: B carrier EPN cabinet with two PNs: D carrier E carrier of an EPN cabinet with two PNs and duplicated PNC; the Tone-clock slot is located with Port Slot #2. If the carrier does not contain a Tone-Clock boa rd, any port board may be installed in this slot.

EXPN INTFC 2Expansion

Interface

3 If the system’s conn ectivity and

4 to 20 Port Boards Any common port board.

TN570 Optional, depending on system’ s

connectivity and duplication configuration; if not used for an EI board, this slot can accept any common port board.

duplication configuration requi re a second EI on a port carrier, it resides in this slot; otherwise, this slot accept s any common port board.

Continued on next page

Page 72

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

555-230-126

Expansion Control Carrier (J58890AF)

The Expansion Control Carrier is located in position A of each EPN. Table 2-3 describes the function of each carrier slot.

Table 2-3. Expansion Control Carrier Slots

Slot Name Circuit Pack Code Notes

POWER UNIT (left side)

MAINTENANCE M aintenan ce TN775B Required TONE-CLOCK Ton e-Clock TN2182 Required

Power Unit (+5V)

Issue 2

January 1998

Page 2-6Carriers in Multi-Carrier Cabinets

631DA1 R equir ed for

AC-powered systems

644A1 Required for

DC-powered systems or empty

EXPN INTFC Expansion

TN570 Required

Interface

2 to 19 Port Boards Any common port

board. Slot 2 may house a second EI if the configuration requires one.

POWER UNIT/ 18, 19

Power Unit, Neon TN755B Required for certain

features; otherwise will accept any common port board .

POWER UNIT (right side)

Power Unit (-48V/-5V)

631DB1 R equir ed for

AC-powered systems

645B1 Required for

DC-powered systems

649A TRI PLS OUTPUT for

Release 5 DC-Powered cabinets

Page 73

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

555-230-126

Switch Node Carrier (J58890SA)

Switch Node carriers house the components of a Center Stage Switch (CSS). The first switch node is located in carrier E of the PPN. If duplicated in a Critical Reliability configuration, its duplicate is located in carrier D of the PPN. The second switch node is located in carrier E of a non-remoted EPN. If duplicated in a Critical Reliability configuration, its duplicate is located in carrier D of the same EPN.

Table 2-4. Switch Node Carrier Circuit Pack Slots

Circuit

Slot Name

Pack Code Notes

Issue 2

January 1998

Page 2-7Carriers in Multi-Carrier Cabinets

POWER UNIT (right side)

EXPN INTFC DS1 CONV/ 1

2 to 9, 13 to 20 Switch

SWITCH NODE CLOCK / 10

SWITCH NODE CLOCK / 12

DS1 CONV/ 21 DS1CONV TN574 Used as abo ve in conjunction with an SNI in

Power Unit (+5V)

DS1 Converter

Expansion Interface

Node Interface

Switch Node Clock

649A Required for DC-powered systems

TN574 Provides fiber connect ivity from DS1 facilities

to a remote EPN; this slot used in conj uncti on with an SNI in one of slots 2 to 9.

TN570 Used for an EI board only in the PPN cabinet

in a system with duplicated PNC (Critical Reliability); used in conjun ction with adj acent SNI

TN573 SNIs are added sequentially as needed

beginning with slot 2. If a second switch node is needed, (for more than 16 EPNs), up to 5 SNIs (those in slots 7, 8, 9, 13 and 14) are connected to corr esponding SNIs in the other SN.

TN572 Required

TN572 Used in High Reliability option only

(duplicated SPE, si mplex PNC)

one of slots 13 to 20

Continued on next page

Page 74

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

555-230-126

PNC Cabling — Fiber Hardware

The term “fibe r” is used to refer to all the hardware needed for the three basic types of connections used to form multi-PN systems. Fiber administration specifies the endpoints to be connected, optional DS1 CONV locations, and parameters for DS1 Facility Line encoding and equalization. The 3 connection types ar e:

1. EI-to-EI or EI-to-SNI Intercabinet hardware

2. EI-to-SNI or EI-to-EI intracabinet hardware

3. EI-DS1CONV or SNI-DS1CONV hardware

EI-to-EI or EI-to-SNI Intercabi net Fiber Optic Cables

EI-to-EI or EI-to-SNI intercabinet connections are implemented by installing a lightwave transceiver on the I/O connector plate for each of the administered fiber endpoints. Each lightwave transceiver has a receive and a transmit connector for a 62.5 micron or 50 micron fiber connection. Standard fibers are available in various lengths up to 150 feet (46 m) for single-mode fiber and up to 200 feet (61 m) for multi-mode fiber. These fibers are used to connect lightwave transceivers to each other when they are close enough together, or to optical cross-connect facilities fo r grea ter dist ance s.

Issue 2

January 1998

Page 2-8PNC Cabling — Fiber Hardware

The lightwave transceivers are powered from I/O connector plate leads attached to TN570 Expansion Interface circuit pack or a TN573 Switch Node Interface circuit pack. The transceivers include loop-around capabilities to support fiber fault isolation. Either of two different 9823-type multi-mode transceivers may be used, depending upon the length of the fiber (table below), or the 300A single mode fiber transceiver. The transceivers at each end of a given fiber should match. Figure 2-2

Part

Number Maximum Fiber Leng th Fiber Mod e

9823A 4900 feet (1494 m) Multi-mode 9823B 25,000 feet (7620 m) Multi-mode 300A 22 miles (35.4 km) Single mode

illustrates the interconnection of fiber optic hardware.

Page 75

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

555-230-126

Issue 2

January 1998

Page 2-9PNC Cabling — Fiber Hardware

9823-Type Lightwave

Transceiver

To I/O

Connector

Plate

9823-Type

Lightwave

Transceiver

To I/O

Connector

Plate

FL2P-P-xx Fiber-Optic

Cables

FL2P-P-xx

Fiber-Optic

Cables

100A

LIU

Optical Cross-Connect Facility

100A

LIU

FL2P-P-xx

Fiber-Optic

Cables

9823-Type

Lightwave

Transceiver

To I/O

Connector

Plate

9823-Type Lightwave

Transceiver

To I/O

Connector

Plate

Figure 2-2. Fiber Link Connection Hardware

Page 76

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

555-230-126

EI-to-SNI or EI-to-EI Intracabi net Metallic Cabling

Metallic cable m ay b e sub stitut ed fo r op tica l cabl e for “fiber ” connections between EIs or between an EI and an SNI in the same MCC cabinet. The same I/O plate connectors are used. The metallic cables should not be used for intercabinet connections, since doing so violates system ground integrity. The metallic cable comes in two lengths.

Part No. Length Intended use

Issue 2

January 1998

Page 2-10PNC Cabling — Fiber Hardware

H600-278,G1 13 inches (33

H600-278,G2 66 inches

DS1 CONV Cabling

Digital services (DS1) can be used to connect PNs that are up to 100 miles (161 km) apart when fiber optic cabling is not practical. Multi-mode (fiber-connected PNs must be less than 25,000 feet (7620 m) and less than 22 miles (35.4 km) for single- mode fiber from the PPN.) A TN574 or TN1654 DS1 Converter (DS1 CONV) circuit pack serves as the interface between the network and an EI or SNI on the switch. DS1 cabling on a carrier consists of a Y-cable that connects a DS1 CONV to an EI or SNI and to the network. The following cables may be used, depending upon where the DS1 CONV and the EI or SNI are located:

Connection Type Length

On same half carrier 1 foot (30.48 cm) 846448637 847245750 On different half

carriers in sa me cabinet

Between two adjacent cabinet s

From an EI in slot 1 of a switch node carrier to an

cm)

(168 cm)

5.5 feet (1.68 m) 846448645 847245768

1 foot (30.48 cm), used with two 9823As, and 1 20-foot (6.1 m) fiber optic cable

SNI in the same half of the carrier (usually the adjacent slot )

From an EI to an SNI in the same cabinet, but in a different carrier or different hal f of a carrier

Comcode

Number

TN574

846448652, and one 846885259 bracket

Comcode

Number

TN1654

847245776 with one 846885259 bracket

Page 77

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

555-230-126

The DS1 CONV to EI/SNI cable is a shielded metallic Y-cable held in place at the EI/SNI port connector by a 4B retainer and at the DS1 CONV port connector by a 4C retainer. The cable end with one 25-pair amphenol connector attaches to the I/O Plate connector for the EI or SNI. The end with two 25-pair amphenol connectors attaches to the DS1 CONV I/O Plate connector.

The 13-inch cable 846448652 or 847245776 connects the DS1 CONV to a fiber-optic cable, enabling the DS1 CONV to connect to an EI or SNI at a greater distance. The cable end with one 25-pair amphenol connecto r attaches to a lightwave transceiver using the 846885259 bracket. The end with two 25-pair amphenol connectors attaches to the DS1 CONV I/O Plate connector. The other end of the fiber-optic cable connects to a lightwave transceiver attached to the I/O plate connector of the EI or SNI.

An H600-348 cable connects the DS1 CONV cable to a Channel Service Unit (CSU), which connects to a wall field. (Alternatively, connection is sometimes made directly from the Y-cable to the wall field. See the pinout for the 50-pin connector at the end of the Fiber Fault Isolation Procedure in Chapter 5,

‘‘Responding to Alarms and Errors’’.) This cable provides from one to four DS1

connections. One end of the H600-348 cable is plugged into the 50-pin amphenol piggy-back connect or on the 8464486x x cable connec ted to the DS1CONV port connector. The other end of the H600-348 cable has four 15-pin sub-miniature D-type connectors that plug into the CSU. A pinout of this cable appears the end of the Fiber Fault Isolation Procedure in Chapter 5. H600-348 cables come in the following lengths:

Issue 2

January 1998

Page 2-11PNC Cabling — Fiber Hardware

Group No. Length Group No. Length

G1 25 feet (7.62 m) G5 125 feet (38.1 m) G2 50 feet (15.24 m) G6 200 feet (60.96 m) G3 75 feet (22.86 m) G7 400 feet (121.9 m) G4 100 feet (30. 48 m) G8 650 feet (198 m)

Page 78

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

DS1C

G3r

CABINET

TN570

CIRCUIT

PACK

TN573

CIRCUIT

PACK

TN574

CIRCUIT

PACK

846448637

846448645

(SEE NOTE 3)

FULLY DUPLICATED

PPN

G3r

CABINET

SEE NOTE 1

TN573

CIRCUIT

PACK

TN573

CIRCUIT

PACK

SEE NOTE 1

9823A 9823A

FL2P-XX

9823A 9823A

650 FEET

H600-348,G-()

EPN

G3r

CABINET

CIRCUIT

(SEE NOTE 3)

TN574

PACK

TN574

PACK

846448652

555-230-126

100 MILES

(SEE NOTE 2)

CROSS

CONNECT

FIELD

CSU CSU

FOR DIRECT CROSS CONNECT -

SEE TEXT

650 FEET 650 FEET

H600-348,G()

CSU CSU

FOR DIRECT CROSS CONNECT -

100 MILES

(SEE NOTE 2)

CROSS

CONNECT

FIELD

CROSS

CONNECT

FIELD

SEE TEXT

650 FEET

MAX

H600-348,G-()

H600-348,G()

846448637

TN570

CIRCUIT

TN574

CIRCUIT

846448637

PACK

G3r EPN

CABINET

TN570

CIRCUIT

PACK

TN574

CIRCUIT

PACK

TN570

CIRCUIT

PACK

TN574

CIRCUIT

PACK

G3r EPN

CABINET

Issue 2

January 1998

Page 2-12Circuit Packs

SEE NOTE 1

Figure 2-3. Typic al DS1 CONV Connections to Remote EPNs

1. Place duplicate pairs in different carriers.

2. When removing two or more, the maximum cable distance between any two remoted end points is 100 miles (161 km). For example, if the EPN is 75 miles (121 km) from the PPN, then EPN 2 can only be 25 miles (40.2 km) from the PPN.

3. 846447637 is used within a carrier for a TN574, for TN1654 within a carrier use a 847245750.

846448645 is used within a cabinet between carriers for a TN574, for TN1654 within a cabinet between carriers use a 847245768.

Circui t Pa c ks

The following tables list all circuit packs supported by DEFINITY Systems. For information concerning vintages and current versions, see

Circuit Pack Vintages and Change Notices

special edition of the

Lucent Technical Monthly

which is published periodically as a

Reference Guide for

Page 79

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

Table 2-5. Circuit packs and modules

supported by DEFINITY

Apparatus

Code Name Type

631DA1 AC Power Unit Power 631DB1 AC Power Unit Power 644A1 DC Power Unit Power 645B1 DC Power Unit Power 649A DC Power Unit Power 676B DC Power Supply Power 982LS Current Lim iter Po wer CFY1B Current Limiter Power CPP1 Memory Expansion Control

555-230-126

Issue 2

January 1998

Page 2-13Circuit Packs

ED-1E546 (TN2169) (TN2170) (TN566) (TN567)

ED-1E546 (TN2208) (TN2170)

J58890MAP (TN800)

TN417 Auxiliary Trunk Port TN419B Tone-Clock Control TN420B/C Tone Detector Service TN429 Direct Inward/Outward Dialing (DIOD) Trunk Port TN433 Speech Synthesizer Service TN436B Direct Inward Dialing Trunk Port TN437 Tie Trunk Port TN438B Central Offi ce Trunk Port TN439 Tie Trunk Port TN447 Central Office Trunk Port

DEFINITY AUDIX R3 System Port Assembly

Call Visor ASAI over the DEFINITY (LAN) Gateway R1 Port Assembly

CallVisor over the DEFINI TY LAN Gateway R2 Port Assembl y

TN457 Speech Synthesizer Service TN458 Tie Trunk Port

Continued on next page

Page 80

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

Table 2-5. Circuit packs and modules

supported by DEFINITY — Continued

Apparatus

Code Name Type

TN459B Direct Inward Dialing Trunk Port TN464C/D/E/F DS1 Interface - T1, 24 Channel - E1, 32 Channel Port TN465/B/C Central Office Trunk Po rt TN467 Analog Line Port TN468B Analog Line Port TN479 Analog Line Port TN497 Tie Trunk Port TN553 Packet Data Line Port TN556/B ISDN-BRI 4-Wire S/T-NT Line (A-Law) Port TN570/B/C Expansion Interf ace Port

555-230-126

Issue 2

January 1998

Page 2-14Circuit Packs

TN572 Switch Node Clock Control TN573/B Switch Node Interface Control TN574 DS1 Converter - T1, 24 Channel Port TN577 Packet Gateway Port TN722B DS1 Tie Trunk Port TN725B Speech Synthesizer Service TN726/B Data Line Port TN735 MET Line Port TN742 Analog Line Port TN744/B Call Classifier Service TN744/C/D Call Class if ier - Detector Service TN746/B Analog Line Port TN747B Central Offi ce Trunk Port TN748/B/C/D Tone Detector Service TN750/B/C Announcement Service TN753 Direct Inward Dialing Trunk Port TN754/B Digital Line 4-Wire DCP Port TN755B Neon Power Unit Power TN756 Tone Detector Service

Continued on next page

Page 81

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

Table 2-5. Circuit packs and modules

supported by DEFINITY — Continued

Apparatus

Code Name Type

TN758 Pooled Modem Port TN760B/C/D Tie Trunk Port TN762B Hybrid Line Port TN763B/C/D Auxiliary Trunk Port TN765 Processor Interface Control TN767B/C/D/E DS1 Interface - T1, 24 Channel Port TN768 Tone-Clock Control TN769 Analog Line Port TN771D Maintenance/Test Service TN772 Duplication Interface Control

555-230-126

Issue 2

January 1998

Page 2-15Circuit Packs

TN773 Processor Control TN775/B Maintenance Service TN776 Expansion In ter face Port TN777/B Network Control Control TN778 Packet Control Control TN780 Tone-Clock Control TN786 Processor Control TN786B Processor Control TN787F/G Multimedia Interface Service TN788B Multimedia Voice Conditioner Service TN789 Radio Controller Control TN790 Processor Control TN793 Analog Line, 24-Port, 2-Wire Port TN796B Processor Control TNPRI/BRI PRI to BRI Converter Port TN1648 System Access/Maintenance Control TN1650B Memory Control TN1654 DS1 Converter - T1, 24 Channel/E1, 32 Channel Port TN1655 Packet Interface Control

Continued on next page

Page 82

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

Table 2-5. Circuit packs and modules

supported by DEFINITY — Continued

Apparatus

Code Name Type

TN1656 Tape Drive Control TN1657 Disk Drive Control TN2135 Analog Line Port TN2136 Digital Line 2-Wire DCP Port TN2138 Central Office Trunk Port TN2139 Direct Inward Dialing Trunk Port TN2140/B Tie Trunk Port TN2144 Analog Line Port TN2146 Direct Inward Dialing Trunk Port TN2147/C Central Office Trunk Port

555-230-126

Issue 2

January 1998

Page 2-16Circuit Packs

TN2149 Analog Line Port TN2180 Analog Line Port TN2181 Digital Line 2-Wire DCP Port TN2182/B Tone-Clock -Tone Detector and Call Classif ier Contr ol TN2183 Analog Line Port TN2184 DIOD Trunk Port TN2198 ISDN-BRI 2-Wire U Interface Port TN2199 Central Office Trunk Port TN2202 Ring Generator Power TN2224 Digital Line, 24-Port, 2-Wire DCP Port UN330B Duplication Interface Control UN331B Processor Control UN332 Mass Storage/Network Control Control WP-90510 AC Power Supply (Compact Single-Carrier Cabinet) Power WP-91153 AC Power Supply (Single-Carrier Cabinet) Power

Continued on next page

Page 83

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

555-230-126

Duplication: Reliability Options

Standard Reliability Option

On Standard Reliability systems, the 512-time-slot TDM bus is divided into two duplicate 256-time-slot buses, A and B. Call traffic is shared between the two buses. The first 5 time slots on each bus are reserved for the control channel, which is active on only one of the two buses at a time. Likewise, the next 17 time slots are reserved for carrying system tones. The tone times slot are not necessarily on the same bus (A or B) as the control channel. If any failure takes place that affects the ability of the active control or tone time slots to function, the other bus becomes active for those time slots.

High Reliability Option

High Rel iability systems duplicate components that are critical to the viability of the system as a whole to prevent a single failure from dropping all service:

Issue 2

January 1998

Page 2-17Duplication: Reliability Options

■ PPN control carrier and carrier power units (OLSs)

■ All SPE circuit packs: Processor, Memory, MSSNET, Disk, Tape, SYSAM,

Duplication Interface, and carrier power units (OLSs)

■ PPN Tone Clock circuit pack (EPN Tone-Clocks are not duplicated)

■ TDM buses (described above)

In addition to the above, the following are duplicated in Center Stage Switch (CSS) configurations:

■ The PPN to CSS fiber link (consisting of the PPN Expansion Interface

circuit packs, the Switch Node Interface circuit packs that connect to the PPN EIs, and cabling from the PPN EI to the CSS)

■ Switch Node Clocks (SNCs) (two; on each Switch Node carrier)

The duplicated SPEs operate in active/standby fashion. Interchanges of the SPE and of PPN Tone-Clocks operate independently unless induced by use of the SPE-select switches. The 2 SNCs on each Switch Node carrier also operate in an active/standby manner.

The duplicated fiber link between the PPN EIs and the CSS (the cable may actually be metallic) do not use an active/standby strategy. Instead, both links simultaneously carry active call traffic and control connectivity in an equally distributed load-sharing manner. If a component fails one of these fiber links, all connectivity over it on it is torn down, resulting in some dropped calls and control and application links. Links and subsequent call service is immediately re-established over the other EI fiber link.

Page 84

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Hardware Configurations

555-230-126

Critical R el iab ili ty O ption

Critical Reliability systems include all of the features of the High Reliability option described above. Additionally, the duplicate com ponen ts of Port Network Connectivity (PNC) and other components critical to the viability of each EPN.

■ Switch Node carriers and carrier power supplies (OLSs)

■ Switch Node Interface (SNI) circuit packs

■ Switch Node Clock (SNC) circuit packs (one on each duplicated Switch

Node carrier)

■ PPN and EPN Tone-Clock circuit packs

■ PPN and EPN Expansion Interface circuit packs

■ Each EPN contains a TN771D Maintenance/T est circuit pack

■ Inter-PN cabling

■ DS1 Converter Complexes (circuit packs, cabling and DS1 facilities used

to connect remote EPNs)

Issue 2

January 1998

Page 2-18Duplication: Reliability Options

The entire PNC (whether direct connect or CSS connected) is duplicated as a whole, forming two identical sets which each function as a whole (A-PNC and B-PNC). The 2 PNCs operate in an active/standby manner with all inter-PN calls set up on both PNCs so that the active can assume control without disruption of service. Operation of PNC duplication is described under PNC-DUP in Chapter

9, ‘‘Maintenance Objec t Repair Procedures’’.

The Tone-Clocks in each EPN operate in an active/standby manner independently from other duplication strategies.

Page 85

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

The management terminal is used to enter commands and monitor operations through the maintenance user interface. Chapter 8, ‘‘

describes the commands available to the maintenanc e user.

555-230-126

Issue 2

January 1998

Page 3-1Terminals Supported

Maintenance Commands’’

Terminals Supported

Refer to

Test for Multi-Carrier Cabinets

setup instructions.

DEFINITY Enterprise Communications Server Release 5 Installation and

Multiple Ac ce ss

Release 6r allows multiple users to perform maintenance and administration at the same time:

■ This system has a security feature to allow the customer to define their

own logins and passwords and to specify a set of commands for each login. It allows up to 11 customer and 4 services logins. Each login name can be customized.

■ Login Security Violation Notification Following a Security Violation and

Login Kill after “N” Attempts features notifies a referral point, and disables a login ID (Customer or Lucent Services logins) following a security violation (a user defined security violation threshold). The Login Kill after “N” Attempts feature will not disable the last remaining inads type login. Lucent Services logins require a Lucent init level login ID to re-enable logins that have been disabled by a security violation or the command disable login.

, and the user manual on your terminal model for

Page 86

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

■

Logoff Notification (Release 5)

555-230-126

alerts system administrators, during log off from the system administration and maintenance interface, of possible system maintenance problems. This notification also alerts the system administrators that features that present a significant security risk are enabled. A message displays on the system administration/maintenance interface during logoff if a security risk feature is enabled. Additionally, the user can be required to acknowledge the notification before the logoff is completed.

■ The system is delivered to the customer with one “super-user” login and

password defined. The customer is required to administer any additional login and passwords. The super-user login has full customer permissions and can customize any login that they create. Login permissions are set by the super-user to allow or block any object that can affect the health of the switch. Up to 40 administration or maintenance objects (commands) can be blocked for a specified login.

■ Two maintenance logins are reserved for the SYSAM-RMT and

SYSAM-LCL ports on the TN1648 SYSAM circuit pack located on PPN control carriers. SYSAM-RMT is a dial-up remote access port reserved for use by INADS. SYSAM-LCL is accessed by RS2 32 connectors on the TN1648. Two other maintenance users can log in by dial-up System Access Ports (SAPs) or by connecting directly to EPN Maintenance circuit packs.

Issue 2

January 1998

Page 3-2Switch-Based Bulletin Board

■ Up to 5 maintenance and 5 administration commands can run

concurrently. Some commands that use the same resources as others experience contention and cannot be run at the same time. For more information on contention, see ‘‘

Commands’’ in Chapter 8, ‘‘Maintenance Commands’’.

Switch-Based Bulletin Board

This feature allows a System Access Terminal (SAT) user to leave messages in the system in order to communicate with other system users.

NOTE:

This feature does not substitute for any existing procedures for escalating problems. It is only an aid to the existing process.

Descrip tion

The bulletin board service provides an easy interface for the customer and Lucent to leave messages on the system.

The bulletin board feature makes it easy for the customer to communicate with Lucent (and vise versa). For example, when a new load is installed on a switch in the customer's system, Lucent is able to leave the customer messages that describe any new functions. It also allow Lucent to keep you informed on the progress of trouble items. In addition, you can use this feature to provide

Contention Between Simultaneous

Page 87

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

555-230-126

additional information concerning problems that have already been escalated by the normal procedure.

Accessing the Bulletin Board

Any user with the appropriate permissions can log into the system and have

access to the bulletin board. Users that have “Maintain System” or “Administer Features” permissions can enter, change, display, print, or schedule to print a message. Users that have “Display Admin” and “Maint ain Data” permiss ion 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 a user logs on to the system they are notified of any messages on the bulletin board. The notification message indicates the last time the bulletin board was updated, if any “High-Priority” message exist, and if the bulletin board is 80% or more f ull. If a “Hig h -Pr iority” me s sag e e x is ts, the co m mand prom pt w ill change to the following message:

■ High-Priority Bulletin Board Messages Entered:

Issue 2

January 1998

Page 3-3Switch-Based Bulletin Board

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.

■ You, the user must maintain the information stored on the bulletin board. It

is your 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 40 characters per line. The first 10 lines of text on page 1 are reserved for Lucent 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.

To edit or enter a message on the Switch Based Bulletin Board you must:

1. Log into the system with “Maintain System or Administer Features” Permissions.

2. Enter the command change bulletin-board.

Page 88

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

555-230-126

3. Follow system prompts.

To display messages on the Switch Based Bulletin Board you must:

1. Log into the system with “Maintain Syste m” , “Display Admin ,” or “Maint

Data” permissions.

2. Enter the command displa y bull etin boa rd.

3. Follow system prompts.

Editing a Switch-Based Bulletin Board Message

As stated before, a message may contain up to three pages of information with the first 10 lines on page 1 reserved for Lucent Service’s (the “INIT”, “INADS”, and “craft” logins can edit the first 10 lines on page one). Pages 2 and 3 will allo w up to 20 lines of 40 cha racters of tex t. Each line has a date field to show when 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:

High-Priority

Issue 2

January 1998

Page 3-4Switch-Based Bulletin Board

messages

■ Uppercase/Lowercase letters, spaces, numerals, and !@#$%^&*()_

-+=[]{};’”<>./?.

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 which cause 2 or more consecutive blank lines the bulletin board is automatically reorganized (upon submittal). Two or more blank lines are changed to a single blank line. A blank line is at the top of a form is also deleted. This prevent holes in the bulletin board screens as old entries are deleted.

To save a message entered into the bulletin board text field, you must execute the save translation command.

The following screen, is an example of bulletin board messages between Lucent and a customer that is having trouble with trunk group translations:

Page 89

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

display bulletin-board Page 1 of 3

555-230-126

Issue 2

January 1998

Page 3-5Switch-Based Bulletin Board Message Notification

Messages (* indicates high-priority) Date

* 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

* Lucent is in the process of 02/02/95

Switch-Based Bulletin Board Message Notification

When a user logs on to the system they are notified of any messages on the bulletin board. The notification message indicates the last time the bulletin board

was updated, if any “High-Priority” message exist and if the bulletin board is 80% or more full. If a “High-Priority” message exists, the command prompt changes to the following message:

High-Priority Bulletin Board Messages Entered:

To Log In

After the next command is entered, the default command prompt returns to the screen.

To log in to the switch:

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.

The password aging screen (Screen 3-1

) is displayed when a user logs in. If the user’s password is expired, the user is prompted to enter a new password. If your password is within 7 days of the expiration date you see:

Page 90

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

Login: telmgr Password: Your Password has expired, enter a new one. Reenter Current Password: Old Password: New Password: Reenter New Password:

555-230-126

Screen 3-1. Password Aging Screen

Forced Password Aging and Administrable Logins for G3V3 and Later Releases

G3V3 and later releases provide enhanced login/password 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 must 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.

Issue 2

January 1998

Page 3-6Switch-Based Bulletin Board Message Notification

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 System Access Terminal is available for use, try executing the command again.

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 his/her 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 cl ear measu rements security-violations command is entered. Once a non-super-user has changed his/her password, the user must wait 24 hours to change the password again.

V4 security is enhanced by providing a logoff notification screen to a system administrator when he/she logs off while either the facility test call or remote access features are still administered. The administrator can be required to acknowledge the notification before completing th e logoff process. Logoff notification is administered on the Login Administration screen.

The system is delivered to the customer with one customer “super-user” login/password defined. The customer is required to administer add itional login/passwords as needed. The super-user login has full customer permissions and can customize any login that he/she creates.

Page 91

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

555-230-126

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. When an object (administrative or maintenance command) is entered in the blocked object list on the Command Permissions Categories Restricted Object List form, the associated administrative or maintenance actions cannot be performed by the specified login.

There are 3 command categories. Each of the 3 command categories has a group of command subcategories listed und er them, and each command subcategory has a list of command objects that the commands acts on. See Table 3-1 and Table 3-2 for a list of objects. A super-user can set a users permissions to restrict or block access to any command in these categories. The 3 categories are:

■ Common Commands

— Display Admin. and Maint. Data — System Measurements

■ Administration Commands

Issue 2

January 1998

Page 3-7Switch-Based Bulletin Board Message Notification

To Log In

— Administer Stations — Administer Trunks — Additional Restrictions — Administer Features — Adm inister Perm is sio ns

■ Maintenance Commands

— Maintain Stations — Maintain Trunks — Maintain System s — Maintain Switch Circuit Packs — Maintain Process Circuit Packs

These categories are displayed on the Command Permissions Categories form.

To log in to the switch:

1. Enter your login name and password on the login and password screen (Screen 3-2

If your password has expired you see the message:

Page 92

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

555-230-126

Issue 2

January 1998

Page 3-8Switch-Based Bulletin Board Message Notification

Password: Your Password has expired, enter a new one.

Reenter Current Password:

Reenter New Password:

New Password:

Screen 3-2. Password Expiration Screen

The Password Expiration screen is displayed when you log in. If your 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. If facility test call notification or remote access notification are enabled for your

login (see Adding Customer Logins and Assigning Initial Passwords, below), you receive a logoff screen. If either the facility test call or remote access acknowledgments are required, you need to respond to the Proceed with Logoff? prompt on the logoff screen. The response is defaulted to n; you will need to enter y to override the defa ult.

CAUTION:

To leave the facility test call administered after you logoff poses a significant security risk.

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 Te st C a ll fe a ture .

Page 93

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

Facility Test Call Administered Remote Access Administered

Proceed with Logoff? [n]

555-230-126

Screen 3-3. Logoff Screen

To Display a Login

To display a specified login:

Issue 2

January 1998

Page 3-9Switch-Based Bulletin Board Message Notification

1. Enter the command displa y logi n [logi n name] and press the

To List Logins

To list all of the system logins and the status of each login:

2. Enter the command list logins.

Enter key.

The system displays the requested login’s:

■ Name

■ Login type

■ Service level

■ Access to INADS Port value (V4)

■ Pas swor d agin g cycle len g th

■ Facility test call notification and acknowledgment

■ Remote access notification and acknowledgment

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)

The system displays only those logins wit h the same, or lower, se rvi ce level as the requestor.

To Remov e a Login

To remove a login from the system:

1. Enter the command remove l ogin [login name].

■ Pas swor d agin g cycle len gth

Page 94

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

555-230-126

The system displays the Login Administration form.

Issue 2

January 1998

Page 3-10Switch-Based Bulletin Board Message Notification

2. Press the

Enter key to remove the login, or press Cancel to exit the remove

To Test a Login

1. Enter your login name at the login prompt.

Password:vvvvvvvvcf

Screen 3-4. Logi n Prompt Form

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 th e 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 [nam e] command is displayed in the Login’s Name field.

3. Enter customer in the Login Type field. The system default 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 non-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

Page 95

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

555-230-126

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 i s y.

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. This step is valid for V4 and higher systems only.

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).

Issue 2

January 1998

Page 3-11Switch-Based Bulletin Board Message Notification

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. Decide whether or not to leave the default of yes (“y”) in the Facility Test Call Notification? field. If you retain the default, 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.

11. Deci de w he t h er or not to le av e the default of yes (“y”) in the F acility Te st Call Notification Acknowledgment Required field. If you retain the default, the user is required to ackn ow ledge that the y w ish to logoff while Facility Test Call is st ill administer ed. If you do no t wan t to f or c e the u s er 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 you retain the default, 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.

Page 96

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

CAUTION:

555-230-126

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 you retain the default, 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 2

January 1998

Page 3-12Switch-Based Bulletin Board Message Notification

Password of Login Making Change:

LOGOFF NOTIFICATION

Facility Test Call Notification? y Acknowledgment Required? y

Remote Access Notification? y Acknowledgment Required? y

Access to INADS Port?

Screen 3-5. Login Administration

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 fo r the s uper-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 [name ] comm and 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.

Page 97

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

555-230-126

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.

6. To allow access to the remote administration port, enter y in the Access to INADS Port? field. This field only displays if Lucent 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

8. Re-enter the password in the Login’s Password field. The system will not echo the password to the screen as you type.

Issue 2

January 1998

Page 3-13Switch-Based Bulletin Board Message Notification

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.

Administering Login Command Permissions

To administer command permissions, log in as super-user and:

1. Access the Command Permissions Categories form by entering the command change permissions login [login name]. When the Command Permission Categories form is displayed for a login, the default permissions for that “login type” are shown on the form. The super-user administering the login can change a y to n for each subcategory field on the form.

2. Select a category for the login and enter y in each field where permission to perform a 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.

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

Page 98

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

555-230-126

January 1998

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

MAINTENANCE COMMANDS Maintain Stations? n Maintain Switch Circuit Packs? n Maintain Trunks? n Maintain Process Circuit Packs? n Maintain Systems? n

Issue 2

Page 3-14Switch-Based Bulletin Board Message Notification

Screen 3-6. Command Permission Categories (Page 1 of 3)

Page 2 of 3

RESTRICTED OBJECT LIST _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ _______________________ ______________________ _______________________ ______________________

COMMAND PERMISSION CATEGORIES

Screen 3-7. Command Permissions Categories (Page 2 of 3)

Page 99

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

Page 3 of 3

555-230-126

COMMAND PERMISSION CATEGORIES

January 1998

Screen 3-8. Command Permissions Categories (Page 3 of 3)

Table 3-1. Command Permissions Form Entries — Display Administration and

Maintenance

Issue 2

Page 3-15Switch-Based Bulletin Board Message Notification

Action

Object

Change Display List Monitor Remove Status

aar analysis X X aar digit-conversion X X aar rout e-chosen X abbreviated-dialing 7103A-buttons X abbreviated-dialing enhanced X abbreviated-dialing group X X abbreviated-dialing personal X X abbreviated-dialing system X aca-parameters X access-endpoint X X X X adjunct-names X adjunt-controlled-agents X administered-connection X X X agent-loginID X X alarms X X alias-station X alphanumeric-dial-table X alternate-frl X

Tes

Continued on next page

Page 100

DEFINITY Enterprise Com munications Server Release 6 Maintenance for R6r Vol u m es 1 & 2

Management Terminal

555-230-126

Issue 2

January 1998

Page 3-16Switch-Based Bulletin Board Message Notification

Table 3-1. Command Permissions Form Entries — Display Administration and

Maintenance — Continued

Action

Object

Change Display List Monitor Remove Status

analog -testcall X announcement s X ars anal ysis X X ars anal ysis X ars digit-conversion X ars digit-conversion X ars route-chosen X ars-toll X attendant X X bcms agent X bcms ligni tes X bcms sp lit X bcms trunk X bcms vdn X board X bri-port X bridged-extens io ns X bullet in-board X button- lo cation-aca X cabinet X X call-forwar din g X call-screening X capacity X card-mem cdr-link XX circuit-pa ck s X communicatio n-interface hop-channels X X communi cation-interface links X communi cation-interface

proc-channels config ur a tio n al l X

Tes

Continued on next page

AT&T Definity Enterprise Definity ECS R6 - Maintenance for R6r

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

About This Book

Safety Precautions

Class 1 Laser Device

Electromagnetic Compatibility Standards

European Union Standards

Standards Compliance

Conven tions Use d in This Doc ume nt

Intended Use

How to Use this Document

Organization

Trademar ks a nd Se rvice Marks

Related Documents

Federal Comm unications Commi ssion Statement

Part 68: Statement

Means of Connection

How to Or der Doc um e n tation

How to Comment on This Document

Maintenance Architecture

What’s new for R6.2r

Multiple feature offers

Offer Security

Initializ ation

Password/System Security

Remote Port Security Device (RPSD)

Softlock

Locking administered passwords

Init logins

There are no changes to these logins for R6.2.

INADS and craft logins

Multimedia Call Handling (MMCH) Enhancements

Maintenance Objects

Alarm and Error Reporting

Alarm and Error Logs

INADS Alarm Reporting

Port Network Con nectivity (PNC)

PNC Configurations

SPE Dupli ca tion

Standby SPE Availability

Standby SPE State of Health

Standby SPE Maintenance Architecture

Standby Maintenance Monitor Software

Handshake Communication

Maintenance of Standby Components

Locking th e Active SPE

Memory Shadowing

Initialization: Bringing the Standby SPE Up

Power Interruptions

Nominal Power Holdover

Effects of Power Interruptions

PPN Cabinet with Power Holdover

EPN Cabinet with Power Holdover

External Alarm Leads

Protocols

Layers

Usage

Layer-1 Protocols

Layer-2 Protocols

Protocol States

Connectivity Rules

Disconnect Supervision

Transfer on Ringing

Conference, Transfer, and Call-Forwar ding Denial

Transmission Characteristics

Frequency Response

Intermodulation Distortion

Quantization Distortion Loss

Impulse Noise

ERL and SFRL Talking State

Peak Noise Level

Echo Path Delay

Service Codes

Facility Interface Codes

Multimed ia I nt er face (M MI )

Hardware Configurations

Multi- Ca r rier Cabinet